From ea1f8d4d643710d5d49bd5bd98b743579e8dc31e Mon Sep 17 00:00:00 2001
From: protectionsmachine
 <72879786+protectionsmachine@users.noreply.github.com>
Date: Wed, 15 May 2024 15:04:11 +0000
Subject: [PATCH] Update latest docs

---
 ...-keychain-credentials-directories.asciidoc |  136 +
 ...behavior-detected-elastic-endgame.asciidoc |   59 +
 ...xecution-at-volume-root-directory.asciidoc |   73 +
 ...ion-with-administrator-privileges.asciidoc |  111 +
 ...authorization-plugin-modification.asciidoc |  106 +
 ...credential-fetch-via-assumed-role.asciidoc |  124 +
 ...-component-object-model-hijacking.asciidoc |  208 ++
 ...n-to-commonly-abused-web-services.asciidoc |  297 +++
 ...4-1-container-workload-protection.asciidoc |   60 +
 ...-dumping-detected-elastic-endgame.asciidoc |   76 +
 ...dumping-prevented-elastic-endgame.asciidoc |   76 +
 ...pulation-detected-elastic-endgame.asciidoc |   72 +
 ...ulation-prevented-elastic-endgame.asciidoc |   72 +
 ...2-ami-shared-with-another-account.asciidoc |  118 +
 ...ilt-rule-8-14-1-endpoint-security.asciidoc |   59 +
 ...s-or-groups-via-built-in-commands.asciidoc |  127 +
 ...-exploit-detected-elastic-endgame.asciidoc |   77 +
 ...exploit-prevented-elastic-endgame.asciidoc |   77 +
 ...built-rule-8-14-1-external-alerts.asciidoc |   68 +
 ...ync-plugin-registered-and-enabled.asciidoc |  116 +
 ...ssword-retrieval-via-command-line.asciidoc |  117 +
 ...ller-package-spawns-network-event.asciidoc |  119 +
 ...-malware-detected-elastic-endgame.asciidoc |   59 +
 ...malware-prevented-elastic-endgame.asciidoc |   59 +
 ...-via-unsigned-or-untrusted-parent.asciidoc |  116 +
 ...on-theft-detected-elastic-endgame.asciidoc |   72 +
 ...n-theft-prevented-elastic-endgame.asciidoc |   72 +
 ...-via-docker-shortcut-modification.asciidoc |  101 +
 ...sistence-via-folder-action-script.asciidoc |  108 +
 ...tial-admin-group-account-addition.asciidoc |  107 +
 ...e-download-via-a-headless-browser.asciidoc |  108 +
 ...ential-persistence-via-login-hook.asciidoc |  117 +
 ...ershell-hacktool-script-by-author.asciidoc |  115 +
 ...h-count-of-readme-files-by-system.asciidoc |  125 +
 ...somware-note-file-dropped-via-smb.asciidoc |  136 +
 ...e-infection-across-multiple-hosts.asciidoc |   66 +
 ...njection-detected-elastic-endgame.asciidoc |   72 +
 ...jection-prevented-elastic-endgame.asciidoc |   72 +
 ...pt-for-credentials-with-osascript.asciidoc |  111 +
 ...-by-unsigned-or-untrusted-process.asciidoc |  110 +
 ...nsomware-detected-elastic-endgame.asciidoc |   59 +
 ...somware-prevented-elastic-endgame.asciidoc |   59 +
 ...r-query-log-configuration-deleted.asciidoc |  123 +
 ...ell-execution-via-apple-scripting.asciidoc |  101 +
 ...-suspicious-browser-child-process.asciidoc |  128 +
 ...1-suspicious-file-renamed-via-smb.asciidoc |  138 +
 ...ous-macos-ms-office-child-process.asciidoc |  168 ++
 ...web-browser-sensitive-file-access.asciidoc |  115 +
 ...systemkey-access-via-command-line.asciidoc |  104 +
 ...via-microsoft-common-console-file.asciidoc |  124 +
 ...-1-webproxy-settings-modification.asciidoc |  104 +
 .../prebuilt-rules-8-14-1-appendix.asciidoc   |   57 +
 .../prebuilt-rules-8-14-1-summary.asciidoc    |  114 +
 ...ebuilt-rules-downloadable-updates.asciidoc |  140 +-
 .../prebuilt-rules-reference.asciidoc         | 2228 +++++++++++------
 .../prebuilt-rules/rule-desc-index.asciidoc   |  468 +++-
 .../a-scheduled-task-was-created.asciidoc     |   78 +-
 .../a-scheduled-task-was-updated.asciidoc     |   85 +-
 ...l-process-id-or-lock-file-created.asciidoc |  198 +-
 .../abnormally-large-dns-response.asciidoc    |  124 +-
 ...ed-default-telnet-port-connection.asciidoc |  114 +-
 ...ess-to-a-sensitive-ldap-attribute.asciidoc |  100 +-
 ...-keychain-credentials-directories.asciidoc |  183 +-
 .../accessing-outlook-data-files.asciidoc     |   69 +
 ...ured-with-never-expiring-password.asciidoc |  105 +-
 ...covery-command-via-system-account.asciidoc |  228 +-
 ...roup-discovery-via-built-in-tools.asciidoc |   92 +
 .../account-password-reset-remotely.asciidoc  |  139 +-
 ...-hidden-file-attribute-via-attrib.asciidoc |  177 +-
 .../adfind-command-activity.asciidoc          |  215 +-
 ...vileges-assigned-to-an-okta-group.asciidoc |   75 +-
 ...tor-role-assigned-to-an-okta-user.asciidoc |   66 +-
 .../adminsdholder-backdoor.asciidoc           |   62 +-
 ...insdholder-sdprop-exclusion-added.asciidoc |  154 +-
 .../adobe-hijack-persistence.asciidoc         |  203 +-
 ...behavior-detected-elastic-endgame.asciidoc |   66 +-
 ...gent-spoofing-mismatched-agent-id.asciidoc |   43 +-
 ...g-multiple-hosts-using-same-agent.asciidoc |   40 +-
 ...xecution-at-volume-root-directory.asciidoc |   73 +
 ...anomalous-linux-compiler-activity.asciidoc |   56 +-
 ...us-process-for-a-linux-population.asciidoc |  119 +-
 ...-process-for-a-windows-population.asciidoc |  156 +-
 ...nomalous-windows-process-creation.asciidoc |  134 +-
 ...on-followed-by-network-connection.asciidoc |  123 +-
 ...ion-with-administrator-privileges.asciidoc |   92 +-
 ...-added-to-google-workspace-domain.asciidoc |  144 +-
 ...rom-blocklist-in-google-workspace.asciidoc |  120 +-
 ...chive-file-with-unusual-extension.asciidoc |   83 +
 .../at-exe-command-lateral-movement.asciidoc  |   81 +
 ...tempt-to-clear-kernel-ring-buffer.asciidoc |  114 +
 .../attempt-to-create-okta-api-token.asciidoc |   76 +-
 ...to-deactivate-an-okta-application.asciidoc |  101 +-
 ...o-deactivate-an-okta-network-zone.asciidoc |  105 +-
 ...to-deactivate-an-okta-policy-rule.asciidoc |  123 +-
 ...empt-to-deactivate-an-okta-policy.asciidoc |  123 +-
 ...mpt-to-delete-an-okta-application.asciidoc |   68 +-
 ...pt-to-delete-an-okta-network-zone.asciidoc |  105 +-
 ...mpt-to-delete-an-okta-policy-rule.asciidoc |  112 +-
 .../attempt-to-delete-an-okta-policy.asciidoc |  123 +-
 .../attempt-to-disable-gatekeeper.asciidoc    |   91 +-
 ...t-to-disable-iptables-or-firewall.asciidoc |  117 +
 ...attempt-to-disable-syslog-service.asciidoc |  133 +-
 ...ttempt-to-enable-the-root-account.asciidoc |   86 +-
 ...mpt-to-install-kali-linux-via-wsl.asciidoc |   73 +
 ...tempt-to-install-root-certificate.asciidoc |   97 +-
 ...mpt-to-modify-an-okta-application.asciidoc |   68 +-
 ...pt-to-modify-an-okta-network-zone.asciidoc |  132 +-
 ...mpt-to-modify-an-okta-policy-rule.asciidoc |  128 +-
 .../attempt-to-modify-an-okta-policy.asciidoc |  112 +-
 ...-mount-smb-share-via-command-line.asciidoc |  108 +-
 ...-factors-for-an-okta-user-account.asciidoc |   75 +-
 .../attempt-to-revoke-okta-api-token.asciidoc |  106 +-
 ...ndpoint-security-kernel-extension.asciidoc |   94 +-
 .../attempted-bypass-of-okta-mfa.asciidoc     |  117 +-
 .../attempted-private-key-access.asciidoc     |   82 +
 ...orce-a-microsoft-365-user-account.asciidoc |  113 +-
 ...-brute-force-an-okta-user-account.asciidoc |  112 +-
 ...authorization-plugin-modification.asciidoc |   97 +-
 ...se-denied-models-by-a-single-user.asciidoc |   69 +
 ...s-within-a-single-blocked-request.asciidoc |   70 +
 ...s-by-a-single-user-over-a-session.asciidoc |   69 +
 .../aws-cloudtrail-log-created.asciidoc       |   84 +-
 .../aws-cloudtrail-log-deleted.asciidoc       |  140 +-
 .../aws-cloudtrail-log-suspended.asciidoc     |  137 +-
 .../aws-cloudtrail-log-updated.asciidoc       |  142 +-
 .../aws-cloudwatch-alarm-deletion.asciidoc    |  131 +-
 ...aws-cloudwatch-log-group-deletion.asciidoc |  144 +-
 ...ws-cloudwatch-log-stream-deletion.asciidoc |  144 +-
 .../aws-config-resource-deletion.asciidoc     |  142 +-
 ...ws-configuration-recorder-stopped.asciidoc |   85 +-
 ...s-searched-for-inside-a-container.asciidoc |   70 +
 ...letion-of-rds-instance-or-cluster.asciidoc |  104 +-
 ...credential-fetch-via-assumed-role.asciidoc |  124 +
 .../aws-ec2-encryption-disabled.asciidoc      |   86 +-
 ...l-network-packet-capture-detected.asciidoc |   77 +-
 ...work-access-control-list-creation.asciidoc |   87 +-
 ...work-access-control-list-deletion.asciidoc |   90 +-
 .../aws-ec2-snapshot-activity.asciidoc        |  127 +-
 .../aws-ec2-vm-export-failure.asciidoc        |   64 +-
 ...-efs-file-system-or-mount-deleted.asciidoc |   76 +-
 ...lasticache-security-group-created.asciidoc |   75 +-
 ...ecurity-group-modified-or-deleted.asciidoc |   80 +-
 ...ntbridge-rule-disabled-or-deleted.asciidoc |   75 +-
 .../aws-execution-via-system-manager.asciidoc |  138 +-
 .../aws-guardduty-detector-deletion.asciidoc  |   88 +-
 ...aws-iam-assume-role-policy-update.asciidoc |  131 +-
 ...brute-force-of-assume-role-policy.asciidoc |  139 +-
 ...ws-iam-deactivation-of-mfa-device.asciidoc |  126 +-
 .../aws-iam-group-creation.asciidoc           |   89 +-
 .../aws-iam-group-deletion.asciidoc           |   81 +-
 ...s-iam-login-profile-added-to-user.asciidoc |   75 +
 ...s-iam-password-recovery-requested.asciidoc |   82 +-
 .../aws-iam-user-addition-to-group.asciidoc   |  131 +-
 ...isabled-or-scheduled-for-deletion.asciidoc |   48 +-
 ...brute-force-of-root-user-identity.asciidoc |   67 +-
 ...aws-management-console-root-login.asciidoc |  129 +-
 .../aws-rds-cluster-creation.asciidoc         |   89 +-
 ...aws-rds-instance-cluster-stoppage.asciidoc |   81 +-
 .../aws-rds-instance-creation.asciidoc        |   69 +-
 .../aws-rds-security-group-creation.asciidoc  |   71 +-
 .../aws-rds-security-group-deletion.asciidoc  |   67 +-
 .../aws-rds-snapshot-export.asciidoc          |   62 +-
 .../aws-rds-snapshot-restored.asciidoc        |   74 +-
 .../aws-redshift-cluster-creation.asciidoc    |   62 +-
 .../aws-root-login-without-mfa.asciidoc       |  135 +-
 ...-53-domain-transfer-lock-disabled.asciidoc |   64 +-
 ...in-transferred-to-another-account.asciidoc |   65 +-
 .../aws-route-table-created.asciidoc          |   78 +-
 ...s-route-table-modified-or-deleted.asciidoc |   72 +-
 ...hosted-zone-associated-with-a-vpc.asciidoc |   68 +-
 ...-s3-bucket-configuration-deletion.asciidoc |   88 +-
 ...bucket-enumeration-or-brute-force.asciidoc |  147 ++
 .../rule-details/aws-saml-activity.asciidoc   |   76 +-
 ...up-configuration-change-detection.asciidoc |  100 +-
 ...oken-service-sts-assumerole-usage.asciidoc |   83 +-
 .../aws-sts-getsessiontoken-abuse.asciidoc    |   76 +-
 .../aws-vpc-flow-logs-deletion.asciidoc       |  137 +-
 ...-waf-access-control-list-deletion.asciidoc |   88 +-
 ...s-waf-rule-or-rule-group-deletion.asciidoc |   98 +-
 ...ctive-directory-high-risk-sign-in.asciidoc |  116 +-
 ...-high-risk-user-sign-in-heuristic.asciidoc |  100 +-
 ...tive-directory-powershell-sign-in.asciidoc |  122 +-
 ...lobal-administrator-role-assigned.asciidoc |   67 +-
 ...pression-rule-created-or-modified.asciidoc |   69 +-
 ...plication-credential-modification.asciidoc |   71 +-
 .../azure-automation-account-created.asciidoc |   84 +-
 ...ation-runbook-created-or-modified.asciidoc |   89 +-
 .../azure-automation-runbook-deleted.asciidoc |   99 +-
 .../azure-automation-webhook-created.asciidoc |   85 +-
 ...ntainer-access-level-modification.asciidoc |   86 +-
 ...ure-blob-permissions-modification.asciidoc |   75 +-
 ...mand-execution-on-virtual-machine.asciidoc |   84 +-
 ...onditional-access-policy-modified.asciidoc |   86 +-
 ...zure-diagnostic-settings-deletion.asciidoc |   87 +-
 ...orization-rule-created-or-updated.asciidoc |   88 +-
 .../azure-event-hub-deletion.asciidoc         |   91 +-
 ...re-external-guest-user-invitation.asciidoc |   81 +-
 .../azure-firewall-policy-deletion.asciidoc   |   90 +-
 ...ation-firewall-waf-policy-deleted.asciidoc |   65 +-
 ...l-network-packet-capture-detected.asciidoc |   74 +-
 ...strator-role-addition-to-pim-user.asciidoc |   91 +-
 .../azure-key-vault-modified.asciidoc         |   87 +-
 .../azure-kubernetes-events-deleted.asciidoc  |   79 +-
 .../azure-kubernetes-pods-deleted.asciidoc    |   70 +-
 ...e-kubernetes-rolebindings-created.asciidoc |   70 +-
 .../azure-network-watcher-deletion.asciidoc   |   90 +-
 ...identity-management-role-modified.asciidoc |  124 +-
 .../azure-resource-group-deletion.asciidoc    |   90 +-
 .../azure-service-principal-addition.asciidoc |  119 +-
 ...rvice-principal-credentials-added.asciidoc |   67 +-
 ...e-storage-account-key-regenerated.asciidoc |   84 +-
 ...etwork-device-modified-or-deleted.asciidoc |  112 +-
 ...base32-encoding-decoding-activity.asciidoc |  130 +-
 .../bash-shell-profile-modification.asciidoc  |   81 +-
 .../binary-content-copy-via-cmd-exe.asciidoc  |   76 +
 ...uted-from-shared-memory-directory.asciidoc |  110 +-
 .../rule-details/bitsadmin-activity.asciidoc  |   86 +
 .../bpf-filter-applied-using-tc.asciidoc      |   91 +-
 .../browser-extension-install.asciidoc        |   76 +
 .../bypass-uac-via-event-viewer.asciidoc      |  234 +-
 .../cap-sys-admin-assigned-to-binary.asciidoc |   96 +
 .../chkconfig-service-add.asciidoc            |  192 +-
 .../clearing-windows-console-history.asciidoc |  160 +-
 .../clearing-windows-event-logs.asciidoc      |  218 +-
 ...strike-command-and-control-beacon.asciidoc |   90 +-
 ...dification-through-built-in-tools.asciidoc |  135 +
 ...icy-modification-through-registry.asciidoc |  146 ++
 ...-execution-via-solarwinds-process.asciidoc |  115 +-
 ...command-prompt-network-connection.asciidoc |  187 +-
 ...ell-activity-started-via-rundll32.asciidoc |  126 +-
 .../component-object-model-hijacking.asciidoc |  319 +--
 ...ion-dll-loaded-by-unusual-process.asciidoc |   78 +
 ...wned-by-suspicious-parent-process.asciidoc |  191 +-
 ...ed-free-ssl-certificate-providers.asciidoc |  113 +-
 ...n-to-commonly-abused-web-services.asciidoc |  479 ++--
 ...on-to-external-network-via-telnet.asciidoc |  151 +-
 ...on-to-internal-network-via-telnet.asciidoc |  151 +-
 ...nt-utility-run-inside-a-container.asciidoc |   60 +
 .../container-workload-protection.asciidoc    |   60 +
 ...el-process-with-unusual-arguments.asciidoc |  121 +-
 .../creation-of-a-dns-named-record.asciidoc   |   95 +
 ...on-of-a-hidden-local-user-account.asciidoc |  121 +-
 ...s-and-directories-via-commandline.asciidoc |  149 +-
 ...-of-hidden-launch-agent-or-daemon.asciidoc |  117 +-
 ...idden-login-item-via-apple-script.asciidoc |   98 +-
 ...tion-of-hidden-shared-object-file.asciidoc |  110 +-
 .../creation-of-kernel-module.asciidoc        |   69 +
 ...eation-of-settingcontent-ms-files.asciidoc |   83 +
 ...new-gpo-scheduled-task-or-service.asciidoc |  122 +-
 ...f-domain-backup-dpapi-private-key.asciidoc |  111 +-
 ...-modification-of-root-certificate.asciidoc |  215 +-
 ...isition-via-registry-hive-dumping.asciidoc |  175 +-
 ...-dumping-detected-elastic-endgame.asciidoc |   81 +-
 ...dumping-prevented-elastic-endgame.asciidoc |   81 +-
 ...pulation-detected-elastic-endgame.asciidoc |   79 +-
 ...ulation-prevented-elastic-endgame.asciidoc |   79 +-
 ...ged-by-previously-unknown-process.asciidoc |  226 ++
 ...-privileged-access-security-error.asciidoc |   60 +-
 ...cess-security-recommended-monitor.asciidoc |   68 +-
 ...lt-strike-team-server-certificate.asciidoc |   94 +-
 .../delayed-execution-via-ping.asciidoc       |  148 ++
 ...te-volume-usn-journal-with-fsutil.asciidoc |  151 +-
 ...ting-backup-catalogs-with-wbadmin.asciidoc |  177 +-
 .../direct-outbound-smb-connection.asciidoc   |  198 +-
 ...ecurity-logs-using-built-in-tools.asciidoc |  183 +-
 ...-windows-firewall-rules-via-netsh.asciidoc |  175 +-
 ...control-via-registry-modification.asciidoc |  178 +-
 ...-security-settings-via-powershell.asciidoc |  166 +-
 .../discovery-of-domain-groups.asciidoc       |   68 +
 ...t-capabilities-via-built-in-tools.asciidoc |   66 +
 ...s-over-https-enabled-via-registry.asciidoc |   90 +-
 .../rule-details/dns-tunneling.asciidoc       |   51 +-
 ...-google-workspace-trusted-domains.asciidoc |  145 +-
 .../downloaded-shortcut-files.asciidoc        |   79 +
 .../downloaded-url-files.asciidoc             |   77 +
 ...ount-hashes-via-built-in-commands.asciidoc |   83 +-
 ...hain-content-via-security-command.asciidoc |   87 +-
 .../rule-details/dynamic-linker-copy.asciidoc |  177 +-
 ...2-ami-shared-with-another-account.asciidoc |  118 +
 .../eggshell-backdoor-execution.asciidoc      |   51 +-
 .../elastic-agent-service-terminated.asciidoc |  127 +-
 ...nd-rules-creation-or-modification.asciidoc |   98 +-
 ...-host-network-discovery-via-netsh.asciidoc |  128 +-
 ...executable-stored-in-the-registry.asciidoc |   70 +-
 ...ncrypting-files-with-winrar-or-7z.asciidoc |  178 +-
 .../rule-details/endpoint-security.asciidoc   |   48 +-
 ...ing-domain-trusts-via-dsquery-exe.asciidoc |  121 +
 ...ting-domain-trusts-via-nltest-exe.asciidoc |  126 +
 ...tion-command-spawned-via-wmiprvse.asciidoc |  141 +-
 ...eration-of-administrator-accounts.asciidoc |  192 +-
 ...ration-of-kernel-modules-via-proc.asciidoc |   84 +
 .../enumeration-of-kernel-modules.asciidoc    |  111 +-
 ...rivileged-local-groups-membership.asciidoc |  259 +-
 ...s-or-groups-via-built-in-commands.asciidoc |  176 +-
 .../esxi-discovery-via-find.asciidoc          |  104 +
 .../esxi-discovery-via-grep.asciidoc          |  106 +
 ...-timestomping-using-touch-command.asciidoc |  109 +
 ...nge-mailbox-export-via-powershell.asciidoc |  130 +
 ...creation-with-multiple-extensions.asciidoc |  114 +-
 ...table-file-with-unusual-extension.asciidoc |   80 +
 ...le-masquerading-as-kernel-process.asciidoc |  110 +
 ...ble-media-with-network-connection.asciidoc |   68 +
 ...om-unusual-directory-command-line.asciidoc |  560 ++---
 .../execution-of-an-unsigned-service.asciidoc |   80 +
 ...ecution-of-com-object-via-xwizard.asciidoc |   93 +-
 ...n-or-modified-by-microsoft-office.asciidoc |  163 +-
 ...written-or-modified-by-pdf-reader.asciidoc |  164 +-
 ...-of-persistent-suspicious-program.asciidoc |  107 +-
 ...tron-child-process-node-js-module.asciidoc |  109 +
 ...ution-via-local-sxs-shared-module.asciidoc |   88 +-
 ...a-microsoft-dotnet-clickonce-host.asciidoc |   71 +
 ...isualstudio-pre-post-build-events.asciidoc |  108 +
 ...ssql-xp-cmdshell-stored-procedure.asciidoc |  155 ++
 ...execution-via-tsclient-mountpoint.asciidoc |   82 +-
 ...n-via-windows-subsystem-for-linux.asciidoc |   76 +
 ...xplicit-credentials-via-scripting.asciidoc |  120 +-
 .../expired-or-revoked-driver-loaded.asciidoc |   75 +
 .../exploit-detected-elastic-endgame.asciidoc |   81 +-
 ...exploit-prevented-elastic-endgame.asciidoc |   81 +-
 ...g-exchange-mailbox-via-powershell.asciidoc |  181 +-
 .../rule-details/external-alerts.asciidoc     |   62 +-
 ...p-lookup-from-non-browser-process.asciidoc |  248 +-
 ...r-added-to-google-workspace-group.asciidoc |  141 ++
 ...irectory-permissions-modification.asciidoc |   73 +
 ...ed-or-archived-into-common-format.asciidoc |  168 ++
 ...-deletion-in-suspicious-directory.asciidoc |  109 +
 .../file-creation-time-changed.asciidoc       |   84 +
 .../file-deletion-via-shred.asciidoc          |  112 +-
 ...able-via-chmod-inside-a-container.asciidoc |   76 +
 .../file-made-immutable-by-chattr.asciidoc    |  107 +-
 ...ile-or-directory-deletion-command.asciidoc |   78 +
 ...odification-in-writable-directory.asciidoc |  123 +-
 ...ged-in-root-folder-of-recycle-bin.asciidoc |   67 +
 ...hed-inside-a-privileged-container.asciidoc |   65 +
 ...r-listener-established-via-netcat.asciidoc |  238 +-
 ...h-suspicious-extension-downloaded.asciidoc |   98 +
 ...ync-plugin-registered-and-enabled.asciidoc |  127 +-
 ...t-for-a-personal-access-token-pat.asciidoc |   62 +
 ...ub-repo-interaction-from-a-new-ip.asciidoc |   62 +
 ...ser-interaction-with-private-repo.asciidoc |   62 +
 ...-github-personal-access-token-pat.asciidoc |   66 +
 ...nce-of-ip-address-for-github-user.asciidoc |   65 +
 ...ta-user-session-started-via-proxy.asciidoc |  111 +
 ...s-token-pat-use-for-a-github-user.asciidoc |   66 +
 ...-github-personal-access-token-pat.asciidoc |   63 +
 ...-github-personal-access-token-pat.asciidoc |   66 +
 ...e-of-user-agent-for-a-github-user.asciidoc |   65 +
 ...value-accessed-in-secrets-manager.asciidoc |  132 +
 ...used-remote-access-tool-execution.asciidoc |  310 +++
 .../first-time-seen-driver-loaded.asciidoc    |  153 ++
 ...ogin-from-third-party-application.asciidoc |  103 +
 ...seen-newcredentials-logon-process.asciidoc |   66 +
 .../first-time-seen-removable-device.asciidoc |   80 +
 ...me-seen-account-performing-dcsync.asciidoc |  164 ++
 ...d-google-workspace-security-alert.asciidoc |   65 +
 ...er-mode-dumps-enabled-system-wide.asciidoc |   56 +-
 .../gcp-firewall-rule-creation.asciidoc       |   84 +-
 .../gcp-firewall-rule-deletion.asciidoc       |   84 +-
 .../gcp-firewall-rule-modification.asciidoc   |   84 +-
 .../gcp-iam-custom-role-creation.asciidoc     |   89 +-
 .../gcp-iam-role-deletion.asciidoc            |   87 +-
 ...-iam-service-account-key-deletion.asciidoc |   90 +-
 .../gcp-logging-bucket-deletion.asciidoc      |   93 +-
 .../gcp-logging-sink-deletion.asciidoc        |   90 +-
 .../gcp-logging-sink-modification.asciidoc    |   87 +-
 ...gcp-pub-sub-subscription-creation.asciidoc |   92 +-
 ...gcp-pub-sub-subscription-deletion.asciidoc |   90 +-
 .../gcp-pub-sub-topic-creation.asciidoc       |   92 +-
 .../gcp-pub-sub-topic-deletion.asciidoc       |   90 +-
 .../gcp-service-account-creation.asciidoc     |   87 +-
 .../gcp-service-account-deletion.asciidoc     |   87 +-
 .../gcp-service-account-disabled.asciidoc     |   87 +-
 .../gcp-service-account-key-creation.asciidoc |   87 +-
 ...bucket-configuration-modification.asciidoc |   91 +-
 .../gcp-storage-bucket-deletion.asciidoc      |   89 +-
 ...e-bucket-permissions-modification.asciidoc |   90 +-
 ...al-private-cloud-network-deletion.asciidoc |   89 +-
 ...tual-private-cloud-route-creation.asciidoc |  102 +-
 ...tual-private-cloud-route-deletion.asciidoc |   89 +-
 .../rule-details/github-app-deleted.asciidoc  |   58 +
 ...github-owner-role-granted-to-user.asciidoc |   63 +
 .../github-pat-access-revoked.asciidoc        |   60 +
 ...protected-branch-settings-changed.asciidoc |   63 +
 .../rule-details/github-repo-created.asciidoc |   60 +
 .../github-repository-deleted.asciidoc        |   59 +
 ...iple-alerts-from-a-github-account.asciidoc |   56 +
 ...ub-user-blocked-from-organization.asciidoc |   60 +
 ...-transferred-via-google-workspace.asciidoc |  111 +-
 ...gle-workspace-2sv-policy-disabled.asciidoc |  107 +-
 ...ace-admin-role-assigned-to-a-user.asciidoc |  159 +-
 ...gle-workspace-admin-role-deletion.asciidoc |  141 +-
 ...main-wide-delegation-of-authority.asciidoc |  142 +-
 ...kspace-bitlocker-setting-disabled.asciidoc |  112 +-
 ...rkspace-custom-admin-role-created.asciidoc |  145 +-
 ...m-gmail-route-created-or-modified.asciidoc |  112 +-
 ...ey-s-accessed-from-anonymous-user.asciidoc |   89 +
 ...orkspace-mfa-enforcement-disabled.asciidoc |  161 +-
 ...ess-granted-to-custom-application.asciidoc |  154 ++
 ...orkspace-password-policy-modified.asciidoc |  190 +-
 ...etplace-modified-to-allow-any-app.asciidoc |  123 +-
 .../google-workspace-role-modified.asciidoc   |  147 +-
 ...ce-suspended-user-account-renewed.asciidoc |   84 +
 ...-user-organizational-unit-changed.asciidoc |  117 +-
 ...licy-abuse-for-privilege-addition.asciidoc |  141 +-
 ...ry-via-microsoft-gpresult-utility.asciidoc |  112 +
 ...fbaked-command-and-control-beacon.asciidoc |   90 +-
 ...s-and-directories-via-hidden-flag.asciidoc |   70 +
 ...ocess-arguments-in-an-rdp-session.asciidoc |   92 +
 ...high-mean-of-rdp-session-duration.asciidoc |   92 +
 ...r-of-cloned-github-repos-from-pat.asciidoc |   61 +
 ...password-reset-or-unlock-attempts.asciidoc |  124 +-
 ...ocess-and-or-service-terminations.asciidoc |  117 +-
 ...gh-number-of-process-terminations.asciidoc |  139 +-
 ...-variance-in-rdp-session-duration.asciidoc |   92 +
 ...s-via-windows-subsystem-for-linux.asciidoc |   71 +
 .../rule-details/hosts-file-modified.asciidoc |  187 +-
 .../hping-process-activity.asciidoc           |  134 +-
 .../iis-http-logging-disabled.asciidoc        |  156 +-
 ...-file-execution-options-injection.asciidoc |  129 +-
 ...age-loaded-with-invalid-signature.asciidoc |   70 +
 ...windows-update-auto-update-client.asciidoc |  165 +-
 ...to-an-unsecure-elasticsearch-node.asciidoc |   80 +-
 ...g-dcom-lateral-movement-via-mshta.asciidoc |  133 +-
 ...ng-dcom-lateral-movement-with-mmc.asciidoc |  121 +-
 ...hellbrowserwindow-or-shellwindows.asciidoc |  109 +-
 ...execution-via-powershell-remoting.asciidoc |  110 +-
 ...-execution-via-winrm-remote-shell.asciidoc |   92 +-
 ...and-execution-via-forfiles-pcalua.asciidoc |   66 +
 ...ingress-transfer-via-windows-bits.asciidoc |  170 ++
 ...allation-of-custom-shim-databases.asciidoc |   89 +-
 ...tion-of-security-support-provider.asciidoc |  119 +-
 .../installutil-activity.asciidoc             |   70 +
 ...rocess-making-network-connections.asciidoc |   89 +-
 ...nched-against-a-running-container.asciidoc |   79 +
 ...ctive-logon-by-an-unusual-process.asciidoc |   98 +
 ...ractive-terminal-spawned-via-perl.asciidoc |  119 +-
 ...ctive-terminal-spawned-via-python.asciidoc |  138 +-
 ...ipsec-nat-traversal-port-activity.asciidoc |   80 +-
 ...rberos-cached-credentials-dumping.asciidoc |  100 +-
 ...-authentication-disabled-for-user.asciidoc |  148 +-
 ...eros-traffic-from-unusual-process.asciidoc |  253 +-
 ...rnel-driver-load-by-non-root-user.asciidoc |  111 +
 .../rule-details/kernel-driver-load.asciidoc  |  101 +
 ...load-or-unload-via-kexec-detected.asciidoc |  132 +
 .../kernel-module-load-via-insmod.asciidoc    |  180 +-
 .../kernel-module-removal.asciidoc            |  126 +-
 ...ssword-retrieval-via-command-line.asciidoc |  114 +-
 .../rule-details/kirbi-file-creation.asciidoc |   65 +
 .../krbtgt-delegation-backdoor.asciidoc       |   71 +-
 ...etes-anonymous-request-authorized.asciidoc |   73 +-
 ...with-excessive-linux-capabilities.asciidoc |   83 +-
 ...es-denied-service-account-request.asciidoc |   52 +-
 ...ervice-created-with-type-nodeport.asciidoc |   68 +-
 ...-with-a-sensitive-hostpath-volume.asciidoc |  112 +-
 ...bernetes-pod-created-with-hostipc.asciidoc |   73 +-
 ...etes-pod-created-with-hostnetwork.asciidoc |   73 +-
 ...bernetes-pod-created-with-hostpid.asciidoc |   73 +-
 ...kubernetes-privileged-pod-created.asciidoc |   73 +-
 ...ent-of-controller-service-account.asciidoc |   72 +-
 ...es-suspicious-self-subject-review.asciidoc |   86 +-
 .../kubernetes-user-exec-into-pod.asciidoc    |   81 +-
 ...teral-movement-via-startup-folder.asciidoc |  103 +-
 ...odification-and-immediate-loading.asciidoc |  104 +-
 ...odification-and-immediate-loading.asciidoc |  113 +-
 .../linux-group-creation.asciidoc             |  158 ++
 ...ux-init-pid-1-secret-dump-via-gdb.asciidoc |  106 +
 .../linux-process-hooking-via-gdb.asciidoc    |   74 +
 ...shell-breakout-via-linux-binary-s.asciidoc |  245 ++
 ...inux-system-information-discovery.asciidoc |   69 +
 .../linux-user-account-creation.asciidoc      |  157 ++
 ...ux-user-added-to-privileged-group.asciidoc |  174 ++
 ...count-tokenfilter-policy-disabled.asciidoc |   69 +-
 .../local-scheduled-task-creation.asciidoc    |  204 +-
 .../lsass-memory-dump-creation.asciidoc       |  191 +-
 .../lsass-memory-dump-handle-access.asciidoc  |  189 +-
 ...ss-process-access-via-windows-api.asciidoc |  195 ++
 ...uest-predicted-to-be-a-dga-domain.asciidoc |  132 +
 ...with-a-high-dga-probability-score.asciidoc |  132 +
 ...redicted-to-be-malicious-activity.asciidoc |  134 +
 ...-high-malicious-probability-score.asciidoc |  135 +
 ...using-a-known-sunburst-dns-domain.asciidoc |  132 +
 ...ller-package-spawns-network-event.asciidoc |  147 +-
 .../malware-detected-elastic-endgame.asciidoc |   60 +-
 ...malware-prevented-elastic-endgame.asciidoc |   60 +-
 ...masquerading-space-after-filename.asciidoc |   56 +-
 ...-removed-from-github-organization.asciidoc |   60 +
 ...-dump-file-with-unusual-extension.asciidoc |   90 +
 ...-activation-for-okta-user-account.asciidoc |  120 +
 ...for-google-workspace-organization.asciidoc |  157 +-
 ...change-anti-phish-policy-deletion.asciidoc |   70 +-
 ...ange-anti-phish-rule-modification.asciidoc |   70 +-
 ...im-signing-configuration-disabled.asciidoc |   73 +-
 ...t-365-exchange-dlp-policy-removed.asciidoc |   70 +-
 ...ge-malware-filter-policy-deletion.asciidoc |   70 +-
 ...-malware-filter-rule-modification.asciidoc |   70 +-
 ...-management-group-role-assignment.asciidoc |   70 +-
 ...nge-safe-attachment-rule-disabled.asciidoc |   70 +-
 ...xchange-safe-link-policy-disabled.asciidoc |   70 +-
 ...-exchange-transport-rule-creation.asciidoc |   73 +-
 ...hange-transport-rule-modification.asciidoc |   70 +-
 ...lobal-administrator-role-assigned.asciidoc |   65 +-
 ...ft-365-impossible-travel-activity.asciidoc |   72 +
 ...365-inbox-forwarding-rule-created.asciidoc |  117 +-
 ...65-mass-download-by-a-single-user.asciidoc |   68 +
 ...365-potential-ransomware-activity.asciidoc |   64 +-
 ...m-application-interaction-allowed.asciidoc |   67 +-
 ...365-teams-external-access-enabled.asciidoc |   74 +-
 ...ft-365-teams-guest-access-enabled.asciidoc |   71 +-
 ...5-unusual-volume-of-file-deletion.asciidoc |   61 +-
 ...ser-restricted-from-sending-email.asciidoc |   61 +-
 ...engine-started-an-unusual-process.asciidoc |  127 +-
 ...ngine-started-by-a-script-process.asciidoc |  142 +-
 ...ngine-started-by-a-system-process.asciidoc |  120 +-
 ...-started-by-an-office-application.asciidoc |  199 +-
 ...ld-engine-using-an-alternate-name.asciidoc |  199 +-
 ...-um-spawning-suspicious-processes.asciidoc |  101 +-
 ...erver-um-writing-suspicious-files.asciidoc |  133 +-
 ...ge-transport-agent-install-script.asciidoc |  110 +
 ...ker-spawning-suspicious-processes.asciidoc |  103 +-
 ...iis-connection-strings-decryption.asciidoc |   99 +-
 ...s-service-account-password-dumped.asciidoc |  106 +-
 ...rosoft-windows-defender-tampering.asciidoc |  299 +--
 ...mimikatz-memssp-log-file-detected.asciidoc |  146 +-
 ...cation-of-amsienable-registry-key.asciidoc |  167 +-
 ...odification-of-boot-configuration.asciidoc |  184 +-
 ...-shared-object-inside-a-container.asciidoc |   65 +
 ...amic-linker-preload-shared-object.asciidoc |  108 +-
 ...-via-unsigned-or-untrusted-parent.asciidoc |  116 +
 .../modification-of-openssh-binaries.asciidoc |  215 +-
 ...ari-settings-via-defaults-command.asciidoc |  100 +-
 ...ntication-module-or-configuration.asciidoc |  126 +-
 ...on-of-the-mspkiaccountcredentials.asciidoc |   59 +-
 ...tion-of-wdigest-security-provider.asciidoc |  177 +-
 ...n-okta-application-sign-on-policy.asciidoc |   82 +-
 .../rule-details/mofcomp-activity.asciidoc    |   82 +
 ...hed-inside-a-privileged-container.asciidoc |   62 +
 ...ng-hidden-or-webdav-remote-shares.asciidoc |  125 +-
 ...o-security-registry-modifications.asciidoc |  180 +-
 ...sbuild-making-network-connections.asciidoc |  162 +-
 .../mshta-making-network-connections.asciidoc |  103 +-
 ...cation-disabled-for-an-azure-user.asciidoc |  122 +-
 ...t-att-ck-tactics-on-a-single-host.asciidoc |   28 +-
 .../multiple-alerts-involving-a-user.asciidoc |   45 +
 ...failure-followed-by-logon-success.asciidoc |  158 +-
 ...lure-from-the-same-source-address.asciidoc |  155 +-
 ...dresses-for-a-single-user-session.asciidoc |   79 +
 ...ssions-detected-for-a-single-user.asciidoc |   78 +
 ...-device-token-hash-behind-a-proxy.asciidoc |  138 +
 ...ltiple-vault-web-credentials-read.asciidoc |   81 +-
 .../rule-details/my-first-rule.asciidoc       |   61 +
 ...espace-manipulation-using-unshare.asciidoc |   96 +-
 ...er-established-inside-a-container.asciidoc |   74 +
 ...t-listener-established-via-rlwrap.asciidoc |  105 +
 .../rule-details/netsh-helper-dll.asciidoc    |   77 +
 ...network-activity-detected-via-cat.asciidoc |  185 ++
 ...ork-activity-detected-via-kworker.asciidoc |  124 +
 ...rom-binary-with-rwx-memory-region.asciidoc |  103 +
 .../network-connection-via-certutil.asciidoc  |  187 +-
 ...connection-via-compiled-html-file.asciidoc |  205 +-
 .../network-connection-via-msxsl.asciidoc     |  107 +-
 ...-via-recently-compiled-executable.asciidoc |  114 +
 ...nnection-via-registration-utility.asciidoc |  268 +-
 ...work-connection-via-signed-binary.asciidoc |  210 +-
 ...level-authentication-nla-disabled.asciidoc |   71 +
 ...on-provider-registry-modification.asciidoc |  167 +-
 ...k-traffic-capture-via-cap-net-raw.asciidoc |   99 +
 ...affic-to-rare-destination-country.asciidoc |   39 +-
 ...oweddeviceid-added-via-powershell.asciidoc |  111 +-
 .../new-github-app-installed.asciidoc         |   58 +
 .../new-github-owner-added.asciidoc           |   63 +
 ...-authentication-behavior-detected.asciidoc |  104 +
 ...ntity-provider-idp-added-by-admin.asciidoc |  114 +
 ...new-or-modified-federation-domain.asciidoc |   78 +-
 ...ted-by-previously-unknown-process.asciidoc |  220 ++
 .../new-systemd-timer-created.asciidoc        |  187 ++
 ...user-added-to-github-organization.asciidoc |   64 +
 .../nping-process-activity.asciidoc           |  129 +-
 .../ntds-or-sam-database-file-copied.asciidoc |  191 +-
 ...sessionpipe-registry-modification.asciidoc |   82 +-
 ...orted-by-user-as-malware-or-phish.asciidoc |   65 +-
 ...ssive-single-sign-on-logon-errors.asciidoc |   73 +-
 ...spicious-mailbox-right-delegation.asciidoc |   87 +-
 ...o365-mailbox-audit-logging-bypass.asciidoc |   65 +-
 .../office-test-registry-persistence.asciidoc |   75 +
 ...force-or-password-spraying-attack.asciidoc |  109 +-
 .../okta-fastpass-phishing-detection.asciidoc |   78 +
 ...ign-in-events-via-third-party-idp.asciidoc |  128 +
 ...nsight-threat-suspected-promotion.asciidoc |   66 +
 .../okta-user-session-impersonation.asciidoc  |   91 +-
 ...arted-from-different-geolocations.asciidoc |   79 +
 .../onedrive-malware-file-upload.asciidoc     |   57 +-
 ...uled-task-activity-via-powershell.asciidoc |  108 +-
 .../parent-process-pid-spoofing.asciidoc      |  142 +-
 .../peripheral-device-discovery.asciidoc      |  151 +-
 ...on-theft-detected-elastic-endgame.asciidoc |   79 +-
 ...n-theft-prevented-elastic-endgame.asciidoc |   79 +-
 ...tence-via-bits-job-notify-cmdline.asciidoc |   79 +-
 ...ectoryservice-plugin-modification.asciidoc |   82 +-
 ...-via-docker-shortcut-modification.asciidoc |   97 +-
 ...sistence-via-folder-action-script.asciidoc |  132 +-
 ...tence-via-hidden-run-key-detected.asciidoc |  149 +-
 ...ript-or-desktop-file-modification.asciidoc |  220 +-
 ...sistence-via-login-or-logout-hook.asciidoc |  114 +-
 ...tence-via-microsoft-office-addins.asciidoc |  100 +-
 ...istence-via-microsoft-outlook-vba.asciidoc |   81 +-
 ...ersistence-via-powershell-profile.asciidoc |  131 +-
 ...stence-via-scheduled-job-creation.asciidoc |   87 +-
 ...ycontroller-scheduled-task-hijack.asciidoc |  147 +-
 ...pdate-orchestrator-service-hijack.asciidoc |  244 +-
 ...stence-via-wmi-event-subscription.asciidoc |  112 +-
 ...ia-wmi-standard-registry-provider.asciidoc |  262 +-
 ...-scripts-in-the-startup-directory.asciidoc |  196 +-
 .../port-forwarding-rule-addition.asciidoc    |  167 +-
 ...-via-azure-registered-application.asciidoc |  160 +-
 ...-dga-command-and-control-behavior.asciidoc |   89 +-
 .../possible-okta-dos-attack.asciidoc         |   85 +-
 ...en-count-and-large-response-sizes.asciidoc |   73 +
 ...ning-via-wildcard-record-creation.asciidoc |   94 +
 ...tial-admin-group-account-addition.asciidoc |   91 +-
 ...n-interface-bypass-via-powershell.asciidoc |  167 ++
 ...-application-shimming-via-sdbinst.asciidoc |  124 +-
 ...l-buffer-overflow-attack-detected.asciidoc |   86 +
 ...chroot-container-escape-via-mount.asciidoc |  116 +
 ...ial-code-execution-via-postgresql.asciidoc |  106 +
 ...and-control-via-internet-explorer.asciidoc |  140 +-
 ...a-modified-notify-on-release-file.asciidoc |   63 +
 ...e-via-modified-release-agent-file.asciidoc |   64 +
 ...okies-theft-via-browser-debugging.asciidoc |   95 +-
 ...tial-credential-access-via-dcsync.asciidoc |  216 +-
 ...cess-via-duplicatehandle-in-lsass.asciidoc |   92 +-
 ...tial-access-via-lsass-memory-dump.asciidoc |  121 +-
 ...ess-via-memory-dump-file-creation.asciidoc |  106 +
 ...cess-via-renamed-com-services-dll.asciidoc |  171 +-
 ...ess-via-trusted-developer-utility.asciidoc |  221 +-
 ...tial-access-via-windows-utilities.asciidoc |  247 +-
 ...otential-cross-site-scripting-xss.asciidoc |   62 +
 ...-curl-cve-2023-38545-exploitation.asciidoc |  120 +
 ...ty-to-an-unusual-destination-port.asciidoc |   91 +
 ...activity-to-an-unusual-ip-address.asciidoc |   91 +
 ...n-activity-to-an-unusual-iso-code.asciidoc |   91 +
 ...ion-activity-to-an-unusual-region.asciidoc |   91 +
 ...ial-defense-evasion-via-cmstp-exe.asciidoc |   67 +
 ...tential-defense-evasion-via-proot.asciidoc |  101 +
 .../potential-dga-activity.asciidoc           |  122 +
 .../potential-disabling-of-apparmor.asciidoc  |  109 +
 .../potential-disabling-of-selinux.asciidoc   |  128 +-
 ...ft-antimalware-service-executable.asciidoc |  107 +-
 ...ng-via-trusted-microsoft-programs.asciidoc |   96 +
 ...ential-dns-tunneling-via-nslookup.asciidoc |  132 +-
 ...-via-active-directory-web-service.asciidoc |   74 +
 ...ential-evasion-via-filter-manager.asciidoc |  171 +-
 ...on-via-windows-filtering-platform.asciidoc |  134 +
 ...otential-execution-via-xzbackdoor.asciidoc |   98 +
 ...quoted-service-path-vulnerability.asciidoc |   67 +
 ...al-linux-ssh-brute-force-detected.asciidoc |  159 ++
 ...e-download-via-a-headless-browser.asciidoc |  108 +
 ...tential-file-transfer-via-certreq.asciidoc |  152 ++
 ...idden-local-user-account-creation.asciidoc |   87 +-
 ...-hidden-process-via-mount-hidepid.asciidoc |  105 +
 ...al-linux-ssh-brute-force-detected.asciidoc |  155 ++
 ...invoke-mimikatz-powershell-script.asciidoc |  152 +-
 ...al-java-jndi-exploitation-attempt.asciidoc |   95 +-
 ...ntial-kerberos-attack-via-bifrost.asciidoc |  107 +-
 ...teral-tool-transfer-via-smb-share.asciidoc |  149 +-
 ...ux-backdoor-user-account-creation.asciidoc |  168 ++
 ...ntial-dumping-via-proc-filesystem.asciidoc |  112 +
 ...x-credential-dumping-via-unshadow.asciidoc |  105 +
 ...otential-linux-hack-tool-launched.asciidoc |  114 +
 ...ocal-account-brute-force-detected.asciidoc |  106 +
 ...ransomware-note-creation-detected.asciidoc |  111 +
 ...otential-linux-ssh-x11-forwarding.asciidoc |  141 ++
 ...-tunneling-and-or-port-forwarding.asciidoc |  196 ++
 ...tential-local-ntlm-relay-via-http.asciidoc |   87 +-
 ...-lsa-authentication-package-abuse.asciidoc |   68 +-
 ...e-creation-via-psscapturesnapshot.asciidoc |   73 +-
 ...emory-dump-via-psscapturesnapshot.asciidoc |   76 +-
 ...al-macos-ssh-brute-force-detected.asciidoc |   83 +-
 ...l-masquerading-as-browser-process.asciidoc |  198 ++
 ...erading-as-business-app-installer.asciidoc |  217 ++
 ...asquerading-as-communication-apps.asciidoc |  134 +
 ...tial-masquerading-as-system32-dll.asciidoc |  157 ++
 ...squerading-as-system32-executable.asciidoc |  120 +
 ...potential-masquerading-as-vlc-dll.asciidoc |   82 +
 ...potential-memory-seeking-activity.asciidoc |   69 +
 ...tential-meterpreter-reverse-shell.asciidoc |  131 +
 ...-microsoft-office-sandbox-evasion.asciidoc |   86 +-
 ...ication-of-accessibility-binaries.asciidoc |  265 +-
 .../potential-network-scan-detected.asciidoc  |   74 +
 ...l-network-scan-executed-from-host.asciidoc |  103 +
 ...potential-network-share-discovery.asciidoc |   76 +
 .../potential-network-sweep-detected.asciidoc |   75 +
 ...andard-port-http-https-connection.asciidoc |  159 ++
 ...-non-standard-port-ssh-connection.asciidoc |   48 +-
 ...fa-bombing-via-push-notifications.asciidoc |  129 +
 ...openssh-backdoor-logging-activity.asciidoc |  169 +-
 ...rdp-connection-by-unusual-process.asciidoc |   77 +
 ...tential-pass-the-hash-pth-attempt.asciidoc |   69 +
 ...ng-of-microsoft-365-user-accounts.asciidoc |  104 +-
 ...rsistence-through-init-d-detected.asciidoc |  189 ++
 ...rough-motd-file-creation-detected.asciidoc |  181 ++
 ...ence-through-run-control-detected.asciidoc |  184 ++
 ...persistence-through-systemd-udevd.asciidoc |  104 +
 ...via-atom-init-script-modification.asciidoc |   83 +-
 ...ential-persistence-via-login-hook.asciidoc |  110 +-
 ...al-persistence-via-periodic-tasks.asciidoc |   87 +-
 ...ce-via-time-provider-modification.asciidoc |  147 +-
 ...rint-processor-registration-abuse.asciidoc |   94 +-
 ...ershell-hacktool-script-by-author.asciidoc |  115 +
 ...hacktool-script-by-function-names.asciidoc |  353 +++
 ...rshell-pass-the-hash-relay-script.asciidoc |  123 +
 ...-bypass-via-localhost-secure-copy.asciidoc |  104 +-
 ...rol-bypass-via-tccdb-modification.asciidoc |  101 +-
 ...on-through-writable-docker-socket.asciidoc |  104 +
 ...on-via-container-misconfiguration.asciidoc |  115 +
 ...ege-escalation-via-cve-2022-38028.asciidoc |   76 +
 ...lege-escalation-via-cve-2023-4911.asciidoc |  114 +
 ...lege-escalation-via-enlightenment.asciidoc |  104 +
 ...alation-via-installerfiletakeover.asciidoc |  206 +-
 ...alation-via-linux-dac-permissions.asciidoc |   99 +
 ...rivilege-escalation-via-overlayfs.asciidoc |  104 +
 ...l-privilege-escalation-via-pkexec.asciidoc |   91 +-
 ...-escalation-via-python-cap-setuid.asciidoc |  109 +
 ...-via-recently-compiled-executable.asciidoc |  105 +
 ...ion-via-sudoers-file-modification.asciidoc |   49 +-
 ...tion-via-uid-int-max-bug-detected.asciidoc |  103 +
 ...ation-via-samaccountname-spoofing.asciidoc |   80 +-
 ...injection-from-malicious-document.asciidoc |   93 +
 ...-process-injection-via-powershell.asciidoc |  201 +-
 ...tocol-tunneling-via-chisel-client.asciidoc |  184 ++
 ...tocol-tunneling-via-chisel-server.asciidoc |  184 ++
 ...-protocol-tunneling-via-earthworm.asciidoc |  181 +-
 ...-pspy-process-monitoring-detected.asciidoc |  103 +
 ...h-count-of-readme-files-by-system.asciidoc |  125 +
 ...somware-note-file-dropped-via-smb.asciidoc |  136 +
 ...ote-code-execution-via-web-server.asciidoc |  201 ++
 ...te-credential-access-via-registry.asciidoc |  174 +-
 ...remote-desktop-shadowing-activity.asciidoc |  108 +-
 ...remote-desktop-tunneling-detected.asciidoc |  174 +-
 ...remote-file-execution-via-msiexec.asciidoc |  107 +
 ...verse-shell-activity-via-terminal.asciidoc |  142 +-
 ...erse-shell-via-background-process.asciidoc |  112 +
 ...potential-reverse-shell-via-child.asciidoc |  119 +
 .../potential-reverse-shell-via-java.asciidoc |  127 +
 ...verse-shell-via-suspicious-binary.asciidoc |  127 +
 ...hell-via-suspicious-child-process.asciidoc |  135 +
 .../potential-reverse-shell-via-udp.asciidoc  |  139 +
 .../potential-reverse-shell.asciidoc          |  117 +
 ...file-deletion-via-sdelete-utility.asciidoc |  132 +-
 ...ow-credentials-added-to-ad-object.asciidoc |  133 +-
 ...e-read-via-command-line-utilities.asciidoc |  113 +-
 .../potential-sharprdp-behavior.asciidoc      |  147 +-
 ...l-via-wildcard-injection-detected.asciidoc |  114 +
 ...ential-ssh-it-ssh-worm-downloaded.asciidoc |  120 +
 ...x-ftp-brute-force-attack-detected.asciidoc |  125 +
 ...x-rdp-brute-force-attack-detected.asciidoc |  123 +
 ...successful-ssh-brute-force-attack.asciidoc |  164 ++
 ...potential-sudo-hijacking-detected.asciidoc |  114 +
 ...ege-escalation-via-cve-2019-14287.asciidoc |  105 +
 ...anipulation-via-process-injection.asciidoc |  114 +
 ...cious-clipboard-activity-detected.asciidoc |   67 +
 ...icious-debugfs-root-device-access.asciidoc |  106 +
 .../potential-suspicious-file-edit.asciidoc   |  112 +
 ...l-syn-based-network-scan-detected.asciidoc |   74 +
 ...s-via-wildcard-injection-detected.asciidoc |  117 +
 ...-upgrade-of-non-interactive-shell.asciidoc |  106 +
 ...l-veeam-credential-access-command.asciidoc |   88 +
 ...e-infection-across-multiple-hosts.asciidoc |   66 +
 ...indows-error-manager-masquerading.asciidoc |  154 +-
 ...ows-session-hijacking-via-ccmexec.asciidoc |   63 +
 ...fa-bombing-via-push-notifications.asciidoc |  123 +
 ...rocess-started-via-tmux-or-screen.asciidoc |   65 +
 ...owershell-invoke-ninjacopy-script.asciidoc |  150 ++
 .../powershell-kerberos-ticket-dump.asciidoc  |  174 ++
 ...owershell-kerberos-ticket-request.asciidoc |  161 +-
 .../powershell-keylogging-script.asciidoc     |  197 +-
 ...ershell-mailbox-collection-script.asciidoc |  174 ++
 .../powershell-minidump-script.asciidoc       |  158 +-
 .../powershell-psreflect-script.asciidoc      |  210 +-
 ...ell-script-block-logging-disabled.asciidoc |  137 +-
 ...-archive-compression-capabilities.asciidoc |  114 +
 ...cript-with-discovery-capabilities.asciidoc |  250 ++
 ...ncryption-decryption-capabilities.asciidoc |  129 +
 ...cript-with-log-clear-capabilities.asciidoc |  113 +
 ...ord-policy-discovery-capabilities.asciidoc |  134 +
 ...-execution-capabilities-via-winrm.asciidoc |  117 +
 ...-token-impersonation-capabilities.asciidoc |  175 +-
 ...am-credential-access-capabilities.asciidoc |  110 +
 ...webcam-video-capture-capabilities.asciidoc |  111 +
 ...wershell-share-enumeration-script.asciidoc |  150 +-
 ...ery-related-windows-api-functions.asciidoc |  227 +-
 ...us-payload-encoded-and-compressed.asciidoc |  202 +-
 ...t-with-audio-capture-capabilities.asciidoc |  181 +-
 ...-clipboard-retrieval-capabilities.asciidoc |  171 ++
 ...ript-with-screenshot-capabilities.asciidoc |  165 +-
 ...cap-chown-cap-fowner-capabilities.asciidoc |  111 +
 ...ia-cap-setuid-setgid-capabilities.asciidoc |  111 +
 ...escalation-via-gdb-cap-sys-ptrace.asciidoc |  110 +
 ...tion-via-named-pipe-impersonation.asciidoc |  156 +-
 ...ia-rogue-named-pipe-impersonation.asciidoc |   70 +-
 ...ia-root-crontab-file-modification.asciidoc |   87 +-
 ...n-via-windir-environment-variable.asciidoc |   80 +-
 .../privileged-account-brute-force.asciidoc   |  137 +-
 ...n-via-parent-process-pid-spoofing.asciidoc |  117 +-
 ...s-activity-via-compiled-html-file.asciidoc |  211 +-
 .../process-capability-enumeration.asciidoc   |  101 +
 ...s-created-with-a-duplicated-token.asciidoc |   95 +
 ...ss-created-with-an-elevated-token.asciidoc |  129 +-
 ...cess-creation-via-secondary-logon.asciidoc |   87 +-
 ...ss-discovery-using-built-in-tools.asciidoc |   72 +
 ...scovery-via-built-in-applications.asciidoc |   74 +
 ...ecution-from-an-unusual-directory.asciidoc |  321 ++-
 ...ion-by-the-microsoft-build-engine.asciidoc |   76 +-
 ...njection-detected-elastic-endgame.asciidoc |   79 +-
 ...jection-prevented-elastic-endgame.asciidoc |   79 +-
 ...-started-from-process-id-pid-file.asciidoc |  106 +-
 ...-termination-followed-by-deletion.asciidoc |  203 +-
 .../processes-with-trailing-spaces.asciidoc   |   71 +
 ...gram-files-directory-masquerading.asciidoc |  107 +-
 ...pt-for-credentials-with-osascript.asciidoc |  109 +-
 .../proxychains-activity.asciidoc             |  146 ++
 .../psexec-network-connection.asciidoc        |  193 +-
 ...script-execution-via-command-line.asciidoc |   85 +
 ...-by-unsigned-or-untrusted-process.asciidoc |  110 +
 ...ery-registry-using-built-in-tools.asciidoc |   77 +
 ...nsomware-detected-elastic-endgame.asciidoc |   58 +-
 ...somware-prevented-elastic-endgame.asciidoc |   58 +-
 .../rule-details/rare-aws-error-code.asciidoc |  130 +-
 ...re-smb-connection-to-the-internet.asciidoc |  100 +
 .../rule-details/rare-user-logon.asciidoc     |   91 +-
 .../rdp-enabled-via-registry.asciidoc         |  164 +-
 ...esktop-protocol-from-the-internet.asciidoc |  166 +-
 ...istry-persistence-via-appcert-dll.asciidoc |  105 +-
 ...istry-persistence-via-appinit-dll.asciidoc |  187 +-
 ...mputer-account-dnshostname-update.asciidoc |   92 +-
 ...bled-in-windows-firewall-by-netsh.asciidoc |  140 +-
 .../remote-execution-via-file-shares.asciidoc |  154 +-
 ...emote-file-copy-to-a-hidden-share.asciidoc |   96 +-
 .../remote-file-copy-via-teamviewer.asciidoc  |  186 +-
 ...oad-via-desktopimgdownldr-utility.asciidoc |  192 +-
 ...remote-file-download-via-mpcmdrun.asciidoc |  182 +-
 ...mote-file-download-via-powershell.asciidoc |  192 +-
 ...e-download-via-script-interpreter.asciidoc |  166 +-
 ...e-scheduled-task-creation-via-rpc.asciidoc |  118 +
 .../remote-scheduled-task-creation.asciidoc   |  164 +-
 ...n-enabled-via-systemsetup-command.asciidoc |  108 +-
 .../remote-system-discovery-commands.asciidoc |  167 +-
 .../remote-windows-service-installed.asciidoc |   99 +-
 ...mote-xsl-script-execution-via-com.asciidoc |   84 +
 ...remotely-started-services-via-rpc.asciidoc |  306 +--
 ...enamed-autoit-scripts-interpreter.asciidoc |  162 +-
 ...-executed-with-short-program-name.asciidoc |  132 +
 ...connection-via-gdb-cap-sys-ptrace.asciidoc |  132 +
 ...file-downloaded-from-the-internet.asciidoc |  131 +-
 ...r-query-log-configuration-deleted.asciidoc |  123 +
 ...-procedure-call-from-the-internet.asciidoc |  154 +-
 ...te-procedure-call-to-the-internet.asciidoc |  154 +-
 ...-task-created-by-a-windows-script.asciidoc |  130 +-
 ...d-task-execution-at-scale-via-gpo.asciidoc |  183 +-
 ...cheduled-tasks-at-command-enabled.asciidoc |  126 +-
 ...ver-spawning-suspicious-processes.asciidoc |   87 +
 ...le-modified-by-unexpected-process.asciidoc |  129 +-
 ...or-saved-credentials-via-vaultcmd.asciidoc |   93 +-
 ...ity-software-discovery-using-wmic.asciidoc |  157 +-
 ...urity-software-discovery-via-grep.asciidoc |  203 +-
 ...e-enabled-by-a-suspicious-process.asciidoc |   94 +-
 .../rule-details/segfault-detected.asciidoc   |   91 +
 ...es-compression-inside-a-container.asciidoc |  107 +
 .../sensitive-files-compression.asciidoc      |  158 +-
 ...s-searched-for-inside-a-container.asciidoc |   77 +
 ...ationprivilege-assigned-to-a-user.asciidoc |  147 +-
 .../service-command-lateral-movement.asciidoc |  100 +-
 ...ol-spawned-via-script-interpreter.asciidoc |  213 +-
 ...via-local-kerberos-authentication.asciidoc |   75 +-
 ...isabled-via-registry-modification.asciidoc |   79 +
 ...vice-path-modification-via-sc-exe.asciidoc |   87 +
 .../service-path-modification.asciidoc        |   97 +
 ...tcap-setuid-setgid-capability-set.asciidoc |  181 ++
 .../setuid-setgid-bit-set-via-chmod.asciidoc  |  131 +-
 ...ged-by-previously-unknown-process.asciidoc |  185 ++
 .../sharepoint-malware-file-upload.asciidoc   |   60 +-
 .../shell-configuration-modification.asciidoc |  121 +
 ...ell-execution-via-apple-scripting.asciidoc |  101 +-
 ...ten-or-modified-on-startup-folder.asciidoc |   78 +
 ...oxy-execution-via-ms-work-folders.asciidoc |  131 +-
 .../sip-provider-modification.asciidoc        |   86 +-
 ...-sharing-activity-to-the-internet.asciidoc |  156 +-
 .../rule-details/smtp-on-port-26-tcp.asciidoc |   86 +-
 ...reupdate-preferences-modification.asciidoc |   99 +-
 ...s-disabling-services-via-registry.asciidoc |  150 +-
 .../spike-in-aws-error-messages.asciidoc      |  133 +-
 ...to-an-external-device-via-airdrop.asciidoc |   90 +
 ...-bytes-sent-to-an-external-device.asciidoc |   90 +
 .../spike-in-failed-logon-events.asciidoc     |   88 +-
 .../spike-in-firewall-denies.asciidoc         |   39 +-
 .../spike-in-logon-events.asciidoc            |   43 +-
 ...e-in-network-traffic-to-a-country.asciidoc |   80 +-
 .../spike-in-network-traffic.asciidoc         |   42 +-
 ...connections-made-from-a-source-ip.asciidoc |   92 +
 ...nections-made-to-a-destination-ip.asciidoc |   92 +
 ...er-of-processes-in-an-rdp-session.asciidoc |   92 +
 .../spike-in-remote-file-transfers.asciidoc   |   91 +
 ...ful-logon-events-from-a-source-ip.asciidoc |  107 +
 ...authorized-keys-file-modification.asciidoc |  126 +-
 ...-file-modified-inside-a-container.asciidoc |   85 +
 ...lished-inside-a-running-container.asciidoc |   83 +
 ...-launched-from-inside-a-container.asciidoc |   77 +
 ...-persistence-via-unsigned-process.asciidoc |  196 +-
 ...ript-added-to-group-policy-object.asciidoc |  169 +-
 ...-or-run-key-registry-modification.asciidoc |  430 ++--
 ...rsistence-by-a-suspicious-process.asciidoc |  213 +-
 ...ing-activity-with-high-confidence.asciidoc |   96 +
 ...el-detected-c2-beaconing-activity.asciidoc |   97 +
 ...n-to-okta-account-after-mfa-reset.asciidoc |  125 +
 ...r-application-script-modification.asciidoc |  118 +-
 ...sudo-command-enumeration-detected.asciidoc |   99 +
 ...eap-based-buffer-overflow-attempt.asciidoc |   52 +-
 .../sudoers-file-modification.asciidoc        |   82 +-
 .../suid-sguid-enumeration-detected.asciidoc  |  119 +
 ...urst-command-and-control-activity.asciidoc |  210 +-
 ...picious-access-to-ldap-attributes.asciidoc |   81 +
 ...us-activity-reported-by-okta-user.asciidoc |   85 +-
 ...us-antimalware-scan-interface-dll.asciidoc |  142 ++
 ...ous-apt-package-manager-execution.asciidoc |  129 +
 ...ackage-manager-network-connection.asciidoc |  118 +
 ...ous-automator-workflows-execution.asciidoc |   84 +-
 .../suspicious-browser-child-process.asciidoc |  140 +-
 ...icious-calendar-file-modification.asciidoc |  108 +-
 .../suspicious-certutil-commands.asciidoc     |  183 +-
 ...obe-acrobat-reader-update-service.asciidoc |  116 +-
 .../suspicious-cmd-execution-via-wmi.asciidoc |   99 +-
 ...s-communication-app-child-process.asciidoc |  299 +++
 ...racted-or-decompressed-via-funzip.asciidoc |  120 +
 ...-crontab-creation-or-modification.asciidoc |   93 +-
 ...ta-encryption-via-openssl-utility.asciidoc |  105 +
 ...rsistence-or-privilege-escalation.asciidoc |  210 +-
 ...s-dynamic-linker-discovery-via-od.asciidoc |  108 +
 .../suspicious-emond-child-process.asciidoc   |  112 +-
 ...-endpoint-security-parent-process.asciidoc |  140 +-
 ...s-execution-from-a-mounted-device.asciidoc |   97 +-
 ...picious-execution-from-inet-cache.asciidoc |   82 +
 ...tion-via-microsoft-office-add-ins.asciidoc |  123 +
 .../suspicious-execution-via-msiexec.asciidoc |   98 +
 ...ious-execution-via-scheduled-task.asciidoc |  191 +-
 ...n-via-windows-subsystem-for-linux.asciidoc |   97 +
 ...suspicious-explorer-child-process.asciidoc |  158 +-
 ...us-file-changes-activity-detected.asciidoc |  108 +
 ...e-creation-in-etc-for-persistence.asciidoc |  233 +-
 ...picious-file-creation-via-kworker.asciidoc |  192 ++
 ...file-downloaded-from-google-drive.asciidoc |   75 +
 .../suspicious-file-renamed-via-smb.asciidoc  |  138 +
 ...s-hidden-child-process-of-launchd.asciidoc |   94 +-
 .../suspicious-html-file-creation.asciidoc    |  107 +-
 ...-load-taskschd-dll-from-ms-office.asciidoc |  182 ++
 ...icious-imagepath-service-creation.asciidoc |   78 +-
 ...process-communication-via-outlook.asciidoc |   91 +
 ...l-spawned-from-inside-a-container.asciidoc |   72 +
 .../suspicious-java-child-process.asciidoc    |  150 +-
 ...-jetbrains-teamcity-child-process.asciidoc |   98 +
 .../suspicious-kworker-uid-elevation.asciidoc |  113 +
 ...ious-lsass-access-via-malseclogon.asciidoc |   76 +-
 .../suspicious-lsass-process-access.asciidoc  |  103 +
 ...ous-macos-ms-office-child-process.asciidoc |  192 +-
 ...ious-managed-code-hosting-process.asciidoc |   98 +-
 .../suspicious-memory-grep-activity.asciidoc  |   65 +
 ...ft-365-mail-access-by-clientappid.asciidoc |   71 +
 ...soft-diagnostics-wizard-execution.asciidoc |  125 +-
 ...ous-mining-process-creation-event.asciidoc |  103 +
 .../suspicious-modprobe-file-event.asciidoc   |   92 +
 ...suspicious-module-loaded-by-lsass.asciidoc |  147 ++
 ...uspicious-ms-office-child-process.asciidoc |  361 +--
 ...spicious-ms-outlook-child-process.asciidoc |  268 +-
 .../suspicious-net-code-compilation.asciidoc  |   97 +
 ...ous-net-reflection-via-powershell.asciidoc |  200 ++
 ...-by-previously-unknown-executable.asciidoc |  241 ++
 ...etwork-connection-via-sudo-binary.asciidoc |  112 +
 ...us-network-connection-via-systemd.asciidoc |  122 +
 ...-tool-launched-inside-a-container.asciidoc |   82 +
 ...spicious-passwd-file-event-action.asciidoc |  130 +
 ...spicious-pdf-reader-child-process.asciidoc |  240 +-
 ...able-encoded-in-powershell-script.asciidoc |  186 +-
 ...cious-powershell-engine-imageload.asciidoc |  296 +--
 .../suspicious-powershell-script.asciidoc     |   64 +-
 ...cious-print-spooler-file-deletion.asciidoc |   75 +-
 ...print-spooler-point-and-print-dll.asciidoc |   77 +-
 ...us-print-spooler-spl-file-created.asciidoc |  196 +-
 ...-service-executable-file-creation.asciidoc |  100 +-
 .../suspicious-proc-maps-discovery.asciidoc   |  102 +
 ...oc-pseudo-file-system-enumeration.asciidoc |   94 +
 ...ess-access-via-direct-system-call.asciidoc |  204 +-
 ...icious-process-creation-calltrace.asciidoc |  158 +-
 ...ion-via-renamed-psexec-executable.asciidoc |  155 +-
 ...rocess-spawned-from-motd-detected.asciidoc |  201 ++
 ...picious-rdp-activex-client-loaded.asciidoc |  134 +-
 ...stry-access-via-sebackupprivilege.asciidoc |  171 +-
 ...suspicious-renaming-of-esxi-files.asciidoc |  104 +
 ...-renaming-of-esxi-index-html-file.asciidoc |  103 +
 ...creenconnect-client-child-process.asciidoc |   86 +
 ...uspicious-script-object-execution.asciidoc |  159 +-
 ...rvice-was-installed-in-the-system.asciidoc |  117 +-
 ...spicious-solarwinds-child-process.asciidoc |  127 +-
 ...startup-shell-folder-modification.asciidoc |  183 +-
 .../suspicious-symbolic-link-created.asciidoc |  129 +
 .../suspicious-sysctl-file-event.asciidoc     |   92 +
 ...-by-previously-unknown-executable.asciidoc |  110 +
 ...cious-termination-of-esxi-process.asciidoc |  101 +
 ...leshooting-pack-cabinet-execution.asciidoc |   79 +
 ...-utility-launched-via-proxychains.asciidoc |  187 ++
 ...web-browser-sensitive-file-access.asciidoc |  115 +
 ...suspicious-werfault-child-process.asciidoc |  141 +-
 .../suspicious-which-enumeration.asciidoc     |   68 +
 ...process-cluster-spawned-by-a-host.asciidoc |  124 +
 ...uster-spawned-by-a-parent-process.asciidoc |  126 +
 ...process-cluster-spawned-by-a-user.asciidoc |  126 +
 ...us-wmi-event-subscription-created.asciidoc |   68 +
 ...ous-wmi-image-load-from-ms-office.asciidoc |  111 +-
 ...picious-wmic-xsl-script-execution.asciidoc |  109 +-
 .../suspicious-zoom-child-process.asciidoc    |  175 +-
 .../svchost-spawning-cmd.asciidoc             |  224 +-
 ...bolic-link-to-shadow-copy-created.asciidoc |  164 +-
 ...-or-moved-to-suspicious-directory.asciidoc |  130 +
 .../system-hosts-file-access.asciidoc         |   67 +
 ...scovery-via-windows-command-shell.asciidoc |  105 +-
 .../system-log-file-deletion.asciidoc         |  157 +-
 ...tem-network-connections-discovery.asciidoc |   67 +
 ...system-owner-user-discovery-linux.asciidoc |   70 +
 ...hrough-built-in-windows-utilities.asciidoc |   72 +
 .../system-shells-via-services.asciidoc       |  214 +-
 .../system-time-discovery.asciidoc            |   73 +
 ...systemkey-access-via-command-line.asciidoc |   96 +-
 .../tainted-kernel-module-load.asciidoc       |  105 +
 ...ed-out-of-tree-kernel-module-load.asciidoc |  105 +
 ...ing-of-shell-command-line-history.asciidoc |   94 +
 ...-via-mounted-apfs-snapshot-access.asciidoc |   85 +-
 ...mporarily-scheduled-task-creation.asciidoc |   83 +-
 ...es-deleted-via-unexpected-process.asciidoc |  169 +-
 ...threat-intel-hash-indicator-match.asciidoc |  137 +
 ...-intel-ip-address-indicator-match.asciidoc |  139 +
 .../threat-intel-url-indicator-match.asciidoc |  142 ++
 ...-windows-registry-indicator-match.asciidoc |  132 +
 .../timestomping-using-touch-command.asciidoc |   96 +-
 .../trap-signals-execution.asciidoc           |   71 +
 ...nternet-explorer-add-on-installer.asciidoc |  137 +-
 ...eged-ifileoperation-com-interface.asciidoc |  115 +-
 ...ia-windows-directory-masquerading.asciidoc |  188 +-
 ...ademanager-elevated-com-interface.asciidoc |  133 +-
 ...diskcleanup-scheduled-task-hijack.asciidoc |  133 +-
 ...icmluautil-elevated-com-interface.asciidoc |  120 +-
 ...a-windows-firewall-snap-in-hijack.asciidoc |  198 +-
 ...rom-previously-unknown-executable.asciidoc |  121 +
 ...zed-access-to-an-okta-application.asciidoc |   66 +-
 ...ommon-registry-persistence-change.asciidoc |  310 +--
 ...ocess-of-macos-screensaver-engine.asciidoc |  100 +-
 .../unix-socket-connection.asciidoc           |   71 +
 ...-of-binary-with-rwx-memory-region.asciidoc |   89 +
 ...igned-bits-service-client-process.asciidoc |   73 +
 ...d-dll-loaded-by-a-trusted-process.asciidoc |  112 +
 .../unsigned-dll-loaded-by-svchost.asciidoc   |  179 ++
 ...-loading-from-a-suspicious-folder.asciidoc |  167 ++
 .../untrusted-driver-loaded.asciidoc          |  144 ++
 .../unusual-aws-command-for-a-user.asciidoc   |  128 +-
 ...ess-from-a-system-virtual-process.asciidoc |   93 +-
 .../unusual-child-process-of-dns-exe.asciidoc |  136 +
 ...usual-child-processes-of-rundll32.asciidoc |  163 +-
 .../unusual-city-for-an-aws-command.asciidoc  |  128 +-
 ...nusual-country-for-an-aws-command.asciidoc |  134 +-
 ...nusual-discovery-activity-by-user.asciidoc |   61 +
 ...with-unusual-process-command-line.asciidoc |   60 +
 ...t-with-unusual-process-executable.asciidoc |   55 +
 .../unusual-dns-activity.asciidoc             |   55 +-
 ...tion-by-a-system-critical-process.asciidoc |  178 +-
 ...via-microsoft-common-console-file.asciidoc |  124 +
 ...le-creation-alternate-data-stream.asciidoc |  249 +-
 ...sual-file-modification-by-dns-exe.asciidoc |  100 +
 ...idence-misconduct-blocks-detected.asciidoc |   68 +
 .../unusual-hour-for-a-user-to-logon.asciidoc |   77 +-
 .../unusual-linux-network-activity.asciidoc   |   67 +-
 ...x-network-configuration-discovery.asciidoc |   49 +
 ...inux-network-connection-discovery.asciidoc |   45 +-
 ...usual-linux-network-port-activity.asciidoc |   54 +-
 ...cess-calling-the-metadata-service.asciidoc |   56 +-
 ...-linux-process-discovery-activity.asciidoc |   45 +-
 ...em-information-discovery-activity.asciidoc |   45 +-
 ...user-calling-the-metadata-service.asciidoc |   56 +-
 ...ual-linux-user-discovery-activity.asciidoc |   49 +
 .../unusual-linux-username.asciidoc           |   78 +-
 .../unusual-login-activity.asciidoc           |   55 +-
 ...vity-from-a-windows-system-binary.asciidoc |  247 +-
 ...al-network-connection-via-dllhost.asciidoc |   85 +-
 ...l-network-connection-via-rundll32.asciidoc |  233 +-
 ...l-network-destination-domain-name.asciidoc |   45 +-
 ...unusual-parent-child-relationship.asciidoc |  388 +--
 ...nusual-parent-process-for-cmd-exe.asciidoc |  104 +
 ...persistence-via-services-registry.asciidoc |  126 +-
 ...usual-print-spooler-child-process.asciidoc |  129 +-
 ...al-process-execution-on-wbem-path.asciidoc |   77 +
 ...cution-path-alternate-data-stream.asciidoc |   92 +-
 .../unusual-process-extension.asciidoc        |   92 +
 .../unusual-process-for-a-linux-host.asciidoc |  118 +-
 ...nusual-process-for-a-windows-host.asciidoc |  176 +-
 ...rocess-for-mssql-service-accounts.asciidoc |  111 +
 ...nusual-process-network-connection.asciidoc |  178 +-
 ...unusual-process-spawned-by-a-host.asciidoc |  126 +
 ...ocess-spawned-by-a-parent-process.asciidoc |  126 +
 ...unusual-process-spawned-by-a-user.asciidoc |  126 +
 ...riting-data-to-an-external-device.asciidoc |   90 +
 .../unusual-remote-file-directory.asciidoc    |   91 +
 .../unusual-remote-file-extension.asciidoc    |   91 +
 .../unusual-remote-file-size.asciidoc         |   91 +
 ...t-child-process-childless-service.asciidoc |  166 +-
 ...ource-ip-for-a-user-to-logon-from.asciidoc |   43 +-
 .../unusual-sudo-activity.asciidoc            |   47 +-
 ...al-time-or-day-for-an-rdp-session.asciidoc |   92 +
 ...user-privilege-enumeration-via-id.asciidoc |   99 +
 .../rule-details/unusual-web-request.asciidoc |   55 +-
 .../unusual-web-user-agent.asciidoc           |   55 +-
 .../unusual-windows-network-activity.asciidoc |   72 +-
 .../unusual-windows-path-activity.asciidoc    |   77 +-
 ...cess-calling-the-metadata-service.asciidoc |   56 +-
 .../unusual-windows-remote-user.asciidoc      |   72 +-
 .../unusual-windows-service.asciidoc          |   61 +-
 ...user-calling-the-metadata-service.asciidoc |   56 +-
 ...user-privilege-elevation-activity.asciidoc |   57 +-
 .../unusual-windows-username.asciidoc         |   86 +-
 .../user-account-creation.asciidoc            |  175 +-
 ...-account-exposed-to-kerberoasting.asciidoc |  153 +-
 ...ed-as-owner-for-azure-application.asciidoc |   71 +-
 ...owner-for-azure-service-principal.asciidoc |   73 +-
 .../user-added-to-privileged-group.asciidoc   |  133 +-
 ...library-loaded-by-unusual-process.asciidoc |   81 +
 ...l-machine-fingerprinting-via-grep.asciidoc |   80 +-
 .../virtual-machine-fingerprinting.asciidoc   |  129 +-
 ...rivate-network-connection-attempt.asciidoc |   92 +-
 ...twork-computing-from-the-internet.asciidoc |  158 +-
 ...network-computing-to-the-internet.asciidoc |  156 +-
 ...y-deleted-or-resized-via-vssadmin.asciidoc |  203 +-
 ...adow-copy-deletion-via-powershell.asciidoc |  170 +-
 ...ume-shadow-copy-deletion-via-wmic.asciidoc |  188 +-
 ...us-activity-post-request-declined.asciidoc |   62 +-
 ...icious-activity-sqlmap-user-agent.asciidoc |   59 +-
 ...ious-activity-unauthorized-method.asciidoc |   62 +-
 ...ess-child-of-common-web-processes.asciidoc |  188 +-
 .../webproxy-settings-modification.asciidoc   |  102 +-
 .../webserver-access-logs-deleted.asciidoc    |   93 +-
 ...fault-reflectdebugger-persistence.asciidoc |   75 +
 .../whoami-process-activity.asciidoc          |  201 +-
 ...indows-account-or-group-discovery.asciidoc |  110 +
 ...erability-cve-2020-0601-curveball.asciidoc |   65 +-
 ...isabled-via-registry-modification.asciidoc |  219 +-
 ...r-exclusions-added-via-powershell.asciidoc |  173 +-
 .../windows-event-logs-cleared.asciidoc       |  107 +-
 ...-firewall-disabled-via-powershell.asciidoc |  146 +-
 ...taller-with-suspicious-properties.asciidoc |   79 +
 .../windows-network-enumeration.asciidoc      |  202 +-
 ...gistry-file-creation-in-smb-share.asciidoc |  134 +-
 ...ndows-script-executing-powershell.asciidoc |  198 +-
 ...rpreter-executing-process-via-wmi.asciidoc |  172 +-
 ...e-installed-via-an-unusual-client.asciidoc |   79 +-
 ...-for-linux-distribution-installed.asciidoc |  126 +
 ...or-linux-enabled-via-dism-utility.asciidoc |  120 +
 ...dows-system-information-discovery.asciidoc |   80 +
 ...tem-network-connections-discovery.asciidoc |   77 +
 .../windows-user-account-creation.asciidoc    |   69 +
 ...ntial-dumping-using-netsh-command.asciidoc |  102 +-
 .../wmi-incoming-lateral-movement.asciidoc    |  143 +-
 .../wmi-wbemtest-utility-execution.asciidoc   |   65 +
 .../rule-details/wmic-remote-command.asciidoc |   76 +
 .../wpad-service-exploit.asciidoc             |   74 +
 ...access-on-active-directory-object.asciidoc |   92 +
 .../zoom-meeting-with-no-passcode.asciidoc    |   66 +-
 docs/index.asciidoc                           |    2 +
 1170 files changed, 89354 insertions(+), 48620 deletions(-)
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-access-to-keychain-credentials-directories.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-adversary-behavior-detected-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-alternate-data-stream-creation-execution-at-volume-root-directory.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-apple-scripting-execution-with-administrator-privileges.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-authorization-plugin-modification.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-aws-ec2-admin-credential-fetch-via-assumed-role.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-component-object-model-hijacking.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-connection-to-commonly-abused-web-services.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-container-workload-protection.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-dumping-detected-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-dumping-prevented-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-manipulation-detected-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-manipulation-prevented-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ec2-ami-shared-with-another-account.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-endpoint-security.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-enumeration-of-users-or-groups-via-built-in-commands.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-exploit-detected-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-exploit-prevented-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-external-alerts.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-finder-sync-plugin-registered-and-enabled.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-keychain-password-retrieval-via-command-line.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-macos-installer-package-spawns-network-event.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-malware-detected-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-malware-prevented-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-modification-of-environment-variable-via-unsigned-or-untrusted-parent.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-permission-theft-detected-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-permission-theft-prevented-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-persistence-via-docker-shortcut-modification.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-persistence-via-folder-action-script.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-admin-group-account-addition.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-file-download-via-a-headless-browser.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-persistence-via-login-hook.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-powershell-hacktool-script-by-author.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-ransomware-behavior-high-count-of-readme-files-by-system.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-ransomware-note-file-dropped-via-smb.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-widespread-malware-infection-across-multiple-hosts.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-process-injection-detected-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-process-injection-prevented-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-prompt-for-credentials-with-osascript.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-quarantine-attrib-removed-by-unsigned-or-untrusted-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ransomware-detected-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ransomware-prevented-elastic-endgame.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-route53-resolver-query-log-configuration-deleted.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-shell-execution-via-apple-scripting.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-browser-child-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-file-renamed-via-smb.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-macos-ms-office-child-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-web-browser-sensitive-file-access.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-systemkey-access-via-command-line.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-unusual-execution-via-microsoft-common-console-file.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-webproxy-settings-modification.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rules-8-14-1-appendix.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rules-8-14-1-summary.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/accessing-outlook-data-files.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/account-or-group-discovery-via-built-in-tools.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/alternate-data-stream-creation-execution-at-volume-root-directory.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/archive-file-with-unusual-extension.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/at-exe-command-lateral-movement.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/attempt-to-clear-kernel-ring-buffer.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/attempt-to-disable-iptables-or-firewall.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/attempt-to-install-kali-linux-via-wsl.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/attempted-private-key-access.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/aws-bedrock-detected-multiple-attempts-to-use-denied-models-by-a-single-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/aws-bedrock-guardrails-detected-multiple-policy-violations-within-a-single-blocked-request.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/aws-bedrock-guardrails-detected-multiple-violations-by-a-single-user-over-a-session.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/aws-credentials-searched-for-inside-a-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/aws-ec2-admin-credential-fetch-via-assumed-role.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/aws-iam-login-profile-added-to-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/aws-s3-bucket-enumeration-or-brute-force.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/binary-content-copy-via-cmd-exe.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/bitsadmin-activity.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/browser-extension-install.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/cap-sys-admin-assigned-to-binary.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/code-signing-policy-modification-through-built-in-tools.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/code-signing-policy-modification-through-registry.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/compression-dll-loaded-by-unusual-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/container-management-utility-run-inside-a-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/container-workload-protection.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/creation-of-a-dns-named-record.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/creation-of-kernel-module.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/creation-of-settingcontent-ms-files.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/cron-job-created-or-changed-by-previously-unknown-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/delayed-execution-via-ping.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/discovery-of-domain-groups.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/discovery-of-internet-capabilities-via-built-in-tools.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/downloaded-shortcut-files.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/downloaded-url-files.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/ec2-ami-shared-with-another-account.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/enumerating-domain-trusts-via-dsquery-exe.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/enumerating-domain-trusts-via-nltest-exe.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/enumeration-of-kernel-modules-via-proc.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/esxi-discovery-via-find.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/esxi-discovery-via-grep.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/esxi-timestomping-using-touch-command.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/exchange-mailbox-export-via-powershell.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/executable-file-with-unusual-extension.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/executable-masquerading-as-kernel-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/execution-from-a-removable-media-with-network-connection.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/execution-of-an-unsigned-service.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/execution-via-electron-child-process-node-js-module.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/execution-via-microsoft-dotnet-clickonce-host.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/execution-via-ms-visualstudio-pre-post-build-events.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/execution-via-mssql-xp-cmdshell-stored-procedure.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/execution-via-windows-subsystem-for-linux.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/expired-or-revoked-driver-loaded.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/external-user-added-to-google-workspace-group.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/file-and-directory-permissions-modification.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/file-compressed-or-archived-into-common-format.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/file-creation-execution-and-self-deletion-in-suspicious-directory.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/file-creation-time-changed.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/file-made-executable-via-chmod-inside-a-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/file-or-directory-deletion-command.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/file-staged-in-root-folder-of-recycle-bin.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/file-system-debugger-launched-inside-a-privileged-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/file-with-suspicious-extension-downloaded.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-occurrence-github-event-for-a-personal-access-token-pat.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-occurrence-of-github-repo-interaction-from-a-new-ip.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-occurrence-of-github-user-interaction-with-private-repo.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-occurrence-of-ip-address-for-github-personal-access-token-pat.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-occurrence-of-ip-address-for-github-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-occurrence-of-okta-user-session-started-via-proxy.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-occurrence-of-personal-access-token-pat-use-for-a-github-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-occurrence-of-private-repo-event-from-specific-github-personal-access-token-pat.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-occurrence-of-user-agent-for-a-github-personal-access-token-pat.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-occurrence-of-user-agent-for-a-github-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-time-seen-aws-secret-value-accessed-in-secrets-manager.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-time-seen-commonly-abused-remote-access-tool-execution.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-time-seen-driver-loaded.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-time-seen-google-workspace-oauth-login-from-third-party-application.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-time-seen-newcredentials-logon-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/first-time-seen-removable-device.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/firsttime-seen-account-performing-dcsync.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/forwarded-google-workspace-security-alert.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/github-app-deleted.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/github-owner-role-granted-to-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/github-pat-access-revoked.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/github-protected-branch-settings-changed.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/github-repo-created.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/github-repository-deleted.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/github-ueba-multiple-alerts-from-a-github-account.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/github-user-blocked-from-organization.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/google-workspace-drive-encryption-key-s-accessed-from-anonymous-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/google-workspace-object-copied-from-external-drive-and-access-granted-to-custom-application.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/google-workspace-suspended-user-account-renewed.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/group-policy-discovery-via-microsoft-gpresult-utility.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/hidden-files-and-directories-via-hidden-flag.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/high-mean-of-process-arguments-in-an-rdp-session.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/high-mean-of-rdp-session-duration.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/high-number-of-cloned-github-repos-from-pat.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/high-variance-in-rdp-session-duration.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/host-files-system-changes-via-windows-subsystem-for-linux.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/image-loaded-with-invalid-signature.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/indirect-command-execution-via-forfiles-pcalua.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/ingress-transfer-via-windows-bits.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/installutil-activity.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/interactive-exec-command-launched-against-a-running-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/interactive-logon-by-an-unusual-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/kernel-driver-load-by-non-root-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/kernel-driver-load.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/kernel-load-or-unload-via-kexec-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/kirbi-file-creation.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/linux-group-creation.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/linux-init-pid-1-secret-dump-via-gdb.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/linux-process-hooking-via-gdb.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/linux-restricted-shell-breakout-via-linux-binary-s.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/linux-system-information-discovery.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/linux-user-account-creation.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/linux-user-added-to-privileged-group.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/lsass-process-access-via-windows-api.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-dns-request-predicted-to-be-a-dga-domain.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-dns-request-with-a-high-dga-probability-score.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-suspicious-windows-event-predicted-to-be-malicious-activity.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-suspicious-windows-event-with-a-high-malicious-probability-score.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/machine-learning-detected-dga-activity-using-a-known-sunburst-dns-domain.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/member-removed-from-github-organization.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/memory-dump-file-with-unusual-extension.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/mfa-deactivation-with-no-re-activation-for-okta-user-account.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/microsoft-365-impossible-travel-activity.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/microsoft-365-mass-download-by-a-single-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/microsoft-exchange-transport-agent-install-script.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/modification-of-dynamic-linker-preload-shared-object-inside-a-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/modification-of-environment-variable-via-unsigned-or-untrusted-parent.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/mofcomp-activity.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/mount-launched-inside-a-privileged-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/multiple-alerts-involving-a-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/multiple-okta-client-addresses-for-a-single-user-session.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/multiple-okta-sessions-detected-for-a-single-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/multiple-okta-user-auth-events-with-same-device-token-hash-behind-a-proxy.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/my-first-rule.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/netcat-listener-established-inside-a-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/netcat-listener-established-via-rlwrap.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/netsh-helper-dll.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/network-activity-detected-via-cat.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/network-activity-detected-via-kworker.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/network-connection-from-binary-with-rwx-memory-region.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/network-connection-via-recently-compiled-executable.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/network-level-authentication-nla-disabled.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/network-traffic-capture-via-cap-net-raw.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/new-github-app-installed.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/new-github-owner-added.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/new-okta-authentication-behavior-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/new-okta-identity-provider-idp-added-by-admin.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/new-systemd-service-created-by-previously-unknown-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/new-systemd-timer-created.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/new-user-added-to-github-organization.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/office-test-registry-persistence.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/okta-fastpass-phishing-detection.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/okta-sign-in-events-via-third-party-idp.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/okta-threatinsight-threat-suspected-promotion.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/okta-user-sessions-started-from-different-geolocations.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-abuse-of-resources-by-high-token-count-and-large-response-sizes.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-adidns-poisoning-via-wildcard-record-creation.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-antimalware-scan-interface-bypass-via-powershell.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-buffer-overflow-attack-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-chroot-container-escape-via-mount.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-code-execution-via-postgresql.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-container-escape-via-modified-notify-on-release-file.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-container-escape-via-modified-release-agent-file.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-memory-dump-file-creation.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-cross-site-scripting-xss.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-curl-cve-2023-38545-exploitation.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-destination-port.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-ip-address.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-iso-code.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-region.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-defense-evasion-via-cmstp-exe.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-defense-evasion-via-proot.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-dga-activity.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-disabling-of-apparmor.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-dll-side-loading-via-trusted-microsoft-programs.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-enumeration-via-active-directory-web-service.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-evasion-via-windows-filtering-platform.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-execution-via-xzbackdoor.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-exploitation-of-an-unquoted-service-path-vulnerability.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-external-linux-ssh-brute-force-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-file-download-via-a-headless-browser.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-file-transfer-via-certreq.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-hidden-process-via-mount-hidepid.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-internal-linux-ssh-brute-force-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-linux-backdoor-user-account-creation.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-linux-credential-dumping-via-proc-filesystem.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-linux-credential-dumping-via-unshadow.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-linux-hack-tool-launched.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-linux-local-account-brute-force-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-linux-ransomware-note-creation-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-linux-ssh-x11-forwarding.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-linux-tunneling-and-or-port-forwarding.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-browser-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-business-app-installer.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-communication-apps.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-system32-dll.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-system32-executable.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-vlc-dll.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-memory-seeking-activity.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-meterpreter-reverse-shell.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-network-scan-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-network-scan-executed-from-host.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-network-share-discovery.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-network-sweep-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-non-standard-port-http-https-connection.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-okta-mfa-bombing-via-push-notifications.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-outgoing-rdp-connection-by-unusual-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-pass-the-hash-pth-attempt.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-persistence-through-init-d-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-persistence-through-motd-file-creation-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-persistence-through-run-control-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-persistence-through-systemd-udevd.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-powershell-hacktool-script-by-author.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-powershell-hacktool-script-by-function-names.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-powershell-pass-the-hash-relay-script.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-through-writable-docker-socket.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-container-misconfiguration.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-cve-2022-38028.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-cve-2023-4911.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-enlightenment.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-linux-dac-permissions.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-overlayfs.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-python-cap-setuid.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-recently-compiled-executable.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-uid-int-max-bug-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-process-injection-from-malicious-document.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-chisel-client.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-chisel-server.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-pspy-process-monitoring-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-ransomware-behavior-high-count-of-readme-files-by-system.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-ransomware-note-file-dropped-via-smb.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-remote-code-execution-via-web-server.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-remote-file-execution-via-msiexec.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-background-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-child.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-java.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-suspicious-binary.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-suspicious-child-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-udp.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-reverse-shell.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-shell-via-wildcard-injection-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-ssh-it-ssh-worm-downloaded.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-successful-linux-ftp-brute-force-attack-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-successful-linux-rdp-brute-force-attack-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-successful-ssh-brute-force-attack.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-sudo-hijacking-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-sudo-privilege-escalation-via-cve-2019-14287.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-sudo-token-manipulation-via-process-injection.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-suspicious-clipboard-activity-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-suspicious-debugfs-root-device-access.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-suspicious-file-edit.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-syn-based-network-scan-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-unauthorized-access-via-wildcard-injection-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-upgrade-of-non-interactive-shell.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-veeam-credential-access-command.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-widespread-malware-infection-across-multiple-hosts.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potential-windows-session-hijacking-via-ccmexec.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potentially-successful-mfa-bombing-via-push-notifications.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/potentially-suspicious-process-started-via-tmux-or-screen.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-invoke-ninjacopy-script.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-kerberos-ticket-dump.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-mailbox-collection-script.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-script-with-archive-compression-capabilities.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-script-with-discovery-capabilities.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-script-with-encryption-decryption-capabilities.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-script-with-log-clear-capabilities.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-script-with-password-policy-discovery-capabilities.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-script-with-remote-execution-capabilities-via-winrm.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-script-with-veeam-credential-access-capabilities.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-script-with-webcam-video-capture-capabilities.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-clipboard-retrieval-capabilities.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-cap-chown-cap-fowner-capabilities.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-cap-setuid-setgid-capabilities.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-gdb-cap-sys-ptrace.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/process-capability-enumeration.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/process-created-with-a-duplicated-token.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/process-discovery-using-built-in-tools.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/process-discovery-via-built-in-applications.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/processes-with-trailing-spaces.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/proxychains-activity.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/python-script-execution-via-command-line.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/quarantine-attrib-removed-by-unsigned-or-untrusted-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/query-registry-using-built-in-tools.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/rare-smb-connection-to-the-internet.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/remote-scheduled-task-creation-via-rpc.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/remote-xsl-script-execution-via-com.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/renamed-utility-executed-with-short-program-name.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/root-network-connection-via-gdb-cap-sys-ptrace.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/route53-resolver-query-log-configuration-deleted.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/screenconnect-server-spawning-suspicious-processes.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/segfault-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/sensitive-files-compression-inside-a-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/sensitive-keys-or-passwords-searched-for-inside-a-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/service-disabled-via-registry-modification.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/service-path-modification-via-sc-exe.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/service-path-modification.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/setcap-setuid-setgid-capability-set.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/shared-object-created-or-changed-by-previously-unknown-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/shell-configuration-modification.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/shortcut-file-written-or-modified-on-startup-folder.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/spike-in-bytes-sent-to-an-external-device-via-airdrop.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/spike-in-bytes-sent-to-an-external-device.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/spike-in-number-of-connections-made-from-a-source-ip.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/spike-in-number-of-connections-made-to-a-destination-ip.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/spike-in-number-of-processes-in-an-rdp-session.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/spike-in-remote-file-transfers.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/spike-in-successful-logon-events-from-a-source-ip.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/ssh-authorized-keys-file-modified-inside-a-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/ssh-connection-established-inside-a-running-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/ssh-process-launched-from-inside-a-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/statistical-model-detected-c2-beaconing-activity-with-high-confidence.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/statistical-model-detected-c2-beaconing-activity.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/stolen-credentials-used-to-login-to-okta-account-after-mfa-reset.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/sudo-command-enumeration-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suid-sguid-enumeration-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-access-to-ldap-attributes.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-antimalware-scan-interface-dll.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-apt-package-manager-execution.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-apt-package-manager-network-connection.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-communication-app-child-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-content-extracted-or-decompressed-via-funzip.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-data-encryption-via-openssl-utility.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-dynamic-linker-discovery-via-od.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-execution-from-inet-cache.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-microsoft-office-add-ins.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-msiexec.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-windows-subsystem-for-linux.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-file-changes-activity-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-file-creation-via-kworker.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-file-downloaded-from-google-drive.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-file-renamed-via-smb.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-image-load-taskschd-dll-from-ms-office.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-inter-process-communication-via-outlook.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-interactive-shell-spawned-from-inside-a-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-jetbrains-teamcity-child-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-kworker-uid-elevation.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-lsass-process-access.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-memory-grep-activity.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-microsoft-365-mail-access-by-clientappid.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-mining-process-creation-event.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-modprobe-file-event.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-module-loaded-by-lsass.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-net-code-compilation.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-net-reflection-via-powershell.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-network-activity-to-the-internet-by-previously-unknown-executable.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-network-connection-via-sudo-binary.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-network-connection-via-systemd.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-network-tool-launched-inside-a-container.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-passwd-file-event-action.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-proc-maps-discovery.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-proc-pseudo-file-system-enumeration.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-process-spawned-from-motd-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-renaming-of-esxi-files.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-renaming-of-esxi-index-html-file.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-screenconnect-client-child-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-symbolic-link-created.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-sysctl-file-event.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-system-commands-executed-by-previously-unknown-executable.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-termination-of-esxi-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-troubleshooting-pack-cabinet-execution.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-utility-launched-via-proxychains.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-web-browser-sensitive-file-access.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-which-enumeration.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-host.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-parent-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/suspicious-wmi-event-subscription-created.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/system-binary-copied-and-or-moved-to-suspicious-directory.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/system-hosts-file-access.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/system-network-connections-discovery.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/system-owner-user-discovery-linux.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/system-service-discovery-through-built-in-windows-utilities.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/system-time-discovery.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/tainted-kernel-module-load.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/tainted-out-of-tree-kernel-module-load.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/tampering-of-shell-command-line-history.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/threat-intel-hash-indicator-match.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/threat-intel-ip-address-indicator-match.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/threat-intel-url-indicator-match.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/threat-intel-windows-registry-indicator-match.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/trap-signals-execution.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/uid-elevation-from-previously-unknown-executable.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unix-socket-connection.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unknown-execution-of-binary-with-rwx-memory-region.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unsigned-bits-service-client-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unsigned-dll-loaded-by-a-trusted-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unsigned-dll-loaded-by-svchost.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unsigned-dll-side-loading-from-a-suspicious-folder.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/untrusted-driver-loaded.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-child-process-of-dns-exe.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-discovery-activity-by-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-discovery-signal-alert-with-unusual-process-command-line.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-discovery-signal-alert-with-unusual-process-executable.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-execution-via-microsoft-common-console-file.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-file-modification-by-dns-exe.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-high-confidence-misconduct-blocks-detected.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-linux-network-configuration-discovery.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-linux-user-discovery-activity.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-parent-process-for-cmd-exe.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-process-execution-on-wbem-path.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-process-extension.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-process-for-mssql-service-accounts.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-host.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-parent-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-user.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-process-writing-data-to-an-external-device.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-remote-file-directory.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-remote-file-extension.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-remote-file-size.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-time-or-day-for-an-rdp-session.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/unusual-user-privilege-enumeration-via-id.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/veeam-backup-library-loaded-by-unusual-process.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/werfault-reflectdebugger-persistence.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/windows-account-or-group-discovery.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/windows-installer-with-suspicious-properties.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/windows-subsystem-for-linux-distribution-installed.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/windows-subsystem-for-linux-enabled-via-dism-utility.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/windows-system-information-discovery.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/windows-system-network-connections-discovery.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/windows-user-account-creation.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/wmi-wbemtest-utility-execution.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/wmic-remote-command.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/wpad-service-exploit.asciidoc
 create mode 100644 docs/detections/prebuilt-rules/rule-details/writedac-access-on-active-directory-object.asciidoc

diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-access-to-keychain-credentials-directories.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-access-to-keychain-credentials-directories.asciidoc
new file mode 100644
index 0000000000..c47cd32b56
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-access-to-keychain-credentials-directories.asciidoc
@@ -0,0 +1,136 @@
+[[prebuilt-rule-8-14-1-access-to-keychain-credentials-directories]]
+=== Access to Keychain Credentials Directories
+
+Adversaries may collect the keychain storage data from a system to acquire credentials. Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features such as WiFi passwords, websites, secure notes and certificates.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://objective-see.com/blog/blog_0x25.html
+* https://securelist.com/calisto-trojan-for-macos/86543/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 207
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and
+  process.args :
+    (
+      "/Users/*/Library/Keychains/*",
+      "/Library/Keychains/*",
+      "/Network/Library/Keychains/*",
+      "System.keychain",
+      "login.keychain-db",
+      "login.keychain"
+    ) and
+    not process.args : ("find-certificate",
+                        "add-trusted-cert",
+                        "set-keychain-settings",
+                        "delete-certificate",
+                        "/Users/*/Library/Keychains/openvpn.keychain-db",
+                        "show-keychain-info",
+                        "lock-keychain",
+                        "set-key-partition-list",
+                        "import",
+                        "find-identity") and
+    not process.parent.executable :
+      (
+        "/Applications/OpenVPN Connect/OpenVPN Connect.app/Contents/MacOS/OpenVPN Connect",
+        "/Applications/Microsoft Defender.app/Contents/MacOS/wdavdaemon_enterprise.app/Contents/MacOS/wdavdaemon_enterprise",
+        "/opt/jc/bin/jumpcloud-agent"
+      ) and
+    not process.executable : ("/opt/jc/bin/jumpcloud-agent", "/usr/bin/basename") and
+    not process.Ext.effective_parent.executable : ("/opt/rapid7/ir_agent/ir_agent",
+                                                   "/Library/Elastic/Endpoint/elastic-endpoint.app/Contents/MacOS/elastic-endpoint",
+                                                   "/Applications/QualysCloudAgent.app/Contents/MacOS/qualys-cloud-agent",
+                                                   "/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfDaemon.app/Contents/MacOS/JamfDaemon",
+                                                   "/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfManagementService.app/Contents/MacOS/JamfManagementService",
+                                                   "/usr/local/jamf/bin/jamf",
+                                                   "/Applications/Microsoft Defender.app/Contents/MacOS/wdavdaemon")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Sub-technique:
+** Name: Keychain
+** ID: T1555.001
+** Reference URL: https://attack.mitre.org/techniques/T1555/001/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-adversary-behavior-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-adversary-behavior-detected-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..fc53f93fb2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-adversary-behavior-detected-elastic-endgame.asciidoc
@@ -0,0 +1,59 @@
+[[prebuilt-rule-8-14-1-adversary-behavior-detected-elastic-endgame]]
+=== Adversary Behavior - Detected - Elastic Endgame
+
+Elastic Endgame detected an Adversary Behavior. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+
+*Version*: 104
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and (event.action:behavior_protection_event or endgame.event_subtype_full:behavior_protection_event)
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-alternate-data-stream-creation-execution-at-volume-root-directory.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-alternate-data-stream-creation-execution-at-volume-root-directory.asciidoc
new file mode 100644
index 0000000000..5c56f2ce09
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-alternate-data-stream-creation-execution-at-volume-root-directory.asciidoc
@@ -0,0 +1,73 @@
+[[prebuilt-rule-8-14-1-alternate-data-stream-creation-execution-at-volume-root-directory]]
+=== Alternate Data Stream Creation/Execution at Volume Root Directory
+
+Identifies the creation of an Alternate Data Stream (ADS) at a volume root directory, which can indicate the attempt to hide tools and malware, as ADSs created in this directory are not displayed by system utilities.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.crowdstrike.com/blog/anatomy-of-alpha-spider-ransomware/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+any where host.os.type == "windows" and event.category in ("file", "process") and 
+  (
+    (event.type == "creation" and file.path regex~ """[A-Z]:\\:.+""") or 
+    (event.type == "start" and process.executable regex~ """[A-Z]:\\:.+""")
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hide Artifacts
+** ID: T1564
+** Reference URL: https://attack.mitre.org/techniques/T1564/
+* Sub-technique:
+** Name: NTFS File Attributes
+** ID: T1564.004
+** Reference URL: https://attack.mitre.org/techniques/T1564/004/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-apple-scripting-execution-with-administrator-privileges.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-apple-scripting-execution-with-administrator-privileges.asciidoc
new file mode 100644
index 0000000000..eb933ae783
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-apple-scripting-execution-with-administrator-privileges.asciidoc
@@ -0,0 +1,111 @@
+[[prebuilt-rule-8-14-1-apple-scripting-execution-with-administrator-privileges]]
+=== Apple Scripting Execution with Administrator Privileges
+
+Identifies execution of the Apple script interpreter (osascript) without a password prompt and with administrator privileges.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://discussions.apple.com/thread/2266150
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 207
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and process.name : "osascript" and
+  process.command_line : "osascript*with administrator privileges" and
+  not process.parent.name : "Electron" and
+  not process.Ext.effective_parent.executable : ("/Applications/Visual Studio Code.app/Contents/MacOS/Electron",
+                                                 "/Applications/OpenVPN Connect/Uninstall OpenVPN Connect.app/Contents/MacOS/uninstaller")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-authorization-plugin-modification.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-authorization-plugin-modification.asciidoc
new file mode 100644
index 0000000000..0c380c60ce
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-authorization-plugin-modification.asciidoc
@@ -0,0 +1,106 @@
+[[prebuilt-rule-8-14-1-authorization-plugin-modification]]
+=== Authorization Plugin Modification
+
+Authorization plugins are used to extend the authorization services API and implement mechanisms that are not natively supported by the OS, such as multi-factor authentication with third party software. Adversaries may abuse this feature to persist and/or collect clear text credentials as they traverse the registered plugins during user logon.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://developer.apple.com/documentation/security/authorization_plug-ins
+* https://www.xorrior.com/persistent-credential-theft/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:file and host.os.type:macos and not event.type:deletion and
+  file.path:(/Library/Security/SecurityAgentPlugins/* and
+  not (/Library/Security/SecurityAgentPlugins/KandjiPassport.bundle/* or /Library/Security/SecurityAgentPlugins/TeamViewerAuthPlugin.bundle/*)) and
+  not (process.name:shove and process.code_signature.trusted:true)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Sub-technique:
+** Name: Authentication Package
+** ID: T1547.002
+** Reference URL: https://attack.mitre.org/techniques/T1547/002/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-aws-ec2-admin-credential-fetch-via-assumed-role.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-aws-ec2-admin-credential-fetch-via-assumed-role.asciidoc
new file mode 100644
index 0000000000..be83512020
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-aws-ec2-admin-credential-fetch-via-assumed-role.asciidoc
@@ -0,0 +1,124 @@
+[[prebuilt-rule-8-14-1-aws-ec2-admin-credential-fetch-via-assumed-role]]
+=== AWS EC2 Admin Credential Fetch via Assumed Role
+
+Identifies the first occurrence of a user identity in AWS using `GetPassword` for the administrator password of an EC2 instance with an assumed role. Adversaries may use this API call to escalate privileges or move laterally within EC2 instances.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-aws.cloudtrail*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://cloud.hacktricks.xyz/pentesting-cloud/aws-security/aws-privilege-escalation/aws-ec2-privesc
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: Amazon EC2
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Credential Access
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+*Triage and Analysis*
+
+
+
+*Investigating AWS EC2 Admin Credential Fetch via Assumed Role*
+
+
+This rule detects the first occurrence of a user identity using the `GetPasswordData` API call in AWS, which retrieves the administrator password of an EC2 instance. This can be an indicator of an adversary attempting to escalate privileges or move laterally within EC2 instances.
+
+This is a New Terms rule, which means it will only trigger once for each unique value of the `aws.cloudtrail.user_identity.session_context.session_issuer.arn` field that has not been seen making this API request within the last 7 days. This field contains the Amazon Resource Name (ARN) of the assumed role that triggered the API call.
+
+
+*Possible Investigation Steps*
+
+
+- **Identify the User Identity and Role**: Examine the AWS CloudTrail logs to determine the user identity that made the `GetPasswordData` request. Pay special attention to the role and permissions associated with the user.
+- **Review Request and Response Parameters**: Analyze the `aws.cloudtrail.request_parameters` and `aws.cloudtrail.response_elements` fields to understand the context of the API call and the retrieved password.
+- **Contextualize with User Behavior**: Compare this activity against the user's typical behavior patterns. Look for unusual login times, IP addresses, or other anomalous actions taken by the user or role prior to and following the incident.
+- **Review EC2 Instance Details**: Check the details of the EC2 instance from which the password was retrieved. Assess the criticality and sensitivity of the applications running on this instance.
+- **Examine Related CloudTrail Events**: Search for other API calls made by the same user identity, especially those modifying security groups, network access controls, or instance metadata.
+- **Check for Lateral Movement**: Look for evidence that the obtained credentials have been used to access other resources or services within AWS.
+- **Investigate the Origin of the API Call**: Analyze the IP address and geographical location from which the request originated. Determine if it aligns with expected locations for legitimate administrative activity.
+
+
+*False Positive Analysis*
+
+
+- **Legitimate Administrative Actions**: Ensure that the activity was not part of legitimate administrative tasks such as system maintenance or updates.
+- **Automation Scripts**: Verify if the activity was generated by automation or deployment scripts that are authorized to use `GetPasswordData` for legitimate purposes.
+
+
+*Response and Remediation*
+
+
+- **Immediate Isolation**: If suspicious, isolate the affected instance to prevent any potential lateral movement or further unauthorized actions.
+- **Credential Rotation**: Rotate credentials of the affected instance or assumed role and any other potentially compromised credentials.
+- **User Account Review**: Review the permissions of the implicated user identity. Apply the principle of least privilege by adjusting permissions to prevent misuse.
+- **Enhanced Monitoring**: Increase monitoring on the user identity that triggered the rule and similar EC2 instances.
+- **Incident Response**: If malicious intent is confirmed, initiate the incident response protocol. This includes further investigation, containment of the threat, eradication of any threat actor presence, and recovery of affected systems.
+- **Preventative Measures**: Implement or enhance security measures such as multi-factor authentication and continuous audits of sensitive operations like `GetPasswordData`.
+
+
+*Additional Information*
+
+
+Refer to resources like https://cloud.hacktricks.xyz/pentesting-cloud/aws-security/aws-privilege-escalation/aws-ec2-privesc[AWS privilege escalation methods] and the MITRE ATT&CK technique https://attack.mitre.org/techniques/T1552/005/[T1552.005 - Cloud Instance Metadata API] for more details on potential vulnerabilities and mitigation strategies.
+
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"aws.cloudtrail"
+    and event.provider:"ec2.amazonaws.com" and event.action:"GetPasswordData"
+    and aws.cloudtrail.user_identity.type:"AssumedRole" and aws.cloudtrail.error_code:"Client.UnauthorizedOperation"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Unsecured Credentials
+** ID: T1552
+** Reference URL: https://attack.mitre.org/techniques/T1552/
+* Sub-technique:
+** Name: Cloud Instance Metadata API
+** ID: T1552.005
+** Reference URL: https://attack.mitre.org/techniques/T1552/005/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-component-object-model-hijacking.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-component-object-model-hijacking.asciidoc
new file mode 100644
index 0000000000..ee037140d5
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-component-object-model-hijacking.asciidoc
@@ -0,0 +1,208 @@
+[[prebuilt-rule-8-14-1-component-object-model-hijacking]]
+=== Component Object Model Hijacking
+
+Identifies Component Object Model (COM) hijacking via registry modification. Adversaries may establish persistence by executing malicious content triggered by hijacked references to COM objects.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.registry-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://bohops.com/2018/08/18/abusing-the-com-registry-structure-part-2-loading-techniques-for-evasion-and-persistence/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Tactic: Privilege Escalation
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 113
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Component Object Model Hijacking*
+
+
+Adversaries can insert malicious code that can be executed in place of legitimate software through hijacking the COM references and relationships as a means of persistence.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Retrieve the file referenced in the registry and determine if it is malicious:
+  - Use a private sandboxed malware analysis system to perform analysis.
+    - Observe and collect information about the following activities:
+      - Attempts to contact external domains and addresses.
+      - File and registry access, modification, and creation activities.
+      - Service creation and launch activities.
+      - Scheduled task creation.
+  - Use the PowerShell Get-FileHash cmdlet to get the files' SHA-256 hash values.
+    - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- Some Microsoft executables will reference the LocalServer32 registry key value for the location of external COM objects.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+registry where host.os.type == "windows" and
+  /* not necessary but good for filtering privileged installations */
+  user.domain != "NT AUTHORITY" and process.executable != null and 
+  (
+    (
+      registry.path : "HK*\\InprocServer32\\" and
+      registry.data.strings: ("scrobj.dll", "?:\\*\\scrobj.dll") and
+      not registry.path : "*\\{06290BD*-48AA-11D2-8432-006008C3FBFC}\\*"
+    ) or
+
+    (
+      registry.path : "HKLM\\*\\InProcServer32\\*" and
+        registry.data.strings : ("*\\Users\\*", "*\\ProgramData\\*")
+    ) or
+
+    /* in general COM Registry changes on Users Hive is less noisy and worth alerting */
+    (
+      registry.path : (
+        "HKEY_USERS\\*\\InprocServer32\\",
+        "HKEY_USERS\\*\\LocalServer32\\",
+        "HKEY_USERS\\*\\DelegateExecute",
+        "HKEY_USERS\\*\\TreatAs\\",
+        "HKEY_USERS\\*\\ScriptletURL*"
+      )  
+    )
+  ) and 
+
+      not  (
+            process.code_signature.trusted == true and
+            process.code_signature.subject_name in 
+                         ("Island Technology Inc.", "Google LLC", "Grammarly, Inc.", "Dropbox, Inc", "REFINITIV US LLC", "HP Inc.",
+                          "Citrix Systems, Inc.", "Adobe Inc.", "Veeam Software Group GmbH", "Zhuhai Kingsoft Office Software Co., Ltd.",
+                          "Oracle America, Inc.")
+        ) and 
+
+  /* excludes Microsoft signed noisy processes */
+  not
+  (
+    process.name : ("OneDrive.exe", "OneDriveSetup.exe", "FileSyncConfig.exe", "Teams.exe", "MicrosoftEdgeUpdate.exe", "msrdcw.exe", "MicrosoftEdgeUpdateComRegisterShell64.exe") and
+    process.code_signature.trusted == true and process.code_signature.subject_name in ("Microsoft Windows", "Microsoft Corporation")
+  ) and
+  
+  not process.executable : 
+                  ("?:\\Program Files (x86)\\*.exe", 
+                   "?:\\Program Files\\*.exe",
+                   "?:\\Windows\\System32\\svchost.exe", 
+                   "?:\\Windows\\System32\\msiexec.exe", 
+                   "?:\\Windows\\SysWOW64\\regsvr32.exe",
+                   "?:\\Windows\\System32\\regsvr32.exe",
+                   "?:\\Windows\\System32\\DriverStore\\FileRepository\\*.exe", 
+                   "?:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\*\\MsMpEng.exe")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: Component Object Model Hijacking
+** ID: T1546.015
+** Reference URL: https://attack.mitre.org/techniques/T1546/015/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: Component Object Model Hijacking
+** ID: T1546.015
+** Reference URL: https://attack.mitre.org/techniques/T1546/015/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-connection-to-commonly-abused-web-services.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-connection-to-commonly-abused-web-services.asciidoc
new file mode 100644
index 0000000000..6c7321e8d4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-connection-to-commonly-abused-web-services.asciidoc
@@ -0,0 +1,297 @@
+[[prebuilt-rule-8-14-1-connection-to-commonly-abused-web-services]]
+=== Connection to Commonly Abused Web Services
+
+Adversaries may implement command and control (C2) communications that use common web services to hide their activity. This attack technique is typically targeted at an organization and uses web services common to the victim network, which allows the adversary to blend into legitimate traffic activity. These popular services are typically targeted since they have most likely been used before compromise, which helps malicious traffic blend in.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.network-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 113
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Connection to Commonly Abused Web Services*
+
+
+Adversaries may use an existing, legitimate external Web service as a means for relaying data to/from a compromised system. Popular websites and social media acting as a mechanism for C2 may give a significant amount of cover due to the likelihood that hosts within a network are already communicating with them prior to a compromise.
+
+This rule looks for processes outside known legitimate program locations communicating with a list of services that can be abused for exfiltration or command and control.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/interactive-investigation-guides.html[Investigate Markdown Plugin] introduced in Elastic Stack version 8.8.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - !{investigate{"label":"Alerts associated with the user in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"user.id","queryType":"phrase","value":"{{user.id}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
+  - !{investigate{"label":"Alerts associated with the host in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"host.name","queryType":"phrase","value":"{{host.name}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
+- Verify whether the digital signature exists in the executable.
+- Identify the operation type (upload, download, tunneling, etc.).
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+        - !{investigate{"label":"Investigate the Subject Process Network Events","providers":[[{"excluded":false,"field":"process.entity_id","queryType":"phrase","value":"{{process.entity_id}}","valueType":"string"},{"excluded":false,"field":"event.category","queryType":"phrase","value":"network","valueType":"string"}]]}}
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- This rule has a high chance to produce false positives because it detects communication with legitimate services. Noisy false positives can be added as exceptions.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+network where host.os.type == "windows" and network.protocol == "dns" and
+    process.name != null and user.id not in ("S-1-5-18", "S-1-5-19", "S-1-5-20") and
+    /* Add new WebSvc domains here */
+    dns.question.name :
+       (
+        "raw.githubusercontent.*",
+        "pastebin.*",
+        "paste4btc.com",
+        "paste.ee",
+        "ghostbin.com",
+        "drive.google.com",
+        "?.docs.live.net",
+        "api.dropboxapi.*",
+        "content.dropboxapi.*",
+        "dl.dropboxusercontent.*",
+        "api.onedrive.com",
+        "*.onedrive.org",
+        "onedrive.live.com",
+        "filebin.net",
+        "*.ngrok.io",
+        "ngrok.com",
+        "*.portmap.*",
+        "*serveo.net",
+        "*localtunnel.me",
+        "*pagekite.me",
+        "*localxpose.io",
+        "*notabug.org",
+        "rawcdn.githack.*",
+        "paste.nrecom.net",
+        "zerobin.net",
+        "controlc.com",
+        "requestbin.net",
+        "slack.com",
+        "api.slack.com",
+        "slack-redir.net",
+        "slack-files.com",
+        "cdn.discordapp.com",
+        "discordapp.com",
+        "discord.com",
+        "apis.azureedge.net",
+        "cdn.sql.gg",
+        "?.top4top.io",
+        "top4top.io",
+        "www.uplooder.net",
+        "*.cdnmegafiles.com",
+        "transfer.sh",
+        "gofile.io",
+        "updates.peer2profit.com",
+        "api.telegram.org",
+        "t.me",
+        "meacz.gq",
+        "rwrd.org",
+        "*.publicvm.com",
+        "*.blogspot.com",
+        "api.mylnikov.org",
+        "file.io",
+        "stackoverflow.com",
+        "*files.1drv.com",
+        "api.anonfile.com",
+        "*hosting-profi.de",
+        "ipbase.com",
+        "ipfs.io",
+        "*up.freeo*.space",
+        "api.mylnikov.org",
+        "script.google.com",
+        "script.googleusercontent.com",
+        "api.notion.com",
+        "graph.microsoft.com",
+        "*.sharepoint.com",
+        "mbasic.facebook.com",
+        "login.live.com",
+        "api.gofile.io",
+        "api.anonfiles.com",
+        "api.notion.com",
+        "api.trello.com",
+        "gist.githubusercontent.com",
+        "files.pythonhosted.org",
+        "g.live.com",
+        "*.zulipchat.com",
+        "webhook.site",
+        "run.mocky.io",
+        "mockbin.org") and
+        
+    /* Insert noisy false positives here */
+    not (
+      (
+        process.executable : (
+          "?:\\Program Files\\*.exe",
+          "?:\\Program Files (x86)\\*.exe",
+          "?:\\Windows\\System32\\WWAHost.exe",
+          "?:\\Windows\\System32\\smartscreen.exe",
+          "?:\\Windows\\System32\\MicrosoftEdgeCP.exe",
+          "?:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\*\\MsMpEng.exe",
+          "?:\\Users\\*\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe",
+          "?:\\Users\\*\\AppData\\Local\\BraveSoftware\\*\\Application\\brave.exe",
+          "?:\\Users\\*\\AppData\\Local\\Vivaldi\\Application\\vivaldi.exe",
+          "?:\\Users\\*\\AppData\\Local\\Programs\\Opera*\\opera.exe",
+          "?:\\Users\\*\\AppData\\Local\\Programs\\Fiddler\\Fiddler.exe",
+          "?:\\Users\\*\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe",
+          "?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\OneDrive.exe",
+          "?:\\Windows\\system32\\mobsync.exe",
+          "?:\\Windows\\SysWOW64\\mobsync.exe"
+        )
+      ) or
+    
+      /* Discord App */
+      (process.name : "Discord.exe" and (process.code_signature.subject_name : "Discord Inc." and
+       process.code_signature.trusted == true) and dns.question.name : ("discord.com", "cdn.discordapp.com", "discordapp.com")
+      ) or 
+
+      /* MS Sharepoint */
+      (process.name : "Microsoft.SharePoint.exe" and (process.code_signature.subject_name : "Microsoft Corporation" and
+       process.code_signature.trusted == true) and dns.question.name : "onedrive.live.com"
+      ) or 
+
+      /* Firefox */
+      (process.name : "firefox.exe" and (process.code_signature.subject_name : "Mozilla Corporation" and
+       process.code_signature.trusted == true)
+      ) or 
+
+      /* Dropbox */
+      (process.name : "Dropbox.exe" and (process.code_signature.subject_name : "Dropbox, Inc" and
+       process.code_signature.trusted == true) and dns.question.name : ("api.dropboxapi.com", "*.dropboxusercontent.com")
+      ) or 
+
+      /* Obsidian - Plugins are stored on raw.githubusercontent.com */
+      (process.name : "Obsidian.exe" and (process.code_signature.subject_name : "Dynalist Inc" and
+       process.code_signature.trusted == true) and dns.question.name : "raw.githubusercontent.com"
+      ) or 
+
+      /* WebExperienceHostApp */
+      (process.name : "WebExperienceHostApp.exe" and (process.code_signature.subject_name : "Microsoft Windows" and
+       process.code_signature.trusted == true) and dns.question.name : ("onedrive.live.com", "skyapi.onedrive.live.com")
+      ) or
+
+      (process.code_signature.subject_name : "Microsoft *" and process.code_signature.trusted == true and
+       dns.question.name : ("*.sharepoint.com", "graph.microsoft.com", "g.live.com", "login.live.com", "login.live.com")) or
+
+      (process.code_signature.trusted == true and
+       process.code_signature.subject_name :
+                             ("Johannes Schindelin",
+                              "Redis Inc.",
+                              "Slack Technologies, LLC",
+                              "Cisco Systems, Inc.",
+                              "Dropbox, Inc",
+                              "Amazon.com Services LLC"))
+    ) 
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Web Service
+** ID: T1102
+** Reference URL: https://attack.mitre.org/techniques/T1102/
+* Technique:
+** Name: Dynamic Resolution
+** ID: T1568
+** Reference URL: https://attack.mitre.org/techniques/T1568/
+* Sub-technique:
+** Name: Domain Generation Algorithms
+** ID: T1568.002
+** Reference URL: https://attack.mitre.org/techniques/T1568/002/
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over Web Service
+** ID: T1567
+** Reference URL: https://attack.mitre.org/techniques/T1567/
+* Sub-technique:
+** Name: Exfiltration to Code Repository
+** ID: T1567.001
+** Reference URL: https://attack.mitre.org/techniques/T1567/001/
+* Sub-technique:
+** Name: Exfiltration to Cloud Storage
+** ID: T1567.002
+** Reference URL: https://attack.mitre.org/techniques/T1567/002/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-container-workload-protection.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-container-workload-protection.asciidoc
new file mode 100644
index 0000000000..dfcf2c5d8d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-container-workload-protection.asciidoc
@@ -0,0 +1,60 @@
+[[prebuilt-rule-8-14-1-container-workload-protection]]
+=== Container Workload Protection
+
+Generates a detection alert each time a 'Container Workload Protection' alert is received. Enabling this rule allows you to immediately begin triaging and investigating these alerts.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-cloud_defend.alerts-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-10m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:cloud_defend
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-dumping-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-dumping-detected-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..f589c641de
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-dumping-detected-elastic-endgame.asciidoc
@@ -0,0 +1,76 @@
+[[prebuilt-rule-8-14-1-credential-dumping-detected-elastic-endgame]]
+=== Credential Dumping - Detected - Elastic Endgame
+
+Elastic Endgame detected Credential Dumping. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Credential Access
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:cred_theft_event or endgame.event_subtype_full:cred_theft_event)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-dumping-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-dumping-prevented-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..0d2ddbdbdd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-dumping-prevented-elastic-endgame.asciidoc
@@ -0,0 +1,76 @@
+[[prebuilt-rule-8-14-1-credential-dumping-prevented-elastic-endgame]]
+=== Credential Dumping - Prevented - Elastic Endgame
+
+Elastic Endgame prevented Credential Dumping. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Credential Access
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:cred_theft_event or endgame.event_subtype_full:cred_theft_event)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-manipulation-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-manipulation-detected-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..f5097a0504
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-manipulation-detected-elastic-endgame.asciidoc
@@ -0,0 +1,72 @@
+[[prebuilt-rule-8-14-1-credential-manipulation-detected-elastic-endgame]]
+=== Credential Manipulation - Detected - Elastic Endgame
+
+Elastic Endgame detected Credential Manipulation. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:token_manipulation_event or endgame.event_subtype_full:token_manipulation_event)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Access Token Manipulation
+** ID: T1134
+** Reference URL: https://attack.mitre.org/techniques/T1134/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-manipulation-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-manipulation-prevented-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..bc301e2f7e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-credential-manipulation-prevented-elastic-endgame.asciidoc
@@ -0,0 +1,72 @@
+[[prebuilt-rule-8-14-1-credential-manipulation-prevented-elastic-endgame]]
+=== Credential Manipulation - Prevented - Elastic Endgame
+
+Elastic Endgame prevented Credential Manipulation. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:token_manipulation_event or endgame.event_subtype_full:token_manipulation_event)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Access Token Manipulation
+** ID: T1134
+** Reference URL: https://attack.mitre.org/techniques/T1134/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ec2-ami-shared-with-another-account.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ec2-ami-shared-with-another-account.asciidoc
new file mode 100644
index 0000000000..f25443bb2d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ec2-ami-shared-with-another-account.asciidoc
@@ -0,0 +1,118 @@
+[[prebuilt-rule-8-14-1-ec2-ami-shared-with-another-account]]
+=== EC2 AMI Shared with Another Account
+
+Identifies an AWS Amazon Machine Image (AMI) being shared with another AWS account. Adversaries with access may share an AMI with an external AWS account as a means of data exfiltration. AMIs can contain secrets, bash histories, code artifacts, and other sensitive data that adversaries may abuse if shared with unauthorized accounts. AMIs can be made publicly available accidentally as well.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-aws.cloudtrail-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html
+* https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-explicit.html
+* https://stratus-red-team.cloud/attack-techniques/AWS/aws.exfiltration.ec2-share-ami/
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS EC2
+* Use Case: Threat Detection
+* Tactic: Exfiltration
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+*Triage and Analysis*
+
+
+
+*Investigating EC2 AMI Shared with Another Account*
+
+
+This rule identifies when an Amazon Machine Image (AMI) is shared with another AWS account. While sharing AMIs is a common practice, adversaries may exploit this feature to exfiltrate data by sharing AMIs with external accounts under their control.
+
+
+*Possible Investigation Steps*
+
+
+- **Review the Sharing Event**: Identify the AMI involved and review the event details in AWS CloudTrail. Look for `ModifyImageAttribute` actions where the AMI attributes were changed to include additional user accounts.
+    - **Request and Response Parameters**: Check the `aws.cloudtrail.request_parameters` and `aws.response.response_elements` fields in the CloudTrail event to identify the AMI ID and the user ID of the account with which the AMI was shared.
+- **Verify the Shared AMI**: Check the AMI that was shared and its contents to determine the sensitivity of the data stored within it.
+- **Contextualize with Recent Changes**: Compare this sharing event against recent changes in AMI configurations and deployments. Look for any other recent permissions changes or unusual administrative actions.
+- **Validate External Account**: Examine the AWS account to which the AMI was shared. Determine whether this account is known and previously authorized to access such resources.
+- **Interview Relevant Personnel**: If the share was initiated by a user, verify the intent and authorization for this action with the person or team responsible for managing AMI deployments.
+- **Audit Related Security Policies**: Check the security policies governing AMI sharing within your organization to ensure they are being followed and are adequate to prevent unauthorized sharing.
+
+
+*False Positive Analysis*
+
+
+- **Legitimate Sharing Practices**: AMI sharing is a common and legitimate practice for collaboration and resource management in AWS. Always verify that the sharing activity was unauthorized before escalating.
+- **Automation Tools**: Some organizations use automation tools for AMI management which might programmatically share AMIs. Verify if such tools are in operation and whether their actions are responsible for the observed behavior.
+
+
+*Response and Remediation*
+
+
+- **Review and Revoke Unauthorized Shares**: If the share is found to be unauthorized, immediately revoke the shared permissions from the AMI.
+- **Enhance Monitoring of Shared AMIs**: Implement monitoring to track changes to shared AMIs and alert on unauthorized access patterns.
+- **Incident Response**: If malicious intent is confirmed, consider it a data breach incident and initiate the incident response protocol. This includes further investigation, containment, and recovery.
+- **Policy Update**: Review and possibly update your organization’s policies on AMI sharing to tighten control and prevent unauthorized access.
+- **Educate Users**: Conduct training sessions for users involved in managing AMIs to reinforce best practices and organizational policies regarding AMI sharing.
+
+
+*Additional Information*
+
+
+For more information on managing and sharing AMIs, refer to the https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html[Amazon EC2 User Guide on AMIs] and https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-explicit.html[Sharing AMIs]. Additionally, explore adversarial techniques related to data exfiltration via AMI sharing as documented by Stratus Red Team https://stratus-red-team.cloud/attack-techniques/AWS/aws.exfiltration.ec2-share-ami/[here].
+
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset: "aws.cloudtrail" and event.provider: "ec2.amazonaws.com"
+    and event.action: ModifyImageAttribute and event.outcome: success
+    and aws.cloudtrail.request_parameters: (*imageId* and *add* and *userId*)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Transfer Data to Cloud Account
+** ID: T1537
+** Reference URL: https://attack.mitre.org/techniques/T1537/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-endpoint-security.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-endpoint-security.asciidoc
new file mode 100644
index 0000000000..913685198e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-endpoint-security.asciidoc
@@ -0,0 +1,59 @@
+[[prebuilt-rule-8-14-1-endpoint-security]]
+=== Endpoint Security
+
+Generates a detection alert each time an Elastic Endpoint Security alert is received. Enabling this rule allows you to immediately begin investigating your Endpoint alerts.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.alerts-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-10m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Defend
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:(endpoint and not endgame)
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-enumeration-of-users-or-groups-via-built-in-commands.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-enumeration-of-users-or-groups-via-built-in-commands.asciidoc
new file mode 100644
index 0000000000..97cd23e088
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-enumeration-of-users-or-groups-via-built-in-commands.asciidoc
@@ -0,0 +1,127 @@
+[[prebuilt-rule-8-14-1-enumeration-of-users-or-groups-via-built-in-commands]]
+=== Enumeration of Users or Groups via Built-in Commands
+
+Identifies the execution of macOS built-in commands related to account or group enumeration. Adversaries may use account and group information to orient themselves before deciding how to act.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+
+*Version*: 207
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and
+  (
+    process.name : ("ldapsearch", "dsmemberutil") or
+    (process.name : "dscl" and
+      process.args : ("read", "-read", "list", "-list", "ls", "search", "-search") and
+      process.args : ("/Active Directory/*", "/Users*", "/Groups*"))
+	) and
+  ((process.Ext.effective_parent.executable : ("/Volumes/*", "/Applications/*") or process.parent.executable : ("/Volumes/*", "/Applications/*")) or
+   (process.Ext.effective_parent.name : ".*" or process.parent.name : ".*")) and
+  not process.Ext.effective_parent.executable : ("/Applications/QualysCloudAgent.app/Contents/MacOS/qualys-cloud-agent",
+                                                 "/Applications/Kaspersky Anti-Virus For Mac.app/Contents/MacOS/kavd.app/Contents/MacOS/kavd",
+                                                 "/Applications/ESET Endpoint Security.app/Contents/MacOS/esets_ctl",
+                                                 "/Applications/NordVPN.app/Contents/MacOS/NordVPN",
+                                                 "/Applications/Xcode.app/Contents/MacOS/Xcode",
+                                                 "/Applications/ESET Endpoint Security.app/Contents/Helpers/Uninstaller.app/Contents/MacOS/Uninstaller",
+                                                 "/Applications/Parallels Desktop.app/Contents/MacOS/prl_client_app",
+                                                 "/Applications/Zscaler/Zscaler.app/Contents/MacOS/Zscaler",
+                                                 "/Applications/com.avast.av.uninstaller.app/Contents/MacOS/com.avast.av.uninstaller",
+                                                 "/Applications/NoMAD.app/Contents/MacOS/NoMAD",
+                                                 "/Applications/ESET Management Agent.app/Contents/MacOS/ERAAgent")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Permission Groups Discovery
+** ID: T1069
+** Reference URL: https://attack.mitre.org/techniques/T1069/
+* Sub-technique:
+** Name: Local Groups
+** ID: T1069.001
+** Reference URL: https://attack.mitre.org/techniques/T1069/001/
+* Technique:
+** Name: Account Discovery
+** ID: T1087
+** Reference URL: https://attack.mitre.org/techniques/T1087/
+* Sub-technique:
+** Name: Local Account
+** ID: T1087.001
+** Reference URL: https://attack.mitre.org/techniques/T1087/001/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-exploit-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-exploit-detected-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..5b7e9dfef5
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-exploit-detected-elastic-endgame.asciidoc
@@ -0,0 +1,77 @@
+[[prebuilt-rule-8-14-1-exploit-detected-elastic-endgame]]
+=== Exploit - Detected - Elastic Endgame
+
+Elastic Endgame detected an Exploit. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Privilege Escalation
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:exploit_event or endgame.event_subtype_full:exploit_event)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-exploit-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-exploit-prevented-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..ec3c46176f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-exploit-prevented-elastic-endgame.asciidoc
@@ -0,0 +1,77 @@
+[[prebuilt-rule-8-14-1-exploit-prevented-elastic-endgame]]
+=== Exploit - Prevented - Elastic Endgame
+
+Elastic Endgame prevented an Exploit. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Privilege Escalation
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:exploit_event or endgame.event_subtype_full:exploit_event)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-external-alerts.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-external-alerts.asciidoc
new file mode 100644
index 0000000000..7ed1b64d41
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-external-alerts.asciidoc
@@ -0,0 +1,68 @@
+[[prebuilt-rule-8-14-1-external-alerts]]
+=== External Alerts
+
+Generates a detection alert for each external alert written to the configured indices. Enabling this rule allows you to immediately begin investigating external alerts in the app.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* apm-*-transaction*
+* traces-apm*
+* auditbeat-*
+* filebeat-*
+* logs-*
+* packetbeat-*
+* winlogbeat-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* OS: Windows
+* Data Source: APM
+* OS: macOS
+* OS: Linux
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and not event.module:(endgame or endpoint or cloud_defend)
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-finder-sync-plugin-registered-and-enabled.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-finder-sync-plugin-registered-and-enabled.asciidoc
new file mode 100644
index 0000000000..63502b186d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-finder-sync-plugin-registered-and-enabled.asciidoc
@@ -0,0 +1,116 @@
+[[prebuilt-rule-8-14-1-finder-sync-plugin-registered-and-enabled]]
+=== Finder Sync Plugin Registered and Enabled
+
+Finder Sync plugins enable users to extend Finder’s functionality by modifying the user interface. Adversaries may abuse this feature by adding a rogue Finder Plugin to repeatedly execute malicious payloads for persistence.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/specterops/presentations/raw/master/Leo%20Pitt/Hey_Im_Still_in_Here_Modern_macOS_Persistence_SO-CON2020.pdf
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and process.name : "pluginkit" and
+  process.args : "-e" and process.args : "use" and process.args : "-i" and
+  not process.args :
+  (
+    "com.google.GoogleDrive.FinderSyncAPIExtension",
+    "com.google.drivefs.findersync",
+    "com.boxcryptor.osx.Rednif",
+    "com.adobe.accmac.ACCFinderSync",
+    "com.microsoft.OneDrive.FinderSync",
+    "com.insynchq.Insync.Insync-Finder-Integration",
+    "com.box.desktop.findersyncext"
+  ) and
+  not process.parent.executable : ("/Library/Application Support/IDriveforMac/IDriveHelperTools/FinderPluginApp.app/Contents/MacOS/FinderPluginApp",
+                                   "/Applications/Google Drive.app/Contents/MacOS/Google Drive") and
+  not process.Ext.effective_parent.executable : ("/Applications/Google Drive.app/Contents/MacOS/Google Drive",
+                                                 "/usr/local/jamf/bin/jamf",
+                                                 "/Applications/Nextcloud.app/Contents/MacOS/Nextcloud",
+                                                 "/Library/Application Support/Checkpoint/Endpoint Security/AMFinderExtensions.app/Contents/MacOS/AMFinderExtensions",
+                                                 "/Applications/pCloud Drive.app/Contents/MacOS/pCloud Drive")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-keychain-password-retrieval-via-command-line.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-keychain-password-retrieval-via-command-line.asciidoc
new file mode 100644
index 0000000000..3831be5640
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-keychain-password-retrieval-via-command-line.asciidoc
@@ -0,0 +1,117 @@
+[[prebuilt-rule-8-14-1-keychain-password-retrieval-via-command-line]]
+=== Keychain Password Retrieval via Command Line
+
+Adversaries may collect keychain storage data from a system to in order to acquire credentials. Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features, including Wi-Fi and website passwords, secure notes, certificates, and Kerberos.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.netmeister.org/blog/keychain-passwords.html
+* https://github.com/priyankchheda/chrome_password_grabber/blob/master/chrome.py
+* https://ss64.com/osx/security.html
+* https://www.intezer.com/blog/research/operation-electrorat-attacker-creates-fake-companies-to-drain-your-crypto-wallets/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 108
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "macos" and event.action == "exec" and
+ process.name : "security" and
+ process.args : ("-wa", "-ga") and process.args : ("find-generic-password", "find-internet-password") and
+ process.command_line : ("*Chrome*", "*Chromium*", "*Opera*", "*Safari*", "*Brave*", "*Microsoft Edge*", "*Firefox*") and
+ not process.parent.executable : "/Applications/Keeper Password Manager.app/Contents/Frameworks/Keeper Password Manager Helper*/Contents/MacOS/Keeper Password Manager Helper*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Sub-technique:
+** Name: Keychain
+** ID: T1555.001
+** Reference URL: https://attack.mitre.org/techniques/T1555/001/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Sub-technique:
+** Name: Credentials from Web Browsers
+** ID: T1555.003
+** Reference URL: https://attack.mitre.org/techniques/T1555/003/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-macos-installer-package-spawns-network-event.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-macos-installer-package-spawns-network-event.asciidoc
new file mode 100644
index 0000000000..3becf9fe96
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-macos-installer-package-spawns-network-event.asciidoc
@@ -0,0 +1,119 @@
+[[prebuilt-rule-8-14-1-macos-installer-package-spawns-network-event]]
+=== MacOS Installer Package Spawns Network Event
+
+Detects the execution of a MacOS installer package with an abnormal child process (e.g bash) followed immediately by a network connection via a suspicious process (e.g curl). Threat actors will build and distribute malicious MacOS installer packages, which have a .pkg extension, many times imitating valid software in order to persuade and infect their victims often using the package files (e.g pre/post install scripts etc.) to download additional tools or malicious software. If this rule fires it should indicate the installation of a malicious or suspicious package.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://redcanary.com/blog/clipping-silver-sparrows-wings
+* https://posts.specterops.io/introducing-mystikal-4fbd2f7ae520
+* https://github.com/D00MFist/Mystikal
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=15s
+[process where host.os.type == "macos" and event.type == "start" and event.action == "exec" and process.parent.name : ("installer", "package_script_service") and process.name : ("bash", "sh", "zsh", "python", "osascript", "tclsh*")] by process.entity_id
+[network where host.os.type == "macos" and event.type == "start" and process.name : ("curl", "osascript", "wget", "python", "java", "ruby", "node")] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: JavaScript
+** ID: T1059.007
+** Reference URL: https://attack.mitre.org/techniques/T1059/007/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
+* Sub-technique:
+** Name: Web Protocols
+** ID: T1071.001
+** Reference URL: https://attack.mitre.org/techniques/T1071/001/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-malware-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-malware-detected-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..fbc6de598e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-malware-detected-elastic-endgame.asciidoc
@@ -0,0 +1,59 @@
+[[prebuilt-rule-8-14-1-malware-detected-elastic-endgame]]
+=== Malware - Detected - Elastic Endgame
+
+Elastic Endgame detected Malware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: critical
+
+*Risk score*: 99
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:file_classification_event or endgame.event_subtype_full:file_classification_event)
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-malware-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-malware-prevented-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..bd2a4fef26
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-malware-prevented-elastic-endgame.asciidoc
@@ -0,0 +1,59 @@
+[[prebuilt-rule-8-14-1-malware-prevented-elastic-endgame]]
+=== Malware - Prevented - Elastic Endgame
+
+Elastic Endgame prevented Malware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:file_classification_event or endgame.event_subtype_full:file_classification_event)
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-modification-of-environment-variable-via-unsigned-or-untrusted-parent.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-modification-of-environment-variable-via-unsigned-or-untrusted-parent.asciidoc
new file mode 100644
index 0000000000..c85d760ba1
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-modification-of-environment-variable-via-unsigned-or-untrusted-parent.asciidoc
@@ -0,0 +1,116 @@
+[[prebuilt-rule-8-14-1-modification-of-environment-variable-via-unsigned-or-untrusted-parent]]
+=== Modification of Environment Variable via Unsigned or Untrusted Parent
+
+Identifies modifications to an environment variable using the built-in launchctl command. Adversaries may execute their own malicious payloads by hijacking certain environment variables to load arbitrary libraries or bypass certain restrictions.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/rapid7/metasploit-framework/blob/master//modules/post/osx/escalate/tccbypass.rb
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:macos and event.type:start and 
+  process.name:launchctl and 
+  (process.parent.code_signature.exists : false or process.parent.code_signature.trusted : false) and
+  process.args:(setenv and not (ANT_HOME or 
+                                DBUS_LAUNCHD_SESSION_BUS_SOCKET or 
+                                EDEN_ENV or 
+                                LG_WEBOS_TV_SDK_HOME or 
+                                RUNTIME_JAVA_HOME or 
+                                WEBOS_CLI_TV or 
+                                JAVA*_HOME) and 
+                not *.vmoptions) and 
+  not process.parent.executable:("/Applications/IntelliJ IDEA CE.app/Contents/jbr/Contents/Home/lib/jspawnhelper" or 
+                                  /Applications/NoMachine.app/Contents/Frameworks/bin/nxserver.bin or 
+                                  /Applications/NoMachine.app/Contents/Frameworks/bin/nxserver.bin or 
+                                  /usr/local/bin/kr)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: Path Interception by PATH Environment Variable
+** ID: T1574.007
+** Reference URL: https://attack.mitre.org/techniques/T1574/007/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-permission-theft-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-permission-theft-detected-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..1736201e7c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-permission-theft-detected-elastic-endgame.asciidoc
@@ -0,0 +1,72 @@
+[[prebuilt-rule-8-14-1-permission-theft-detected-elastic-endgame]]
+=== Permission Theft - Detected - Elastic Endgame
+
+Elastic Endgame detected Permission Theft. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:token_protection_event or endgame.event_subtype_full:token_protection_event)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Access Token Manipulation
+** ID: T1134
+** Reference URL: https://attack.mitre.org/techniques/T1134/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-permission-theft-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-permission-theft-prevented-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..3ecf5b70d5
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-permission-theft-prevented-elastic-endgame.asciidoc
@@ -0,0 +1,72 @@
+[[prebuilt-rule-8-14-1-permission-theft-prevented-elastic-endgame]]
+=== Permission Theft - Prevented - Elastic Endgame
+
+Elastic Endgame prevented Permission Theft. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:token_protection_event or endgame.event_subtype_full:token_protection_event)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Access Token Manipulation
+** ID: T1134
+** Reference URL: https://attack.mitre.org/techniques/T1134/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-persistence-via-docker-shortcut-modification.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-persistence-via-docker-shortcut-modification.asciidoc
new file mode 100644
index 0000000000..f3890587be
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-persistence-via-docker-shortcut-modification.asciidoc
@@ -0,0 +1,101 @@
+[[prebuilt-rule-8-14-1-persistence-via-docker-shortcut-modification]]
+=== Persistence via Docker Shortcut Modification
+
+An adversary can establish persistence by modifying an existing macOS dock property list in order to execute a malicious application instead of the intended one when invoked.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/specterops/presentations/raw/master/Leo%20Pitt/Hey_Im_Still_in_Here_Modern_macOS_Persistence_SO-CON2020.pdf
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:file and host.os.type:macos and event.action:modification and
+ file.path:/Users/*/Library/Preferences/com.apple.dock.plist and
+ not process.name:(xpcproxy or cfprefsd or plutil or jamf or PlistBuddy or InstallerRemotePluginService) and
+ not process.executable:(/Library/Addigy/download-cache/* or "/Library/Kandji/Kandji Agent.app/Contents/MacOS/kandji-library-manager")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-persistence-via-folder-action-script.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-persistence-via-folder-action-script.asciidoc
new file mode 100644
index 0000000000..1c49d4966e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-persistence-via-folder-action-script.asciidoc
@@ -0,0 +1,108 @@
+[[prebuilt-rule-8-14-1-persistence-via-folder-action-script]]
+=== Persistence via Folder Action Script
+
+Detects modification of a Folder Action script. A Folder Action script is executed when the folder to which it is attached has items added or removed, or when its window is opened, closed, moved, or resized. Adversaries may abuse this feature to establish persistence by utilizing a malicious script.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://posts.specterops.io/folder-actions-for-persistence-on-macos-8923f222343d
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "macos" and event.type : "start" and process.name in ("osascript", "python", "tcl", "node", "perl", "ruby", "php", "bash", "csh", "zsh", "sh") and
+  process.parent.name == "com.apple.foundation.UserScriptService" and not process.args : ("/Users/*/Library/Application Support/iTerm2/Scripts/AutoLaunch/*.scpt", "/Users/*/Library/Application Scripts/com.microsoft.*/FoxitUtils.applescript")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Initialization Scripts
+** ID: T1037
+** Reference URL: https://attack.mitre.org/techniques/T1037/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-admin-group-account-addition.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-admin-group-account-addition.asciidoc
new file mode 100644
index 0000000000..4113d1bb56
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-admin-group-account-addition.asciidoc
@@ -0,0 +1,107 @@
+[[prebuilt-rule-8-14-1-potential-admin-group-account-addition]]
+=== Potential Admin Group Account Addition
+
+Identifies attempts to add an account to the admin group via the command line. This could be an indication of privilege escalation activity.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://managingosx.wordpress.com/2010/01/14/add-a-user-to-the-admin-group-via-command-line-3-0/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+ process.name:(dscl or dseditgroup) and process.args:(("/Groups/admin" or admin) and ("-a" or "-append")) and
+ not process.Ext.effective_parent.executable : ("/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfDaemon.app/Contents/MacOS/JamfDaemon" or
+                                                "/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfManagementService.app/Contents/MacOS/JamfManagementService" or
+                                                "/opt/jc/bin/jumpcloud-agent" or
+                                                "/Library/Addigy/go-agent")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Local Accounts
+** ID: T1078.003
+** Reference URL: https://attack.mitre.org/techniques/T1078/003/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-file-download-via-a-headless-browser.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-file-download-via-a-headless-browser.asciidoc
new file mode 100644
index 0000000000..435f213261
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-file-download-via-a-headless-browser.asciidoc
@@ -0,0 +1,108 @@
+[[prebuilt-rule-8-14-1-potential-file-download-via-a-headless-browser]]
+=== Potential File Download via a Headless Browser
+
+Identifies the use of a browser to download a file from a remote URL and from a suspicious parent process. Adversaries may use browsers to avoid ingress tool transfer restrictions.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://lolbas-project.github.io/lolbas/Binaries/Msedge/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Windows
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential File Download via a Headless Browser*
+
+
+- Investigate the process execution chain (parent process tree).
+- Investigate the process network and file events.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.name : ("chrome.exe", "msedge.exe", "brave.exe", "browser.exe", "dragon.exe", "vivaldi.exe") and
+  (process.args : "--headless*" or process.args : "data:text/html;base64,*") and
+  process.parent.name :
+     ("cmd.exe", "powershell.exe", "wscript.exe", "cscript.exe", "mshta.exe", "conhost.exe", "msiexec.exe",
+      "explorer.exe", "rundll32.exe", "winword.exe", "excel.exe", "onenote.exe", "hh.exe", "powerpnt.exe", "forfiles.exe",
+      "pcalua.exe", "wmiprvse.exe")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Ingress Tool Transfer
+** ID: T1105
+** Reference URL: https://attack.mitre.org/techniques/T1105/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-persistence-via-login-hook.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-persistence-via-login-hook.asciidoc
new file mode 100644
index 0000000000..e407ea7bab
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-persistence-via-login-hook.asciidoc
@@ -0,0 +1,117 @@
+[[prebuilt-rule-8-14-1-potential-persistence-via-login-hook]]
+=== Potential Persistence via Login Hook
+
+Identifies the creation or modification of the login window property list (plist). Adversaries may modify plist files to run a program during system boot or user login for persistence.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/D00MFist/PersistentJXA/blob/master/LoginScript.js
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 108
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+Starting in Mac OS X 10.7 (Lion), users can specify certain applications to be re-opened when a user reboots their machine. This can be abused to establish or maintain persistence on a compromised system.
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:file and host.os.type:macos and not event.type:"deletion" and
+ file.name:"com.apple.loginwindow.plist" and
+ not process.name: (systemmigrationd or DesktopServicesHelper or diskmanagementd or rsync or launchd or cfprefsd or xpcproxy or ManagedClient or MCXCompositor or backupd or "iMazing Profile Editor" or storagekitd or CloneKitService)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Plist File Modification
+** ID: T1647
+** Reference URL: https://attack.mitre.org/techniques/T1647/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-powershell-hacktool-script-by-author.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-powershell-hacktool-script-by-author.asciidoc
new file mode 100644
index 0000000000..a44f641759
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-powershell-hacktool-script-by-author.asciidoc
@@ -0,0 +1,115 @@
+[[prebuilt-rule-8-14-1-potential-powershell-hacktool-script-by-author]]
+=== Potential PowerShell HackTool Script by Author
+
+Detects known PowerShell offensive tooling author's name in PowerShell scripts. Attackers commonly use out-of-the-box offensive tools without modifying the code, which may still contain the author artifacts. This rule identifies common author handles found in popular PowerShell scripts used for red team exercises.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0109_windows_powershell_script_block_log.md
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: PowerShell Logs
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:windows and event.category:process and
+  powershell.file.script_block_text : (
+      "mattifestation" or "JosephBialek" or
+      "harmj0y" or "ukstufus" or
+      "SecureThisShit" or "Matthew Graeber" or
+      "secabstraction" or "mgeeky" or
+      "oddvarmoe" or "am0nsec" or
+      "obscuresec" or "sixdub" or
+      "darkoperator" or "funoverip" or
+      "rvrsh3ll" or "kevin_robertson" or
+      "dafthack" or "r4wd3r" or
+      "danielhbohannon" or "OneLogicalMyth" or
+      "cobbr_io" or "xorrior" or
+      "PetrMedonos" or "citronneur" or
+      "eladshamir" or "RastaMouse" or
+      "enigma0x3" or "FuzzySec" or
+      "424f424f" or "jaredhaight" or
+      "fullmetalcache" or "Hubbl3" or
+      "curi0usJack" or "Cx01N" or
+      "itm4n" or "nurfed1" or
+      "cfalta" or "Scott Sutherland" or
+      "_nullbind" or "_tmenochet" or
+      "Boe Prox" or "jaredcatkinson" or
+      "ChrisTruncer" or "monoxgas" or
+      "TheRealWover" or "splinter_code"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-ransomware-behavior-high-count-of-readme-files-by-system.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-ransomware-behavior-high-count-of-readme-files-by-system.asciidoc
new file mode 100644
index 0000000000..af5706aa3c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-ransomware-behavior-high-count-of-readme-files-by-system.asciidoc
@@ -0,0 +1,125 @@
+[[prebuilt-rule-8-14-1-potential-ransomware-behavior-high-count-of-readme-files-by-system]]
+=== Potential Ransomware Behavior - High count of Readme files by System
+
+This rule identifies a high number (20) of file creation event by the System virtual process from the same host and with same file name containing keywords similar to ransomware note files and all within a short time period.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-1m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://news.sophos.com/en-us/2023/12/21/akira-again-the-ransomware-that-keeps-on-taking/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Possible investigation steps*
+
+
+- Investigate the content of the readme files.
+- Investigate any file names with unusual extensions.
+- Investigate any incoming network connection to port 445 on this host.
+- Investigate any network logon events to this host.
+- Identify the total number and type of modified files by pid 4.
+- If the number of files is too high and source.ip connecting over SMB is unusual isolate the host and block the used credentials.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Local file modification from a Kernel mode driver.
+
+
+*Related rules*
+
+
+- Third-party Backup Files Deleted via Unexpected Process - 11ea6bec-ebde-4d71-a8e9-784948f8e3e9
+- Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
+- Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
+- Volume Shadow Copy Deletion via WMIC - dc9c1f74-dac3-48e3-b47f-eb79db358f57
+- Potential Ransomware Note File Dropped via SMB - 02bab13d-fb14-4d7c-b6fe-4a28874d37c5
+- Suspicious File Renamed via SMB - 78e9b5d5-7c07-40a7-a591-3dbbf464c386
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look for ransomware preparation and execution activities.
+- If any backups were affected:
+  - Perform data recovery locally or restore the backups from replicated copies (cloud, other servers, etc.).
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:file and host.os.type:windows and process.pid:4 and event.action:creation and
+ file.name:(*read*me* or *README* or *lock* or *LOCK* or *how*to* or *HOW*TO* or *@* or *recover* or *RECOVER* or *decrypt* or *DECRYPT* or *restore* or *RESTORE* or *FILES_BACK* or *files_back*)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Data Destruction
+** ID: T1485
+** Reference URL: https://attack.mitre.org/techniques/T1485/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-ransomware-note-file-dropped-via-smb.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-ransomware-note-file-dropped-via-smb.asciidoc
new file mode 100644
index 0000000000..670ba1ed2f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-ransomware-note-file-dropped-via-smb.asciidoc
@@ -0,0 +1,136 @@
+[[prebuilt-rule-8-14-1-potential-ransomware-note-file-dropped-via-smb]]
+=== Potential Ransomware Note File Dropped via SMB
+
+Identifies an incoming SMB connection followed by the creation of a file with a name similar to ransomware note files. This may indicate a remote ransomware attack via the SMB protocol.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Performance*
+
+
+- This rule may cause medium to high performance impact due to logic scoping all icoming SMB network events.
+
+
+*Possible investigation steps*
+
+
+- Investigate the source.ip address connecting to port 445 on this host.
+- Identify the user account that performed the file creation via SMB.
+- If the number of files is too high and source.ip connecting over SMB is unusual isolate the host and block the used credentials.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Remote file creation with similar file naming convention via SMB.
+
+
+
+*Related rules*
+
+
+- Third-party Backup Files Deleted via Unexpected Process - 11ea6bec-ebde-4d71-a8e9-784948f8e3e9
+- Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
+- Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
+- Volume Shadow Copy Deletion via WMIC - dc9c1f74-dac3-48e3-b47f-eb79db358f57
+- Suspicious File Renamed via SMB - 78e9b5d5-7c07-40a7-a591-3dbbf464c386
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look for ransomware preparation and execution activities.
+- If any backups were affected:
+  - Perform data recovery locally or restore the backups from replicated copies (cloud, other servers, etc.).
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=1s
+ [network where host.os.type == "windows" and
+  event.action == "connection_accepted" and destination.port == 445 and source.port >= 49152 and process.pid == 4 and
+  source.ip != "127.0.0.1" and source.ip != "::1"]
+ [file where host.os.type == "windows" and event.action == "creation" and
+  process.pid == 4 and user.id : ("S-1-5-21*", "S-1-12-*") and file.extension : ("hta", "txt", "readme", "htm*") and
+   /* ransom file name keywords */
+    file.name : ("*read*me*", "*lock*", "*@*", "*RECOVER*", "*decrypt*", "*restore*file*", "*FILES_BACK*", "*how*to*")] with runs=3
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Inhibit System Recovery
+** ID: T1490
+** Reference URL: https://attack.mitre.org/techniques/T1490/
+* Technique:
+** Name: Data Destruction
+** ID: T1485
+** Reference URL: https://attack.mitre.org/techniques/T1485/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-widespread-malware-infection-across-multiple-hosts.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-widespread-malware-infection-across-multiple-hosts.asciidoc
new file mode 100644
index 0000000000..676bb9e1c2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-potential-widespread-malware-infection-across-multiple-hosts.asciidoc
@@ -0,0 +1,66 @@
+[[prebuilt-rule-8-14-1-potential-widespread-malware-infection-across-multiple-hosts]]
+=== Potential Widespread Malware Infection Across Multiple Hosts
+
+This rule uses alert data to determine when a malware signature is triggered in multiple hosts. Analysts can use this to prioritize triage and response, as this can potentially indicate a widespread malware infection.
+
+*Rule type*: esql
+
+*Rule indices*: None
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/elastic/protections-artifacts/tree/main/yara/rules
+
+*Tags*: 
+
+* Domain: Endpoint
+* Data Source: Elastic Defend
+* Use Case: Threat Detection
+* Tactic: Execution
+* Rule Type: Higher-Order Rule
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+from logs-endpoint.alerts-*
+| where event.code in ("malicious_file", "memory_signature", "shellcode_thread") and rule.name is not null
+| stats hosts = count_distinct(host.id) by rule.name, event.code
+| where hosts >= 3
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: User Execution
+** ID: T1204
+** Reference URL: https://attack.mitre.org/techniques/T1204/
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-process-injection-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-process-injection-detected-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..a7bd73460e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-process-injection-detected-elastic-endgame.asciidoc
@@ -0,0 +1,72 @@
+[[prebuilt-rule-8-14-1-process-injection-detected-elastic-endgame]]
+=== Process Injection - Detected - Elastic Endgame
+
+Elastic Endgame detected Process Injection. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:kernel_shellcode_event or endgame.event_subtype_full:kernel_shellcode_event)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-process-injection-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-process-injection-prevented-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..e6de731ee2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-process-injection-prevented-elastic-endgame.asciidoc
@@ -0,0 +1,72 @@
+[[prebuilt-rule-8-14-1-process-injection-prevented-elastic-endgame]]
+=== Process Injection - Prevented - Elastic Endgame
+
+Elastic Endgame prevented Process Injection. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:kernel_shellcode_event or endgame.event_subtype_full:kernel_shellcode_event)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-prompt-for-credentials-with-osascript.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-prompt-for-credentials-with-osascript.asciidoc
new file mode 100644
index 0000000000..b31fdecd4c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-prompt-for-credentials-with-osascript.asciidoc
@@ -0,0 +1,111 @@
+[[prebuilt-rule-8-14-1-prompt-for-credentials-with-osascript]]
+=== Prompt for Credentials with OSASCRIPT
+
+Identifies the use of osascript to execute scripts via standard input that may prompt a user with a rogue dialog for credentials.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/EmpireProject/EmPyre/blob/master/lib/modules/collection/osx/prompt.py
+* https://ss64.com/osx/osascript.html
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 207
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.action == "exec" and
+ process.name : "osascript" and process.args : "-e" and process.command_line : ("*osascript*display*dialog*password*", "*osascript*display*dialog*passphrase*") and
+ not (process.parent.executable : "/usr/bin/sudo" and process.command_line : "*Encryption Key Escrow*") and
+ not (process.command_line : "*-e with timeout of 3600 seconds*" and user.id == "0" and process.parent.executable : "/bin/bash") and
+ not process.Ext.effective_parent.executable : ("/usr/local/jamf/*", 
+                                                "/Applications/Karabiner-Elements.app/Contents/MacOS/Karabiner-Elements",
+                                                "/System/Applications/Utilities/Terminal.app/Contents/MacOS/Terminal",
+                                                "/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfDaemon.app/Contents/MacOS/JamfDaemon",
+                                                "/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfManagementService.app/Contents/MacOS/JamfManagementService")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Input Capture
+** ID: T1056
+** Reference URL: https://attack.mitre.org/techniques/T1056/
+* Sub-technique:
+** Name: GUI Input Capture
+** ID: T1056.002
+** Reference URL: https://attack.mitre.org/techniques/T1056/002/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-quarantine-attrib-removed-by-unsigned-or-untrusted-process.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-quarantine-attrib-removed-by-unsigned-or-untrusted-process.asciidoc
new file mode 100644
index 0000000000..58b479f94f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-quarantine-attrib-removed-by-unsigned-or-untrusted-process.asciidoc
@@ -0,0 +1,110 @@
+[[prebuilt-rule-8-14-1-quarantine-attrib-removed-by-unsigned-or-untrusted-process]]
+=== Quarantine Attrib Removed by Unsigned or Untrusted Process
+
+Detects deletion of the quarantine attribute by an unusual process (xattr). In macOS, when applications or programs are downloaded from the internet, there is a quarantine flag set on the file. This attribute is read by Apple's Gatekeeper defense program at execution time. An adversary may disable this attribute to evade defenses.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://nixhacker.com/security-protection-in-macos-1/
+* https://eclecticlight.co/2020/10/29/quarantine-and-the-quarantine-flag/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 108
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where event.action == "extended_attributes_delete" and process.executable != null and
+(process.code_signature.trusted == false or process.code_signature.exists == false) and not
+process.executable : ("/usr/bin/xattr", 
+                      "/System/*", 
+                      "/private/tmp/KSInstallAction.*/*/Install Google Software Update.app/Contents/Helpers/ksinstall",
+                      "/Applications/CEWE Fotoschau.app/Contents/MacOS/FotoPlus",
+                      "/Applications/.com.bomgar.scc.*/Remote Support Customer Client.app/Contents/MacOS/sdcust") and not
+file.path : "/private/var/folders/*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ransomware-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ransomware-detected-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..d63b01eaea
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ransomware-detected-elastic-endgame.asciidoc
@@ -0,0 +1,59 @@
+[[prebuilt-rule-8-14-1-ransomware-detected-elastic-endgame]]
+=== Ransomware - Detected - Elastic Endgame
+
+Elastic Endgame detected ransomware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: critical
+
+*Risk score*: 99
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:ransomware_event or endgame.event_subtype_full:ransomware_event)
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ransomware-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ransomware-prevented-elastic-endgame.asciidoc
new file mode 100644
index 0000000000..592ba5294a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-ransomware-prevented-elastic-endgame.asciidoc
@@ -0,0 +1,59 @@
+[[prebuilt-rule-8-14-1-ransomware-prevented-elastic-endgame]]
+=== Ransomware - Prevented - Elastic Endgame
+
+Elastic Endgame prevented ransomware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 10m
+
+*Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Endgame
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:ransomware_event or endgame.event_subtype_full:ransomware_event)
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-route53-resolver-query-log-configuration-deleted.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-route53-resolver-query-log-configuration-deleted.asciidoc
new file mode 100644
index 0000000000..8463cd3d0d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-route53-resolver-query-log-configuration-deleted.asciidoc
@@ -0,0 +1,123 @@
+[[prebuilt-rule-8-14-1-route53-resolver-query-log-configuration-deleted]]
+=== Route53 Resolver Query Log Configuration Deleted
+
+Identifies when a Route53 Resolver Query Log Configuration is deleted. When a Route53 Resolver query log configuration is deleted, Resolver stops logging DNS queries and responses for the specified configuration. Adversaries may delete query log configurations to evade detection or cover their tracks.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-aws.cloudtrail*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_DeleteResolverQueryLogConfig.html
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: Amazon Route53
+* Use Case: Log Auditing
+* Resources: Investigation Guide
+* Tactic: Defense Evasion
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+*Triage and Analysis*
+
+
+
+*Investigating Route53 Resolver Query Log Configuration Deleted*
+
+
+This rule detects when a Route53 Resolver Query Log Configuration is deleted. Deleting these configurations stops the logging of DNS queries and responses, which can significantly impede network monitoring and compromise security visibility. Adversaries may delete these configurations to evade detection, remove evidence, or obscure their activities within a network.
+
+Adversaries target Route53 Resolver query log configurations because these logs can contain evidence of malicious domain queries or responses. By deleting these logs, an adversary can prevent the capture of information that could reveal unauthorized network activities, aiding in avoiding detection and thwarting incident response efforts.
+
+
+*Possible Investigation Steps*
+
+
+- **Review the Deletion Details**: Examine the CloudTrail logs to identify when and by whom the deletion was initiated.
+    - Check the `event.action` and `user_identity` elements to understand the scope and authorization of the deletion.
+- **Contextualize with User Actions**: Assess whether the deletion aligns with the user’s role and job responsibilities.
+    - Investigate if similar modifications have occurred recently that could suggest a pattern or broader campaign.
+- **Analyze Access Patterns and Permissions**: Verify whether the user had the appropriate permissions to delete log configurations.
+    - Investigate any recent permission changes that might indicate role abuse or credentials compromise.
+- **Correlate with Other Security Incidents**: Look for related security alerts or incidents that could be connected to the log deletion.
+    - This includes unusual network traffic, alerts from other AWS services, or findings from intrusion detection systems.
+- **Interview the Responsible Team**: If the deletion was initiated by an internal team member, confirm their intent and authorization to ensure it was a legitimate action.
+
+
+*False Positive Analysis*
+
+
+- **Legitimate Administrative Actions**: Confirm that the deletion was part of scheduled IT operations or network management activities, possibly linked to maintenance or infrastructure updates. Validate this action against change management records or through interviews with relevant personnel.
+
+
+*Response and Remediation*
+
+
+- **Restore Logs if Feasible**: If the deletion was unauthorized, consider restoring the configuration from backups to ensure continuous visibility into DNS queries.
+- **Review and Tighten Permissions**: Ensure that only authorized personnel have the capability to delete critical configurations.
+    - Adjust AWS IAM policies to reinforce security measures.
+- **Enhance Monitoring of Log Management**: Implement or enhance monitoring rules to detect and alert on unauthorized changes to logging configurations, focusing on critical deletions.
+- **Conduct Comprehensive Security Review**: If the deletion is verified as malicious, initiate a thorough security assessment to identify any further unauthorized changes or ongoing malicious activities.
+
+
+*Additional Information*
+
+
+For detailed instructions on managing Route53 Resolver and securing its configurations, refer to the https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_DeleteResolverQueryLogConfig.html[Amazon Route53 Resolver documentation].
+
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:aws.cloudtrail and event.provider: route53resolver.amazonaws.com
+    and event.action: DeleteResolverQueryLogConfig and event.outcome: success
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Cloud Logs
+** ID: T1562.008
+** Reference URL: https://attack.mitre.org/techniques/T1562/008/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-shell-execution-via-apple-scripting.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-shell-execution-via-apple-scripting.asciidoc
new file mode 100644
index 0000000000..b734f3efa0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-shell-execution-via-apple-scripting.asciidoc
@@ -0,0 +1,101 @@
+[[prebuilt-rule-8-14-1-shell-execution-via-apple-scripting]]
+=== Shell Execution via Apple Scripting
+
+Identifies the execution of the shell process (sh) via scripting (JXA or AppleScript). Adversaries may use the doShellScript functionality in JXA or do shell script in AppleScript to execute system commands.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://developer.apple.com/library/archive/technotes/tn2065/_index.html
+* https://objectivebythesea.com/v2/talks/OBTS_v2_Thomas.pdf
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=5s
+ [process where host.os.type == "macos" and event.type in ("start", "process_started", "info") and process.name == "osascript" and process.args : "-e"] by process.entity_id
+ [process where host.os.type == "macos" and event.type in ("start", "process_started") and process.name : ("sh", "bash", "zsh") and process.args == "-c" and process.args : ("*curl*", "*pbcopy*", "*http*", "*chmod*")] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-browser-child-process.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-browser-child-process.asciidoc
new file mode 100644
index 0000000000..b5cb202524
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-browser-child-process.asciidoc
@@ -0,0 +1,128 @@
+[[prebuilt-rule-8-14-1-suspicious-browser-child-process]]
+=== Suspicious Browser Child Process
+
+Identifies the execution of a suspicious browser child process. Adversaries may gain access to a system through a user visiting a website over the normal course of browsing. With this technique, the user's web browser is typically targeted for exploitation.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://objective-see.com/blog/blog_0x43.html
+* https://fr.slideshare.net/codeblue_jp/cb19-recent-apt-attack-on-crypto-exchange-employees-by-heungsoo-kang
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and
+  process.parent.name : ("Google Chrome", "Google Chrome Helper*", "firefox", "Opera", "Safari", "com.apple.WebKit.WebContent", "Microsoft Edge") and
+  process.name : ("sh", "bash", "dash", "ksh", "tcsh", "zsh", "curl", "wget", "python*", "perl*", "php*", "osascript", "pwsh") and
+  process.command_line != null and
+  not process.command_line : "*/Library/Application Support/Microsoft/MAU*/Microsoft AutoUpdate.app/Contents/MacOS/msupdate*" and
+  not process.args :
+    (
+      "hw.model",
+      "IOPlatformExpertDevice",
+      "/Volumes/Google Chrome/Google Chrome.app/Contents/Frameworks/*/Resources/install.sh",
+      "/Applications/Google Chrome.app/Contents/Frameworks/Google Chrome Framework.framework/Versions/*/Helpers/Google Chrome Helper (Renderer).app/Contents/MacOS/Google Chrome Helper (Renderer)",
+      "/Applications/Firefox.app/Contents/MacOS/plugin-container.app/Contents/MacOS/plugin-container",
+      "--defaults-torrc",
+      "*Chrome.app",
+      "Framework.framework/Versions/*/Resources/keystone_promote_preflight.sh",
+      "/Users/*/Library/Application Support/Google/Chrome/recovery/*/ChromeRecovery",
+      "$DISPLAY",
+      "*GIO_LAUNCHED_DESKTOP_FILE_PID=$$*",
+      "/opt/homebrew/*",
+      "/usr/local/*brew*"
+    )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Exploitation for Client Execution
+** ID: T1203
+** Reference URL: https://attack.mitre.org/techniques/T1203/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Drive-by Compromise
+** ID: T1189
+** Reference URL: https://attack.mitre.org/techniques/T1189/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-file-renamed-via-smb.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-file-renamed-via-smb.asciidoc
new file mode 100644
index 0000000000..22d527c10b
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-file-renamed-via-smb.asciidoc
@@ -0,0 +1,138 @@
+[[prebuilt-rule-8-14-1-suspicious-file-renamed-via-smb]]
+=== Suspicious File Renamed via SMB
+
+Identifies an incoming SMB connection followed by a suspicious file rename operation. This may indicate a remote ransomware attack via the SMB protocol.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://news.sophos.com/en-us/2023/12/21/akira-again-the-ransomware-that-keeps-on-taking/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Performance*
+
+
+- This rule may cause medium to high performance impact due to logic scoping all icoming SMB network events.
+
+
+*Possible investigation steps*
+
+
+- Investigate the source.ip address connecting to port 445 on this host.
+- Identify the user account that performed the file creation via SMB.
+- If the number of files is too high and source.ip connecting over SMB is unusual isolate the host and block the used credentials.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Remote file rename over SMB.
+
+
+*Related rules*
+
+
+- Third-party Backup Files Deleted via Unexpected Process - 11ea6bec-ebde-4d71-a8e9-784948f8e3e9
+- Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
+- Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
+- Volume Shadow Copy Deletion via WMIC - dc9c1f74-dac3-48e3-b47f-eb79db358f57
+- Potential Ransomware Note File Dropped via SMB - 02bab13d-fb14-4d7c-b6fe-4a28874d37c5
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look for ransomware preparation and execution activities.
+- If any backups were affected:
+  - Perform data recovery locally or restore the backups from replicated copies (cloud, other servers, etc.).
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=1s
+ [network where host.os.type == "windows" and
+  event.action == "connection_accepted" and destination.port == 445 and source.port >= 49152 and process.pid == 4 and
+  source.ip != "127.0.0.1" and source.ip != "::1"]
+ [file where host.os.type == "windows" and
+  event.action == "rename" and process.pid == 4 and user.id : ("S-1-5-21*", "S-1-12-*") and
+  file.extension != null and file.Ext.entropy >= 6 and
+  file.Ext.original.name : ("*.jpg", "*.bmp", "*.png", "*.pdf", "*.doc", "*.docx", "*.xls", "*.xlsx", "*.ppt", "*.pptx", "*.lnk") and
+  not file.extension : ("jpg", "bmp", "png", "pdf", "doc", "docx", "xls", "xlsx", "ppt", "pptx", "*.lnk")] with runs=3
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Inhibit System Recovery
+** ID: T1490
+** Reference URL: https://attack.mitre.org/techniques/T1490/
+* Technique:
+** Name: Data Destruction
+** ID: T1485
+** Reference URL: https://attack.mitre.org/techniques/T1485/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-macos-ms-office-child-process.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-macos-ms-office-child-process.asciidoc
new file mode 100644
index 0000000000..21c7b2c363
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-macos-ms-office-child-process.asciidoc
@@ -0,0 +1,168 @@
+[[prebuilt-rule-8-14-1-suspicious-macos-ms-office-child-process]]
+=== Suspicious macOS MS Office Child Process
+
+Identifies suspicious child processes of frequently targeted Microsoft Office applications (Word, PowerPoint, and Excel). These child processes are often launched during exploitation of Office applications or by documents with malicious macros.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.malwarebytes.com/cybercrime/2017/02/microsoft-office-macro-malware-targets-macs/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.action == "exec" and
+    process.parent.name: (
+      "Microsoft Word",
+      "Microsoft Outlook",
+      "Microsoft Excel",
+      "Microsoft PowerPoint",
+      "Microsoft OneNote"
+    ) and
+  process.name : (
+    "curl",
+    "nscurl",
+    "bash",
+    "sh",
+    "osascript",
+    "python*",
+    "perl*",
+    "mktemp",
+    "chmod",
+    "php",
+    "nohup",
+    "openssl",
+    "plutil",
+    "PlistBuddy",
+    "xattr",
+    "mktemp",
+    "sqlite3",
+    "funzip",
+    "popen"
+  ) and
+
+  // Filter FPs related to product version discovery and Office error reporting behavior
+  not process.args:
+    (
+      "ProductVersion",
+      "hw.model",
+      "ioreg",
+      "ProductName",
+      "ProductUserVisibleVersion",
+      "ProductBuildVersion",
+      "/Library/Application Support/Microsoft/MERP*/Microsoft Error Reporting.app/Contents/MacOS/Microsoft Error Reporting",
+      "open -a Safari *",
+      "defaults read *",
+      "sysctl hw.model*",
+      "ioreg -d2 -c IOPlatformExpertDevice *",
+      "ps aux | grep 'ToDesk_Desktop' | grep -v grep",
+      "PIPE=\"$CFFIXED_USER_HOME/.zoteroIntegrationPipe*"
+    ) and
+
+   not process.parent.executable :
+        (
+          "/Applications/ToDesk.app/Contents/MacOS/ToDesk_Service",
+          "/usr/local/Privacy-i/PISupervisor",
+          "/Library/Addigy/lan-cache",
+          "/Library/Elastic/Agent/*",
+          "/opt/jc/bin/jumpcloud-agent",
+          "/usr/sbin/networksetup"
+        ) and
+   not (process.name : "sh" and process.command_line : "*$CFFIXED_USER_HOME/.zoteroIntegrationPipe*") and
+
+   not process.Ext.effective_parent.executable : (
+        "/Applications/ToDesk.app/Contents/MacOS/ToDesk_Service",
+        "/usr/local/Privacy-i/PISupervisor",
+        "/Library/Addigy/auditor",
+        "/Library/Elastic/Agent/*",
+        "/opt/jc/bin/jumpcloud-agent",
+        "/usr/sbin/networksetup"
+      )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-web-browser-sensitive-file-access.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-web-browser-sensitive-file-access.asciidoc
new file mode 100644
index 0000000000..c7ed26cb06
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-suspicious-web-browser-sensitive-file-access.asciidoc
@@ -0,0 +1,115 @@
+[[prebuilt-rule-8-14-1-suspicious-web-browser-sensitive-file-access]]
+=== Suspicious Web Browser Sensitive File Access
+
+Identifies the access or file open of web browser sensitive files by an untrusted/unsigned process or osascript. Adversaries may acquire credentials from web browsers by reading files specific to the target browser.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://securelist.com/calisto-trojan-for-macos/86543/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 207
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where event.action == "open" and process.executable != null and 
+ file.name : ("cookies.sqlite", 
+              "key?.db", 
+              "logins.json", 
+              "Cookies", 
+              "Cookies.binarycookies", 
+              "Login Data") and 
+ ((process.code_signature.trusted == false or process.code_signature.exists == false) or process.name : "osascript") and 
+ not process.code_signature.signing_id : "org.mozilla.firefox" and
+ not process.Ext.effective_parent.executable : "/Library/Elastic/Endpoint/elastic-endpoint.app/Contents/MacOS/elastic-endpoint"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Steal Web Session Cookie
+** ID: T1539
+** Reference URL: https://attack.mitre.org/techniques/T1539/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Sub-technique:
+** Name: Credentials from Web Browsers
+** ID: T1555.003
+** Reference URL: https://attack.mitre.org/techniques/T1555/003/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-systemkey-access-via-command-line.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-systemkey-access-via-command-line.asciidoc
new file mode 100644
index 0000000000..7c985db4c9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-systemkey-access-via-command-line.asciidoc
@@ -0,0 +1,104 @@
+[[prebuilt-rule-8-14-1-systemkey-access-via-command-line]]
+=== SystemKey Access via Command Line
+
+Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features, including Wi-Fi and website passwords, secure notes, certificates, and Kerberos. Adversaries may collect the keychain storage data from a system to acquire credentials.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/AlessandroZ/LaZagne/blob/master/Mac/lazagne/softwares/system/chainbreaker.py
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+  process.args:("/private/var/db/SystemKey" or "/var/db/SystemKey") and
+  not process.Ext.effective_parent.executable : "/Library/Elastic/Endpoint/elastic-endpoint.app/Contents/MacOS/elastic-endpoint"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Sub-technique:
+** Name: Keychain
+** ID: T1555.001
+** Reference URL: https://attack.mitre.org/techniques/T1555/001/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-unusual-execution-via-microsoft-common-console-file.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-unusual-execution-via-microsoft-common-console-file.asciidoc
new file mode 100644
index 0000000000..ae2bc11041
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-unusual-execution-via-microsoft-common-console-file.asciidoc
@@ -0,0 +1,124 @@
+[[prebuilt-rule-8-14-1-unusual-execution-via-microsoft-common-console-file]]
+=== Unusual Execution via Microsoft Common Console File
+
+Identifies the execution of a child process from a Microsoft Common Console file. Adversaries may embed a malicious command in an MSC file in order to trick victims into executing malicious commands.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.genians.co.kr/blog/threat_intelligence/facebook
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Initial Access
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Execution via Microsoft Common Console File*
+
+
+- Investigate the source of the MSC file.
+- Investigate the process execution chain (all spawned child processes and their descendants).
+- Investigate the process and it's descendants network and file events.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+
+
+*Response and remediation*
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.parent.executable : "?:\\Windows\\System32\\mmc.exe" and endswith~(process.parent.args, ".msc") and
+ not process.parent.args : ("?:\\Windows\\System32\\*.msc", "?:\\Windows\\SysWOW64\\*.msc", "?:\\Program files\\*.msc", "?:\\Program Files (x86)\\*.msc")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: User Execution
+** ID: T1204
+** Reference URL: https://attack.mitre.org/techniques/T1204/
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-webproxy-settings-modification.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-webproxy-settings-modification.asciidoc
new file mode 100644
index 0000000000..95a18b3bcb
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rule-8-14-1-webproxy-settings-modification.asciidoc
@@ -0,0 +1,104 @@
+[[prebuilt-rule-8-14-1-webproxy-settings-modification]]
+=== WebProxy Settings Modification
+
+Identifies the use of the built-in networksetup command to configure webproxy settings. This may indicate an attempt to hijack web browser traffic for credential access via traffic sniffing or redirection.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://unit42.paloaltonetworks.com/mac-malware-steals-cryptocurrency-exchanges-cookies/
+* https://objectivebythesea.com/v2/talks/OBTS_v2_Zohar.pdf
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:macos and event.type:start and
+ process.name : networksetup and process.args : (("-setwebproxy" or "-setsecurewebproxy" or "-setautoproxyurl") and not (Bluetooth or off)) and
+ not process.parent.executable : ("/Library/PrivilegedHelperTools/com.80pct.FreedomHelper" or
+                                  "/Applications/Fiddler Everywhere.app/Contents/Resources/app/out/WebServer/Fiddler.WebUi" or
+                                  "/usr/libexec/xpcproxy") and
+ not process.Ext.effective_parent.executable : ("/Applications/Proxyman.app/Contents/MacOS/Proxyman" or "/Applications/Incoggo.app/Contents/MacOS/Incoggo.app")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Steal Web Session Cookie
+** ID: T1539
+** Reference URL: https://attack.mitre.org/techniques/T1539/
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rules-8-14-1-appendix.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rules-8-14-1-appendix.asciidoc
new file mode 100644
index 0000000000..308f72d142
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rules-8-14-1-appendix.asciidoc
@@ -0,0 +1,57 @@
+["appendix",role="exclude",id="prebuilt-rule-8-14-1-prebuilt-rules-8-14-1-appendix"]
+= Downloadable rule update v8.14.1
+
+This section lists all updates associated with version 8.14.1 of the Fleet integration *Prebuilt Security Detection Rules*.
+
+
+include::prebuilt-rule-8-14-1-potential-widespread-malware-infection-across-multiple-hosts.asciidoc[]
+include::prebuilt-rule-8-14-1-aws-ec2-admin-credential-fetch-via-assumed-role.asciidoc[]
+include::prebuilt-rule-8-14-1-route53-resolver-query-log-configuration-deleted.asciidoc[]
+include::prebuilt-rule-8-14-1-ec2-ami-shared-with-another-account.asciidoc[]
+include::prebuilt-rule-8-14-1-potential-file-download-via-a-headless-browser.asciidoc[]
+include::prebuilt-rule-8-14-1-alternate-data-stream-creation-execution-at-volume-root-directory.asciidoc[]
+include::prebuilt-rule-8-14-1-unusual-execution-via-microsoft-common-console-file.asciidoc[]
+include::prebuilt-rule-8-14-1-potential-powershell-hacktool-script-by-author.asciidoc[]
+include::prebuilt-rule-8-14-1-potential-ransomware-behavior-high-count-of-readme-files-by-system.asciidoc[]
+include::prebuilt-rule-8-14-1-suspicious-file-renamed-via-smb.asciidoc[]
+include::prebuilt-rule-8-14-1-potential-ransomware-note-file-dropped-via-smb.asciidoc[]
+include::prebuilt-rule-8-14-1-container-workload-protection.asciidoc[]
+include::prebuilt-rule-8-14-1-endpoint-security.asciidoc[]
+include::prebuilt-rule-8-14-1-access-to-keychain-credentials-directories.asciidoc[]
+include::prebuilt-rule-8-14-1-keychain-password-retrieval-via-command-line.asciidoc[]
+include::prebuilt-rule-8-14-1-webproxy-settings-modification.asciidoc[]
+include::prebuilt-rule-8-14-1-prompt-for-credentials-with-osascript.asciidoc[]
+include::prebuilt-rule-8-14-1-suspicious-web-browser-sensitive-file-access.asciidoc[]
+include::prebuilt-rule-8-14-1-systemkey-access-via-command-line.asciidoc[]
+include::prebuilt-rule-8-14-1-quarantine-attrib-removed-by-unsigned-or-untrusted-process.asciidoc[]
+include::prebuilt-rule-8-14-1-modification-of-environment-variable-via-unsigned-or-untrusted-parent.asciidoc[]
+include::prebuilt-rule-8-14-1-enumeration-of-users-or-groups-via-built-in-commands.asciidoc[]
+include::prebuilt-rule-8-14-1-suspicious-browser-child-process.asciidoc[]
+include::prebuilt-rule-8-14-1-macos-installer-package-spawns-network-event.asciidoc[]
+include::prebuilt-rule-8-14-1-shell-execution-via-apple-scripting.asciidoc[]
+include::prebuilt-rule-8-14-1-suspicious-macos-ms-office-child-process.asciidoc[]
+include::prebuilt-rule-8-14-1-authorization-plugin-modification.asciidoc[]
+include::prebuilt-rule-8-14-1-persistence-via-docker-shortcut-modification.asciidoc[]
+include::prebuilt-rule-8-14-1-finder-sync-plugin-registered-and-enabled.asciidoc[]
+include::prebuilt-rule-8-14-1-persistence-via-folder-action-script.asciidoc[]
+include::prebuilt-rule-8-14-1-potential-persistence-via-login-hook.asciidoc[]
+include::prebuilt-rule-8-14-1-apple-scripting-execution-with-administrator-privileges.asciidoc[]
+include::prebuilt-rule-8-14-1-potential-admin-group-account-addition.asciidoc[]
+include::prebuilt-rule-8-14-1-credential-dumping-detected-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-credential-dumping-prevented-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-adversary-behavior-detected-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-malware-detected-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-malware-prevented-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-ransomware-detected-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-ransomware-prevented-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-exploit-detected-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-exploit-prevented-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-external-alerts.asciidoc[]
+include::prebuilt-rule-8-14-1-credential-manipulation-detected-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-credential-manipulation-prevented-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-permission-theft-detected-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-permission-theft-prevented-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-process-injection-detected-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-process-injection-prevented-elastic-endgame.asciidoc[]
+include::prebuilt-rule-8-14-1-connection-to-commonly-abused-web-services.asciidoc[]
+include::prebuilt-rule-8-14-1-component-object-model-hijacking.asciidoc[]
diff --git a/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rules-8-14-1-summary.asciidoc b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rules-8-14-1-summary.asciidoc
new file mode 100644
index 0000000000..c7ded1cf95
--- /dev/null
+++ b/docs/detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rules-8-14-1-summary.asciidoc
@@ -0,0 +1,114 @@
+[[prebuilt-rule-8-14-1-prebuilt-rules-8-14-1-summary]]
+[role="xpack"]
+== Update v8.14.1
+
+This section lists all updates associated with version 8.14.1 of the Fleet integration *Prebuilt Security Detection Rules*.
+
+
+[width="100%",options="header"]
+|==============================================
+|Rule |Description |Status |Version
+
+|<<prebuilt-rule-8-14-1-potential-widespread-malware-infection-across-multiple-hosts, Potential Widespread Malware Infection Across Multiple Hosts>> | This rule uses alert data to determine when a malware signature is triggered in multiple hosts. Analysts can use this to prioritize triage and response, as this can potentially indicate a widespread malware infection. | new | 1 
+
+|<<prebuilt-rule-8-14-1-aws-ec2-admin-credential-fetch-via-assumed-role, AWS EC2 Admin Credential Fetch via Assumed Role>> | Identifies the first occurrence of a user identity in AWS using `GetPassword` for the administrator password of an EC2 instance with an assumed role. Adversaries may use this API call to escalate privileges or move laterally within EC2 instances. | new | 2 
+
+|<<prebuilt-rule-8-14-1-route53-resolver-query-log-configuration-deleted, Route53 Resolver Query Log Configuration Deleted>> | Identifies when a Route53 Resolver Query Log Configuration is deleted. When a Route53 Resolver query log configuration is deleted, Resolver stops logging DNS queries and responses for the specified configuration. Adversaries may delete query log configurations to evade detection or cover their tracks. | new | 1 
+
+|<<prebuilt-rule-8-14-1-ec2-ami-shared-with-another-account, EC2 AMI Shared with Another Account>> | Identifies an AWS Amazon Machine Image (AMI) being shared with another AWS account. Adversaries with access may share an AMI with an external AWS account as a means of data exfiltration. AMIs can contain secrets, bash histories, code artifacts, and other sensitive data that adversaries may abuse if shared with unauthorized accounts. AMIs can be made publicly available accidentally as well. | new | 1 
+
+|<<prebuilt-rule-8-14-1-potential-file-download-via-a-headless-browser, Potential File Download via a Headless Browser>> | Identifies the use of a browser to download a file from a remote URL and from a suspicious parent process. Adversaries may use browsers to avoid ingress tool transfer restrictions. | new | 1 
+
+|<<prebuilt-rule-8-14-1-alternate-data-stream-creation-execution-at-volume-root-directory, Alternate Data Stream Creation/Execution at Volume Root Directory>> | Identifies the creation of an Alternate Data Stream (ADS) at a volume root directory, which can indicate the attempt to hide tools and malware, as ADSs created in this directory are not displayed by system utilities. | new | 1 
+
+|<<prebuilt-rule-8-14-1-unusual-execution-via-microsoft-common-console-file, Unusual Execution via Microsoft Common Console File>> | Identifies the execution of a child process from a Microsoft Common Console file. Adversaries may embed a malicious command in an MSC file in order to trick victims into executing malicious commands. | new | 1 
+
+|<<prebuilt-rule-8-14-1-potential-powershell-hacktool-script-by-author, Potential PowerShell HackTool Script by Author>> | Detects known PowerShell offensive tooling author's name in PowerShell scripts. Attackers commonly use out-of-the-box offensive tools without modifying the code, which may still contain the author artifacts. This rule identifies common author handles found in popular PowerShell scripts used for red team exercises. | new | 1 
+
+|<<prebuilt-rule-8-14-1-potential-ransomware-behavior-high-count-of-readme-files-by-system, Potential Ransomware Behavior - High count of Readme files by System>> | This rule identifies a high number (20) of file creation event by the System virtual process from the same host and with same file name containing keywords similar to ransomware note files and all within a short time period. | new | 1 
+
+|<<prebuilt-rule-8-14-1-suspicious-file-renamed-via-smb, Suspicious File Renamed via SMB>> | Identifies an incoming SMB connection followed by a suspicious file rename operation. This may indicate a remote ransomware attack via the SMB protocol. | new | 1 
+
+|<<prebuilt-rule-8-14-1-potential-ransomware-note-file-dropped-via-smb, Potential Ransomware Note File Dropped via SMB>> | Identifies an incoming SMB connection followed by the creation of a file with a name similar to ransomware note files. This may indicate a remote ransomware attack via the SMB protocol. | new | 1 
+
+|<<prebuilt-rule-8-14-1-container-workload-protection, Container Workload Protection>> | Generates a detection alert each time a 'Container Workload Protection' alert is received. Enabling this rule allows you to immediately begin triaging and investigating these alerts. | update | 4 
+
+|<<prebuilt-rule-8-14-1-endpoint-security, Endpoint Security>> | Generates a detection alert each time an Elastic Endpoint Security alert is received. Enabling this rule allows you to immediately begin investigating your Endpoint alerts. | update | 103 
+
+|<<prebuilt-rule-8-14-1-access-to-keychain-credentials-directories, Access to Keychain Credentials Directories>> | Adversaries may collect the keychain storage data from a system to acquire credentials. Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features such as WiFi passwords, websites, secure notes and certificates. | update | 207 
+
+|<<prebuilt-rule-8-14-1-keychain-password-retrieval-via-command-line, Keychain Password Retrieval via Command Line>> | Adversaries may collect keychain storage data from a system to in order to acquire credentials. Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features, including Wi-Fi and website passwords, secure notes, certificates, and Kerberos. | update | 108 
+
+|<<prebuilt-rule-8-14-1-webproxy-settings-modification, WebProxy Settings Modification>> | Identifies the use of the built-in networksetup command to configure webproxy settings. This may indicate an attempt to hijack web browser traffic for credential access via traffic sniffing or redirection. | update | 206 
+
+|<<prebuilt-rule-8-14-1-prompt-for-credentials-with-osascript, Prompt for Credentials with OSASCRIPT>> | Identifies the use of osascript to execute scripts via standard input that may prompt a user with a rogue dialog for credentials. | update | 207 
+
+|<<prebuilt-rule-8-14-1-suspicious-web-browser-sensitive-file-access, Suspicious Web Browser Sensitive File Access>> | Identifies the access or file open of web browser sensitive files by an untrusted/unsigned process or osascript. Adversaries may acquire credentials from web browsers by reading files specific to the target browser. | update | 207 
+
+|<<prebuilt-rule-8-14-1-systemkey-access-via-command-line, SystemKey Access via Command Line>> | Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features, including Wi-Fi and website passwords, secure notes, certificates, and Kerberos. Adversaries may collect the keychain storage data from a system to acquire credentials. | update | 206 
+
+|<<prebuilt-rule-8-14-1-quarantine-attrib-removed-by-unsigned-or-untrusted-process, Quarantine Attrib Removed by Unsigned or Untrusted Process>> | Detects deletion of the quarantine attribute by an unusual process (xattr). In macOS, when applications or programs are downloaded from the internet, there is a quarantine flag set on the file. This attribute is read by Apple's Gatekeeper defense program at execution time. An adversary may disable this attribute to evade defenses. | update | 108 
+
+|<<prebuilt-rule-8-14-1-modification-of-environment-variable-via-unsigned-or-untrusted-parent, Modification of Environment Variable via Unsigned or Untrusted Parent>> | Identifies modifications to an environment variable using the built-in launchctl command. Adversaries may execute their own malicious payloads by hijacking certain environment variables to load arbitrary libraries or bypass certain restrictions. | update | 206 
+
+|<<prebuilt-rule-8-14-1-enumeration-of-users-or-groups-via-built-in-commands, Enumeration of Users or Groups via Built-in Commands>> | Identifies the execution of macOS built-in commands related to account or group enumeration. Adversaries may use account and group information to orient themselves before deciding how to act. | update | 207 
+
+|<<prebuilt-rule-8-14-1-suspicious-browser-child-process, Suspicious Browser Child Process>> | Identifies the execution of a suspicious browser child process. Adversaries may gain access to a system through a user visiting a website over the normal course of browsing. With this technique, the user's web browser is typically targeted for exploitation. | update | 107 
+
+|<<prebuilt-rule-8-14-1-macos-installer-package-spawns-network-event, MacOS Installer Package Spawns Network Event>> | Detects the execution of a MacOS installer package with an abnormal child process (e.g bash) followed immediately by a network connection via a suspicious process (e.g curl). Threat actors will build and distribute malicious MacOS installer packages, which have a .pkg extension, many times imitating valid software in order to persuade and infect their victims often using the package files (e.g pre/post install scripts etc.) to download additional tools or malicious software. If this rule fires it should indicate the installation of a malicious or suspicious package. | update | 107 
+
+|<<prebuilt-rule-8-14-1-shell-execution-via-apple-scripting, Shell Execution via Apple Scripting>> | Identifies the execution of the shell process (sh) via scripting (JXA or AppleScript). Adversaries may use the doShellScript functionality in JXA or do shell script in AppleScript to execute system commands. | update | 107 
+
+|<<prebuilt-rule-8-14-1-suspicious-macos-ms-office-child-process, Suspicious macOS MS Office Child Process>> | Identifies suspicious child processes of frequently targeted Microsoft Office applications (Word, PowerPoint, and Excel). These child processes are often launched during exploitation of Office applications or by documents with malicious macros. | update | 206 
+
+|<<prebuilt-rule-8-14-1-authorization-plugin-modification, Authorization Plugin Modification>> | Authorization plugins are used to extend the authorization services API and implement mechanisms that are not natively supported by the OS, such as multi-factor authentication with third party software. Adversaries may abuse this feature to persist and/or collect clear text credentials as they traverse the registered plugins during user logon. | update | 107 
+
+|<<prebuilt-rule-8-14-1-persistence-via-docker-shortcut-modification, Persistence via Docker Shortcut Modification>> | An adversary can establish persistence by modifying an existing macOS dock property list in order to execute a malicious application instead of the intended one when invoked. | update | 107 
+
+|<<prebuilt-rule-8-14-1-finder-sync-plugin-registered-and-enabled, Finder Sync Plugin Registered and Enabled>> | Finder Sync plugins enable users to extend Finder’s functionality by modifying the user interface. Adversaries may abuse this feature by adding a rogue Finder Plugin to repeatedly execute malicious payloads for persistence. | update | 206 
+
+|<<prebuilt-rule-8-14-1-persistence-via-folder-action-script, Persistence via Folder Action Script>> | Detects modification of a Folder Action script. A Folder Action script is executed when the folder to which it is attached has items added or removed, or when its window is opened, closed, moved, or resized. Adversaries may abuse this feature to establish persistence by utilizing a malicious script. | update | 107 
+
+|<<prebuilt-rule-8-14-1-potential-persistence-via-login-hook, Potential Persistence via Login Hook>> | Identifies the creation or modification of the login window property list (plist). Adversaries may modify plist files to run a program during system boot or user login for persistence. | update | 108 
+
+|<<prebuilt-rule-8-14-1-apple-scripting-execution-with-administrator-privileges, Apple Scripting Execution with Administrator Privileges>> | Identifies execution of the Apple script interpreter (osascript) without a password prompt and with administrator privileges. | update | 207 
+
+|<<prebuilt-rule-8-14-1-potential-admin-group-account-addition, Potential Admin Group Account Addition>> | Identifies attempts to add an account to the admin group via the command line. This could be an indication of privilege escalation activity. | update | 206 
+
+|<<prebuilt-rule-8-14-1-credential-dumping-detected-elastic-endgame, Credential Dumping - Detected - Elastic Endgame>> | Elastic Endgame detected Credential Dumping. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-credential-dumping-prevented-elastic-endgame, Credential Dumping - Prevented - Elastic Endgame>> | Elastic Endgame prevented Credential Dumping. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-adversary-behavior-detected-elastic-endgame, Adversary Behavior - Detected - Elastic Endgame>> | Elastic Endgame detected an Adversary Behavior. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 104 
+
+|<<prebuilt-rule-8-14-1-malware-detected-elastic-endgame, Malware - Detected - Elastic Endgame>> | Elastic Endgame detected Malware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-malware-prevented-elastic-endgame, Malware - Prevented - Elastic Endgame>> | Elastic Endgame prevented Malware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-ransomware-detected-elastic-endgame, Ransomware - Detected - Elastic Endgame>> | Elastic Endgame detected ransomware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-ransomware-prevented-elastic-endgame, Ransomware - Prevented - Elastic Endgame>> | Elastic Endgame prevented ransomware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-exploit-detected-elastic-endgame, Exploit - Detected - Elastic Endgame>> | Elastic Endgame detected an Exploit. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-exploit-prevented-elastic-endgame, Exploit - Prevented - Elastic Endgame>> | Elastic Endgame prevented an Exploit. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-external-alerts, External Alerts>> | Generates a detection alert for each external alert written to the configured indices. Enabling this rule allows you to immediately begin investigating external alerts in the app. | update | 103 
+
+|<<prebuilt-rule-8-14-1-credential-manipulation-detected-elastic-endgame, Credential Manipulation - Detected - Elastic Endgame>> | Elastic Endgame detected Credential Manipulation. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-credential-manipulation-prevented-elastic-endgame, Credential Manipulation - Prevented - Elastic Endgame>> | Elastic Endgame prevented Credential Manipulation. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-permission-theft-detected-elastic-endgame, Permission Theft - Detected - Elastic Endgame>> | Elastic Endgame detected Permission Theft. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-permission-theft-prevented-elastic-endgame, Permission Theft - Prevented - Elastic Endgame>> | Elastic Endgame prevented Permission Theft. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-process-injection-detected-elastic-endgame, Process Injection - Detected - Elastic Endgame>> | Elastic Endgame detected Process Injection. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-process-injection-prevented-elastic-endgame, Process Injection - Prevented - Elastic Endgame>> | Elastic Endgame prevented Process Injection. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. | update | 103 
+
+|<<prebuilt-rule-8-14-1-connection-to-commonly-abused-web-services, Connection to Commonly Abused Web Services>> | Adversaries may implement command and control (C2) communications that use common web services to hide their activity. This attack technique is typically targeted at an organization and uses web services common to the victim network, which allows the adversary to blend into legitimate traffic activity. These popular services are typically targeted since they have most likely been used before compromise, which helps malicious traffic blend in. | update | 113 
+
+|<<prebuilt-rule-8-14-1-component-object-model-hijacking, Component Object Model Hijacking>> | Identifies Component Object Model (COM) hijacking via registry modification. Adversaries may establish persistence by executing malicious content triggered by hijacked references to COM objects. | update | 113 
+
+|==============================================
diff --git a/docs/detections/prebuilt-rules/prebuilt-rules-downloadable-updates.asciidoc b/docs/detections/prebuilt-rules/prebuilt-rules-downloadable-updates.asciidoc
index c285889192..2386d50389 100644
--- a/docs/detections/prebuilt-rules/prebuilt-rules-downloadable-updates.asciidoc
+++ b/docs/detections/prebuilt-rules/prebuilt-rules-downloadable-updates.asciidoc
@@ -1,139 +1 @@
-[[prebuilt-rules-downloadable-updates]]
-[role="xpack"]
-== Downloadable rule updates
-
-This section lists all updates to prebuilt detection rules, made available with the *Prebuilt Security Detection Rules* integration in Fleet.
-
-To update your installed rules to the latest versions, follow the instructions in <<update-prebuilt-rules>>.
-
-
-[width="100%",options="header"]
-|==============================================
-|Update version |Date | New rules | Updated rules | Notes
-
-|<<prebuilt-rule-8-7-1-prebuilt-rules-8-7-1-summary, 8.7.1>> | 15 Feb 2023 | 29 | 110 |
-This release includes new rules for Windows and Linux endpoints.
-Additionally, significant rule tuning for Windows and Linux rules has been added for better rule efficacy.
-A Google Workspace promotional rule was added to promote security alerts from the Alert Center.
-Machine learning rules related to failed logins have been adjusted for better scoring results.
-Additional investigation guides have been added for Windows and Linux rules.
-A https://www.elastic.co/guide/en/security/current/rules-ui-create.html[New Terms] rule has been created to identify loaded Windows drivers not seen in the last 30 days.
-A guided onboarding rule has been created to assist new SIEM users with getting started.
-
-|<<prebuilt-rule-8-6-1-prebuilt-rules-8-6-1-summary, 8.6.1>> | 15 Feb 2023 | 28 | 110 |
-This release includes new rules for Windows and Linux endpoints.
-Additionally, significant rule tuning for Windows and Linux rules has been added for better rule efficacy.
-A Google Workspace promotional rule was added to promote security alerts from the Alert Center.
-Machine learning rules related to failed logins have been adjusted for better scoring results.
-Additional investigation guides have been added for Windows and Linux rules.
-A https://www.elastic.co/guide/en/security/current/rules-ui-create.html[New Terms] rule has been created to identify loaded Windows drivers not seen in the last 30 days.
-
-|<<prebuilt-rule-8-5-1-prebuilt-rules-8-5-1-summary, 8.5.1>> | 14 Feb 2023 | 27 | 110 |
-This release includes new rules for Windows and Linux endpoints.
-Additionally, significant rule tuning for Windows and Linux rules has been added for better rule efficacy.
-A Google Workspace promotional rule was added to promote security alerts from the Alert Center.
-Machine learning rules related to failed logins have been adjusted for better scoring results.
-Additional investigation guides have been added for Windows and Linux rules.
-
-|<<prebuilt-rule-8-4-3-prebuilt-rules-8-4-3-summary, 8.4.3>> | 14 Feb 2023 | 27 | 110 |
-This release includes new rules for Windows and Linux endpoints.
-Additionally, significant rule tuning for Windows and Linux rules has been added for better rule efficacy.
-A Google Workspace promotional rule was added to promote security alerts from the Alert Center.
-Machine learning rules related to failed logins have been adjusted for better scoring results.
-Additional investigation guides have been added for Windows and Linux rules.
-
-|<<prebuilt-rule-8-4-2-prebuilt-rules-8-4-2-summary, 8.4.2>> | 24 Jan 2023 | 5 | 494 |
-This release includes new rules for Windows regarding Microsoft Exchange interaction via Powershell.
-Additionally, significant rule tuning for Windows rules has been added for better rule efficacy.
-A new rule for multiple alerts with different ATT&CK tactics on a single host has also been included.
-A new rule for multiple alerts involving a single user has been added.
-Related integration tags and recommended versions have been added to endpoint rules.
-Bug fixes for OSQuery execution in rule investigation guides has been added.
-
-|<<prebuilt-rule-8-3-4-prebuilt-rules-8-3-4-summary, 8.3.4>> | 24 Jan 2023 | 1 | 4 |
-This release includes new rules for Windows regarding Microsoft Exchange interaction via PowerShell.
-A new rule for multiple alerts with different ATT&CK tactics on a single host has also been included.
-Additionally, a new rule for multiple alerts involving a single user has been added.
-This release also includes rule tuning for suspicious Windows Error Reporting child processes.
-
-|<<prebuilt-rule-8-3-3-prebuilt-rules-8-3-3-summary, 8.3.3>> | 19 Jan 2023 | 17 | 500 |
-This release includes new rules for Windows regarding Microsoft Exchange interaction via PowerShell.
-Additionally, significant rule tuning for Windows rules has been added for better rule efficacy.
-Related integration tags and recommended versions have been added to endpoint rules.
-Bug fixes for OSQuery execution in rule investigation guides has been added.
-
-|<<prebuilt-rule-8-4-1-prebuilt-rules-8-4-1-summary, 8.4.1>> | 05 Dec 2022 | 20 | 298 |
-This release includes new rules for Linux regarding reverse shells.
-Additionally, new windows rules have been added to supply coverage for credential access and access token manipulation.
-Specific Windows and Linux rules have been tuned to reduce false-positive signals.
-
-|<<prebuilt-rule-8-3-2-prebuilt-rules-8-3-2-summary, 8.3.2>> | 06 Oct 2022 | 25 | 232 |
-This release includes new rules for Linux, Windows, Google Workspace and Kubernetes.
-Also included are expanded investigation guides for Linux, Windows and macOS rules.
-
-|<<prebuilt-rule-8-3-1-prebuilt-rules-8-3-1-summary, 8.3.1>> | 26 Aug 2022 | 0 | 113 |
-This release includes new rules for Linux, Windows, Google Workspace and Kubernetes.
-Also included are expanded investigation and setup guides for Linux, Windows and macOS rules.
-Rule compatability for required event fields and related Fleet integrations has also been included.
-
-|<<prebuilt-rule-8-2-1-prebuilt-rules-8-2-1-summary, 8.2.1>> | 24 Aug 2022 | 442 | 96 |
-This release includes new rules for Windows, MacOS, Linux, Kubernetes, and considerable tuning efforts.
-Also included are expanded investion guides for Windows, Azure and AWS rules.
-
-|<<prebuilt-rule-8-1-1-prebuilt-rules-8-1-1-summary, 8.1.1>> | 24 Jun 2022 | 14 | 159 |
-This release includes new rules for Windows, MacOS, Linux and Kubernetes.
-Also included are expanded investigation guides for Windows rules.
-Additionally, this update includes new rules to help detect emerging threat https://www.elastic.co/blog/a-peek-behind-the-bpfdoor[BPFDoor].
-Updates to existing Windows rules were made to help detect exploitation attempts against https://www.elastic.co/blog/vulnerability-summary-follina[CVE-2022-30190].
-
-|<<prebuilt-rule-1-0-2-prebuilt-rules-1-0-2-summary, 1.0.2>> | 03 May 2022 | 42 | 341 |
-This release includes new rules for MacOS regarding initial access and persistence coverage.
-New rules to detect shell evasion in Linux have also been added.
-Also included are expanded investigation guides for Windows rules as well as new rules for credential theft and Active Directory (AD).
-Additionally, this update includes new rules to help detect the emerging threat https://www.elastic.co/blog/detecting-and-responding-to-dirty-pipe-with-elastic[CVE-2022-0847 (Dirty Pipe)]
-
-|<<prebuilt-rule-0-14-3-prebuilt-rules-0-14-3-summary, 0.14.3>> | 13 Dec 2021 | 35 | 45 |
-This release includes an update to an existing rule and adds a new rule to help detect https://www.elastic.co/blog/detecting-log4j2-with-elastic-security[CVE-2021-44228 (log4j2)].
-Also included are updates and new rules for cloud integrations, windows, PowerShell, and others.
-
-|<<prebuilt-rule-0-14-2-prebuilt-rules-0-14-2-summary, 0.14.2>> | 15 Oct 2021 | 18 | 89 |
-This release includes rules covering Windows endpoints, as well as several third-party integrations — including rules contributed by the community.
-
-|<<prebuilt-rule-0-14-1-prebuilt-rules-0-14-1-summary, 0.14.1>> | 08 Sep 2021 | 3 | 71 |
-Included in this release is a rule to detect web shells, including
-https://discuss.elastic.co/t/detection-and-response-for-proxyshell-activity/282407[ProxyShell] activity.
-
-|<<prebuilt-rule-0-13-3-prebuilt-rules-0-13-3-summary, 0.13.3>> | 22 Jul 2021 | 4 | 36 |
-Included in this release is a rule for Windows Defender Exclusions, which has been used in recent campaigns, as well as
-a rule to resiliently detect parent PID spoofing.
-
-|<<prebuilt-rule-0-13-2-prebuilt-rules-0-13-2-summary, 0.13.2>> | 07 Jul 2021 | 15 | 6 |
-Included in this release are 3 new rules for the recently observed
-https://www.elastic.co/blog/elastic-security-prevents-100-percent-of-revil-ransomware-samples[REvil]
-activity as well as 4 new rules covering the recent
-https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-34527[PrintNightmare] vulnerability.
-
-|<<prebuilt-rule-0-13-1-prebuilt-rules-0-13-1-summary, 0.13.1>> | 21 Jun 2021 | 4 | 41 |
-
-|==============================================
-
-
-include::downloadable-packages/0-13-1/prebuilt-rules-0-13-1-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/0-13-2/prebuilt-rules-0-13-2-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/0-13-3/prebuilt-rules-0-13-3-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/0-14-1/prebuilt-rules-0-14-1-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/0-14-2/prebuilt-rules-0-14-2-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/0-14-3/prebuilt-rules-0-14-3-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/1-0-2/prebuilt-rules-1-0-2-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-1-1/prebuilt-rules-8-1-1-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-2-1/prebuilt-rules-8-2-1-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-3-1/prebuilt-rules-8-3-1-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-3-2/prebuilt-rules-8-3-2-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-3-3/prebuilt-rules-8-3-3-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-3-4/prebuilt-rules-8-3-4-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-4-1/prebuilt-rules-8-4-1-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-4-2/prebuilt-rules-8-4-2-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-4-3/prebuilt-rules-8-4-3-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-5-1/prebuilt-rules-8-5-1-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-6-1/prebuilt-rules-8-6-1-summary.asciidoc[leveloffset=+1]
-include::downloadable-packages/8-7-1/prebuilt-rules-8-7-1-summary.asciidoc[leveloffset=+1]
+include::downloadable-packages/8-14-1/prebuilt-rules-8-14-1-summary.asciidoc[leveloffset=+1]
diff --git a/docs/detections/prebuilt-rules/prebuilt-rules-reference.asciidoc b/docs/detections/prebuilt-rules/prebuilt-rules-reference.asciidoc
index 980b406671..c6439db7d9 100644
--- a/docs/detections/prebuilt-rules/prebuilt-rules-reference.asciidoc
+++ b/docs/detections/prebuilt-rules/prebuilt-rules-reference.asciidoc
@@ -14,1450 +14,2230 @@ and their rule type is `machine_learning`.
 |Rule |Description |Tags |Added |Version
 
 
-|<<a-scheduled-task-was-created, A scheduled task was created>> |Indicates the creation of a scheduled task using Windows event logs. Adversaries can use these to establish persistence, move laterally, and/or escalate privileges. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |8.5.0 |2 <<a-scheduled-task-was-created-history, Version history>>
+|<<a-scheduled-task-was-created, A scheduled task was created>> |Indicates the creation of a scheduled task using Windows event logs. Adversaries can use these to establish persistence, move laterally, and/or escalate privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence] |8.3.0 |8
 
-|<<a-scheduled-task-was-updated, A scheduled task was updated>> |Indicates the update of a scheduled task using Windows event logs. Adversaries can use these to establish persistence, by changing the configuration of a legit scheduled task. Some changes such as disabling or enabling a scheduled task are common and may may generate noise. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |8.5.0 |2 <<a-scheduled-task-was-updated-history, Version history>>
+|<<a-scheduled-task-was-updated, A scheduled task was updated>> |Indicates the update of a scheduled task using Windows event logs. Adversaries can use these to establish persistence, by changing the configuration of a legit scheduled task. Some changes such as disabling or enabling a scheduled task are common and may may generate noise. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence] |8.3.0 |8
 
-|<<aws-access-secret-in-secrets-manager, AWS Access Secret in Secrets Manager>> |An adversary may attempt to access the secrets in secrets manager to steal certificates, credentials, or other sensitive material |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Data Protection] [Credential Access] [Investigation Guide]  |7.9.0 |103 <<aws-access-secret-in-secrets-manager-history, Version history>>
+|<<aws-bedrock-detected-multiple-attempts-to-use-denied-models-by-a-single-user, AWS Bedrock Detected Multiple Attempts to use Denied Models by a Single User>> |Identifies multiple successive failed attempts to use denied model resources within AWS Bedrock. This could indicated attempts to bypass limitations of other approved models, or to force an impact on the environment by incurring exhorbitant costs. |[Domain: LLM], [Data Source: AWS Bedrock], [Data Source: AWS S3], [Resources: Investigation Guide], [Use Case: Policy Violation], [Mitre Atlas: T0015], [Mitre Atlas: T0034] |8.13.0 |1
 
-|<<aws-cloudtrail-log-created, AWS CloudTrail Log Created>> |Identifies the creation of an AWS log trail that specifies the settings for delivery of log data. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.9.0 |101 <<aws-cloudtrail-log-created-history, Version history>>
+|<<aws-bedrock-guardrails-detected-multiple-policy-violations-within-a-single-blocked-request, AWS Bedrock Guardrails Detected Multiple Policy Violations Within a Single Blocked Request>> |Identifies multiple violations of AWS Bedrock guardrails within a single request, resulting in a block action, increasing the likelihood of malicious intent. Multiple violations implies that a user may be intentionally attempting to cirvumvent security controls, access sensitive information, or possibly exploit a vulnerability in the system. |[Domain: LLM], [Data Source: AWS Bedrock], [Data Source: AWS S3], [Resources: Investigation Guide], [Use Case: Policy Violation], [Mitre Atlas: T0051], [Mitre Atlas: T0054] |8.13.0 |1
 
-|<<aws-cloudtrail-log-deleted, AWS CloudTrail Log Deleted>> |Identifies the deletion of an AWS log trail. An adversary may delete trails in an attempt to evade defenses. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Log Auditing] [Investigation Guide]  |7.9.0 |103 <<aws-cloudtrail-log-deleted-history, Version history>>
+|<<aws-bedrock-guardrails-detected-multiple-violations-by-a-single-user-over-a-session, AWS Bedrock Guardrails Detected Multiple Violations by a Single User Over a Session>> |Identifies multiple violations of AWS Bedrock guardrails by the same user in the same account over a session. Multiple violations implies that a user may be intentionally attempting to cirvumvent security controls, access sensitive information, or possibly exploit a vulnerability in the system. |[Domain: LLM], [Data Source: AWS Bedrock], [Data Source: AWS S3], [Resources: Investigation Guide], [Use Case: Policy Violation], [Mitre Atlas: T0051], [Mitre Atlas: T0054] |8.13.0 |1
 
-|<<aws-cloudtrail-log-suspended, AWS CloudTrail Log Suspended>> |Identifies suspending the recording of AWS API calls and log file delivery for the specified trail. An adversary may suspend trails in an attempt to evade defenses. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Log Auditing] [Investigation Guide]  |7.9.0 |103 <<aws-cloudtrail-log-suspended-history, Version history>>
+|<<aws-cloudtrail-log-created, AWS CloudTrail Log Created>> |Identifies the creation of an AWS log trail that specifies the settings for delivery of log data. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Log Auditing], [Tactic: Collection] |8.9.0 |207
 
-|<<aws-cloudtrail-log-updated, AWS CloudTrail Log Updated>> |Identifies an update to an AWS log trail setting that specifies the delivery of log files. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Log Auditing] [Investigation Guide]  |7.9.0 |103 <<aws-cloudtrail-log-updated-history, Version history>>
+|<<aws-cloudtrail-log-deleted, AWS CloudTrail Log Deleted>> |Identifies the deletion of an AWS log trail. An adversary may delete trails in an attempt to evade defenses. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Log Auditing], [Resources: Investigation Guide], [Tactic: Defense Evasion] |8.9.0 |209
 
-|<<aws-cloudwatch-alarm-deletion, AWS CloudWatch Alarm Deletion>> |Identifies the deletion of an AWS CloudWatch alarm. An adversary may delete alarms in an attempt to evade defenses. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Monitoring] [Investigation Guide]  |7.9.0 |103 <<aws-cloudwatch-alarm-deletion-history, Version history>>
+|<<aws-cloudtrail-log-suspended, AWS CloudTrail Log Suspended>> |Identifies suspending the recording of AWS API calls and log file delivery for the specified trail. An adversary may suspend trails in an attempt to evade defenses. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Log Auditing], [Resources: Investigation Guide], [Tactic: Defense Evasion] |8.9.0 |209
 
-|<<aws-cloudwatch-log-group-deletion, AWS CloudWatch Log Group Deletion>> |Identifies the deletion of a specified AWS CloudWatch log group. When a log group is deleted, all the archived log events associated with the log group are also permanently deleted. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Log Auditing] [Investigation Guide]  |7.9.0 |103 <<aws-cloudwatch-log-group-deletion-history, Version history>>
+|<<aws-cloudtrail-log-updated, AWS CloudTrail Log Updated>> |Identifies an update to an AWS log trail setting that specifies the delivery of log files. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS Cloudtrail], [Use Case: Log Auditing], [Resources: Investigation Guide], [Tactic: Impact] |8.9.0 |209
 
-|<<aws-cloudwatch-log-stream-deletion, AWS CloudWatch Log Stream Deletion>> |Identifies the deletion of an AWS CloudWatch log stream, which permanently deletes all associated archived log events with the stream. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Log Auditing] [Impact] [Investigation Guide]  |7.9.0 |103 <<aws-cloudwatch-log-stream-deletion-history, Version history>>
+|<<aws-cloudwatch-alarm-deletion, AWS CloudWatch Alarm Deletion>> |Identifies the deletion of an AWS CloudWatch alarm. An adversary may delete alarms in an attempt to evade defenses. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Resources: Investigation Guide], [Tactic: Defense Evasion] |8.9.0 |209
 
-|<<aws-config-resource-deletion, AWS Config Resource Deletion>> |Identifies attempts to delete an AWS Config Service resource. An adversary may tamper with Config services in order to reduce visibility into the security posture of an account and / or its workload instances. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Monitoring] [Investigation Guide]  |7.9.0 |103 <<aws-config-resource-deletion-history, Version history>>
+|<<aws-cloudwatch-log-group-deletion, AWS CloudWatch Log Group Deletion>> |Identifies the deletion of a specified AWS CloudWatch log group. When a log group is deleted, all the archived log events associated with the log group are also permanently deleted. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS CloudWatch], [Use Case: Log Auditing], [Resources: Investigation Guide], [Tactic: Impact] |8.9.0 |209
 
-|<<aws-configuration-recorder-stopped, AWS Configuration Recorder Stopped>> |Identifies an AWS configuration change to stop recording a designated set of resources. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Monitoring]  |7.9.0 |101 <<aws-configuration-recorder-stopped-history, Version history>>
+|<<aws-cloudwatch-log-stream-deletion, AWS CloudWatch Log Stream Deletion>> |Identifies the deletion of an AWS CloudWatch log stream, which permanently deletes all associated archived log events with the stream. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS CloudWatch], [Use Case: Log Auditing], [Tactic: Impact], [Resources: Investigation Guide] |8.9.0 |209
 
-|<<aws-deletion-of-rds-instance-or-cluster, AWS Deletion of RDS Instance or Cluster>> |Identifies the deletion of an Amazon Relational Database Service (RDS) Aurora database cluster, global database cluster, or database instance. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility]  |7.9.0 |101 <<aws-deletion-of-rds-instance-or-cluster-history, Version history>>
+|<<aws-config-resource-deletion, AWS Config Resource Deletion>> |Identifies attempts to delete an AWS Config Service resource. An adversary may tamper with Config services in order to reduce visibility into the security posture of an account and / or its workload instances. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Resources: Investigation Guide], [Tactic: Defense Evasion] |8.9.0 |209
 
-|<<aws-ec2-encryption-disabled, AWS EC2 Encryption Disabled>> |Identifies disabling of Amazon Elastic Block Store (EBS) encryption by default in the current region. Disabling encryption by default does not change the encryption status of your existing volumes. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Data Protection]  |7.9.0 |101 <<aws-ec2-encryption-disabled-history, Version history>>
+|<<aws-configuration-recorder-stopped, AWS Configuration Recorder Stopped>> |Identifies an AWS configuration change to stop recording a designated set of resources. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Tactic: Defense Evasion] |8.9.0 |206
 
-|<<aws-ec2-full-network-packet-capture-detected, AWS EC2 Full Network Packet Capture Detected>> |Identifies potential Traffic Mirroring in an Amazon Elastic Compute Cloud (EC2) instance. Traffic Mirroring is an Amazon VPC feature that you can use to copy network traffic from an Elastic network interface. This feature can potentially be abused to exfiltrate sensitive data from unencrypted internal traffic. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Network Security]  |7.14.0 |101 <<aws-ec2-full-network-packet-capture-detected-history, Version history>>
+|<<aws-credentials-searched-for-inside-a-container, AWS Credentials Searched For Inside A Container>> |This rule detects the use of system search utilities like grep and find to search for AWS credentials inside a container. Unauthorized access to these sensitive files could lead to further compromise of the container environment or facilitate a container breakout to the underlying cloud environment. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access] |8.8.0 |1
 
-|<<aws-ec2-network-access-control-list-creation, AWS EC2 Network Access Control List Creation>> |Identifies the creation of an AWS Elastic Compute Cloud (EC2) network access control list (ACL) or an entry in a network ACL with a specified rule number. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Network Security]  |7.9.0 |101 <<aws-ec2-network-access-control-list-creation-history, Version history>>
+|<<aws-deletion-of-rds-instance-or-cluster, AWS Deletion of RDS Instance or Cluster>> |Identifies the deletion of an Amazon Relational Database Service (RDS) Aurora database cluster, global database cluster, or database instance. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS RDS], [Use Case: Asset Visibility], [Tactic: Impact] |8.9.0 |206
 
-|<<aws-ec2-network-access-control-list-deletion, AWS EC2 Network Access Control List Deletion>> |Identifies the deletion of an Amazon Elastic Compute Cloud (EC2) network access control list (ACL) or one of its ingress/egress entries. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Network Security]  |7.9.0 |101 <<aws-ec2-network-access-control-list-deletion-history, Version history>>
+|<<aws-ec2-admin-credential-fetch-via-assumed-role, AWS EC2 Admin Credential Fetch via Assumed Role>> |Identifies the first occurrence of a user identity in AWS using `GetPassword` for the administrator password of an EC2 instance with an assumed role. Adversaries may use this API call to escalate privileges or move laterally within EC2 instances. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: Amazon EC2], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Credential Access] |8.3.0 |2
 
-|<<aws-ec2-snapshot-activity, AWS EC2 Snapshot Activity>> |An attempt was made to modify AWS EC2 snapshot attributes. Snapshots are sometimes shared by threat actors in order to exfiltrate bulk data from an EC2 fleet. If the permissions were modified, verify the snapshot was not shared with an unauthorized or unexpected AWS account. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility] [Exfiltration] [Investigation Guide]  |7.9.0 |103 <<aws-ec2-snapshot-activity-history, Version history>>
+|<<aws-ec2-encryption-disabled, AWS EC2 Encryption Disabled>> |Identifies disabling of Amazon Elastic Block Store (EBS) encryption by default in the current region. Disabling encryption by default does not change the encryption status of your existing volumes. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS EC2], [Tactic: Impact] |8.9.0 |206
 
-|<<aws-ec2-vm-export-failure, AWS EC2 VM Export Failure>> |Identifies an attempt to export an AWS EC2 instance. A virtual machine (VM) export may indicate an attempt to extract or exfiltrate information. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility]  |7.14.0 |101 <<aws-ec2-vm-export-failure-history, Version history>>
+|<<aws-ec2-full-network-packet-capture-detected, AWS EC2 Full Network Packet Capture Detected>> |Identifies potential Traffic Mirroring in an Amazon Elastic Compute Cloud (EC2) instance. Traffic Mirroring is an Amazon VPC feature that you can use to copy network traffic from an Elastic network interface. This feature can potentially be abused to exfiltrate sensitive data from unencrypted internal traffic. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Network Security Monitoring], [Tactic: Exfiltration], [Tactic: Collection] |8.9.0 |206
 
-|<<aws-efs-file-system-or-mount-deleted, AWS EFS File System or Mount Deleted>> |Detects when an EFS File System or Mount is deleted. An adversary could break any file system using the mount target that is being deleted, which might disrupt instances or applications using those mounts. The mount must be deleted prior to deleting the File System, or the adversary will be unable to delete the File System. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Data Protection]  |7.16.0 |101 <<aws-efs-file-system-or-mount-deleted-history, Version history>>
+|<<aws-ec2-network-access-control-list-creation, AWS EC2 Network Access Control List Creation>> |Identifies the creation of an AWS Elastic Compute Cloud (EC2) network access control list (ACL) or an entry in a network ACL with a specified rule number. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS EC2], [Use Case: Network Security Monitoring], [Tactic: Persistence] |8.9.0 |206
 
-|<<aws-elasticache-security-group-created, AWS ElastiCache Security Group Created>> |Identifies when an ElastiCache security group has been created. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Monitoring]  |7.16.0 |101 <<aws-elasticache-security-group-created-history, Version history>>
+|<<aws-ec2-network-access-control-list-deletion, AWS EC2 Network Access Control List Deletion>> |Identifies the deletion of an Amazon Elastic Compute Cloud (EC2) network access control list (ACL) or one of its ingress/egress entries. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Network Security Monitoring], [Tactic: Defense Evasion] |8.9.0 |206
 
-|<<aws-elasticache-security-group-modified-or-deleted, AWS ElastiCache Security Group Modified or Deleted>> |Identifies when an ElastiCache security group has been modified or deleted. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Monitoring]  |7.16.0 |101 <<aws-elasticache-security-group-modified-or-deleted-history, Version history>>
+|<<aws-ec2-snapshot-activity, AWS EC2 Snapshot Activity>> |An attempt was made to modify AWS EC2 snapshot attributes. Snapshots are sometimes shared by threat actors in order to exfiltrate bulk data from an EC2 fleet. If the permissions were modified, verify the snapshot was not shared with an unauthorized or unexpected AWS account. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Asset Visibility], [Tactic: Exfiltration], [Resources: Investigation Guide] |8.9.0 |209
 
-|<<aws-eventbridge-rule-disabled-or-deleted, AWS EventBridge Rule Disabled or Deleted>> |Identifies when a user has disabled or deleted an EventBridge rule. This activity can result in an unintended loss of visibility in applications or a break in the flow with other AWS services. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Monitoring] [Impact]  |7.16.0 |101 <<aws-eventbridge-rule-disabled-or-deleted-history, Version history>>
+|<<aws-ec2-vm-export-failure, AWS EC2 VM Export Failure>> |Identifies an attempt to export an AWS EC2 instance. A virtual machine (VM) export may indicate an attempt to extract or exfiltrate information. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Asset Visibility], [Tactic: Exfiltration], [Tactic: Collection] |8.9.0 |206
 
-|<<aws-execution-via-system-manager, AWS Execution via System Manager>> |Identifies the execution of commands and scripts via System Manager. Execution methods such as RunShellScript, RunPowerShellScript, and alike can be abused by an authenticated attacker to install a backdoor or to interact with a compromised instance via reverse-shell using system only commands. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Log Auditing] [Initial Access] [Investigation Guide]  |7.9.0 |103 <<aws-execution-via-system-manager-history, Version history>>
+|<<aws-efs-file-system-or-mount-deleted, AWS EFS File System or Mount Deleted>> |Detects when an EFS File System or Mount is deleted. An adversary could break any file system using the mount target that is being deleted, which might disrupt instances or applications using those mounts. The mount must be deleted prior to deleting the File System, or the adversary will be unable to delete the File System. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Tactic: Impact] |8.9.0 |206
 
-|<<aws-guardduty-detector-deletion, AWS GuardDuty Detector Deletion>> |Identifies the deletion of an Amazon GuardDuty detector. Upon deletion, GuardDuty stops monitoring the environment and all existing findings are lost. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Monitoring]  |7.9.0 |101 <<aws-guardduty-detector-deletion-history, Version history>>
+|<<aws-elasticache-security-group-created, AWS ElastiCache Security Group Created>> |Identifies when an ElastiCache security group has been created. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Tactic: Defense Evasion] |8.9.0 |206
 
-|<<aws-iam-assume-role-policy-update, AWS IAM Assume Role Policy Update>> |Identifies attempts to modify an AWS IAM Assume Role Policy. An adversary may attempt to modify the AssumeRolePolicy of a misconfigured role in order to gain the privileges of that role. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Identity and Access] [Investigation Guide]  |7.9.0 |103 <<aws-iam-assume-role-policy-update-history, Version history>>
+|<<aws-elasticache-security-group-modified-or-deleted, AWS ElastiCache Security Group Modified or Deleted>> |Identifies when an ElastiCache security group has been modified or deleted. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Tactic: Defense Evasion] |8.9.0 |206
 
-|<<aws-iam-brute-force-of-assume-role-policy, AWS IAM Brute Force of Assume Role Policy>> |Identifies a high number of failed attempts to assume an AWS Identity and Access Management (IAM) role. IAM roles are used to delegate access to users or services. An adversary may attempt to enumerate IAM roles in order to determine if a role exists before attempting to assume or hijack the discovered role. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Identity and Access] [Investigation Guide]  |7.9.0 |103 <<aws-iam-brute-force-of-assume-role-policy-history, Version history>>
+|<<aws-eventbridge-rule-disabled-or-deleted, AWS EventBridge Rule Disabled or Deleted>> |Identifies when a user has disabled or deleted an EventBridge rule. This activity can result in an unintended loss of visibility in applications or a break in the flow with other AWS services. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Tactic: Impact] |8.9.0 |206
 
-|<<aws-iam-deactivation-of-mfa-device, AWS IAM Deactivation of MFA Device>> |Identifies the deactivation of a specified multi-factor authentication (MFA) device and removes it from association with the user name for which it was originally enabled. In AWS Identity and Access Management (IAM), a device must be deactivated before it can be deleted. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Monitoring] [Investigation Guide]  |7.9.0 |103 <<aws-iam-deactivation-of-mfa-device-history, Version history>>
+|<<aws-execution-via-system-manager, AWS Execution via System Manager>> |Identifies the execution of commands and scripts via System Manager. Execution methods such as RunShellScript, RunPowerShellScript, and alike can be abused by an authenticated attacker to install a backdoor or to interact with a compromised instance via reverse-shell using system only commands. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS SSM], [Use Case: Log Auditing], [Tactic: Initial Access], [Resources: Investigation Guide] |8.9.0 |209
 
-|<<aws-iam-group-creation, AWS IAM Group Creation>> |Identifies the creation of a group in AWS Identity and Access Management (IAM). Groups specify permissions for multiple users. Any user in a group automatically has the permissions that are assigned to the group. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.9.0 |101 <<aws-iam-group-creation-history, Version history>>
+|<<aws-guardduty-detector-deletion, AWS GuardDuty Detector Deletion>> |Identifies the deletion of an Amazon GuardDuty detector. Upon deletion, GuardDuty stops monitoring the environment and all existing findings are lost. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Tactic: Defense Evasion] |8.9.0 |206
 
-|<<aws-iam-group-deletion, AWS IAM Group Deletion>> |Identifies the deletion of a specified AWS Identity and Access Management (IAM) resource group. Deleting a resource group does not delete resources that are members of the group; it only deletes the group structure. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Monitoring]  |7.9.0 |101 <<aws-iam-group-deletion-history, Version history>>
+|<<aws-iam-assume-role-policy-update, AWS IAM Assume Role Policy Update>> |Identifies attempts to modify an AWS IAM Assume Role Policy. An adversary may attempt to modify the AssumeRolePolicy of a misconfigured role in order to gain the privileges of that role. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS STS], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Privilege Escalation] |8.9.0 |209
 
-|<<aws-iam-password-recovery-requested, AWS IAM Password Recovery Requested>> |Identifies AWS IAM password recovery requests. An adversary may attempt to gain unauthorized AWS access by abusing password recovery mechanisms. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.9.0 |101 <<aws-iam-password-recovery-requested-history, Version history>>
+|<<aws-iam-brute-force-of-assume-role-policy, AWS IAM Brute Force of Assume Role Policy>> |Identifies a high number of failed attempts to assume an AWS Identity and Access Management (IAM) role. IAM roles are used to delegate access to users or services. An adversary may attempt to enumerate IAM roles in order to determine if a role exists before attempting to assume or hijack the discovered role. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Credential Access] |8.9.0 |210
 
-|<<aws-iam-user-addition-to-group, AWS IAM User Addition to Group>> |Identifies the addition of a user to a specified group in AWS Identity and Access Management (IAM). |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Identity and Access] [Credential Access] [Persistence] [Investigation Guide]  |7.9.0 |103 <<aws-iam-user-addition-to-group-history, Version history>>
+|<<aws-iam-deactivation-of-mfa-device, AWS IAM Deactivation of MFA Device>> |Identifies the deactivation of a specified multi-factor authentication (MFA) device and removes it from association with the user name for which it was originally enabled. In AWS Identity and Access Management (IAM), a device must be deactivated before it can be deleted. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS IAM], [Resources: Investigation Guide], [Tactic: Impact] |8.9.0 |209
 
-|<<aws-kms-customer-managed-key-disabled-or-scheduled-for-deletion, AWS KMS Customer Managed Key Disabled or Scheduled for Deletion>> |Identifies attempts to disable or schedule the deletion of an AWS KMS Customer Managed Key (CMK). Deleting an AWS KMS key is destructive and potentially dangerous. It deletes the key material and all metadata associated with the KMS key and is irreversible. After a KMS key is deleted, the data that was encrypted under that KMS key can no longer be decrypted, which means that data becomes unrecoverable. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Log Auditing] [Impact]  |8.6.0 |1
+|<<aws-iam-group-creation, AWS IAM Group Creation>> |Identifies the creation of a group in AWS Identity and Access Management (IAM). Groups specify permissions for multiple users. Any user in a group automatically has the permissions that are assigned to the group. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS IAM], [Use Case: Identity and Access Audit], [Tactic: Persistence] |8.9.0 |206
 
-|<<aws-management-console-brute-force-of-root-user-identity, AWS Management Console Brute Force of Root User Identity>> |Identifies a high number of failed authentication attempts to the AWS management console for the Root user identity. An adversary may attempt to brute force the password for the Root user identity, as it has complete access to all services and resources for the AWS account. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |101 <<aws-management-console-brute-force-of-root-user-identity-history, Version history>>
+|<<aws-iam-group-deletion, AWS IAM Group Deletion>> |Identifies the deletion of a specified AWS Identity and Access Management (IAM) resource group. Deleting a resource group does not delete resources that are members of the group; it only deletes the group structure. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS IAM], [Tactic: Impact] |8.9.0 |206
 
-|<<aws-management-console-root-login, AWS Management Console Root Login>> |Identifies a successful login to the AWS Management Console by the Root user. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Identity and Access] [Investigation Guide]  |7.9.0 |103 <<aws-management-console-root-login-history, Version history>>
+|<<aws-iam-login-profile-added-to-user, AWS IAM Login Profile Added to User>> |Identifies when an AWS IAM login profile is added to a user. Adversaries may add a login profile to an IAM user who typically does not have one and is used only for programmatic access. This can be used to maintain access to the account even if the original access key is rotated or disabled. This is a building block rule and does not generate alerts on its own. It is meant to be used for correlation with other rules to detect suspicious activity. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS IAM], [Use Case: Identity and Access Audit], [Tactic: Persistence], [Rule Type: BBR] |8.9.0 |1
 
-|<<aws-rds-cluster-creation, AWS RDS Cluster Creation>> |Identifies the creation of a new Amazon Relational Database Service (RDS) Aurora DB cluster or global database spread across multiple regions. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility]  |7.9.0 |101 <<aws-rds-cluster-creation-history, Version history>>
+|<<aws-iam-password-recovery-requested, AWS IAM Password Recovery Requested>> |Identifies AWS IAM password recovery requests. An adversary may attempt to gain unauthorized AWS access by abusing password recovery mechanisms. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS Signin], [Use Case: Identity and Access Audit], [Tactic: Initial Access] |8.9.0 |206
 
-|<<aws-rds-instance-creation, AWS RDS Instance Creation>> |Identifies the creation of an Amazon Relational Database Service (RDS) Aurora database instance. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility] [Persistence]  |7.14.0 |101 <<aws-rds-instance-creation-history, Version history>>
+|<<aws-iam-user-addition-to-group, AWS IAM User Addition to Group>> |Identifies the addition of a user to a specified group in AWS Identity and Access Management (IAM). |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Identity and Access Audit], [Tactic: Credential Access], [Tactic: Persistence], [Resources: Investigation Guide] |8.9.0 |209
 
-|<<aws-rds-instance-cluster-stoppage, AWS RDS Instance/Cluster Stoppage>> |Identifies that an Amazon Relational Database Service (RDS) cluster or instance has been stopped. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility]  |7.9.0 |101 <<aws-rds-instance-cluster-stoppage-history, Version history>>
+|<<aws-kms-customer-managed-key-disabled-or-scheduled-for-deletion, AWS KMS Customer Managed Key Disabled or Scheduled for Deletion>> |Identifies attempts to disable or schedule the deletion of an AWS KMS Customer Managed Key (CMK). Deleting an AWS KMS key is destructive and potentially dangerous. It deletes the key material and all metadata associated with the KMS key and is irreversible. After a KMS key is deleted, the data that was encrypted under that KMS key can no longer be decrypted, which means that data becomes unrecoverable. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS KMS], [Use Case: Log Auditing], [Tactic: Impact] |8.9.0 |106
 
-|<<aws-rds-security-group-creation, AWS RDS Security Group Creation>> |Identifies the creation of an Amazon Relational Database Service (RDS) Security group. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Monitoring]  |7.14.0 |101 <<aws-rds-security-group-creation-history, Version history>>
+|<<aws-management-console-brute-force-of-root-user-identity, AWS Management Console Brute Force of Root User Identity>> |Identifies a high number of failed authentication attempts to the AWS management console for the Root user identity. An adversary may attempt to brute force the password for the Root user identity, as it has complete access to all services and resources for the AWS account. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Identity and Access Audit], [Tactic: Credential Access] |8.9.0 |207
 
-|<<aws-rds-security-group-deletion, AWS RDS Security Group Deletion>> |Identifies the deletion of an Amazon Relational Database Service (RDS) Security group. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Monitoring]  |7.14.0 |101 <<aws-rds-security-group-deletion-history, Version history>>
+|<<aws-management-console-root-login, AWS Management Console Root Login>> |Identifies a successful login to the AWS Management Console by the Root user. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS Signin], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Initial Access] |8.9.0 |209
 
-|<<aws-rds-snapshot-export, AWS RDS Snapshot Export>> |Identifies the export of an Amazon Relational Database Service (RDS) Aurora database snapshot. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility] [Exfiltration]  |7.16.0 |101 <<aws-rds-snapshot-export-history, Version history>>
+|<<aws-rds-cluster-creation, AWS RDS Cluster Creation>> |Identifies the creation of a new Amazon Relational Database Service (RDS) Aurora DB cluster or global database spread across multiple regions. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS RDS], [Use Case: Asset Visibility], [Tactic: Persistence] |8.9.0 |206
 
-|<<aws-rds-snapshot-restored, AWS RDS Snapshot Restored>> |Identifies when an attempt was made to restore an RDS Snapshot. Snapshots are sometimes shared by threat actors in order to exfiltrate bulk data or evade detection after performing malicious activities. If the permissions were modified, verify if the snapshot was shared with an unauthorized or unexpected AWS account. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility] [Defense Evasion]  |7.16.0 |101 <<aws-rds-snapshot-restored-history, Version history>>
+|<<aws-rds-instance-creation, AWS RDS Instance Creation>> |Identifies the creation of an Amazon Relational Database Service (RDS) Aurora database instance. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS RDS], [Use Case: Asset Visibility], [Tactic: Persistence] |8.9.0 |206
 
-|<<aws-redshift-cluster-creation, AWS Redshift Cluster Creation>> |Identifies the creation of an Amazon Redshift cluster. Unexpected creation of this cluster by a non-administrative user may indicate a permission or role issue with current users. If unexpected, the resource may not properly be configured and could introduce security vulnerabilities. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility] [Persistence]  |8.3.0 |101 <<aws-redshift-cluster-creation-history, Version history>>
+|<<aws-rds-instance-cluster-stoppage, AWS RDS Instance/Cluster Stoppage>> |Identifies that an Amazon Relational Database Service (RDS) cluster or instance has been stopped. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS RDS], [Use Case: Asset Visibility], [Tactic: Impact] |8.9.0 |206
 
-|<<aws-root-login-without-mfa, AWS Root Login Without MFA>> |Identifies attempts to login to AWS as the root user without using multi-factor authentication (MFA). Amazon AWS best practices indicate that the root user should be protected by MFA. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Identity and Access] [Investigation Guide]  |7.9.0 |103 <<aws-root-login-without-mfa-history, Version history>>
+|<<aws-rds-security-group-creation, AWS RDS Security Group Creation>> |Identifies the creation of an Amazon Relational Database Service (RDS) Security group. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS RDS], [Tactic: Persistence] |8.9.0 |206
 
-|<<aws-route-53-domain-transfer-lock-disabled, AWS Route 53 Domain Transfer Lock Disabled>> |Identifies when a transfer lock was removed from a Route 53 domain. It is recommended to refrain from performing this action unless intending to transfer the domain to a different registrar. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility]  |7.14.0 |101 <<aws-route-53-domain-transfer-lock-disabled-history, Version history>>
+|<<aws-rds-security-group-deletion, AWS RDS Security Group Deletion>> |Identifies the deletion of an Amazon Relational Database Service (RDS) Security group. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS RDS], [Tactic: Impact] |8.9.0 |206
 
-|<<aws-route-53-domain-transferred-to-another-account, AWS Route 53 Domain Transferred to Another Account>> |Identifies when a request has been made to transfer a Route 53 domain to another AWS account. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility]  |7.14.0 |101 <<aws-route-53-domain-transferred-to-another-account-history, Version history>>
+|<<aws-rds-snapshot-export, AWS RDS Snapshot Export>> |Identifies the export of an Amazon Relational Database Service (RDS) Aurora database snapshot. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Asset Visibility], [Tactic: Exfiltration] |8.9.0 |206
 
-|<<aws-route-table-created, AWS Route Table Created>> |Identifies when an AWS Route Table has been created. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Network Security] [Persistence]  |7.16.0 |101 <<aws-route-table-created-history, Version history>>
+|<<aws-rds-snapshot-restored, AWS RDS Snapshot Restored>> |Identifies when an attempt was made to restore an RDS Snapshot. Snapshots are sometimes shared by threat actors in order to exfiltrate bulk data or evade detection after performing malicious activities. If the permissions were modified, verify if the snapshot was shared with an unauthorized or unexpected AWS account. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Asset Visibility], [Tactic: Defense Evasion] |8.9.0 |206
 
-|<<aws-route-table-modified-or-deleted, AWS Route Table Modified or Deleted>> |Identifies when an AWS Route Table has been modified or deleted. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Network Security] [Persistence]  |7.16.0 |101 <<aws-route-table-modified-or-deleted-history, Version history>>
+|<<aws-redshift-cluster-creation, AWS Redshift Cluster Creation>> |Identifies the creation of an Amazon Redshift cluster. Unexpected creation of this cluster by a non-administrative user may indicate a permission or role issue with current users. If unexpected, the resource may not properly be configured and could introduce security vulnerabilities. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS Redshift], [Use Case: Asset Visibility], [Tactic: Persistence] |8.9.0 |206
 
-|<<aws-route53-private-hosted-zone-associated-with-a-vpc, AWS Route53 private hosted zone associated with a VPC>> |Identifies when a Route53 private hosted zone has been associated with VPC. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility]  |7.16.0 |101 <<aws-route53-private-hosted-zone-associated-with-a-vpc-history, Version history>>
+|<<aws-root-login-without-mfa, AWS Root Login Without MFA>> |Identifies attempts to login to AWS as the root user without using multi-factor authentication (MFA). Amazon AWS best practices indicate that the root user should be protected by MFA. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS Route53], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Privilege Escalation] |8.9.0 |209
 
-|<<aws-s3-bucket-configuration-deletion, AWS S3 Bucket Configuration Deletion>> |Identifies the deletion of various Amazon Simple Storage Service (S3) bucket configuration components. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Asset Visibility]  |7.9.0 |101 <<aws-s3-bucket-configuration-deletion-history, Version history>>
+|<<aws-route-53-domain-transfer-lock-disabled, AWS Route 53 Domain Transfer Lock Disabled>> |Identifies when a transfer lock was removed from a Route 53 domain. It is recommended to refrain from performing this action unless intending to transfer the domain to a different registrar. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS Route53], [Use Case: Asset Visibility], [Tactic: Persistence] |8.9.0 |206
 
-|<<aws-saml-activity, AWS SAML Activity>> |Identifies when SAML activity has occurred in AWS. An adversary could manipulate SAML to maintain access to the target. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.16.0 |101 <<aws-saml-activity-history, Version history>>
+|<<aws-route-53-domain-transferred-to-another-account, AWS Route 53 Domain Transferred to Another Account>> |Identifies when a request has been made to transfer a Route 53 domain to another AWS account. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS Route53], [Use Case: Asset Visibility], [Tactic: Persistence] |8.9.0 |206
 
-|<<aws-sts-getsessiontoken-abuse, AWS STS GetSessionToken Abuse>> |Identifies the suspicious use of GetSessionToken. Tokens could be created and used by attackers to move laterally and escalate privileges. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.16.0 |101 <<aws-sts-getsessiontoken-abuse-history, Version history>>
+|<<aws-route-table-created, AWS Route Table Created>> |Identifies when an AWS Route Table has been created. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS Route53], [Use Case: Network Security Monitoring], [Tactic: Persistence] |8.9.0 |207
 
-|<<aws-security-group-configuration-change-detection, AWS Security Group Configuration Change Detection>> |Identifies a change to an AWS Security Group Configuration. A security group is like a virtual firewall, and modifying configurations may allow unauthorized access. Threat actors may abuse this to establish persistence, exfiltrate data, or pivot in an AWS environment. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Network Security]  |7.15.0 |101 <<aws-security-group-configuration-change-detection-history, Version history>>
+|<<aws-route-table-modified-or-deleted, AWS Route Table Modified or Deleted>> |Identifies when an AWS Route Table has been modified or deleted. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS Route53], [Use Case: Network Security Monitoring], [Tactic: Persistence] |8.9.0 |207
 
-|<<aws-security-token-service-sts-assumerole-usage, AWS Security Token Service (STS) AssumeRole Usage>> |Identifies the use of AssumeRole. AssumeRole returns a set of temporary security credentials that can be used to access AWS resources. An adversary could use those credentials to move laterally and escalate privileges. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.16.0 |101 <<aws-security-token-service-sts-assumerole-usage-history, Version history>>
+|<<aws-route53-private-hosted-zone-associated-with-a-vpc, AWS Route53 private hosted zone associated with a VPC>> |Identifies when a Route53 private hosted zone has been associated with VPC. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS Route53], [Use Case: Asset Visibility], [Tactic: Persistence] |8.9.0 |206
 
-|<<aws-vpc-flow-logs-deletion, AWS VPC Flow Logs Deletion>> |Identifies the deletion of one or more flow logs in AWS Elastic Compute Cloud (EC2). An adversary may delete flow logs in an attempt to evade defenses. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Log Auditing] [Investigation Guide]  |7.9.0 |103 <<aws-vpc-flow-logs-deletion-history, Version history>>
+|<<aws-s3-bucket-configuration-deletion, AWS S3 Bucket Configuration Deletion>> |Identifies the deletion of various Amazon Simple Storage Service (S3) bucket configuration components. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Asset Visibility], [Tactic: Defense Evasion] |8.9.0 |207
 
-|<<aws-waf-access-control-list-deletion, AWS WAF Access Control List Deletion>> |Identifies the deletion of a specified AWS Web Application Firewall (WAF) access control list. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Network Security]  |7.9.0 |101 <<aws-waf-access-control-list-deletion-history, Version history>>
+|<<aws-s3-bucket-enumeration-or-brute-force, AWS S3 Bucket Enumeration or Brute Force>> |Identifies a high number of failed S3 operations from a single source and account (or anonymous account) within a short timeframe. This activity can be indicative of attempting to cause an increase in billing to an account for excessive random operations, cause resource exhaustion, or enumerating bucket names for discovery. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS S3], [Resources: Investigation Guide], [Use Case: Log Auditing], [Tactic: Impact] |8.13.0 |1
 
-|<<aws-waf-rule-or-rule-group-deletion, AWS WAF Rule or Rule Group Deletion>> |Identifies the deletion of a specified AWS Web Application Firewall (WAF) rule or rule group. |[Elastic] [Cloud] [AWS] [Continuous Monitoring] [SecOps] [Network Security]  |7.9.0 |101 <<aws-waf-rule-or-rule-group-deletion-history, Version history>>
+|<<aws-saml-activity, AWS SAML Activity>> |Identifies when SAML activity has occurred in AWS. An adversary could manipulate SAML to maintain access to the target. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Identity and Access Audit], [Tactic: Defense Evasion] |8.9.0 |206
 
-|<<abnormal-process-id-or-lock-file-created, Abnormal Process ID or Lock File Created>> |Identifies the creation of a Process ID (PID), lock or reboot file created in temporary file storage paradigm (tmpfs) directory /var/run. On Linux, the PID files typically hold the process ID to track previous copies running and manage other tasks. Certain Linux malware use the /var/run directory for holding data, executables and other tasks, disguising itself or these files as legitimate PID files. |[Elastic] [Host] [Linux] [Threat Detection] [Execution] [BPFDoor] [Investigation Guide]  |8.3.0 |102 <<abnormal-process-id-or-lock-file-created-history, Version history>>
+|<<aws-sts-getsessiontoken-abuse, AWS STS GetSessionToken Abuse>> |Identifies the suspicious use of GetSessionToken. Tokens could be created and used by attackers to move laterally and escalate privileges. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS STS], [Use Case: Identity and Access Audit], [Tactic: Privilege Escalation] |8.9.0 |206
 
-|<<abnormally-large-dns-response, Abnormally Large DNS Response>> |Specially crafted DNS requests can manipulate a known overflow vulnerability in some Windows DNS servers, resulting in Remote Code Execution (RCE) or a Denial of Service (DoS) from crashing the service. |[Elastic] [Network] [Threat Detection] [Lateral Movement] [Investigation Guide]  |7.10.0 |102 <<abnormally-large-dns-response-history, Version history>>
+|<<aws-security-group-configuration-change-detection, AWS Security Group Configuration Change Detection>> |Identifies a change to an AWS Security Group Configuration. A security group is like a virtual firewall, and modifying configurations may allow unauthorized access. Threat actors may abuse this to establish persistence, exfiltrate data, or pivot in an AWS environment. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS EC2], [Use Case: Network Security Monitoring], [Tactic: Persistence] |8.9.0 |206
 
-|<<accepted-default-telnet-port-connection, Accepted Default Telnet Port Connection>> |This rule detects network events that may indicate the use of Telnet traffic. Telnet is commonly used by system administrators to remotely control older or embedded systems using the command line shell. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. As a plain-text protocol, it may also expose usernames and passwords to anyone capable of observing the traffic. |[Elastic] [Host] [Network] [Threat Detection] [Command and Control] [Host] [Lateral Movement] [Initial Access]  |7.6.0 |101 <<accepted-default-telnet-port-connection-history, Version history>>
+|<<aws-security-token-service-sts-assumerole-usage, AWS Security Token Service (STS) AssumeRole Usage>> |Identifies the use of AssumeRole. AssumeRole returns a set of temporary security credentials that can be used to access AWS resources. An adversary could use those credentials to move laterally and escalate privileges. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS STS], [Use Case: Identity and Access Audit], [Tactic: Privilege Escalation] |8.9.0 |206
 
-|<<access-of-stored-browser-credentials, Access of Stored Browser Credentials>> |Identifies the execution of a process with arguments pointing to known browser files that store passwords and cookies. Adversaries may acquire credentials from web browsers by reading files specific to the target browser. |[Elastic] [Host] [macOS] [Threat Detection] [Credential Access]  |7.12.0 |100 <<access-of-stored-browser-credentials-history, Version history>>
+|<<aws-vpc-flow-logs-deletion, AWS VPC Flow Logs Deletion>> |Identifies the deletion of one or more flow logs in AWS Elastic Compute Cloud (EC2). An adversary may delete flow logs in an attempt to evade defenses. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Log Auditing], [Resources: Investigation Guide], [Tactic: Defense Evasion] |8.9.0 |209
 
-|<<access-to-keychain-credentials-directories, Access to Keychain Credentials Directories>> |Adversaries may collect the keychain storage data from a system to acquire credentials. Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features such as WiFi passwords, websites, secure notes and certificates. |[Elastic] [Host] [macOS] [Threat Detection] [Credential Access]  |7.10.0 |100 <<access-to-keychain-credentials-directories-history, Version history>>
+|<<aws-waf-access-control-list-deletion, AWS WAF Access Control List Deletion>> |Identifies the deletion of a specified AWS Web Application Firewall (WAF) access control list. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Network Security Monitoring], [Tactic: Defense Evasion] |8.9.0 |206
 
-|<<access-to-a-sensitive-ldap-attribute, Access to a Sensitive LDAP Attribute>> |Identify access to sensitive Active Directory object attributes that contains credentials and decryption keys such as unixUserPassword, ms-PKI-AccountCredentials and msPKI-CredentialRoamingTokens. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Active Directory]  |8.6.0 |1
+|<<aws-waf-rule-or-rule-group-deletion, AWS WAF Rule or Rule Group Deletion>> |Identifies the deletion of a specified AWS Web Application Firewall (WAF) rule or rule group. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Use Case: Network Security Monitoring], [Tactic: Defense Evasion] |8.9.0 |206
 
-|<<account-configured-with-never-expiring-password, Account Configured with Never-Expiring Password>> |Detects the creation and modification of an account with the "Don't Expire Password" option Enabled. Attackers can abuse this misconfiguration to persist in the domain and maintain long-term access using compromised accounts with this property. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Active Directory] [Investigation Guide]  |8.2.0 |102 <<account-configured-with-never-expiring-password-history, Version history>>
+|<<abnormal-process-id-or-lock-file-created, Abnormal Process ID or Lock File Created>> |Identifies the creation of a Process ID (PID), lock or reboot file created in temporary file storage paradigm (tmpfs) directory /var/run. On Linux, the PID files typically hold the process ID to track previous copies running and manage other tasks. Certain Linux malware use the /var/run directory for holding data, executables and other tasks, disguising itself or these files as legitimate PID files. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Threat: BPFDoor], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.6.0 |213
 
-|<<account-discovery-command-via-system-account, Account Discovery Command via SYSTEM Account>> |Identifies when the SYSTEM account uses an account discovery utility. This could be a sign of discovery activity after an adversary has achieved privilege escalation. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide]  |7.7.0 |102 <<account-discovery-command-via-system-account-history, Version history>>
+|<<abnormally-large-dns-response, Abnormally Large DNS Response>> |Specially crafted DNS requests can manipulate a known overflow vulnerability in some Windows DNS servers, resulting in Remote Code Execution (RCE) or a Denial of Service (DoS) from crashing the service. |[Use Case: Threat Detection], [Tactic: Lateral Movement], [Resources: Investigation Guide], [Use Case: Vulnerability] |8.3.0 |105
 
-|<<account-password-reset-remotely, Account Password Reset Remotely>> |Identifies an attempt to reset a potentially privileged account password remotely. Adversaries may manipulate account passwords to maintain access or evade password duration policies and preserve compromised credentials. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |8.0.0 |101 <<account-password-reset-remotely-history, Version history>>
+|<<accepted-default-telnet-port-connection, Accepted Default Telnet Port Connection>> |This rule detects network events that may indicate the use of Telnet traffic. Telnet is commonly used by system administrators to remotely control older or embedded systems using the command line shell. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. As a plain-text protocol, it may also expose usernames and passwords to anyone capable of observing the traffic. |[Domain: Endpoint], [Use Case: Threat Detection], [Tactic: Command and Control], [Tactic: Lateral Movement], [Tactic: Initial Access] |8.3.0 |104
 
-|<<adfind-command-activity, AdFind Command Activity>> |This rule detects the Active Directory query tool, AdFind.exe. AdFind has legitimate purposes, but it is frequently leveraged by threat actors to perform post-exploitation Active Directory reconnaissance. The AdFind tool has been observed in Trickbot, Ryuk, Maze, and FIN6 campaigns. For Winlogbeat, this rule requires Sysmon. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<adfind-command-activity-history, Version history>>
+|<<access-to-keychain-credentials-directories, Access to Keychain Credentials Directories>> |Adversaries may collect the keychain storage data from a system to acquire credentials. Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features such as WiFi passwords, websites, secure notes and certificates. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.7.0 |207
 
-|<<adding-hidden-file-attribute-via-attrib, Adding Hidden File Attribute via Attrib>> |Adversaries can add the 'hidden' attribute to files to hide them from the user in an attempt to evade detection. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.6.0 |102 <<adding-hidden-file-attribute-via-attrib-history, Version history>>
+|<<access-to-a-sensitive-ldap-attribute, Access to a Sensitive LDAP Attribute>> |Identify access to sensitive Active Directory object attributes that contains credentials and decryption keys such as unixUserPassword, ms-PKI-AccountCredentials and msPKI-CredentialRoamingTokens. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Privilege Escalation], [Use Case: Active Directory Monitoring], [Data Source: Active Directory] |8.3.0 |10
 
-|<<adminsdholder-backdoor, AdminSDHolder Backdoor>> |Detects modifications in the AdminSDHolder object. Attackers can abuse the SDProp process to implement a persistent backdoor in Active Directory. SDProp compares the permissions on protected objects with those defined on the AdminSDHolder object. If the permissions on any of the protected accounts and groups do not match, the permissions on the protected accounts and groups are reset to match those of the domain's AdminSDHolder object, regaining their Administrative Privileges. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Active Directory]  |8.1.0 |100 <<adminsdholder-backdoor-history, Version history>>
+|<<accessing-outlook-data-files, Accessing Outlook Data Files>> |Identifies commands containing references to Outlook data files extensions, which can potentially indicate the search, access, or modification of these files. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |2
 
-|<<adminsdholder-sdprop-exclusion-added, AdminSDHolder SDProp Exclusion Added>> |Identifies a modification on the dsHeuristics attribute on the bit that holds the configuration of groups excluded from the SDProp process. The SDProp compares the permissions on protected objects with those defined on the AdminSDHolder object. If the permissions on any of the protected accounts and groups do not match, the permissions on the protected accounts and groups are reset to match those of the domain's AdminSDHolder object, meaning that groups excluded will remain unchanged. Attackers can abuse this misconfiguration to maintain long-term access to privileged accounts in these groups. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Active Directory] [Investigation Guide]  |8.2.0 |102 <<adminsdholder-sdprop-exclusion-added-history, Version history>>
+|<<account-configured-with-never-expiring-password, Account Configured with Never-Expiring Password>> |Detects the creation and modification of an account with the "Don't Expire Password" option Enabled. Attackers can abuse this misconfiguration to persist in the domain and maintain long-term access using compromised accounts with this property. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Active Directory], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring] |8.3.0 |108
 
-|<<administrator-privileges-assigned-to-an-okta-group, Administrator Privileges Assigned to an Okta Group>> |Detects when an administrator role is assigned to an Okta group. An adversary may attempt to assign administrator privileges to an Okta group in order to assign additional permissions to compromised user accounts and maintain access to their target organization. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring]  |7.9.0 |102 <<administrator-privileges-assigned-to-an-okta-group-history, Version history>>
+|<<account-discovery-command-via-system-account, Account Discovery Command via SYSTEM Account>> |Identifies when the SYSTEM account uses an account discovery utility. This could be a sign of discovery activity after an adversary has achieved privilege escalation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Tactic: Privilege Escalation], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
 
-|<<administrator-role-assigned-to-an-okta-user, Administrator Role Assigned to an Okta User>> |Identifies when an administrator role is assigned to an Okta user. An adversary may attempt to assign an administrator role to an Okta user in order to assign additional permissions to a user account and maintain access to their target's environment. |[Elastic] [Okta] [SecOps] [Monitoring] [Continuous Monitoring]  |7.11.0 |102 <<administrator-role-assigned-to-an-okta-user-history, Version history>>
+|<<account-password-reset-remotely, Account Password Reset Remotely>> |Identifies an attempt to reset a potentially privileged account password remotely. Adversaries may manipulate account passwords to maintain access or evade password duration policies and preserve compromised credentials. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Impact] |8.3.0 |114
 
-|<<adobe-hijack-persistence, Adobe Hijack Persistence>> |Detects writing executable files that will be automatically launched by Adobe on launch. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.6.0 |102 <<adobe-hijack-persistence-history, Version history>>
+|<<account-or-group-discovery-via-built-in-tools, Account or Group Discovery via Built-In Tools>> |Adversaries may use built-in applications to get a listing of local system or domain accounts and groups. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |3
 
-|<<adversary-behavior-detected-elastic-endgame, Adversary Behavior - Detected - Elastic Endgame>> |Elastic Endgame detected an Adversary Behavior. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame]  |7.6.0 |101 <<adversary-behavior-detected-elastic-endgame-history, Version history>>
+|<<adfind-command-activity, AdFind Command Activity>> |This rule detects the Active Directory query tool, AdFind.exe. AdFind has legitimate purposes, but it is frequently leveraged by threat actors to perform post-exploitation Active Directory reconnaissance. The AdFind tool has been observed in Trickbot, Ryuk, Maze, and FIN6 campaigns. For Winlogbeat, this rule requires Sysmon. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<agent-spoofing-mismatched-agent-id, Agent Spoofing - Mismatched Agent ID>> |Detects events that have a mismatch on the expected event agent ID. The status "agent_id_mismatch" occurs when the expected agent ID associated with the API key does not match the actual agent ID in an event. This could indicate attempts to spoof events in order to masquerade actual activity to evade detection. |[Elastic] [Threat Detection] [Defense Evasion]  |7.14.0 |100 <<agent-spoofing-mismatched-agent-id-history, Version history>>
+|<<adding-hidden-file-attribute-via-attrib, Adding Hidden File Attribute via Attrib>> |Adversaries can add the 'hidden' attribute to files to hide them from the user in an attempt to evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Persistence], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<agent-spoofing-multiple-hosts-using-same-agent, Agent Spoofing - Multiple Hosts Using Same Agent>> |Detects when multiple hosts are using the same agent ID. This could occur in the event of an agent being taken over and used to inject illegitimate documents into an instance as an attempt to spoof events in order to masquerade actual activity to evade detection. |[Elastic] [Threat Detection] [Defense Evasion]  |7.14.0 |100 <<agent-spoofing-multiple-hosts-using-same-agent-history, Version history>>
+|<<adminsdholder-backdoor, AdminSDHolder Backdoor>> |Detects modifications in the AdminSDHolder object. Attackers can abuse the SDProp process to implement a persistent backdoor in Active Directory. SDProp compares the permissions on protected objects with those defined on the AdminSDHolder object. If the permissions on any of the protected accounts and groups do not match, the permissions on the protected accounts and groups are reset to match those of the domain's AdminSDHolder object, regaining their Administrative Privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Use Case: Active Directory Monitoring], [Data Source: Active Directory] |8.3.0 |106
 
-|<<anomalous-linux-compiler-activity, Anomalous Linux Compiler Activity>> |Looks for compiler activity by a user context which does not normally run compilers. This can be the result of ad-hoc software changes or unauthorized software deployment. This can also be due to local privilege elevation via locally run exploits or malware activity. |[Elastic] [Host] [Linux] [Threat Detection] [ML] [Resource Development]  |7.10.0 |100 <<anomalous-linux-compiler-activity-history, Version history>>
+|<<adminsdholder-sdprop-exclusion-added, AdminSDHolder SDProp Exclusion Added>> |Identifies a modification on the dsHeuristics attribute on the bit that holds the configuration of groups excluded from the SDProp process. The SDProp compares the permissions on protected objects with those defined on the AdminSDHolder object. If the permissions on any of the protected accounts and groups do not match, the permissions on the protected accounts and groups are reset to match those of the domain's AdminSDHolder object, meaning that groups excluded will remain unchanged. Attackers can abuse this misconfiguration to maintain long-term access to privileged accounts in these groups. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Active Directory], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring] |8.3.0 |110
 
-|<<anomalous-process-for-a-linux-population, Anomalous Process For a Linux Population>> |Searches for rare processes running on multiple Linux hosts in an entire fleet or network. This reduces the detection of false positives since automated maintenance processes usually only run occasionally on a single machine but are common to all or many hosts in a fleet. |[Elastic] [Host] [Linux] [Threat Detection] [ML] [Persistence]  |7.7.0 |100 <<anomalous-process-for-a-linux-population-history, Version history>>
+|<<administrator-privileges-assigned-to-an-okta-group, Administrator Privileges Assigned to an Okta Group>> |Detects when an administrator role is assigned to an Okta group. An adversary may attempt to assign administrator privileges to an Okta group in order to assign additional permissions to compromised user accounts and maintain access to their target organization. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Persistence] |8.10.0 |205
 
-|<<anomalous-process-for-a-windows-population, Anomalous Process For a Windows Population>> |Searches for rare processes running on multiple hosts in an entire fleet or network. This reduces the detection of false positives since automated maintenance processes usually only run occasionally on a single machine but are common to all or many hosts in a fleet. |[Elastic] [Host] [Windows] [Threat Detection] [ML] [Persistence]  |7.7.0 |100 <<anomalous-process-for-a-windows-population-history, Version history>>
+|<<administrator-role-assigned-to-an-okta-user, Administrator Role Assigned to an Okta User>> |Identifies when an administrator role is assigned to an Okta user. An adversary may attempt to assign an administrator role to an Okta user in order to assign additional permissions to a user account and maintain access to their target's environment. |[Data Source: Okta], [Use Case: Identity and Access Audit], [Tactic: Persistence] |8.10.0 |205
 
-|<<anomalous-windows-process-creation, Anomalous Windows Process Creation>> |Identifies unusual parent-child process relationships that can indicate malware execution or persistence mechanisms. Malicious scripts often call on other applications and processes as part of their exploit payload. For example, when a malicious Office document runs scripts as part of an exploit payload, Excel or Word may start a script interpreter process, which, in turn, runs a script that downloads and executes malware. Another common scenario is Outlook running an unusual process when malware is downloaded in an email. Monitoring and identifying anomalous process relationships is a method of detecting new and emerging malware that is not yet recognized by anti-virus scanners. |[Elastic] [Host] [Windows] [Threat Detection] [ML] [Persistence]  |7.7.0 |100 <<anomalous-windows-process-creation-history, Version history>>
+|<<adobe-hijack-persistence, Adobe Hijack Persistence>> |Detects writing executable files that will be automatically launched by Adobe on launch. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
 
-|<<apple-script-execution-followed-by-network-connection, Apple Script Execution followed by Network Connection>> |Detects execution via the Apple script interpreter (osascript) followed by a network connection from the same process within a short time period. Adversaries may use malicious scripts for execution and command and control. |[Elastic] [Host] [macOS] [Threat Detection] [Command and Control] [Execution]  |7.11.0 |100 <<apple-script-execution-followed-by-network-connection-history, Version history>>
+|<<adversary-behavior-detected-elastic-endgame, Adversary Behavior - Detected - Elastic Endgame>> |Elastic Endgame detected an Adversary Behavior. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame] |8.3.0 |104
 
-|<<apple-scripting-execution-with-administrator-privileges, Apple Scripting Execution with Administrator Privileges>> |Identifies execution of the Apple script interpreter (osascript) without a password prompt and with administrator privileges. |[Elastic] [Host] [macOS] [Threat Detection] [Execution] [Privilege Escalation]  |7.12.0 |100 <<apple-scripting-execution-with-administrator-privileges-history, Version history>>
+|<<agent-spoofing-mismatched-agent-id, Agent Spoofing - Mismatched Agent ID>> |Detects events that have a mismatch on the expected event agent ID. The status "agent_id_mismatch" occurs when the expected agent ID associated with the API key does not match the actual agent ID in an event. This could indicate attempts to spoof events in order to masquerade actual activity to evade detection. |[Use Case: Threat Detection], [Tactic: Defense Evasion] |8.3.0 |101
 
-|<<application-added-to-google-workspace-domain, Application Added to Google Workspace Domain>> |Detects when a Google marketplace application is added to the Google Workspace domain. An adversary may add a malicious application to an organization’s Google Workspace domain in order to maintain a presence in their target’s organization and steal data. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Configuration Audit] [Persistence]  |7.11.0 |101 <<application-added-to-google-workspace-domain-history, Version history>>
+|<<agent-spoofing-multiple-hosts-using-same-agent, Agent Spoofing - Multiple Hosts Using Same Agent>> |Detects when multiple hosts are using the same agent ID. This could occur in the event of an agent being taken over and used to inject illegitimate documents into an instance as an attempt to spoof events in order to masquerade actual activity to evade detection. |[Use Case: Threat Detection], [Tactic: Defense Evasion] |8.3.0 |101
 
-|<<application-removed-from-blocklist-in-google-workspace, Application Removed from Blocklist in Google Workspace>> |Google Workspace administrators may be aware of malicious applications within the Google marketplace and block these applications for user security purposes. An adversary, with administrative privileges, may remove this application from the explicit block list to allow distribution of the application amongst users. This may also indicate the unauthorized use of an application that had been previously blocked before by a user with admin privileges. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Configuration Audit] [Impair Defenses]  |8.5.0 |2 <<application-removed-from-blocklist-in-google-workspace-history, Version history>>
+|<<alternate-data-stream-creation-execution-at-volume-root-directory, Alternate Data Stream Creation/Execution at Volume Root Directory>> |Identifies the creation of an Alternate Data Stream (ADS) at a volume root directory, which can indicate the attempt to hide tools and malware, as ADSs created in this directory are not displayed by system utilities. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |1
 
-|<<attempt-to-create-okta-api-token, Attempt to Create Okta API Token>> |Detects attempts to create an Okta API token. An adversary may create an Okta API token to maintain access to an organization's network while they work to achieve their objectives. An attacker may abuse an API token to execute techniques such as creating user accounts or disabling security rules or policies. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring]  |7.9.0 |102 <<attempt-to-create-okta-api-token-history, Version history>>
+|<<anomalous-linux-compiler-activity, Anomalous Linux Compiler Activity>> |Looks for compiler activity by a user context which does not normally run compilers. This can be the result of ad-hoc software changes or unauthorized software deployment. This can also be due to local privilege elevation via locally run exploits or malware activity. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Resource Development] |8.3.0 |103
 
-|<<attempt-to-deactivate-mfa-for-an-okta-user-account, Attempt to Deactivate MFA for an Okta User Account>> |Detects attempts to deactivate multi-factor authentication (MFA) for an Okta user. An adversary may deactivate MFA for an Okta user account in order to weaken the authentication requirements for the account. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.9.0 |102 <<attempt-to-deactivate-mfa-for-an-okta-user-account-history, Version history>>
+|<<anomalous-process-for-a-linux-population, Anomalous Process For a Linux Population>> |Searches for rare processes running on multiple Linux hosts in an entire fleet or network. This reduces the detection of false positives since automated maintenance processes usually only run occasionally on a single machine but are common to all or many hosts in a fleet. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Persistence], [Resources: Investigation Guide] |8.3.0 |104
 
-|<<attempt-to-deactivate-an-okta-application, Attempt to Deactivate an Okta Application>> |Detects attempts to deactivate an Okta application. An adversary may attempt to modify, deactivate, or delete an Okta application in order to weaken an organization's security controls or disrupt their business operations. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring] [Impact]  |7.11.0 |102 <<attempt-to-deactivate-an-okta-application-history, Version history>>
+|<<anomalous-process-for-a-windows-population, Anomalous Process For a Windows Population>> |Searches for rare processes running on multiple hosts in an entire fleet or network. This reduces the detection of false positives since automated maintenance processes usually only run occasionally on a single machine but are common to all or many hosts in a fleet. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Persistence], [Tactic: Execution] |8.3.0 |105
 
-|<<attempt-to-deactivate-an-okta-network-zone, Attempt to Deactivate an Okta Network Zone>> |Detects attempts to deactivate an Okta network zone. Okta network zones can be configured to limit or restrict access to a network based on IP addresses or geolocations. An adversary may attempt to modify, delete, or deactivate an Okta network zone in order to remove or weaken an organization's security controls. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Network Security] [Defense Evasion]  |7.11.0 |102 <<attempt-to-deactivate-an-okta-network-zone-history, Version history>>
+|<<anomalous-windows-process-creation, Anomalous Windows Process Creation>> |Identifies unusual parent-child process relationships that can indicate malware execution or persistence mechanisms. Malicious scripts often call on other applications and processes as part of their exploit payload. For example, when a malicious Office document runs scripts as part of an exploit payload, Excel or Word may start a script interpreter process, which, in turn, runs a script that downloads and executes malware. Another common scenario is Outlook running an unusual process when malware is downloaded in an email. Monitoring and identifying anomalous process relationships is a method of detecting new and emerging malware that is not yet recognized by anti-virus scanners. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Persistence], [Resources: Investigation Guide] |8.3.0 |105
 
-|<<attempt-to-deactivate-an-okta-policy, Attempt to Deactivate an Okta Policy>> |Detects attempts to deactivate an Okta policy. An adversary may attempt to deactivate an Okta policy in order to weaken an organization's security controls. For example, an adversary may attempt to deactivate an Okta multi-factor authentication (MFA) policy in order to weaken the authentication requirements for user accounts. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring] [Defense Evasion]  |7.9.0 |102 <<attempt-to-deactivate-an-okta-policy-history, Version history>>
+|<<apple-script-execution-followed-by-network-connection, Apple Script Execution followed by Network Connection>> |Detects execution via the Apple script interpreter (osascript) followed by a network connection from the same process within a short time period. Adversaries may use malicious scripts for execution and command and control. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Command and Control], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<attempt-to-deactivate-an-okta-policy-rule, Attempt to Deactivate an Okta Policy Rule>> |Detects attempts to deactivate a rule within an Okta policy. An adversary may attempt to deactivate a rule within an Okta policy in order to remove or weaken an organization's security controls. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access] [Defense Evasion]  |7.9.0 |102 <<attempt-to-deactivate-an-okta-policy-rule-history, Version history>>
+|<<apple-scripting-execution-with-administrator-privileges, Apple Scripting Execution with Administrator Privileges>> |Identifies execution of the Apple script interpreter (osascript) without a password prompt and with administrator privileges. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.11.0 |207
 
-|<<attempt-to-delete-an-okta-application, Attempt to Delete an Okta Application>> |Detects attempts to delete an Okta application. An adversary may attempt to modify, deactivate, or delete an Okta application in order to weaken an organization's security controls or disrupt their business operations. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring] [Impact]  |7.11.0 |102 <<attempt-to-delete-an-okta-application-history, Version history>>
+|<<application-added-to-google-workspace-domain, Application Added to Google Workspace Domain>> |Detects when a Google marketplace application is added to the Google Workspace domain. An adversary may add a malicious application to an organization’s Google Workspace domain in order to maintain a presence in their target’s organization and steal data. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Configuration Audit], [Tactic: Persistence], [Resources: Investigation Guide] |8.4.0 |205
 
-|<<attempt-to-delete-an-okta-network-zone, Attempt to Delete an Okta Network Zone>> |Detects attempts to delete an Okta network zone. Okta network zones can be configured to limit or restrict access to a network based on IP addresses or geolocations. An adversary may attempt to modify, delete, or deactivate an Okta network zone in order to remove or weaken an organization's security controls. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Network Security] [Defense Evasion]  |7.11.0 |102 <<attempt-to-delete-an-okta-network-zone-history, Version history>>
+|<<application-removed-from-blocklist-in-google-workspace, Application Removed from Blocklist in Google Workspace>> |Google Workspace administrators may be aware of malicious applications within the Google marketplace and block these applications for user security purposes. An adversary, with administrative privileges, may remove this application from the explicit block list to allow distribution of the application amongst users. This may also indicate the unauthorized use of an application that had been previously blocked before by a user with admin privileges. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Configuration Audit], [Resources: Investigation Guide], [Tactic: Defense Evasion] |8.4.0 |106
 
-|<<attempt-to-delete-an-okta-policy, Attempt to Delete an Okta Policy>> |Detects attempts to delete an Okta policy. An adversary may attempt to delete an Okta policy in order to weaken an organization's security controls. For example, an adversary may attempt to delete an Okta multi-factor authentication (MFA) policy in order to weaken the authentication requirements for user accounts. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring] [Defense Evasion]  |7.9.0 |102 <<attempt-to-delete-an-okta-policy-history, Version history>>
+|<<archive-file-with-unusual-extension, Archive File with Unusual Extension>> |Identifies the creation of an archive file with an unusual extension. Attackers may attempt to evade detection by masquerading files using the file extension values used by image, audio, or document file types. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |2
 
-|<<attempt-to-delete-an-okta-policy-rule, Attempt to Delete an Okta Policy Rule>> |Detects attempts to delete a rule within an Okta policy. An adversary may attempt to delete an Okta policy rule in order to weaken an organization's security controls. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring] [Defense Evasion]  |7.11.0 |102 <<attempt-to-delete-an-okta-policy-rule-history, Version history>>
+|<<at-exe-command-lateral-movement, At.exe Command Lateral Movement>> |Identifies use of at.exe to interact with the task scheduler on remote hosts. Remote task creations, modifications or execution could be indicative of adversary lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend], [Rule Type: BBR], [Data Source: Elastic Endgame] |8.3.0 |3
 
-|<<attempt-to-disable-gatekeeper, Attempt to Disable Gatekeeper>> |Detects attempts to disable Gatekeeper on macOS. Gatekeeper is a security feature that's designed to ensure that only trusted software is run. Adversaries may attempt to disable Gatekeeper before executing malicious code. |[Elastic] [Host] [macOS] [Threat Detection] [Defense Evasion]  |7.12.0 |100 <<attempt-to-disable-gatekeeper-history, Version history>>
+|<<attempt-to-clear-kernel-ring-buffer, Attempt to Clear Kernel Ring Buffer>> |Monitors for the deletion of the kernel ring buffer events through dmesg. Attackers may clear kernel ring buffer events to evade detection after installing a Linux kernel module (LKM). |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |4
 
-|<<attempt-to-disable-syslog-service, Attempt to Disable Syslog Service>> |Adversaries may attempt to disable the syslog service in an attempt to an attempt to disrupt event logging and evade detection by security controls. |[Elastic] [Host] [Linux] [Threat Detection] [Defense Evasion]  |7.8.0 |100 <<attempt-to-disable-syslog-service-history, Version history>>
+|<<attempt-to-create-okta-api-token, Attempt to Create Okta API Token>> |Detects attempts to create an Okta API token. An adversary may create an Okta API token to maintain access to an organization's network while they work to achieve their objectives. An attacker may abuse an API token to execute techniques such as creating user accounts or disabling security rules or policies. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Persistence] |8.10.0 |205
 
-|<<attempt-to-enable-the-root-account, Attempt to Enable the Root Account>> |Identifies attempts to enable the root account using the dsenableroot command. This command may be abused by adversaries for persistence, as the root account is disabled by default. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<attempt-to-enable-the-root-account-history, Version history>>
+|<<attempt-to-deactivate-an-okta-application, Attempt to Deactivate an Okta Application>> |Detects attempts to deactivate an Okta application. An adversary may attempt to modify, deactivate, or delete an Okta application in order to weaken an organization's security controls or disrupt their business operations. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Impact] |8.10.0 |206
 
-|<<attempt-to-install-root-certificate, Attempt to Install Root Certificate>> |Adversaries may install a root certificate on a compromised system to avoid warnings when connecting to their command and control servers. Root certificates are used in public key cryptography to identify a root certificate authority (CA). When a root certificate is installed, the system or application will trust certificates in the root's chain of trust that have been signed by the root certificate. |[Elastic] [Host] [macOS] [Threat Detection] [Defense Evasion]  |7.12.0 |100 <<attempt-to-install-root-certificate-history, Version history>>
+|<<attempt-to-deactivate-an-okta-network-zone, Attempt to Deactivate an Okta Network Zone>> |Detects attempts to deactivate an Okta network zone. Okta network zones can be configured to limit or restrict access to a network based on IP addresses or geolocations. An adversary may attempt to modify, delete, or deactivate an Okta network zone in order to remove or weaken an organization's security controls. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Use Case: Network Security Monitoring], [Tactic: Defense Evasion] |8.10.0 |206
 
-|<<attempt-to-modify-an-okta-application, Attempt to Modify an Okta Application>> |Detects attempts to modify an Okta application. An adversary may attempt to modify, deactivate, or delete an Okta application in order to weaken an organization's security controls or disrupt their business operations. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring] [Impact]  |7.11.0 |102 <<attempt-to-modify-an-okta-application-history, Version history>>
+|<<attempt-to-deactivate-an-okta-policy, Attempt to Deactivate an Okta Policy>> |Detects attempts to deactivate an Okta policy. An adversary may attempt to deactivate an Okta policy in order to weaken an organization's security controls. For example, an adversary may attempt to deactivate an Okta multi-factor authentication (MFA) policy in order to weaken the authentication requirements for user accounts. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Defense Evasion] |8.10.0 |206
 
-|<<attempt-to-modify-an-okta-network-zone, Attempt to Modify an Okta Network Zone>> |Detects attempts to modify an Okta network zone. Okta network zones can be configured to limit or restrict access to a network based on IP addresses or geolocations. An adversary may attempt to modify, delete, or deactivate an Okta network zone in order to remove or weaken an organization's security controls. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Network Security] [Defense Evasion]  |7.9.0 |102 <<attempt-to-modify-an-okta-network-zone-history, Version history>>
+|<<attempt-to-deactivate-an-okta-policy-rule, Attempt to Deactivate an Okta Policy Rule>> |Detects attempts to deactivate a rule within an Okta policy. An adversary may attempt to deactivate a rule within an Okta policy in order to remove or weaken an organization's security controls. |[Use Case: Identity and Access Audit], [Tactic: Defense Evasion], [Data Source: Okta] |8.10.0 |207
 
-|<<attempt-to-modify-an-okta-policy, Attempt to Modify an Okta Policy>> |Detects attempts to modify an Okta policy. An adversary may attempt to modify an Okta policy in order to weaken an organization's security controls. For example, an adversary may attempt to modify an Okta multi-factor authentication (MFA) policy in order to weaken the authentication requirements for user accounts. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring] [Defense Evasion]  |7.9.0 |102 <<attempt-to-modify-an-okta-policy-history, Version history>>
+|<<attempt-to-delete-an-okta-application, Attempt to Delete an Okta Application>> |Detects attempts to delete an Okta application. An adversary may attempt to modify, deactivate, or delete an Okta application in order to weaken an organization's security controls or disrupt their business operations. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Impact] |8.10.0 |205
 
-|<<attempt-to-modify-an-okta-policy-rule, Attempt to Modify an Okta Policy Rule>> |Detects attempts to modify a rule within an Okta policy. An adversary may attempt to modify an Okta policy rule in order to weaken an organization's security controls. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access] [Defense Evasion]  |7.9.0 |102 <<attempt-to-modify-an-okta-policy-rule-history, Version history>>
+|<<attempt-to-delete-an-okta-network-zone, Attempt to Delete an Okta Network Zone>> |Detects attempts to delete an Okta network zone. Okta network zones can be configured to limit or restrict access to a network based on IP addresses or geolocations. An adversary may attempt to modify, delete, or deactivate an Okta network zone in order to remove or weaken an organization's security controls. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Use Case: Network Security Monitoring], [Tactic: Defense Evasion] |8.10.0 |206
 
-|<<attempt-to-mount-smb-share-via-command-line, Attempt to Mount SMB Share via Command Line>> |Identifies the execution of macOS built-in commands to mount a Server Message Block (SMB) network share. Adversaries may use valid accounts to interact with a remote network share using SMB. |[Elastic] [Host] [macOS] [Threat Detection] [Lateral Movement]  |7.12.0 |100 <<attempt-to-mount-smb-share-via-command-line-history, Version history>>
+|<<attempt-to-delete-an-okta-policy, Attempt to Delete an Okta Policy>> |Detects attempts to delete an Okta policy. An adversary may attempt to delete an Okta policy in order to weaken an organization's security controls. For example, an adversary may attempt to delete an Okta multi-factor authentication (MFA) policy in order to weaken the authentication requirements for user accounts. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Defense Evasion] |8.10.0 |206
 
-|<<attempt-to-remove-file-quarantine-attribute, Attempt to Remove File Quarantine Attribute>> |Identifies a potential Gatekeeper bypass. In macOS, when applications or programs are downloaded from the internet, there is a quarantine flag set on the file. This attribute is read by Apple's Gatekeeper defense program at execution time. An adversary may disable this attribute to evade defenses. |[Elastic] [Host] [macOS] [Threat Detection] [Defense Evasion]  |7.11.0 |100 <<attempt-to-remove-file-quarantine-attribute-history, Version history>>
+|<<attempt-to-delete-an-okta-policy-rule, Attempt to Delete an Okta Policy Rule>> |Detects attempts to delete a rule within an Okta policy. An adversary may attempt to delete an Okta policy rule in order to weaken an organization's security controls. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Defense Evasion] |8.10.0 |206
 
-|<<attempt-to-reset-mfa-factors-for-an-okta-user-account, Attempt to Reset MFA Factors for an Okta User Account>> |Detects attempts to reset an Okta user's enrolled multi-factor authentication (MFA) factors. An adversary may attempt to reset the MFA factors for an Okta user's account in order to register new MFA factors and abuse the account to blend in with normal activity in the victim's environment. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.9.0 |102 <<attempt-to-reset-mfa-factors-for-an-okta-user-account-history, Version history>>
+|<<attempt-to-disable-gatekeeper, Attempt to Disable Gatekeeper>> |Detects attempts to disable Gatekeeper on macOS. Gatekeeper is a security feature that's designed to ensure that only trusted software is run. Adversaries may attempt to disable Gatekeeper before executing malicious code. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<attempt-to-revoke-okta-api-token, Attempt to Revoke Okta API Token>> |Identifies attempts to revoke an Okta API token. An adversary may attempt to revoke or delete an Okta API token to disrupt an organization's business operations. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring]  |7.9.0 |102 <<attempt-to-revoke-okta-api-token-history, Version history>>
+|<<attempt-to-disable-iptables-or-firewall, Attempt to Disable IPTables or Firewall>> |Adversaries may attempt to disable the iptables or firewall service in an attempt to affect how a host is allowed to receive or send network traffic. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |7
 
-|<<attempt-to-unload-elastic-endpoint-security-kernel-extension, Attempt to Unload Elastic Endpoint Security Kernel Extension>> |Identifies attempts to unload the Elastic Endpoint Security kernel extension via the kextunload command. |[Elastic] [Host] [macOS] [Threat Detection] [Defense Evasion]  |7.12.0 |100 <<attempt-to-unload-elastic-endpoint-security-kernel-extension-history, Version history>>
+|<<attempt-to-disable-syslog-service, Attempt to Disable Syslog Service>> |Adversaries may attempt to disable the syslog service in an attempt to an attempt to disrupt event logging and evade detection by security controls. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<attempted-bypass-of-okta-mfa, Attempted Bypass of Okta MFA>> |Detects attempts to bypass Okta multi-factor authentication (MFA). An adversary may attempt to bypass the Okta MFA policies configured for an organization in order to obtain unauthorized access to an application. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.9.0 |102 <<attempted-bypass-of-okta-mfa-history, Version history>>
+|<<attempt-to-enable-the-root-account, Attempt to Enable the Root Account>> |Identifies attempts to enable the root account using the dsenableroot command. This command may be abused by adversaries for persistence, as the root account is disabled by default. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<attempts-to-brute-force-a-microsoft-365-user-account, Attempts to Brute Force a Microsoft 365 User Account>> |Identifies attempts to brute force a Microsoft 365 user account. An adversary may attempt a brute force attack to obtain unauthorized access to user accounts. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.11.0 |101 <<attempts-to-brute-force-a-microsoft-365-user-account-history, Version history>>
+|<<attempt-to-install-kali-linux-via-wsl, Attempt to Install Kali Linux via WSL>> |Detects attempts to install or use Kali Linux via Windows Subsystem for Linux. Adversaries may enable and use WSL for Linux to avoid detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |7
 
-|<<attempts-to-brute-force-an-okta-user-account, Attempts to Brute Force an Okta User Account>> |Identifies when an Okta user account is locked out 3 times within a 3 hour window. An adversary may attempt a brute force or password spraying attack to obtain unauthorized access to user accounts. The default Okta authentication policy ensures that a user account is locked out after 10 failed authentication attempts. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |102 <<attempts-to-brute-force-an-okta-user-account-history, Version history>>
+|<<attempt-to-install-root-certificate, Attempt to Install Root Certificate>> |Adversaries may install a root certificate on a compromised system to avoid warnings when connecting to their command and control servers. Root certificates are used in public key cryptography to identify a root certificate authority (CA). When a root certificate is installed, the system or application will trust certificates in the root's chain of trust that have been signed by the root certificate. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<authorization-plugin-modification, Authorization Plugin Modification>> |Authorization plugins are used to extend the authorization services API and implement mechanisms that are not natively supported by the OS, such as multi-factor authentication with third party software. Adversaries may abuse this feature to persist and/or collect clear text credentials as they traverse the registered plugins during user logon. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<authorization-plugin-modification-history, Version history>>
+|<<attempt-to-modify-an-okta-application, Attempt to Modify an Okta Application>> |Detects attempts to modify an Okta application. An adversary may attempt to modify, deactivate, or delete an Okta application in order to weaken an organization's security controls or disrupt their business operations. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Impact] |8.10.0 |205
 
-|<<azure-ad-global-administrator-role-assigned, Azure AD Global Administrator Role Assigned>> |In Azure Active Directory (Azure AD), permissions to manage resources are assigned using roles. The Global Administrator is a role that enables users to have access to all administrative features in Azure AD and services that use Azure AD identities like the Microsoft 365 Defender portal, the Microsoft 365 compliance center, Exchange, SharePoint Online, and Skype for Business Online. Attackers can add users as Global Administrators to maintain access and manage all subscriptions and their settings and resources. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access]  |8.1.0 |101 <<azure-ad-global-administrator-role-assigned-history, Version history>>
+|<<attempt-to-modify-an-okta-network-zone, Attempt to Modify an Okta Network Zone>> |Detects attempts to modify an Okta network zone. Okta network zones can be configured to limit or restrict access to a network based on IP addresses or geolocations. An adversary may attempt to modify, delete, or deactivate an Okta network zone in order to remove or weaken an organization's security controls. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Use Case: Network Security Monitoring], [Tactic: Defense Evasion] |8.10.0 |206
 
-|<<azure-active-directory-high-risk-sign-in, Azure Active Directory High Risk Sign-in>> |Identifies high risk Azure Active Directory (AD) sign-ins by leveraging Microsoft's Identity Protection machine learning and heuristics. Identity Protection categorizes risk into three tiers: low, medium, and high. While Microsoft does not provide specific details about how risk is calculated, each level brings higher confidence that the user or sign-in is compromised. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access] [Investigation Guide]  |7.12.0 |103 <<azure-active-directory-high-risk-sign-in-history, Version history>>
+|<<attempt-to-modify-an-okta-policy, Attempt to Modify an Okta Policy>> |Detects attempts to modify an Okta policy. An adversary may attempt to modify an Okta policy in order to weaken an organization's security controls. For example, an adversary may attempt to modify an Okta multi-factor authentication (MFA) policy in order to weaken the authentication requirements for user accounts. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Defense Evasion] |8.10.0 |206
 
-|<<azure-active-directory-high-risk-user-sign-in-heuristic, Azure Active Directory High Risk User Sign-in Heuristic>> |Identifies high risk Azure Active Directory (AD) sign-ins by leveraging Microsoft Identity Protection machine learning and heuristics. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access] [Investigation Guide]  |8.0.0 |103 <<azure-active-directory-high-risk-user-sign-in-heuristic-history, Version history>>
+|<<attempt-to-modify-an-okta-policy-rule, Attempt to Modify an Okta Policy Rule>> |Detects attempts to modify a rule within an Okta policy. An adversary may attempt to modify an Okta policy rule in order to weaken an organization's security controls. |[Use Case: Identity and Access Audit], [Tactic: Defense Evasion], [Data Source: Okta] |8.10.0 |207
 
-|<<azure-active-directory-powershell-sign-in, Azure Active Directory PowerShell Sign-in>> |Identifies a sign-in using the Azure Active Directory PowerShell module. PowerShell for Azure Active Directory allows for managing settings from the command line, which is intended for users who are members of an admin role. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access] [Investigation Guide]  |7.11.0 |103 <<azure-active-directory-powershell-sign-in-history, Version history>>
+|<<attempt-to-mount-smb-share-via-command-line, Attempt to Mount SMB Share via Command Line>> |Identifies the execution of macOS built-in commands to mount a Server Message Block (SMB) network share. Adversaries may use valid accounts to interact with a remote network share using SMB. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<azure-alert-suppression-rule-created-or-modified, Azure Alert Suppression Rule Created or Modified>> |Identifies the creation of suppression rules in Azure. Suppression rules are a mechanism used to suppress alerts previously identified as false positives or too noisy to be in production. This mechanism can be abused or mistakenly configured, resulting in defense evasions and loss of security visibility. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Configuration Audit]  |8.0.0 |101 <<azure-alert-suppression-rule-created-or-modified-history, Version history>>
+|<<attempt-to-reset-mfa-factors-for-an-okta-user-account, Attempt to Reset MFA Factors for an Okta User Account>> |Detects attempts to reset an Okta user's enrolled multi-factor authentication (MFA) factors. An adversary may attempt to reset the MFA factors for an Okta user's account in order to register new MFA factors and abuse the account to blend in with normal activity in the victim's environment. |[Tactic: Persistence], [Use Case: Identity and Access Audit], [Data Source: Okta] |8.10.0 |206
 
-|<<azure-application-credential-modification, Azure Application Credential Modification>> |Identifies when a new credential is added to an application in Azure. An application may use a certificate or secret string to prove its identity when requesting a token. Multiple certificates and secrets can be added for an application and an adversary may abuse this by creating an additional authentication method to evade defenses or persist in an environment. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.11.0 |101 <<azure-application-credential-modification-history, Version history>>
+|<<attempt-to-revoke-okta-api-token, Attempt to Revoke Okta API Token>> |Identifies attempts to revoke an Okta API token. An adversary may attempt to revoke or delete an Okta API token to disrupt an organization's business operations. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Impact] |8.10.0 |206
 
-|<<azure-automation-account-created, Azure Automation Account Created>> |Identifies when an Azure Automation account is created. Azure Automation accounts can be used to automate management tasks and orchestrate actions across systems. An adversary may create an Automation account in order to maintain persistence in their target's environment. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |101 <<azure-automation-account-created-history, Version history>>
+|<<attempt-to-unload-elastic-endpoint-security-kernel-extension, Attempt to Unload Elastic Endpoint Security Kernel Extension>> |Identifies attempts to unload the Elastic Endpoint Security kernel extension via the kextunload command. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<azure-automation-runbook-created-or-modified, Azure Automation Runbook Created or Modified>> |Identifies when an Azure Automation runbook is created or modified. An adversary may create or modify an Azure Automation runbook to execute malicious code and maintain persistence in their target's environment. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.10.0 |101 <<azure-automation-runbook-created-or-modified-history, Version history>>
+|<<attempted-bypass-of-okta-mfa, Attempted Bypass of Okta MFA>> |Detects attempts to bypass Okta multi-factor authentication (MFA). An adversary may attempt to bypass the Okta MFA policies configured for an organization in order to obtain unauthorized access to an application. |[Data Source: Okta], [Use Case: Identity and Access Audit], [Tactic: Credential Access] |8.10.0 |207
 
-|<<azure-automation-runbook-deleted, Azure Automation Runbook Deleted>> |Identifies when an Azure Automation runbook is deleted. An adversary may delete an Azure Automation runbook in order to disrupt their target's automated business operations or to remove a malicious runbook for defense evasion. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Configuration Audit] [Defense Evasion]  |7.10.0 |101 <<azure-automation-runbook-deleted-history, Version history>>
+|<<attempted-private-key-access, Attempted Private Key Access>> |Attackers may try to access private keys, e.g. ssh, in order to gain further authenticated access to the environment. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |3
 
-|<<azure-automation-webhook-created, Azure Automation Webhook Created>> |Identifies when an Azure Automation webhook is created. Azure Automation runbooks can be configured to execute via a webhook. A webhook uses a custom URL passed to Azure Automation along with a data payload specific to the runbook. An adversary may create a webhook in order to trigger a runbook that contains malicious code. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.10.0 |101 <<azure-automation-webhook-created-history, Version history>>
+|<<attempts-to-brute-force-a-microsoft-365-user-account, Attempts to Brute Force a Microsoft 365 User Account>> |Identifies attempts to brute force a Microsoft 365 user account. An adversary may attempt a brute force attack to obtain unauthorized access to user accounts. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Identity and Access Audit], [Tactic: Credential Access] |8.8.0 |207
 
-|<<azure-blob-container-access-level-modification, Azure Blob Container Access Level Modification>> |Identifies changes to container access levels in Azure. Anonymous public read access to containers and blobs in Azure is a way to share data broadly, but can present a security risk if access to sensitive data is not managed judiciously. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Asset Visibility]  |7.10.0 |101 <<azure-blob-container-access-level-modification-history, Version history>>
+|<<attempts-to-brute-force-an-okta-user-account, Attempts to Brute Force an Okta User Account>> |Identifies when an Okta user account is locked out 3 times within a 3 hour window. An adversary may attempt a brute force or password spraying attack to obtain unauthorized access to user accounts. The default Okta authentication policy ensures that a user account is locked out after 10 failed authentication attempts. |[Use Case: Identity and Access Audit], [Tactic: Credential Access], [Data Source: Okta] |8.10.0 |208
 
-|<<azure-blob-permissions-modification, Azure Blob Permissions Modification>> |Identifies when the Azure role-based access control (Azure RBAC) permissions are modified for an Azure Blob. An adversary may modify the permissions on a blob to weaken their target's security controls or an administrator may inadvertently modify the permissions, which could lead to data exposure or loss. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.16.0 |101 <<azure-blob-permissions-modification-history, Version history>>
+|<<authorization-plugin-modification, Authorization Plugin Modification>> |Authorization plugins are used to extend the authorization services API and implement mechanisms that are not natively supported by the OS, such as multi-factor authentication with third party software. Adversaries may abuse this feature to persist and/or collect clear text credentials as they traverse the registered plugins during user logon. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<azure-command-execution-on-virtual-machine, Azure Command Execution on Virtual Machine>> |Identifies command execution on a virtual machine (VM) in Azure. A Virtual Machine Contributor role lets you manage virtual machines, but not access them, nor access the virtual network or storage account they’re connected to. However, commands can be run via PowerShell on the VM, which execute as System. Other roles, such as certain Administrator roles may be able to execute commands on a VM as well. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.10.0 |101 <<azure-command-execution-on-virtual-machine-history, Version history>>
+|<<azure-ad-global-administrator-role-assigned, Azure AD Global Administrator Role Assigned>> |In Azure Active Directory (Azure AD), permissions to manage resources are assigned using roles. The Global Administrator is a role that enables users to have access to all administrative features in Azure AD and services that use Azure AD identities like the Microsoft 365 Defender portal, the Microsoft 365 compliance center, Exchange, SharePoint Online, and Skype for Business Online. Attackers can add users as Global Administrators to maintain access and manage all subscriptions and their settings and resources. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Tactic: Persistence] |8.3.0 |102
 
-|<<azure-conditional-access-policy-modified, Azure Conditional Access Policy Modified>> |Identifies when an Azure Conditional Access policy is modified. Azure Conditional Access policies control access to resources via if-then statements. For example, if a user wants to access a resource, then they must complete an action such as using multi-factor authentication to access it. An adversary may modify a Conditional Access policy in order to weaken their target's security controls. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.10.0 |101 <<azure-conditional-access-policy-modified-history, Version history>>
+|<<azure-active-directory-high-risk-sign-in, Azure Active Directory High Risk Sign-in>> |Identifies high risk Azure Active Directory (AD) sign-ins by leveraging Microsoft's Identity Protection machine learning and heuristics. Identity Protection categorizes risk into three tiers: low, medium, and high. While Microsoft does not provide specific details about how risk is calculated, each level brings higher confidence that the user or sign-in is compromised. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Initial Access] |8.3.0 |105
 
-|<<azure-diagnostic-settings-deletion, Azure Diagnostic Settings Deletion>> |Identifies the deletion of diagnostic settings in Azure, which send platform logs and metrics to different destinations. An adversary may delete diagnostic settings in an attempt to evade defenses. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Monitoring]  |7.10.0 |101 <<azure-diagnostic-settings-deletion-history, Version history>>
+|<<azure-active-directory-high-risk-user-sign-in-heuristic, Azure Active Directory High Risk User Sign-in Heuristic>> |Identifies high risk Azure Active Directory (AD) sign-ins by leveraging Microsoft Identity Protection machine learning and heuristics. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Initial Access] |8.3.0 |105
 
-|<<azure-event-hub-authorization-rule-created-or-updated, Azure Event Hub Authorization Rule Created or Updated>> |Identifies when an Event Hub Authorization Rule is created or updated in Azure. An authorization rule is associated with specific rights, and carries a pair of cryptographic keys. When you create an Event Hubs namespace, a policy rule named RootManageSharedAccessKey is created for the namespace. This has manage permissions for the entire namespace and it's recommended that you treat this rule like an administrative root account and don't use it in your application. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.10.0 |101 <<azure-event-hub-authorization-rule-created-or-updated-history, Version history>>
+|<<azure-active-directory-powershell-sign-in, Azure Active Directory PowerShell Sign-in>> |Identifies a sign-in using the Azure Active Directory PowerShell module. PowerShell for Azure Active Directory allows for managing settings from the command line, which is intended for users who are members of an admin role. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Initial Access] |8.3.0 |105
 
-|<<azure-event-hub-deletion, Azure Event Hub Deletion>> |Identifies an Event Hub deletion in Azure. An Event Hub is an event processing service that ingests and processes large volumes of events and data. An adversary may delete an Event Hub in an attempt to evade detection. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.10.0 |101 <<azure-event-hub-deletion-history, Version history>>
+|<<azure-alert-suppression-rule-created-or-modified, Azure Alert Suppression Rule Created or Modified>> |Identifies the creation of suppression rules in Azure. Suppression rules are a mechanism used to suppress alerts previously identified as false positives or too noisy to be in production. This mechanism can be abused or mistakenly configured, resulting in defense evasions and loss of security visibility. |[Domain: Cloud], [Data Source: Azure], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.3.0 |102
 
-|<<azure-external-guest-user-invitation, Azure External Guest User Invitation>> |Identifies an invitation to an external user in Azure Active Directory (AD). Azure AD is extended to include collaboration, allowing you to invite people from outside your organization to be guest users in your cloud account. Unless there is a business need to provision guest access, it is best practice avoid creating guest users. Guest users could potentially be overlooked indefinitely leading to a potential vulnerability. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |101 <<azure-external-guest-user-invitation-history, Version history>>
+|<<azure-application-credential-modification, Azure Application Credential Modification>> |Identifies when a new credential is added to an application in Azure. An application may use a certificate or secret string to prove its identity when requesting a token. Multiple certificates and secrets can be added for an application and an adversary may abuse this by creating an additional authentication method to evade defenses or persist in an environment. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Tactic: Defense Evasion] |8.3.0 |102
 
-|<<azure-firewall-policy-deletion, Azure Firewall Policy Deletion>> |Identifies the deletion of a firewall policy in Azure. An adversary may delete a firewall policy in an attempt to evade defenses and/or to eliminate barriers to their objective. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Network Security]  |7.10.0 |101 <<azure-firewall-policy-deletion-history, Version history>>
+|<<azure-automation-account-created, Azure Automation Account Created>> |Identifies when an Azure Automation account is created. Azure Automation accounts can be used to automate management tasks and orchestrate actions across systems. An adversary may create an Automation account in order to maintain persistence in their target's environment. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Tactic: Persistence] |8.3.0 |102
 
-|<<azure-frontdoor-web-application-firewall-waf-policy-deleted, Azure Frontdoor Web Application Firewall (WAF) Policy Deleted>> |Identifies the deletion of a Frontdoor Web Application Firewall (WAF) Policy in Azure. An adversary may delete a Frontdoor Web Application Firewall (WAF) Policy in an attempt to evade defenses and/or to eliminate barriers to their objective. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Network Security]  |7.16.0 |101 <<azure-frontdoor-web-application-firewall-waf-policy-deleted-history, Version history>>
+|<<azure-automation-runbook-created-or-modified, Azure Automation Runbook Created or Modified>> |Identifies when an Azure Automation runbook is created or modified. An adversary may create or modify an Azure Automation runbook to execute malicious code and maintain persistence in their target's environment. |[Domain: Cloud], [Data Source: Azure], [Use Case: Configuration Audit], [Tactic: Persistence] |8.3.0 |102
 
-|<<azure-full-network-packet-capture-detected, Azure Full Network Packet Capture Detected>> |Identifies potential full network packet capture in Azure. Packet Capture is an Azure Network Watcher feature that can be used to inspect network traffic. This feature can potentially be abused to read sensitive data from unencrypted internal traffic. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Monitoring]  |7.16.0 |101 <<azure-full-network-packet-capture-detected-history, Version history>>
+|<<azure-automation-runbook-deleted, Azure Automation Runbook Deleted>> |Identifies when an Azure Automation runbook is deleted. An adversary may delete an Azure Automation runbook in order to disrupt their target's automated business operations or to remove a malicious runbook for defense evasion. |[Domain: Cloud], [Data Source: Azure], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.3.0 |102
 
-|<<azure-global-administrator-role-addition-to-pim-user, Azure Global Administrator Role Addition to PIM User>> |Identifies an Azure Active Directory (AD) Global Administrator role addition to a Privileged Identity Management (PIM) user account. PIM is a service that enables you to manage, control, and monitor access to important resources in an organization. Users who are assigned to the Global administrator role can read and modify any administrative setting in your Azure AD organization. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |101 <<azure-global-administrator-role-addition-to-pim-user-history, Version history>>
+|<<azure-automation-webhook-created, Azure Automation Webhook Created>> |Identifies when an Azure Automation webhook is created. Azure Automation runbooks can be configured to execute via a webhook. A webhook uses a custom URL passed to Azure Automation along with a data payload specific to the runbook. An adversary may create a webhook in order to trigger a runbook that contains malicious code. |[Domain: Cloud], [Data Source: Azure], [Use Case: Configuration Audit], [Tactic: Persistence] |8.3.0 |102
 
-|<<azure-key-vault-modified, Azure Key Vault Modified>> |Identifies modifications to a Key Vault in Azure. The Key Vault is a service that safeguards encryption keys and secrets like certificates, connection strings, and passwords. Because this data is sensitive and business critical, access to key vaults should be secured to allow only authorized applications and users. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Data Protection]  |7.10.0 |102 <<azure-key-vault-modified-history, Version history>>
+|<<azure-blob-container-access-level-modification, Azure Blob Container Access Level Modification>> |Identifies changes to container access levels in Azure. Anonymous public read access to containers and blobs in Azure is a way to share data broadly, but can present a security risk if access to sensitive data is not managed judiciously. |[Domain: Cloud], [Data Source: Azure], [Use Case: Asset Visibility], [Tactic: Discovery] |8.3.0 |102
 
-|<<azure-kubernetes-events-deleted, Azure Kubernetes Events Deleted>> |Identifies when events are deleted in Azure Kubernetes. Kubernetes events are objects that log any state changes. Example events are a container creation, an image pull, or a pod scheduling on a node. An adversary may delete events in Azure Kubernetes in an attempt to evade detection. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.16.0 |101 <<azure-kubernetes-events-deleted-history, Version history>>
+|<<azure-blob-permissions-modification, Azure Blob Permissions Modification>> |Identifies when the Azure role-based access control (Azure RBAC) permissions are modified for an Azure Blob. An adversary may modify the permissions on a blob to weaken their target's security controls or an administrator may inadvertently modify the permissions, which could lead to data exposure or loss. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |103
 
-|<<azure-kubernetes-pods-deleted, Azure Kubernetes Pods Deleted>> |Identifies the deletion of Azure Kubernetes Pods. Adversaries may delete a Kubernetes pod to disrupt the normal behavior of the environment. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Asset Visibility]  |7.16.0 |101 <<azure-kubernetes-pods-deleted-history, Version history>>
+|<<azure-command-execution-on-virtual-machine, Azure Command Execution on Virtual Machine>> |Identifies command execution on a virtual machine (VM) in Azure. A Virtual Machine Contributor role lets you manage virtual machines, but not access them, nor access the virtual network or storage account they’re connected to. However, commands can be run via PowerShell on the VM, which execute as System. Other roles, such as certain Administrator roles may be able to execute commands on a VM as well. |[Domain: Cloud], [Data Source: Azure], [Use Case: Log Auditing], [Tactic: Execution] |8.3.0 |102
 
-|<<azure-kubernetes-rolebindings-created, Azure Kubernetes Rolebindings Created>> |Identifies the creation of role binding or cluster role bindings. You can assign these roles to Kubernetes subjects (users, groups, or service accounts) with role bindings and cluster role bindings. An adversary who has permissions to create bindings and cluster-bindings in the cluster can create a binding to the cluster-admin ClusterRole or to other high privileges roles. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access]  |8.0.0 |101 <<azure-kubernetes-rolebindings-created-history, Version history>>
+|<<azure-conditional-access-policy-modified, Azure Conditional Access Policy Modified>> |Identifies when an Azure Conditional Access policy is modified. Azure Conditional Access policies control access to resources via if-then statements. For example, if a user wants to access a resource, then they must complete an action such as using multi-factor authentication to access it. An adversary may modify a Conditional Access policy in order to weaken their target's security controls. |[Domain: Cloud], [Data Source: Azure], [Use Case: Configuration Audit], [Tactic: Persistence] |8.3.0 |102
 
-|<<azure-network-watcher-deletion, Azure Network Watcher Deletion>> |Identifies the deletion of a Network Watcher in Azure. Network Watchers are used to monitor, diagnose, view metrics, and enable or disable logs for resources in an Azure virtual network. An adversary may delete a Network Watcher in an attempt to evade defenses. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Network Security]  |7.10.0 |101 <<azure-network-watcher-deletion-history, Version history>>
+|<<azure-diagnostic-settings-deletion, Azure Diagnostic Settings Deletion>> |Identifies the deletion of diagnostic settings in Azure, which send platform logs and metrics to different destinations. An adversary may delete diagnostic settings in an attempt to evade defenses. |[Domain: Cloud], [Data Source: Azure], [Tactic: Defense Evasion] |8.3.0 |102
 
-|<<azure-privilege-identity-management-role-modified, Azure Privilege Identity Management Role Modified>> |Azure Active Directory (AD) Privileged Identity Management (PIM) is a service that enables you to manage, control, and monitor access to important resources in an organization. PIM can be used to manage the built-in Azure resource roles such as Global Administrator and Application Administrator. An adversary may add a user to a PIM role in order to maintain persistence in their target's environment or modify a PIM role to weaken their target's security controls. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access] [Investigation Guide]  |7.10.0 |103 <<azure-privilege-identity-management-role-modified-history, Version history>>
+|<<azure-event-hub-authorization-rule-created-or-updated, Azure Event Hub Authorization Rule Created or Updated>> |Identifies when an Event Hub Authorization Rule is created or updated in Azure. An authorization rule is associated with specific rights, and carries a pair of cryptographic keys. When you create an Event Hubs namespace, a policy rule named RootManageSharedAccessKey is created for the namespace. This has manage permissions for the entire namespace and it's recommended that you treat this rule like an administrative root account and don't use it in your application. |[Domain: Cloud], [Data Source: Azure], [Use Case: Log Auditing], [Tactic: Collection] |8.3.0 |103
 
-|<<azure-resource-group-deletion, Azure Resource Group Deletion>> |Identifies the deletion of a resource group in Azure, which includes all resources within the group. Deletion is permanent and irreversible. An adversary may delete a resource group in an attempt to evade defenses or intentionally destroy data. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.10.0 |101 <<azure-resource-group-deletion-history, Version history>>
+|<<azure-event-hub-deletion, Azure Event Hub Deletion>> |Identifies an Event Hub deletion in Azure. An Event Hub is an event processing service that ingests and processes large volumes of events and data. An adversary may delete an Event Hub in an attempt to evade detection. |[Domain: Cloud], [Data Source: Azure], [Use Case: Log Auditing], [Tactic: Defense Evasion] |8.3.0 |102
 
-|<<azure-service-principal-addition, Azure Service Principal Addition>> |Identifies when a new service principal is added in Azure. An application, hosted service, or automated tool that accesses or modifies resources needs an identity created. This identity is known as a service principal. For security reasons, it's always recommended to use service principals with automated tools rather than allowing them to log in with a user identity. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access] [Investigation Guide]  |7.11.0 |103 <<azure-service-principal-addition-history, Version history>>
+|<<azure-external-guest-user-invitation, Azure External Guest User Invitation>> |Identifies an invitation to an external user in Azure Active Directory (AD). Azure AD is extended to include collaboration, allowing you to invite people from outside your organization to be guest users in your cloud account. Unless there is a business need to provision guest access, it is best practice avoid creating guest users. Guest users could potentially be overlooked indefinitely leading to a potential vulnerability. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Tactic: Initial Access] |8.3.0 |102
 
-|<<azure-service-principal-credentials-added, Azure Service Principal Credentials Added>> |Identifies when new Service Principal credentials have been added in Azure. In most organizations, credentials will be added to service principals infrequently. Hijacking an application (by adding a rogue secret or certificate) with granted permissions will allow the attacker to access data that is normally protected by MFA requirements. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.14.0 |101 <<azure-service-principal-credentials-added-history, Version history>>
+|<<azure-firewall-policy-deletion, Azure Firewall Policy Deletion>> |Identifies the deletion of a firewall policy in Azure. An adversary may delete a firewall policy in an attempt to evade defenses and/or to eliminate barriers to their objective. |[Domain: Cloud], [Data Source: Azure], [Use Case: Network Security Monitoring], [Tactic: Defense Evasion] |8.3.0 |102
 
-|<<azure-storage-account-key-regenerated, Azure Storage Account Key Regenerated>> |Identifies a rotation to storage account access keys in Azure. Regenerating access keys can affect any applications or Azure services that are dependent on the storage account key. Adversaries may regenerate a key as a means of acquiring credentials to access systems and resources. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |101 <<azure-storage-account-key-regenerated-history, Version history>>
+|<<azure-frontdoor-web-application-firewall-waf-policy-deleted, Azure Frontdoor Web Application Firewall (WAF) Policy Deleted>> |Identifies the deletion of a Frontdoor Web Application Firewall (WAF) Policy in Azure. An adversary may delete a Frontdoor Web Application Firewall (WAF) Policy in an attempt to evade defenses and/or to eliminate barriers to their objective. |[Domain: Cloud], [Data Source: Azure], [Use Case: Network Security Monitoring], [Tactic: Defense Evasion] |8.3.0 |102
 
-|<<azure-virtual-network-device-modified-or-deleted, Azure Virtual Network Device Modified or Deleted>> |Identifies when a virtual network device is modified or deleted. This can be a network virtual appliance, virtual hub, or virtual router. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Network Security] [Impact]  |7.16.0 |101 <<azure-virtual-network-device-modified-or-deleted-history, Version history>>
+|<<azure-full-network-packet-capture-detected, Azure Full Network Packet Capture Detected>> |Identifies potential full network packet capture in Azure. Packet Capture is an Azure Network Watcher feature that can be used to inspect network traffic. This feature can potentially be abused to read sensitive data from unencrypted internal traffic. |[Domain: Cloud], [Data Source: Azure], [Tactic: Credential Access] |8.3.0 |103
 
-|<<bpf-filter-applied-using-tc, BPF filter applied using TC>> |Detects when the tc (transmission control) binary is utilized to set a BPF (Berkeley Packet Filter) on a network interface. Tc is used to configure Traffic Control in the Linux kernel. It can shape, schedule, police and drop traffic. A threat actor can utilize tc to set a bpf filter on an interface for the purpose of manipulating the incoming traffic. This technique is not at all common and should indicate abnormal, suspicious or malicious activity. |[Elastic] [Host] [Linux] [Threat Detection] [Execution] [TripleCross]  |8.4.0 |100 <<bpf-filter-applied-using-tc-history, Version history>>
+|<<azure-global-administrator-role-addition-to-pim-user, Azure Global Administrator Role Addition to PIM User>> |Identifies an Azure Active Directory (AD) Global Administrator role addition to a Privileged Identity Management (PIM) user account. PIM is a service that enables you to manage, control, and monitor access to important resources in an organization. Users who are assigned to the Global administrator role can read and modify any administrative setting in your Azure AD organization. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Tactic: Persistence] |8.3.0 |102
 
-|<<base16-or-base32-encoding-decoding-activity, Base16 or Base32 Encoding/Decoding Activity>> |Adversaries may encode/decode data in an attempt to evade detection by host- or network-based security controls. |[Elastic] [Host] [Linux] [Threat Detection] [Defense Evasion]  |7.8.0 |100 <<base16-or-base32-encoding-decoding-activity-history, Version history>>
+|<<azure-key-vault-modified, Azure Key Vault Modified>> |Identifies modifications to a Key Vault in Azure. The Key Vault is a service that safeguards encryption keys and secrets like certificates, connection strings, and passwords. Because this data is sensitive and business critical, access to key vaults should be secured to allow only authorized applications and users. |[Domain: Cloud], [Data Source: Azure], [Tactic: Credential Access] |8.3.0 |103
 
-|<<bash-shell-profile-modification, Bash Shell Profile Modification>> |Both ~/.bash_profile and ~/.bashrc are files containing shell commands that are run when Bash is invoked. These files are executed in a user's context, either interactively or non-interactively, when a user logs in so that their environment is set correctly. Adversaries may abuse this to establish persistence by executing malicious content triggered by a user’s shell. |[Elastic] [Host] [macOS] [Linux] [Threat Detection] [Persistence]  |7.12.0 |100 <<bash-shell-profile-modification-history, Version history>>
+|<<azure-kubernetes-events-deleted, Azure Kubernetes Events Deleted>> |Identifies when events are deleted in Azure Kubernetes. Kubernetes events are objects that log any state changes. Example events are a container creation, an image pull, or a pod scheduling on a node. An adversary may delete events in Azure Kubernetes in an attempt to evade detection. |[Domain: Cloud], [Data Source: Azure], [Use Case: Log Auditing], [Tactic: Defense Evasion] |8.3.0 |102
 
-|<<binary-executed-from-shared-memory-directory, Binary Executed from Shared Memory Directory>> |Identifies the execution of a binary by root in Linux shared memory directories: (/dev/shm/, /run/shm/, /var/run/, /var/lock/). This activity is to be considered highly abnormal and should be investigated. Threat actors have placed executables used for persistence on high-uptime servers in these directories as system backdoors. |[Elastic] [Host] [Linux] [Threat Detection] [Execution] [BPFDoor]  |8.3.0 |101 <<binary-executed-from-shared-memory-directory-history, Version history>>
+|<<azure-kubernetes-pods-deleted, Azure Kubernetes Pods Deleted>> |Identifies the deletion of Azure Kubernetes Pods. Adversaries may delete a Kubernetes pod to disrupt the normal behavior of the environment. |[Domain: Cloud], [Data Source: Azure], [Use Case: Asset Visibility], [Tactic: Impact] |8.3.0 |102
 
-|<<bypass-uac-via-event-viewer, Bypass UAC via Event Viewer>> |Identifies User Account Control (UAC) bypass via eventvwr.exe. Attackers bypass UAC to stealthily execute code with elevated permissions. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Investigation Guide]  |7.7.0 |102 <<bypass-uac-via-event-viewer-history, Version history>>
+|<<azure-kubernetes-rolebindings-created, Azure Kubernetes Rolebindings Created>> |Identifies the creation of role binding or cluster role bindings. You can assign these roles to Kubernetes subjects (users, groups, or service accounts) with role bindings and cluster role bindings. An adversary who has permissions to create bindings and cluster-bindings in the cluster can create a binding to the cluster-admin ClusterRole or to other high privileges roles. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Tactic: Privilege Escalation] |8.3.0 |102
 
-|<<chkconfig-service-add, Chkconfig Service Add>> |Detects the use of the chkconfig binary to manually add a service for management by chkconfig. Threat actors may utilize this technique to maintain persistence on a system. When a new service is added, chkconfig ensures that the service has either a start or a kill entry in every runlevel and when the system is rebooted the service file added will run providing long-term persistence. |[Elastic] [Host] [Linux] [Threat Detection] [Persistence] [Lightning Framework]  |8.4.0 |100 <<chkconfig-service-add-history, Version history>>
+|<<azure-network-watcher-deletion, Azure Network Watcher Deletion>> |Identifies the deletion of a Network Watcher in Azure. Network Watchers are used to monitor, diagnose, view metrics, and enable or disable logs for resources in an Azure virtual network. An adversary may delete a Network Watcher in an attempt to evade defenses. |[Domain: Cloud], [Data Source: Azure], [Use Case: Network Security Monitoring], [Tactic: Defense Evasion] |8.3.0 |102
 
-|<<clearing-windows-console-history, Clearing Windows Console History>> |Identifies when a user attempts to clear console history. An adversary may clear the command history of a compromised account to conceal the actions undertaken during an intrusion. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |8.0.0 |102 <<clearing-windows-console-history-history, Version history>>
+|<<azure-privilege-identity-management-role-modified, Azure Privilege Identity Management Role Modified>> |Azure Active Directory (AD) Privileged Identity Management (PIM) is a service that enables you to manage, control, and monitor access to important resources in an organization. PIM can be used to manage the built-in Azure resource roles such as Global Administrator and Application Administrator. An adversary may add a user to a PIM role in order to maintain persistence in their target's environment or modify a PIM role to weaken their target's security controls. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Persistence] |8.3.0 |105
 
-|<<clearing-windows-event-logs, Clearing Windows Event Logs>> |Identifies attempts to clear or disable Windows event log stores using Windows wevetutil command. This is often done by attackers in an attempt to evade detection or destroy forensic evidence on a system. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.6.0 |102 <<clearing-windows-event-logs-history, Version history>>
+|<<azure-resource-group-deletion, Azure Resource Group Deletion>> |Identifies the deletion of a resource group in Azure, which includes all resources within the group. Deletion is permanent and irreversible. An adversary may delete a resource group in an attempt to evade defenses or intentionally destroy data. |[Domain: Cloud], [Data Source: Azure], [Use Case: Log Auditing], [Tactic: Impact] |8.3.0 |102
 
-|<<cobalt-strike-command-and-control-beacon, Cobalt Strike Command and Control Beacon>> |Cobalt Strike is a threat emulation platform commonly modified and used by adversaries to conduct network attack and exploitation campaigns. This rule detects a network activity algorithm leveraged by Cobalt Strike implant beacons for command and control. |[Elastic] [Network] [Threat Detection] [Command and Control] [Host]  |7.10.0 |101 <<cobalt-strike-command-and-control-beacon-history, Version history>>
+|<<azure-service-principal-addition, Azure Service Principal Addition>> |Identifies when a new service principal is added in Azure. An application, hosted service, or automated tool that accesses or modifies resources needs an identity created. This identity is known as a service principal. For security reasons, it's always recommended to use service principals with automated tools rather than allowing them to log in with a user identity. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Defense Evasion] |8.3.0 |105
 
-|<<command-execution-via-solarwinds-process, Command Execution via SolarWinds Process>> |A suspicious SolarWinds child process (Cmd.exe or Powershell.exe) was detected. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Elastic Endgame]  |7.11.0 |102 <<command-execution-via-solarwinds-process-history, Version history>>
+|<<azure-service-principal-credentials-added, Azure Service Principal Credentials Added>> |Identifies when new Service Principal credentials have been added in Azure. In most organizations, credentials will be added to service principals infrequently. Hijacking an application (by adding a rogue secret or certificate) with granted permissions will allow the attacker to access data that is normally protected by MFA requirements. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Tactic: Impact] |8.3.0 |102
 
-|<<command-prompt-network-connection, Command Prompt Network Connection>> |Identifies cmd.exe making a network connection. Adversaries could abuse cmd.exe to download or execute malware from a remote URL. |[Elastic] [Host] [Windows] [Threat Detection] [Execution]  |7.6.0 |100 <<command-prompt-network-connection-history, Version history>>
+|<<azure-storage-account-key-regenerated, Azure Storage Account Key Regenerated>> |Identifies a rotation to storage account access keys in Azure. Regenerating access keys can affect any applications or Azure services that are dependent on the storage account key. Adversaries may regenerate a key as a means of acquiring credentials to access systems and resources. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Tactic: Credential Access] |8.3.0 |102
 
-|<<command-shell-activity-started-via-rundll32, Command Shell Activity Started via RunDLL32>> |Identifies command shell activity started via RunDLL32, which is commonly abused by attackers to host malicious code. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Elastic Endgame]  |7.11.0 |101 <<command-shell-activity-started-via-rundll32-history, Version history>>
+|<<azure-virtual-network-device-modified-or-deleted, Azure Virtual Network Device Modified or Deleted>> |Identifies when a virtual network device is modified or deleted. This can be a network virtual appliance, virtual hub, or virtual router. |[Domain: Cloud], [Data Source: Azure], [Use Case: Network Security Monitoring], [Tactic: Impact] |8.3.0 |102
 
-|<<component-object-model-hijacking, Component Object Model Hijacking>> |Identifies Component Object Model (COM) hijacking via registry modification. Adversaries may establish persistence by executing malicious content triggered by hijacked references to COM objects. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.11.0 |102 <<component-object-model-hijacking-history, Version history>>
+|<<bpf-filter-applied-using-tc, BPF filter applied using TC>> |Detects when the tc (transmission control) binary is utilized to set a BPF (Berkeley Packet Filter) on a network interface. Tc is used to configure Traffic Control in the Linux kernel. It can shape, schedule, police and drop traffic. A threat actor can utilize tc to set a bpf filter on an interface for the purpose of manipulating the incoming traffic. This technique is not at all common and should indicate abnormal, suspicious or malicious activity. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Threat: TripleCross], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<conhost-spawned-by-suspicious-parent-process, Conhost Spawned By Suspicious Parent Process>> |Detects when the Console Window Host (conhost.exe) process is spawned by a suspicious parent process, which could be indicative of code injection. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Investigation Guide] [Elastic Endgame]  |7.10.0 |102 <<conhost-spawned-by-suspicious-parent-process-history, Version history>>
+|<<base16-or-base32-encoding-decoding-activity, Base16 or Base32 Encoding/Decoding Activity>> |Adversaries may encode/decode data in an attempt to evade detection by host- or network-based security controls. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |110
 
-|<<connection-to-commonly-abused-free-ssl-certificate-providers, Connection to Commonly Abused Free SSL Certificate Providers>> |Identifies unusual processes connecting to domains using known free SSL certificates. Adversaries may employ a known encryption algorithm to conceal command and control traffic. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control]  |7.11.0 |100 <<connection-to-commonly-abused-free-ssl-certificate-providers-history, Version history>>
+|<<bash-shell-profile-modification, Bash Shell Profile Modification>> |Both ~/.bash_profile and ~/.bashrc are files containing shell commands that are run when Bash is invoked. These files are executed in a user's context, either interactively or non-interactively, when a user logs in so that their environment is set correctly. Adversaries may abuse this to establish persistence by executing malicious content triggered by a user’s shell. |[Domain: Endpoint], [OS: macOS], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |104
 
-|<<connection-to-commonly-abused-web-services, Connection to Commonly Abused Web Services>> |Adversaries may implement command and control (C2) communications that use common web services to hide their activity. This attack technique is typically targeted at an organization and uses web services common to the victim network, which allows the adversary to blend into legitimate traffic activity. These popular services are typically targeted since they have most likely been used before compromise, which helps malicious traffic blend in. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control] [Investigation Guide]  |7.11.0 |102 <<connection-to-commonly-abused-web-services-history, Version history>>
+|<<binary-content-copy-via-cmd-exe, Binary Content Copy via Cmd.exe>> |Attackers may abuse cmd.exe commands to reassemble binary fragments into a malicious payload. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |3
 
-|<<connection-to-external-network-via-telnet, Connection to External Network via Telnet>> |Telnet provides a command line interface for communication with a remote device or server. This rule identifies Telnet network connections to publicly routable IP addresses. |[Elastic] [Host] [Linux] [Threat Detection] [Lateral Movement]  |7.8.0 |100 <<connection-to-external-network-via-telnet-history, Version history>>
+|<<binary-executed-from-shared-memory-directory, Binary Executed from Shared Memory Directory>> |Identifies the execution of a binary by root in Linux shared memory directories: (/dev/shm/, /run/shm/, /var/run/, /var/lock/). This activity is to be considered highly abnormal and should be investigated. Threat actors have placed executables used for persistence on high-uptime servers in these directories as system backdoors. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Threat: BPFDoor], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<connection-to-internal-network-via-telnet, Connection to Internal Network via Telnet>> |Telnet provides a command line interface for communication with a remote device or server. This rule identifies Telnet network connections to non-publicly routable IP addresses. |[Elastic] [Host] [Linux] [Threat Detection] [Lateral Movement]  |7.8.0 |100 <<connection-to-internal-network-via-telnet-history, Version history>>
+|<<bitsadmin-activity, Bitsadmin Activity>> |Windows Background Intelligent Transfer Service (BITS) is a low-bandwidth, asynchronous file transfer mechanism. Adversaries may abuse BITS to persist, download, execute, and even clean up after running malicious code. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |2
 
-|<<control-panel-process-with-unusual-arguments, Control Panel Process with Unusual Arguments>> |Identifies unusual instances of Control Panel with suspicious keywords or paths in the process command line value. Adversaries may abuse control.exe to proxy execution of malicious code. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.16.0 |102 <<control-panel-process-with-unusual-arguments-history, Version history>>
+|<<browser-extension-install, Browser Extension Install>> |Identifies the install of browser extensions. Malicious browser extensions can be installed via app store downloads masquerading as legitimate extensions, social engineering, or by an adversary that has already compromised a system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<creation-of-hidden-files-and-directories-via-commandline, Creation of Hidden Files and Directories via CommandLine>> |Users can mark specific files as hidden simply by putting a "." as the first character in the file or folder name. Adversaries can use this to their advantage to hide files and folders on the system for persistence and defense evasion. This rule looks for hidden files or folders in common writable directories. |[Elastic] [Host] [Linux] [Threat Detection] [Defense Evasion]  |7.9.0 |100 <<creation-of-hidden-files-and-directories-via-commandline-history, Version history>>
+|<<bypass-uac-via-event-viewer, Bypass UAC via Event Viewer>> |Identifies User Account Control (UAC) bypass via eventvwr.exe. Attackers bypass UAC to stealthily execute code with elevated permissions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
 
-|<<creation-of-hidden-launch-agent-or-daemon, Creation of Hidden Launch Agent or Daemon>> |Identifies the creation of a hidden launch agent or daemon. An adversary may establish persistence by installing a new launch agent or daemon which executes at login. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence] [Defense Evasion]  |7.12.0 |100 <<creation-of-hidden-launch-agent-or-daemon-history, Version history>>
+|<<cap-sys-admin-assigned-to-binary, CAP_SYS_ADMIN Assigned to Binary>> |Identifies instances where a binary is granted the CAP_SYS_ADMIN capability. In Linux, the CAP_SYS_ADMIN capability is a powerful and broad capability that allows a process to perform a range of system administration operations, such as mounting and unmounting filesystems, configuring network interfaces, and accessing hardware devices. Attackers may leverage a misconfiguration for exploitation in order to escalate their privileges to root. The rule identifies previously unknown processes executing with CAP_SYS_ADMIN capabilities through the use of the new terms rule type. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend], [Rule Type: BBR] |8.11.0 |2
 
-|<<creation-of-hidden-login-item-via-apple-script, Creation of Hidden Login Item via Apple Script>> |Identifies the execution of osascript to create a hidden login item. This may indicate an attempt to persist a malicious program while concealing its presence. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence] [Execution]  |7.12.0 |101 <<creation-of-hidden-login-item-via-apple-script-history, Version history>>
+|<<chkconfig-service-add, Chkconfig Service Add>> |Detects the use of the chkconfig binary to manually add a service for management by chkconfig. Threat actors may utilize this technique to maintain persistence on a system. When a new service is added, chkconfig ensures that the service has either a start or a kill entry in every runlevel and when the system is rebooted the service file added will run providing long-term persistence. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Threat: Lightning Framework], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<creation-of-hidden-shared-object-file, Creation of Hidden Shared Object File>> |Identifies the creation of a hidden shared object (.so) file. Users can mark specific files as hidden simply by putting a "." as the first character in the file or folder name. Adversaries can use this to their advantage to hide files and folders on the system for persistence and defense evasion. |[Elastic] [Host] [Linux] [Threat Detection] [Defense Evasion]  |8.4.0 |100 <<creation-of-hidden-shared-object-file-history, Version history>>
+|<<clearing-windows-console-history, Clearing Windows Console History>> |Identifies when a user attempts to clear console history. An adversary may clear the command history of a compromised account to conceal the actions undertaken during an intrusion. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<creation-of-a-hidden-local-user-account, Creation of a Hidden Local User Account>> |Identifies the creation of a hidden local user account by appending the dollar sign to the account name. This is sometimes done by attackers to increase access to a system and avoid appearing in the results of accounts listing using the net users command. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.12.0 |102 <<creation-of-a-hidden-local-user-account-history, Version history>>
+|<<clearing-windows-event-logs, Clearing Windows Event Logs>> |Identifies attempts to clear or disable Windows event log stores using Windows wevetutil command. This is often done by attackers in an attempt to evade detection or destroy forensic evidence on a system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
 
-|<<creation-or-modification-of-domain-backup-dpapi-private-key, Creation or Modification of Domain Backup DPAPI private key>> |Identifies the creation or modification of Domain Backup private keys. Adversaries may extract the Data Protection API (DPAPI) domain backup key from a Domain Controller (DC) to be able to decrypt any domain user master key file. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Elastic Endgame]  |7.10.0 |101 <<creation-or-modification-of-domain-backup-dpapi-private-key-history, Version history>>
+|<<cobalt-strike-command-and-control-beacon, Cobalt Strike Command and Control Beacon>> |Cobalt Strike is a threat emulation platform commonly modified and used by adversaries to conduct network attack and exploitation campaigns. This rule detects a network activity algorithm leveraged by Cobalt Strike implant beacons for command and control. |[Use Case: Threat Detection], [Tactic: Command and Control], [Domain: Endpoint] |8.3.0 |105
 
-|<<creation-or-modification-of-root-certificate, Creation or Modification of Root Certificate>> |Identifies the creation or modification of a local trusted root certificate in Windows. The install of a malicious root certificate would allow an attacker the ability to masquerade malicious files as valid signed components from any entity (for example, Microsoft). It could also allow an attacker to decrypt SSL traffic. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.12.0 |102 <<creation-or-modification-of-root-certificate-history, Version history>>
+|<<code-signing-policy-modification-through-built-in-tools, Code Signing Policy Modification Through Built-in tools>> |Identifies attempts to disable/modify the code signing policy through system native utilities. Code signing provides authenticity on a program, and grants the user with the ability to check whether the program has been tampered with. By allowing the execution of unsigned or self-signed code, threat actors can craft and execute malicious code. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |7
 
-|<<creation-or-modification-of-a-new-gpo-scheduled-task-or-service, Creation or Modification of a new GPO Scheduled Task or Service>> |Detects the creation or modification of a new Group Policy based scheduled task or service. These methods are used for legitimate system administration, but can also be abused by an attacker with domain admin permissions to execute a malicious payload remotely on all or a subset of the domain joined machines. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.10.0 |101 <<creation-or-modification-of-a-new-gpo-scheduled-task-or-service-history, Version history>>
+|<<code-signing-policy-modification-through-registry, Code Signing Policy Modification Through Registry>> |Identifies attempts to disable the code signing policy through the registry. Code signing provides authenticity on a program, and grants the user with the ability to check whether the program has been tampered with. By allowing the execution of unsigned or self-signed code, threat actors can craft and execute malicious code. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |9
 
-|<<credential-acquisition-via-registry-hive-dumping, Credential Acquisition via Registry Hive Dumping>> |Identifies attempts to export a registry hive which may contain credentials using the Windows reg.exe tool. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<credential-acquisition-via-registry-hive-dumping-history, Version history>>
+|<<command-execution-via-solarwinds-process, Command Execution via SolarWinds Process>> |A suspicious SolarWinds child process (Cmd.exe or Powershell.exe) was detected. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Initial Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<credential-dumping-detected-elastic-endgame, Credential Dumping - Detected - Elastic Endgame>> |Elastic Endgame detected Credential Dumping. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame] [Threat Detection] [Credential Access]  |7.6.0 |100 <<credential-dumping-detected-elastic-endgame-history, Version history>>
+|<<command-prompt-network-connection, Command Prompt Network Connection>> |Identifies cmd.exe making a network connection. Adversaries could abuse cmd.exe to download or execute malware from a remote URL. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<credential-dumping-prevented-elastic-endgame, Credential Dumping - Prevented - Elastic Endgame>> |Elastic Endgame prevented Credential Dumping. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame] [Threat Detection] [Credential Access]  |7.6.0 |100 <<credential-dumping-prevented-elastic-endgame-history, Version history>>
+|<<command-shell-activity-started-via-rundll32, Command Shell Activity Started via RunDLL32>> |Identifies command shell activity started via RunDLL32, which is commonly abused by attackers to host malicious code. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Credential Access], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
 
-|<<credential-manipulation-detected-elastic-endgame, Credential Manipulation - Detected - Elastic Endgame>> |Elastic Endgame detected Credential Manipulation. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame] [Threat Detection] [Privilege Escalation]  |7.6.0 |100 <<credential-manipulation-detected-elastic-endgame-history, Version history>>
+|<<component-object-model-hijacking, Component Object Model Hijacking>> |Identifies Component Object Model (COM) hijacking via registry modification. Adversaries may establish persistence by executing malicious content triggered by hijacked references to COM objects. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Tactic: Privilege Escalation], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |113
 
-|<<credential-manipulation-prevented-elastic-endgame, Credential Manipulation - Prevented - Elastic Endgame>> |Elastic Endgame prevented Credential Manipulation. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame] [Threat Detection] [Privilege Escalation]  |7.6.0 |100 <<credential-manipulation-prevented-elastic-endgame-history, Version history>>
+|<<compression-dll-loaded-by-unusual-process, Compression DLL Loaded by Unusual Process>> |Identifies the image load of a compression DLL. Adversaries will often compress and encrypt data in preparation for exfiltration. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |3
 
-|<<cyberark-privileged-access-security-error, CyberArk Privileged Access Security Error>> |Identifies the occurrence of a CyberArk Privileged Access Security (PAS) error level audit event. The event.code correlates to the CyberArk Vault Audit Action Code. |[Elastic] [cyberarkpas] [SecOps] [Log Auditing] [Threat Detection] [Privilege Escalation]  |7.14.0 |101 <<cyberark-privileged-access-security-error-history, Version history>>
+|<<conhost-spawned-by-suspicious-parent-process, Conhost Spawned By Suspicious Parent Process>> |Detects when the Console Window Host (conhost.exe) process is spawned by a suspicious parent process, which could be indicative of code injection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Defense Evasion], [Tactic: Privilege Escalation], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
 
-|<<cyberark-privileged-access-security-recommended-monitor, CyberArk Privileged Access Security Recommended Monitor>> |Identifies the occurrence of a CyberArk Privileged Access Security (PAS) non-error level audit event which is recommended for monitoring by the vendor. The event.code correlates to the CyberArk Vault Audit Action Code. |[Elastic] [cyberarkpas] [SecOps] [Log Auditing] [Threat Detection] [Privilege Escalation]  |7.14.0 |101 <<cyberark-privileged-access-security-recommended-monitor-history, Version history>>
+|<<connection-to-commonly-abused-free-ssl-certificate-providers, Connection to Commonly Abused Free SSL Certificate Providers>> |Identifies unusual processes connecting to domains using known free SSL certificates. Adversaries may employ a known encryption algorithm to conceal command and control traffic. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
 
-|<<dns-tunneling, DNS Tunneling>> |A machine learning job detected unusually large numbers of DNS queries for a single top-level DNS domain, which is often used for DNS tunneling. DNS tunneling can be used for command-and-control, persistence, or data exfiltration activity. For example, dnscat tends to generate many DNS questions for a top-level domain as it uses the DNS protocol to tunnel data. |[Elastic] [Network] [Threat Detection] [ML] [Command and Control]  |7.7.0 |100 <<dns-tunneling-history, Version history>>
+|<<connection-to-commonly-abused-web-services, Connection to Commonly Abused Web Services>> |Adversaries may implement command and control (C2) communications that use common web services to hide their activity. This attack technique is typically targeted at an organization and uses web services common to the victim network, which allows the adversary to blend into legitimate traffic activity. These popular services are typically targeted since they have most likely been used before compromise, which helps malicious traffic blend in. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |113
 
-|<<dns-over-https-enabled-via-registry, DNS-over-HTTPS Enabled via Registry>> |Identifies when a user enables DNS-over-HTTPS. This can be used to hide internet activity or the process of exfiltrating data. With this enabled, an organization will lose visibility into data such as query type, response, and originating IP, which are used to determine bad actors. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.16.0 |101 <<dns-over-https-enabled-via-registry-history, Version history>>
+|<<connection-to-external-network-via-telnet, Connection to External Network via Telnet>> |Telnet provides a command line interface for communication with a remote device or server. This rule identifies Telnet network connections to publicly routable IP addresses. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<default-cobalt-strike-team-server-certificate, Default Cobalt Strike Team Server Certificate>> |This rule detects the use of the default Cobalt Strike Team Server TLS certificate. Cobalt Strike is software for Adversary Simulations and Red Team Operations which are security assessments that replicate the tactics and techniques of an advanced adversary in a network. Modifications to the Packetbeat configuration can be made to include MD5 and SHA256 hashing algorithms (the default is SHA1). See the References section for additional information on module configuration. |[Command and Control] [Post-Execution] [Threat Detection] [Elastic] [Network] [Host]  |7.11.0 |101 <<default-cobalt-strike-team-server-certificate-history, Version history>>
+|<<connection-to-internal-network-via-telnet, Connection to Internal Network via Telnet>> |Telnet provides a command line interface for communication with a remote device or server. This rule identifies Telnet network connections to non-publicly routable IP addresses. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<delete-volume-usn-journal-with-fsutil, Delete Volume USN Journal with Fsutil>> |Identifies use of the fsutil.exe to delete the volume USNJRNL. This technique is used by attackers to eliminate evidence of files created during post-exploitation activities. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.6.0 |102 <<delete-volume-usn-journal-with-fsutil-history, Version history>>
+|<<container-management-utility-run-inside-a-container, Container Management Utility Run Inside A Container>> |This rule detects when a container management binary is run from inside a container. These binaries are critical components of many containerized environments, and their presence and execution in unauthorized containers could indicate compromise or a misconfiguration. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution] |8.8.0 |2
 
-|<<deleting-backup-catalogs-with-wbadmin, Deleting Backup Catalogs with Wbadmin>> |Identifies use of the wbadmin.exe to delete the backup catalog. Ransomware and other malware may do this to prevent system recovery. |[Elastic] [Host] [Windows] [Threat Detection] [Impact] [Investigation Guide]  |7.6.0 |102 <<deleting-backup-catalogs-with-wbadmin-history, Version history>>
+|<<container-workload-protection, Container Workload Protection>> |Generates a detection alert each time a 'Container Workload Protection' alert is received. Enabling this rule allows you to immediately begin triaging and investigating these alerts. |[Data Source: Elastic Defend for Containers], [Domain: Container] |8.8.0 |4
 
-|<<direct-outbound-smb-connection, Direct Outbound SMB Connection>> |Identifies unexpected processes making network connections over port 445. Windows File Sharing is typically implemented over Server Message Block (SMB), which communicates between hosts using port 445. When legitimate, these network connections are established by the kernel. Processes making 445/tcp connections may be port scanners, exploits, or suspicious user-level processes moving laterally. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement] [Investigation Guide]  |7.6.0 |102 <<direct-outbound-smb-connection-history, Version history>>
+|<<control-panel-process-with-unusual-arguments, Control Panel Process with Unusual Arguments>> |Identifies unusual instances of Control Panel with suspicious keywords or paths in the process command line value. Adversaries may abuse control.exe to proxy execution of malicious code. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<disable-windows-event-and-security-logs-using-built-in-tools, Disable Windows Event and Security Logs Using Built-in Tools>> |Identifies attempts to disable EventLog via the logman Windows utility, PowerShell, or auditpol. This is often done by attackers in an attempt to evade detection on a system. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.14.0 |102 <<disable-windows-event-and-security-logs-using-built-in-tools-history, Version history>>
+|<<creation-of-hidden-files-and-directories-via-commandline, Creation of Hidden Files and Directories via CommandLine>> |Users can mark specific files as hidden simply by putting a "." as the first character in the file or folder name. Adversaries can use this to their advantage to hide files and folders on the system for persistence and defense evasion. This rule looks for hidden files or folders in common writable directories. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<disable-windows-firewall-rules-via-netsh, Disable Windows Firewall Rules via Netsh>> |Identifies use of the netsh.exe to disable or weaken the local firewall. Attackers will use this command line tool to disable the firewall during troubleshooting or to enable network mobility. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.6.0 |102 <<disable-windows-firewall-rules-via-netsh-history, Version history>>
+|<<creation-of-hidden-launch-agent-or-daemon, Creation of Hidden Launch Agent or Daemon>> |Identifies the creation of a hidden launch agent or daemon. An adversary may establish persistence by installing a new launch agent or daemon which executes at login. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<disabling-user-account-control-via-registry-modification, Disabling User Account Control via Registry Modification>> |User Account Control (UAC) can help mitigate the impact of malware on Windows hosts. With UAC, apps and tasks always run in the security context of a non-administrator account, unless an administrator specifically authorizes administrator-level access to the system. This rule identifies registry value changes to bypass User Access Control (UAC) protection. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Investigation Guide]  |7.12.0 |102 <<disabling-user-account-control-via-registry-modification-history, Version history>>
+|<<creation-of-hidden-login-item-via-apple-script, Creation of Hidden Login Item via Apple Script>> |Identifies the execution of osascript to create a hidden login item. This may indicate an attempt to persist a malicious program while concealing its presence. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<disabling-windows-defender-security-settings-via-powershell, Disabling Windows Defender Security Settings via PowerShell>> |Identifies use of the Set-MpPreference PowerShell command to disable or weaken certain Windows Defender settings. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.14.0 |102 <<disabling-windows-defender-security-settings-via-powershell-history, Version history>>
+|<<creation-of-hidden-shared-object-file, Creation of Hidden Shared Object File>> |Identifies the creation of a hidden shared object (.so) file. Users can mark specific files as hidden simply by putting a "." as the first character in the file or folder name. Adversaries can use this to their advantage to hide files and folders on the system for persistence and defense evasion. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<domain-added-to-google-workspace-trusted-domains, Domain Added to Google Workspace Trusted Domains>> |Detects when a domain is added to the list of trusted Google Workspace domains. An adversary may add a trusted domain in order to collect and exfiltrate data from their target’s organization with less restrictive security controls. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Configuration Audit] [Defense Evasion]  |7.11.0 |101 <<domain-added-to-google-workspace-trusted-domains-history, Version history>>
+|<<creation-of-kernel-module, Creation of Kernel Module>> |Identifies activity related to loading kernel modules on Linux via creation of new ko files in the LKM directory. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |3
 
-|<<dumping-account-hashes-via-built-in-commands, Dumping Account Hashes via Built-In Commands>> |Identifies the execution of macOS built-in commands used to dump user account hashes. Adversaries may attempt to dump credentials to obtain account login information in the form of a hash. These hashes can be cracked or leveraged for lateral movement. |[Elastic] [Host] [macOS] [Threat Detection] [Credential Access]  |7.12.0 |100 <<dumping-account-hashes-via-built-in-commands-history, Version history>>
+|<<creation-of-settingcontent-ms-files, Creation of SettingContent-ms Files>> |Identifies the suspicious creation of SettingContents-ms files, which have been used in attacks to achieve code execution while evading defenses. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |3
 
-|<<dumping-of-keychain-content-via-security-command, Dumping of Keychain Content via Security Command>> |Adversaries may dump the content of the keychain storage data from a system to acquire credentials. Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features, including Wi-Fi and website passwords, secure notes, certificates, and Kerberos. |[Elastic] [Host] [macOS] [Threat Detection] [Credential Access]  |7.12.0 |100 <<dumping-of-keychain-content-via-security-command-history, Version history>>
+|<<creation-of-a-dns-named-record, Creation of a DNS-Named Record>> |Active Directory Integrated DNS (ADIDNS) is one of the core components of AD DS, leveraging AD's access control and replication to maintain domain consistency. It stores DNS zones as AD objects, a feature that, while robust, introduces some security issues because of the default permission (Any authenticated users) to create DNS-named records. Attackers can perform Dynamic Spoofing attacks, where they monitor LLMNR/NBT-NS requests and create DNS-named records to target systems that are requested from multiple systems. They can also create specific records to target specific services, such as wpad, for spoofing attacks. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Active Directory], [Use Case: Active Directory Monitoring] |8.3.0 |1
 
-|<<dynamic-linker-copy, Dynamic Linker Copy>> |Detects the copying of the Linux dynamic loader binary and subsequent file creation for the purpose of creating a backup copy. This technique was seen recently being utilized by Linux malware prior to patching the dynamic loader in order to inject and preload a malicious shared object file. This activity should never occur and if it does then it should be considered highly suspicious or malicious. |[Elastic] [Host] [Linux] [Threat Detection] [Persistence] [Orbit]  |8.4.0 |100 <<dynamic-linker-copy-history, Version history>>
+|<<creation-of-a-hidden-local-user-account, Creation of a Hidden Local User Account>> |Identifies the creation of a hidden local user account by appending the dollar sign to the account name. This is sometimes done by attackers to increase access to a system and avoid appearing in the results of accounts listing using the net users command. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
 
-|<<eggshell-backdoor-execution, EggShell Backdoor Execution>> |Identifies the execution of and EggShell Backdoor. EggShell is a known post exploitation tool for macOS and Linux. |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Execution]  |7.12.0 |100 <<eggshell-backdoor-execution-history, Version history>>
+|<<creation-or-modification-of-domain-backup-dpapi-private-key, Creation or Modification of Domain Backup DPAPI private key>> |Identifies the creation or modification of Domain Backup private keys. Adversaries may extract the Data Protection API (DPAPI) domain backup key from a Domain Controller (DC) to be able to decrypt any domain user master key file. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<elastic-agent-service-terminated, Elastic Agent Service Terminated>> |Identifies the Elastic endpoint agent has stopped and is no longer running on the host. Adversaries may attempt to disable security monitoring tools in an attempt to evade detection or prevention capabilities during an intrusion. This may also indicate an issue with the agent itself and should be addressed to ensure defensive measures are back in a stable state. |[Elastic] [Host] [Linux] [Windows] [macOS] [Threat Detection] [Defense Evasion]  |8.3.0 |100 <<elastic-agent-service-terminated-history, Version history>>
+|<<creation-or-modification-of-root-certificate, Creation or Modification of Root Certificate>> |Identifies the creation or modification of a local trusted root certificate in Windows. The install of a malicious root certificate would allow an attacker the ability to masquerade malicious files as valid signed components from any entity (for example, Microsoft). It could also allow an attacker to decrypt SSL traffic. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
 
-|<<emond-rules-creation-or-modification, Emond Rules Creation or Modification>> |Identifies the creation or modification of the Event Monitor Daemon (emond) rules. Adversaries may abuse this service by writing a rule to execute commands when a defined event occurs, such as system start up or user authentication. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<emond-rules-creation-or-modification-history, Version history>>
+|<<creation-or-modification-of-a-new-gpo-scheduled-task-or-service, Creation or Modification of a new GPO Scheduled Task or Service>> |Detects the creation or modification of a new Group Policy based scheduled task or service. These methods are used for legitimate system administration, but can also be abused by an attacker with domain admin permissions to execute a malicious payload remotely on all or a subset of the domain joined machines. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<enable-host-network-discovery-via-netsh, Enable Host Network Discovery via Netsh>> |Identifies use of the netsh.exe program to enable host discovery via the network. Attackers can use this command-line tool to weaken the host firewall settings. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.14.0 |102 <<enable-host-network-discovery-via-netsh-history, Version history>>
+|<<credential-acquisition-via-registry-hive-dumping, Credential Acquisition via Registry Hive Dumping>> |Identifies attempts to export a registry hive which may contain credentials using the Windows reg.exe tool. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<encoded-executable-stored-in-the-registry, Encoded Executable Stored in the Registry>> |Identifies registry write modifications to hide an encoded portable executable. This could be indicative of adversary defense evasion by avoiding the storing of malicious content directly on disk. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.11.0 |101 <<encoded-executable-stored-in-the-registry-history, Version history>>
+|<<credential-dumping-detected-elastic-endgame, Credential Dumping - Detected - Elastic Endgame>> |Elastic Endgame detected Credential Dumping. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame], [Use Case: Threat Detection], [Tactic: Credential Access] |8.3.0 |103
 
-|<<encrypting-files-with-winrar-or-7z, Encrypting Files with WinRar or 7z>> |Identifies use of WinRar or 7z to create an encrypted files. Adversaries will often compress and encrypt data in preparation for exfiltration. |[Elastic] [Host] [Windows] [Threat Detection] [Collection] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<encrypting-files-with-winrar-or-7z-history, Version history>>
+|<<credential-dumping-prevented-elastic-endgame, Credential Dumping - Prevented - Elastic Endgame>> |Elastic Endgame prevented Credential Dumping. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame], [Use Case: Threat Detection], [Tactic: Credential Access] |8.3.0 |103
 
-|<<endpoint-security, Endpoint Security>> |Generates a detection alert each time an Elastic Endpoint Security alert is received. Enabling this rule allows you to immediately begin investigating your Endpoint alerts. |[Elastic] [Endpoint Security]  |7.9.0 |100 <<endpoint-security-history, Version history>>
+|<<credential-manipulation-detected-elastic-endgame, Credential Manipulation - Detected - Elastic Endgame>> |Elastic Endgame detected Credential Manipulation. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |103
 
-|<<enumerating-domain-trusts-via-nltest.exe, Enumerating Domain Trusts via NLTEST.EXE>> |Identifies the use of nltest.exe for domain trust discovery purposes. Adversaries may use this command-line utility to enumerate domain trusts and gain insight into trust relationships, as well as the state of Domain Controller (DC) replication in a Microsoft Windows NT Domain. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Elastic Endgame]  |8.4.0 |102 <<enumerating-domain-trusts-via-nltest.exe-history, Version history>>
+|<<credential-manipulation-prevented-elastic-endgame, Credential Manipulation - Prevented - Elastic Endgame>> |Elastic Endgame prevented Credential Manipulation. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |103
 
-|<<enumeration-command-spawned-via-wmiprvse, Enumeration Command Spawned via WMIPrvSE>> |Identifies native Windows host and network enumeration commands spawned by the Windows Management Instrumentation Provider Service (WMIPrvSE). |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Elastic Endgame]  |7.12.0 |102 <<enumeration-command-spawned-via-wmiprvse-history, Version history>>
+|<<cron-job-created-or-changed-by-previously-unknown-process, Cron Job Created or Changed by Previously Unknown Process>> |Linux cron jobs are scheduled tasks that can be leveraged by malicious actors for persistence, privilege escalation and command execution. By creating or modifying cron job configurations, attackers can execute malicious commands or scripts at predefined intervals, ensuring their continued presence and enabling unauthorized activities. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Privilege Escalation], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.6.0 |9
 
-|<<enumeration-of-administrator-accounts, Enumeration of Administrator Accounts>> |Identifies instances of lower privilege accounts enumerating Administrator accounts or groups using built-in Windows tools. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<enumeration-of-administrator-accounts-history, Version history>>
+|<<cyberark-privileged-access-security-error, CyberArk Privileged Access Security Error>> |Identifies the occurrence of a CyberArk Privileged Access Security (PAS) error level audit event. The event.code correlates to the CyberArk Vault Audit Action Code. |[Data Source: CyberArk PAS], [Use Case: Log Auditing], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |102
 
-|<<enumeration-of-kernel-modules, Enumeration of Kernel Modules>> |Loadable Kernel Modules (or LKMs) are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. This identifies attempts to enumerate information about a kernel module. |[Elastic] [Host] [Linux] [Threat Detection] [Discovery]  |7.8.0 |100 <<enumeration-of-kernel-modules-history, Version history>>
+|<<cyberark-privileged-access-security-recommended-monitor, CyberArk Privileged Access Security Recommended Monitor>> |Identifies the occurrence of a CyberArk Privileged Access Security (PAS) non-error level audit event which is recommended for monitoring by the vendor. The event.code correlates to the CyberArk Vault Audit Action Code. |[Data Source: CyberArk PAS], [Use Case: Log Auditing], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |102
 
-|<<enumeration-of-privileged-local-groups-membership, Enumeration of Privileged Local Groups Membership>> |Identifies instances of an unusual process enumerating built-in Windows privileged local groups membership like Administrators or Remote Desktop users. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide]  |8.0.0 |102 <<enumeration-of-privileged-local-groups-membership-history, Version history>>
+|<<dns-tunneling, DNS Tunneling>> |A machine learning job detected unusually large numbers of DNS queries for a single top-level DNS domain, which is often used for DNS tunneling. DNS tunneling can be used for command-and-control, persistence, or data exfiltration activity. For example, dnscat tends to generate many DNS questions for a top-level domain as it uses the DNS protocol to tunnel data. |[Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Command and Control] |8.3.0 |103
 
-|<<enumeration-of-users-or-groups-via-built-in-commands, Enumeration of Users or Groups via Built-in Commands>> |Identifies the execution of macOS built-in commands related to account or group enumeration. Adversaries may use account and group information to orient themselves before deciding how to act. |[Elastic] [Host] [macOS] [Threat Detection] [Discovery]  |7.12.0 |100 <<enumeration-of-users-or-groups-via-built-in-commands-history, Version history>>
+|<<dns-over-https-enabled-via-registry, DNS-over-HTTPS Enabled via Registry>> |Identifies when a user enables DNS-over-HTTPS. This can be used to hide internet activity or the process of exfiltrating data. With this enabled, an organization will lose visibility into data such as query type, response, and originating IP, which are used to determine bad actors. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<executable-file-creation-with-multiple-extensions, Executable File Creation with Multiple Extensions>> |Masquerading can allow an adversary to evade defenses and better blend in with the environment. One way it occurs is when the name or location of a file is manipulated as a means of tricking a user into executing what they think is a benign file type but is actually executable code. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.12.0 |101 <<executable-file-creation-with-multiple-extensions-history, Version history>>
+|<<default-cobalt-strike-team-server-certificate, Default Cobalt Strike Team Server Certificate>> |This rule detects the use of the default Cobalt Strike Team Server TLS certificate. Cobalt Strike is software for Adversary Simulations and Red Team Operations which are security assessments that replicate the tactics and techniques of an advanced adversary in a network. Modifications to the Packetbeat configuration can be made to include MD5 and SHA256 hashing algorithms (the default is SHA1). See the References section for additional information on module configuration. |[Tactic: Command and Control], [Threat: Cobalt Strike], [Use Case: Threat Detection], [Domain: Endpoint] |8.3.0 |104
 
-|<<execution-from-unusual-directory-command-line, Execution from Unusual Directory - Command Line>> |Identifies process execution from suspicious default Windows directories. This may be abused by adversaries to hide malware in trusted paths. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<execution-from-unusual-directory-command-line-history, Version history>>
+|<<delayed-execution-via-ping, Delayed Execution via Ping>> |Identifies the execution of commonly abused Windows utilities via a delayed Ping execution. This behavior is often observed during malware installation and is consistent with an attacker attempting to evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<execution-of-com-object-via-xwizard, Execution of COM object via Xwizard>> |Windows Component Object Model (COM) is an inter-process communication (IPC) component of the native Windows application programming interface (API) that enables interaction between software objects or executable code. Xwizard can be used to run a COM object created in registry to evade defensive counter measures. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Elastic Endgame]  |7.12.0 |102 <<execution-of-com-object-via-xwizard-history, Version history>>
+|<<delete-volume-usn-journal-with-fsutil, Delete Volume USN Journal with Fsutil>> |Identifies use of the fsutil.exe to delete the volume USNJRNL. This technique is used by attackers to eliminate evidence of files created during post-exploitation activities. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<execution-of-file-written-or-modified-by-microsoft-office, Execution of File Written or Modified by Microsoft Office>> |Identifies an executable created by a Microsoft Office application and subsequently executed. These processes are often launched via scripts inside documents or during exploitation of Microsoft Office applications. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Investigation Guide] [Elastic Endgame]  |7.10.0 |102 <<execution-of-file-written-or-modified-by-microsoft-office-history, Version history>>
+|<<deleting-backup-catalogs-with-wbadmin, Deleting Backup Catalogs with Wbadmin>> |Identifies use of the wbadmin.exe to delete the backup catalog. Ransomware and other malware may do this to prevent system recovery. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Impact], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<execution-of-file-written-or-modified-by-pdf-reader, Execution of File Written or Modified by PDF Reader>> |Identifies a suspicious file that was written by a PDF reader application and subsequently executed. These processes are often launched via exploitation of PDF applications. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Investigation Guide] [Elastic Endgame]  |7.10.0 |102 <<execution-of-file-written-or-modified-by-pdf-reader-history, Version history>>
+|<<direct-outbound-smb-connection, Direct Outbound SMB Connection>> |Identifies unexpected processes making network connections over port 445. Windows File Sharing is typically implemented over Server Message Block (SMB), which communicates between hosts using port 445. When legitimate, these network connections are established by the kernel. Processes making 445/tcp connections may be port scanners, exploits, or suspicious user-level processes moving laterally. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<execution-of-persistent-suspicious-program, Execution of Persistent Suspicious Program>> |Identifies execution of suspicious persistent programs (scripts, rundll32, etc.) by looking at process lineage and command line usage. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |101 <<execution-of-persistent-suspicious-program-history, Version history>>
+|<<disable-windows-event-and-security-logs-using-built-in-tools, Disable Windows Event and Security Logs Using Built-in Tools>> |Identifies attempts to disable EventLog via the logman Windows utility, PowerShell, or auditpol. This is often done by attackers in an attempt to evade detection on a system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
 
-|<<execution-via-electron-child-process-node.js-module, Execution via Electron Child Process Node.js Module>> |Identifies attempts to execute a child process from within the context of an Electron application using the child_process Node.js module. Adversaries may abuse this technique to inherit permissions from parent processes. |[Elastic] [Host] [macOS] [Threat Detection] [Defense Evasion] [Execution]  |7.12.0 |100 <<execution-via-electron-child-process-node.js-module-history, Version history>>
+|<<disable-windows-firewall-rules-via-netsh, Disable Windows Firewall Rules via Netsh>> |Identifies use of the netsh.exe to disable or weaken the local firewall. Attackers will use this command line tool to disable the firewall during troubleshooting or to enable network mobility. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<execution-via-mssql-xp_cmdshell-stored-procedure, Execution via MSSQL xp_cmdshell Stored Procedure>> |Identifies execution via MSSQL xp_cmdshell stored procedure. Malicious users may attempt to elevate their privileges by using xp_cmdshell, which is disabled by default, thus, it's important to review the context of it's use. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Investigation Guide] [Elastic Endgame]  |7.10.0 |102 <<execution-via-mssql-xp_cmdshell-stored-procedure-history, Version history>>
+|<<disabling-user-account-control-via-registry-modification, Disabling User Account Control via Registry Modification>> |User Account Control (UAC) can help mitigate the impact of malware on Windows hosts. With UAC, apps and tasks always run in the security context of a non-administrator account, unless an administrator specifically authorizes administrator-level access to the system. This rule identifies registry value changes to bypass User Access Control (UAC) protection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
 
-|<<execution-via-tsclient-mountpoint, Execution via TSClient Mountpoint>> |Identifies execution from the Remote Desktop Protocol (RDP) shared mountpoint tsclient on the target host. This may indicate a lateral movement attempt. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.11.0 |101 <<execution-via-tsclient-mountpoint-history, Version history>>
+|<<disabling-windows-defender-security-settings-via-powershell, Disabling Windows Defender Security Settings via PowerShell>> |Identifies use of the Set-MpPreference PowerShell command to disable or weaken certain Windows Defender settings. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<execution-via-local-sxs-shared-module, Execution via local SxS Shared Module>> |Identifies the creation, change, or deletion of a DLL module within a Windows SxS local folder. Adversaries may abuse shared modules to execute malicious payloads by instructing the Windows module loader to load DLLs from arbitrary local paths. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Elastic Endgame]  |7.11.0 |101 <<execution-via-local-sxs-shared-module-history, Version history>>
+|<<discovery-of-domain-groups, Discovery of Domain Groups>> |Identifies the execution of Linux built-in commands related to account or group enumeration. Adversaries may use account and group information to orient themselves before deciding how to act. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |2
 
-|<<execution-with-explicit-credentials-via-scripting, Execution with Explicit Credentials via Scripting>> |Identifies execution of the security_authtrampoline process via a scripting interpreter. This occurs when programs use AuthorizationExecute-WithPrivileges from the Security.framework to run another program with root privileges. It should not be run by itself, as this is a sign of execution with explicit logon credentials. |[Elastic] [Host] [macOS] [Threat Detection] [Execution] [Privilege Escalation]  |7.11.0 |100 <<execution-with-explicit-credentials-via-scripting-history, Version history>>
+|<<discovery-of-internet-capabilities-via-built-in-tools, Discovery of Internet Capabilities via Built-in Tools>> |Identifies the use of built-in tools attackers can use to check for Internet connectivity on compromised systems. These results may be used to determine communication capabilities with C2 servers, or to identify routes, redirectors, and proxy servers. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend] |8.6.0 |102
 
-|<<exploit-detected-elastic-endgame, Exploit - Detected - Elastic Endgame>> |Elastic Endgame detected an Exploit. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame] [Threat Detection] [Execution] [Privilege Escalation]  |7.6.0 |100 <<exploit-detected-elastic-endgame-history, Version history>>
+|<<domain-added-to-google-workspace-trusted-domains, Domain Added to Google Workspace Trusted Domains>> |Detects when a domain is added to the list of trusted Google Workspace domains. An adversary may add a trusted domain in order to collect and exfiltrate data from their target’s organization with less restrictive security controls. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Configuration Audit], [Tactic: Defense Evasion], [Resources: Investigation Guide] |8.4.0 |205
 
-|<<exploit-prevented-elastic-endgame, Exploit - Prevented - Elastic Endgame>> |Elastic Endgame prevented an Exploit. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame] [Threat Detection] [Execution] [Privilege Escalation]  |7.6.0 |100 <<exploit-prevented-elastic-endgame-history, Version history>>
+|<<downloaded-shortcut-files, Downloaded Shortcut Files>> |Identifies .lnk shortcut file downloaded from outside the local network. These shortcut files are commonly used in phishing campaigns. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<exporting-exchange-mailbox-via-powershell, Exporting Exchange Mailbox via PowerShell>> |Identifies the use of the Exchange PowerShell cmdlet, New-MailBoxExportRequest, to export the contents of a primary mailbox or archive to a .pst file. Adversaries may target user email to collect sensitive information. |[Elastic] [Host] [Windows] [Threat Detection] [Collection] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<exporting-exchange-mailbox-via-powershell-history, Version history>>
+|<<downloaded-url-files, Downloaded URL Files>> |Identifies .url shortcut files downloaded from outside the local network. These shortcut files are commonly used in phishing campaigns. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |2
 
-|<<external-alerts, External Alerts>> |Generates a detection alert for each external alert written to the configured indices. Enabling this rule allows you to immediately begin investigating external alerts in the app. |[Elastic] [Network] [Windows] [APM] [macOS] [Linux]  |7.9.0 |100 <<external-alerts-history, Version history>>
+|<<dumping-account-hashes-via-built-in-commands, Dumping Account Hashes via Built-In Commands>> |Identifies the execution of macOS built-in commands used to dump user account hashes. Adversaries may attempt to dump credentials to obtain account login information in the form of a hash. These hashes can be cracked or leveraged for lateral movement. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<external-ip-lookup-from-non-browser-process, External IP Lookup from Non-Browser Process>> |Identifies domains commonly used by adversaries for post-exploitation IP lookups. It is common for adversaries to test for Internet access and acquire their external IP address after they have gained access to a system. Among others, this has been observed in campaigns leveraging the information stealer, Trickbot. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide]  |7.10.0 |102 <<external-ip-lookup-from-non-browser-process-history, Version history>>
+|<<dumping-of-keychain-content-via-security-command, Dumping of Keychain Content via Security Command>> |Adversaries may dump the content of the keychain storage data from a system to acquire credentials. Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features, including Wi-Fi and website passwords, secure notes, certificates, and Kerberos. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<file-deletion-via-shred, File Deletion via Shred>> |Malware or other files dropped or created on a system by an adversary may leave traces behind as to what was done within a network and how. Adversaries may remove these files over the course of an intrusion to keep their footprint low or remove them at the end as part of the post-intrusion cleanup process. |[Elastic] [Host] [Linux] [Threat Detection] [Defense Evasion]  |7.8.0 |100 <<file-deletion-via-shred-history, Version history>>
+|<<dynamic-linker-copy, Dynamic Linker Copy>> |Detects the copying of the Linux dynamic loader binary and subsequent file creation for the purpose of creating a backup copy. This technique was seen recently being utilized by Linux malware prior to patching the dynamic loader in order to inject and preload a malicious shared object file. This activity should never occur and if it does then it should be considered highly suspicious or malicious. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Threat: Orbit], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<file-permission-modification-in-writable-directory, File Permission Modification in Writable Directory>> |Identifies file permission modifications in common writable directories by a non-root user. Adversaries often drop files or payloads into a writable directory and change permissions prior to execution. |[Elastic] [Host] [Linux] [Threat Detection] [Defense Evasion]  |7.8.0 |100 <<file-permission-modification-in-writable-directory-history, Version history>>
+|<<ec2-ami-shared-with-another-account, EC2 AMI Shared with Another Account>> |Identifies an AWS Amazon Machine Image (AMI) being shared with another AWS account. Adversaries with access may share an AMI with an external AWS account as a means of data exfiltration. AMIs can contain secrets, bash histories, code artifacts, and other sensitive data that adversaries may abuse if shared with unauthorized accounts. AMIs can be made publicly available accidentally as well. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: AWS EC2], [Use Case: Threat Detection], [Tactic: Exfiltration] |8.9.0 |1
 
-|<<file-transfer-or-listener-established-via-netcat, File Transfer or Listener Established via Netcat>> |A netcat process is engaging in network activity on a Linux host. Netcat is often used as a persistence mechanism by exporting a reverse shell or by serving a shell on a listening port. Netcat is also sometimes used for data exfiltration. |[Elastic] [Host] [Linux] [Threat Detection] [Execution] [Investigation Guide]  |7.6.0 |102 <<file-transfer-or-listener-established-via-netcat-history, Version history>>
+|<<esxi-discovery-via-find, ESXI Discovery via Find>> |Identifies instances where the 'find' command is started on a Linux system with arguments targeting specific VM-related paths, such as "/etc/vmware/", "/usr/lib/vmware/", or "/vmfs/*". These paths are associated with VMware virtualization software, and their presence in the find command arguments may indicate that a threat actor is attempting to search for, analyze, or manipulate VM-related files and configurations on the system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.5.0 |6
 
-|<<file-made-immutable-by-chattr, File made Immutable by Chattr>> |Detects a file being made immutable using the chattr binary. Making a file immutable means it cannot be deleted or renamed, no link can be created to this file, most of the file's metadata can not be modified, and the file can not be opened in write mode. Threat actors will commonly utilize this to prevent tampering or modification of their malicious files or any system files they have modified for purposes of persistence (e.g .ssh, /etc/passwd, etc.). |[Elastic] [Host] [Linux] [Threat Detection] [Defense Evasion]  |8.4.0 |100 <<file-made-immutable-by-chattr-history, Version history>>
+|<<esxi-discovery-via-grep, ESXI Discovery via Grep>> |Identifies instances where a process named 'grep', 'egrep', or 'pgrep' is started on a Linux system with arguments related to virtual machine (VM) files, such as "vmdk", "vmx", "vmxf", "vmsd", "vmsn", "vswp", "vmss", "nvram", or "vmem". These file extensions are associated with VM-related file formats, and their presence in grep command arguments may indicate that a threat actor is attempting to search for, analyze, or manipulate VM files on the system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.5.0 |6
 
-|<<finder-sync-plugin-registered-and-enabled, Finder Sync Plugin Registered and Enabled>> |Finder Sync plugins enable users to extend Finder’s functionality by modifying the user interface. Adversaries may abuse this feature by adding a rogue Finder Plugin to repeatedly execute malicious payloads for persistence. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<finder-sync-plugin-registered-and-enabled-history, Version history>>
+|<<esxi-timestomping-using-touch-command, ESXI Timestomping using Touch Command>> |Identifies instances where the 'touch' command is executed on a Linux system with the "-r" flag, which is used to modify the timestamp of a file based on another file's timestamp. The rule targets specific VM-related paths, such as "/etc/vmware/", "/usr/lib/vmware/", or "/vmfs/*". These paths are associated with VMware virtualization software, and their presence in the touch command arguments may indicate that a threat actor is attempting to tamper with timestamps of VM-related files and configurations on the system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.5.0 |8
 
-|<<full-user-mode-dumps-enabled-system-wide, Full User-Mode Dumps Enabled System-Wide>> |Identifies the enable of the full user-mode dumps feature system-wide. This feature allows Windows Error Reporting (WER) to collect data after an application crashes. This setting is a requirement for the LSASS Shtinkering attack, which fakes the communication of a crash on LSASS, generating a dump of the process memory, which gives the attacker access to the credentials present on the system without having to bring malware to the system. This setting is not enabled by default, and applications must create their registry subkeys to hold settings that enable them to collect dumps. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access]  |8.5.0 |1
+|<<eggshell-backdoor-execution, EggShell Backdoor Execution>> |Identifies the execution of and EggShell Backdoor. EggShell is a known post exploitation tool for macOS and Linux. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |103
 
-|<<gcp-firewall-rule-creation, GCP Firewall Rule Creation>> |Identifies when a firewall rule is created in Google Cloud Platform (GCP) for Virtual Private Cloud (VPC) or App Engine. These firewall rules can be configured to allow or deny connections to or from virtual machine (VM) instances or specific applications. An adversary may create a new firewall rule in order to weaken their target's security controls and allow more permissive ingress or egress traffic flows for their benefit. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.10.0 |102 <<gcp-firewall-rule-creation-history, Version history>>
+|<<elastic-agent-service-terminated, Elastic Agent Service Terminated>> |Identifies the Elastic endpoint agent has stopped and is no longer running on the host. Adversaries may attempt to disable security monitoring tools in an attempt to evade detection or prevention capabilities during an intrusion. This may also indicate an issue with the agent itself and should be addressed to ensure defensive measures are back in a stable state. |[Domain: Endpoint], [OS: Linux], [OS: Windows], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<gcp-firewall-rule-deletion, GCP Firewall Rule Deletion>> |Identifies when a firewall rule is deleted in Google Cloud Platform (GCP) for Virtual Private Cloud (VPC) or App Engine. These firewall rules can be configured to allow or deny connections to or from virtual machine (VM) instances or specific applications. An adversary may delete a firewall rule in order to weaken their target's security controls. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.10.0 |102 <<gcp-firewall-rule-deletion-history, Version history>>
+|<<emond-rules-creation-or-modification, Emond Rules Creation or Modification>> |Identifies the creation or modification of the Event Monitor Daemon (emond) rules. Adversaries may abuse this service by writing a rule to execute commands when a defined event occurs, such as system start up or user authentication. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<gcp-firewall-rule-modification, GCP Firewall Rule Modification>> |Identifies when a firewall rule is modified in Google Cloud Platform (GCP) for Virtual Private Cloud (VPC) or App Engine. These firewall rules can be modified to allow or deny connections to or from virtual machine (VM) instances or specific applications. An adversary may modify an existing firewall rule in order to weaken their target's security controls and allow more permissive ingress or egress traffic flows for their benefit. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.10.0 |102 <<gcp-firewall-rule-modification-history, Version history>>
+|<<enable-host-network-discovery-via-netsh, Enable Host Network Discovery via Netsh>> |Identifies use of the netsh.exe program to enable host discovery via the network. Attackers can use this command-line tool to weaken the host firewall settings. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<gcp-iam-custom-role-creation, GCP IAM Custom Role Creation>> |Identifies an Identity and Access Management (IAM) custom role creation in Google Cloud Platform (GCP). Custom roles are user-defined, and allow for the bundling of one or more supported permissions to meet specific needs. Custom roles will not be updated automatically and could lead to privilege creep if not carefully scrutinized. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |102 <<gcp-iam-custom-role-creation-history, Version history>>
+|<<encoded-executable-stored-in-the-registry, Encoded Executable Stored in the Registry>> |Identifies registry write modifications to hide an encoded portable executable. This could be indicative of adversary defense evasion by avoiding the storing of malicious content directly on disk. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
 
-|<<gcp-iam-role-deletion, GCP IAM Role Deletion>> |Identifies an Identity and Access Management (IAM) role deletion in Google Cloud Platform (GCP). A role contains a set of permissions that allows you to perform specific actions on Google Cloud resources. An adversary may delete an IAM role to inhibit access to accounts utilized by legitimate users. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |102 <<gcp-iam-role-deletion-history, Version history>>
+|<<encrypting-files-with-winrar-or-7z, Encrypting Files with WinRar or 7z>> |Identifies use of WinRar or 7z to create an encrypted files. Adversaries will often compress and encrypt data in preparation for exfiltration. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<gcp-iam-service-account-key-deletion, GCP IAM Service Account Key Deletion>> |Identifies the deletion of an Identity and Access Management (IAM) service account key in Google Cloud Platform (GCP). Each service account is associated with two sets of public/private RSA key pairs that are used to authenticate. If a key is deleted, the application will no longer be able to access Google Cloud resources using that key. A security best practice is to rotate your service account keys regularly. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |102 <<gcp-iam-service-account-key-deletion-history, Version history>>
+|<<endpoint-security, Endpoint Security>> |Generates a detection alert each time an Elastic Endpoint Security alert is received. Enabling this rule allows you to immediately begin investigating your Endpoint alerts. |[Data Source: Elastic Defend] |8.3.0 |103
 
-|<<gcp-logging-bucket-deletion, GCP Logging Bucket Deletion>> |Identifies a Logging bucket deletion in Google Cloud Platform (GCP). Log buckets are containers that store and organize log data. A deleted bucket stays in a pending state for 7 days, and Logging continues to route logs to the bucket during that time. To stop routing logs to a deleted bucket, you can delete the log sinks that have the bucket as their destination, or modify the filter for the sinks to stop it from routing logs to the deleted bucket. An adversary may delete a log bucket to evade detection. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.10.0 |102 <<gcp-logging-bucket-deletion-history, Version history>>
+|<<enumerating-domain-trusts-via-dsquery-exe, Enumerating Domain Trusts via DSQUERY.EXE>> |Identifies the use of dsquery.exe for domain trust discovery purposes. Adversaries may use this command-line utility to enumerate trust relationships that may be used for Lateral Movement opportunities in Windows multi-domain forest environments. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |7
 
-|<<gcp-logging-sink-deletion, GCP Logging Sink Deletion>> |Identifies a Logging sink deletion in Google Cloud Platform (GCP). Every time a log entry arrives, Logging compares the log entry to the sinks in that resource. Each sink whose filter matches the log entry writes a copy of the log entry to the sink's export destination. An adversary may delete a Logging sink to evade detection. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.10.0 |102 <<gcp-logging-sink-deletion-history, Version history>>
+|<<enumerating-domain-trusts-via-nltest-exe, Enumerating Domain Trusts via NLTEST.EXE>> |Identifies the use of nltest.exe for domain trust discovery purposes. Adversaries may use this command-line utility to enumerate domain trusts and gain insight into trust relationships, as well as the state of Domain Controller (DC) replication in a Microsoft Windows NT Domain. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<gcp-logging-sink-modification, GCP Logging Sink Modification>> |Identifies a modification to a Logging sink in Google Cloud Platform (GCP). Logging compares the log entry to the sinks in that resource. Each sink whose filter matches the log entry writes a copy of the log entry to the sink's export destination. An adversary may update a Logging sink to exfiltrate logs to a different export destination. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.10.0 |102 <<gcp-logging-sink-modification-history, Version history>>
+|<<enumeration-command-spawned-via-wmiprvse, Enumeration Command Spawned via WMIPrvSE>> |Identifies native Windows host and network enumeration commands spawned by the Windows Management Instrumentation Provider Service (WMIPrvSE). |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<gcp-pub-sub-subscription-creation, GCP Pub/Sub Subscription Creation>> |Identifies the creation of a subscription in Google Cloud Platform (GCP). In GCP, the publisher-subscriber relationship (Pub/Sub) is an asynchronous messaging service that decouples event-producing and event-processing services. A subscription is a named resource representing the stream of messages to be delivered to the subscribing application. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.10.0 |102 <<gcp-pub-sub-subscription-creation-history, Version history>>
+|<<enumeration-of-administrator-accounts, Enumeration of Administrator Accounts>> |Identifies instances of lower privilege accounts enumerating Administrator accounts or groups using built-in Windows tools. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
 
-|<<gcp-pub-sub-subscription-deletion, GCP Pub/Sub Subscription Deletion>> |Identifies the deletion of a subscription in Google Cloud Platform (GCP). In GCP, the publisher-subscriber relationship (Pub/Sub) is an asynchronous messaging service that decouples event-producing and event-processing services. A subscription is a named resource representing the stream of messages to be delivered to the subscribing application. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.10.0 |102 <<gcp-pub-sub-subscription-deletion-history, Version history>>
+|<<enumeration-of-kernel-modules, Enumeration of Kernel Modules>> |Loadable Kernel Modules (or LKMs) are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. This identifies attempts to enumerate information about a kernel module. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.6.0 |209
 
-|<<gcp-pub-sub-topic-creation, GCP Pub/Sub Topic Creation>> |Identifies the creation of a topic in Google Cloud Platform (GCP). In GCP, the publisher-subscriber relationship (Pub/Sub) is an asynchronous messaging service that decouples event-producing and event-processing services. A topic is used to forward messages from publishers to subscribers. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.10.0 |102 <<gcp-pub-sub-topic-creation-history, Version history>>
+|<<enumeration-of-kernel-modules-via-proc, Enumeration of Kernel Modules via Proc>> |Loadable Kernel Modules (or LKMs) are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. This identifies attempts to enumerate information about a kernel module using the /proc/modules filesystem. This filesystem is used by utilities such as lsmod and kmod to list the available kernel modules. |[Data Source: Auditd Manager], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR] |8.6.0 |106
 
-|<<gcp-pub-sub-topic-deletion, GCP Pub/Sub Topic Deletion>> |Identifies the deletion of a topic in Google Cloud Platform (GCP). In GCP, the publisher-subscriber relationship (Pub/Sub) is an asynchronous messaging service that decouples event-producing and event-processing services. A publisher application creates and sends messages to a topic. Deleting a topic can interrupt message flow in the Pub/Sub pipeline. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Log Auditing]  |7.10.0 |102 <<gcp-pub-sub-topic-deletion-history, Version history>>
+|<<enumeration-of-privileged-local-groups-membership, Enumeration of Privileged Local Groups Membership>> |Identifies instances of an unusual process enumerating built-in Windows privileged local groups membership like Administrators or Remote Desktop users. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Resources: Investigation Guide] |8.12.0 |311
 
-|<<gcp-service-account-creation, GCP Service Account Creation>> |Identifies when a new service account is created in Google Cloud Platform (GCP). A service account is a special type of account used by an application or a virtual machine (VM) instance, not a person. Applications use service accounts to make authorized API calls, authorized as either the service account itself, or as G Suite or Cloud Identity users through domain-wide delegation. If service accounts are not tracked and managed properly, they can present a security risk. An adversary may create a new service account to use during their operations in order to avoid using a standard user account and attempt to evade detection. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |102 <<gcp-service-account-creation-history, Version history>>
+|<<enumeration-of-users-or-groups-via-built-in-commands, Enumeration of Users or Groups via Built-in Commands>> |Identifies the execution of macOS built-in commands related to account or group enumeration. Adversaries may use account and group information to orient themselves before deciding how to act. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend] |8.7.0 |207
 
-|<<gcp-service-account-deletion, GCP Service Account Deletion>> |Identifies when a service account is deleted in Google Cloud Platform (GCP). A service account is a special type of account used by an application or a virtual machine (VM) instance, not a person. Applications use service accounts to make authorized API calls, authorized as either the service account itself, or as G Suite or Cloud Identity users through domain-wide delegation. An adversary may delete a service account in order to disrupt their target's business operations. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |102 <<gcp-service-account-deletion-history, Version history>>
+|<<exchange-mailbox-export-via-powershell, Exchange Mailbox Export via PowerShell>> |Identifies the use of the Exchange PowerShell cmdlet, New-MailBoxExportRequest, to export the contents of a primary mailbox or archive to a .pst file. Adversaries may target user email to collect sensitive information. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.12.0 |108
 
-|<<gcp-service-account-disabled, GCP Service Account Disabled>> |Identifies when a service account is disabled in Google Cloud Platform (GCP). A service account is a special type of account used by an application or a virtual machine (VM) instance, not a person. Applications use service accounts to make authorized API calls, authorized as either the service account itself, or as G Suite or Cloud Identity users through domain-wide delegation. An adversary may disable a service account in order to disrupt to disrupt their target's business operations. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |102 <<gcp-service-account-disabled-history, Version history>>
+|<<executable-file-creation-with-multiple-extensions, Executable File Creation with Multiple Extensions>> |Masquerading can allow an adversary to evade defenses and better blend in with the environment. One way it occurs is when the name or location of a file is manipulated as a means of tricking a user into executing what they think is a benign file type but is actually executable code. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<gcp-service-account-key-creation, GCP Service Account Key Creation>> |Identifies when a new key is created for a service account in Google Cloud Platform (GCP). A service account is a special type of account used by an application or a virtual machine (VM) instance, not a person. Applications use service accounts to make authorized API calls, authorized as either the service account itself, or as G Suite or Cloud Identity users through domain-wide delegation. If private keys are not tracked and managed properly, they can present a security risk. An adversary may create a new key for a service account in order to attempt to abuse the permissions assigned to that account and evade detection. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |102 <<gcp-service-account-key-creation-history, Version history>>
+|<<executable-file-with-unusual-extension, Executable File with Unusual Extension>> |Identifies the creation or modification of an executable file with an unexpected file extension. Attackers may attempt to evade detection by masquerading files using the file extension values used by image, audio, or document file types. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<gcp-storage-bucket-configuration-modification, GCP Storage Bucket Configuration Modification>> |Identifies when the configuration is modified for a storage bucket in Google Cloud Platform (GCP). An adversary may modify the configuration of a storage bucket in order to weaken the security controls of their target's environment. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Identity and Access] [Defense Evasion]  |7.10.0 |102 <<gcp-storage-bucket-configuration-modification-history, Version history>>
+|<<executable-masquerading-as-kernel-process, Executable Masquerading as Kernel Process>> |Monitors for kernel processes with associated process executable fields that are not empty. Unix kernel processes such as kthreadd and kworker typically do not have process.executable fields associated to them. Attackers may attempt to hide their malicious programs by masquerading as legitimate kernel processes. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |2
 
-|<<gcp-storage-bucket-deletion, GCP Storage Bucket Deletion>> |Identifies when a Google Cloud Platform (GCP) storage bucket is deleted. An adversary may delete a storage bucket in order to disrupt their target's business operations. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Monitoring]  |7.10.0 |102 <<gcp-storage-bucket-deletion-history, Version history>>
+|<<execution-from-unusual-directory-command-line, Execution from Unusual Directory - Command Line>> |Identifies process execution from suspicious default Windows directories. This may be abused by adversaries to hide malware in trusted paths. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
 
-|<<gcp-storage-bucket-permissions-modification, GCP Storage Bucket Permissions Modification>> |Identifies when the Identity and Access Management (IAM) permissions are modified for a Google Cloud Platform (GCP) storage bucket. An adversary may modify the permissions on a storage bucket to weaken their target's security controls or an administrator may inadvertently modify the permissions, which could lead to data exposure or loss. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |102 <<gcp-storage-bucket-permissions-modification-history, Version history>>
+|<<execution-from-a-removable-media-with-network-connection, Execution from a Removable Media with Network Connection>> |Identifies process execution from a removable media and by an unusual process. Adversaries may move onto systems, possibly those on disconnected or air-gapped networks, by copying malware to removable media and taking advantage of Autorun features when the media is inserted into a system and executes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Data Source: Elastic Defend] |8.3.0 |3
 
-|<<gcp-virtual-private-cloud-network-deletion, GCP Virtual Private Cloud Network Deletion>> |Identifies when a Virtual Private Cloud (VPC) network is deleted in Google Cloud Platform (GCP). A VPC network is a virtual version of a physical network within a GCP project. Each VPC network has its own subnets, routes, and firewall, as well as other elements. An adversary may delete a VPC network in order to disrupt their target's network and business operations. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Configuration Audit] [Defense Evasion]  |7.10.0 |102 <<gcp-virtual-private-cloud-network-deletion-history, Version history>>
+|<<execution-of-com-object-via-xwizard, Execution of COM object via Xwizard>> |Windows Component Object Model (COM) is an inter-process communication (IPC) component of the native Windows application programming interface (API) that enables interaction between software objects or executable code. Xwizard can be used to run a COM object created in registry to evade defensive counter measures. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<gcp-virtual-private-cloud-route-creation, GCP Virtual Private Cloud Route Creation>> |Identifies when a virtual private cloud (VPC) route is created in Google Cloud Platform (GCP). Google Cloud routes define the paths that network traffic takes from a virtual machine (VM) instance to other destinations. These destinations can be inside a Google VPC network or outside it. An adversary may create a route in order to impact the flow of network traffic in their target's cloud environment. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Configuration Audit] [Defense Evasion]  |7.10.0 |102 <<gcp-virtual-private-cloud-route-creation-history, Version history>>
+|<<execution-of-file-written-or-modified-by-microsoft-office, Execution of File Written or Modified by Microsoft Office>> |Identifies an executable created by a Microsoft Office application and subsequently executed. These processes are often launched via scripts inside documents or during exploitation of Microsoft Office applications. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<gcp-virtual-private-cloud-route-deletion, GCP Virtual Private Cloud Route Deletion>> |Identifies when a Virtual Private Cloud (VPC) route is deleted in Google Cloud Platform (GCP). Google Cloud routes define the paths that network traffic takes from a virtual machine (VM) instance to other destinations. These destinations can be inside a Google VPC network or outside it. An adversary may delete a route in order to impact the flow of network traffic in their target's cloud environment. |[Elastic] [Cloud] [GCP] [Continuous Monitoring] [SecOps] [Configuration Audit] [Defense Evasion]  |7.10.0 |102 <<gcp-virtual-private-cloud-route-deletion-history, Version history>>
+|<<execution-of-file-written-or-modified-by-pdf-reader, Execution of File Written or Modified by PDF Reader>> |Identifies a suspicious file that was written by a PDF reader application and subsequently executed. These processes are often launched via exploitation of PDF applications. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<google-drive-ownership-transferred-via-google-workspace, Google Drive Ownership Transferred via Google Workspace>> |Drive and Docs is a Google Workspace service that allows users to leverage Google Drive and Google Docs. Access to files is based on inherited permissions from the child organizational unit the user belongs to which is scoped by administrators. Typically if a user is removed, their files can be transferred to another user by the administrator. This service can also be abused by adversaries to transfer files to an adversary account for potential exfiltration. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Collection]  |8.5.0 |2 <<google-drive-ownership-transferred-via-google-workspace-history, Version history>>
+|<<execution-of-persistent-suspicious-program, Execution of Persistent Suspicious Program>> |Identifies execution of suspicious persistent programs (scripts, rundll32, etc.) by looking at process lineage and command line usage. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
 
-|<<google-workspace-2sv-policy-disabled, Google Workspace 2SV Policy Disabled>> |Google Workspace admins may setup 2-step verification (2SV) to add an extra layer of security to user accounts by asking users to verify their identity when they use login credentials. Admins have the ability to enforce 2SV from the admin console as well as the methods acceptable for verification and enrollment period. 2SV requires enablement on admin accounts prior to it being enabled for users within organization units. Adversaries may disable 2SV to lower the security requirements to access a valid account. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Configuration Audit] [Persistence]  |8.5.0 |2 <<google-workspace-2sv-policy-disabled-history, Version history>>
+|<<execution-of-an-unsigned-service, Execution of an Unsigned Service>> |This rule identifies the execution of unsigned executables via service control manager (SCM). Adversaries may abuse SCM to execute malware or escalate privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend] |8.6.0 |105
 
-|<<google-workspace-api-access-granted-via-domain-wide-delegation-of-authority, Google Workspace API Access Granted via Domain-Wide Delegation of Authority>> |Detects when a domain-wide delegation of authority is granted to a service account. Domain-wide delegation can be configured to grant third-party and internal applications to access the data of Google Workspace users. An adversary may configure domain-wide delegation to maintain access to their target’s data. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.11.0 |101 <<google-workspace-api-access-granted-via-domain-wide-delegation-of-authority-history, Version history>>
+|<<execution-via-electron-child-process-node-js-module, Execution via Electron Child Process Node.js Module>> |Identifies attempts to execute a child process from within the context of an Electron application using the child_process Node.js module. Adversaries may abuse this technique to inherit permissions from parent processes. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<google-workspace-admin-role-assigned-to-a-user, Google Workspace Admin Role Assigned to a User>> |Assigning the administrative role to a user will grant them access to the Google Admin console and grant them administrator privileges which allow them to access and manage various resources and applications. An adversary may create a new administrator account for persistence or apply the admin role to an existing user to carry out further intrusion efforts. Users with super-admin privileges can bypass single-sign on if enabled in Google Workspace. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Identity and Access] [Persistence]  |7.11.0 |102 <<google-workspace-admin-role-assigned-to-a-user-history, Version history>>
+|<<execution-via-ms-visualstudio-pre-post-build-events, Execution via MS VisualStudio Pre/Post Build Events>> |Identifies the execution of a command via Microsoft Visual Studio Pre or Post build events. Adversaries may backdoor a trusted visual studio project to execute a malicious command during the project build process. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<google-workspace-admin-role-deletion, Google Workspace Admin Role Deletion>> |Detects when a custom admin role is deleted. An adversary may delete a custom admin role in order to impact the permissions or capabilities of system administrators. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Identity and Access] [Impact]  |7.11.0 |101 <<google-workspace-admin-role-deletion-history, Version history>>
+|<<execution-via-mssql-xp-cmdshell-stored-procedure, Execution via MSSQL xp_cmdshell Stored Procedure>> |Identifies execution via MSSQL xp_cmdshell stored procedure. Malicious users may attempt to elevate their privileges by using xp_cmdshell, which is disabled by default, thus, it's important to review the context of it's use. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<google-workspace-bitlocker-setting-disabled, Google Workspace Bitlocker Setting Disabled>> |Google Workspace administrators whom manage Windows devices and have Windows device management enabled may also enable BitLocker drive encryption to mitigate unauthorized data access on lost or stolen computers. Adversaries with valid account access may disable BitLocker to access sensitive data on an endpoint added to Google Workspace device management. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Configuration Audit] [Defense Evasion]  |8.5.0 |2 <<google-workspace-bitlocker-setting-disabled-history, Version history>>
+|<<execution-via-microsoft-dotnet-clickonce-host, Execution via Microsoft DotNet ClickOnce Host>> |Identifies the execution of DotNet ClickOnce installer via Dfsvc.exe trampoline. Adversaries may take advantage of ClickOnce to proxy execution of malicious payloads via trusted Microsoft processes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |1
 
-|<<google-workspace-custom-admin-role-created, Google Workspace Custom Admin Role Created>> |Detects when a custom admin role is created in Google Workspace. An adversary may create a custom admin role in order to elevate the permissions of other user accounts and persist in their target’s environment. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.11.0 |101 <<google-workspace-custom-admin-role-created-history, Version history>>
+|<<execution-via-tsclient-mountpoint, Execution via TSClient Mountpoint>> |Identifies execution from the Remote Desktop Protocol (RDP) shared mountpoint tsclient on the target host. This may indicate a lateral movement attempt. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<google-workspace-custom-gmail-route-created-or-modified, Google Workspace Custom Gmail Route Created or Modified>> |Detects when a custom Gmail route is added or modified in Google Workspace. Adversaries can add a custom e-mail route for outbound mail to route these e-mails to their own inbox of choice for data gathering. This allows adversaries to capture sensitive information from e-mail and potential attachments, such as invoices or payment documents. By default, all email from current Google Workspace users with accounts are routed through a domain's mail server for inbound and outbound mail. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Collection]  |8.5.0 |2 <<google-workspace-custom-gmail-route-created-or-modified-history, Version history>>
+|<<execution-via-windows-subsystem-for-linux, Execution via Windows Subsystem for Linux>> |Detects attempts to execute a program on the host from the Windows Subsystem for Linux. Adversaries may enable and use WSL for Linux to avoid detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |6
 
-|<<google-workspace-mfa-enforcement-disabled, Google Workspace MFA Enforcement Disabled>> |Detects when multi-factor authentication (MFA) enforcement is disabled for Google Workspace users. An adversary may disable MFA enforcement in order to weaken an organization’s security controls. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Configuration Audit] [Impact] [Investigation Guide]  |7.11.0 |103 <<google-workspace-mfa-enforcement-disabled-history, Version history>>
+|<<execution-via-local-sxs-shared-module, Execution via local SxS Shared Module>> |Identifies the creation, change, or deletion of a DLL module within a Windows SxS local folder. Adversaries may abuse shared modules to execute malicious payloads by instructing the Windows module loader to load DLLs from arbitrary local paths. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<google-workspace-password-policy-modified, Google Workspace Password Policy Modified>> |Detects when a Google Workspace password policy is modified. An adversary may attempt to modify a password policy in order to weaken an organization’s security controls. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Identity and Access] [Persistence]  |7.11.0 |101 <<google-workspace-password-policy-modified-history, Version history>>
+|<<execution-with-explicit-credentials-via-scripting, Execution with Explicit Credentials via Scripting>> |Identifies execution of the security_authtrampoline process via a scripting interpreter. This occurs when programs use AuthorizationExecute-WithPrivileges from the Security.framework to run another program with root privileges. It should not be run by itself, as this is a sign of execution with explicit logon credentials. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<google-workspace-restrictions-for-google-marketplace-modified-to-allow-any-app, Google Workspace Restrictions for Google Marketplace Modified to Allow Any App>> |Detects when the Google Marketplace restrictions are changed to allow any application for users in Google Workspace. Malicious APKs created by adversaries may be uploaded to the Google marketplace but not installed on devices managed within Google Workspace. Administrators should set restrictions to not allow any application from the marketplace for security reasons. Adversaries may enable any app to be installed and executed on mobile devices within a Google Workspace environment prior to distributing the malicious APK to the end user. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Configuration Audit] [Defense Evasion]  |8.5.0 |2 <<google-workspace-restrictions-for-google-marketplace-modified-to-allow-any-app-history, Version history>>
+|<<expired-or-revoked-driver-loaded, Expired or Revoked Driver Loaded>> |Identifies an attempt to load a revoked or expired driver. Adversaries may bring outdated drivers with vulnerabilities to gain code execution in kernel mode or abuse revoked certificates to sign their drivers. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |5
 
-|<<google-workspace-role-modified, Google Workspace Role Modified>> |Detects when a custom admin role or its permissions are modified. An adversary may modify a custom admin role in order to elevate the permissions of other user accounts and persist in their target’s environment. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.11.0 |101 <<google-workspace-role-modified-history, Version history>>
+|<<exploit-detected-elastic-endgame, Exploit - Detected - Elastic Endgame>> |Elastic Endgame detected an Exploit. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Privilege Escalation] |8.3.0 |103
 
-|<<google-workspace-user-group-access-modified-to-allow-external-access, Google Workspace User Group Access Modified to Allow External Access>> |User groups in Google Workspace are created to help manage users permissions and access to various resources and applications. The security label is only applied to a group when users within that group are expected to access sensitive data and/or resources so administrators add this label to easily manage security groups better. Adversaries with administrator access may modify a security group to allow external access from members outside the organization. This detection does not capture all modifications to security groups, but only those that could increase the risk associated with them. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Identity and Access] [Persistence]  |8.5.0 |2 <<google-workspace-user-group-access-modified-to-allow-external-access-history, Version history>>
+|<<exploit-prevented-elastic-endgame, Exploit - Prevented - Elastic Endgame>> |Elastic Endgame prevented an Exploit. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Privilege Escalation] |8.3.0 |103
 
-|<<google-workspace-user-organizational-unit-changed, Google Workspace User Organizational Unit Changed>> |Users in Google Workspace are typically assigned a specific organizational unit that grants them permissions to certain services and roles that are inherited from this organizational unit. Adversaries may compromise a valid account and change which organizational account the user belongs to which then could allow them to inherit permissions to applications and resources inaccessible prior to. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Configuration Audit] [Persistence]  |8.5.0 |2 <<google-workspace-user-organizational-unit-changed-history, Version history>>
+|<<exporting-exchange-mailbox-via-powershell, Exporting Exchange Mailbox via PowerShell>> |Identifies the use of the Exchange PowerShell cmdlet, New-MailBoxExportRequest, to export the contents of a primary mailbox or archive to a .pst file. Adversaries may target user email to collect sensitive information. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<group-policy-abuse-for-privilege-addition, Group Policy Abuse for Privilege Addition>> |Detects the first occurrence of a modification to Group Policy Object Attributes to add privileges to user accounts or use them to add users as local admins. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Active Directory] [Investigation Guide]  |8.0.0 |102 <<group-policy-abuse-for-privilege-addition-history, Version history>>
+|<<external-alerts, External Alerts>> |Generates a detection alert for each external alert written to the configured indices. Enabling this rule allows you to immediately begin investigating external alerts in the app. |[OS: Windows], [Data Source: APM], [OS: macOS], [OS: Linux] |8.3.0 |103
 
-|<<halfbaked-command-and-control-beacon, Halfbaked Command and Control Beacon>> |Halfbaked is a malware family used to establish persistence in a contested network. This rule detects a network activity algorithm leveraged by Halfbaked implant beacons for command and control. |[Elastic] [Network] [Threat Detection] [Command and Control] [Host]  |7.10.0 |100 <<halfbaked-command-and-control-beacon-history, Version history>>
+|<<external-ip-lookup-from-non-browser-process, External IP Lookup from Non-Browser Process>> |Identifies domains commonly used by adversaries for post-exploitation IP lookups. It is common for adversaries to test for Internet access and acquire their external IP address after they have gained access to a system. Among others, this has been observed in campaigns leveraging the information stealer, Trickbot. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |108
 
-|<<high-number-of-okta-user-password-reset-or-unlock-attempts, High Number of Okta User Password Reset or Unlock Attempts>> |Identifies a high number of Okta user password reset or account unlock attempts. An adversary may attempt to obtain unauthorized access to Okta user accounts using these methods and attempt to blend in with normal activity in their target's environment and evade detection. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.10.0 |102 <<high-number-of-okta-user-password-reset-or-unlock-attempts-history, Version history>>
+|<<external-user-added-to-google-workspace-group, External User Added to Google Workspace Group>> |Detects an external Google Workspace user account being added to an existing group. Adversaries may add external user accounts as a means to intercept shared files or emails with that specific group. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Identity and Access Audit], [Tactic: Initial Access], [Resources: Investigation Guide] |8.4.0 |2
 
-|<<high-number-of-process-terminations, High Number of Process Terminations>> |This rule identifies a high number (10) of process terminations via pkill from the same host within a short time period. |[Elastic] [Host] [Linux] [Threat Detection] [Impact] [Investigation Guide]  |8.4.0 |102 <<high-number-of-process-terminations-history, Version history>>
+|<<file-compressed-or-archived-into-common-format, File Compressed or Archived into Common Format>> |Detects files being compressed or archived into common formats. This is a common technique used to obfuscate files to evade detection or to staging data for exfiltration. |[Data Source: Elastic Defend], [Domain: Endpoint], [OS: macOS], [OS: Windows], [Tactic: Collection], [Rule Type: BBR] |8.3.0 |4
 
-|<<high-number-of-process-and-or-service-terminations, High Number of Process and/or Service Terminations>> |This rule identifies a high number (10) of process terminations (stop, delete, or suspend) from the same host within a short time period. |[Elastic] [Host] [Windows] [Threat Detection] [Impact] [Investigation Guide]  |7.11.0 |102 <<high-number-of-process-and-or-service-terminations-history, Version history>>
+|<<file-creation-time-changed, File Creation Time Changed>> |Identifies modification of a file creation time. Adversaries may modify file time attributes to blend malicious content with existing files. Timestomping is a technique that modifies the timestamps of a file often to mimic files that are in trusted directories. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Sysmon] |8.3.0 |5
 
-|<<hosts-file-modified, Hosts File Modified>> |The hosts file on endpoints is used to control manual IP address to hostname resolutions. The hosts file is the first point of lookup for DNS hostname resolution so if adversaries can modify the endpoint hosts file, they can route traffic to malicious infrastructure. This rule detects modifications to the hosts file on Microsoft Windows, Linux (Ubuntu or RHEL) and macOS systems. |[Elastic] [Host] [Linux] [Windows] [macOS] [Threat Detection] [Impact] [Investigation Guide]  |7.10.0 |102 <<hosts-file-modified-history, Version history>>
+|<<file-creation-execution-and-self-deletion-in-suspicious-directory, File Creation, Execution and Self-Deletion in Suspicious Directory>> |This rule monitors for the creation of a file, followed by its execution and self-deletion in a short timespan within a directory often used for malicious purposes by threat actors. This behavior is often used by malware to execute malicious code and delete itself to hide its tracks. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |4
 
-|<<hping-process-activity, Hping Process Activity>> |Hping ran on a Linux host. Hping is a FOSS command-line packet analyzer and has the ability to construct network packets for a wide variety of network security testing applications, including scanning and firewall auditing. |[Elastic] [Host] [Linux] [Threat Detection] [Discovery]  |7.6.0 |100 <<hping-process-activity-history, Version history>>
+|<<file-deletion-via-shred, File Deletion via Shred>> |Malware or other files dropped or created on a system by an adversary may leave traces behind as to what was done within a network and how. Adversaries may remove these files over the course of an intrusion to keep their footprint low or remove them at the end as part of the post-intrusion cleanup process. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |109
 
-|<<iis-http-logging-disabled, IIS HTTP Logging Disabled>> |Identifies when Internet Information Services (IIS) HTTP Logging is disabled on a server. An attacker with IIS server access via a webshell or other mechanism can disable HTTP Logging as an effective anti-forensics measure. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.10.0 |102 <<iis-http-logging-disabled-history, Version history>>
+|<<file-made-executable-via-chmod-inside-a-container, File Made Executable via Chmod Inside A Container>> |This rule detects when chmod is used to add the execute permission to a file inside a container. Modifying file permissions to make a file executable could indicate malicious activity, as an attacker may attempt to run unauthorized or malicious code inside the container. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Defense Evasion] |8.8.0 |2
 
-|<<ipsec-nat-traversal-port-activity, IPSEC NAT Traversal Port Activity>> |This rule detects events that could be describing IPSEC NAT Traversal traffic. IPSEC is a VPN technology that allows one system to talk to another using encrypted tunnels. NAT Traversal enables these tunnels to communicate over the Internet where one of the sides is behind a NAT router gateway. This may be common on your network, but this technique is also used by threat actors to avoid detection. |[Elastic] [Host] [Network] [Threat Detection] [Command and Control] [Host]  |7.6.0 |100 <<ipsec-nat-traversal-port-activity-history, Version history>>
+|<<file-permission-modification-in-writable-directory, File Permission Modification in Writable Directory>> |Identifies file permission modifications in common writable directories by a non-root user. Adversaries often drop files or payloads into a writable directory and change permissions prior to execution. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.6.0 |210
 
-|<<image-file-execution-options-injection, Image File Execution Options Injection>> |The Debugger and SilentProcessExit registry keys can allow an adversary to intercept the execution of files, causing a different process to be executed. This functionality can be abused by an adversary to establish persistence. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<image-file-execution-options-injection-history, Version history>>
+|<<file-staged-in-root-folder-of-recycle-bin, File Staged in Root Folder of Recycle Bin>> |Identifies files written to the root of the Recycle Bin folder instead of subdirectories. Adversaries may place files in the root of the Recycle Bin in preparation for exfiltration or to evade defenses. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |3
 
-|<<imageload-via-windows-update-auto-update-client, ImageLoad via Windows Update Auto Update Client>> |Identifies abuse of the Windows Update Auto Update Client (wuauclt.exe) to load an arbitrary DLL. This behavior is used as a defense evasion technique to blend-in malicious activity with legitimate Windows software. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.11.0 |102 <<imageload-via-windows-update-auto-update-client-history, Version history>>
+|<<file-system-debugger-launched-inside-a-privileged-container, File System Debugger Launched Inside a Privileged Container>> |This rule detects the use of the built-in Linux DebugFS utility from inside a privileged container. DebugFS is a special file system debugging utility which supports reading and writing directly from a hard drive device. When launched inside a privileged container, a container deployed with all the capabilities of the host machine, an attacker can access sensitive host level files which could be used for further privilege escalation and container escapes to the host machine. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.10.0 |1
 
-|<<inbound-connection-to-an-unsecure-elasticsearch-node, Inbound Connection to an Unsecure Elasticsearch Node>> |Identifies Elasticsearch nodes that do not have Transport Layer Security (TLS), and/or lack authentication, and are accepting inbound network connections over the default Elasticsearch port. |[Elastic] [Network] [Threat Detection] [Initial Access] [Host]  |7.10.0 |100 <<inbound-connection-to-an-unsecure-elasticsearch-node-history, Version history>>
+|<<file-transfer-or-listener-established-via-netcat, File Transfer or Listener Established via Netcat>> |A netcat process is engaging in network activity on a Linux host. Netcat is often used as a persistence mechanism by exporting a reverse shell or by serving a shell on a listening port. Netcat is also sometimes used for data exfiltration. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<incoming-dcom-lateral-movement-via-mshta, Incoming DCOM Lateral Movement via MSHTA>> |Identifies the use of Distributed Component Object Model (DCOM) to execute commands from a remote host, which are launched via the HTA Application COM Object. This behavior may indicate an attacker abusing a DCOM application to move laterally while attempting to evade detection. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.11.0 |101 <<incoming-dcom-lateral-movement-via-mshta-history, Version history>>
+|<<file-and-directory-permissions-modification, File and Directory Permissions Modification>> |Identifies the change of permissions/ownership of files/folders through built-in Windows utilities. Threat actors may require permission modification of files/folders to change, modify or delete them. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<incoming-dcom-lateral-movement-with-mmc, Incoming DCOM Lateral Movement with MMC>> |Identifies the use of Distributed Component Object Model (DCOM) to run commands from a remote host, which are launched via the MMC20 Application COM Object. This behavior may indicate an attacker abusing a DCOM application to move laterally. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.11.0 |101 <<incoming-dcom-lateral-movement-with-mmc-history, Version history>>
+|<<file-made-immutable-by-chattr, File made Immutable by Chattr>> |Detects a file being made immutable using the chattr binary. Making a file immutable means it cannot be deleted or renamed, no link can be created to this file, most of the file's metadata can not be modified, and the file can not be opened in write mode. Threat actors will commonly utilize this to prevent tampering or modification of their malicious files or any system files they have modified for purposes of persistence (e.g .ssh, /etc/passwd, etc.). |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<incoming-dcom-lateral-movement-with-shellbrowserwindow-or-shellwindows, Incoming DCOM Lateral Movement with ShellBrowserWindow or ShellWindows>> |Identifies use of Distributed Component Object Model (DCOM) to run commands from a remote host, which are launched via the ShellBrowserWindow or ShellWindows Application COM Object. This behavior may indicate an attacker abusing a DCOM application to stealthily move laterally. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.11.0 |101 <<incoming-dcom-lateral-movement-with-shellbrowserwindow-or-shellwindows-history, Version history>>
+|<<file-or-directory-deletion-command, File or Directory Deletion Command>> |This rule identifies the execution of commands that can be used to delete files and directories. Adversaries may delete files and directories on a host system, such as logs, browser history, or malware. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |3
 
-|<<incoming-execution-via-powershell-remoting, Incoming Execution via PowerShell Remoting>> |Identifies remote execution via Windows PowerShell remoting. Windows PowerShell remoting allows a user to run any Windows PowerShell command on one or more remote computers. This could be an indication of lateral movement. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.11.0 |100 <<incoming-execution-via-powershell-remoting-history, Version history>>
+|<<file-with-suspicious-extension-downloaded, File with Suspicious Extension Downloaded>> |Identifies unusual files downloaded from outside the local network that have the potential to be abused for code execution. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |3
 
-|<<incoming-execution-via-winrm-remote-shell, Incoming Execution via WinRM Remote Shell>> |Identifies remote execution via Windows Remote Management (WinRM) remote shell on a target host. This could be an indication of lateral movement. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.11.0 |100 <<incoming-execution-via-winrm-remote-shell-history, Version history>>
+|<<finder-sync-plugin-registered-and-enabled, Finder Sync Plugin Registered and Enabled>> |Finder Sync plugins enable users to extend Finder’s functionality by modifying the user interface. Adversaries may abuse this feature by adding a rogue Finder Plugin to repeatedly execute malicious payloads for persistence. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.11.0 |206
 
-|<<installutil-process-making-network-connections, InstallUtil Process Making Network Connections>> |Identifies InstallUtil.exe making outbound network connections. This may indicate adversarial activity as InstallUtil is often leveraged by adversaries to execute code and evade detection. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.10.0 |101 <<installutil-process-making-network-connections-history, Version history>>
+|<<first-occurrence-github-event-for-a-personal-access-token-pat, First Occurrence GitHub Event for a Personal Access Token (PAT)>> |Detects a first occurrence event for a personal access token (PAT) not seen in the last 14 days. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Execution], [Rule Type: BBR], [Data Source: Github] |8.8.0 |1
 
-|<<installation-of-custom-shim-databases, Installation of Custom Shim Databases>> |Identifies the installation of custom Application Compatibility Shim databases. This Windows functionality has been abused by attackers to stealthily gain persistence and arbitrary code execution in legitimate Windows processes. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.10.0 |101 <<installation-of-custom-shim-databases-history, Version history>>
+|<<first-occurrence-of-github-repo-interaction-from-a-new-ip, First Occurrence of GitHub Repo Interaction From a New IP>> |Detects an interaction with a private GitHub repository from a new IP address not seen in the last 14 days. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Execution], [Rule Type: BBR], [Data Source: Github] |8.8.0 |1
 
-|<<installation-of-security-support-provider, Installation of Security Support Provider>> |Identifies registry modifications related to the Windows Security Support Provider (SSP) configuration. Adversaries may abuse this to establish persistence in an environment. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<installation-of-security-support-provider-history, Version history>>
+|<<first-occurrence-of-github-user-interaction-with-private-repo, First Occurrence of GitHub User Interaction with Private Repo>> |Detects a new private repo interaction for a GitHub user not seen in the last 14 days. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Execution], [Rule Type: BBR], [Data Source: Github] |8.6.0 |1
 
-|<<interactive-terminal-spawned-via-perl, Interactive Terminal Spawned via Perl>> |Identifies when a terminal (tty) is spawned via Perl. Attackers may upgrade a simple reverse shell to a fully interactive tty after obtaining initial access to a host. |[Elastic] [Host] [Linux] [Threat Detection] [Execution]  |7.8.0 |100 <<interactive-terminal-spawned-via-perl-history, Version history>>
+|<<first-occurrence-of-ip-address-for-github-personal-access-token-pat, First Occurrence of IP Address For GitHub Personal Access Token (PAT)>> |Detects a new IP address used for a GitHub PAT not previously seen in the last 14 days. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Initial Access], [Rule Type: BBR], [Data Source: Github] |8.8.0 |1
 
-|<<interactive-terminal-spawned-via-python, Interactive Terminal Spawned via Python>> |Identifies when a terminal (tty) is spawned via Python. Attackers may upgrade a simple reverse shell to a fully interactive tty after obtaining initial access to a host. |[Elastic] [Host] [Linux] [Threat Detection] [Execution]  |7.8.0 |100 <<interactive-terminal-spawned-via-python-history, Version history>>
+|<<first-occurrence-of-ip-address-for-github-user, First Occurrence of IP Address For GitHub User>> |Detects a new IP address used for a GitHub user not previously seen in the last 14 days. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Initial Access], [Rule Type: BBR], [Data Source: Github] |8.8.0 |1
 
-|<<krbtgt-delegation-backdoor, KRBTGT Delegation Backdoor>> |Identifies the modification of the msDS-AllowedToDelegateTo attribute to KRBTGT. Attackers can use this technique to maintain persistence to the domain by having the ability to request tickets for the KRBTGT service. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Active Directory]  |8.1.0 |100 <<krbtgt-delegation-backdoor-history, Version history>>
+|<<first-occurrence-of-okta-user-session-started-via-proxy, First Occurrence of Okta User Session Started via Proxy>> |Identifies the first occurrence of an Okta user session started via a proxy. |[Tactic: Initial Access], [Use Case: Identity and Access Audit], [Data Source: Okta] |8.10.0 |1
 
-|<<kerberos-cached-credentials-dumping, Kerberos Cached Credentials Dumping>> |Identifies the use of the Kerberos credential cache (kcc) utility to dump locally cached Kerberos tickets. Adversaries may attempt to dump credential material in the form of tickets that can be leveraged for lateral movement. |[Elastic] [Host] [macOS] [Threat Detection] [Credential Access]  |7.10.0 |100 <<kerberos-cached-credentials-dumping-history, Version history>>
+|<<first-occurrence-of-personal-access-token-pat-use-for-a-github-user, First Occurrence of Personal Access Token (PAT) Use For a GitHub User>> |A new PAT was used for a GitHub user not previously seen in the last 14 days. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Persistence], [Rule Type: BBR], [Data Source: Github] |8.8.0 |1
 
-|<<kerberos-pre-authentication-disabled-for-user, Kerberos Pre-authentication Disabled for User>> |Identifies the modification of an account's Kerberos pre-authentication options. An adversary with GenericWrite/GenericAll rights over the account can maliciously modify these settings to perform offline password cracking attacks such as AS-REP roasting. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide]  |8.1.0 |102 <<kerberos-pre-authentication-disabled-for-user-history, Version history>>
+|<<first-occurrence-of-private-repo-event-from-specific-github-personal-access-token-pat, First Occurrence of Private Repo Event from Specific GitHub Personal Access Token (PAT)>> |Detects a new private repo interaction for a GitHub PAT not seen in the last 14 days. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Execution], [Rule Type: BBR], [Data Source: Github] |8.8.0 |1
 
-|<<kerberos-traffic-from-unusual-process, Kerberos Traffic from Unusual Process>> |Identifies network connections to the standard Kerberos port from an unusual process. On Windows, the only process that normally performs Kerberos traffic from a domain joined host is lsass.exe. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide]  |7.11.0 |102 <<kerberos-traffic-from-unusual-process-history, Version history>>
+|<<first-occurrence-of-user-agent-for-a-github-personal-access-token-pat, First Occurrence of User Agent For a GitHub Personal Access Token (PAT)>> |Detects a new user agent used for a GitHub PAT not previously seen in the last 14 days. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Initial Access], [Rule Type: BBR], [Data Source: Github] |8.8.0 |1
 
-|<<kernel-module-removal, Kernel Module Removal>> |Kernel modules are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. This rule identifies attempts to remove a kernel module. |[Elastic] [Host] [Linux] [Threat Detection] [Defense Evasion]  |7.8.0 |100 <<kernel-module-removal-history, Version history>>
+|<<first-occurrence-of-user-agent-for-a-github-user, First Occurrence of User-Agent For a GitHub User>> |Detects a new user agent used for a GitHub user not previously seen in the last 14 days. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Initial Access], [Rule Type: BBR], [Data Source: Github] |8.8.0 |1
 
-|<<kernel-module-load-via-insmod, Kernel module load via insmod>> |Detects the use of the insmod binary to load a Linux kernel object file. Threat actors can use this binary, given they have root privileges, to load a rootkit on a system providing them with complete control and the ability to hide from security products. Manually loading a kernel module in this manner should not be at all common and can indicate suspcious or malicious behavior. |[Elastic] [Host] [Linux] [Threat Detection] [Persistence] [Rootkit]  |8.4.0 |100 <<kernel-module-load-via-insmod-history, Version history>>
+|<<first-time-seen-aws-secret-value-accessed-in-secrets-manager, First Time Seen AWS Secret Value Accessed in Secrets Manager>> |An adversary with access to a compromised AWS service such as an EC2 instance, Lambda function, or other service may attempt to leverage the compromised service to access secrets in AWS Secrets Manager. This rule looks for the first time a specific user identity has programmatically retrieved a specific secret value from Secrets Manager using the `GetSecretValue` action.  This rule assumes that AWS services such as Lambda functions and EC2 instances are setup with IAM role's assigned that have the necessary permissions to access the secrets in Secrets Manager. An adversary with access to a compromised AWS service such as an EC2 instance, Lambda function, or other service would rely on the compromised service's IAM role to access the secrets in Secrets Manager. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Tactic: Credential Access], [Resources: Investigation Guide] |8.9.0 |310
 
-|<<keychain-password-retrieval-via-command-line, Keychain Password Retrieval via Command Line>> |Adversaries may collect keychain storage data from a system to in order to acquire credentials. Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features, including Wi-Fi and website passwords, secure notes, certificates, and Kerberos. |[Elastic] [Host] [macOS] [Threat Detection] [Credential Access]  |7.12.0 |100 <<keychain-password-retrieval-via-command-line-history, Version history>>
+|<<first-time-seen-commonly-abused-remote-access-tool-execution, First Time Seen Commonly Abused Remote Access Tool Execution>> |Adversaries may install legitimate remote access tools (RAT) to compromised endpoints for further command-and-control (C2). Adversaries can rely on installed RATs for persistence, execution of native commands and more. This rule detects when a process is started whose name or code signature resembles commonly abused RATs. This is a New Terms rule type indicating the host has not seen this RAT process started before within the last 30 days. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.4.0 |5
 
-|<<kubernetes-anonymous-request-authorized, Kubernetes Anonymous Request Authorized>> |This rule detects when an unauthenticated user request is authorized within the cluster. Attackers may attempt to use anonymous accounts to gain initial access to the cluster or to avoid attribution of their activities within the cluster. This rule excludes the /healthz, /livez and /readyz endpoints which are commonly accessed anonymously. |[Elastic] [Kubernetes] [Continuous Monitoring] [Execution] [Initial Access] [Defense Evasion]  |8.5.0 |2 <<kubernetes-anonymous-request-authorized-history, Version history>>
+|<<first-time-seen-driver-loaded, First Time Seen Driver Loaded>> |Identifies the load of a driver with an original file name and signature values that were observed for the first time during the last 30 days. This rule type can help baseline drivers installation within your environment. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Persistence], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.6.0 |7
 
-|<<kubernetes-container-created-with-excessive-linux-capabilities, Kubernetes Container Created with Excessive Linux Capabilities>> |This rule detects a container deployed with one or more dangerously permissive Linux capabilities. An attacker with the ability to deploy a container with added capabilities could use this for further execution, lateral movement, or privilege escalation within a cluster. The capabilities detected in this rule have been used in container escapes to the host machine. |[Elastic] [Kubernetes] [Continuous Monitoring] [Execution] [Privilege Escalation]  |8.6.0 |1
+|<<first-time-seen-google-workspace-oauth-login-from-third-party-application, First Time Seen Google Workspace OAuth Login from Third-Party Application>> |Detects the first time a third-party application logs in and authenticated with OAuth. OAuth is used to grant permissions to specific resources and services in Google Workspace. Compromised credentials or service accounts could allow an adversary to authenticate to Google Workspace as a valid user and inherit their privileges. |[Domain: Cloud], [Data Source: Google Workspace], [Tactic: Defense Evasion], [Tactic: Initial Access] |8.4.0 |3
 
-|<<kubernetes-denied-service-account-request, Kubernetes Denied Service Account Request>> |This rule detects when a service account makes an unauthorized request for resources from the API server. Service accounts follow a very predictable pattern of behavior. A service account should never send an unauthorized request to the API server. This behavior is likely an indicator of compromise or of a problem within the cluster. An adversary may have gained access to credentials/tokens and this could be an attempt to access or create resources to facilitate further movement or execution within the cluster. |[Elastic] [Kubernetes] [Continuous Monitoring] [Discovery]  |8.5.0 |2 <<kubernetes-denied-service-account-request-history, Version history>>
+|<<first-time-seen-newcredentials-logon-process, First Time Seen NewCredentials Logon Process>> |Identifies a new credentials logon type performed by an unusual process. This may indicate the existence of an access token forging capability that are often abused to bypass access control restrictions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.4.0 |2
 
-|<<kubernetes-exposed-service-created-with-type-nodeport, Kubernetes Exposed Service Created With Type NodePort>> |This rule detects an attempt to create or modify a service as type NodePort. The NodePort service allows a user to externally expose a set of labeled pods to the internet. This creates an open port on every worker node in the cluster that has a pod for that service. When external traffic is received on that open port, it directs it to the specific pod through the service representing it. A malicious user can configure a service as type Nodeport in order to intercept traffic from other pods or nodes, bypassing firewalls and other network security measures configured for load balancers within a cluster. This creates a direct method of communication between the cluster and the outside world, which could be used for more malicious behavior and certainly widens the attack surface of your cluster. |[Elastic] [Kubernetes] [Continuous Monitoring] [Execution] [Persistence]  |8.4.0 |200 <<kubernetes-exposed-service-created-with-type-nodeport-history, Version history>>
+|<<first-time-seen-removable-device, First Time Seen Removable Device>> |Identifies newly seen removable devices by device friendly name using registry modification events. While this activity is not inherently malicious, analysts can use those events to aid monitoring for data exfiltration over those devices. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Exfiltration], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.4.0 |4
 
-|<<kubernetes-pod-created-with-hostipc, Kubernetes Pod Created With HostIPC>> |This rule detects an attempt to create or modify a pod using the host IPC namespace. This gives access to data used by any pod that also use the hosts IPC namespace. If any process on the host or any processes in a pod uses the hosts inter-process communication mechanisms (shared memory, semaphore arrays, message queues, etc.), an attacker can read/write to those same mechanisms. They may look for files in /dev/shm or use ipcs to check for any IPC facilities being used. |[Elastic] [Kubernetes] [Continuous Monitoring] [Execution] [Privilege Escalation]  |8.4.0 |200 <<kubernetes-pod-created-with-hostipc-history, Version history>>
+|<<firsttime-seen-account-performing-dcsync, FirstTime Seen Account Performing DCSync>> |This rule identifies when a User Account starts the Active Directory Replication Process for the first time. Attackers can use the DCSync technique to get credential information of individual accounts or the entire domain, thus compromising the entire domain. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Privilege Escalation], [Use Case: Active Directory Monitoring], [Data Source: Active Directory], [Resources: Investigation Guide] |8.4.0 |10
 
-|<<kubernetes-pod-created-with-hostnetwork, Kubernetes Pod Created With HostNetwork>> |This rules detects an attempt to create or modify a pod attached to the host network. HostNetwork allows a pod to use the node network namespace. Doing so gives the pod access to any service running on localhost of the host. An attacker could use this access to snoop on network activity of other pods on the same node or bypass restrictive network policies applied to its given namespace. |[Elastic] [Kubernetes] [Continuous Monitoring] [Execution] [Privilege Escalation]  |8.4.0 |200 <<kubernetes-pod-created-with-hostnetwork-history, Version history>>
+|<<forwarded-google-workspace-security-alert, Forwarded Google Workspace Security Alert>> |Identifies the occurrence of a security alert from the Google Workspace alerts center. Google Workspace's security alert center provides an overview of actionable alerts that may be affecting an organization's domain. An alert is a warning of a potential security issue that Google has detected. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Log Auditing], [Use Case: Threat Detection] |8.4.0 |2
 
-|<<kubernetes-pod-created-with-hostpid, Kubernetes Pod Created With HostPID>> |This rule detects an attempt to create or modify a pod attached to the host PID namespace. HostPID allows a pod to access all the processes running on the host and could allow an attacker to take malicious action. When paired with ptrace this can be used to escalate privileges outside of the container. When paired with a privileged container, the pod can see all of the processes on the host. An attacker can enter the init system (PID 1) on the host. From there, they could execute a shell and continue to escalate privileges to root. |[Elastic] [Kubernetes] [Continuous Monitoring] [Execution] [Privilege Escalation]  |8.4.0 |200 <<kubernetes-pod-created-with-hostpid-history, Version history>>
+|<<full-user-mode-dumps-enabled-system-wide, Full User-Mode Dumps Enabled System-Wide>> |Identifies the enable of the full user-mode dumps feature system-wide. This feature allows Windows Error Reporting (WER) to collect data after an application crashes. This setting is a requirement for the LSASS Shtinkering attack, which fakes the communication of a crash on LSASS, generating a dump of the process memory, which gives the attacker access to the credentials present on the system without having to bring malware to the system. This setting is not enabled by default, and applications must create their registry subkeys to hold settings that enable them to collect dumps. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Sysmon] |8.3.0 |7
 
-|<<kubernetes-pod-created-with-a-sensitive-hostpath-volume, Kubernetes Pod created with a Sensitive hostPath Volume>> |This rule detects when a pod is created with a sensitive volume of type hostPath. A hostPath volume type mounts a sensitive file or folder from the node to the container. If the container gets compromised, the attacker can use this mount for gaining access to the node. There are many ways a container with unrestricted access to the host filesystem can escalate privileges, including reading data from other containers, and accessing tokens of more privileged pods. |[Elastic] [Kubernetes] [Continuous Monitoring] [Execution] [Privilege Escalation]  |8.4.0 |200 <<kubernetes-pod-created-with-a-sensitive-hostpath-volume-history, Version history>>
+|<<gcp-firewall-rule-creation, GCP Firewall Rule Creation>> |Identifies when a firewall rule is created in Google Cloud Platform (GCP) for Virtual Private Cloud (VPC) or App Engine. These firewall rules can be configured to allow or deny connections to or from virtual machine (VM) instances or specific applications. An adversary may create a new firewall rule in order to weaken their target's security controls and allow more permissive ingress or egress traffic flows for their benefit. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<kubernetes-privileged-pod-created, Kubernetes Privileged Pod Created>> |This rule detects when a user creates a pod/container running in privileged mode. A highly privileged container has access to the node's resources and breaks the isolation between containers. If compromised, an attacker can use the privileged container to gain access to the underlying host. Gaining access to the host may provide the adversary with the opportunity to achieve follow-on objectives, such as establishing persistence, moving laterally within the environment, or setting up a command and control channel on the host. |[Elastic] [Kubernetes] [Continuous Monitoring] [Execution] [Privilege Escalation]  |8.4.0 |200 <<kubernetes-privileged-pod-created-history, Version history>>
+|<<gcp-firewall-rule-deletion, GCP Firewall Rule Deletion>> |Identifies when a firewall rule is deleted in Google Cloud Platform (GCP) for Virtual Private Cloud (VPC) or App Engine. These firewall rules can be configured to allow or deny connections to or from virtual machine (VM) instances or specific applications. An adversary may delete a firewall rule in order to weaken their target's security controls. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<kubernetes-suspicious-assignment-of-controller-service-account, Kubernetes Suspicious Assignment of Controller Service Account>> |This rule detects a request to attach a controller service account to an existing or new pod running in the kube-system namespace. By default, controllers running as part of the API Server utilize admin-equivalent service accounts hosted in the kube-system namespace. Controller service accounts aren't normally assigned to running pods and could indicate adversary behavior within the cluster. An attacker that can create or modify pods or pod controllers in the kube-system namespace, can assign one of these admin-equivalent service accounts to a pod and abuse their powerful token to escalate privileges and gain complete cluster control. |[Elastic] [Kubernetes] [Continuous Monitoring] [Execution] [Privilege Escalation]  |8.5.0 |3 <<kubernetes-suspicious-assignment-of-controller-service-account-history, Version history>>
+|<<gcp-firewall-rule-modification, GCP Firewall Rule Modification>> |Identifies when a firewall rule is modified in Google Cloud Platform (GCP) for Virtual Private Cloud (VPC) or App Engine. These firewall rules can be modified to allow or deny connections to or from virtual machine (VM) instances or specific applications. An adversary may modify an existing firewall rule in order to weaken their target's security controls and allow more permissive ingress or egress traffic flows for their benefit. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<kubernetes-suspicious-self-subject-review, Kubernetes Suspicious Self-Subject Review>> |This rule detects when a service account or node attempts to enumerate their own permissions via the selfsubjectaccessreview or selfsubjectrulesreview APIs. This is highly unusual behavior for non-human identities like service accounts and nodes. An adversary may have gained access to credentials/tokens and this could be an attempt to determine what privileges they have to facilitate further movement or execution within the cluster. |[Elastic] [Kubernetes] [Continuous Monitoring] [Discovery]  |8.4.0 |200 <<kubernetes-suspicious-self-subject-review-history, Version history>>
+|<<gcp-iam-custom-role-creation, GCP IAM Custom Role Creation>> |Identifies an Identity and Access Management (IAM) custom role creation in Google Cloud Platform (GCP). Custom roles are user-defined, and allow for the bundling of one or more supported permissions to meet specific needs. Custom roles will not be updated automatically and could lead to privilege creep if not carefully scrutinized. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Identity and Access Audit], [Tactic: Initial Access] |8.3.0 |104
 
-|<<kubernetes-user-exec-into-pod, Kubernetes User Exec into Pod>> |This rule detects a user attempt to establish a shell session into a pod using the 'exec' command. Using the 'exec' command in a pod allows a user to establish a temporary shell session and execute any process/commands in the pod. An adversary may call bash to gain a persistent interactive shell which will allow access to any data the pod has permissions to, including secrets. |[Elastic] [Kubernetes] [Continuous Monitoring] [Execution]  |8.3.0 |200 <<kubernetes-user-exec-into-pod-history, Version history>>
+|<<gcp-iam-role-deletion, GCP IAM Role Deletion>> |Identifies an Identity and Access Management (IAM) role deletion in Google Cloud Platform (GCP). A role contains a set of permissions that allows you to perform specific actions on Google Cloud resources. An adversary may delete an IAM role to inhibit access to accounts utilized by legitimate users. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Identity and Access Audit], [Tactic: Impact] |8.3.0 |104
 
-|<<lsass-memory-dump-creation, LSASS Memory Dump Creation>> |Identifies the creation of a Local Security Authority Subsystem Service (lsass.exe) default memory dump. This may indicate a credential access attempt via trusted system utilities such as Task Manager (taskmgr.exe) and SQL Dumper (sqldumper.exe) or known pentesting tools such as Dumpert and AndrewSpecial. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Elastic Endgame]  |7.11.0 |101 <<lsass-memory-dump-creation-history, Version history>>
+|<<gcp-iam-service-account-key-deletion, GCP IAM Service Account Key Deletion>> |Identifies the deletion of an Identity and Access Management (IAM) service account key in Google Cloud Platform (GCP). Each service account is associated with two sets of public/private RSA key pairs that are used to authenticate. If a key is deleted, the application will no longer be able to access Google Cloud resources using that key. A security best practice is to rotate your service account keys regularly. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Identity and Access Audit], [Tactic: Persistence] |8.3.0 |104
 
-|<<lsass-memory-dump-handle-access, LSASS Memory Dump Handle Access>> |Identifies handle requests for the Local Security Authority Subsystem Service (LSASS) object access with specific access masks that many tools with a capability to dump memory to disk use (0x1fffff, 0x1010, 0x120089). This rule is tool agnostic as it has been validated against a host of various LSASS dump tools such as SharpDump, Procdump, Mimikatz, Comsvcs etc. It detects this behavior at a low level and does not depend on a specific tool or dump file name. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide]  |8.2.0 |102 <<lsass-memory-dump-handle-access-history, Version history>>
+|<<gcp-logging-bucket-deletion, GCP Logging Bucket Deletion>> |Identifies a Logging bucket deletion in Google Cloud Platform (GCP). Log buckets are containers that store and organize log data. A deleted bucket stays in a pending state for 7 days, and Logging continues to route logs to the bucket during that time. To stop routing logs to a deleted bucket, you can delete the log sinks that have the bucket as their destination, or modify the filter for the sinks to stop it from routing logs to the deleted bucket. An adversary may delete a log bucket to evade detection. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Log Auditing], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<lateral-movement-via-startup-folder, Lateral Movement via Startup Folder>> |Identifies suspicious file creations in the startup folder of a remote system. An adversary could abuse this to move laterally by dropping a malicious script or executable that will be executed after a reboot or user logon. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.11.0 |100 <<lateral-movement-via-startup-folder-history, Version history>>
+|<<gcp-logging-sink-deletion, GCP Logging Sink Deletion>> |Identifies a Logging sink deletion in Google Cloud Platform (GCP). Every time a log entry arrives, Logging compares the log entry to the sinks in that resource. Each sink whose filter matches the log entry writes a copy of the log entry to the sink's export destination. An adversary may delete a Logging sink to evade detection. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Log Auditing], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<launch-agent-creation-or-modification-and-immediate-loading, Launch Agent Creation or Modification and Immediate Loading>> |An adversary can establish persistence by installing a new launch agent that executes at login by using launchd or launchctl to load a plist into the appropriate directories. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.11.0 |100 <<launch-agent-creation-or-modification-and-immediate-loading-history, Version history>>
+|<<gcp-logging-sink-modification, GCP Logging Sink Modification>> |Identifies a modification to a Logging sink in Google Cloud Platform (GCP). Logging compares the log entry to the sinks in that resource. Each sink whose filter matches the log entry writes a copy of the log entry to the sink's export destination. An adversary may update a Logging sink to exfiltrate logs to a different export destination. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Log Auditing], [Tactic: Exfiltration] |8.3.0 |104
 
-|<<launchdaemon-creation-or-modification-and-immediate-loading, LaunchDaemon Creation or Modification and Immediate Loading>> |Indicates the creation or modification of a launch daemon, which adversaries may use to repeatedly execute malicious payloads as part of persistence. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.11.0 |100 <<launchdaemon-creation-or-modification-and-immediate-loading-history, Version history>>
+|<<gcp-pub-sub-subscription-creation, GCP Pub/Sub Subscription Creation>> |Identifies the creation of a subscription in Google Cloud Platform (GCP). In GCP, the publisher-subscriber relationship (Pub/Sub) is an asynchronous messaging service that decouples event-producing and event-processing services. A subscription is a named resource representing the stream of messages to be delivered to the subscribing application. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Log Auditing], [Tactic: Collection] |8.3.0 |105
 
-|<<linux-restricted-shell-breakout-via-linux-binarys, Linux Restricted Shell Breakout via  Linux Binary(s)>> |Identifies Linux binary(s) abuse to breakout of restricted shells or environments by spawning an interactive system shell. The linux utility(s) activity of spawning shell is not a standard use of the binary for a user or system administrator. It may indicates an attempt to improve the capabilities or stability of an adversary access. |[Elastic] [Host] [Linux] [Threat Detection] [Execution] [GTFOBins]  |8.3.0 |100 <<linux-restricted-shell-breakout-via-linux-binarys-history, Version history>>
+|<<gcp-pub-sub-subscription-deletion, GCP Pub/Sub Subscription Deletion>> |Identifies the deletion of a subscription in Google Cloud Platform (GCP). In GCP, the publisher-subscriber relationship (Pub/Sub) is an asynchronous messaging service that decouples event-producing and event-processing services. A subscription is a named resource representing the stream of messages to be delivered to the subscribing application. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Log Auditing], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<local-account-tokenfilter-policy-disabled, Local Account TokenFilter Policy Disabled>> |Identifies registry modification to the LocalAccountTokenFilterPolicy policy. If this value exists (which doesn't by default) and is set to 1, then remote connections from all local members of Administrators are granted full high-integrity tokens during negotiation. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Privilege Escalation] [Elastic Endgame]  |8.6.0 |1
+|<<gcp-pub-sub-topic-creation, GCP Pub/Sub Topic Creation>> |Identifies the creation of a topic in Google Cloud Platform (GCP). In GCP, the publisher-subscriber relationship (Pub/Sub) is an asynchronous messaging service that decouples event-producing and event-processing services. A topic is used to forward messages from publishers to subscribers. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Log Auditing], [Tactic: Collection] |8.3.0 |105
 
-|<<local-scheduled-task-creation, Local Scheduled Task Creation>> |Indicates the creation of a scheduled task. Adversaries can use these to establish persistence, move laterally, and/or escalate privileges. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.6.0 |101 <<local-scheduled-task-creation-history, Version history>>
+|<<gcp-pub-sub-topic-deletion, GCP Pub/Sub Topic Deletion>> |Identifies the deletion of a topic in Google Cloud Platform (GCP). In GCP, the publisher-subscriber relationship (Pub/Sub) is an asynchronous messaging service that decouples event-producing and event-processing services. A publisher application creates and sends messages to a topic. Deleting a topic can interrupt message flow in the Pub/Sub pipeline. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Log Auditing], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<mfa-disabled-for-google-workspace-organization, MFA Disabled for Google Workspace Organization>> |Detects when multi-factor authentication (MFA) is disabled for a Google Workspace organization. An adversary may attempt to modify a password policy in order to weaken an organization’s security controls. |[Elastic] [Cloud] [Google Workspace] [Continuous Monitoring] [SecOps] [Identity and Access] [Persistence]  |7.11.0 |101 <<mfa-disabled-for-google-workspace-organization-history, Version history>>
+|<<gcp-service-account-creation, GCP Service Account Creation>> |Identifies when a new service account is created in Google Cloud Platform (GCP). A service account is a special type of account used by an application or a virtual machine (VM) instance, not a person. Applications use service accounts to make authorized API calls, authorized as either the service account itself, or as G Suite or Cloud Identity users through domain-wide delegation. If service accounts are not tracked and managed properly, they can present a security risk. An adversary may create a new service account to use during their operations in order to avoid using a standard user account and attempt to evade detection. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Identity and Access Audit], [Tactic: Persistence] |8.3.0 |104
 
-|<<ms-office-macro-security-registry-modifications, MS Office Macro Security Registry Modifications>> |Microsoft Office Products offer options for users and developers to control the security settings for running and using Macros. Adversaries may abuse these security settings to modify the default behavior of the Office Application to trust future macros and/or disable security warnings, which could increase their chances of establishing persistence. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |8.1.0 |102 <<ms-office-macro-security-registry-modifications-history, Version history>>
+|<<gcp-service-account-deletion, GCP Service Account Deletion>> |Identifies when a service account is deleted in Google Cloud Platform (GCP). A service account is a special type of account used by an application or a virtual machine (VM) instance, not a person. Applications use service accounts to make authorized API calls, authorized as either the service account itself, or as G Suite or Cloud Identity users through domain-wide delegation. An adversary may delete a service account in order to disrupt their target's business operations. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Identity and Access Audit], [Tactic: Impact] |8.3.0 |104
 
-|<<macos-installer-package-spawns-network-event, MacOS Installer Package Spawns Network Event>> |Detects the execution of a MacOS installer package with an abnormal child process (e.g bash) followed immediately by a network connection via a suspicious process (e.g curl). Threat actors will build and distribute malicious MacOS installer packages, which have a .pkg extension, many times imitating valid software in order to persuade and infect their victims often using the package files (e.g pre/post install scripts etc.) to download additional tools or malicious software. If this rule fires it should indicate the installation of a malicious or suspicious package. |[Elastic] [Host] [macOS] [Threat Detection] [Execution] [Command and Control]  |7.12.0 |100 <<macos-installer-package-spawns-network-event-history, Version history>>
+|<<gcp-service-account-disabled, GCP Service Account Disabled>> |Identifies when a service account is disabled in Google Cloud Platform (GCP). A service account is a special type of account used by an application or a virtual machine (VM) instance, not a person. Applications use service accounts to make authorized API calls, authorized as either the service account itself, or as G Suite or Cloud Identity users through domain-wide delegation. An adversary may disable a service account in order to disrupt to disrupt their target's business operations. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Identity and Access Audit], [Tactic: Impact] |8.3.0 |104
 
-|<<malware-detected-elastic-endgame, Malware - Detected - Elastic Endgame>> |Elastic Endgame detected Malware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame]  |7.6.0 |100 <<malware-detected-elastic-endgame-history, Version history>>
+|<<gcp-service-account-key-creation, GCP Service Account Key Creation>> |Identifies when a new key is created for a service account in Google Cloud Platform (GCP). A service account is a special type of account used by an application or a virtual machine (VM) instance, not a person. Applications use service accounts to make authorized API calls, authorized as either the service account itself, or as G Suite or Cloud Identity users through domain-wide delegation. If private keys are not tracked and managed properly, they can present a security risk. An adversary may create a new key for a service account in order to attempt to abuse the permissions assigned to that account and evade detection. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Identity and Access Audit], [Tactic: Persistence] |8.3.0 |104
 
-|<<malware-prevented-elastic-endgame, Malware - Prevented - Elastic Endgame>> |Elastic Endgame prevented Malware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame]  |7.6.0 |100 <<malware-prevented-elastic-endgame-history, Version history>>
+|<<gcp-storage-bucket-configuration-modification, GCP Storage Bucket Configuration Modification>> |Identifies when the configuration is modified for a storage bucket in Google Cloud Platform (GCP). An adversary may modify the configuration of a storage bucket in order to weaken the security controls of their target's environment. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Identity and Access Audit], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<masquerading-space-after-filename, Masquerading Space After Filename>> |This rules identifies a process created from an executable with a space appended to the end of the filename. This may indicate an attempt to masquerade a malicious file as benign to gain user execution. When a space is added to the end of certain files, the OS will execute the file according to it's true filetype instead of it's extension. Adversaries can hide a program's true filetype by changing the extension of the file. They can then add a space to the end of the name so that the OS automatically executes the file when it's double-clicked. |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Defense Evasion]  |8.6.0 |1
+|<<gcp-storage-bucket-deletion, GCP Storage Bucket Deletion>> |Identifies when a Google Cloud Platform (GCP) storage bucket is deleted. An adversary may delete a storage bucket in order to disrupt their target's business operations. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Tactic: Impact] |8.3.0 |104
 
-|<<microsoft-365-exchange-anti-phish-policy-deletion, Microsoft 365 Exchange Anti-Phish Policy Deletion>> |Identifies the deletion of an anti-phishing policy in Microsoft 365. By default, Microsoft 365 includes built-in features that help protect users from phishing attacks. Anti-phishing polices increase this protection by refining settings to better detect and prevent attacks. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.11.0 |101 <<microsoft-365-exchange-anti-phish-policy-deletion-history, Version history>>
+|<<gcp-storage-bucket-permissions-modification, GCP Storage Bucket Permissions Modification>> |Identifies when the Identity and Access Management (IAM) permissions are modified for a Google Cloud Platform (GCP) storage bucket. An adversary may modify the permissions on a storage bucket to weaken their target's security controls or an administrator may inadvertently modify the permissions, which could lead to data exposure or loss. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Identity and Access Audit], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<microsoft-365-exchange-anti-phish-rule-modification, Microsoft 365 Exchange Anti-Phish Rule Modification>> |Identifies the modification of an anti-phishing rule in Microsoft 365. By default, Microsoft 365 includes built-in features that help protect users from phishing attacks. Anti-phishing rules increase this protection by refining settings to better detect and prevent attacks. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.11.0 |101 <<microsoft-365-exchange-anti-phish-rule-modification-history, Version history>>
+|<<gcp-virtual-private-cloud-network-deletion, GCP Virtual Private Cloud Network Deletion>> |Identifies when a Virtual Private Cloud (VPC) network is deleted in Google Cloud Platform (GCP). A VPC network is a virtual version of a physical network within a GCP project. Each VPC network has its own subnets, routes, and firewall, as well as other elements. An adversary may delete a VPC network in order to disrupt their target's network and business operations. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<microsoft-365-exchange-dkim-signing-configuration-disabled, Microsoft 365 Exchange DKIM Signing Configuration Disabled>> |Identifies when a DomainKeys Identified Mail (DKIM) signing configuration is disabled in Microsoft 365. With DKIM in Microsoft 365, messages that are sent from Exchange Online will be cryptographically signed. This will allow the receiving email system to validate that the messages were generated by a server that the organization authorized and were not spoofed. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Data Protection] [Persistence]  |7.11.0 |101 <<microsoft-365-exchange-dkim-signing-configuration-disabled-history, Version history>>
+|<<gcp-virtual-private-cloud-route-creation, GCP Virtual Private Cloud Route Creation>> |Identifies when a virtual private cloud (VPC) route is created in Google Cloud Platform (GCP). Google Cloud routes define the paths that network traffic takes from a virtual machine (VM) instance to other destinations. These destinations can be inside a Google VPC network or outside it. An adversary may create a route in order to impact the flow of network traffic in their target's cloud environment. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<microsoft-365-exchange-dlp-policy-removed, Microsoft 365 Exchange DLP Policy Removed>> |Identifies when a Data Loss Prevention (DLP) policy is removed in Microsoft 365. An adversary may remove a DLP policy to evade existing DLP monitoring. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.11.0 |101 <<microsoft-365-exchange-dlp-policy-removed-history, Version history>>
+|<<gcp-virtual-private-cloud-route-deletion, GCP Virtual Private Cloud Route Deletion>> |Identifies when a Virtual Private Cloud (VPC) route is deleted in Google Cloud Platform (GCP). Google Cloud routes define the paths that network traffic takes from a virtual machine (VM) instance to other destinations. These destinations can be inside a Google VPC network or outside it. An adversary may delete a route in order to impact the flow of network traffic in their target's cloud environment. |[Domain: Cloud], [Data Source: GCP], [Data Source: Google Cloud Platform], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.3.0 |104
 
-|<<microsoft-365-exchange-malware-filter-policy-deletion, Microsoft 365 Exchange Malware Filter Policy Deletion>> |Identifies when a malware filter policy has been deleted in Microsoft 365. A malware filter policy is used to alert administrators that an internal user sent a message that contained malware. This may indicate an account or machine compromise that would need to be investigated. Deletion of a malware filter policy may be done to evade detection. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.11.0 |101 <<microsoft-365-exchange-malware-filter-policy-deletion-history, Version history>>
+|<<github-app-deleted, GitHub App Deleted>> |Detects the deletion of a GitHub app either from a repo or an organization. |[Domain: Cloud], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Github] |8.3.0 |1
 
-|<<microsoft-365-exchange-malware-filter-rule-modification, Microsoft 365 Exchange Malware Filter Rule Modification>> |Identifies when a malware filter rule has been deleted or disabled in Microsoft 365. An adversary or insider threat may want to modify a malware filter rule to evade detection. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.11.0 |101 <<microsoft-365-exchange-malware-filter-rule-modification-history, Version history>>
+|<<github-owner-role-granted-to-user, GitHub Owner Role Granted To User>> |This rule detects when a member is granted the organization owner role of a GitHub organization. This role provides admin level privileges. Any new owner role should be investigated to determine its validity. Unauthorized owner roles could indicate compromise within your organization and provide unlimited access to data and settings. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Persistence], [Data Source: Github] |8.3.0 |3
 
-|<<microsoft-365-exchange-management-group-role-assignment, Microsoft 365 Exchange Management Group Role Assignment>> |Identifies when a new role is assigned to a management group in Microsoft 365. An adversary may attempt to add a role in order to maintain persistence in an environment. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.11.0 |101 <<microsoft-365-exchange-management-group-role-assignment-history, Version history>>
+|<<github-pat-access-revoked, GitHub PAT Access Revoked>> |Access to private GitHub organization resources was revoked for a PAT. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Impact], [Rule Type: BBR], [Data Source: Github] |8.3.0 |1
 
-|<<microsoft-365-exchange-safe-attachment-rule-disabled, Microsoft 365 Exchange Safe Attachment Rule Disabled>> |Identifies when a safe attachment rule is disabled in Microsoft 365. Safe attachment rules can extend malware protections to include routing all messages and attachments without a known malware signature to a special hypervisor environment. An adversary or insider threat may disable a safe attachment rule to exfiltrate data or evade defenses. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.11.0 |101 <<microsoft-365-exchange-safe-attachment-rule-disabled-history, Version history>>
+|<<github-protected-branch-settings-changed, GitHub Protected Branch Settings Changed>> |This rule detects setting modifications for protected branches of a GitHub repository. Branch protection rules can be used to enforce certain workflows or requirements before a contributor can push changes to a branch in your repository. Changes to these protected branch settings should be investigated and verified as legitimate activity. Unauthorized changes could be used to lower your organization's security posture and leave you exposed for future attacks. |[Domain: Cloud], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Github] |8.3.0 |2
 
-|<<microsoft-365-exchange-safe-link-policy-disabled, Microsoft 365 Exchange Safe Link Policy Disabled>> |Identifies when a Safe Link policy is disabled in Microsoft 365. Safe Link policies for Office applications extend phishing protection to documents that contain hyperlinks, even after they have been delivered to a user. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.11.0 |101 <<microsoft-365-exchange-safe-link-policy-disabled-history, Version history>>
+|<<github-repo-created, GitHub Repo Created>> |A new GitHub repository was created. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Execution], [Rule Type: BBR], [Data Source: Github] |8.3.0 |1
 
-|<<microsoft-365-exchange-transport-rule-creation, Microsoft 365 Exchange Transport Rule Creation>> |Identifies a transport rule creation in Microsoft 365. As a best practice, Exchange Online mail transport rules should not be set to forward email to domains outside of your organization. An adversary may create transport rules to exfiltrate data. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.11.0 |101 <<microsoft-365-exchange-transport-rule-creation-history, Version history>>
+|<<github-repository-deleted, GitHub Repository Deleted>> |This rule detects when a GitHub repository is deleted within your organization. Repositories are a critical component used within an organization to manage work, collaborate with others and release products to the public. Any delete action against a repository should be investigated to determine it's validity. Unauthorized deletion of organization repositories could cause irreversible loss of intellectual property and indicate compromise within your organization. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Impact], [Data Source: Github] |8.3.0 |2
 
-|<<microsoft-365-exchange-transport-rule-modification, Microsoft 365 Exchange Transport Rule Modification>> |Identifies when a transport rule has been disabled or deleted in Microsoft 365. Mail flow rules (also known as transport rules) are used to identify and take action on messages that flow through your organization. An adversary or insider threat may modify a transport rule to exfiltrate data or evade defenses. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.11.0 |101 <<microsoft-365-exchange-transport-rule-modification-history, Version history>>
+|<<github-ueba-multiple-alerts-from-a-github-account, GitHub UEBA - Multiple Alerts from a GitHub Account>> |This rule is part of the "GitHub UEBA - Unusual Activity from Account Pack", and leverages alert data to determine when multiple alerts are executed by the same user in a timespan of one hour. Analysts can use this to prioritize triage and response, as these alerts are a higher indicator of compromised user accounts or PATs. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Execution], [Rule Type: Higher-Order Rule], [Data Source: Github] |8.3.0 |1
 
-|<<microsoft-365-global-administrator-role-assigned, Microsoft 365 Global Administrator Role Assigned>> |In Azure Active Directory (Azure AD), permissions to manage resources are assigned using roles. The Global Administrator is a role that enables users to have access to all administrative features in Azure AD and services that use Azure AD identities like the Microsoft 365 Defender portal, the Microsoft 365 compliance center, Exchange, SharePoint Online, and Skype for Business Online. Attackers can add users as Global Administrators to maintain access and manage all subscriptions and their settings and resources. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Identity and Access]  |8.1.0 |101 <<microsoft-365-global-administrator-role-assigned-history, Version history>>
+|<<github-user-blocked-from-organization, GitHub User Blocked From Organization>> |A GitHub user was blocked from access to an organization. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Impact], [Rule Type: BBR], [Data Source: Github] |8.3.0 |1
 
-|<<microsoft-365-inbox-forwarding-rule-created, Microsoft 365 Inbox Forwarding Rule Created>> |Identifies when a new Inbox forwarding rule is created in Microsoft 365. Inbox rules process messages in the Inbox based on conditions and take actions. In this case, the rules will forward the emails to a defined address. Attackers can abuse Inbox Rules to intercept and exfiltrate email data without making organization-wide configuration changes or having the corresponding privileges. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.13.0 |101 <<microsoft-365-inbox-forwarding-rule-created-history, Version history>>
+|<<google-drive-ownership-transferred-via-google-workspace, Google Drive Ownership Transferred via Google Workspace>> |Drive and Docs is a Google Workspace service that allows users to leverage Google Drive and Google Docs. Access to files is based on inherited permissions from the child organizational unit the user belongs to which is scoped by administrators. Typically if a user is removed, their files can be transferred to another user by the administrator. This service can also be abused by adversaries to transfer files to an adversary account for potential exfiltration. |[Domain: Cloud], [Data Source: Google Workspace], [Tactic: Collection], [Resources: Investigation Guide] |8.4.0 |106
 
-|<<microsoft-365-potential-ransomware-activity, Microsoft 365 Potential ransomware activity>> |Identifies when Microsoft Cloud App Security reports that a user has uploaded files to the cloud that might be infected with ransomware. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.16.0 |101 <<microsoft-365-potential-ransomware-activity-history, Version history>>
+|<<google-workspace-2sv-policy-disabled, Google Workspace 2SV Policy Disabled>> |Google Workspace admins may setup 2-step verification (2SV) to add an extra layer of security to user accounts by asking users to verify their identity when they use login credentials. Admins have the ability to enforce 2SV from the admin console as well as the methods acceptable for verification and enrollment period. 2SV requires enablement on admin accounts prior to it being enabled for users within organization units. Adversaries may disable 2SV to lower the security requirements to access a valid account. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Configuration Audit], [Tactic: Persistence], [Resources: Investigation Guide] |8.4.0 |106
 
-|<<microsoft-365-teams-custom-application-interaction-allowed, Microsoft 365 Teams Custom Application Interaction Allowed>> |Identifies when custom applications are allowed in Microsoft Teams. If an organization requires applications other than those available in the Teams app store, custom applications can be developed as packages and uploaded. An adversary may abuse this behavior to establish persistence in an environment. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit] [Persistence]  |7.11.0 |101 <<microsoft-365-teams-custom-application-interaction-allowed-history, Version history>>
+|<<google-workspace-api-access-granted-via-domain-wide-delegation-of-authority, Google Workspace API Access Granted via Domain-Wide Delegation of Authority>> |Detects when a domain-wide delegation of authority is granted to a service account. Domain-wide delegation can be configured to grant third-party and internal applications to access the data of Google Workspace users. An adversary may configure domain-wide delegation to maintain access to their target’s data. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Persistence] |8.4.0 |205
 
-|<<microsoft-365-teams-external-access-enabled, Microsoft 365 Teams External Access Enabled>> |Identifies when external access is enabled in Microsoft Teams. External access lets Teams and Skype for Business users communicate with other users that are outside their organization. An adversary may enable external access or add an allowed domain to exfiltrate data or maintain persistence in an environment. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.11.0 |101 <<microsoft-365-teams-external-access-enabled-history, Version history>>
+|<<google-workspace-admin-role-assigned-to-a-user, Google Workspace Admin Role Assigned to a User>> |Assigning the administrative role to a user will grant them access to the Google Admin console and grant them administrator privileges which allow them to access and manage various resources and applications. An adversary may create a new administrator account for persistence or apply the admin role to an existing user to carry out further intrusion efforts. Users with super-admin privileges can bypass single-sign on if enabled in Google Workspace. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Identity and Access Audit], [Tactic: Persistence], [Resources: Investigation Guide] |8.4.0 |206
 
-|<<microsoft-365-teams-guest-access-enabled, Microsoft 365 Teams Guest Access Enabled>> |Identifies when guest access is enabled in Microsoft Teams. Guest access in Teams allows people outside the organization to access teams and channels. An adversary may enable guest access to maintain persistence in an environment. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.11.0 |101 <<microsoft-365-teams-guest-access-enabled-history, Version history>>
+|<<google-workspace-admin-role-deletion, Google Workspace Admin Role Deletion>> |Detects when a custom admin role is deleted. An adversary may delete a custom admin role in order to impact the permissions or capabilities of system administrators. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Identity and Access Audit], [Tactic: Impact], [Resources: Investigation Guide] |8.4.0 |205
 
-|<<microsoft-365-unusual-volume-of-file-deletion, Microsoft 365 Unusual Volume of File Deletion>> |Identifies that a user has deleted an unusually large volume of files as reported by Microsoft Cloud App Security. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.16.0 |101 <<microsoft-365-unusual-volume-of-file-deletion-history, Version history>>
+|<<google-workspace-bitlocker-setting-disabled, Google Workspace Bitlocker Setting Disabled>> |Google Workspace administrators whom manage Windows devices and have Windows device management enabled may also enable BitLocker drive encryption to mitigate unauthorized data access on lost or stolen computers. Adversaries with valid account access may disable BitLocker to access sensitive data on an endpoint added to Google Workspace device management. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Configuration Audit], [Tactic: Defense Evasion], [Resources: Investigation Guide] |8.4.0 |106
 
-|<<microsoft-365-user-restricted-from-sending-email, Microsoft 365 User Restricted from Sending Email>> |Identifies when a user has been restricted from sending email due to exceeding sending limits of the service policies per the Security Compliance Center. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.16.0 |101 <<microsoft-365-user-restricted-from-sending-email-history, Version history>>
+|<<google-workspace-custom-admin-role-created, Google Workspace Custom Admin Role Created>> |Detects when a custom admin role is created in Google Workspace. An adversary may create a custom admin role in order to elevate the permissions of other user accounts and persist in their target’s environment. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Persistence] |8.4.0 |205
 
-|<<microsoft-build-engine-started-an-unusual-process, Microsoft Build Engine Started an Unusual Process>> |An instance of MSBuild, the Microsoft Build Engine, started a PowerShell script or the Visual C# Command Line Compiler. This technique is sometimes used to deploy a malicious payload using the Build Engine. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.7.0 |102 <<microsoft-build-engine-started-an-unusual-process-history, Version history>>
+|<<google-workspace-custom-gmail-route-created-or-modified, Google Workspace Custom Gmail Route Created or Modified>> |Detects when a custom Gmail route is added or modified in Google Workspace. Adversaries can add a custom e-mail route for outbound mail to route these e-mails to their own inbox of choice for data gathering. This allows adversaries to capture sensitive information from e-mail and potential attachments, such as invoices or payment documents. By default, all email from current Google Workspace users with accounts are routed through a domain's mail server for inbound and outbound mail. |[Domain: Cloud], [Data Source: Google Workspace], [Tactic: Collection], [Resources: Investigation Guide] |8.4.0 |106
 
-|<<microsoft-build-engine-started-by-a-script-process, Microsoft Build Engine Started by a Script Process>> |An instance of MSBuild, the Microsoft Build Engine, was started by a script or the Windows command interpreter. This behavior is unusual and is sometimes used by malicious payloads. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.7.0 |101 <<microsoft-build-engine-started-by-a-script-process-history, Version history>>
+|<<google-workspace-drive-encryption-key-s-accessed-from-anonymous-user, Google Workspace Drive Encryption Key(s) Accessed from Anonymous User>> |Detects when an external (anonymous) user has viewed, copied or downloaded an encryption key file from a Google Workspace drive. Adversaries may gain access to encryption keys stored in private drives from rogue access links that do not have an expiration. Access to encryption keys may allow adversaries to access sensitive data or authenticate on behalf of users. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Configuration Audit], [Tactic: Credential Access] |8.4.0 |3
 
-|<<microsoft-build-engine-started-by-a-system-process, Microsoft Build Engine Started by a System Process>> |An instance of MSBuild, the Microsoft Build Engine, was started by Explorer or the WMI (Windows Management Instrumentation) subsystem. This behavior is unusual and is sometimes used by malicious payloads. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.7.0 |102 <<microsoft-build-engine-started-by-a-system-process-history, Version history>>
+|<<google-workspace-mfa-enforcement-disabled, Google Workspace MFA Enforcement Disabled>> |Detects when multi-factor authentication (MFA) enforcement is disabled for Google Workspace users. An adversary may disable MFA enforcement in order to weaken an organization’s security controls. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Configuration Audit], [Tactic: Impact], [Resources: Investigation Guide] |8.4.0 |207
 
-|<<microsoft-build-engine-started-by-an-office-application, Microsoft Build Engine Started by an Office Application>> |An instance of MSBuild, the Microsoft Build Engine, was started by Excel or Word. This is unusual behavior for the Build Engine and could have been caused by an Excel or Word document executing a malicious script payload. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.7.0 |102 <<microsoft-build-engine-started-by-an-office-application-history, Version history>>
+|<<google-workspace-object-copied-from-external-drive-and-access-granted-to-custom-application, Google Workspace Object Copied from External Drive and Access Granted to Custom Application>> |Detects when a user copies a Google spreadsheet, form, document or script from an external drive. Sequence logic has been added to also detect when a user grants a custom Google application permission via OAuth shortly after. An adversary may send a phishing email to the victim with a Drive object link where "copy" is included in the URI, thus copying the object to the victim's drive. If a container-bound script exists within the object, execution will require permission access via OAuth in which the user has to accept. |[Domain: Cloud], [Data Source: Google Workspace], [Tactic: Initial Access], [Resources: Investigation Guide] |8.4.0 |4
 
-|<<microsoft-build-engine-using-an-alternate-name, Microsoft Build Engine Using an Alternate Name>> |An instance of MSBuild, the Microsoft Build Engine, was started after being renamed. This is uncommon behavior and may indicate an attempt to run unnoticed or undetected. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.7.0 |102 <<microsoft-build-engine-using-an-alternate-name-history, Version history>>
+|<<google-workspace-password-policy-modified, Google Workspace Password Policy Modified>> |Detects when a Google Workspace password policy is modified. An adversary may attempt to modify a password policy in order to weaken an organization’s security controls. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Identity and Access Audit], [Tactic: Persistence], [Resources: Investigation Guide] |8.4.0 |205
 
-|<<microsoft-exchange-server-um-spawning-suspicious-processes, Microsoft Exchange Server UM Spawning Suspicious Processes>> |Identifies suspicious processes being spawned by the Microsoft Exchange Server Unified Messaging (UM) service. This activity has been observed exploiting CVE-2021-26857. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access]  |7.12.0 |100 <<microsoft-exchange-server-um-spawning-suspicious-processes-history, Version history>>
+|<<google-workspace-restrictions-for-google-marketplace-modified-to-allow-any-app, Google Workspace Restrictions for Google Marketplace Modified to Allow Any App>> |Detects when the Google Marketplace restrictions are changed to allow any application for users in Google Workspace. Malicious APKs created by adversaries may be uploaded to the Google marketplace but not installed on devices managed within Google Workspace. Administrators should set restrictions to not allow any application from the marketplace for security reasons. Adversaries may enable any app to be installed and executed on mobile devices within a Google Workspace environment prior to distributing the malicious APK to the end user. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Configuration Audit], [Tactic: Defense Evasion], [Resources: Investigation Guide] |8.4.0 |106
 
-|<<microsoft-exchange-server-um-writing-suspicious-files, Microsoft Exchange Server UM Writing Suspicious Files>> |Identifies suspicious files being written by the Microsoft Exchange Server Unified Messaging (UM) service. This activity has been observed exploiting CVE-2021-26858. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access]  |7.12.0 |100 <<microsoft-exchange-server-um-writing-suspicious-files-history, Version history>>
+|<<google-workspace-role-modified, Google Workspace Role Modified>> |Detects when a custom admin role or its permissions are modified. An adversary may modify a custom admin role in order to elevate the permissions of other user accounts and persist in their target’s environment. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Persistence] |8.4.0 |205
 
-|<<microsoft-exchange-worker-spawning-suspicious-processes, Microsoft Exchange Worker Spawning Suspicious Processes>> |Identifies suspicious processes being spawned by the Microsoft Exchange Server worker process (w3wp). This activity may indicate exploitation activity or access to an existing web shell backdoor. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access]  |7.12.0 |100 <<microsoft-exchange-worker-spawning-suspicious-processes-history, Version history>>
+|<<google-workspace-suspended-user-account-renewed, Google Workspace Suspended User Account Renewed>> |Detects when a previously suspended user's account is renewed in Google Workspace. An adversary may renew a suspended user account to maintain access to the Google Workspace organization with a valid account. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Identity and Access Audit], [Tactic: Initial Access] |8.4.0 |2
 
-|<<microsoft-iis-connection-strings-decryption, Microsoft IIS Connection Strings Decryption>> |Identifies use of aspnet_regiis to decrypt Microsoft IIS connection strings. An attacker with Microsoft IIS web server access via a webshell or alike can decrypt and dump any hardcoded connection strings, such as the MSSQL service account password using aspnet_regiis command. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Elastic Endgame]  |7.10.0 |102 <<microsoft-iis-connection-strings-decryption-history, Version history>>
+|<<google-workspace-user-organizational-unit-changed, Google Workspace User Organizational Unit Changed>> |Users in Google Workspace are typically assigned a specific organizational unit that grants them permissions to certain services and roles that are inherited from this organizational unit. Adversaries may compromise a valid account and change which organizational account the user belongs to which then could allow them to inherit permissions to applications and resources inaccessible prior to. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Configuration Audit], [Tactic: Persistence], [Resources: Investigation Guide] |8.4.0 |106
 
-|<<microsoft-iis-service-account-password-dumped, Microsoft IIS Service Account Password Dumped>> |Identifies the Internet Information Services (IIS) command-line tool, AppCmd, being used to list passwords. An attacker with IIS web server access via a web shell can decrypt and dump the IIS AppPool service account password using AppCmd. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Elastic Endgame]  |7.10.0 |102 <<microsoft-iis-service-account-password-dumped-history, Version history>>
+|<<group-policy-abuse-for-privilege-addition, Group Policy Abuse for Privilege Addition>> |Detects the first occurrence of a modification to Group Policy Object Attributes to add privileges to user accounts or use them to add users as local admins. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Active Directory], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring] |8.3.0 |109
 
-|<<microsoft-windows-defender-tampering, Microsoft Windows Defender Tampering>> |Identifies when one or more features on Microsoft Defender are disabled. Adversaries may disable or tamper with Microsoft Defender features to evade detection and conceal malicious behavior. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide]  |8.0.0 |102 <<microsoft-windows-defender-tampering-history, Version history>>
+|<<group-policy-discovery-via-microsoft-gpresult-utility, Group Policy Discovery via Microsoft GPResult Utility>> |Detects the usage of gpresult.exe to query group policy objects. Attackers may query group policy objects during the reconnaissance phase after compromising a system to gain a better understanding of the active directory environment and possible methods to escalate privileges or move laterally. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |8
 
-|<<mimikatz-memssp-log-file-detected, Mimikatz Memssp Log File Detected>> |Identifies the password log file from the default Mimikatz memssp module. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide] [Elastic Endgame]  |7.10.0 |102 <<mimikatz-memssp-log-file-detected-history, Version history>>
+|<<halfbaked-command-and-control-beacon, Halfbaked Command and Control Beacon>> |Halfbaked is a malware family used to establish persistence in a contested network. This rule detects a network activity algorithm leveraged by Halfbaked implant beacons for command and control. |[Use Case: Threat Detection], [Tactic: Command and Control], [Domain: Endpoint] |8.3.0 |104
 
-|<<modification-of-amsienable-registry-key, Modification of AmsiEnable Registry Key>> |Identifies modifications of the AmsiEnable registry key to 0, which disables the Antimalware Scan Interface (AMSI). An adversary can modify this key to disable AMSI protections. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.14.0 |102 <<modification-of-amsienable-registry-key-history, Version history>>
+|<<hidden-files-and-directories-via-hidden-flag, Hidden Files and Directories via Hidden Flag>> |Identify activity related where adversaries can add the 'hidden' flag to files to hide them from the user in an attempt to evade detection. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |2
 
-|<<modification-of-boot-configuration, Modification of Boot Configuration>> |Identifies use of bcdedit.exe to delete boot configuration data. This tactic is sometimes used as by malware or an attacker as a destructive technique. |[Elastic] [Host] [Windows] [Threat Detection] [Impact] [Investigation Guide]  |7.7.0 |102 <<modification-of-boot-configuration-history, Version history>>
+|<<high-mean-of-process-arguments-in-an-rdp-session, High Mean of Process Arguments in an RDP Session>> |A machine learning job has detected unusually high number of process arguments in an RDP session. Executing sophisticated attacks such as lateral movement can involve the use of complex commands, obfuscation mechanisms, redirection and piping, which in turn increases the number of arguments in a command. |[Use Case: Lateral Movement Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Lateral Movement] |8.9.0 |3
 
-|<<modification-of-dynamic-linker-preload-shared-object, Modification of Dynamic Linker Preload Shared Object>> |Identifies modification of the dynamic linker preload shared object (ld.so.preload). Adversaries may execute malicious payloads by hijacking the dynamic linker used to load libraries. |[Elastic] [Host] [Linux] [Threat Detection] [Privilege Escalation]  |7.12.0 |100 <<modification-of-dynamic-linker-preload-shared-object-history, Version history>>
+|<<high-mean-of-rdp-session-duration, High Mean of RDP Session Duration>> |A machine learning job has detected unusually high mean of RDP session duration. Long RDP sessions can be used to evade detection mechanisms via session persistence, and might be used to perform tasks such as lateral movement, that might require uninterrupted access to a compromised machine. |[Use Case: Lateral Movement Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Lateral Movement] |8.9.0 |3
 
-|<<modification-of-environment-variable-via-launchctl, Modification of Environment Variable via Launchctl>> |Identifies modifications to an environment variable using the built-in launchctl command. Adversaries may execute their own malicious payloads by hijacking certain environment variables to load arbitrary libraries or bypass certain restrictions. |[Elastic] [Host] [macOS] [Threat Detection] [Defense Evasion]  |7.12.0 |100 <<modification-of-environment-variable-via-launchctl-history, Version history>>
+|<<high-number-of-cloned-github-repos-from-pat, High Number of Cloned GitHub Repos From PAT>> |Detects a high number of unique private repo clone events originating from a single personal access token within a short time period. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Execution], [Data Source: Github] |8.8.0 |1
 
-|<<modification-of-openssh-binaries, Modification of OpenSSH Binaries>> |Adversaries may modify SSH related binaries for persistence or credential access by patching sensitive functions to enable unauthorized access or by logging SSH credentials for exfiltration. |[Elastic] [Host] [Linux] [Threat Detection] [Credential Access] [Persistence]  |7.12.0 |100 <<modification-of-openssh-binaries-history, Version history>>
+|<<high-number-of-okta-user-password-reset-or-unlock-attempts, High Number of Okta User Password Reset or Unlock Attempts>> |Identifies a high number of Okta user password reset or account unlock attempts. An adversary may attempt to obtain unauthorized access to Okta user accounts using these methods and attempt to blend in with normal activity in their target's environment and evade detection. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Defense Evasion] |8.10.0 |208
 
-|<<modification-of-safari-settings-via-defaults-command, Modification of Safari Settings via Defaults Command>> |Identifies changes to the Safari configuration using the built-in defaults command. Adversaries may attempt to enable or disable certain Safari settings, such as enabling JavaScript from Apple Events to ease in the hijacking of the users browser. |[Elastic] [Host] [macOS] [Threat Detection] [Defense Evasion]  |7.12.0 |100 <<modification-of-safari-settings-via-defaults-command-history, Version history>>
+|<<high-number-of-process-terminations, High Number of Process Terminations>> |This rule identifies a high number (10) of process terminations via pkill from the same host within a short time period. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Impact], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |112
 
-|<<modification-of-standard-authentication-module-or-configuration, Modification of Standard Authentication Module or Configuration>> |Adversaries may modify the standard authentication module for persistence via patching the normal authorization process or modifying the login configuration to allow unauthorized access or elevate privileges. |[Elastic] [Host] [macOS] [Linux] [Threat Detection] [Credential Access] [Persistence]  |7.12.0 |100 <<modification-of-standard-authentication-module-or-configuration-history, Version history>>
+|<<high-number-of-process-and-or-service-terminations, High Number of Process and/or Service Terminations>> |This rule identifies a high number (10) of process terminations (stop, delete, or suspend) from the same host within a short time period. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Impact], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<modification-of-wdigest-security-provider, Modification of WDigest Security Provider>> |Identifies attempts to modify the WDigest security provider in the registry to force the user's password to be stored in clear text in memory. This behavior can be indicative of an adversary attempting to weaken the security configuration of an endpoint. Once the UseLogonCredential value is modified, the adversary may attempt to dump clear text passwords from memory. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide] [Elastic Endgame]  |7.12.0 |102 <<modification-of-wdigest-security-provider-history, Version history>>
+|<<high-variance-in-rdp-session-duration, High Variance in RDP Session Duration>> |A machine learning job has detected unusually high variance of RDP session duration. Long RDP sessions can be used to evade detection mechanisms via session persistence, and might be used to perform tasks such as lateral movement, that might require uninterrupted access to a compromised machine. |[Use Case: Lateral Movement Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Lateral Movement] |8.9.0 |3
 
-|<<modification-of-the-mspkiaccountcredentials, Modification of the msPKIAccountCredentials>> |Identify the modification of the msPKIAccountCredentials attribute in an Active Directory User Object. Attackers can abuse the credentials roaming feature to overwrite an arbitrary file for privilege escalation. ms-PKI-AccountCredentials contains binary large objects (BLOBs) of encrypted credential objects from the credential manager store, private keys, certificates, and certificate requests. |[Elastic] [Host] [Windows] [Threat Detection] [Active Directory] [Privilege Escalation]  |8.6.0 |1
+|<<host-files-system-changes-via-windows-subsystem-for-linux, Host Files System Changes via Windows Subsystem for Linux>> |Detects files creation and modification on the host system from the the Windows Subsystem for Linux. Adversaries may enable and use WSL for Linux to avoid detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |7
 
-|<<modification-or-removal-of-an-okta-application-sign-on-policy, Modification or Removal of an Okta Application Sign-On Policy>> |Detects attempts to modify or delete a sign on policy for an Okta application. An adversary may attempt to modify or delete the sign on policy for an Okta application in order to remove or weaken an organization's security controls. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access] [Persistence]  |7.9.0 |102 <<modification-or-removal-of-an-okta-application-sign-on-policy-history, Version history>>
+|<<hosts-file-modified, Hosts File Modified>> |The hosts file on endpoints is used to control manual IP address to hostname resolutions. The hosts file is the first point of lookup for DNS hostname resolution so if adversaries can modify the endpoint hosts file, they can route traffic to malicious infrastructure. This rule detects modifications to the hosts file on Microsoft Windows, Linux (Ubuntu or RHEL) and macOS systems. |[Domain: Endpoint], [OS: Linux], [OS: Windows], [OS: macOS], [Use Case: Threat Detection], [Tactic: Impact], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<mounting-hidden-or-webdav-remote-shares, Mounting Hidden or WebDav Remote Shares>> |Identifies the use of net.exe to mount a WebDav or hidden remote share. This may indicate lateral movement or preparation for data exfiltration. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access] [Lateral Movement]  |7.11.0 |102 <<mounting-hidden-or-webdav-remote-shares-history, Version history>>
+|<<hping-process-activity, Hping Process Activity>> |Hping ran on a Linux host. Hping is a FOSS command-line packet analyzer and has the ability to construct network packets for a wide variety of network security testing applications, including scanning and firewall auditing. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |108
 
-|<<msbuild-making-network-connections, MsBuild Making Network Connections>> |Identifies MsBuild.exe making outbound network connections. This may indicate adversarial activity as MsBuild is often leveraged by adversaries to execute code and evade detection. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.6.0 |100 <<msbuild-making-network-connections-history, Version history>>
+|<<iis-http-logging-disabled, IIS HTTP Logging Disabled>> |Identifies when Internet Information Services (IIS) HTTP Logging is disabled on a server. An attacker with IIS server access via a webshell or other mechanism can disable HTTP Logging as an effective anti-forensics measure. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<mshta-making-network-connections, Mshta Making Network Connections>> |Identifies Mshta.exe making outbound network connections. This may indicate adversarial activity, as Mshta is often leveraged by adversaries to execute malicious scripts and evade detection. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.10.0 |101 <<mshta-making-network-connections-history, Version history>>
+|<<ipsec-nat-traversal-port-activity, IPSEC NAT Traversal Port Activity>> |This rule detects events that could be describing IPSEC NAT Traversal traffic. IPSEC is a VPN technology that allows one system to talk to another using encrypted tunnels. NAT Traversal enables these tunnels to communicate over the Internet where one of the sides is behind a NAT router gateway. This may be common on your network, but this technique is also used by threat actors to avoid detection. |[Tactic: Command and Control], [Domain: Endpoint], [Use Case: Threat Detection] |8.3.0 |104
 
-|<<multi-factor-authentication-disabled-for-an-azure-user, Multi-Factor Authentication Disabled for an Azure User>> |Identifies when multi-factor authentication (MFA) is disabled for an Azure user account. An adversary may disable MFA for a user account in order to weaken the authentication requirements for the account. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access] [Investigation Guide]  |7.10.0 |103 <<multi-factor-authentication-disabled-for-an-azure-user-history, Version history>>
+|<<image-file-execution-options-injection, Image File Execution Options Injection>> |The Debugger and SilentProcessExit registry keys can allow an adversary to intercept the execution of files, causing a different process to be executed. This functionality can be abused by an adversary to establish persistence. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
 
-|<<multiple-alerts-in-different-att-ck-tactics-on-a-single-host, Multiple Alerts in Different ATT&CK Tactics on a Single Host>> |This rule uses alert data to determine when multiple alerts in different phases of an attack involving the same host are triggered. Analysts can use this to prioritize triage and response, as these hosts are more likely to be compromised. |[Elastic] [Threat Detection] [Higher-Order Rules]  |8.6.0 |1
+|<<image-loaded-with-invalid-signature, Image Loaded with Invalid Signature>> |Identifies binaries that are loaded and with an invalid code signature. This may indicate an attempt to masquerade as a signed binary. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<multiple-logon-failure-followed-by-logon-success, Multiple Logon Failure Followed by Logon Success>> |Identifies multiple logon failures followed by a successful one from the same source address. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to accounts. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access]  |8.5.0 |1
+|<<imageload-via-windows-update-auto-update-client, ImageLoad via Windows Update Auto Update Client>> |Identifies abuse of the Windows Update Auto Update Client (wuauclt.exe) to load an arbitrary DLL. This behavior is used as a defense evasion technique to blend-in malicious activity with legitimate Windows software. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
 
-|<<multiple-logon-failure-from-the-same-source-address, Multiple Logon Failure from the same Source Address>> |Identifies multiple consecutive logon failures from the same source address and within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to accounts. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access]  |8.5.0 |1
+|<<inbound-connection-to-an-unsecure-elasticsearch-node, Inbound Connection to an Unsecure Elasticsearch Node>> |Identifies Elasticsearch nodes that do not have Transport Layer Security (TLS), and/or lack authentication, and are accepting inbound network connections over the default Elasticsearch port. |[Use Case: Threat Detection], [Tactic: Initial Access], [Domain: Endpoint] |8.3.0 |104
 
-|<<multiple-vault-web-credentials-read, Multiple Vault Web Credentials Read>> |Windows Credential Manager allows you to create, view, or delete saved credentials for signing into websites, connected applications, and networks. An adversary may abuse this to list or dump credentials stored in the Credential Manager for saved usernames and passwords. This may also be performed in preparation of lateral movement. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access]  |8.5.0 |2 <<multiple-vault-web-credentials-read-history, Version history>>
+|<<incoming-dcom-lateral-movement-via-mshta, Incoming DCOM Lateral Movement via MSHTA>> |Identifies the use of Distributed Component Object Model (DCOM) to execute commands from a remote host, which are launched via the HTA Application COM Object. This behavior may indicate an attacker abusing a DCOM application to move laterally while attempting to evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
 
-|<<my-first-alert, My First Alert>> |This rule helps you test and practice using alerts with Elastic Security as you get set up. It’s not a sign of threat activity. |[Elastic] [Example] [Guided Onboarding] [Network] [APM] [Windows] [Elastic Endgame]  |8.6.0 |1
+|<<incoming-dcom-lateral-movement-with-mmc, Incoming DCOM Lateral Movement with MMC>> |Identifies the use of Distributed Component Object Model (DCOM) to run commands from a remote host, which are launched via the MMC20 Application COM Object. This behavior may indicate an attacker abusing a DCOM application to move laterally. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<ntds-or-sam-database-file-copied, NTDS or SAM Database File Copied>> |Identifies a copy operation of the Active Directory Domain Database (ntds.dit) or Security Account Manager (SAM) files. Those files contain sensitive information including hashed domain and/or local credentials. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Elastic Endgame]  |7.11.0 |102 <<ntds-or-sam-database-file-copied-history, Version history>>
+|<<incoming-dcom-lateral-movement-with-shellbrowserwindow-or-shellwindows, Incoming DCOM Lateral Movement with ShellBrowserWindow or ShellWindows>> |Identifies use of Distributed Component Object Model (DCOM) to run commands from a remote host, which are launched via the ShellBrowserWindow or ShellWindows Application COM Object. This behavior may indicate an attacker abusing a DCOM application to stealthily move laterally. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
 
-|<<namespace-manipulation-using-unshare, Namespace Manipulation Using Unshare>> |Identifies suspicious usage of unshare to manipulate system namespaces. Unshare can be utilized to escalate privileges or escape container security boundaries. Threat actors have utilized this binary to allow themselves to escape to the host and access other resources or escalate privileges. |[Elastic] [Host] [Linux] [Threat Detection] [Privilege Escalation]  |8.5.0 |1
+|<<incoming-execution-via-powershell-remoting, Incoming Execution via PowerShell Remoting>> |Identifies remote execution via Windows PowerShell remoting. Windows PowerShell remoting allows a user to run any Windows PowerShell command on one or more remote computers. This could be an indication of lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Execution], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<network-connection-via-certutil, Network Connection via Certutil>> |Identifies certutil.exe making a network connection. Adversaries could abuse certutil.exe to download a certificate, or malware, from a remote URL. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control] [Investigation Guide]  |7.7.0 |102 <<network-connection-via-certutil-history, Version history>>
+|<<incoming-execution-via-winrm-remote-shell, Incoming Execution via WinRM Remote Shell>> |Identifies remote execution via Windows Remote Management (WinRM) remote shell on a target host. This could be an indication of lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<network-connection-via-compiled-html-file, Network Connection via Compiled HTML File>> |Compiled HTML files (.chm) are commonly distributed as part of the Microsoft HTML Help system. Adversaries may conceal malicious code in a CHM file and deliver it to a victim for execution. CHM content is loaded by the HTML Help executable program (hh.exe). |[Elastic] [Host] [Windows] [Threat Detection] [Execution]  |7.6.0 |100 <<network-connection-via-compiled-html-file-history, Version history>>
+|<<indirect-command-execution-via-forfiles-pcalua, Indirect Command Execution via Forfiles/Pcalua>> |Identifies indirect command execution via Program Compatibility Assistant (pcalua.exe) or forfiles.exe. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Rule Type: BBR], [Data Source: Elastic Endgame] |8.3.0 |2
 
-|<<network-connection-via-msxsl, Network Connection via MsXsl>> |Identifies msxsl.exe making a network connection. This may indicate adversarial activity as msxsl.exe is often leveraged by adversaries to execute malicious scripts and evade detection. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.7.0 |100 <<network-connection-via-msxsl-history, Version history>>
+|<<ingress-transfer-via-windows-bits, Ingress Transfer via Windows BITS>> |Identifies downloads of executable and archive files via the Windows Background Intelligent Transfer Service (BITS). Adversaries could leverage Windows BITS transfer jobs to download remote payloads. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Command and Control], [Data Source: Elastic Defend] |8.3.0 |7
 
-|<<network-connection-via-registration-utility, Network Connection via Registration Utility>> |Identifies the native Windows tools regsvr32.exe, regsvr64.exe, RegSvcs.exe, or RegAsm.exe making a network connection. This may be indicative of an attacker bypassing allowlists or running arbitrary scripts via a signed Microsoft binary. |[Elastic] [Host] [Windows] [Threat Detection] [Execution]  |7.6.0 |100 <<network-connection-via-registration-utility-history, Version history>>
+|<<installutil-activity, InstallUtil Activity>> |InstallUtil is a command-line utility that allows for installation and uninstallation of resources by executing specific installer components specified in .NET binaries. Adversaries may use InstallUtil to proxy the execution of code through a trusted Windows utility. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Rule Type: BBR], [Data Source: Elastic Endgame] |8.3.0 |2
 
-|<<network-connection-via-signed-binary, Network Connection via Signed Binary>> |Binaries signed with trusted digital certificates can execute on Windows systems protected by digital signature validation. Adversaries may use these binaries to 'live off the land' and execute malicious files that could bypass application allowlists and signature validation. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.6.0 |100 <<network-connection-via-signed-binary-history, Version history>>
+|<<installutil-process-making-network-connections, InstallUtil Process Making Network Connections>> |Identifies InstallUtil.exe making outbound network connections. This may indicate adversarial activity as InstallUtil is often leveraged by adversaries to execute code and evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
 
-|<<network-logon-provider-registry-modification, Network Logon Provider Registry Modification>> |Identifies the modification of the network logon provider registry. Adversaries may register a rogue network logon provider module for persistence and/or credential access via intercepting the authentication credentials in clear text during user logon. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Credential Access] [Elastic Endgame]  |7.13.0 |101 <<network-logon-provider-registry-modification-history, Version history>>
+|<<installation-of-custom-shim-databases, Installation of Custom Shim Databases>> |Identifies the installation of custom Application Compatibility Shim databases. This Windows functionality has been abused by attackers to stealthily gain persistence and arbitrary code execution in legitimate Windows processes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<network-traffic-to-rare-destination-country, Network Traffic to Rare Destination Country>> |A machine learning job detected a rare destination country name in the network logs. This can be due to initial access, persistence, command-and-control, or exfiltration activity. For example, when a user clicks on a link in a phishing email or opens a malicious document, a request may be sent to download and run a payload from a server in a country which does not normally appear in network traffic or business work-flows. Malware instances and persistence mechanisms may communicate with command-and-control (C2) infrastructure in their country of origin, which may be an unusual destination country for the source network. |[Elastic] [Network] [Threat Detection] [ML]  |7.13.0 |100 <<network-traffic-to-rare-destination-country-history, Version history>>
+|<<installation-of-security-support-provider, Installation of Security Support Provider>> |Identifies registry modifications related to the Windows Security Support Provider (SSP) configuration. Adversaries may abuse this to establish persistence in an environment. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<new-activesyncalloweddeviceid-added-via-powershell, New ActiveSyncAllowedDeviceID Added via PowerShell>> |Identifies the use of the Exchange PowerShell cmdlet, Set-CASMailbox, to add a new ActiveSync allowed device. Adversaries may target user email to collect sensitive information. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |101 <<new-activesyncalloweddeviceid-added-via-powershell-history, Version history>>
+|<<interactive-exec-command-launched-against-a-running-container, Interactive Exec Command Launched Against A Running Container>> |This rule detects interactive 'exec' events launched against a container using the 'exec' command. Using the 'exec' command in a pod allows a user to establish a temporary shell session and execute any process/command inside the container. This rule specifically targets higher-risk interactive commands that allow real-time interaction with a container's shell. A malicious actor could use this level of access to further compromise the container environment or attempt a container breakout. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution] |8.8.0 |2
 
-|<<new-or-modified-federation-domain, New or Modified Federation Domain>> |Identifies a new or modified federation domain, which can be used to create a trust between O365 and an external identity provider. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.16.0 |101 <<new-or-modified-federation-domain-history, Version history>>
+|<<interactive-logon-by-an-unusual-process, Interactive Logon by an Unusual Process>> |Identifies interactive logon attempt with alternate credentials and by an unusual process. Adversaries may create a new token to escalate privileges and bypass access controls. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |3
 
-|<<nping-process-activity, Nping Process Activity>> |Nping ran on a Linux host. Nping is part of the Nmap tool suite and has the ability to construct raw packets for a wide variety of security testing applications, including denial of service testing. |[Elastic] [Host] [Linux] [Threat Detection] [Discovery]  |7.6.0 |100 <<nping-process-activity-history, Version history>>
+|<<interactive-terminal-spawned-via-perl, Interactive Terminal Spawned via Perl>> |Identifies when a terminal (tty) is spawned via Perl. Attackers may upgrade a simple reverse shell to a fully interactive tty after obtaining initial access to a host. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<nullsessionpipe-registry-modification, NullSessionPipe Registry Modification>> |Identifies NullSessionPipe registry modifications that specify which pipes can be accessed anonymously. This could be indicative of adversary lateral movement preparation by making the added pipe available to everyone. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.13.0 |101 <<nullsessionpipe-registry-modification-history, Version history>>
+|<<interactive-terminal-spawned-via-python, Interactive Terminal Spawned via Python>> |Identifies when a terminal (tty) is spawned via Python. Attackers may upgrade a simple reverse shell to a fully interactive tty after obtaining initial access to a host. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<o365-email-reported-by-user-as-malware-or-phish, O365 Email Reported by User as Malware or Phish>> |Detects the occurrence of emails reported as Phishing or Malware by Users. Security Awareness training is essential to stay ahead of scammers and threat actors, as security products can be bypassed, and the user can still receive a malicious message. Educating users to report suspicious messages can help identify gaps in security controls and prevent malware infections and Business Email Compromise attacks. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Initial Access]  |8.1.0 |101 <<o365-email-reported-by-user-as-malware-or-phish-history, Version history>>
+|<<krbtgt-delegation-backdoor, KRBTGT Delegation Backdoor>> |Identifies the modification of the msDS-AllowedToDelegateTo attribute to KRBTGT. Attackers can use this technique to maintain persistence to the domain by having the ability to request tickets for the KRBTGT service. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Use Case: Active Directory Monitoring], [Data Source: Active Directory] |8.3.0 |107
 
-|<<o365-excessive-single-sign-on-logon-errors, O365 Excessive Single Sign-On Logon Errors>> |Identifies accounts with a high number of single sign-on (SSO) logon errors. Excessive logon errors may indicate an attempt to brute force a password or SSO token. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.14.0 |101 <<o365-excessive-single-sign-on-logon-errors-history, Version history>>
+|<<kerberos-cached-credentials-dumping, Kerberos Cached Credentials Dumping>> |Identifies the use of the Kerberos credential cache (kcc) utility to dump locally cached Kerberos tickets. Adversaries may attempt to dump credential material in the form of tickets that can be leveraged for lateral movement. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<o365-exchange-suspicious-mailbox-right-delegation, O365 Exchange Suspicious Mailbox Right Delegation>> |Identifies the assignment of rights to access content from another mailbox. An adversary may use the compromised account to send messages to other accounts in the network of the target organization while creating inbox rules, so messages can evade spam/phishing detection mechanisms. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.16.0 |101 <<o365-exchange-suspicious-mailbox-right-delegation-history, Version history>>
+|<<kerberos-pre-authentication-disabled-for-user, Kerberos Pre-authentication Disabled for User>> |Identifies the modification of an account's Kerberos pre-authentication options. An adversary with GenericWrite/GenericAll rights over the account can maliciously modify these settings to perform offline password cracking attacks such as AS-REP roasting. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Defense Evasion], [Tactic: Privilege Escalation], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring], [Data Source: Active Directory] |8.3.0 |110
 
-|<<o365-mailbox-audit-logging-bypass, O365 Mailbox Audit Logging Bypass>> |Detects the occurrence of mailbox audit bypass associations. The mailbox audit is responsible for logging specified mailbox events (like accessing a folder or a message or permanently deleting a message). However, actions taken by some authorized accounts, such as accounts used by third-party tools or accounts used for lawful monitoring, can create a large number of mailbox audit log entries and may not be of interest to your organization. Because of this, administrators can create bypass associations, allowing certain accounts to perform their tasks without being logged. Attackers can abuse this allowlist mechanism to conceal actions taken, as the mailbox audit will log no activity done by the account. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Initial Access]  |8.0.0 |101 <<o365-mailbox-audit-logging-bypass-history, Version history>>
+|<<kerberos-traffic-from-unusual-process, Kerberos Traffic from Unusual Process>> |Identifies network connections to the standard Kerberos port from an unusual process. On Windows, the only process that normally performs Kerberos traffic from a domain joined host is lsass.exe. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<okta-brute-force-or-password-spraying-attack, Okta Brute Force or Password Spraying Attack>> |Identifies a high number of failed Okta user authentication attempts from a single IP address, which could be indicative of a brute force or password spraying attack. An adversary may attempt a brute force or password spraying attack to obtain unauthorized access to user accounts. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.9.0 |102 <<okta-brute-force-or-password-spraying-attack-history, Version history>>
+|<<kernel-driver-load, Kernel Driver Load>> |Detects the loading of a Linux kernel module through system calls. Threat actors may leverage Linux kernel modules to load a rootkit on a system providing them with complete control and the ability to hide from security products. As other rules monitor for the addition of Linux kernel modules through system utilities or .ko files, this rule covers the gap that evasive rootkits leverage by monitoring for kernel module additions on the lowest level through auditd_manager. |[Data Source: Auditd Manager], [Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion] |8.3.0 |4
 
-|<<okta-user-session-impersonation, Okta User Session Impersonation>> |A user has initiated a session impersonation granting them access to the environment with the permissions of the user they are impersonating. This would likely indicate Okta administrative access and should only ever occur if requested and expected. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access] [Credential Access]  |8.2.0 |102 <<okta-user-session-impersonation-history, Version history>>
+|<<kernel-driver-load-by-non-root-user, Kernel Driver Load by non-root User>> |Detects the loading of a Linux kernel module by a non-root user through system calls. Threat actors may leverage Linux kernel modules to load a rootkit on a system providing them with complete control and the ability to hide from security products. As other rules monitor for the addition of Linux kernel modules through system utilities or .ko files, this rule covers the gap that evasive rootkits leverage by monitoring for kernel module additions on the lowest level through auditd_manager. |[Data Source: Auditd Manager], [Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion] |8.3.0 |3
 
-|<<onedrive-malware-file-upload, OneDrive Malware File Upload>> |Identifies the occurence of files uploaded to OneDrive being detected as Malware by the file scanning engine. Attackers can use File Sharing and Organization Repositories to spread laterally within the company and amplify their access. Users can inadvertently share these files without knowing their maliciousness, giving adversaries opportunity to gain initial access to other endpoints in the environment. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Lateral Movement]  |8.1.0 |101 <<onedrive-malware-file-upload-history, Version history>>
+|<<kernel-load-or-unload-via-kexec-detected, Kernel Load or Unload via Kexec Detected>> |This detection rule identifies the usage of kexec, helping to uncover unauthorized kernel replacements and potential compromise of the system's integrity. Kexec is a Linux feature that enables the loading and execution of a different kernel without going through the typical boot process. Malicious actors can abuse kexec to bypass security measures, escalate privileges, establish persistence or hide their activities by loading a malicious kernel, enabling them to tamper with the system's trusted state, allowing e.g. a VM Escape. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |6
 
-|<<outbound-scheduled-task-activity-via-powershell, Outbound Scheduled Task Activity via PowerShell>> |Identifies the PowerShell process loading the Task Scheduler COM DLL followed by an outbound RPC network connection within a short time period. This may indicate lateral movement or remote discovery via scheduled tasks. |[Elastic] [Host] [Windows] [Threat Detection] [Execution]  |7.11.0 |100 <<outbound-scheduled-task-activity-via-powershell-history, Version history>>
+|<<kernel-module-load-via-insmod, Kernel Module Load via insmod>> |Detects the use of the insmod binary to load a Linux kernel object file. Threat actors can use this binary, given they have root privileges, to load a rootkit on a system providing them with complete control and the ability to hide from security products. Manually loading a kernel module in this manner should not be at all common and can indicate suspcious or malicious behavior. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Threat: Rootkit], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |109
 
-|<<parent-process-pid-spoofing, Parent Process PID Spoofing>> |Identifies parent process spoofing used to thwart detection. Adversaries may spoof the parent process identifier (PPID) of a new process to evade process-monitoring defenses or to elevate privileges. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.14.0 |100 <<parent-process-pid-spoofing-history, Version history>>
+|<<kernel-module-removal, Kernel Module Removal>> |Kernel modules are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. This rule identifies attempts to remove a kernel module. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<peripheral-device-discovery, Peripheral Device Discovery>> |Identifies use of the Windows file system utility (fsutil.exe) to gather information about attached peripheral devices and components connected to a computer system. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<peripheral-device-discovery-history, Version history>>
+|<<keychain-password-retrieval-via-command-line, Keychain Password Retrieval via Command Line>> |Adversaries may collect keychain storage data from a system to in order to acquire credentials. Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features, including Wi-Fi and website passwords, secure notes, certificates, and Kerberos. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<permission-theft-detected-elastic-endgame, Permission Theft - Detected - Elastic Endgame>> |Elastic Endgame detected Permission Theft. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame] [Threat Detection] [Privilege Escalation]  |7.6.0 |100 <<permission-theft-detected-elastic-endgame-history, Version history>>
+|<<kirbi-file-creation, Kirbi File Creation>> |Identifies the creation of .kirbi files. The creation of this kind of file is an indicator of an attacker running Kerberos ticket dump utilities, such as Mimikatz, and precedes attacks such as Pass-The-Ticket (PTT), which allows the attacker to impersonate users using Kerberos tickets. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |5
 
-|<<permission-theft-prevented-elastic-endgame, Permission Theft - Prevented - Elastic Endgame>> |Elastic Endgame prevented Permission Theft. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame] [Threat Detection] [Privilege Escalation]  |7.6.0 |100 <<permission-theft-prevented-elastic-endgame-history, Version history>>
+|<<kubernetes-anonymous-request-authorized, Kubernetes Anonymous Request Authorized>> |This rule detects when an unauthenticated user request is authorized within the cluster. Attackers may attempt to use anonymous accounts to gain initial access to the cluster or to avoid attribution of their activities within the cluster. This rule excludes the /healthz, /livez and /readyz endpoints which are commonly accessed anonymously. |[Data Source: Kubernetes], [Tactic: Execution], [Tactic: Initial Access], [Tactic: Defense Evasion] |8.4.0 |6
 
-|<<persistence-via-bits-job-notify-cmdline, Persistence via BITS Job Notify Cmdline>> |An adversary can use the Background Intelligent Transfer Service (BITS) SetNotifyCmdLine method to execute a program that runs after a job finishes transferring data or after a job enters a specified state in order to persist on a system. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.13.0 |100 <<persistence-via-bits-job-notify-cmdline-history, Version history>>
+|<<kubernetes-container-created-with-excessive-linux-capabilities, Kubernetes Container Created with Excessive Linux Capabilities>> |This rule detects a container deployed with one or more dangerously permissive Linux capabilities. An attacker with the ability to deploy a container with added capabilities could use this for further execution, lateral movement, or privilege escalation within a cluster. The capabilities detected in this rule have been used in container escapes to the host machine. |[Data Source: Kubernetes], [Tactic: Execution], [Tactic: Privilege Escalation] |8.4.0 |4
 
-|<<persistence-via-directoryservice-plugin-modification, Persistence via DirectoryService Plugin Modification>> |Identifies the creation or modification of a DirectoryService PlugIns (dsplug) file. The DirectoryService daemon launches on each system boot and automatically reloads after crash. It scans and executes bundles that are located in the DirectoryServices PlugIns folder and can be abused by adversaries to maintain persistence. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<persistence-via-directoryservice-plugin-modification-history, Version history>>
+|<<kubernetes-denied-service-account-request, Kubernetes Denied Service Account Request>> |This rule detects when a service account makes an unauthorized request for resources from the API server. Service accounts follow a very predictable pattern of behavior. A service account should never send an unauthorized request to the API server. This behavior is likely an indicator of compromise or of a problem within the cluster. An adversary may have gained access to credentials/tokens and this could be an attempt to access or create resources to facilitate further movement or execution within the cluster. |[Data Source: Kubernetes], [Tactic: Discovery] |8.4.0 |5
 
-|<<persistence-via-docker-shortcut-modification, Persistence via Docker Shortcut Modification>> |An adversary can establish persistence by modifying an existing macOS dock property list in order to execute a malicious application instead of the intended one when invoked. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<persistence-via-docker-shortcut-modification-history, Version history>>
+|<<kubernetes-exposed-service-created-with-type-nodeport, Kubernetes Exposed Service Created With Type NodePort>> |This rule detects an attempt to create or modify a service as type NodePort. The NodePort service allows a user to externally expose a set of labeled pods to the internet. This creates an open port on every worker node in the cluster that has a pod for that service. When external traffic is received on that open port, it directs it to the specific pod through the service representing it. A malicious user can configure a service as type Nodeport in order to intercept traffic from other pods or nodes, bypassing firewalls and other network security measures configured for load balancers within a cluster. This creates a direct method of communication between the cluster and the outside world, which could be used for more malicious behavior and certainly widens the attack surface of your cluster. |[Data Source: Kubernetes], [Tactic: Execution], [Tactic: Persistence] |8.4.0 |203
 
-|<<persistence-via-folder-action-script, Persistence via Folder Action Script>> |Detects modification of a Folder Action script. A Folder Action script is executed when the folder to which it is attached has items added or removed, or when its window is opened, closed, moved, or resized. Adversaries may abuse this feature to establish persistence by utilizing a malicious script. |[Elastic] [Host] [macOS] [Threat Detection] [Execution] [Persistence]  |7.11.0 |100 <<persistence-via-folder-action-script-history, Version history>>
+|<<kubernetes-pod-created-with-hostipc, Kubernetes Pod Created With HostIPC>> |This rule detects an attempt to create or modify a pod using the host IPC namespace. This gives access to data used by any pod that also use the hosts IPC namespace. If any process on the host or any processes in a pod uses the hosts inter-process communication mechanisms (shared memory, semaphore arrays, message queues, etc.), an attacker can read/write to those same mechanisms. They may look for files in /dev/shm or use ipcs to check for any IPC facilities being used. |[Data Source: Kubernetes], [Tactic: Execution], [Tactic: Privilege Escalation] |8.4.0 |203
 
-|<<persistence-via-hidden-run-key-detected, Persistence via Hidden Run Key Detected>> |Identifies a persistence mechanism that utilizes the NtSetValueKey native API to create a hidden (null terminated) registry key. An adversary may use this method to hide from system utilities such as the Registry Editor (regedit). |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<persistence-via-hidden-run-key-detected-history, Version history>>
+|<<kubernetes-pod-created-with-hostnetwork, Kubernetes Pod Created With HostNetwork>> |This rules detects an attempt to create or modify a pod attached to the host network. HostNetwork allows a pod to use the node network namespace. Doing so gives the pod access to any service running on localhost of the host. An attacker could use this access to snoop on network activity of other pods on the same node or bypass restrictive network policies applied to its given namespace. |[Data Source: Kubernetes], [Tactic: Execution], [Tactic: Privilege Escalation] |8.4.0 |203
 
-|<<persistence-via-kde-autostart-script-or-desktop-file-modification, Persistence via KDE AutoStart Script or Desktop File Modification>> |Identifies the creation or modification of a K Desktop Environment (KDE) AutoStart script or desktop file that will execute upon each user logon. Adversaries may abuse this method for persistence. |[Elastic] [Host] [Linux] [Threat Detection] [Persistence]  |7.12.0 |100 <<persistence-via-kde-autostart-script-or-desktop-file-modification-history, Version history>>
+|<<kubernetes-pod-created-with-hostpid, Kubernetes Pod Created With HostPID>> |This rule detects an attempt to create or modify a pod attached to the host PID namespace. HostPID allows a pod to access all the processes running on the host and could allow an attacker to take malicious action. When paired with ptrace this can be used to escalate privileges outside of the container. When paired with a privileged container, the pod can see all of the processes on the host. An attacker can enter the init system (PID 1) on the host. From there, they could execute a shell and continue to escalate privileges to root. |[Data Source: Kubernetes], [Tactic: Execution], [Tactic: Privilege Escalation] |8.4.0 |203
 
-|<<persistence-via-login-or-logout-hook, Persistence via Login or Logout Hook>> |Identifies use of the Defaults command to install a login or logoff hook in MacOS. An adversary may abuse this capability to establish persistence in an environment by inserting code to be executed at login or logout. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.11.0 |100 <<persistence-via-login-or-logout-hook-history, Version history>>
+|<<kubernetes-pod-created-with-a-sensitive-hostpath-volume, Kubernetes Pod created with a Sensitive hostPath Volume>> |This rule detects when a pod is created with a sensitive volume of type hostPath. A hostPath volume type mounts a sensitive file or folder from the node to the container. If the container gets compromised, the attacker can use this mount for gaining access to the node. There are many ways a container with unrestricted access to the host filesystem can escalate privileges, including reading data from other containers, and accessing tokens of more privileged pods. |[Data Source: Kubernetes], [Tactic: Execution], [Tactic: Privilege Escalation] |8.4.0 |203
 
-|<<persistence-via-microsoft-office-addins, Persistence via Microsoft Office AddIns>> |Detects attempts to establish persistence on an endpoint by abusing Microsoft Office add-ins. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<persistence-via-microsoft-office-addins-history, Version history>>
+|<<kubernetes-privileged-pod-created, Kubernetes Privileged Pod Created>> |This rule detects when a user creates a pod/container running in privileged mode. A highly privileged container has access to the node's resources and breaks the isolation between containers. If compromised, an attacker can use the privileged container to gain access to the underlying host. Gaining access to the host may provide the adversary with the opportunity to achieve follow-on objectives, such as establishing persistence, moving laterally within the environment, or setting up a command and control channel on the host. |[Data Source: Kubernetes], [Tactic: Execution], [Tactic: Privilege Escalation] |8.4.0 |203
 
-|<<persistence-via-microsoft-outlook-vba, Persistence via Microsoft Outlook VBA>> |Detects attempts to establish persistence on an endpoint by installing a rogue Microsoft Outlook VBA Template. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<persistence-via-microsoft-outlook-vba-history, Version history>>
+|<<kubernetes-suspicious-assignment-of-controller-service-account, Kubernetes Suspicious Assignment of Controller Service Account>> |This rule detects a request to attach a controller service account to an existing or new pod running in the kube-system namespace. By default, controllers running as part of the API Server utilize admin-equivalent service accounts hosted in the kube-system namespace. Controller service accounts aren't normally assigned to running pods and could indicate adversary behavior within the cluster. An attacker that can create or modify pods or pod controllers in the kube-system namespace, can assign one of these admin-equivalent service accounts to a pod and abuse their powerful token to escalate privileges and gain complete cluster control. |[Data Source: Kubernetes], [Tactic: Execution], [Tactic: Privilege Escalation] |8.4.0 |6
 
-|<<persistence-via-powershell-profile, Persistence via PowerShell profile>> |Identifies the creation or modification of a PowerShell profile. PowerShell profile is a script that is executed when PowerShell starts to customize the user environment, which can be abused by attackers to persist in a environment where PowerShell is common. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |8.6.0 |1
+|<<kubernetes-suspicious-self-subject-review, Kubernetes Suspicious Self-Subject Review>> |This rule detects when a service account or node attempts to enumerate their own permissions via the selfsubjectaccessreview or selfsubjectrulesreview APIs. This is highly unusual behavior for non-human identities like service accounts and nodes. An adversary may have gained access to credentials/tokens and this could be an attempt to determine what privileges they have to facilitate further movement or execution within the cluster. |[Data Source: Kubernetes], [Tactic: Discovery] |8.4.0 |203
 
-|<<persistence-via-scheduled-job-creation, Persistence via Scheduled Job Creation>> |A job can be used to schedule programs or scripts to be executed at a specified date and time. Adversaries may abuse task scheduling functionality to facilitate initial or recurring execution of malicious code. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.13.0 |100 <<persistence-via-scheduled-job-creation-history, Version history>>
+|<<kubernetes-user-exec-into-pod, Kubernetes User Exec into Pod>> |This rule detects a user attempt to establish a shell session into a pod using the 'exec' command. Using the 'exec' command in a pod allows a user to establish a temporary shell session and execute any process/commands in the pod. An adversary may call bash to gain a persistent interactive shell which will allow access to any data the pod has permissions to, including secrets. |[Data Source: Kubernetes], [Tactic: Execution] |8.4.0 |203
 
-|<<persistence-via-telemetrycontroller-scheduled-task-hijack, Persistence via TelemetryController Scheduled Task Hijack>> |Detects the successful hijack of Microsoft Compatibility Appraiser scheduled task to establish persistence with an integrity level of system. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.10.0 |101 <<persistence-via-telemetrycontroller-scheduled-task-hijack-history, Version history>>
+|<<lsass-memory-dump-creation, LSASS Memory Dump Creation>> |Identifies the creation of a Local Security Authority Subsystem Service (lsass.exe) default memory dump. This may indicate a credential access attempt via trusted system utilities such as Task Manager (taskmgr.exe) and SQL Dumper (sqldumper.exe) or known pentesting tools such as Dumpert and AndrewSpecial. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<persistence-via-update-orchestrator-service-hijack, Persistence via Update Orchestrator Service Hijack>> |Identifies potential hijacking of the Microsoft Update Orchestrator Service to establish persistence with an integrity level of SYSTEM. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [CVE-2020-1313] [Investigation Guide]  |7.10.0 |102 <<persistence-via-update-orchestrator-service-hijack-history, Version history>>
+|<<lsass-memory-dump-handle-access, LSASS Memory Dump Handle Access>> |Identifies handle requests for the Local Security Authority Subsystem Service (LSASS) object access with specific access masks that many tools with a capability to dump memory to disk use (0x1fffff, 0x1010, 0x120089). This rule is tool agnostic as it has been validated against a host of various LSASS dump tools such as SharpDump, Procdump, Mimikatz, Comsvcs etc. It detects this behavior at a low level and does not depend on a specific tool or dump file name. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide] |8.3.0 |110
 
-|<<persistence-via-wmi-event-subscription, Persistence via WMI Event Subscription>> |An adversary can use Windows Management Instrumentation (WMI) to install event filters, providers, consumers, and bindings that execute code when a defined event occurs. Adversaries may use the capabilities of WMI to subscribe to an event and execute arbitrary code when that event occurs, providing persistence on a system. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |102 <<persistence-via-wmi-event-subscription-history, Version history>>
+|<<lsass-process-access-via-windows-api, LSASS Process Access via Windows API>> |Identifies access attempts to the LSASS handle, which may indicate an attempt to dump credentials from LSASS memory. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Execution], [Data Source: Elastic Defend] |8.7.0 |7
 
-|<<persistence-via-wmi-standard-registry-provider, Persistence via WMI Standard Registry Provider>> |Identifies use of the Windows Management Instrumentation StdRegProv (registry provider) to modify commonly abused registry locations for persistence. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.13.0 |101 <<persistence-via-wmi-standard-registry-provider-history, Version history>>
+|<<lateral-movement-via-startup-folder, Lateral Movement via Startup Folder>> |Identifies suspicious file creations in the startup folder of a remote system. An adversary could abuse this to move laterally by dropping a malicious script or executable that will be executed after a reboot or user logon. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<persistent-scripts-in-the-startup-directory, Persistent Scripts in the Startup Directory>> |Identifies script engines creating files in the Startup folder, or the creation of script files in the Startup folder. Adversaries may abuse this technique to maintain persistence in an environment. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.11.0 |102 <<persistent-scripts-in-the-startup-directory-history, Version history>>
+|<<launch-agent-creation-or-modification-and-immediate-loading, Launch Agent Creation or Modification and Immediate Loading>> |An adversary can establish persistence by installing a new launch agent that executes at login by using launchd or launchctl to load a plist into the appropriate directories. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<port-forwarding-rule-addition, Port Forwarding Rule Addition>> |Identifies the creation of a new port forwarding rule. An adversary may abuse this technique to bypass network segmentation restrictions. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<port-forwarding-rule-addition-history, Version history>>
+|<<launchdaemon-creation-or-modification-and-immediate-loading, LaunchDaemon Creation or Modification and Immediate Loading>> |Indicates the creation or modification of a launch daemon, which adversaries may use to repeatedly execute malicious payloads as part of persistence. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<possible-consent-grant-attack-via-azure-registered-application, Possible Consent Grant Attack via Azure-Registered Application>> |Detects when a user grants permissions to an Azure-registered application or when an administrator grants tenant-wide permissions to an application. An adversary may create an Azure-registered application that requests access to data such as contact information, email, or documents. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Identity and Access] [Investigation Guide]  |7.10.0 |103 <<possible-consent-grant-attack-via-azure-registered-application-history, Version history>>
+|<<linux-group-creation, Linux Group Creation>> |Identifies attempts to create a new group. Attackers may create new groups to establish persistence on a system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide] |8.3.0 |5
 
-|<<possible-fin7-dga-command-and-control-behavior, Possible FIN7 DGA Command and Control Behavior>> |This rule detects a known command and control pattern in network events. The FIN7 threat group is known to use this command and control technique, while maintaining persistence in their target's network. |[Elastic] [Network] [Threat Detection] [Command and Control] [Host]  |7.10.0 |100 <<possible-fin7-dga-command-and-control-behavior-history, Version history>>
+|<<linux-process-hooking-via-gdb, Linux Process Hooking via GDB>> |This rule monitors for potential memory dumping through gdb. Attackers may leverage memory dumping techniques to attempt secret extraction from privileged processes. Tools that display this behavior include "truffleproc" and "bash-memory-dump". This behavior should not happen by default, and should be investigated thoroughly. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |3
 
-|<<possible-okta-dos-attack, Possible Okta DoS Attack>> |Detects possible Denial of Service (DoS) attacks against an Okta organization. An adversary may attempt to disrupt an organization's business operations by performing a DoS attack against its Okta service. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring]  |7.9.0 |102 <<possible-okta-dos-attack-history, Version history>>
+|<<linux-restricted-shell-breakout-via-linux-binary-s, Linux Restricted Shell Breakout via Linux Binary(s)>> |Identifies the abuse of a Linux binary to break out of a restricted shell or environment by spawning an interactive system shell. The activity of spawning a shell from a binary is not common behavior for a user or system administrator, and may indicate an attempt to evade detection, increase capabilities or enhance the stability of an adversary. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
 
-|<<potential-abuse-of-repeated-mfa-push-notifications, Potential Abuse of Repeated MFA Push Notifications>> |Detects when an attacker abuses the Multi-Factor authentication mechanism by repeatedly issuing login requests until the user eventually accepts the Okta push notification. An adversary may attempt to bypass the Okta MFA policies configured for an organization to obtain unauthorized access. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access]  |8.1.0 |101 <<potential-abuse-of-repeated-mfa-push-notifications-history, Version history>>
+|<<linux-system-information-discovery, Linux System Information Discovery>> |Enrich process events with uname and other command lines that imply Linux system information discovery. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |3
 
-|<<potential-admin-group-account-addition, Potential Admin Group Account Addition>> |Identifies attempts to add an account to the admin group via the command line. This could be an indication of privilege escalation activity. |[Elastic] [Host] [macOS] [Threat Detection] [Privilege Escalation]  |7.12.0 |100 <<potential-admin-group-account-addition-history, Version history>>
+|<<linux-user-account-creation, Linux User Account Creation>> |Identifies attempts to create new users. Attackers may add new users to establish persistence on a system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide] |8.3.0 |5
 
-|<<potential-application-shimming-via-sdbinst, Potential Application Shimming via Sdbinst>> |The Application Shim was created to allow for backward compatibility of software as the operating system codebase changes over time. This Windows functionality has been abused by attackers to stealthily gain persistence and arbitrary code execution in legitimate Windows processes. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.6.0 |102 <<potential-application-shimming-via-sdbinst-history, Version history>>
+|<<linux-user-added-to-privileged-group, Linux User Added to Privileged Group>> |Identifies attempts to add a user to a privileged group. Attackers may add users to a privileged group in order to establish persistence on a system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |6
 
-|<<potential-command-and-control-via-internet-explorer, Potential Command and Control via Internet Explorer>> |Identifies instances of Internet Explorer (iexplore.exe) being started via the Component Object Model (COM) making unusual network connections. Adversaries could abuse Internet Explorer via COM to avoid suspicious processes making network connections and bypass host-based firewall restrictions. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control]  |7.11.0 |100 <<potential-command-and-control-via-internet-explorer-history, Version history>>
+|<<linux-init-pid-1-secret-dump-via-gdb, Linux init (PID 1) Secret Dump via GDB>> |This rule monitors for the potential memory dump of the init process (PID 1) through gdb. Attackers may leverage memory dumping techniques to attempt secret extraction from privileged processes. Tools that display this behavior include "truffleproc" and "bash-memory-dump". This behavior should not happen by default, and should be investigated thoroughly. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |6
 
-|<<potential-cookies-theft-via-browser-debugging, Potential Cookies Theft via Browser Debugging>> |Identifies the execution of a Chromium based browser with the debugging process argument, which may indicate an attempt to steal authentication cookies. An adversary may steal web application or service session cookies and use them to gain access web applications or Internet services as an authenticated user without needing credentials. |[Elastic] [Host] [Linux] [Windows] [macOS] [Threat Detection] [Credential Access]  |7.12.0 |100 <<potential-cookies-theft-via-browser-debugging-history, Version history>>
+|<<local-account-tokenfilter-policy-disabled, Local Account TokenFilter Policy Disabled>> |Identifies registry modification to the LocalAccountTokenFilterPolicy policy. If this value exists (which doesn't by default) and is set to 1, then remote connections from all local members of Administrators are granted full high-integrity tokens during negotiation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Lateral Movement], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |8
 
-|<<potential-credential-access-via-dcsync, Potential Credential Access via DCSync>> |This rule identifies when a User Account starts the Active Directory Replication Process. Attackers can use the DCSync technique to get credential information of individual accounts or the entire domain, thus compromising the entire domain. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Active Directory] [Investigation Guide]  |8.1.0 |102 <<potential-credential-access-via-dcsync-history, Version history>>
+|<<local-scheduled-task-creation, Local Scheduled Task Creation>> |Indicates the creation of a scheduled task. Adversaries can use these to establish persistence, move laterally, and/or escalate privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
 
-|<<potential-credential-access-via-duplicatehandle-in-lsass, Potential Credential Access via DuplicateHandle in LSASS>> |Identifies suspicious access to an LSASS handle via DuplicateHandle from an unknown call trace module. This may indicate an attempt to bypass the NtOpenProcess API to evade detection and dump LSASS memory for credential access. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Sysmon Only]  |7.16.0 |101 <<potential-credential-access-via-duplicatehandle-in-lsass-history, Version history>>
+|<<mfa-deactivation-with-no-re-activation-for-okta-user-account, MFA Deactivation with no Re-Activation for Okta User Account>> |Detects multi-factor authentication (MFA) deactivation with no subsequent re-activation for an Okta user account. An adversary may deactivate MFA for an Okta user account in order to weaken the authentication requirements for the account. |[Tactic: Persistence], [Use Case: Identity and Access Audit], [Data Source: Okta], [Domain: Cloud] |8.10.0 |207
 
-|<<potential-credential-access-via-lsass-memory-dump, Potential Credential Access via LSASS Memory Dump>> |Identifies suspicious access to LSASS handle from a call trace pointing to DBGHelp.dll or DBGCore.dll, which both export the MiniDumpWriteDump method that can be used to dump LSASS memory content in preparation for credential access. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Sysmon Only]  |8.0.0 |101 <<potential-credential-access-via-lsass-memory-dump-history, Version history>>
+|<<mfa-disabled-for-google-workspace-organization, MFA Disabled for Google Workspace Organization>> |Detects when multi-factor authentication (MFA) is disabled for a Google Workspace organization. An adversary may attempt to modify a password policy in order to weaken an organization’s security controls. |[Domain: Cloud], [Data Source: Google Workspace], [Use Case: Identity and Access Audit], [Tactic: Persistence], [Resources: Investigation Guide] |8.4.0 |205
 
-|<<potential-credential-access-via-renamed-com-services-dll, Potential Credential Access via Renamed COM+ Services DLL>> |Identifies suspicious renamed COMSVCS.DLL Image Load, which exports the MiniDump function that can be used to dump a process memory. This may indicate an attempt to dump LSASS memory while bypassing command-line based detection in preparation for credential access. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Sysmon Only]  |8.0.0 |101 <<potential-credential-access-via-renamed-com-services-dll-history, Version history>>
+|<<ms-office-macro-security-registry-modifications, MS Office Macro Security Registry Modifications>> |Microsoft Office Products offer options for users and developers to control the security settings for running and using Macros. Adversaries may abuse these security settings to modify the default behavior of the Office Application to trust future macros and/or disable security warnings, which could increase their chances of establishing persistence. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Sysmon] |8.3.0 |107
 
-|<<potential-credential-access-via-trusted-developer-utility, Potential Credential Access via Trusted Developer Utility>> |An instance of MSBuild, the Microsoft Build Engine, loaded DLLs (dynamically linked libraries) responsible for Windows credential management. This technique is sometimes used for credential dumping. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide]  |7.7.0 |102 <<potential-credential-access-via-trusted-developer-utility-history, Version history>>
+|<<macos-installer-package-spawns-network-event, MacOS Installer Package Spawns Network Event>> |Detects the execution of a MacOS installer package with an abnormal child process (e.g bash) followed immediately by a network connection via a suspicious process (e.g curl). Threat actors will build and distribute malicious MacOS installer packages, which have a .pkg extension, many times imitating valid software in order to persuade and infect their victims often using the package files (e.g pre/post install scripts etc.) to download additional tools or malicious software. If this rule fires it should indicate the installation of a malicious or suspicious package. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Command and Control], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<potential-credential-access-via-windows-utilities, Potential Credential Access via Windows Utilities>> |Identifies the execution of known Windows utilities often abused to dump LSASS memory or the Active Directory database (NTDS.dit) in preparation for credential access. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<potential-credential-access-via-windows-utilities-history, Version history>>
+|<<machine-learning-detected-dga-activity-using-a-known-sunburst-dns-domain, Machine Learning Detected DGA activity using a known SUNBURST DNS domain>> |A supervised machine learning model has identified a DNS question name that used by the SUNBURST malware and is predicted to be the result of a Domain Generation Algorithm. |[Domain: Network], [Domain: Endpoint], [Data Source: Elastic Defend], [Use Case: Domain Generation Algorithm Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Command and Control] |8.9.0 |3
 
-|<<potential-dll-side-loading-via-microsoft-antimalware-service-executable, Potential DLL Side-Loading via Microsoft Antimalware Service Executable>> |Identifies a Windows trusted program that is known to be vulnerable to DLL Search Order Hijacking starting after being renamed or from a non-standard path. This is uncommon behavior and may indicate an attempt to evade defenses via side-loading a malicious DLL within the memory space of one of those processes. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.14.0 |101 <<potential-dll-side-loading-via-microsoft-antimalware-service-executable-history, Version history>>
+|<<machine-learning-detected-a-dns-request-predicted-to-be-a-dga-domain, Machine Learning Detected a DNS Request Predicted to be a DGA Domain>> |A supervised machine learning model has identified a DNS question name that is predicted to be the result of a Domain Generation Algorithm (DGA), which could indicate command and control network activity. |[Domain: Network], [Domain: Endpoint], [Data Source: Elastic Defend], [Use Case: Domain Generation Algorithm Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Command and Control] |8.9.0 |3
 
-|<<potential-dll-sideloading-via-trusted-microsoft-programs, Potential DLL SideLoading via Trusted Microsoft Programs>> |Identifies an instance of a Windows trusted program that is known to be vulnerable to DLL Search Order Hijacking starting after being renamed or from a non-standard path. This is uncommon behavior and may indicate an attempt to evade defenses via side loading a malicious DLL within the memory space of one of those processes. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.10.0 |101 <<potential-dll-sideloading-via-trusted-microsoft-programs-history, Version history>>
+|<<machine-learning-detected-a-dns-request-with-a-high-dga-probability-score, Machine Learning Detected a DNS Request With a High DGA Probability Score>> |A supervised machine learning model has identified a DNS question name with a high probability of sourcing from a Domain Generation Algorithm (DGA), which could indicate command and control network activity. |[Domain: Network], [Domain: Endpoint], [Data Source: Elastic Defend], [Use Case: Domain Generation Algorithm Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Command and Control] |8.9.0 |3
 
-|<<potential-dns-tunneling-via-iodine, Potential DNS Tunneling via Iodine>> |Iodine is a tool for tunneling Internet protocol version 4 (IPV4) traffic over the DNS protocol to circumvent firewalls, network security groups, and network access lists while evading detection. |[Elastic] [Host] [Linux] [Threat Detection] [Command and Control]  |7.6.0 |100 <<potential-dns-tunneling-via-iodine-history, Version history>>
+|<<machine-learning-detected-a-suspicious-windows-event-predicted-to-be-malicious-activity, Machine Learning Detected a Suspicious Windows Event Predicted to be Malicious Activity>> |A supervised machine learning model (ProblemChild) has identified a suspicious Windows process event with high probability of it being malicious activity. Alternatively, the model's blocklist identified the event as being malicious. |[OS: Windows], [Data Source: Elastic Endgame], [Use Case: Living off the Land Attack Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Defense Evasion] |8.9.0 |4
 
-|<<potential-dns-tunneling-via-nslookup, Potential DNS Tunneling via NsLookup>> |This rule identifies a large number (15) of nslookup.exe executions with an explicit query type from the same host. This may indicate command and control activity utilizing the DNS protocol. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<potential-dns-tunneling-via-nslookup-history, Version history>>
+|<<machine-learning-detected-a-suspicious-windows-event-with-a-high-malicious-probability-score, Machine Learning Detected a Suspicious Windows Event with a High Malicious Probability Score>> |A supervised machine learning model (ProblemChild) has identified a suspicious Windows process event with high probability of it being malicious activity. Alternatively, the model's blocklist identified the event as being malicious. |[OS: Windows], [Data Source: Elastic Endgame], [Use Case: Living off the Land Attack Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Defense Evasion] |8.9.0 |4
 
-|<<potential-disabling-of-selinux, Potential Disabling of SELinux>> |Identifies potential attempts to disable Security-Enhanced Linux (SELinux), which is a Linux kernel security feature to support access control policies. Adversaries may disable security tools to avoid possible detection of their tools and activities. |[Elastic] [Host] [Linux] [Threat Detection] [Defense Evasion]  |7.8.0 |100 <<potential-disabling-of-selinux-history, Version history>>
+|<<malware-detected-elastic-endgame, Malware - Detected - Elastic Endgame>> |Elastic Endgame detected Malware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame] |8.3.0 |103
 
-|<<potential-evasion-via-filter-manager, Potential Evasion via Filter Manager>> |The Filter Manager Control Program (fltMC.exe) binary may be abused by adversaries to unload a filter driver and evade defenses. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.6.0 |102 <<potential-evasion-via-filter-manager-history, Version history>>
+|<<malware-prevented-elastic-endgame, Malware - Prevented - Elastic Endgame>> |Elastic Endgame prevented Malware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame] |8.3.0 |103
 
-|<<potential-hidden-local-user-account-creation, Potential Hidden Local User Account Creation>> |Identifies attempts to create a local account that will be hidden from the macOS logon window. This may indicate an attempt to evade user attention while maintaining persistence using a separate local account. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<potential-hidden-local-user-account-creation-history, Version history>>
+|<<masquerading-space-after-filename, Masquerading Space After Filename>> |This rules identifies a process created from an executable with a space appended to the end of the filename. This may indicate an attempt to masquerade a malicious file as benign to gain user execution. When a space is added to the end of certain files, the OS will execute the file according to it's true filetype instead of it's extension. Adversaries can hide a program's true filetype by changing the extension of the file. They can then add a space to the end of the name so that the OS automatically executes the file when it's double-clicked. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |6
 
-|<<potential-invoke-mimikatz-powershell-script, Potential Invoke-Mimikatz PowerShell Script>> |Mimikatz is a credential dumper capable of obtaining plaintext Windows account logins and passwords, along with many other features that make it useful for testing the security of networks. This rule detects Invoke-Mimikatz PowerShell script and alike. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide]  |8.3.0 |102 <<potential-invoke-mimikatz-powershell-script-history, Version history>>
+|<<member-removed-from-github-organization, Member Removed From GitHub Organization>> |A member was removed or their invitation to join was removed from a GitHub Organization. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Impact], [Rule Type: BBR], [Data Source: Github] |8.3.0 |1
 
-|<<potential-java-jndi-exploitation-attempt, Potential JAVA/JNDI Exploitation Attempt>> |Identifies an outbound network connection by JAVA to LDAP, RMI or DNS standard ports followed by a suspicious JAVA child processes. This may indicate an attempt to exploit a JAVA/NDI (Java Naming and Directory Interface) injection vulnerability. |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Execution]  |8.1.0 |101 <<potential-java-jndi-exploitation-attempt-history, Version history>>
+|<<memory-dump-file-with-unusual-extension, Memory Dump File with Unusual Extension>> |Identifies the creation of a memory dump file with an unusual extension, which can indicate an attempt to disguise a memory dump as another file type to bypass security defenses. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |2
 
-|<<potential-kerberos-attack-via-bifrost, Potential Kerberos Attack via Bifrost>> |Identifies use of Bifrost, a known macOS Kerberos pentesting tool, which can be used to dump cached Kerberos tickets or attempt unauthorized authentication techniques such as pass-the-ticket/hash and kerberoasting. |[Elastic] [Host] [macOS] [Threat Detection] [Credential Access] [Lateral Movement]  |7.12.0 |100 <<potential-kerberos-attack-via-bifrost-history, Version history>>
+|<<microsoft-365-exchange-anti-phish-policy-deletion, Microsoft 365 Exchange Anti-Phish Policy Deletion>> |Identifies the deletion of an anti-phishing policy in Microsoft 365. By default, Microsoft 365 includes built-in features that help protect users from phishing attacks. Anti-phishing polices increase this protection by refining settings to better detect and prevent attacks. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Initial Access] |8.8.0 |206
 
-|<<potential-lsa-authentication-package-abuse, Potential LSA Authentication Package Abuse>> |Adversaries can use the autostart mechanism provided by the Local Security Authority (LSA) authentication packages for privilege escalation or persistence by placing a reference to a binary in the Windows registry. The binary will then be executed by SYSTEM when the authentication packages are loaded. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.12.0 |100 <<potential-lsa-authentication-package-abuse-history, Version history>>
+|<<microsoft-365-exchange-anti-phish-rule-modification, Microsoft 365 Exchange Anti-Phish Rule Modification>> |Identifies the modification of an anti-phishing rule in Microsoft 365. By default, Microsoft 365 includes built-in features that help protect users from phishing attacks. Anti-phishing rules increase this protection by refining settings to better detect and prevent attacks. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Initial Access] |8.8.0 |206
 
-|<<potential-lsass-clone-creation-via-psscapturesnapshot, Potential LSASS Clone Creation via PssCaptureSnapShot>> |Identifies the creation of an LSASS process clone via PssCaptureSnapShot where the parent process is the initial LSASS process instance. This may indicate an attempt to evade detection and dump LSASS memory for credential access. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Sysmon Only]  |8.0.0 |101 <<potential-lsass-clone-creation-via-psscapturesnapshot-history, Version history>>
+|<<microsoft-365-exchange-dkim-signing-configuration-disabled, Microsoft 365 Exchange DKIM Signing Configuration Disabled>> |Identifies when a DomainKeys Identified Mail (DKIM) signing configuration is disabled in Microsoft 365. With DKIM in Microsoft 365, messages that are sent from Exchange Online will be cryptographically signed. This will allow the receiving email system to validate that the messages were generated by a server that the organization authorized and were not spoofed. |[Domain: Cloud], [Data Source: Microsoft 365], [Tactic: Persistence] |8.8.0 |206
 
-|<<potential-lsass-memory-dump-via-psscapturesnapshot, Potential LSASS Memory Dump via PssCaptureSnapShot>> |Identifies suspicious access to an LSASS handle via PssCaptureSnapShot where two successive process accesses are performed by the same process and target two different instances of LSASS. This may indicate an attempt to evade detection and dump LSASS memory for credential access. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Sysmon Only]  |8.0.0 |101 <<potential-lsass-memory-dump-via-psscapturesnapshot-history, Version history>>
+|<<microsoft-365-exchange-dlp-policy-removed, Microsoft 365 Exchange DLP Policy Removed>> |Identifies when a Data Loss Prevention (DLP) policy is removed in Microsoft 365. An adversary may remove a DLP policy to evade existing DLP monitoring. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.8.0 |206
 
-|<<potential-lateral-tool-transfer-via-smb-share, Potential Lateral Tool Transfer via SMB Share>> |Identifies the creation or change of a Windows executable file over network shares. Adversaries may transfer tools or other files between systems in a compromised environment. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement] [Investigation Guide]  |7.11.0 |102 <<potential-lateral-tool-transfer-via-smb-share-history, Version history>>
+|<<microsoft-365-exchange-malware-filter-policy-deletion, Microsoft 365 Exchange Malware Filter Policy Deletion>> |Identifies when a malware filter policy has been deleted in Microsoft 365. A malware filter policy is used to alert administrators that an internal user sent a message that contained malware. This may indicate an account or machine compromise that would need to be investigated. Deletion of a malware filter policy may be done to evade detection. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.8.0 |206
 
-|<<potential-linux-ssh-brute-force-detected, Potential Linux SSH Brute Force Detected>> |Identifies multiple consecutive login failures targeting an user account from the same source address and within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to accounts. |[Elastic] [Host] [Linux] [Threat Detection] [Credential Access]  |8.5.0 |1
+|<<microsoft-365-exchange-malware-filter-rule-modification, Microsoft 365 Exchange Malware Filter Rule Modification>> |Identifies when a malware filter rule has been deleted or disabled in Microsoft 365. An adversary or insider threat may want to modify a malware filter rule to evade detection. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.8.0 |206
 
-|<<potential-local-ntlm-relay-via-http, Potential Local NTLM Relay via HTTP>> |Identifies attempt to coerce a local NTLM authentication via HTTP using the Windows Printer Spooler service as a target. An adversary may use this primitive in combination with other techniques to elevate privileges on a compromised system. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Elastic Endgame]  |8.3.0 |102 <<potential-local-ntlm-relay-via-http-history, Version history>>
+|<<microsoft-365-exchange-management-group-role-assignment, Microsoft 365 Exchange Management Group Role Assignment>> |Identifies when a new role is assigned to a management group in Microsoft 365. An adversary may attempt to add a role in order to maintain persistence in an environment. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Identity and Access Audit], [Tactic: Persistence] |8.8.0 |206
 
-|<<potential-microsoft-office-sandbox-evasion, Potential Microsoft Office Sandbox Evasion>> |Identifies the creation of a suspicious zip file prepended with special characters. Sandboxed Microsoft Office applications on macOS are allowed to write files that start with special characters, which can be combined with an AutoStart location to achieve sandbox evasion. |[Elastic] [Host] [macOS] [Threat Detection] [Defense Evasion]  |7.12.0 |100 <<potential-microsoft-office-sandbox-evasion-history, Version history>>
+|<<microsoft-365-exchange-safe-attachment-rule-disabled, Microsoft 365 Exchange Safe Attachment Rule Disabled>> |Identifies when a safe attachment rule is disabled in Microsoft 365. Safe attachment rules can extend malware protections to include routing all messages and attachments without a known malware signature to a special hypervisor environment. An adversary or insider threat may disable a safe attachment rule to exfiltrate data or evade defenses. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Defense Evasion] |8.8.0 |206
 
-|<<potential-modification-of-accessibility-binaries, Potential Modification of Accessibility Binaries>> |Windows contains accessibility features that may be launched with a key combination before a user has logged in. An adversary can modify the way these programs are launched to get a command prompt or backdoor without logging in to the system. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.6.0 |102 <<potential-modification-of-accessibility-binaries-history, Version history>>
+|<<microsoft-365-exchange-safe-link-policy-disabled, Microsoft 365 Exchange Safe Link Policy Disabled>> |Identifies when a Safe Link policy is disabled in Microsoft 365. Safe Link policies for Office applications extend phishing protection to documents that contain hyperlinks, even after they have been delivered to a user. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Identity and Access Audit], [Tactic: Initial Access] |8.8.0 |206
 
-|<<potential-non-standard-port-ssh-connection, Potential Non-Standard Port SSH connection>> |Identifies potentially malicious processes communicating via a port paring typically not associated with SSH. For example, SSH over port 2200 or port 2222 as opposed to the traditional port 22. Adversaries may make changes to the standard port a protocol uses to bypass filtering or muddle analysis/parsing of network data. |[Elastic] [Host] [Linux] [Threat Detection] [Command and Control] [macOS]  |8.6.0 |1
+|<<microsoft-365-exchange-transport-rule-creation, Microsoft 365 Exchange Transport Rule Creation>> |Identifies a transport rule creation in Microsoft 365. As a best practice, Exchange Online mail transport rules should not be set to forward email to domains outside of your organization. An adversary may create transport rules to exfiltrate data. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Exfiltration] |8.8.0 |206
 
-|<<potential-openssh-backdoor-logging-activity, Potential OpenSSH Backdoor Logging Activity>> |Identifies a Secure Shell (SSH) client or server process creating or writing to a known SSH backdoor log file. Adversaries may modify SSH related binaries for persistence or credential access via patching sensitive functions to enable unauthorized access or to log SSH credentials for exfiltration. |[Elastic] [Host] [Linux] [Threat Detection] [Persistence] [Credential Access]  |7.12.0 |100 <<potential-openssh-backdoor-logging-activity-history, Version history>>
+|<<microsoft-365-exchange-transport-rule-modification, Microsoft 365 Exchange Transport Rule Modification>> |Identifies when a transport rule has been disabled or deleted in Microsoft 365. Mail flow rules (also known as transport rules) are used to identify and take action on messages that flow through your organization. An adversary or insider threat may modify a transport rule to exfiltrate data or evade defenses. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Exfiltration] |8.8.0 |206
 
-|<<potential-password-spraying-of-microsoft-365-user-accounts, Potential Password Spraying of Microsoft 365 User Accounts>> |Identifies a high number (25) of failed Microsoft 365 user authentication attempts from a single IP address within 30 minutes, which could be indicative of a password spraying attack. An adversary may attempt a password spraying attack to obtain unauthorized access to user accounts. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.11.0 |101 <<potential-password-spraying-of-microsoft-365-user-accounts-history, Version history>>
+|<<microsoft-365-global-administrator-role-assigned, Microsoft 365 Global Administrator Role Assigned>> |In Azure Active Directory (Azure AD), permissions to manage resources are assigned using roles. The Global Administrator is a role that enables users to have access to all administrative features in Azure AD and services that use Azure AD identities like the Microsoft 365 Defender portal, the Microsoft 365 compliance center, Exchange, SharePoint Online, and Skype for Business Online. Attackers can add users as Global Administrators to maintain access and manage all subscriptions and their settings and resources. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Identity and Access Audit], [Tactic: Persistence] |8.8.0 |206
 
-|<<potential-persistence-via-atom-init-script-modification, Potential Persistence via Atom Init Script Modification>> |Identifies modifications to the Atom desktop text editor Init File. Adversaries may add malicious JavaScript code to the init.coffee file that will be executed upon the Atom application opening. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<potential-persistence-via-atom-init-script-modification-history, Version history>>
+|<<microsoft-365-impossible-travel-activity, Microsoft 365 Impossible travel activity>> |Identifies when a Microsoft Cloud App Security reported a risky sign-in attempt due to a login associated with an impossible travel. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Initial Access] |None |1
 
-|<<potential-persistence-via-login-hook, Potential Persistence via Login Hook>> |Identifies the creation or modification of the login window property list (plist). Adversaries may modify plist files to run a program during system boot or user login for persistence. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |101 <<potential-persistence-via-login-hook-history, Version history>>
+|<<microsoft-365-inbox-forwarding-rule-created, Microsoft 365 Inbox Forwarding Rule Created>> |Identifies when a new Inbox forwarding rule is created in Microsoft 365. Inbox rules process messages in the Inbox based on conditions and take actions. In this case, the rules will forward the emails to a defined address. Attackers can abuse Inbox Rules to intercept and exfiltrate email data without making organization-wide configuration changes or having the corresponding privileges. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Collection] |8.8.0 |206
 
-|<<potential-persistence-via-periodic-tasks, Potential Persistence via Periodic Tasks>> |Identifies the creation or modification of the default configuration for periodic tasks. Adversaries may abuse periodic tasks to execute malicious code or maintain persistence. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<potential-persistence-via-periodic-tasks-history, Version history>>
+|<<microsoft-365-mass-download-by-a-single-user, Microsoft 365 Mass download by a single user>> |Identifies when Microsoft Cloud App Security reports that a single user performs more than 50 downloads within 1 minute. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Exfiltration] |None |1
 
-|<<potential-persistence-via-time-provider-modification, Potential Persistence via Time Provider Modification>> |Identifies modification of the Time Provider. Adversaries may establish persistence by registering and enabling a malicious DLL as a time provider. Windows uses the time provider architecture to obtain accurate time stamps from other network devices or clients in the network. Time providers are implemented in the form of a DLL file which resides in the System32 folder. The service W32Time initiates during the startup of Windows and loads w32time.dll. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.12.0 |100 <<potential-persistence-via-time-provider-modification-history, Version history>>
+|<<microsoft-365-potential-ransomware-activity, Microsoft 365 Potential ransomware activity>> |Identifies when Microsoft Cloud App Security reports that a user has uploaded files to the cloud that might be infected with ransomware. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Impact] |8.8.0 |206
 
-|<<potential-port-monitor-or-print-processor-registration-abuse, Potential Port Monitor or Print Processor Registration Abuse>> |Identifies port monitor and print processor registry modifications. Adversaries may abuse port monitor and print processors to run malicious DLLs during system boot that will be executed as SYSTEM for privilege escalation and/or persistence, if permissions allow writing a fully-qualified pathname for that DLL. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.12.0 |100 <<potential-port-monitor-or-print-processor-registration-abuse-history, Version history>>
+|<<microsoft-365-teams-custom-application-interaction-allowed, Microsoft 365 Teams Custom Application Interaction Allowed>> |Identifies when custom applications are allowed in Microsoft Teams. If an organization requires applications other than those available in the Teams app store, custom applications can be developed as packages and uploaded. An adversary may abuse this behavior to establish persistence in an environment. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Persistence] |8.8.0 |207
 
-|<<potential-privacy-control-bypass-via-localhost-secure-copy, Potential Privacy Control Bypass via Localhost Secure Copy>> |Identifies use of the Secure Copy Protocol (SCP) to copy files locally by abusing the auto addition of the Secure Shell Daemon (sshd) to the authorized application list for Full Disk Access. This may indicate attempts to bypass macOS privacy controls to access sensitive files. |[Elastic] [Host] [macOS] [Threat Detection] [Privilege Escalation] [Defense Evasion]  |7.12.0 |100 <<potential-privacy-control-bypass-via-localhost-secure-copy-history, Version history>>
+|<<microsoft-365-teams-external-access-enabled, Microsoft 365 Teams External Access Enabled>> |Identifies when external access is enabled in Microsoft Teams. External access lets Teams and Skype for Business users communicate with other users that are outside their organization. An adversary may enable external access or add an allowed domain to exfiltrate data or maintain persistence in an environment. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Persistence] |8.8.0 |206
 
-|<<potential-privacy-control-bypass-via-tccdb-modification, Potential Privacy Control Bypass via TCCDB Modification>> |Identifies the use of sqlite3 to directly modify the Transparency, Consent, and Control (TCC) SQLite database. This may indicate an attempt to bypass macOS privacy controls, including access to sensitive resources like the system camera, microphone, address book, and calendar. |[Elastic] [Host] [macOS] [Threat Detection] [Defense Evasion]  |7.12.0 |100 <<potential-privacy-control-bypass-via-tccdb-modification-history, Version history>>
+|<<microsoft-365-teams-guest-access-enabled, Microsoft 365 Teams Guest Access Enabled>> |Identifies when guest access is enabled in Microsoft Teams. Guest access in Teams allows people outside the organization to access teams and channels. An adversary may enable guest access to maintain persistence in an environment. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Persistence] |8.8.0 |206
 
-|<<potential-privilege-escalation-via-installerfiletakeover, Potential Privilege Escalation via InstallerFileTakeOver>> |Identifies a potential exploitation of InstallerTakeOver (CVE-2021-41379) default PoC execution. Successful exploitation allows an unprivileged user to escalate privileges to SYSTEM. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Investigation Guide]  |8.0.0 |102 <<potential-privilege-escalation-via-installerfiletakeover-history, Version history>>
+|<<microsoft-365-unusual-volume-of-file-deletion, Microsoft 365 Unusual Volume of File Deletion>> |Identifies that a user has deleted an unusually large volume of files as reported by Microsoft Cloud App Security. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Impact] |8.8.0 |206
 
-|<<potential-privilege-escalation-via-pkexec, Potential Privilege Escalation via PKEXEC>> |Identifies an attempt to exploit a local privilege escalation in polkit pkexec (CVE-2021-4034) via unsecure environment variable injection. Successful exploitation allows an unprivileged user to escalate to the root user. |[Elastic] [Host] [Linux] [Threat Detection] [Privilege Escalation]  |8.1.0 |100 <<potential-privilege-escalation-via-pkexec-history, Version history>>
+|<<microsoft-365-user-restricted-from-sending-email, Microsoft 365 User Restricted from Sending Email>> |Identifies when a user has been restricted from sending email due to exceeding sending limits of the service policies per the Security Compliance Center. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Initial Access] |8.8.0 |206
 
-|<<potential-privilege-escalation-via-sudoers-file-modification, Potential Privilege Escalation via Sudoers File Modification>> |A sudoers file specifies the commands users or groups can run and from which terminals. Adversaries can take advantage of these configurations to execute commands as other users or spawn processes with higher privileges. |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Privilege Escalation]  |7.12.0 |100 <<potential-privilege-escalation-via-sudoers-file-modification-history, Version history>>
+|<<microsoft-build-engine-started-an-unusual-process, Microsoft Build Engine Started an Unusual Process>> |An instance of MSBuild, the Microsoft Build Engine, started a PowerShell script or the Visual C# Command Line Compiler. This technique is sometimes used to deploy a malicious payload using the Build Engine. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Defend] |8.6.0 |211
 
-|<<potential-privileged-escalation-via-samaccountname-spoofing, Potential Privileged Escalation via SamAccountName Spoofing>> |Identifies a suspicious computer account name rename event, which may indicate an attempt to exploit CVE-2021-42278 to elevate privileges from a standard domain user to a user with domain admin privileges. CVE-2021-42278 is a security vulnerability that allows potential attackers to impersonate a domain controller via samAccountName attribute spoofing. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Privilege Escalation]  |8.1.0 |100 <<potential-privileged-escalation-via-samaccountname-spoofing-history, Version history>>
+|<<microsoft-build-engine-started-by-a-script-process, Microsoft Build Engine Started by a Script Process>> |An instance of MSBuild, the Microsoft Build Engine, was started by a script or the Windows command interpreter. This behavior is unusual and is sometimes used by malicious payloads. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Defend] |8.6.0 |209
 
-|<<potential-process-herpaderping-attempt, Potential Process Herpaderping Attempt>> |Identifies process execution followed by a file overwrite of an executable by the same parent process. This may indicate an evasion attempt to execute malicious code in a stealthy way. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.11.0 |101 <<potential-process-herpaderping-attempt-history, Version history>>
+|<<microsoft-build-engine-started-by-a-system-process, Microsoft Build Engine Started by a System Process>> |An instance of MSBuild, the Microsoft Build Engine, was started by Explorer or the WMI (Windows Management Instrumentation) subsystem. This behavior is unusual and is sometimes used by malicious payloads. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<potential-process-injection-via-powershell, Potential Process Injection via PowerShell>> |Detects the use of Windows API functions that are commonly abused by malware and security tools to load malicious code or inject it into remote processes. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide]  |8.0.0 |102 <<potential-process-injection-via-powershell-history, Version history>>
+|<<microsoft-build-engine-started-by-an-office-application, Microsoft Build Engine Started by an Office Application>> |An instance of MSBuild, the Microsoft Build Engine, was started by Excel or Word. This is unusual behavior for the Build Engine and could have been caused by an Excel or Word document executing a malicious script payload. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<potential-protocol-tunneling-via-earthworm, Potential Protocol Tunneling via EarthWorm>> |Identifies the execution of the EarthWorm tunneler. Adversaries may tunnel network communications to and from a victim system within a separate protocol to avoid detection and network filtering, or to enable access to otherwise unreachable systems. |[Elastic] [Host] [Linux] [Threat Detection] [Command and Control]  |7.13.0 |100 <<potential-protocol-tunneling-via-earthworm-history, Version history>>
+|<<microsoft-build-engine-using-an-alternate-name, Microsoft Build Engine Using an Alternate Name>> |An instance of MSBuild, the Microsoft Build Engine, was started after being renamed. This is uncommon behavior and may indicate an attempt to run unnoticed or undetected. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |112
 
-|<<potential-remote-credential-access-via-registry, Potential Remote Credential Access via Registry>> |Identifies remote access to the registry to potentially dump credential data from the Security Account Manager (SAM) registry hive in preparation for credential access and privileges elevation. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement] [Credential Access] [Investigation Guide]  |8.2.0 |102 <<potential-remote-credential-access-via-registry-history, Version history>>
+|<<microsoft-exchange-server-um-spawning-suspicious-processes, Microsoft Exchange Server UM Spawning Suspicious Processes>> |Identifies suspicious processes being spawned by the Microsoft Exchange Server Unified Messaging (UM) service. This activity has been observed exploiting CVE-2021-26857. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Lateral Movement], [Data Source: Elastic Endgame], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<potential-remote-desktop-shadowing-activity, Potential Remote Desktop Shadowing Activity>> |Identifies the modification of the Remote Desktop Protocol (RDP) Shadow registry or the execution of processes indicative of an active RDP shadowing session. An adversary may abuse the RDP Shadowing feature to spy on or control other users active RDP sessions. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.13.0 |100 <<potential-remote-desktop-shadowing-activity-history, Version history>>
+|<<microsoft-exchange-server-um-writing-suspicious-files, Microsoft Exchange Server UM Writing Suspicious Files>> |Identifies suspicious files being written by the Microsoft Exchange Server Unified Messaging (UM) service. This activity has been observed exploiting CVE-2021-26858. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Lateral Movement], [Data Source: Elastic Endgame], [Use Case: Vulnerability], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<potential-remote-desktop-tunneling-detected, Potential Remote Desktop Tunneling Detected>> |Identifies potential use of an SSH utility to establish RDP over a reverse SSH Tunnel. This can be used by attackers to enable routing of network packets that would otherwise not reach their intended destination. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<potential-remote-desktop-tunneling-detected-history, Version history>>
+|<<microsoft-exchange-transport-agent-install-script, Microsoft Exchange Transport Agent Install Script>> |Identifies the use of Cmdlets and methods related to Microsoft Exchange Transport Agents install. Adversaries may leverage malicious Microsoft Exchange Transport Agents to execute tasks in response to adversary-defined criteria, establishing persistence. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: PowerShell Logs], [Rule Type: BBR] |8.3.0 |5
 
-|<<potential-reverse-shell-activity-via-terminal, Potential Reverse Shell Activity via Terminal>> |Identifies the execution of a shell process with suspicious arguments which may be indicative of reverse shell activity. |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Execution] [Investigation Guide]  |7.12.0 |102 <<potential-reverse-shell-activity-via-terminal-history, Version history>>
+|<<microsoft-exchange-worker-spawning-suspicious-processes, Microsoft Exchange Worker Spawning Suspicious Processes>> |Identifies suspicious processes being spawned by the Microsoft Exchange Server worker process (w3wp). This activity may indicate exploitation activity or access to an existing web shell backdoor. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<potential-ssh-brute-force-detected-on-privileged-account, Potential SSH Brute Force Detected on Privileged Account>> |Identifies multiple consecutive login failures targeting a root user account from the same source address and within a short time interval. Adversaries will often brute force login attempts on privileged accounts with a common or known password, in an attempt to gain privileged access to systems. |[Elastic] [Host] [Linux] [Threat Detection] [Credential Access]  |8.5.0 |1
+|<<microsoft-iis-connection-strings-decryption, Microsoft IIS Connection Strings Decryption>> |Identifies use of aspnet_regiis to decrypt Microsoft IIS connection strings. An attacker with Microsoft IIS web server access via a webshell or alike can decrypt and dump any hardcoded connection strings, such as the MSSQL service account password using aspnet_regiis command. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<potential-ssh-password-guessing, Potential SSH Password Guessing>> |Identifies multiple SSH login failures followed by a successful one from the same source address. Adversaries can attempt to login into multiple users with a common or known password to gain access to accounts. |[Elastic] [Host] [Linux] [Threat Detection] [Credential Access]  |8.5.0 |1
+|<<microsoft-iis-service-account-password-dumped, Microsoft IIS Service Account Password Dumped>> |Identifies the Internet Information Services (IIS) command-line tool, AppCmd, being used to list passwords. An attacker with IIS web server access via a web shell can decrypt and dump the IIS AppPool service account password using AppCmd. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<potential-secure-file-deletion-via-sdelete-utility, Potential Secure File Deletion via SDelete Utility>> |Detects file name patterns generated by the use of Sysinternals SDelete utility to securely delete a file via multiple file overwrite and rename operations. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.10.0 |101 <<potential-secure-file-deletion-via-sdelete-utility-history, Version history>>
+|<<microsoft-windows-defender-tampering, Microsoft Windows Defender Tampering>> |Identifies when one or more features on Microsoft Defender are disabled. Adversaries may disable or tamper with Microsoft Defender features to evade detection and conceal malicious behavior. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
 
-|<<potential-shadow-credentials-added-to-ad-object, Potential Shadow Credentials added to AD Object>> |Identify the modification of the msDS-KeyCredentialLink attribute in an Active Directory Computer or User Object. Attackers can abuse control over the object and create a key pair, append to raw public key in the attribute, and obtain persistent and stealthy access to the target user or computer object. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Active Directory]  |8.1.0 |101 <<potential-shadow-credentials-added-to-ad-object-history, Version history>>
+|<<mimikatz-memssp-log-file-detected, Mimikatz Memssp Log File Detected>> |Identifies the password log file from the default Mimikatz memssp module. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<potential-shadow-file-read-via-command-line-utilities, Potential Shadow File Read via Command Line Utilities>> |Identifies access to the /etc/shadow file via the commandline using standard system utilities. After elevating privileges to root, threat actors may attempt to read or dump this file in order to gain valid credentials. They may utilize these to move laterally undetected and access additional resources. |[Elastic] [Host] [Linux] [Threat Detection] [Privilege Escalation] [Credential Access]  |8.5.0 |2 <<potential-shadow-file-read-via-command-line-utilities-history, Version history>>
+|<<modification-of-amsienable-registry-key, Modification of AmsiEnable Registry Key>> |Identifies modifications of the AmsiEnable registry key to 0, which disables the Antimalware Scan Interface (AMSI). An adversary can modify this key to disable AMSI protections. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
 
-|<<potential-sharprdp-behavior, Potential SharpRDP Behavior>> |Identifies potential behavior of SharpRDP, which is a tool that can be used to perform authenticated command execution against a remote target via Remote Desktop Protocol (RDP) for the purposes of lateral movement. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.11.0 |101 <<potential-sharprdp-behavior-history, Version history>>
+|<<modification-of-boot-configuration, Modification of Boot Configuration>> |Identifies use of bcdedit.exe to delete boot configuration data. This tactic is sometimes used as by malware or an attacker as a destructive technique. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Impact], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<potential-shell-via-web-server, Potential Shell via Web Server>> |Identifies suspicious commands executed via a web server, which may suggest a vulnerability and remote shell access. |[Elastic] [Host] [Linux] [Threat Detection] [Persistence] [Investigation Guide]  |7.6.0 |102 <<potential-shell-via-web-server-history, Version history>>
+|<<modification-of-dynamic-linker-preload-shared-object, Modification of Dynamic Linker Preload Shared Object>> |Identifies modification of the dynamic linker preload shared object (ld.so.preload). Adversaries may execute malicious payloads by hijacking the dynamic linker used to load libraries. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.6.0 |209
 
-|<<potential-windows-error-manager-masquerading, Potential Windows Error Manager Masquerading>> |Identifies suspicious instances of the Windows Error Reporting process (WerFault.exe or Wermgr.exe) with matching command-line and process executable values performing outgoing network connections. This may be indicative of a masquerading attempt to evade suspicious child process behavior detections. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.10.0 |100 <<potential-windows-error-manager-masquerading-history, Version history>>
+|<<modification-of-dynamic-linker-preload-shared-object-inside-a-container, Modification of Dynamic Linker Preload Shared Object Inside A Container>> |This rule detects the creation or modification of the dynamic linker preload shared object (ld.so.preload) inside a container. The Linux dynamic linker is used to load libraries needed by a program at runtime. Adversaries may hijack the dynamic linker by modifying the /etc/ld.so.preload file to point to malicious libraries. This behavior can be used to grant unauthorized access to system resources and has been used to evade detection of malicious processes in container environments. |[Data Source: Elastic Defend for Containers], [Domain: Container], [Tactic: Defense Evasion] |8.8.0 |1
 
-|<<potential-macos-ssh-brute-force-detected, Potential macOS SSH Brute Force Detected>> |Identifies a high number (20) of macOS SSH KeyGen process executions from the same host. An adversary may attempt a brute force attack to obtain unauthorized access to user accounts. |[Elastic] [Host] [macOS] [Threat Detection] [Credential Access]  |7.11.0 |101 <<potential-macos-ssh-brute-force-detected-history, Version history>>
+|<<modification-of-environment-variable-via-unsigned-or-untrusted-parent, Modification of Environment Variable via Unsigned or Untrusted Parent>> |Identifies modifications to an environment variable using the built-in launchctl command. Adversaries may execute their own malicious payloads by hijacking certain environment variables to load arbitrary libraries or bypass certain restrictions. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.11.0 |206
 
-|<<powershell-kerberos-ticket-request, PowerShell Kerberos Ticket Request>> |Detects PowerShell scripts that have the capability of requesting kerberos tickets, which is a common step in Kerberoasting toolkits to crack service accounts. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide]  |8.1.0 |102 <<powershell-kerberos-ticket-request-history, Version history>>
+|<<modification-of-openssh-binaries, Modification of OpenSSH Binaries>> |Adversaries may modify SSH related binaries for persistence or credential access by patching sensitive functions to enable unauthorized access or by logging SSH credentials for exfiltration. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Persistence], [Tactic: Lateral Movement], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<powershell-keylogging-script, PowerShell Keylogging Script>> |Detects the use of Win32 API Functions that can be used to capture user keystrokes in PowerShell scripts. Attackers use this technique to capture user input, looking for credentials and/or other valuable data. |[Elastic] [Host] [Windows] [Threat Detection] [Collection] [Investigation Guide]  |8.0.0 |102 <<powershell-keylogging-script-history, Version history>>
+|<<modification-of-safari-settings-via-defaults-command, Modification of Safari Settings via Defaults Command>> |Identifies changes to the Safari configuration using the built-in defaults command. Adversaries may attempt to enable or disable certain Safari settings, such as enabling JavaScript from Apple Events to ease in the hijacking of the users browser. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<powershell-minidump-script, PowerShell MiniDump Script>> |This rule detects PowerShell scripts capable of dumping process memory using WindowsErrorReporting or Dbghelp.dll MiniDumpWriteDump. Attackers can use this tooling to dump LSASS and get access to credentials. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide]  |7.16.0 |102 <<powershell-minidump-script-history, Version history>>
+|<<modification-of-standard-authentication-module-or-configuration, Modification of Standard Authentication Module or Configuration>> |Adversaries may modify the standard authentication module for persistence via patching the normal authorization process or modifying the login configuration to allow unauthorized access or elevate privileges. |[Domain: Endpoint], [OS: macOS], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Persistence], [Data Source: Elastic Defend] |8.6.0 |204
 
-|<<powershell-psreflect-script, PowerShell PSReflect Script>> |Detects the use of PSReflect in PowerShell scripts. Attackers leverage PSReflect as a library that enables PowerShell to access win32 API functions. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Investigation Guide]  |8.0.0 |102 <<powershell-psreflect-script-history, Version history>>
+|<<modification-of-wdigest-security-provider, Modification of WDigest Security Provider>> |Identifies attempts to modify the WDigest security provider in the registry to force the user's password to be stored in clear text in memory. This behavior can be indicative of an adversary attempting to weaken the security configuration of an endpoint. Once the UseLogonCredential value is modified, the adversary may attempt to dump clear text passwords from memory. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<powershell-script-block-logging-disabled, PowerShell Script Block Logging Disabled>> |Identifies attempts to disable PowerShell Script Block Logging via registry modification. Attackers may disable this logging to conceal their activities in the host and evade detection. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |8.1.0 |102 <<powershell-script-block-logging-disabled-history, Version history>>
+|<<modification-of-the-mspkiaccountcredentials, Modification of the msPKIAccountCredentials>> |Identify the modification of the msPKIAccountCredentials attribute in an Active Directory User Object. Attackers can abuse the credentials roaming feature to overwrite an arbitrary file for privilege escalation. ms-PKI-AccountCredentials contains binary large objects (BLOBs) of encrypted credential objects from the credential manager store, private keys, certificates, and certificate requests. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Data Source: Active Directory], [Tactic: Privilege Escalation], [Use Case: Active Directory Monitoring] |8.3.0 |9
 
-|<<powershell-script-with-token-impersonation-capabilities, PowerShell Script with Token Impersonation Capabilities>> |Detects scripts that contain PowerShell functions, structures, or Windows API functions related to token impersonation/theft. Attackers may duplicate then impersonate another user's token to escalate privileges and bypass access controls. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |8.5.0 |1
+|<<modification-or-removal-of-an-okta-application-sign-on-policy, Modification or Removal of an Okta Application Sign-On Policy>> |Detects attempts to modify or delete a sign on policy for an Okta application. An adversary may attempt to modify or delete the sign on policy for an Okta application in order to remove or weaken an organization's security controls. |[Tactic: Persistence], [Use Case: Identity and Access Audit], [Data Source: Okta] |8.10.0 |206
 
-|<<powershell-share-enumeration-script, PowerShell Share Enumeration Script>> |Detects scripts that contain PowerShell functions, structures, or Windows API functions related to windows share enumeration activities. Attackers, mainly ransomware groups, commonly identify and inspect network shares, looking for critical information for encryption and/or exfiltration. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide]  |8.5.0 |2 <<powershell-share-enumeration-script-history, Version history>>
+|<<mofcomp-activity, Mofcomp Activity>> |Managed Object Format (MOF) files can be compiled locally or remotely through mofcomp.exe. Attackers may leverage MOF files to build their own namespaces and classes into the Windows Management Instrumentation (WMI) repository, or establish persistence using WMI Event Subscription. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<powershell-suspicious-discovery-related-windows-api-functions, PowerShell Suspicious Discovery Related Windows API Functions>> |This rule detects the use of discovery-related Windows API functions in PowerShell Scripts. Attackers can use these functions to perform various situational awareness related activities, like enumerating users, shares, sessions, domain trusts, groups, etc. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide]  |7.16.0 |102 <<powershell-suspicious-discovery-related-windows-api-functions-history, Version history>>
+|<<mount-launched-inside-a-privileged-container, Mount Launched Inside a Privileged Container>> |This rule detects the use of the mount utility from inside a privileged container. The mount command is used to make a device or file system accessible to the system, and then to connect its root directory to a specified mount point on the local file system. When launched inside a privileged container--a container deployed with all the capabilities of the host machine-- an attacker can access sensitive host level files which could be used for further privilege escalation and container escapes to the host machine. Any usage of mount inside a running privileged container should be further investigated. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.10.0 |1
 
-|<<powershell-suspicious-payload-encoded-and-compressed, PowerShell Suspicious Payload Encoded and Compressed>> |Identifies the use of .NET functionality for decompression and base64 decoding combined in PowerShell scripts, which malware and security tools heavily use to deobfuscate payloads and load them directly in memory to bypass defenses. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide]  |8.0.0 |102 <<powershell-suspicious-payload-encoded-and-compressed-history, Version history>>
+|<<mounting-hidden-or-webdav-remote-shares, Mounting Hidden or WebDav Remote Shares>> |Identifies the use of net.exe to mount a WebDav or hidden remote share. This may indicate lateral movement or preparation for data exfiltration. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Lateral Movement], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<powershell-suspicious-script-with-audio-capture-capabilities, PowerShell Suspicious Script with Audio Capture Capabilities>> |Detects PowerShell scripts that can record audio, a common feature in popular post-exploitation tooling. |[Elastic] [Host] [Windows] [Threat Detection] [Collection] [Investigation Guide]  |7.16.0 |102 <<powershell-suspicious-script-with-audio-capture-capabilities-history, Version history>>
+|<<msbuild-making-network-connections, MsBuild Making Network Connections>> |Identifies MsBuild.exe making outbound network connections. This may indicate adversarial activity as MsBuild is often leveraged by adversaries to execute code and evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<powershell-suspicious-script-with-screenshot-capabilities, PowerShell Suspicious Script with Screenshot Capabilities>> |Detects PowerShell scripts that can take screenshots, which is a common feature in post-exploitation kits and remote access tools (RATs). |[Elastic] [Host] [Windows] [Threat Detection] [Collection] [Investigation Guide]  |8.0.0 |102 <<powershell-suspicious-script-with-screenshot-capabilities-history, Version history>>
+|<<mshta-making-network-connections, Mshta Making Network Connections>> |Identifies Mshta.exe making outbound network connections. This may indicate adversarial activity, as Mshta is often leveraged by adversaries to execute malicious scripts and evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
 
-|<<privilege-escalation-via-named-pipe-impersonation, Privilege Escalation via Named Pipe Impersonation>> |Identifies a privilege escalation attempt via named pipe impersonation. An adversary may abuse this technique by utilizing a framework such Metasploit's meterpreter getsystem command. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.11.0 |101 <<privilege-escalation-via-named-pipe-impersonation-history, Version history>>
+|<<multi-factor-authentication-disabled-for-an-azure-user, Multi-Factor Authentication Disabled for an Azure User>> |Identifies when multi-factor authentication (MFA) is disabled for an Azure user account. An adversary may disable MFA for a user account in order to weaken the authentication requirements for the account. |[Domain: Cloud], [Data Source: Azure], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Persistence] |8.3.0 |105
 
-|<<privilege-escalation-via-rogue-named-pipe-impersonation, Privilege Escalation via Rogue Named Pipe Impersonation>> |Identifies a privilege escalation attempt via rogue named pipe impersonation. An adversary may abuse this technique by masquerading as a known named pipe and manipulating a privileged process to connect to it. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Sysmon Only]  |8.0.0 |101 <<privilege-escalation-via-rogue-named-pipe-impersonation-history, Version history>>
+|<<multiple-alerts-involving-a-user, Multiple Alerts Involving a User>> |This rule uses alert data to determine when multiple different alerts involving the same user are triggered. Analysts can use this to prioritize triage and response, as these users are more likely to be compromised. |[Use Case: Threat Detection], [Rule Type: Higher-Order Rule] |8.3.0 |3
 
-|<<privilege-escalation-via-root-crontab-file-modification, Privilege Escalation via Root Crontab File Modification>> |Identifies modifications to the root crontab file. Adversaries may overwrite this file to gain code execution with root privileges by exploiting privileged file write or move related vulnerabilities. |[Elastic] [Host] [macOS] [Threat Detection] [Privilege Escalation]  |7.12.0 |100 <<privilege-escalation-via-root-crontab-file-modification-history, Version history>>
+|<<multiple-alerts-in-different-att-ck-tactics-on-a-single-host, Multiple Alerts in Different ATT&CK Tactics on a Single Host>> |This rule uses alert data to determine when multiple alerts in different phases of an attack involving the same host are triggered. Analysts can use this to prioritize triage and response, as these hosts are more likely to be compromised. |[Use Case: Threat Detection], [Rule Type: Higher-Order Rule] |8.3.0 |4
 
-|<<privilege-escalation-via-windir-environment-variable, Privilege Escalation via Windir Environment Variable>> |Identifies a privilege escalation attempt via a rogue Windows directory (Windir) environment variable. This is a known primitive that is often combined with other vulnerabilities to elevate privileges. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.11.0 |100 <<privilege-escalation-via-windir-environment-variable-history, Version history>>
+|<<multiple-logon-failure-followed-by-logon-success, Multiple Logon Failure Followed by Logon Success>> |Identifies multiple logon failures followed by a successful one from the same source address. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to accounts. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide] |8.3.0 |10
 
-|<<privileged-account-brute-force, Privileged Account Brute Force>> |Identifies multiple consecutive logon failures targeting an Admin account from the same source address and within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to accounts. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access]  |8.5.0 |1
+|<<multiple-logon-failure-from-the-same-source-address, Multiple Logon Failure from the same Source Address>> |Identifies multiple consecutive logon failures from the same source address and within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to accounts. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide] |8.3.0 |9
 
-|<<privileges-elevation-via-parent-process-pid-spoofing, Privileges Elevation via Parent Process PID Spoofing>> |Identifies parent process spoofing used to create an elevated child process. Adversaries may spoof the parent process identifier (PPID) of a new process to evade process-monitoring defenses or to elevate privileges. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |8.6.0 |1
+|<<multiple-okta-client-addresses-for-a-single-user-session, Multiple Okta Client Addresses for a Single User Session>> |Detects when a user has started multiple Okta sessions with the same user account and different session IDs. This may indicate an attacker has compromised a user's Okta account and is using it to access the organization's resources. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Initial Access] |8.10.0 |2
 
-|<<process-activity-via-compiled-html-file, Process Activity via Compiled HTML File>> |Compiled HTML files (.chm) are commonly distributed as part of the Microsoft HTML Help system. Adversaries may conceal malicious code in a CHM file and deliver it to a victim for execution. CHM content is loaded by the HTML Help executable program (hh.exe). |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Elastic Endgame]  |7.6.0 |102 <<process-activity-via-compiled-html-file-history, Version history>>
+|<<multiple-okta-sessions-detected-for-a-single-user, Multiple Okta Sessions Detected for a Single User>> |Detects when a user has started multiple Okta sessions with the same user account and different session IDs. This may indicate that an attacker has stolen the user's session cookie and is using it to access the user's account from a different location. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Lateral Movement] |8.10.0 |1
 
-|<<process-created-with-an-elevated-token, Process Created with an Elevated Token>> |Identifies the creation of a process running as SYSTEM and impersonating a Windows core binary privileges. Adversaries may create a new process with a different token to escalate privileges and bypass access controls. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |8.6.0 |1
+|<<multiple-okta-user-auth-events-with-same-device-token-hash-behind-a-proxy, Multiple Okta User Auth Events with Same Device Token Hash Behind a Proxy>> |Detects when Okta user authentication events are reported for multiple users with the same device token hash behind a proxy. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Credential Access] |8.10.0 |2
 
-|<<process-creation-via-secondary-logon, Process Creation via Secondary Logon>> |Identifies process creation with alternate credentials. Adversaries may create a new process with a different token to escalate privileges and bypass access controls. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |8.5.0 |2 <<process-creation-via-secondary-logon-history, Version history>>
+|<<multiple-vault-web-credentials-read, Multiple Vault Web Credentials Read>> |Windows Credential Manager allows you to create, view, or delete saved credentials for signing into websites, connected applications, and networks. An adversary may abuse this to list or dump credentials stored in the Credential Manager for saved usernames and passwords. This may also be performed in preparation of lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access] |8.3.0 |10
 
-|<<process-execution-from-an-unusual-directory, Process Execution from an Unusual Directory>> |Identifies process execution from suspicious default Windows directories. This is sometimes done by adversaries to hide malware in trusted paths. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.11.0 |102 <<process-execution-from-an-unusual-directory-history, Version history>>
+|<<my-first-rule, My First Rule>> |This rule helps you test and practice using alerts with Elastic Security as you get set up. It’s not a sign of threat activity. |[Use Case: Guided Onboarding] |8.7.0 |3
 
-|<<process-injection-detected-elastic-endgame, Process Injection - Detected - Elastic Endgame>> |Elastic Endgame detected Process Injection. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame] [Threat Detection] [Privilege Escalation]  |7.6.0 |100 <<process-injection-detected-elastic-endgame-history, Version history>>
+|<<ntds-or-sam-database-file-copied, NTDS or SAM Database File Copied>> |Identifies a copy operation of the Active Directory Domain Database (ntds.dit) or Security Account Manager (SAM) files. Those files contain sensitive information including hashed domain and/or local credentials. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
 
-|<<process-injection-prevented-elastic-endgame, Process Injection - Prevented - Elastic Endgame>> |Elastic Endgame prevented Process Injection. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame] [Threat Detection] [Privilege Escalation]  |7.6.0 |100 <<process-injection-prevented-elastic-endgame-history, Version history>>
+|<<namespace-manipulation-using-unshare, Namespace Manipulation Using Unshare>> |Identifies suspicious usage of unshare to manipulate system namespaces. Unshare can be utilized to escalate privileges or escape container security boundaries. Threat actors have utilized this binary to allow themselves to escape to the host and access other resources or escalate privileges. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |9
 
-|<<process-injection-by-the-microsoft-build-engine, Process Injection by the Microsoft Build Engine>> |An instance of MSBuild, the Microsoft Build Engine, created a thread in another process. This technique is sometimes used to evade detection or elevate privileges. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Sysmon Only]  |7.7.0 |101 <<process-injection-by-the-microsoft-build-engine-history, Version history>>
+|<<netcat-listener-established-inside-a-container, Netcat Listener Established Inside A Container>> |This rule detects an established netcat listener running inside a container. Netcat is a utility used for reading and writing data across network connections, and it can be used for malicious purposes such as establishing a backdoor for persistence or exfiltrating data. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution] |8.8.0 |2
 
-|<<process-started-from-process-id-pid-file, Process Started from Process ID (PID) File>> |Identifies a new process starting from a process ID (PID), lock or reboot file within the temporary file storage paradigm (tmpfs) directory /var/run directory. On Linux, the PID files typically hold the process ID to track previous copies running and manage other tasks. Certain Linux malware use the /var/run directory for holding data, executables and other tasks, disguising itself or these files as legitimate PID files. |[Elastic] [Host] [Linux] [Threat Detection] [Execution] [BPFDoor]  |8.3.0 |101 <<process-started-from-process-id-pid-file-history, Version history>>
+|<<netcat-listener-established-via-rlwrap, Netcat Listener Established via rlwrap>> |Monitors for the execution of a netcat listener via rlwrap. rlwrap is a 'readline wrapper', a small utility that uses the GNU Readline library to allow the editing of keyboard input for any command. This utility can be used in conjunction with netcat to gain a more stable reverse shell. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |3
 
-|<<process-termination-followed-by-deletion, Process Termination followed by Deletion>> |Identifies a process termination event quickly followed by the deletion of its executable file. Malware tools and other non-native files dropped or created on a system by an adversary may leave traces to indicate to what occurred. Removal of these files can occur during an intrusion, or as part of a post-intrusion process to minimize the adversary's footprint. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.11.0 |101 <<process-termination-followed-by-deletion-history, Version history>>
+|<<netsh-helper-dll, Netsh Helper DLL>> |Identifies the addition of a Netsh Helper DLL, netsh.exe supports the addition of these DLLs to extend its functionality. Attackers may abuse this mechanism to execute malicious payloads every time the utility is executed, which can be done by administrators or a scheduled task. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<program-files-directory-masquerading, Program Files Directory Masquerading>> |Identifies execution from a directory masquerading as the Windows Program Files directories. These paths are trusted and usually host trusted third party programs. An adversary may leverage masquerading, along with low privileges to bypass detections allowlisting those folders. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.11.0 |101 <<program-files-directory-masquerading-history, Version history>>
+|<<network-activity-detected-via-kworker, Network Activity Detected via Kworker>> |This rule monitors for network connections from a kworker process. kworker, or kernel worker, processes are part of the kernel's workqueue mechanism. They are responsible for executing work that has been scheduled to be done in kernel space, which might include tasks like handling interrupts, background activities, and other kernel-related tasks. Attackers may attempt to evade detection by masquerading as a kernel worker process. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Defend] |8.6.0 |4
 
-|<<prompt-for-credentials-with-osascript, Prompt for Credentials with OSASCRIPT>> |Identifies the use of osascript to execute scripts via standard input that may prompt a user with a rogue dialog for credentials. |[Elastic] [Host] [macOS] [Threat Detection] [Credential Access]  |7.11.0 |100 <<prompt-for-credentials-with-osascript-history, Version history>>
+|<<network-activity-detected-via-cat, Network Activity Detected via cat>> |This rule monitors for the execution of the cat command, followed by a connection attempt by the same process. Cat is capable of transfering data via tcp/udp channels by redirecting its read output to a /dev/tcp or /dev/udp channel. This activity is highly suspicious, and should be investigated. Attackers may leverage this capability to transfer tools or files to another host in the network or exfiltrate data while attempting to evade detection in the process. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Defend] |8.3.0 |6
 
-|<<psexec-network-connection, PsExec Network Connection>> |Identifies use of the SysInternals tool PsExec.exe making a network connection. This could be an indication of lateral movement. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Investigation Guide]  |7.6.0 |102 <<psexec-network-connection-history, Version history>>
+|<<network-connection-from-binary-with-rwx-memory-region, Network Connection from Binary with RWX Memory Region>> |Monitors for the execution of a unix binary with read, write and execute memory region permissions, followed by a network connection. The mprotect() system call is used to change the access protections on a region of memory that has already been allocated. This syscall allows a process to modify the permissions of pages in its virtual address space, enabling or disabling permissions such as read, write, and execute for those pages. RWX permissions on memory is in many cases overly permissive, and should (especially in conjunction with an outbound network connection) be analyzed thoroughly. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.6.0 |1
 
-|<<rdp-remote-desktop-protocol-from-the-internet, RDP (Remote Desktop Protocol) from the Internet>> |This rule detects network events that may indicate the use of RDP traffic from the Internet. RDP is commonly used by system administrators to remotely control a system for maintenance or to use shared resources. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. |[Elastic] [Host] [Network] [Threat Detection] [Command and Control] [Host]  |7.6.0 |100 <<rdp-remote-desktop-protocol-from-the-internet-history, Version history>>
+|<<network-connection-via-certutil, Network Connection via Certutil>> |Identifies certutil.exe making a network connection. Adversaries could abuse certutil.exe to download a certificate, or malware, from a remote URL. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
 
-|<<rdp-enabled-via-registry, RDP Enabled via Registry>> |Identifies registry write modifications to enable Remote Desktop Protocol (RDP) access. This could be indicative of adversary lateral movement preparation. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement] [Investigation Guide]  |7.11.0 |102 <<rdp-enabled-via-registry-history, Version history>>
+|<<network-connection-via-compiled-html-file, Network Connection via Compiled HTML File>> |Compiled HTML files (.chm) are commonly distributed as part of the Microsoft HTML Help system. Adversaries may conceal malicious code in a CHM file and deliver it to a victim for execution. CHM content is loaded by the HTML Help executable program (hh.exe). |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<rpc-remote-procedure-call-from-the-internet, RPC (Remote Procedure Call) from the Internet>> |This rule detects network events that may indicate the use of RPC traffic from the Internet. RPC is commonly used by system administrators to remotely control a system for maintenance or to use shared resources. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. |[Elastic] [Host] [Network] [Threat Detection] [Initial Access] [Host]  |7.6.0 |100 <<rpc-remote-procedure-call-from-the-internet-history, Version history>>
+|<<network-connection-via-msxsl, Network Connection via MsXsl>> |Identifies msxsl.exe making a network connection. This may indicate adversarial activity as msxsl.exe is often leveraged by adversaries to execute malicious scripts and evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |106
 
-|<<rpc-remote-procedure-call-to-the-internet, RPC (Remote Procedure Call) to the Internet>> |This rule detects network events that may indicate the use of RPC traffic to the Internet. RPC is commonly used by system administrators to remotely control a system for maintenance or to use shared resources. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. |[Elastic] [Host] [Network] [Threat Detection] [Initial Access] [Host]  |7.6.0 |100 <<rpc-remote-procedure-call-to-the-internet-history, Version history>>
+|<<network-connection-via-recently-compiled-executable, Network Connection via Recently Compiled Executable>> |This rule monitors a sequence involving a program compilation event followed by its execution and a subsequent network connection event. This behavior can indicate the set up of a reverse tcp connection to a command-and-control server. Attackers may spawn reverse shells to establish persistence onto a target system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |5
 
-|<<ransomware-detected-elastic-endgame, Ransomware - Detected - Elastic Endgame>> |Elastic Endgame detected ransomware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame]  |7.6.0 |100 <<ransomware-detected-elastic-endgame-history, Version history>>
+|<<network-connection-via-registration-utility, Network Connection via Registration Utility>> |Identifies the native Windows tools regsvr32.exe, regsvr64.exe, RegSvcs.exe, or RegAsm.exe making a network connection. This may be indicative of an attacker bypassing allowlists or running arbitrary scripts via a signed Microsoft binary. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<ransomware-prevented-elastic-endgame, Ransomware - Prevented - Elastic Endgame>> |Elastic Endgame prevented ransomware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Elastic] [Elastic Endgame]  |7.6.0 |100 <<ransomware-prevented-elastic-endgame-history, Version history>>
+|<<network-connection-via-signed-binary, Network Connection via Signed Binary>> |Binaries signed with trusted digital certificates can execute on Windows systems protected by digital signature validation. Adversaries may use these binaries to 'live off the land' and execute malicious files that could bypass application allowlists and signature validation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<rare-aws-error-code, Rare AWS Error Code>> |A machine learning job detected an unusual error in a CloudTrail message. These can be byproducts of attempted or successful persistence, privilege escalation, defense evasion, discovery, lateral movement, or collection. |[Elastic] [Cloud] [AWS] [ML] [Investigation Guide]  |7.9.0 |102 <<rare-aws-error-code-history, Version history>>
+|<<network-logon-provider-registry-modification, Network Logon Provider Registry Modification>> |Identifies the modification of the network logon provider registry. Adversaries may register a rogue network logon provider module for persistence and/or credential access via intercepting the authentication credentials in clear text during user logon. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<rare-user-logon, Rare User Logon>> |A machine learning job found an unusual user name in the authentication logs. An unusual user name is one way of detecting credentialed access by means of a new or dormant user account. An inactive user account (because the user has left the organization) that becomes active may be due to credentialed access using a compromised account password. Threat actors will sometimes also create new users as a means of persisting in a compromised web application. |[Elastic] [Authentication] [Threat Detection] [ML] [Initial Access]  |7.14.0 |100 <<rare-user-logon-history, Version history>>
+|<<network-traffic-capture-via-cap-net-raw, Network Traffic Capture via CAP_NET_RAW>> |Identifies the ability of a process to be able to create RAW and PACKET socket types for the available network namespaces by a non-root user. A malicious process with this capability may exploit routing between hosts, bypass network access controls, and otherwise tamper with host networking if a firewall is not in place to limit the packet types and contents. The CAP_NET_RAW capability allows the process to bind to any address within the available namespaces, which allows network traffic sniffing by a non root user. The rule identifies previously unknown processes executing with CAP_NET_RAW capabilities through the use of the new terms rule type. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend] |8.11.0 |2
 
-|<<registry-persistence-via-appcert-dll, Registry Persistence via AppCert DLL>> |Detects attempts to maintain persistence by creating registry keys using AppCert DLLs. AppCert DLLs are loaded by every process using the common API functions to create processes. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<registry-persistence-via-appcert-dll-history, Version history>>
+|<<network-traffic-to-rare-destination-country, Network Traffic to Rare Destination Country>> |A machine learning job detected a rare destination country name in the network logs. This can be due to initial access, persistence, command-and-control, or exfiltration activity. For example, when a user clicks on a link in a phishing email or opens a malicious document, a request may be sent to download and run a payload from a server in a country which does not normally appear in network traffic or business work-flows. Malware instances and persistence mechanisms may communicate with command-and-control (C2) infrastructure in their country of origin, which may be an unusual destination country for the source network. |[Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning] |8.3.0 |103
 
-|<<registry-persistence-via-appinit-dll, Registry Persistence via AppInit DLL>> |Attackers may maintain persistence by creating registry keys using AppInit DLLs. AppInit DLLs are loaded by every process using the common library, user32.dll. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<registry-persistence-via-appinit-dll-history, Version history>>
+|<<network-level-authentication-nla-disabled, Network-Level Authentication (NLA) Disabled>> |Identifies the attempt to disable Network-Level Authentication (NLA) via registry modification. Network Level Authentication (NLA) is a feature on Windows that provides an extra layer of security for Remote Desktop (RDP) connections, as it requires users to authenticate before allowing a full RDP session. Attackers can disable NLA to enable persistence methods that require access to the Windows sign-in screen without authenticating, such as Accessibility Features persistence methods, like Sticky Keys. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |3
 
-|<<remote-computer-account-dnshostname-update, Remote Computer Account DnsHostName Update>> |Identifies the remote update to a computer account's DnsHostName attribute. If the new value set is a valid domain controller DNS hostname and the subject computer name is not a domain controller, then it's highly likely a preparation step to exploit CVE-2022-26923 in an attempt to elevate privileges from a standard domain user to domain admin privileges. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Active Directory]  |8.3.0 |101 <<remote-computer-account-dnshostname-update-history, Version history>>
+|<<new-activesyncalloweddeviceid-added-via-powershell, New ActiveSyncAllowedDeviceID Added via PowerShell>> |Identifies the use of the Exchange PowerShell cmdlet, Set-CASMailbox, to add a new ActiveSync allowed device. Adversaries may target user email to collect sensitive information. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<remote-desktop-enabled-in-windows-firewall-by-netsh, Remote Desktop Enabled in Windows Firewall by Netsh>> |Identifies use of the network shell utility (netsh.exe) to enable inbound Remote Desktop Protocol (RDP) connections in the Windows Firewall. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<remote-desktop-enabled-in-windows-firewall-by-netsh-history, Version history>>
+|<<new-github-app-installed, New GitHub App Installed>> |This rule detects when a new GitHub App has been installed in your organization account. GitHub Apps extend GitHub's functionality both within and outside of GitHub. When an app is installed it is granted permissions to read or modify your repository and organization data. Only trusted apps should be installed and any newly installed apps should be investigated to verify their legitimacy. Unauthorized app installation could lower your organization's security posture and leave you exposed for future attacks. |[Domain: Cloud], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Github] |8.3.0 |1
 
-|<<remote-execution-via-file-shares, Remote Execution via File Shares>> |Identifies the execution of a file that was created by the virtual system process. This may indicate lateral movement via network file shares. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement] [Investigation Guide]  |7.11.0 |102 <<remote-execution-via-file-shares-history, Version history>>
+|<<new-github-owner-added, New GitHub Owner Added>> |Detects when a new member is added to a GitHub organization as an owner. This role provides admin level privileges. Any new owner roles should be investigated to determine it's validity. Unauthorized owner roles could indicate compromise within your organization and provide unlimited access to data and settings. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Persistence], [Data Source: Github] |8.3.0 |3
 
-|<<remote-file-copy-to-a-hidden-share, Remote File Copy to a Hidden Share>> |Identifies a remote file copy attempt to a hidden network share. This may indicate lateral movement or data staging activity. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.11.0 |101 <<remote-file-copy-to-a-hidden-share-history, Version history>>
+|<<new-okta-authentication-behavior-detected, New Okta Authentication Behavior Detected>> |Detects events where Okta behavior detection has identified a new authentication behavior. |[Use Case: Identity and Access Audit], [Tactic: Initial Access], [Data Source: Okta] |8.10.0 |1
 
-|<<remote-file-copy-via-teamviewer, Remote File Copy via TeamViewer>> |Identifies an executable or script file remotely downloaded via a TeamViewer transfer session. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control] [Investigation Guide] [Elastic Endgame]  |7.10.0 |102 <<remote-file-copy-via-teamviewer-history, Version history>>
+|<<new-okta-identity-provider-idp-added-by-admin, New Okta Identity Provider (IdP) Added by Admin>> |Detects the creation of a new Identity Provider (IdP) by a Super Administrator or Organization Administrator within Okta. |[Use Case: Identity and Access Audit], [Tactic: Persistence], [Data Source: Okta] |8.10.0 |1
 
-|<<remote-file-download-via-desktopimgdownldr-utility, Remote File Download via Desktopimgdownldr Utility>> |Identifies the desktopimgdownldr utility being used to download a remote file. An adversary may use desktopimgdownldr to download arbitrary files as an alternative to certutil. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control] [Investigation Guide] [Elastic Endgame]  |7.10.0 |102 <<remote-file-download-via-desktopimgdownldr-utility-history, Version history>>
+|<<new-systemd-service-created-by-previously-unknown-process, New Systemd Service Created by Previously Unknown Process>> |Systemd service files are configuration files in Linux systems used to define and manage system services. Malicious actors can leverage systemd service files to achieve persistence by creating or modifying service files to execute malicious commands or payloads during system startup. This allows them to maintain unauthorized access, execute additional malicious activities, or evade detection. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.6.0 |9
 
-|<<remote-file-download-via-mpcmdrun, Remote File Download via MpCmdRun>> |Identifies the Windows Defender configuration utility (MpCmdRun.exe) being used to download a remote file. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control] [Investigation Guide] [Elastic Endgame]  |7.10.0 |102 <<remote-file-download-via-mpcmdrun-history, Version history>>
+|<<new-systemd-timer-created, New Systemd Timer Created>> |Detects the creation of a systemd timer within any of the default systemd timer directories. Systemd timers can be used by an attacker to gain persistence, by scheduling the execution of a command or script. Similarly to cron/at, systemd timers can be set up to execute on boot time, or on a specific point in time, which allows attackers to regain access in case the connection to the infected asset was lost. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.6.0 |9
 
-|<<remote-file-download-via-powershell, Remote File Download via PowerShell>> |Identifies powershell.exe being used to download an executable file from an untrusted remote destination. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control] [Investigation Guide]  |7.11.0 |102 <<remote-file-download-via-powershell-history, Version history>>
+|<<new-user-added-to-github-organization, New User Added To GitHub Organization>> |A new user was added to a GitHub organization. |[Domain: Cloud], [Use Case: Threat Detection], [Use Case: UEBA], [Tactic: Persistence], [Rule Type: BBR], [Data Source: Github] |8.3.0 |1
 
-|<<remote-file-download-via-script-interpreter, Remote File Download via Script Interpreter>> |Identifies built-in Windows script interpreters (cscript.exe or wscript.exe) being used to download an executable file from a remote destination. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control] [Investigation Guide]  |7.11.0 |102 <<remote-file-download-via-script-interpreter-history, Version history>>
+|<<new-or-modified-federation-domain, New or Modified Federation Domain>> |Identifies a new or modified federation domain, which can be used to create a trust between O365 and an external identity provider. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Identity and Access Audit], [Tactic: Privilege Escalation] |8.8.0 |206
 
-|<<remote-logon-followed-by-scheduled-task-creation, Remote Logon followed by Scheduled Task Creation>> |Identifies a remote logon followed by a scheduled task creation on the target host. This could be indicative of adversary lateral movement. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |8.5.0 |1
+|<<nping-process-activity, Nping Process Activity>> |Nping ran on a Linux host. Nping is part of the Nmap tool suite and has the ability to construct raw packets for a wide variety of security testing applications, including denial of service testing. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |108
 
-|<<remote-ssh-login-enabled-via-systemsetup-command, Remote SSH Login Enabled via systemsetup Command>> |Detects use of the systemsetup command to enable remote SSH Login. |[Elastic] [Host] [macOS] [Threat Detection] [Lateral Movement]  |7.10.0 |100 <<remote-ssh-login-enabled-via-systemsetup-command-history, Version history>>
+|<<nullsessionpipe-registry-modification, NullSessionPipe Registry Modification>> |Identifies NullSessionPipe registry modifications that specify which pipes can be accessed anonymously. This could be indicative of adversary lateral movement preparation by making the added pipe available to everyone. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<remote-scheduled-task-creation, Remote Scheduled Task Creation>> |Identifies remote scheduled task creations on a target host. This could be indicative of adversary lateral movement. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement] [Investigation Guide]  |7.11.0 |102 <<remote-scheduled-task-creation-history, Version history>>
+|<<o365-email-reported-by-user-as-malware-or-phish, O365 Email Reported by User as Malware or Phish>> |Detects the occurrence of emails reported as Phishing or Malware by Users. Security Awareness training is essential to stay ahead of scammers and threat actors, as security products can be bypassed, and the user can still receive a malicious message. Educating users to report suspicious messages can help identify gaps in security controls and prevent malware infections and Business Email Compromise attacks. |[Domain: Cloud], [Data Source: Microsoft 365], [Tactic: Initial Access] |8.8.0 |206
 
-|<<remote-system-discovery-commands, Remote System Discovery Commands>> |Discovery of remote system information using built-in commands, which may be used to move laterally. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<remote-system-discovery-commands-history, Version history>>
+|<<o365-excessive-single-sign-on-logon-errors, O365 Excessive Single Sign-On Logon Errors>> |Identifies accounts with a high number of single sign-on (SSO) logon errors. Excessive logon errors may indicate an attempt to brute force a password or SSO token. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Identity and Access Audit], [Tactic: Credential Access] |8.8.0 |207
 
-|<<remote-windows-service-installed, Remote Windows Service Installed>> |Identifies a network logon followed by Windows service creation with same LogonId. This could be indicative of lateral movement, but will be noisy if commonly done by administrators." |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement] [Persistence]  |8.6.0 |1
+|<<o365-exchange-suspicious-mailbox-right-delegation, O365 Exchange Suspicious Mailbox Right Delegation>> |Identifies the assignment of rights to access content from another mailbox. An adversary may use the compromised account to send messages to other accounts in the network of the target organization while creating inbox rules, so messages can evade spam/phishing detection mechanisms. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Persistence] |8.8.0 |206
 
-|<<remotely-started-services-via-rpc, Remotely Started Services via RPC>> |Identifies remote execution of Windows services over remote procedure call (RPC). This could be indicative of lateral movement, but will be noisy if commonly done by administrators." |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement] [Investigation Guide]  |7.11.0 |102 <<remotely-started-services-via-rpc-history, Version history>>
+|<<o365-mailbox-audit-logging-bypass, O365 Mailbox Audit Logging Bypass>> |Detects the occurrence of mailbox audit bypass associations. The mailbox audit is responsible for logging specified mailbox events (like accessing a folder or a message or permanently deleting a message). However, actions taken by some authorized accounts, such as accounts used by third-party tools or accounts used for lawful monitoring, can create a large number of mailbox audit log entries and may not be of interest to your organization. Because of this, administrators can create bypass associations, allowing certain accounts to perform their tasks without being logged. Attackers can abuse this allowlist mechanism to conceal actions taken, as the mailbox audit will log no activity done by the account. |[Domain: Cloud], [Data Source: Microsoft 365], [Tactic: Initial Access], [Tactic: Defense Evasion] |8.8.0 |206
 
-|<<renamed-autoit-scripts-interpreter, Renamed AutoIt Scripts Interpreter>> |Identifies a suspicious AutoIt process execution. Malware written as an AutoIt script tends to rename the AutoIt executable to avoid detection. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.10.0 |102 <<renamed-autoit-scripts-interpreter-history, Version history>>
+|<<office-test-registry-persistence, Office Test Registry Persistence>> |Identifies the modification of the Microsoft Office "Office Test" Registry key, a registry location that can be used to specify a DLL which will be executed every time an MS Office application is started. Attackers can abuse this to gain persistence on a compromised host. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |3
 
-|<<reverse-shell-created-via-named-pipe, Reverse Shell Created via Named Pipe>> |Identifies a reverse shell via the abuse of named pipes on Linux with the help of OpenSSL or Netcat. First in, first out (FIFO) files are special files for reading and writing to by Linux processes. For this to work, a named pipe is created and passed to a Linux shell where the use of a network connection tool such as Netcat or OpenSSL has been established. The stdout and stderr are captured in the named pipe from the network connection and passed back to the shell for execution. |[Elastic] [Host] [Linux] [Threat Detection] [Execution] [Investigation Guide]  |8.6.0 |1
+|<<okta-brute-force-or-password-spraying-attack, Okta Brute Force or Password Spraying Attack>> |Identifies a high number of failed Okta user authentication attempts from a single IP address, which could be indicative of a brute force or password spraying attack. An adversary may attempt a brute force or password spraying attack to obtain unauthorized access to user accounts. |[Use Case: Identity and Access Audit], [Tactic: Credential Access], [Data Source: Okta] |8.10.0 |208
 
-|<<roshal-archive-rar-or-powershell-file-downloaded-from-the-internet, Roshal Archive (RAR) or PowerShell File Downloaded from the Internet>> |Detects a Roshal Archive (RAR) file or PowerShell script downloaded from the internet by an internal host. Gaining initial access to a system and then downloading encoded or encrypted tools to move laterally is a common practice for adversaries as a way to protect their more valuable tools and tactics, techniques, and procedures (TTPs). This may be atypical behavior for a managed network and can be indicative of malware, exfiltration, or command and control. |[Elastic] [Network] [Threat Detection] [Command and Control] [Host]  |7.10.0 |100 <<roshal-archive-rar-or-powershell-file-downloaded-from-the-internet-history, Version history>>
+|<<okta-fastpass-phishing-detection, Okta FastPass Phishing Detection>> |Detects when Okta FastPass prevents a user from authenticating to a phishing website. |[Tactic: Initial Access], [Use Case: Identity and Access Audit], [Data Source: Okta] |8.10.0 |103
 
-|<<sip-provider-modification, SIP Provider Modification>> |Identifies modifications to the registered Subject Interface Package (SIP) providers. SIP providers are used by the Windows cryptographic system to validate file signatures on the system. This may be an attempt to bypass signature validation checks or inject code into critical processes. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.12.0 |101 <<sip-provider-modification-history, Version history>>
+|<<okta-sign-in-events-via-third-party-idp, Okta Sign-In Events via Third-Party IdP>> |Detects sign-in events where authentication is carried out via a third-party Identity Provider (IdP). |[Use Case: Identity and Access Audit], [Tactic: Initial Access], [Data Source: Okta] |8.10.0 |2
 
-|<<smb-windows-file-sharing-activity-to-the-internet, SMB (Windows File Sharing) Activity to the Internet>> |This rule detects network events that may indicate the use of Windows file sharing (also called SMB or CIFS) traffic to the Internet. SMB is commonly used within networks to share files, printers, and other system resources amongst trusted systems. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector or for data exfiltration. |[Elastic] [Host] [Network] [Threat Detection] [Initial Access] [Host]  |7.6.0 |100 <<smb-windows-file-sharing-activity-to-the-internet-history, Version history>>
+|<<okta-threatinsight-threat-suspected-promotion, Okta ThreatInsight Threat Suspected Promotion>> |Okta ThreatInsight is a feature that provides valuable debug data regarding authentication and authorization processes, which is logged in the system. Within this data, there is a specific field called threat_suspected, which represents Okta's internal evaluation of the authentication or authorization workflow. When this field is set to True, it suggests the presence of potential credential access techniques, such as password-spraying, brute-forcing, replay attacks, and other similar threats. |[Use Case: Identity and Access Audit], [Data Source: Okta] |8.10.0 |205
 
-|<<smtp-on-port-26-tcp, SMTP on Port 26/TCP>> |This rule detects events that may indicate use of SMTP on TCP port 26. This port is commonly used by several popular mail transfer agents to deconflict with the default SMTP port 25. This port has also been used by a malware family called BadPatch for command and control of Windows systems. |[Elastic] [Host] [Network] [Threat Detection] [Command and Control] [Host]  |7.6.0 |100 <<smtp-on-port-26-tcp-history, Version history>>
+|<<okta-user-session-impersonation, Okta User Session Impersonation>> |A user has initiated a session impersonation granting them access to the environment with the permissions of the user they are impersonating. This would likely indicate Okta administrative access and should only ever occur if requested and expected. |[Use Case: Identity and Access Audit], [Tactic: Credential Access], [Data Source: Okta] |8.10.0 |207
 
-|<<ssh-authorized-keys-file-modification, SSH Authorized Keys File Modification>> |The Secure Shell (SSH) authorized_keys file specifies which users are allowed to log into a server using public key authentication. Adversaries may modify it to maintain persistence on a victim host by adding their own public key(s). |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<ssh-authorized-keys-file-modification-history, Version history>>
+|<<okta-user-sessions-started-from-different-geolocations, Okta User Sessions Started from Different Geolocations>> |Detects when a specific Okta actor has multiple sessions started from different geolocations. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Initial Access] |8.10.0 |1
 
-|<<sunburst-command-and-control-activity, SUNBURST Command and Control Activity>> |The malware known as SUNBURST targets the SolarWind's Orion business software for command and control. This rule detects post-exploitation command and control activity of the SUNBURST backdoor. |[Elastic] [Host] [Windows] [Threat Detection] [Command and Control] [Investigation Guide]  |7.11.0 |102 <<sunburst-command-and-control-activity-history, Version history>>
+|<<onedrive-malware-file-upload, OneDrive Malware File Upload>> |Identifies the occurence of files uploaded to OneDrive being detected as Malware by the file scanning engine. Attackers can use File Sharing and Organization Repositories to spread laterally within the company and amplify their access. Users can inadvertently share these files without knowing their maliciousness, giving adversaries opportunity to gain initial access to other endpoints in the environment. |[Domain: Cloud], [Data Source: Microsoft 365], [Tactic: Lateral Movement] |8.8.0 |206
 
-|<<scheduled-task-created-by-a-windows-script, Scheduled Task Created by a Windows Script>> |A scheduled task was created by a Windows script via cscript.exe, wscript.exe or powershell.exe. This can be abused by an adversary to establish persistence. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<scheduled-task-created-by-a-windows-script-history, Version history>>
+|<<outbound-scheduled-task-activity-via-powershell, Outbound Scheduled Task Activity via PowerShell>> |Identifies the PowerShell process loading the Task Scheduler COM DLL followed by an outbound RPC network connection within a short time period. This may indicate lateral movement or remote discovery via scheduled tasks. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<scheduled-task-execution-at-scale-via-gpo, Scheduled Task Execution at Scale via GPO>> |Detects the modification of Group Policy Object attributes to execute a scheduled task in the objects controlled by the GPO. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Active Directory] [Investigation Guide]  |8.0.0 |102 <<scheduled-task-execution-at-scale-via-gpo-history, Version history>>
+|<<parent-process-pid-spoofing, Parent Process PID Spoofing>> |Identifies parent process spoofing used to thwart detection. Adversaries may spoof the parent process identifier (PPID) of a new process to evade process-monitoring defenses or to elevate privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<scheduled-tasks-at-command-enabled, Scheduled Tasks AT Command Enabled>> |Identifies attempts to enable the Windows scheduled tasks AT command via the registry. Attackers may use this method to move laterally or persist locally. The AT command has been deprecated since Windows 8 and Windows Server 2012, but still exists for backwards compatibility. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.11.0 |101 <<scheduled-tasks-at-command-enabled-history, Version history>>
+|<<peripheral-device-discovery, Peripheral Device Discovery>> |Identifies use of the Windows file system utility (fsutil.exe) to gather information about attached peripheral devices and components connected to a computer system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<screensaver-plist-file-modified-by-unexpected-process, Screensaver Plist File Modified by Unexpected Process>> |Identifies when a screensaver plist file is modified by an unexpected process. An adversary can maintain persistence on a macOS endpoint by creating a malicious screensaver (.saver) file and configuring the screensaver plist file to execute code each time the screensaver is activated. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.16.0 |100 <<screensaver-plist-file-modified-by-unexpected-process-history, Version history>>
+|<<permission-theft-detected-elastic-endgame, Permission Theft - Detected - Elastic Endgame>> |Elastic Endgame detected Permission Theft. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |103
 
-|<<sedebugprivilege-enabled-by-a-suspicious-process, SeDebugPrivilege Enabled by a Suspicious Process>> |Identifies the creation of a process running as SYSTEM and impersonating a Windows core binary privileges. Adversaries may create a new process with a different token to escalate privileges and bypass access controls. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |8.6.0 |1
+|<<permission-theft-prevented-elastic-endgame, Permission Theft - Prevented - Elastic Endgame>> |Elastic Endgame prevented Permission Theft. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |103
 
-|<<searching-for-saved-credentials-via-vaultcmd, Searching for Saved Credentials via VaultCmd>> |Windows Credential Manager allows you to create, view, or delete saved credentials for signing into websites, connected applications, and networks. An adversary may abuse this to list or dump credentials stored in the Credential Manager for saved usernames and passwords. This may also be performed in preparation of lateral movement. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Elastic Endgame]  |7.12.0 |102 <<searching-for-saved-credentials-via-vaultcmd-history, Version history>>
+|<<persistence-via-bits-job-notify-cmdline, Persistence via BITS Job Notify Cmdline>> |An adversary can use the Background Intelligent Transfer Service (BITS) SetNotifyCmdLine method to execute a program that runs after a job finishes transferring data or after a job enters a specified state in order to persist on a system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
 
-|<<security-software-discovery-using-wmic, Security Software Discovery using WMIC>> |Identifies the use of Windows Management Instrumentation Command (WMIC) to discover certain System Security Settings such as AntiVirus or Host Firewall details. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<security-software-discovery-using-wmic-history, Version history>>
+|<<persistence-via-directoryservice-plugin-modification, Persistence via DirectoryService Plugin Modification>> |Identifies the creation or modification of a DirectoryService PlugIns (dsplug) file. The DirectoryService daemon launches on each system boot and automatically reloads after crash. It scans and executes bundles that are located in the DirectoryServices PlugIns folder and can be abused by adversaries to maintain persistence. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<security-software-discovery-via-grep, Security Software Discovery via Grep>> |Identifies the use of the grep command to discover known third-party macOS and Linux security tools, such as Antivirus or Host Firewall details. |[Elastic] [Host] [macOS] [Linux] [Threat Detection] [Discovery] [Investigation Guide]  |7.12.0 |102 <<security-software-discovery-via-grep-history, Version history>>
+|<<persistence-via-docker-shortcut-modification, Persistence via Docker Shortcut Modification>> |An adversary can establish persistence by modifying an existing macOS dock property list in order to execute a malicious application instead of the intended one when invoked. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<sensitive-files-compression, Sensitive Files Compression>> |Identifies the use of a compression utility to collect known files containing sensitive information, such as credentials and system configurations. |[Elastic] [Host] [Linux] [Threat Detection] [Collection] [Credential Access]  |7.12.0 |100 <<sensitive-files-compression-history, Version history>>
+|<<persistence-via-folder-action-script, Persistence via Folder Action Script>> |Detects modification of a Folder Action script. A Folder Action script is executed when the folder to which it is attached has items added or removed, or when its window is opened, closed, moved, or resized. Adversaries may abuse this feature to establish persistence by utilizing a malicious script. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<sensitive-privilege-seenabledelegationprivilege-assigned-to-a-user, Sensitive Privilege SeEnableDelegationPrivilege assigned to a User>> |Identifies the assignment of the SeEnableDelegationPrivilege sensitive "user right" to a user. The SeEnableDelegationPrivilege "user right" enables computer and user accounts to be trusted for delegation. Attackers can abuse this right to compromise Active Directory accounts and elevate their privileges. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Active Directory] [Investigation Guide]  |8.1.0 |102 <<sensitive-privilege-seenabledelegationprivilege-assigned-to-a-user-history, Version history>>
+|<<persistence-via-hidden-run-key-detected, Persistence via Hidden Run Key Detected>> |Identifies a persistence mechanism that utilizes the NtSetValueKey native API to create a hidden (null terminated) registry key. An adversary may use this method to hide from system utilities such as the Registry Editor (regedit). |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<service-command-lateral-movement, Service Command Lateral Movement>> |Identifies use of sc.exe to create, modify, or start services on remote hosts. This could be indicative of adversary lateral movement but will be noisy if commonly done by admins. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.10.0 |101 <<service-command-lateral-movement-history, Version history>>
+|<<persistence-via-kde-autostart-script-or-desktop-file-modification, Persistence via KDE AutoStart Script or Desktop File Modification>> |Identifies the creation or modification of a K Desktop Environment (KDE) AutoStart script or desktop file that will execute upon each user logon. Adversaries may abuse this method for persistence. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<service-control-spawned-via-script-interpreter, Service Control Spawned via Script Interpreter>> |Identifies Service Control (sc.exe) spawning from script interpreter processes to create, modify, or start services. This could be indicative of adversary lateral movement but will be noisy if commonly done by admins. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.6.0 |100 <<service-control-spawned-via-script-interpreter-history, Version history>>
+|<<persistence-via-login-or-logout-hook, Persistence via Login or Logout Hook>> |Identifies use of the Defaults command to install a login or logoff hook in MacOS. An adversary may abuse this capability to establish persistence in an environment by inserting code to be executed at login or logout. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<service-creation-via-local-kerberos-authentication, Service Creation via Local Kerberos Authentication>> |Identifies a suspicious local successful logon event where the Logon Package is Kerberos, the remote address is set to localhost, followed by a sevice creation from the same LogonId. This may indicate an attempt to leverage a Kerberos relay attack variant that can be used to elevate privilege locally from a domain joined user to local System privileges. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Credential Access]  |8.3.0 |100 <<service-creation-via-local-kerberos-authentication-history, Version history>>
+|<<persistence-via-microsoft-office-addins, Persistence via Microsoft Office AddIns>> |Detects attempts to establish persistence on an endpoint by abusing Microsoft Office add-ins. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<setuid-setgid-bit-set-via-chmod, Setuid / Setgid Bit Set via chmod>> |An adversary may add the setuid or setgid bit to a file or directory in order to run a file with the privileges of the owning user or group. An adversary can take advantage of this to either do a shell escape or exploit a vulnerability in an application with the setuid or setgid bit to get code running in a different user’s context. Additionally, adversaries can use this mechanism on their own malware to make sure they're able to execute in elevated contexts in the future. |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Privilege Escalation]  |7.8.0 |100 <<setuid-setgid-bit-set-via-chmod-history, Version history>>
+|<<persistence-via-microsoft-outlook-vba, Persistence via Microsoft Outlook VBA>> |Detects attempts to establish persistence on an endpoint by installing a rogue Microsoft Outlook VBA Template. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
 
-|<<sharepoint-malware-file-upload, SharePoint Malware File Upload>> |Identifies the occurence of files uploaded to SharePoint being detected as Malware by the file scanning engine. Attackers can use File Sharing and Organization Repositories to spread laterally within the company and amplify their access. Users can inadvertently share these files without knowing their maliciousness, giving adversaries opportunities to gain initial access to other endpoints in the environment. |[Elastic] [Cloud] [Microsoft 365] [Continuous Monitoring] [SecOps] [Lateral Movement]  |8.1.0 |101 <<sharepoint-malware-file-upload-history, Version history>>
+|<<persistence-via-powershell-profile, Persistence via PowerShell profile>> |Identifies the creation or modification of a PowerShell profile. PowerShell profile is a script that is executed when PowerShell starts to customize the user environment, which can be abused by attackers to persist in a environment where PowerShell is common. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |9
 
-|<<shell-execution-via-apple-scripting, Shell Execution via Apple Scripting>> |Identifies the execution of the shell process (sh) via scripting (JXA or AppleScript). Adversaries may use the doShellScript functionality in JXA or do shell script in AppleScript to execute system commands. |[Elastic] [Host] [macOS] [Threat Detection] [Execution]  |7.11.0 |100 <<shell-execution-via-apple-scripting-history, Version history>>
+|<<persistence-via-scheduled-job-creation, Persistence via Scheduled Job Creation>> |A job can be used to schedule programs or scripts to be executed at a specified date and time. Adversaries may abuse task scheduling functionality to facilitate initial or recurring execution of malicious code. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<signed-proxy-execution-via-ms-work-folders, Signed Proxy Execution via MS Work Folders>> |Identifies the use of Windows Work Folders to execute a potentially masqueraded control.exe file in the current working directory. Misuse of Windows Work Folders could indicate malicious activity. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |8.2.0 |102 <<signed-proxy-execution-via-ms-work-folders-history, Version history>>
+|<<persistence-via-telemetrycontroller-scheduled-task-hijack, Persistence via TelemetryController Scheduled Task Hijack>> |Detects the successful hijack of Microsoft Compatibility Appraiser scheduled task to establish persistence with an integrity level of system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<softwareupdate-preferences-modification, SoftwareUpdate Preferences Modification>> |Identifies changes to the SoftwareUpdate preferences using the built-in defaults command. Adversaries may abuse this in an attempt to disable security updates. |[Elastic] [Host] [macOS] [Threat Detection] [Defense Evasion]  |7.12.0 |100 <<softwareupdate-preferences-modification-history, Version history>>
+|<<persistence-via-update-orchestrator-service-hijack, Persistence via Update Orchestrator Service Hijack>> |Identifies potential hijacking of the Microsoft Update Orchestrator Service to establish persistence with an integrity level of SYSTEM. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Privilege Escalation], [Use Case: Vulnerability], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<solarwinds-process-disabling-services-via-registry, SolarWinds Process Disabling Services via Registry>> |Identifies a SolarWinds binary modifying the start type of a service to be disabled. An adversary may abuse this technique to manipulate relevant security services. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.11.0 |101 <<solarwinds-process-disabling-services-via-registry-history, Version history>>
+|<<persistence-via-wmi-event-subscription, Persistence via WMI Event Subscription>> |An adversary can use Windows Management Instrumentation (WMI) to install event filters, providers, consumers, and bindings that execute code when a defined event occurs. Adversaries may use the capabilities of WMI to subscribe to an event and execute arbitrary code when that event occurs, providing persistence on a system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<spike-in-aws-error-messages, Spike in AWS Error Messages>> |A machine learning job detected a significant spike in the rate of a particular error in the CloudTrail messages. Spikes in error messages may accompany attempts at privilege escalation, lateral movement, or discovery. |[Elastic] [Cloud] [AWS] [ML] [Investigation Guide]  |7.9.0 |102 <<spike-in-aws-error-messages-history, Version history>>
+|<<persistence-via-wmi-standard-registry-provider, Persistence via WMI Standard Registry Provider>> |Identifies use of the Windows Management Instrumentation StdRegProv (registry provider) to modify commonly abused registry locations for persistence. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<spike-in-failed-logon-events, Spike in Failed Logon Events>> |A machine learning job found an unusually large spike in authentication failure events. This can be due to password spraying, user enumeration or brute force activity and may be a precursor to account takeover or credentialed access. |[Elastic] [Authentication] [Threat Detection] [ML] [Credential Access]  |7.14.0 |100 <<spike-in-failed-logon-events-history, Version history>>
+|<<persistent-scripts-in-the-startup-directory, Persistent Scripts in the Startup Directory>> |Identifies script engines creating files in the Startup folder, or the creation of script files in the Startup folder. Adversaries may abuse this technique to maintain persistence in an environment. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
 
-|<<spike-in-firewall-denies, Spike in Firewall Denies>> |A machine learning job detected an unusually large spike in network traffic that was denied by network access control lists (ACLs) or firewall rules. Such a burst of denied traffic is usually caused by either 1) a mis-configured application or firewall or 2) suspicious or malicious activity. Unsuccessful attempts at network transit, in order to connect to command-and-control (C2), or engage in data exfiltration, may produce a burst of failed connections. This could also be due to unusually large amounts of reconnaissance or enumeration traffic. Denial-of-service attacks or traffic floods may also produce such a surge in traffic. |[Elastic] [Network] [Threat Detection] [ML]  |7.13.0 |100 <<spike-in-firewall-denies-history, Version history>>
+|<<port-forwarding-rule-addition, Port Forwarding Rule Addition>> |Identifies the creation of a new port forwarding rule. An adversary may abuse this technique to bypass network segmentation restrictions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
 
-|<<spike-in-logon-events, Spike in Logon Events>> |A machine learning job found an unusually large spike in successful authentication events. This can be due to password spraying, user enumeration or brute force activity. |[Elastic] [Authentication] [Threat Detection] [ML] [Credential Access]  |7.14.0 |100 <<spike-in-logon-events-history, Version history>>
+|<<possible-consent-grant-attack-via-azure-registered-application, Possible Consent Grant Attack via Azure-Registered Application>> |Detects when a user grants permissions to an Azure-registered application or when an administrator grants tenant-wide permissions to an application. An adversary may create an Azure-registered application that requests access to data such as contact information, email, or documents. |[Domain: Cloud], [Data Source: Azure], [Data Source: Microsoft 365], [Use Case: Identity and Access Audit], [Resources: Investigation Guide], [Tactic: Initial Access] |8.8.0 |212
 
-|<<spike-in-logon-events-from-a-source-ip, Spike in Logon Events from a Source IP>> |A machine learning job found an unusually large spike in successful authentication events from a particular source IP address. This can be due to password spraying, user enumeration or brute force activity. |[Elastic] [Authentication] [Threat Detection] [ML] [Credential Access]  |7.14.0 |100 <<spike-in-logon-events-from-a-source-ip-history, Version history>>
+|<<possible-fin7-dga-command-and-control-behavior, Possible FIN7 DGA Command and Control Behavior>> |This rule detects a known command and control pattern in network events. The FIN7 threat group is known to use this command and control technique, while maintaining persistence in their target's network. |[Use Case: Threat Detection], [Tactic: Command and Control], [Domain: Endpoint] |8.3.0 |105
 
-|<<spike-in-network-traffic, Spike in Network Traffic>> |A machine learning job detected an unusually large spike in network traffic. Such a burst of traffic, if not caused by a surge in business activity, can be due to suspicious or malicious activity. Large-scale data exfiltration may produce a burst of network traffic; this could also be due to unusually large amounts of reconnaissance or enumeration traffic. Denial-of-service attacks or traffic floods may also produce such a surge in traffic. |[Elastic] [Network] [Threat Detection] [ML]  |7.13.0 |100 <<spike-in-network-traffic-history, Version history>>
+|<<possible-okta-dos-attack, Possible Okta DoS Attack>> |Detects possible Denial of Service (DoS) attacks against an Okta organization. An adversary may attempt to disrupt an organization's business operations by performing a DoS attack against its Okta service. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Impact] |8.10.0 |205
 
-|<<spike-in-network-traffic-to-a-country, Spike in Network Traffic To a Country>> |A machine learning job detected an unusually large spike in network activity to one destination country in the network logs. This could be due to unusually large amounts of reconnaissance or enumeration traffic. Data exfiltration activity may also produce such a surge in traffic to a destination country which does not normally appear in network traffic or business work-flows. Malware instances and persistence mechanisms may communicate with command-and-control (C2) infrastructure in their country of origin, which may be an unusual destination country for the source network. |[Elastic] [Network] [Threat Detection] [ML]  |7.13.0 |100 <<spike-in-network-traffic-to-a-country-history, Version history>>
+|<<potential-adidns-poisoning-via-wildcard-record-creation, Potential ADIDNS Poisoning via Wildcard Record Creation>> |Active Directory Integrated DNS (ADIDNS) is one of the core components of AD DS, leveraging AD's access control and replication to maintain domain consistency. It stores DNS zones as AD objects, a feature that, while robust, introduces some security issues, such as wildcard records, mainly because of the default permission (Any authenticated users) to create DNS-named records. Attackers can create wildcard records to redirect traffic that doesn't explicitly match records contained in the zone, becoming the Man-in-the-Middle and being able to abuse DNS similarly to LLMNR/NBNS spoofing. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Active Directory], [Use Case: Active Directory Monitoring] |8.3.0 |1
 
-|<<startup-folder-persistence-via-unsigned-process, Startup Folder Persistence via Unsigned Process>> |Identifies files written or modified in the startup folder by unsigned processes. Adversaries may abuse this technique to maintain persistence in an environment. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.11.0 |102 <<startup-folder-persistence-via-unsigned-process-history, Version history>>
+|<<potential-abuse-of-resources-by-high-token-count-and-large-response-sizes, Potential Abuse of Resources by High Token Count and Large Response Sizes>> |Detects potential resource exhaustion or data breach attempts by monitoring for users who consistently generate high input token counts, submit numerous requests, and receive large responses. This behavior could indicate an attempt to overload the system or extract an unusually large amount of data, possibly revealing sensitive information or causing service disruptions. |[Domain: LLM], [Data Source: AWS Bedrock], [Data Source: Amazon Web Services], [Data Source: AWS S3], [Use Case: Potential Overload], [Use Case: Resource Exhaustion], [Mitre Atlas: LLM04] |8.13.0 |1
 
-|<<startup-persistence-by-a-suspicious-process, Startup Persistence by a Suspicious Process>> |Identifies files written to or modified in the startup folder by commonly abused processes. Adversaries may use this technique to maintain persistence. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.11.0 |102 <<startup-persistence-by-a-suspicious-process-history, Version history>>
+|<<potential-admin-group-account-addition, Potential Admin Group Account Addition>> |Identifies attempts to add an account to the admin group via the command line. This could be an indication of privilege escalation activity. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.11.0 |206
 
-|<<startup-or-run-key-registry-modification, Startup or Run Key Registry Modification>> |Identifies run key or startup key registry modifications. In order to survive reboots and other system interrupts, attackers will modify run keys within the registry or leverage startup folder items as a form of persistence. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.11.0 |102 <<startup-or-run-key-registry-modification-history, Version history>>
+|<<potential-antimalware-scan-interface-bypass-via-powershell, Potential Antimalware Scan Interface Bypass via PowerShell>> |Identifies the execution of PowerShell script with keywords related to different Antimalware Scan Interface (AMSI) bypasses. An adversary may attempt first to disable AMSI before executing further malicious powershell scripts to evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: PowerShell Logs], [Resources: Investigation Guide] |8.3.0 |8
 
-|<<startup-logon-script-added-to-group-policy-object, Startup/Logon Script added to Group Policy Object>> |Detects the modification of Group Policy Objects (GPO) to add a startup/logon script to users or computer objects. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Active Directory] [Investigation Guide]  |8.0.0 |102 <<startup-logon-script-added-to-group-policy-object-history, Version history>>
+|<<potential-application-shimming-via-sdbinst, Potential Application Shimming via Sdbinst>> |The Application Shim was created to allow for backward compatibility of software as the operating system codebase changes over time. This Windows functionality has been abused by attackers to stealthily gain persistence and arbitrary code execution in legitimate Windows processes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<sublime-plugin-or-application-script-modification, Sublime Plugin or Application Script Modification>> |Adversaries may create or modify the Sublime application plugins or scripts to execute a malicious payload each time the Sublime application is started. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<sublime-plugin-or-application-script-modification-history, Version history>>
+|<<potential-buffer-overflow-attack-detected, Potential Buffer Overflow Attack Detected>> |Detects potential buffer overflow attacks by querying the "Segfault Detected" pre-built rule signal index, through a threshold rule, with a minimum number of 100 segfault alerts in a short timespan. A large amount of segfaults in a short time interval could indicate application exploitation attempts. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Initial Access], [Use Case: Vulnerability], [Rule Type: Higher-Order Rule] |8.3.0 |2
 
-|<<sudo-heap-based-buffer-overflow-attempt, Sudo Heap-Based Buffer Overflow Attempt>> |Identifies the attempted use of a heap-based buffer overflow vulnerability for the Sudo binary in Unix-like systems (CVE-2021-3156). Successful exploitation allows an unprivileged user to escalate to the root user. |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Privilege Escalation]  |7.12.0 |100 <<sudo-heap-based-buffer-overflow-attempt-history, Version history>>
+|<<potential-chroot-container-escape-via-mount, Potential Chroot Container Escape via Mount>> |Monitors for the execution of a file system mount followed by a chroot execution. Given enough permissions, a user within a container is capable of mounting the root file system of the host, and leveraging chroot to escape its containarized environment. This behavior pattern is very uncommon and should be investigated. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Domain: Container], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<sudoers-file-modification, Sudoers File Modification>> |A sudoers file specifies the commands that users or groups can run and from which terminals. Adversaries can take advantage of these configurations to execute commands as other users or spawn processes with higher privileges. |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Privilege Escalation]  |7.8.0 |100 <<sudoers-file-modification-history, Version history>>
+|<<potential-code-execution-via-postgresql, Potential Code Execution via Postgresql>> |This rule monitors for suspicious activities that may indicate an attacker attempting to execute arbitrary code within a PostgreSQL environment. Attackers can execute code via PostgreSQL as a result of gaining unauthorized access to a public facing PostgreSQL database or exploiting vulnerabilities, such as remote command execution and SQL injection attacks, which can result in unauthorized access and malicious actions, and facilitate post-exploitation activities for unauthorized access and malicious actions. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |6
 
-|<<suspicious-.net-code-compilation, Suspicious .NET Code Compilation>> |Identifies suspicious .NET code execution. connections. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.10.0 |102 <<suspicious-.net-code-compilation-history, Version history>>
+|<<potential-command-and-control-via-internet-explorer, Potential Command and Control via Internet Explorer>> |Identifies instances of Internet Explorer (iexplore.exe) being started via the Component Object Model (COM) making unusual network connections. Adversaries could abuse Internet Explorer via COM to avoid suspicious processes making network connections and bypass host-based firewall restrictions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<suspicious-.net-reflection-via-powershell, Suspicious .NET Reflection via PowerShell>> |Detects the use of Reflection.Assembly to load PEs and DLLs in memory in PowerShell scripts. Attackers use this method to load executables and DLLs without writing to the disk, bypassing security solutions. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide]  |8.0.0 |102 <<suspicious-.net-reflection-via-powershell-history, Version history>>
+|<<potential-container-escape-via-modified-notify-on-release-file, Potential Container Escape via Modified notify_on_release File>> |This rule detects modification of the cgroup notify_on_release file from inside a container. When the notify_on_release flag is enabled (1) in a cgroup, then whenever the last task in the cgroup exits or attaches to another cgroup, the command specified in the release_agent file is run and invoked from the host. A privileged container with SYS_ADMIN capabilities, enables a threat actor to mount a cgroup directory and modify the notify_on_release flag in order to take advantage of this feature, which could be used for further privilege escalation and container escapes to the host machine. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.8.0 |1
 
-|<<suspicious-activity-reported-by-okta-user, Suspicious Activity Reported by Okta User>> |Detects when a user reports suspicious activity for their Okta account. These events should be investigated, as they can help security teams identify when an adversary is attempting to gain access to their network. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring]  |7.9.0 |102 <<suspicious-activity-reported-by-okta-user-history, Version history>>
+|<<potential-container-escape-via-modified-release-agent-file, Potential Container Escape via Modified release_agent File>> |This rule detects modification of the CGroup release_agent file from inside a privileged container. The release_agent is a script that is executed at the termination of any process on that CGroup and is invoked from the host. A privileged container with SYS_ADMIN capabilities, enables a threat actor to mount a CGroup directory and modify the release_agent which could be used for further privilege escalation and container escapes to the host machine. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.8.0 |1
 
-|<<suspicious-automator-workflows-execution, Suspicious Automator Workflows Execution>> |Identifies the execution of the Automator Workflows process followed by a network connection from it's XPC service. Adversaries may drop a custom workflow template that hosts malicious JavaScript for Automation (JXA) code as an alternative to using osascript. |[Elastic] [Host] [macOS] [Threat Detection] [Execution]  |7.12.0 |100 <<suspicious-automator-workflows-execution-history, Version history>>
+|<<potential-cookies-theft-via-browser-debugging, Potential Cookies Theft via Browser Debugging>> |Identifies the execution of a Chromium based browser with the debugging process argument, which may indicate an attempt to steal authentication cookies. An adversary may steal web application or service session cookies and use them to gain access web applications or Internet services as an authenticated user without needing credentials. |[Domain: Endpoint], [OS: Linux], [OS: Windows], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.3.0 |105
 
-|<<suspicious-browser-child-process, Suspicious Browser Child Process>> |Identifies the execution of a suspicious browser child process. Adversaries may gain access to a system through a user visiting a website over the normal course of browsing. With this technique, the user's web browser is typically targeted for exploitation. |[Elastic] [Host] [macOS] [Threat Detection] [Initial Access] [Execution]  |7.12.0 |100 <<suspicious-browser-child-process-history, Version history>>
+|<<potential-credential-access-via-dcsync, Potential Credential Access via DCSync>> |This rule identifies when a User Account starts the Active Directory Replication Process. Attackers can use the DCSync technique to get credential information of individual accounts or the entire domain, thus compromising the entire domain. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Privilege Escalation], [Data Source: Active Directory], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring] |8.3.0 |113
 
-|<<suspicious-calendar-file-modification, Suspicious Calendar File Modification>> |Identifies suspicious modifications of the calendar file by an unusual process. Adversaries may create a custom calendar notification procedure to execute a malicious program at a recurring interval to establish persistence. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<suspicious-calendar-file-modification-history, Version history>>
+|<<potential-credential-access-via-duplicatehandle-in-lsass, Potential Credential Access via DuplicateHandle in LSASS>> |Identifies suspicious access to an LSASS handle via DuplicateHandle from an unknown call trace module. This may indicate an attempt to bypass the NtOpenProcess API to evade detection and dump LSASS memory for credential access. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Sysmon] |8.8.0 |208
 
-|<<suspicious-certutil-commands, Suspicious CertUtil Commands>> |Identifies suspicious commands being used with certutil.exe. CertUtil is a native Windows component which is part of Certificate Services. CertUtil is often abused by attackers to live off the land for stealthier command and control or data exfiltration. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.6.0 |101 <<suspicious-certutil-commands-history, Version history>>
+|<<potential-credential-access-via-lsass-memory-dump, Potential Credential Access via LSASS Memory Dump>> |Identifies suspicious access to LSASS handle from a call trace pointing to DBGHelp.dll or DBGCore.dll, which both export the MiniDumpWriteDump method that can be used to dump LSASS memory content in preparation for credential access. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic:Execution], [Data Source: Sysmon] |8.8.0 |209
 
-|<<suspicious-child-process-of-adobe-acrobat-reader-update-service, Suspicious Child Process of Adobe Acrobat Reader Update Service>> |Detects attempts to exploit privilege escalation vulnerabilities related to the Adobe Acrobat Reader PrivilegedHelperTool responsible for installing updates. For more information, refer to CVE-2020-9615, CVE-2020-9614 and CVE-2020-9613 and verify that the impacted system is patched. |[Elastic] [Host] [macOS] [Threat Detection] [Privilege Escalation] [CVE-2020-9615] [CVE-2020-9614] [CVE-2020-9613]  |7.12.0 |100 <<suspicious-child-process-of-adobe-acrobat-reader-update-service-history, Version history>>
+|<<potential-credential-access-via-memory-dump-file-creation, Potential Credential Access via Memory Dump File Creation>> |Identifies the creation or modification of a medium size memory dump file which can indicate an attempt to access credentials from a process memory. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |3
 
-|<<suspicious-cmd-execution-via-wmi, Suspicious Cmd Execution via WMI>> |Identifies suspicious command execution (cmd) via Windows Management Instrumentation (WMI) on a remote host. This could be indicative of adversary lateral movement. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Elastic Endgame]  |7.11.0 |102 <<suspicious-cmd-execution-via-wmi-history, Version history>>
+|<<potential-credential-access-via-renamed-com-services-dll, Potential Credential Access via Renamed COM+ Services DLL>> |Identifies suspicious renamed COMSVCS.DLL Image Load, which exports the MiniDump function that can be used to dump a process memory. This may indicate an attempt to dump LSASS memory while bypassing command-line based detection in preparation for credential access. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Defense Evasion], [Data Source: Sysmon] |8.3.0 |108
 
-|<<suspicious-crontab-creation-or-modification, Suspicious CronTab Creation or Modification>> |Identifies attempts to create or modify a crontab via a process that is not crontab (i.e python, osascript, etc.). This activity should not be highly prevalent and could indicate the use of cron as a persistence mechanism by a threat actor. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |8.3.0 |100 <<suspicious-crontab-creation-or-modification-history, Version history>>
+|<<potential-credential-access-via-trusted-developer-utility, Potential Credential Access via Trusted Developer Utility>> |An instance of MSBuild, the Microsoft Build Engine, loaded DLLs (dynamically linked libraries) responsible for Windows credential management. This technique is sometimes used for credential dumping. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
 
-|<<suspicious-dll-loaded-for-persistence-or-privilege-escalation, Suspicious DLL Loaded for Persistence or Privilege Escalation>> |Identifies the loading of a non Microsoft signed DLL that is missing on a default Windows install (phantom DLL) or one that can be loaded from a different location by a native Windows process. This may be abused to persist or elevate privileges via privileged file write vulnerabilities. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Privilege Escalation] [Investigation Guide]  |7.12.0 |102 <<suspicious-dll-loaded-for-persistence-or-privilege-escalation-history, Version history>>
+|<<potential-credential-access-via-windows-utilities, Potential Credential Access via Windows Utilities>> |Identifies the execution of known Windows utilities often abused to dump LSASS memory or the Active Directory database (NTDS.dit) in preparation for credential access. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
 
-|<<suspicious-emond-child-process, Suspicious Emond Child Process>> |Identifies the execution of a suspicious child process of the Event Monitor Daemon (emond). Adversaries may abuse this service by writing a rule to execute commands when a defined event occurs, such as system start up or user authentication. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.12.0 |100 <<suspicious-emond-child-process-history, Version history>>
+|<<potential-cross-site-scripting-xss, Potential Cross Site Scripting (XSS)>> |Cross-Site Scripting (XSS) is a type of attack in which malicious scripts are injected into trusted websites. In XSS attacks, an attacker uses a benign web application to send malicious code, generally in the form of a browser-side script. This detection rule identifies the potential malicious executions of such browser-side scripts. |[Data Source: APM], [Use Case: Threat Detection], [Tactic: Initial Access] |8.3.0 |1
 
-|<<suspicious-endpoint-security-parent-process, Suspicious Endpoint Security Parent Process>> |A suspicious Endpoint Security parent process was detected. This may indicate a process hollowing or other form of code injection. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.10.0 |102 <<suspicious-endpoint-security-parent-process-history, Version history>>
+|<<potential-dga-activity, Potential DGA Activity>> |A population analysis machine learning job detected potential DGA (domain generation algorithm) activity. Such activity is often used by malware command and control (C2) channels. This machine learning job looks for a source IP address making DNS requests that have an aggregate high probability of being DGA activity. |[Use Case: Domain Generation Algorithm Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Command and Control] |8.9.0 |3
 
-|<<suspicious-execution-short-program-name, Suspicious Execution - Short Program Name>> |Identifies process execution with a single character process name. This is often done by adversaries while staging or executing temporary utilities. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.11.0 |102 <<suspicious-execution-short-program-name-history, Version history>>
+|<<potential-dll-side-loading-via-microsoft-antimalware-service-executable, Potential DLL Side-Loading via Microsoft Antimalware Service Executable>> |Identifies a Windows trusted program that is known to be vulnerable to DLL Search Order Hijacking starting after being renamed or from a non-standard path. This is uncommon behavior and may indicate an attempt to evade defenses via side-loading a malicious DLL within the memory space of one of those processes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Tactic: Execution], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
 
-|<<suspicious-execution-from-a-mounted-device, Suspicious Execution from a Mounted Device>> |Identifies when a script interpreter or signed binary is launched via a non-standard working directory. An attacker may use this technique to evade defenses. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.14.0 |100 <<suspicious-execution-from-a-mounted-device-history, Version history>>
+|<<potential-dll-side-loading-via-trusted-microsoft-programs, Potential DLL Side-Loading via Trusted Microsoft Programs>> |Identifies an instance of a Windows trusted program that is known to be vulnerable to DLL Search Order Hijacking starting after being renamed or from a non-standard path. This is uncommon behavior and may indicate an attempt to evade defenses via side loading a malicious DLL within the memory space of one of those processes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
 
-|<<suspicious-execution-via-scheduled-task, Suspicious Execution via Scheduled Task>> |Identifies execution of a suspicious program via scheduled tasks by looking at process lineage and command line usage. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<suspicious-execution-via-scheduled-task-history, Version history>>
+|<<potential-dns-tunneling-via-nslookup, Potential DNS Tunneling via NsLookup>> |This rule identifies a large number (15) of nslookup.exe executions with an explicit query type from the same host. This may indicate command and control activity utilizing the DNS protocol. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<suspicious-explorer-child-process, Suspicious Explorer Child Process>> |Identifies a suspicious Windows explorer child process. Explorer.exe can be abused to launch malicious scripts or executables from a trusted parent process. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access]  |7.11.0 |101 <<suspicious-explorer-child-process-history, Version history>>
+|<<potential-data-exfiltration-activity-to-an-unusual-destination-port, Potential Data Exfiltration Activity to an Unusual Destination Port>> |A machine learning job has detected data exfiltration to a particular destination port. Data transfer patterns that are outside the normal traffic patterns of an organization could indicate exfiltration over command and control channels. |[Use Case: Data Exfiltration Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Exfiltration] |8.9.0 |3
 
-|<<suspicious-file-creation-in-etc-for-persistence, Suspicious File Creation in /etc for Persistence>> |Detects the manual creation of files in specific etc directories, via user root, used by Linux malware to persist and elevate privileges on compromised systems. File creation in these directories should not be entirely common and could indicate a malicious binary or script installing persistence for long term access. |[Elastic] [Host] [Linux] [Threat Detection] [Persistence] [Orbit] [Lightning Framework]  |8.4.0 |101 <<suspicious-file-creation-in-etc-for-persistence-history, Version history>>
+|<<potential-data-exfiltration-activity-to-an-unusual-ip-address, Potential Data Exfiltration Activity to an Unusual IP Address>> |A machine learning job has detected data exfiltration to a particular geo-location (by IP address). Data transfers to geo-locations that are outside the normal traffic patterns of an organization could indicate exfiltration over command and control channels. |[Use Case: Data Exfiltration Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Exfiltration] |8.9.0 |3
 
-|<<suspicious-html-file-creation, Suspicious HTML File Creation>> |Identifies the execution of a browser process to open an HTML file with high entropy and size. Adversaries may smuggle data and files past content filters by hiding malicious payloads inside of seemingly benign HTML files. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access]  |8.4.0 |100 <<suspicious-html-file-creation-history, Version history>>
+|<<potential-data-exfiltration-activity-to-an-unusual-iso-code, Potential Data Exfiltration Activity to an Unusual ISO Code>> |A machine learning job has detected data exfiltration to a particular geo-location (by region name). Data transfers to geo-locations that are outside the normal traffic patterns of an organization could indicate exfiltration over command and control channels. |[Use Case: Data Exfiltration Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Exfiltration] |8.9.0 |3
 
-|<<suspicious-hidden-child-process-of-launchd, Suspicious Hidden Child Process of Launchd>> |Identifies the execution of a launchd child process with a hidden file. An adversary can establish persistence by installing a new logon item, launch agent, or daemon that executes upon login. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence] [Defense Evasion]  |7.12.0 |100 <<suspicious-hidden-child-process-of-launchd-history, Version history>>
+|<<potential-data-exfiltration-activity-to-an-unusual-region, Potential Data Exfiltration Activity to an Unusual Region>> |A machine learning job has detected data exfiltration to a particular geo-location (by region name). Data transfers to geo-locations that are outside the normal traffic patterns of an organization could indicate exfiltration over command and control channels. |[Use Case: Data Exfiltration Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Exfiltration] |8.9.0 |3
 
-|<<suspicious-image-load-taskschd.dll-from-ms-office, Suspicious Image Load (taskschd.dll) from MS Office>> |Identifies a suspicious image load (taskschd.dll) from Microsoft Office processes. This behavior may indicate adversarial activity where a scheduled task is configured via Windows Component Object Model (COM). This technique can be used to configure persistence and evade monitoring by avoiding the usage of the traditional Windows binary (schtasks.exe) used to manage scheduled tasks. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<suspicious-image-load-taskschd.dll-from-ms-office-history, Version history>>
+|<<potential-defense-evasion-via-cmstp-exe, Potential Defense Evasion via CMSTP.exe>> |The Microsoft Connection Manager Profile Installer (CMSTP.exe) is a command-line program to install Connection Manager service profiles, which accept installation information file (INF) files. Adversaries may abuse CMSTP to proxy the execution of malicious code by supplying INF files that contain malicious commands. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |2
 
-|<<suspicious-imagepath-service-creation, Suspicious ImagePath Service Creation>> |Identifies the creation of a suspicious ImagePath value. This could be an indication of an adversary attempting to stealthily persist or escalate privileges through abnormal service creation. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<suspicious-imagepath-service-creation-history, Version history>>
+|<<potential-defense-evasion-via-proot, Potential Defense Evasion via PRoot>> |Identifies the execution of the PRoot utility, an open-source tool for user-space implementation of chroot, mount --bind, and binfmt_misc. Adversaries can leverage an open-source tool PRoot to expand the scope of their operations to multiple Linux distributions and simplify their necessary efforts. In a normal threat scenario, the scope of an attack is limited by the varying configurations of each Linux distribution. With PRoot, it provides an attacker with a consistent operational environment across different Linux distributions, such as Ubuntu, Fedora, and Alpine. PRoot also provides emulation capabilities that allow for malware built on other architectures, such as ARM, to be run.The post-exploitation technique called bring your own filesystem (BYOF), can be used by the threat actors to execute malicious payload or elevate privileges or perform network scans or orchestrate another attack on the environment. Although PRoot was originally not developed with malicious intent it can be easily tuned to work for one. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |7
 
-|<<suspicious-java-child-process, Suspicious JAVA Child Process>> |Identifies suspicious child processes of the Java interpreter process. This may indicate an attempt to execute a malicious JAR file or an exploitation attempt via a JAVA specific vulnerability. |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Execution] [Investigation Guide]  |7.12.0 |102 <<suspicious-java-child-process-history, Version history>>
+|<<potential-disabling-of-apparmor, Potential Disabling of AppArmor>> |This rule monitors for potential attempts to disable AppArmor. AppArmor is a Linux security module that enforces fine-grained access control policies to restrict the actions and resources that specific applications and processes can access. Adversaries may disable security tools to avoid possible detection of their tools and activities. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |6
 
-|<<suspicious-lsass-access-via-malseclogon, Suspicious LSASS Access via MalSecLogon>> |Identifies suspicious access to LSASS handle from a call trace pointing to seclogon.dll and with a suspicious access rights value. This may indicate an attempt to leak an LSASS handle via abusing the Secondary Logon service in preparation for credential access. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Sysmon Only]  |8.4.0 |101 <<suspicious-lsass-access-via-malseclogon-history, Version history>>
+|<<potential-disabling-of-selinux, Potential Disabling of SELinux>> |Identifies potential attempts to disable Security-Enhanced Linux (SELinux), which is a Linux kernel security feature to support access control policies. Adversaries may disable security tools to avoid possible detection of their tools and activities. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |110
 
-|<<suspicious-ms-office-child-process, Suspicious MS Office Child Process>> |Identifies suspicious child processes of frequently targeted Microsoft Office applications (Word, PowerPoint, Excel). These child processes are often launched during exploitation of Office applications or from documents with malicious macros. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access] [Investigation Guide]  |7.6.0 |102 <<suspicious-ms-office-child-process-history, Version history>>
+|<<potential-enumeration-via-active-directory-web-service, Potential Enumeration via Active Directory Web Service>> |Identifies processes loading Active Directory related modules followed by a network connection to the ADWS dedicated TCP port. Adversaries may abuse the ADWS Windows service that allows Active Directory to be queried via this web service. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<suspicious-ms-outlook-child-process, Suspicious MS Outlook Child Process>> |Identifies suspicious child processes of Microsoft Outlook. These child processes are often associated with spear phishing activity. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access] [Investigation Guide]  |7.6.0 |102 <<suspicious-ms-outlook-child-process-history, Version history>>
+|<<potential-evasion-via-filter-manager, Potential Evasion via Filter Manager>> |The Filter Manager Control Program (fltMC.exe) binary may be abused by adversaries to unload a filter driver and evade defenses. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<suspicious-managed-code-hosting-process, Suspicious Managed Code Hosting Process>> |Identifies a suspicious managed code hosting process which could indicate code injection or other form of suspicious code execution. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.10.0 |100 <<suspicious-managed-code-hosting-process-history, Version history>>
+|<<potential-evasion-via-windows-filtering-platform, Potential Evasion via Windows Filtering Platform>> |Identifies multiple Windows Filtering Platform block events and where the process name is related to an endpoint security software. Adversaries may add malicious WFP rules to prevent Endpoint security from sending telemetry. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |3
 
-|<<suspicious-microsoft-diagnostics-wizard-execution, Suspicious Microsoft Diagnostics Wizard Execution>> |Identifies potential abuse of the Microsoft Diagnostics Troubleshooting Wizard (MSDT) to proxy malicious command or binary execution via malicious process arguments. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |8.3.0 |102 <<suspicious-microsoft-diagnostics-wizard-execution-history, Version history>>
+|<<potential-execution-via-xzbackdoor, Potential Execution via XZBackdoor>> |It identifies potential malicious shell executions through remote SSH and detects cases where the sshd service suddenly terminates soon after successful execution, suggesting suspicious behavior similar to the XZ backdoor. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Persistence], [Tactic: Lateral Movement], [Data Source: Elastic Defend] |8.3.0 |1
 
-|<<suspicious-network-connection-attempt-by-root, Suspicious Network Connection Attempt by Root>> |Identifies an outbound network connection attempt followed by a session id change as the root user by the same process entity. This particular instantiation of a network connection is abnormal and should be investigated as it may indicate a potential reverse shell activity via a privileged process. |[Elastic] [Host] [Linux] [Threat Detection] [Command and Control]  |8.3.0 |100 <<suspicious-network-connection-attempt-by-root-history, Version history>>
+|<<potential-exploitation-of-an-unquoted-service-path-vulnerability, Potential Exploitation of an Unquoted Service Path Vulnerability>> |Adversaries may leverage unquoted service path vulnerabilities to escalate privileges. By placing an executable in a higher-level directory within the path of an unquoted service executable, Windows will natively launch this executable from its defined path variable instead of the benign one in a deeper directory, thus leading to code execution. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.3.0 |3
 
-|<<suspicious-pdf-reader-child-process, Suspicious PDF Reader Child Process>> |Identifies suspicious child processes of PDF reader applications. These child processes are often launched via exploitation of PDF applications or social engineering. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Investigation Guide] [Elastic Endgame]  |7.7.0 |102 <<suspicious-pdf-reader-child-process-history, Version history>>
+|<<potential-external-linux-ssh-brute-force-detected, Potential External Linux SSH Brute Force Detected>> |Identifies multiple external consecutive login failures targeting a user account from the same source address within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to these accounts. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access] |8.3.0 |7
 
-|<<suspicious-portable-executable-encoded-in-powershell-script, Suspicious Portable Executable Encoded in Powershell Script>> |Detects the presence of a portable executable (PE) in a PowerShell script by looking for its encoded header. Attackers embed PEs into PowerShell scripts to inject them into memory, avoiding defences by not writing to disk. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Investigation Guide]  |7.16.0 |102 <<suspicious-portable-executable-encoded-in-powershell-script-history, Version history>>
+|<<potential-file-download-via-a-headless-browser, Potential File Download via a Headless Browser>> |Identifies the use of a browser to download a file from a remote URL and from a suspicious parent process. Adversaries may use browsers to avoid ingress tool transfer restrictions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Windows], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |1
 
-|<<suspicious-powershell-engine-imageload, Suspicious PowerShell Engine ImageLoad>> |Identifies the PowerShell engine being invoked by unexpected processes. Rather than executing PowerShell functionality with powershell.exe, some attackers do this to operate more stealthily. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<suspicious-powershell-engine-imageload-history, Version history>>
+|<<potential-file-transfer-via-certreq, Potential File Transfer via Certreq>> |Identifies Certreq making an HTTP Post request. Adversaries could abuse Certreq to download files or upload data to a remote URL. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Command and Control], [Tactic: Exfiltration], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |8
 
-|<<suspicious-powershell-script, Suspicious Powershell Script>> |A machine learning job detected a PowerShell script with unusual data characteristics, such as obfuscation, that may be a characteristic of malicious PowerShell script text blocks. |[Elastic] [Host] [Windows] [Threat Detection] [ML] [Execution]  |7.7.0 |101 <<suspicious-powershell-script-history, Version history>>
+|<<potential-hidden-local-user-account-creation, Potential Hidden Local User Account Creation>> |Identifies attempts to create a local account that will be hidden from the macOS logon window. This may indicate an attempt to evade user attention while maintaining persistence using a separate local account. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<suspicious-print-spooler-file-deletion, Suspicious Print Spooler File Deletion>> |Detects deletion of print driver files by an unusual process. This may indicate a clean up attempt post successful privilege escalation via Print Spooler service related vulnerabilities. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.14.0 |100 <<suspicious-print-spooler-file-deletion-history, Version history>>
+|<<potential-hidden-process-via-mount-hidepid, Potential Hidden Process via Mount Hidepid>> |Identifies the execution of mount process with hidepid parameter, which can make processes invisible to other users from the system. Adversaries using Linux kernel version 3.2+ (or RHEL/CentOS v6.5+ above) can hide the process from other users. When hidepid=2 option is executed to mount the /proc filesystem, only the root user can see all processes and the logged-in user can only see their own process. This provides a defense evasion mechanism for the adversaries to hide their process executions from all other commands such as ps, top, pgrep and more. With the Linux kernel hardening hidepid option all the user has to do is remount the /proc filesystem with the option, which can now be monitored and detected. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |8
 
-|<<suspicious-print-spooler-point-and-print-dll, Suspicious Print Spooler Point and Print DLL>> |Detects attempts to exploit a privilege escalation vulnerability (CVE-2020-1030) related to the print spooler service. Exploitation involves chaining multiple primitives to load an arbitrary DLL into the print spooler process running as SYSTEM. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.11.0 |100 <<suspicious-print-spooler-point-and-print-dll-history, Version history>>
+|<<potential-internal-linux-ssh-brute-force-detected, Potential Internal Linux SSH Brute Force Detected>> |Identifies multiple internal consecutive login failures targeting a user account from the same source address within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to these accounts. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access] |8.3.0 |11
 
-|<<suspicious-print-spooler-spl-file-created, Suspicious Print Spooler SPL File Created>> |Detects attempts to exploit privilege escalation vulnerabilities related to the Print Spooler service including CVE-2020-1048 and CVE-2020-1337. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Investigation Guide]  |7.10.0 |102 <<suspicious-print-spooler-spl-file-created-history, Version history>>
+|<<potential-invoke-mimikatz-powershell-script, Potential Invoke-Mimikatz PowerShell Script>> |Mimikatz is a credential dumper capable of obtaining plaintext Windows account logins and passwords, along with many other features that make it useful for testing the security of networks. This rule detects Invoke-Mimikatz PowerShell script and alike. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.3.0 |108
 
-|<<suspicious-printspooler-service-executable-file-creation, Suspicious PrintSpooler Service Executable File Creation>> |Detects attempts to exploit privilege escalation vulnerabilities related to the Print Spooler service. For more information refer to the following CVE's - CVE-2020-1048, CVE-2020-1337 and CVE-2020-1300 and verify that the impacted system is patched. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.10.0 |100 <<suspicious-printspooler-service-executable-file-creation-history, Version history>>
+|<<potential-java-jndi-exploitation-attempt, Potential JAVA/JNDI Exploitation Attempt>> |Identifies an outbound network connection by JAVA to LDAP, RMI or DNS standard ports followed by a suspicious JAVA child processes. This may indicate an attempt to exploit a JAVA/NDI (Java Naming and Directory Interface) injection vulnerability. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Execution], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |104
 
-|<<suspicious-process-access-via-direct-system-call, Suspicious Process Access via Direct System Call>> |Identifies suspicious process access events from an unknown memory region. Endpoint security solutions usually hook userland Windows APIs in order to decide if the code that is being executed is malicious or not. It's possible to bypass hooked functions by writing malicious functions that call syscalls directly. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Sysmon Only]  |7.16.0 |102 <<suspicious-process-access-via-direct-system-call-history, Version history>>
+|<<potential-kerberos-attack-via-bifrost, Potential Kerberos Attack via Bifrost>> |Identifies use of Bifrost, a known macOS Kerberos pentesting tool, which can be used to dump cached Kerberos tickets or attempt unauthorized authentication techniques such as pass-the-ticket/hash and kerberoasting. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Lateral Movement], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<suspicious-process-creation-calltrace, Suspicious Process Creation CallTrace>> |Identifies when a process is created and immediately accessed from an unknown memory code region and by the same parent process. This may indicate a code injection attempt. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Sysmon Only]  |8.0.0 |102 <<suspicious-process-creation-calltrace-history, Version history>>
+|<<potential-lsa-authentication-package-abuse, Potential LSA Authentication Package Abuse>> |Adversaries can use the autostart mechanism provided by the Local Security Authority (LSA) authentication packages for privilege escalation or persistence by placing a reference to a binary in the Windows registry. The binary will then be executed by SYSTEM when the authentication packages are loaded. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |105
 
-|<<suspicious-process-execution-via-renamed-psexec-executable, Suspicious Process Execution via Renamed PsExec Executable>> |Identifies suspicious psexec activity which is executing from the psexec service that has been renamed, possibly to evade detection. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Elastic Endgame]  |7.10.0 |102 <<suspicious-process-execution-via-renamed-psexec-executable-history, Version history>>
+|<<potential-lsass-clone-creation-via-psscapturesnapshot, Potential LSASS Clone Creation via PssCaptureSnapShot>> |Identifies the creation of an LSASS process clone via PssCaptureSnapShot where the parent process is the initial LSASS process instance. This may indicate an attempt to evade detection and dump LSASS memory for credential access. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Sysmon] |8.3.0 |106
 
-|<<suspicious-rdp-activex-client-loaded, Suspicious RDP ActiveX Client Loaded>> |Identifies suspicious Image Loading of the Remote Desktop Services ActiveX Client (mstscax), this may indicate the presence of RDP lateral movement capability. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.11.0 |100 <<suspicious-rdp-activex-client-loaded-history, Version history>>
+|<<potential-lsass-memory-dump-via-psscapturesnapshot, Potential LSASS Memory Dump via PssCaptureSnapShot>> |Identifies suspicious access to an LSASS handle via PssCaptureSnapShot where two successive process accesses are performed by the same process and target two different instances of LSASS. This may indicate an attempt to evade detection and dump LSASS memory for credential access. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Sysmon] |8.8.0 |208
 
-|<<suspicious-remote-registry-access-via-sebackupprivilege, Suspicious Remote Registry Access via SeBackupPrivilege>> |Identifies remote access to the registry using an account with Backup Operators group membership. This may indicate an attempt to exfiltrate credentials by dumping the Security Account Manager (SAM) registry hive in preparation for credential access and privileges elevation. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement] [Credential Access] [Investigation Guide]  |8.2.0 |102 <<suspicious-remote-registry-access-via-sebackupprivilege-history, Version history>>
+|<<potential-lateral-tool-transfer-via-smb-share, Potential Lateral Tool Transfer via SMB Share>> |Identifies the creation or change of a Windows executable file over network shares. Adversaries may transfer tools or other files between systems in a compromised environment. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<suspicious-script-object-execution, Suspicious Script Object Execution>> |Identifies scrobj.dll loaded into unusual Microsoft processes. This usually means a malicious scriptlet is being executed in the target process. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.10.0 |100 <<suspicious-script-object-execution-history, Version history>>
+|<<potential-linux-backdoor-user-account-creation, Potential Linux Backdoor User Account Creation>> |Identifies the attempt to create a new backdoor user by setting the user's UID to 0. Attackers may alter a user's UID to 0 to establish persistence on a system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |6
 
-|<<suspicious-solarwinds-child-process, Suspicious SolarWinds Child Process>> |A suspicious SolarWinds child process was detected, which may indicate an attempt to execute malicious programs. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Elastic Endgame]  |7.11.0 |102 <<suspicious-solarwinds-child-process-history, Version history>>
+|<<potential-linux-credential-dumping-via-proc-filesystem, Potential Linux Credential Dumping via Proc Filesystem>> |Identifies the execution of the mimipenguin exploit script which is linux adaptation of Windows tool mimikatz. Mimipenguin exploit script is used to dump clear text passwords from a currently logged-in user. The tool exploits a known vulnerability CVE-2018-20781. Malicious actors can exploit the cleartext credentials in memory by dumping the process and extracting lines that have a high probability of containing cleartext passwords. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |7
 
-|<<suspicious-startup-shell-folder-modification, Suspicious Startup Shell Folder Modification>> |Identifies suspicious startup shell folder modifications to change the default Startup directory in order to bypass detections monitoring file creation in the Windows Startup folder. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.13.0 |102 <<suspicious-startup-shell-folder-modification-history, Version history>>
+|<<potential-linux-credential-dumping-via-unshadow, Potential Linux Credential Dumping via Unshadow>> |Identifies the execution of the unshadow utility which is part of John the Ripper, a password-cracking tool on the host machine. Malicious actors can use the utility to retrieve the combined contents of the '/etc/shadow' and '/etc/password' files. Using the combined file generated from the utility, the malicious threat actors can use them as input for password-cracking utilities or prepare themselves for future operations by gathering credential information of the victim. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |8
 
-|<<suspicious-wmi-image-load-from-ms-office, Suspicious WMI Image Load from MS Office>> |Identifies a suspicious image load (wmiutils.dll) from Microsoft Office processes. This behavior may indicate adversarial activity where child processes are spawned via Windows Management Instrumentation (WMI). This technique can be used to execute code and evade traditional parent/child processes spawned from Microsoft Office products. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Elastic Endgame]  |7.11.0 |101 <<suspicious-wmi-image-load-from-ms-office-history, Version history>>
+|<<potential-linux-hack-tool-launched, Potential Linux Hack Tool Launched>> |Monitors for the execution of different processes that might be used by attackers for malicious intent. An alert from this rule should be investigated further, as hack tools are commonly used by blue teamers and system administrators as well. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |3
 
-|<<suspicious-wmic-xsl-script-execution, Suspicious WMIC XSL Script Execution>> |Identifies WMIC allowlist bypass techniques by alerting on suspicious execution of scripts. When WMIC loads scripting libraries it may be indicative of an allowlist bypass. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.10.0 |101 <<suspicious-wmic-xsl-script-execution-history, Version history>>
+|<<potential-linux-local-account-brute-force-detected, Potential Linux Local Account Brute Force Detected>> |Identifies multiple consecutive login attempts executed by one process targeting a local linux user account within a short time interval. Adversaries might brute force login attempts across different users with a default wordlist or a set of customly crafted passwords in an attempt to gain access to these accounts. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.3.0 |6
 
-|<<suspicious-werfault-child-process, Suspicious WerFault Child Process>> |A suspicious WerFault child process was detected, which may indicate an attempt to run unnoticed. Verify process details such as command line, network connections, file writes and parent process details as well. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.10.0 |102 <<suspicious-werfault-child-process-history, Version history>>
+|<<potential-linux-ransomware-note-creation-detected, Potential Linux Ransomware Note Creation Detected>> |This rule identifies a sequence of a mass file encryption event in conjunction with the creation of a .txt file with a file name containing ransomware keywords executed by the same process in a 1 second timespan. Ransomware is a type of malware that encrypts a victim's files or systems and demands payment (usually in cryptocurrency) in exchange for the decryption key. One important indicator of a ransomware attack is the mass encryption of the file system, after which a new file extension is added to the file. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Impact], [Data Source: Elastic Defend] |8.3.0 |8
 
-|<<suspicious-zoom-child-process, Suspicious Zoom Child Process>> |A suspicious Zoom child process was detected, which may indicate an attempt to run unnoticed. Verify process details such as command line, network connections, file writes and associated file signature details as well. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.10.0 |102 <<suspicious-zoom-child-process-history, Version history>>
+|<<potential-linux-ssh-x11-forwarding, Potential Linux SSH X11 Forwarding>> |This rule monitors for X11 forwarding via SSH. X11 forwarding is a feature that allows users to run graphical applications on a remote server and display the application's graphical user interface on their local machine. Attackers can abuse X11 forwarding for tunneling their GUI-based tools, pivot through compromised systems, and create covert communication channels, enabling lateral movement and facilitating remote control of systems within a network. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Rule Type: BBR] |8.3.0 |3
 
-|<<suspicious-macos-ms-office-child-process, Suspicious macOS MS Office Child Process>> |Identifies suspicious child processes of frequently targeted Microsoft Office applications (Word, PowerPoint, and Excel). These child processes are often launched during exploitation of Office applications or by documents with malicious macros. |[Elastic] [Host] [macOS] [Threat Detection] [Initial Access]  |7.12.0 |100 <<suspicious-macos-ms-office-child-process-history, Version history>>
+|<<potential-linux-tunneling-and-or-port-forwarding, Potential Linux Tunneling and/or Port Forwarding>> |This rule monitors for a set of Linux utilities that can be used for tunneling and port forwarding. Attackers can leverage tunneling and port forwarding techniques to bypass network defenses, establish hidden communication channels, and gain unauthorized access to internal resources, facilitating data exfiltration, lateral movement, and remote control. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |7
 
-|<<suspicious-service-was-installed-in-the-system, Suspicious service was installed in the system>> |Identifies the creation of a new Windows service with suspicious Service command values. Windows services typically run as SYSTEM and can be used for privilege escalation and persistence. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |8.6.0 |1
+|<<potential-local-ntlm-relay-via-http, Potential Local NTLM Relay via HTTP>> |Identifies attempt to coerce a local NTLM authentication via HTTP using the Windows Printer Spooler service as a target. An adversary may use this primitive in combination with other techniques to elevate privileges on a compromised system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<svchost-spawning-cmd, Svchost spawning Cmd>> |Identifies a suspicious parent child process relationship with cmd.exe descending from svchost.exe |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Investigation Guide] [Elastic Endgame]  |7.6.0 |102 <<svchost-spawning-cmd-history, Version history>>
+|<<potential-masquerading-as-browser-process, Potential Masquerading as Browser Process>> |Identifies suspicious instances of browser processes, such as unsigned or signed with unusual certificates, that can indicate an attempt to conceal malicious activity, bypass security features such as allowlists, or trick users into executing malware. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Persistence], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |4
 
-|<<symbolic-link-to-shadow-copy-created, Symbolic Link to Shadow Copy Created>> |Identifies the creation of symbolic links to a shadow copy. Symbolic links can be used to access files in the shadow copy, including sensitive files such as ntds.dit, System Boot Key and browser offline credentials. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Investigation Guide] [Elastic Endgame]  |8.0.0 |102 <<symbolic-link-to-shadow-copy-created-history, Version history>>
+|<<potential-masquerading-as-business-app-installer, Potential Masquerading as Business App Installer>> |Identifies executables with names resembling legitimate business applications but lacking signatures from the original developer. Attackers may trick users into downloading malicious executables that masquerade as legitimate applications via malicious ads, forum posts, and tutorials, effectively gaining initial access. |[Domain: Endpoint], [Data Source: Elastic Defend], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Initial Access], [Tactic: Execution] |8.3.0 |4
 
-|<<system-information-discovery-via-windows-command-shell, System Information Discovery via Windows Command Shell>> |Identifies the execution of discovery commands to enumerate system info or files and folders using the Windows Command Shell. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Execution]  |8.6.0 |1
+|<<potential-masquerading-as-communication-apps, Potential Masquerading as Communication Apps>> |Identifies suspicious instances of communications apps, both unsigned and renamed ones, that can indicate an attempt to conceal malicious activity, bypass security features such as allowlists, or trick users into executing malware. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |5
 
-|<<system-log-file-deletion, System Log File Deletion>> |Identifies the deletion of sensitive Linux system logs. This may indicate an attempt to evade detection or destroy forensic evidence on a system. |[Elastic] [Host] [Linux] [Threat Detection] [Defense Evasion]  |7.11.0 |101 <<system-log-file-deletion-history, Version history>>
+|<<potential-masquerading-as-system32-dll, Potential Masquerading as System32 DLL>> |Identifies suspicious instances of default system32 DLLs either unsigned or signed with non-MS certificates. This can potentially indicate the attempt to masquerade as system DLLs, perform DLL Search Order Hijacking or backdoor and resign legitimate DLLs. |[Domain: Endpoint], [Data Source: Elastic Defend], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Persistence], [Rule Type: BBR] |8.4.0 |104
 
-|<<system-shells-via-services, System Shells via Services>> |Windows services typically run as SYSTEM and can be used as a privilege escalation opportunity. Malware or penetration testers may run a shell as a service to gain SYSTEM permissions. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.6.0 |102 <<system-shells-via-services-history, Version history>>
+|<<potential-masquerading-as-system32-executable, Potential Masquerading as System32 Executable>> |Identifies suspicious instances of default system32 executables, either unsigned or signed with non-MS certificates. This could indicate the attempt to masquerade as system executables or backdoored and resigned legitimate executables. |[Domain: Endpoint], [Data Source: Elastic Defend], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Persistence], [Rule Type: BBR] |8.3.0 |4
 
-|<<systemkey-access-via-command-line, SystemKey Access via Command Line>> |Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features, including Wi-Fi and website passwords, secure notes, certificates, and Kerberos. Adversaries may collect the keychain storage data from a system to acquire credentials. |[Elastic] [Host] [macOS] [Threat Detection] [Credential Access]  |7.12.0 |100 <<systemkey-access-via-command-line-history, Version history>>
+|<<potential-masquerading-as-vlc-dll, Potential Masquerading as VLC DLL>> |Identifies instances of VLC-related DLLs which are not signed by the original developer. Attackers may name their payload as legitimate applications to blend into the environment, or embedding its malicious code within legitimate applications to deceive machine learning algorithms by incorporating authentic and benign code. |[Domain: Endpoint], [Data Source: Elastic Defend], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Persistence], [Rule Type: BBR] |8.3.0 |3
 
-|<<tcc-bypass-via-mounted-apfs-snapshot-access, TCC Bypass via Mounted APFS Snapshot Access>> |Identifies the use of the mount_apfs command to mount the entire file system through Apple File System (APFS) snapshots as read-only and with the noowners flag set. This action enables the adversary to access almost any file in the file system, including all user data and files protected by Apple’s privacy framework (TCC). |[Elastic] [Host] [macOS] [Threat Detection] [Defense Evasion] [CVE_2020_9771]  |7.12.0 |100 <<tcc-bypass-via-mounted-apfs-snapshot-access-history, Version history>>
+|<<potential-memory-seeking-activity, Potential Memory Seeking Activity>> |Monitors for the execution of Unix utilities that may be leveraged as memory address seekers. Attackers may leverage built-in utilities to seek specific memory addresses, allowing for potential future manipulation/exploitation. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |2
 
-|<<tampering-of-bash-command-line-history, Tampering of Bash Command-Line History>> |Adversaries may attempt to clear or disable the Bash command-line history in an attempt to evade detection or forensic investigations. |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Defense Evasion]  |7.9.0 |100 <<tampering-of-bash-command-line-history-history, Version history>>
+|<<potential-meterpreter-reverse-shell, Potential Meterpreter Reverse Shell>> |This detection rule identifies a sample of suspicious Linux system file reads used for system fingerprinting, leveraged by the Metasploit Meterpreter shell to gather information about the target that it is executing its shell on. Detecting this pattern is indicative of a successful meterpreter shell connection. |[Data Source: Auditd Manager], [Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution] |8.6.0 |6
 
-|<<temporarily-scheduled-task-creation, Temporarily Scheduled Task Creation>> |Indicates the creation and deletion of a scheduled task within a short time interval. Adversaries can use these to proxy malicious execution via the schedule service and perform clean up. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Persistence]  |8.5.0 |2 <<temporarily-scheduled-task-creation-history, Version history>>
+|<<potential-microsoft-office-sandbox-evasion, Potential Microsoft Office Sandbox Evasion>> |Identifies the creation of a suspicious zip file prepended with special characters. Sandboxed Microsoft Office applications on macOS are allowed to write files that start with special characters, which can be combined with an AutoStart location to achieve sandbox evasion. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<third-party-backup-files-deleted-via-unexpected-process, Third-party Backup Files Deleted via Unexpected Process>> |Identifies the deletion of backup files, saved using third-party software, by a process outside of the backup suite. Adversaries may delete Backup files to ensure that recovery from a ransomware attack is less likely. |[Elastic] [Host] [Windows] [Threat Detection] [Impact] [Investigation Guide] [Elastic Endgame]  |7.16.0 |102 <<third-party-backup-files-deleted-via-unexpected-process-history, Version history>>
+|<<potential-modification-of-accessibility-binaries, Potential Modification of Accessibility Binaries>> |Windows contains accessibility features that may be launched with a key combination before a user has logged in. An adversary can modify the way these programs are launched to get a command prompt or backdoor without logging in to the system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
 
-|<<threat-detected-by-okta-threatinsight, Threat Detected by Okta ThreatInsight>> |Detects when Okta ThreatInsight identifies a request from a malicious IP address. Investigating requests from IP addresses identified as malicious by Okta ThreatInsight can help security teams monitor for and respond to credential based attacks against their organization, such as brute force and password spraying attacks. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Monitoring]  |7.9.0 |102 <<threat-detected-by-okta-threatinsight-history, Version history>>
+|<<potential-network-scan-detected, Potential Network Scan Detected>> |This rule identifies a potential port scan. A port scan is a method utilized by attackers to systematically scan a target system or network for open ports, allowing them to identify available services and potential vulnerabilities. By mapping out the open ports, attackers can gather critical information to plan and execute targeted attacks, gaining unauthorized access, compromising security, and potentially leading to data breaches, unauthorized control, or further exploitation of the targeted system or network. This rule proposes threshold logic to check for connection attempts from one source host to 20 or more destination ports. |[Domain: Network], [Tactic: Discovery], [Tactic: Reconnaissance], [Use Case: Network Security Monitoring] |8.3.0 |5
 
-|<<threat-intel-filebeat-module-v8.x-indicator-match, Threat Intel Filebeat Module (v8.x) Indicator Match>> |This rule is triggered when indicators from the Threat Intel Filebeat module (v8.x) has a match against local file or network observations. |[Elastic] [Windows] [Elastic Endgame] [Network] [Continuous Monitoring] [SecOps] [Monitoring] [Investigation Guide]  |8.0.0 |102 <<threat-intel-filebeat-module-v8.x-indicator-match-history, Version history>>
+|<<potential-network-scan-executed-from-host, Potential Network Scan Executed From Host>> |This threshold rule monitors for the rapid execution of unix utilities that are capable of conducting network scans. Adversaries may leverage built-in tools such as ping, netcat or socat to execute ping sweeps across the network while attempting to evade detection or due to the lack of network mapping tools available on the compromised host. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |3
 
-|<<threat-intel-indicator-match, Threat Intel Indicator Match>> |This rule is triggered when indicators from the Threat Intel integrations have a match against local file or network observations. |[Elastic] [Windows] [Elastic Endgame] [Network] [Continuous Monitoring] [SecOps] [Monitoring] [Investigation Guide]  |8.0.0 |102 <<threat-intel-indicator-match-history, Version history>>
+|<<potential-network-share-discovery, Potential Network Share Discovery>> |Adversaries may look for folders and drives shared on remote systems to identify sources of information to gather as a precursor for collection and identify potential systems of interest for Lateral Movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Tactic: Collection], [Rule Type: BBR] |8.3.0 |3
 
-|<<timestomping-using-touch-command, Timestomping using Touch Command>> |Timestomping is an anti-forensics technique which is used to modify the timestamps of a file, often to mimic files that are in the same folder. |[Elastic] [Host] [Linux] [macOS] [Threat Detection] [Defense Evasion]  |7.11.0 |100 <<timestomping-using-touch-command-history, Version history>>
+|<<potential-network-sweep-detected, Potential Network Sweep Detected>> |This rule identifies a potential network sweep.  A network sweep is a method used by attackers to scan a target network, identifying active hosts, open ports, and available services to gather information on vulnerabilities and weaknesses. This reconnaissance helps them plan subsequent attacks and exploit potential entry points for unauthorized access, data theft, or other malicious activities. This rule proposes threshold logic to check for connection attempts from one source host to 10 or more destination hosts on commonly used network services. |[Domain: Network], [Tactic: Discovery], [Tactic: Reconnaissance], [Use Case: Network Security Monitoring] |8.3.0 |5
 
-|<<uac-bypass-attempt-via-elevated-com-internet-explorer-add-on-installer, UAC Bypass Attempt via Elevated COM Internet Explorer Add-On Installer>> |Identifies User Account Control (UAC) bypass attempts by abusing an elevated COM Interface to launch a malicious program. Attackers may attempt to bypass UAC to stealthily execute code with elevated permissions. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.11.0 |101 <<uac-bypass-attempt-via-elevated-com-internet-explorer-add-on-installer-history, Version history>>
+|<<potential-non-standard-port-http-https-connection, Potential Non-Standard Port HTTP/HTTPS connection>> |Identifies potentially malicious processes communicating via a port paring typically not associated with HTTP/HTTPS. For example, HTTP over port 8443 or port 440 as opposed to the traditional port 80 , 443. Adversaries may make changes to the standard port a protocol uses to bypass filtering or muddle analysis/parsing of network data. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Command and Control], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |4
 
-|<<uac-bypass-attempt-via-privileged-ifileoperation-com-interface, UAC Bypass Attempt via Privileged IFileOperation COM Interface>> |Identifies attempts to bypass User Account Control (UAC) via DLL side-loading. Attackers may attempt to bypass UAC to stealthily execute code with elevated permissions. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.11.0 |101 <<uac-bypass-attempt-via-privileged-ifileoperation-com-interface-history, Version history>>
+|<<potential-non-standard-port-ssh-connection, Potential Non-Standard Port SSH connection>> |Identifies potentially malicious processes communicating via a port paring typically not associated with SSH. For example, SSH over port 2200 or port 2222 as opposed to the traditional port 22. Adversaries may make changes to the standard port a protocol uses to bypass filtering or muddle analysis/parsing of network data. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Command and Control], [OS: macOS], [Data Source: Elastic Defend] |8.3.0 |5
 
-|<<uac-bypass-attempt-via-windows-directory-masquerading, UAC Bypass Attempt via Windows Directory Masquerading>> |Identifies an attempt to bypass User Account Control (UAC) by masquerading as a Microsoft trusted Windows directory. Attackers may bypass UAC to stealthily execute code with elevated permissions. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Investigation Guide]  |7.11.0 |102 <<uac-bypass-attempt-via-windows-directory-masquerading-history, Version history>>
+|<<potential-okta-mfa-bombing-via-push-notifications, Potential Okta MFA Bombing via Push Notifications>> |Detects when an attacker abuses the Multi-Factor authentication mechanism by repeatedly issuing login requests until the user eventually accepts the Okta push notification. An adversary may attempt to bypass the Okta MFA policies configured for an organization to obtain unauthorized access. |[Use Case: Identity and Access Audit], [Tactic: Credential Access], [Data Source: Okta] |8.10.0 |3
 
-|<<uac-bypass-attempt-with-ieditionupgrademanager-elevated-com-interface, UAC Bypass Attempt with IEditionUpgradeManager Elevated COM Interface>> |Identifies attempts to bypass User Account Control (UAC) by abusing an elevated COM Interface to launch a rogue Windows ClipUp program. Attackers may attempt to bypass UAC to stealthily execute code with elevated permissions. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.11.0 |101 <<uac-bypass-attempt-with-ieditionupgrademanager-elevated-com-interface-history, Version history>>
+|<<potential-openssh-backdoor-logging-activity, Potential OpenSSH Backdoor Logging Activity>> |Identifies a Secure Shell (SSH) client or server process creating or writing to a known SSH backdoor log file. Adversaries may modify SSH related binaries for persistence or credential access via patching sensitive functions to enable unauthorized access or to log SSH credentials for exfiltration. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
 
-|<<uac-bypass-via-diskcleanup-scheduled-task-hijack, UAC Bypass via DiskCleanup Scheduled Task Hijack>> |Identifies User Account Control (UAC) bypass via hijacking DiskCleanup Scheduled Task. Attackers bypass UAC to stealthily execute code with elevated permissions. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.10.0 |100 <<uac-bypass-via-diskcleanup-scheduled-task-hijack-history, Version history>>
+|<<potential-outgoing-rdp-connection-by-unusual-process, Potential Outgoing RDP Connection by Unusual Process>> |Adversaries may attempt to connect to a remote system over Windows Remote Desktop Protocol (RDP) to achieve lateral movement. Adversaries may avoid using the Microsoft Terminal Services Client (mstsc.exe) binary to establish an RDP connection to evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend] |8.3.0 |3
 
-|<<uac-bypass-via-icmluautil-elevated-com-interface, UAC Bypass via ICMLuaUtil Elevated COM Interface>> |Identifies User Account Control (UAC) bypass attempts via the ICMLuaUtil Elevated COM interface. Attackers may attempt to bypass UAC to stealthily execute code with elevated permissions. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.11.0 |101 <<uac-bypass-via-icmluautil-elevated-com-interface-history, Version history>>
+|<<potential-pass-the-hash-pth-attempt, Potential Pass-the-Hash (PtH) Attempt>> |Adversaries may pass the hash using stolen password hashes to move laterally within an environment, bypassing normal system access controls. Pass the hash (PtH) is a method of authenticating as a user without having access to the user's cleartext password. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement] |8.4.0 |3
 
-|<<uac-bypass-via-windows-firewall-snap-in-hijack, UAC Bypass via Windows Firewall Snap-In Hijack>> |Identifies attempts to bypass User Account Control (UAC) by hijacking the Microsoft Management Console (MMC) Windows Firewall snap-in. Attackers bypass UAC to stealthily execute code with elevated permissions. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Investigation Guide]  |7.11.0 |102 <<uac-bypass-via-windows-firewall-snap-in-hijack-history, Version history>>
+|<<potential-password-spraying-of-microsoft-365-user-accounts, Potential Password Spraying of Microsoft 365 User Accounts>> |Identifies a high number (25) of failed Microsoft 365 user authentication attempts from a single IP address within 30 minutes, which could be indicative of a password spraying attack. An adversary may attempt a password spraying attack to obtain unauthorized access to user accounts. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Identity and Access Audit], [Tactic: Credential Access] |8.8.0 |207
 
-|<<unauthorized-access-to-an-okta-application, Unauthorized Access to an Okta Application>> |Identifies unauthorized access attempts to Okta applications. |[Elastic] [Identity] [Okta] [Continuous Monitoring] [SecOps] [Identity and Access]  |7.16.0 |102 <<unauthorized-access-to-an-okta-application-history, Version history>>
+|<<potential-persistence-through-motd-file-creation-detected, Potential Persistence Through MOTD File Creation Detected>> |Message of the day (MOTD) is the message that is presented to the user when a user connects to a Linux server via SSH or a serial connection. Linux systems contain several default MOTD files located in the "/etc/update-motd.d/" and "/usr/lib/update-notifier/" directories. These scripts run as the root user every time a user connects over SSH or a serial connection. Adversaries may create malicious MOTD files that grant them persistence onto the target every time a user connects to the system by executing a backdoor script or command. This rule detects the creation of potentially malicious files within the default MOTD file directories. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.6.0 |9
 
-|<<uncommon-registry-persistence-change, Uncommon Registry Persistence Change>> |Detects changes to registry persistence keys that are not commonly used or modified by legitimate programs. This could be an indication of an adversary's attempt to persist in a stealthy manner. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<uncommon-registry-persistence-change-history, Version history>>
+|<<potential-persistence-through-run-control-detected, Potential Persistence Through Run Control Detected>> |This rule monitors the creation/alteration of the rc.local file by a previously unknown process executable through the use of the new terms rule type. The /etc/rc.local file is used to start custom applications, services, scripts or commands during start-up. The rc.local file has mostly been replaced by Systemd. However, through the "systemd-rc-local-generator", rc.local files can be converted to services that run at boot. Adversaries may alter rc.local to execute malicious code at start-up, and gain persistence onto the system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.6.0 |110
 
-|<<unexpected-child-process-of-macos-screensaver-engine, Unexpected Child Process of macOS Screensaver Engine>> |Identifies when a child process is spawned by the screensaver engine process, which is consistent with an attacker's malicious payload being executed after the screensaver activated on the endpoint. An adversary can maintain persistence on a macOS endpoint by creating a malicious screensaver (.saver) file and configuring the screensaver plist file to execute code each time the screensaver is activated. |[Elastic] [Host] [macOS] [Threat Detection] [Persistence]  |7.16.0 |100 <<unexpected-child-process-of-macos-screensaver-engine-history, Version history>>
+|<<potential-persistence-through-systemd-udevd, Potential Persistence Through Systemd-udevd>> |Monitors for the creation of rule files that are used by systemd-udevd to manage device nodes and handle kernel device events in the Linux operating system. Systemd-udevd can be exploited for persistence by adversaries by creating malicious udev rules that trigger on specific events, executing arbitrary commands or payloads whenever a certain device is plugged in or recognized by the system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.6.0 |3
 
-|<<unusual-aws-command-for-a-user, Unusual AWS Command for a User>> |A machine learning job detected an AWS API command that, while not inherently suspicious or abnormal, is being made by a user context that does not normally use the command. This can be the result of compromised credentials or keys as someone uses a valid account to persist, move laterally, or exfiltrate data. |[Elastic] [Cloud] [AWS] [ML] [Investigation Guide]  |7.9.0 |102 <<unusual-aws-command-for-a-user-history, Version history>>
+|<<potential-persistence-through-init-d-detected, Potential Persistence Through init.d Detected>> |Files that are placed in the /etc/init.d/ directory in Unix can be used to start custom applications, services, scripts or commands during start-up. Init.d has been mostly replaced in favor of Systemd. However, the "systemd-sysv-generator" can convert init.d files to service unit files that run at boot. Adversaries may add or alter files located in the /etc/init.d/ directory to execute malicious code upon boot in order to gain persistence on the system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.6.0 |9
 
-|<<unusual-child-process-from-a-system-virtual-process, Unusual Child Process from a System Virtual Process>> |Identifies a suspicious child process of the Windows virtual system process, which could indicate code injection. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.10.0 |102 <<unusual-child-process-from-a-system-virtual-process-history, Version history>>
+|<<potential-persistence-via-atom-init-script-modification, Potential Persistence via Atom Init Script Modification>> |Identifies modifications to the Atom desktop text editor Init File. Adversaries may add malicious JavaScript code to the init.coffee file that will be executed upon the Atom application opening. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<unusual-child-process-of-dns.exe, Unusual Child Process of dns.exe>> |Identifies an unexpected process spawning from dns.exe, the process responsible for Windows DNS server services, which may indicate activity related to remote code execution or other forms of exploitation. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access] [Investigation Guide]  |7.10.0 |102 <<unusual-child-process-of-dns.exe-history, Version history>>
+|<<potential-persistence-via-login-hook, Potential Persistence via Login Hook>> |Identifies the creation or modification of the login window property list (plist). Adversaries may modify plist files to run a program during system boot or user login for persistence. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<unusual-child-processes-of-rundll32, Unusual Child Processes of RunDLL32>> |Identifies child processes of unusual instances of RunDLL32 where the command line parameters were suspicious. Misuse of RunDLL32 could indicate malicious activity. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.10.0 |101 <<unusual-child-processes-of-rundll32-history, Version history>>
+|<<potential-persistence-via-periodic-tasks, Potential Persistence via Periodic Tasks>> |Identifies the creation or modification of the default configuration for periodic tasks. Adversaries may abuse periodic tasks to execute malicious code or maintain persistence. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<unusual-city-for-an-aws-command, Unusual City For an AWS Command>> |A machine learning job detected AWS command activity that, while not inherently suspicious or abnormal, is sourcing from a geolocation (city) that is unusual for the command. This can be the result of compromised credentials or keys being used by a threat actor in a different geography than the authorized user(s). |[Elastic] [Cloud] [AWS] [ML] [Investigation Guide]  |7.9.0 |102 <<unusual-city-for-an-aws-command-history, Version history>>
+|<<potential-persistence-via-time-provider-modification, Potential Persistence via Time Provider Modification>> |Identifies modification of the Time Provider. Adversaries may establish persistence by registering and enabling a malicious DLL as a time provider. Windows uses the time provider architecture to obtain accurate time stamps from other network devices or clients in the network. Time providers are implemented in the form of a DLL file which resides in the System32 folder. The service W32Time initiates during the startup of Windows and loads w32time.dll. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<unusual-country-for-an-aws-command, Unusual Country For an AWS Command>> |A machine learning job detected AWS command activity that, while not inherently suspicious or abnormal, is sourcing from a geolocation (country) that is unusual for the command. This can be the result of compromised credentials or keys being used by a threat actor in a different geography than the authorized user(s). |[Elastic] [Cloud] [AWS] [ML] [Investigation Guide]  |7.9.0 |102 <<unusual-country-for-an-aws-command-history, Version history>>
+|<<potential-port-monitor-or-print-processor-registration-abuse, Potential Port Monitor or Print Processor Registration Abuse>> |Identifies port monitor and print processor registry modifications. Adversaries may abuse port monitor and print processors to run malicious DLLs during system boot that will be executed as SYSTEM for privilege escalation and/or persistence, if permissions allow writing a fully-qualified pathname for that DLL. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<unusual-dns-activity, Unusual DNS Activity>> |A machine learning job detected a rare and unusual DNS query that indicate network activity with unusual DNS domains. This can be due to initial access, persistence, command-and-control, or exfiltration activity. For example, when a user clicks on a link in a phishing email or opens a malicious document, a request may be sent to download and run a payload from an uncommon domain. When malware is already running, it may send requests to an uncommon DNS domain the malware uses for command-and-control communication. |[Elastic] [Network] [Threat Detection] [ML] [Command and Control]  |7.7.0 |100 <<unusual-dns-activity-history, Version history>>
+|<<potential-powershell-hacktool-script-by-author, Potential PowerShell HackTool Script by Author>> |Detects known PowerShell offensive tooling author's name in PowerShell scripts. Attackers commonly use out-of-the-box offensive tools without modifying the code, which may still contain the author artifacts. This rule identifies common author handles found in popular PowerShell scripts used for red team exercises. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: PowerShell Logs] |8.3.0 |1
 
-|<<unusual-executable-file-creation-by-a-system-critical-process, Unusual Executable File Creation by a System Critical Process>> |Identifies an unexpected executable file being created or modified by a Windows system critical process, which may indicate activity related to remote code execution or other forms of exploitation. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.10.0 |102 <<unusual-executable-file-creation-by-a-system-critical-process-history, Version history>>
+|<<potential-powershell-hacktool-script-by-function-names, Potential PowerShell HackTool Script by Function Names>> |Detects known PowerShell offensive tooling functions names in PowerShell scripts. Attackers commonly use out-of-the-box offensive tools without modifying the code. This rule aim is to take advantage of that. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: PowerShell Logs] |8.12.0 |111
 
-|<<unusual-file-creation-alternate-data-stream, Unusual File Creation - Alternate Data Stream>> |Identifies suspicious creation of Alternate Data Streams on highly targeted files. This is uncommon for legitimate files and sometimes done by adversaries to hide malware. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide]  |7.12.0 |102 <<unusual-file-creation-alternate-data-stream-history, Version history>>
+|<<potential-powershell-pass-the-hash-relay-script, Potential PowerShell Pass-the-Hash/Relay Script>> |Detects PowerShell scripts that can execute pass-the-hash (PtH) attacks, intercept and relay NTLM challenges, and carry out other man-in-the-middle (MitM) attacks. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.3.0 |1
 
-|<<unusual-file-modification-by-dns.exe, Unusual File Modification by dns.exe>> |Identifies an unexpected file being modified by dns.exe, the process responsible for Windows DNS Server services, which may indicate activity related to remote code execution or other forms of exploitation. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access]  |7.10.0 |101 <<unusual-file-modification-by-dns.exe-history, Version history>>
+|<<potential-privacy-control-bypass-via-localhost-secure-copy, Potential Privacy Control Bypass via Localhost Secure Copy>> |Identifies use of the Secure Copy Protocol (SCP) to copy files locally by abusing the auto addition of the Secure Shell Daemon (sshd) to the authorized application list for Full Disk Access. This may indicate attempts to bypass macOS privacy controls to access sensitive files. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<unusual-hour-for-a-user-to-logon, Unusual Hour for a User to Logon>> |A machine learning job detected a user logging in at a time of day that is unusual for the user. This can be due to credentialed access via a compromised account when the user and the threat actor are in different time zones. In addition, unauthorized user activity often takes place during non-business hours. |[Elastic] [Authentication] [Threat Detection] [ML] [Initial Access]  |7.14.0 |100 <<unusual-hour-for-a-user-to-logon-history, Version history>>
+|<<potential-privacy-control-bypass-via-tccdb-modification, Potential Privacy Control Bypass via TCCDB Modification>> |Identifies the use of sqlite3 to directly modify the Transparency, Consent, and Control (TCC) SQLite database. This may indicate an attempt to bypass macOS privacy controls, including access to sensitive resources like the system camera, microphone, address book, and calendar. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |107
 
-|<<unusual-linux-network-activity, Unusual Linux Network Activity>> |Identifies Linux processes that do not usually use the network but have unexpected network activity, which can indicate command-and-control, lateral movement, persistence, or data exfiltration activity. A process with unusual network activity can denote process exploitation or injection, where the process is used to run persistence mechanisms that allow a malicious actor remote access or control of the host, data exfiltration, and execution of unauthorized network applications. |[Elastic] [Host] [Linux] [Threat Detection] [ML]  |7.7.0 |100 <<unusual-linux-network-activity-history, Version history>>
+|<<potential-privilege-escalation-through-writable-docker-socket, Potential Privilege Escalation through Writable Docker Socket>> |This rule monitors for the usage of Docker runtime sockets to escalate privileges on Linux systems. Docker sockets by default are only be writable by the root user and docker group. Attackers that have permissions to write to these sockets may be able to create and run a container that allows them to escalate privileges and gain further access onto the host file system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Domain: Container], [Data Source: Elastic Defend] |8.3.0 |5
 
-|<<unusual-linux-network-connection-discovery, Unusual Linux Network Connection Discovery>> |Looks for commands related to system network connection discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used by a threat actor to engage in system network connection discovery in order to increase their understanding of connected services and systems. This information may be used to shape follow-up behaviors such as lateral movement or additional discovery. |[Elastic] [Host] [Linux] [Threat Detection] [ML]  |7.10.0 |100 <<unusual-linux-network-connection-discovery-history, Version history>>
+|<<potential-privilege-escalation-via-cve-2023-4911, Potential Privilege Escalation via CVE-2023-4911>> |This rule detects potential privilege escalation attempts through Looney Tunables (CVE-2023-4911). Looney Tunables is a buffer overflow vulnerability in GNU C Library's dynamic loader's processing of the GLIBC_TUNABLES environment variable. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.6.0 |4
 
-|<<unusual-linux-network-port-activity, Unusual Linux Network Port Activity>> |Identifies unusual destination port activity that can indicate command-and-control, persistence mechanism, or data exfiltration activity. Rarely used destination port activity is generally unusual in Linux fleets, and can indicate unauthorized access or threat actor activity. |[Elastic] [Host] [Linux] [Threat Detection] [ML]  |7.7.0 |100 <<unusual-linux-network-port-activity-history, Version history>>
+|<<potential-privilege-escalation-via-container-misconfiguration, Potential Privilege Escalation via Container Misconfiguration>> |This rule monitors for the execution of processes that interact with Linux containers through an interactive shell without root permissions. Utilities such as runc and ctr are universal command-line utilities leveraged to interact with containers via root permissions. On systems where the access to these utilities are misconfigured, attackers might be able to create and run a container that mounts the root folder or spawn a privileged container vulnerable to a container escape attack, which might allow them to escalate privileges and gain further access onto the host file system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Domain: Container], [Data Source: Elastic Defend] |8.3.0 |5
 
-|<<unusual-linux-process-calling-the-metadata-service, Unusual Linux Process Calling the Metadata Service>> |Looks for anomalous access to the metadata service by an unusual process. The metadata service may be targeted in order to harvest credentials or user data scripts containing secrets. |[Elastic] [Host] [Linux] [Threat Detection] [ML] [Credential Access]  |7.10.0 |100 <<unusual-linux-process-calling-the-metadata-service-history, Version history>>
+|<<potential-privilege-escalation-via-enlightenment, Potential Privilege Escalation via Enlightenment>> |Identifies an attempt to exploit a local privilege escalation CVE-2022-37706 via a flaw in Linux window manager package Enlightenment. enlightenment_sys in Enlightenment before 0.25.4 allows local users to gain privileges because it is setuid root, and the system library function mishandles pathnames that begin with a /dev/.. substring. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.11.0 |2
 
-|<<unusual-linux-process-discovery-activity, Unusual Linux Process Discovery Activity>> |Looks for commands related to system process discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used by a threat actor to engage in system process discovery in order to increase their understanding of software applications running on a target host or network. This may be a precursor to selection of a persistence mechanism or a method of privilege elevation. |[Elastic] [Host] [Linux] [Threat Detection] [ML]  |7.10.0 |100 <<unusual-linux-process-discovery-activity-history, Version history>>
+|<<potential-privilege-escalation-via-installerfiletakeover, Potential Privilege Escalation via InstallerFileTakeOver>> |Identifies a potential exploitation of InstallerTakeOver (CVE-2021-41379) default PoC execution. Successful exploitation allows an unprivileged user to escalate privileges to SYSTEM. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Resources: Investigation Guide], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<unusual-linux-system-information-discovery-activity, Unusual Linux System Information Discovery Activity>> |Looks for commands related to system information discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used to engage in system information discovery in order to gather detailed information about system configuration and software versions. This may be a precursor to selection of a persistence mechanism or a method of privilege elevation. |[Elastic] [Host] [Linux] [Threat Detection] [ML]  |7.10.0 |100 <<unusual-linux-system-information-discovery-activity-history, Version history>>
+|<<potential-privilege-escalation-via-linux-dac-permissions, Potential Privilege Escalation via Linux DAC permissions>> |Identifies potential privilege escalation exploitation of DAC (Discretionary access control) file permissions. The rule identifies exploitation of DAC checks on sensitive file paths via suspicious processes whose capabilities include CAP_DAC_OVERRIDE (where a process can bypass all read write and execution checks) or CAP_DAC_READ_SEARCH (where a process can read any file or perform any executable permission on the directories). |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.11.0 |2
 
-|<<unusual-linux-system-network-configuration-discovery, Unusual Linux System Network Configuration Discovery>> |Looks for commands related to system network configuration discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used by a threat actor to engage in system network configuration discovery in order to increase their understanding of connected networks and hosts. This information may be used to shape follow-up behaviors such as lateral movement or additional discovery. |[Elastic] [Host] [Linux] [Threat Detection] [ML]  |7.10.0 |100 <<unusual-linux-system-network-configuration-discovery-history, Version history>>
+|<<potential-privilege-escalation-via-overlayfs, Potential Privilege Escalation via OverlayFS>> |Identifies an attempt to exploit a local privilege escalation (CVE-2023-2640 and CVE-2023-32629) via a flaw in Ubuntu's modifications to OverlayFS. These flaws allow the creation of specialized executables, which, upon execution, grant the ability to escalate privileges to root on the affected machine. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |5
 
-|<<unusual-linux-system-owner-or-user-discovery-activity, Unusual Linux System Owner or User Discovery Activity>> |Looks for commands related to system user or owner discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used to engage in system owner or user discovery in order to identify currently active or primary users of a system. This may be a precursor to additional discovery, credential dumping or privilege elevation activity. |[Elastic] [Host] [Linux] [Threat Detection] [ML]  |7.10.0 |100 <<unusual-linux-system-owner-or-user-discovery-activity-history, Version history>>
+|<<potential-privilege-escalation-via-pkexec, Potential Privilege Escalation via PKEXEC>> |Identifies an attempt to exploit a local privilege escalation in polkit pkexec (CVE-2021-4034) via unsecure environment variable injection. Successful exploitation allows an unprivileged user to escalate to the root user. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<unusual-linux-user-calling-the-metadata-service, Unusual Linux User Calling the Metadata Service>> |Looks for anomalous access to the cloud platform metadata service by an unusual user. The metadata service may be targeted in order to harvest credentials or user data scripts containing secrets. |[Elastic] [Host] [Linux] [Threat Detection] [ML] [Credential Access]  |7.10.0 |100 <<unusual-linux-user-calling-the-metadata-service-history, Version history>>
+|<<potential-privilege-escalation-via-python-cap-setuid, Potential Privilege Escalation via Python cap_setuid>> |This detection rule monitors for the execution of a system command with setuid or setgid capabilities via Python, followed by a uid or gid change to the root user. This sequence of events may indicate successful privilege escalation. Setuid (Set User ID) and setgid (Set Group ID) are Unix-like OS features that enable processes to run with elevated privileges, based on the file owner or group. Threat actors can exploit these attributes to escalate privileges to the privileges that are set on the binary that is being executed. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.3.0 |3
 
-|<<unusual-linux-username, Unusual Linux Username>> |A machine learning job detected activity for a username that is not normally active, which can indicate unauthorized changes, activity by unauthorized users, lateral movement, or compromised credentials. In many organizations, new usernames are not often created apart from specific types of system activities, such as creating new accounts for new employees. These user accounts quickly become active and routine. Events from rarely used usernames can point to suspicious activity. Additionally, automated Linux fleets tend to see activity from rarely used usernames only when personnel log in to make authorized or unauthorized changes, or threat actors have acquired credentials and log in for malicious purposes. Unusual usernames can also indicate pivoting, where compromised credentials are used to try and move laterally from one host to another. |[Elastic] [Host] [Linux] [Threat Detection] [ML] [Initial Access]  |7.7.0 |100 <<unusual-linux-username-history, Version history>>
+|<<potential-privilege-escalation-via-recently-compiled-executable, Potential Privilege Escalation via Recently Compiled Executable>> |This rule monitors a sequence involving a program compilation event followed by its execution and a subsequent alteration of UID permissions to root privileges. This behavior can potentially indicate the execution of a kernel or software privilege escalation exploit. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |4
 
-|<<unusual-login-activity, Unusual Login Activity>> |Identifies an unusually high number of authentication attempts. |[Elastic] [Authentication] [Threat Detection] [ML] [Credential Access]  |7.7.0 |100 <<unusual-login-activity-history, Version history>>
+|<<potential-privilege-escalation-via-sudoers-file-modification, Potential Privilege Escalation via Sudoers File Modification>> |A sudoers file specifies the commands users or groups can run and from which terminals. Adversaries can take advantage of these configurations to execute commands as other users or spawn processes with higher privileges. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.3.0 |103
 
-|<<unusual-network-activity-from-a-windows-system-binary, Unusual Network Activity from a Windows System Binary>> |Identifies network activity from unexpected system applications. This may indicate adversarial activity as these applications are often leveraged by adversaries to execute code and evade detection. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.10.0 |101 <<unusual-network-activity-from-a-windows-system-binary-history, Version history>>
+|<<potential-privilege-escalation-via-uid-int-max-bug-detected, Potential Privilege Escalation via UID INT_MAX Bug Detected>> |This rule monitors for the execution of the systemd-run command by a user with a UID that is larger than the maximum allowed UID size (INT_MAX). Some older Linux versions were affected by a bug which allows user accounts with a UID greater than INT_MAX to escalate privileges by spawning a shell through systemd-run. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |5
 
-|<<unusual-network-connection-via-dllhost, Unusual Network Connection via DllHost>> |Identifies unusual instances of dllhost.exe making outbound network connections. This may indicate adversarial Command and Control activity. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.14.0 |101 <<unusual-network-connection-via-dllhost-history, Version history>>
+|<<potential-privileged-escalation-via-samaccountname-spoofing, Potential Privileged Escalation via SamAccountName Spoofing>> |Identifies a suspicious computer account name rename event, which may indicate an attempt to exploit CVE-2021-42278 to elevate privileges from a standard domain user to a user with domain admin privileges. CVE-2021-42278 is a security vulnerability that allows potential attackers to impersonate a domain controller via samAccountName attribute spoofing. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Privilege Escalation], [Use Case: Active Directory Monitoring], [Data Source: Active Directory], [Use Case: Vulnerability] |8.3.0 |108
 
-|<<unusual-network-connection-via-rundll32, Unusual Network Connection via RunDLL32>> |Identifies unusual instances of rundll32.exe making outbound network connections. This may indicate adversarial Command and Control activity. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide]  |7.6.0 |102 <<unusual-network-connection-via-rundll32-history, Version history>>
+|<<potential-process-injection-from-malicious-document, Potential Process Injection from Malicious Document>> |Identifies child processes of frequently targeted Microsoft Office applications (Word, PowerPoint, Excel) with unusual process arguments and path. This behavior is often observed during exploitation of Office applications or from documents with malicious macros. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Privilege Escalation], [Tactic: Initial Access], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<unusual-network-destination-domain-name, Unusual Network Destination Domain Name>> |A machine learning job detected an unusual network destination domain name. This can be due to initial access, persistence, command-and-control, or exfiltration activity. For example, when a user clicks on a link in a phishing email or opens a malicious document, a request may be sent to download and run a payload from an uncommon web server name. When malware is already running, it may send requests to an uncommon DNS domain the malware uses for command-and-control communication. |[Elastic] [Network] [Threat Detection] [ML]  |7.7.0 |100 <<unusual-network-destination-domain-name-history, Version history>>
+|<<potential-process-injection-via-powershell, Potential Process Injection via PowerShell>> |Detects the use of Windows API functions that are commonly abused by malware and security tools to load malicious code or inject it into remote processes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.3.0 |110
 
-|<<unusual-parent-process-for-cmd.exe, Unusual Parent Process for cmd.exe>> |Identifies a suspicious parent child process relationship with cmd.exe descending from an unusual process. |[Elastic] [Host] [Windows] [Threat Detection] [Execution] [Elastic Endgame]  |7.10.0 |102 <<unusual-parent-process-for-cmd.exe-history, Version history>>
+|<<potential-protocol-tunneling-via-chisel-client, Potential Protocol Tunneling via Chisel Client>> |This rule monitors for common command line flags leveraged by the Chisel client utility followed by a connection attempt. Chisel is a command-line utility used for creating and managing TCP and UDP tunnels, enabling port forwarding and secure communication between machines. Attackers can abuse the Chisel utility to establish covert communication channels, bypass network restrictions, and carry out malicious activities by creating tunnels that allow unauthorized access to internal systems. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Defend] |8.3.0 |5
 
-|<<unusual-parent-child-relationship, Unusual Parent-Child Relationship>> |Identifies Windows programs run from unexpected parent processes. This could indicate masquerading or other strange activity on a system. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation] [Investigation Guide]  |7.6.0 |102 <<unusual-parent-child-relationship-history, Version history>>
+|<<potential-protocol-tunneling-via-chisel-server, Potential Protocol Tunneling via Chisel Server>> |This rule monitors for common command line flags leveraged by the Chisel server utility followed by a received connection within a timespan of 1 minute. Chisel is a command-line utility used for creating and managing TCP and UDP tunnels, enabling port forwarding and secure communication between machines. Attackers can abuse the Chisel utility to establish covert communication channels, bypass network restrictions, and carry out malicious activities by creating tunnels that allow unauthorized access to internal systems. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Defend] |8.3.0 |6
 
-|<<unusual-persistence-via-services-registry, Unusual Persistence via Services Registry>> |Identifies processes modifying the services registry key directly, instead of through the expected Windows APIs. This could be an indication of an adversary attempting to stealthily persist through abnormal service creation or modification of an existing service. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence]  |7.11.0 |100 <<unusual-persistence-via-services-registry-history, Version history>>
+|<<potential-protocol-tunneling-via-earthworm, Potential Protocol Tunneling via EarthWorm>> |Identifies the execution of the EarthWorm tunneler. Adversaries may tunnel network communications to and from a victim system within a separate protocol to avoid detection and network filtering, or to enable access to otherwise unreachable systems. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<unusual-print-spooler-child-process, Unusual Print Spooler Child Process>> |Detects unusual Print Spooler service (spoolsv.exe) child processes. This may indicate an attempt to exploit privilege escalation vulnerabilities related to the Printing Service on Windows. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |7.14.0 |100 <<unusual-print-spooler-child-process-history, Version history>>
+|<<potential-pspy-process-monitoring-detected, Potential Pspy Process Monitoring Detected>> |This rule leverages auditd to monitor for processes scanning different processes within the /proc directory using the openat syscall. This is a strong indication for the usage of the pspy utility. Attackers may leverage the pspy process monitoring utility to monitor system processes without requiring root permissions, in order to find potential privilege escalation vectors. |[Data Source: Auditd Manager], [Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery] |8.3.0 |7
 
-|<<unusual-process-execution-path-alternate-data-stream, Unusual Process Execution Path - Alternate Data Stream>> |Identifies processes running from an Alternate Data Stream. This is uncommon for legitimate processes and sometimes done by adversaries to hide malware. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Elastic Endgame]  |7.11.0 |101 <<unusual-process-execution-path-alternate-data-stream-history, Version history>>
+|<<potential-ransomware-behavior-high-count-of-readme-files-by-system, Potential Ransomware Behavior - High count of Readme files by System>> |This rule identifies a high number (20) of file creation event by the System virtual process from the same host and with same file name containing keywords similar to ransomware note files and all within a short time period. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Impact], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |1
 
-|<<unusual-process-for-a-linux-host, Unusual Process For a Linux Host>> |Identifies rare processes that do not usually run on individual hosts, which can indicate execution of unauthorized services, malware, or persistence mechanisms. Processes are considered rare when they only run occasionally as compared with other processes running on the host. |[Elastic] [Host] [Linux] [Threat Detection] [ML] [Persistence]  |7.7.0 |100 <<unusual-process-for-a-linux-host-history, Version history>>
+|<<potential-ransomware-note-file-dropped-via-smb, Potential Ransomware Note File Dropped via SMB>> |Identifies an incoming SMB connection followed by the creation of a file with a name similar to ransomware note files. This may indicate a remote ransomware attack via the SMB protocol. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Impact], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |1
 
-|<<unusual-process-for-a-windows-host, Unusual Process For a Windows Host>> |Identifies rare processes that do not usually run on individual hosts, which can indicate execution of unauthorized services, malware, or persistence mechanisms. Processes are considered rare when they only run occasionally as compared with other processes running on the host. |[Elastic] [Host] [Windows] [Threat Detection] [ML] [Persistence] [Investigation Guide]  |7.7.0 |102 <<unusual-process-for-a-windows-host-history, Version history>>
+|<<potential-remote-code-execution-via-web-server, Potential Remote Code Execution via Web Server>> |Identifies suspicious commands executed via a web server, which may suggest a vulnerability and remote shell access. Attackers may exploit a vulnerability in a web application to execute commands via a web server, or place a backdoor file that can be abused to gain code execution as a mechanism for persistence. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Initial Access], [Data Source: Elastic Endgame], [Use Case: Vulnerability], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |7
 
-|<<unusual-process-network-connection, Unusual Process Network Connection>> |Identifies network activity from unexpected system applications. This may indicate adversarial activity as these applications are often leveraged by adversaries to execute code and evade detection. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide]  |7.6.0 |102 <<unusual-process-network-connection-history, Version history>>
+|<<potential-remote-credential-access-via-registry, Potential Remote Credential Access via Registry>> |Identifies remote access to the registry to potentially dump credential data from the Security Account Manager (SAM) registry hive in preparation for credential access and privileges elevation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Credential Access], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |111
 
-|<<unusual-service-host-child-process-childless-service, Unusual Service Host Child Process - Childless Service>> |Identifies unusual child processes of Service Host (svchost.exe) that traditionally do not spawn any child processes. This may indicate a code injection or an equivalent form of exploitation. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Privilege Escalation]  |7.11.0 |101 <<unusual-service-host-child-process-childless-service-history, Version history>>
+|<<potential-remote-desktop-shadowing-activity, Potential Remote Desktop Shadowing Activity>> |Identifies the modification of the Remote Desktop Protocol (RDP) Shadow registry or the execution of processes indicative of an active RDP shadowing session. An adversary may abuse the RDP Shadowing feature to spy on or control other users active RDP sessions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<unusual-source-ip-for-a-user-to-logon-from, Unusual Source IP for a User to Logon from>> |A machine learning job detected a user logging in from an IP address that is unusual for the user. This can be due to credentialed access via a compromised account when the user and the threat actor are in different locations. An unusual source IP address for a username could also be due to lateral movement when a compromised account is used to pivot between hosts. |[Elastic] [Authentication] [Threat Detection] [ML] [Initial Access]  |7.14.0 |100 <<unusual-source-ip-for-a-user-to-logon-from-history, Version history>>
+|<<potential-remote-desktop-tunneling-detected, Potential Remote Desktop Tunneling Detected>> |Identifies potential use of an SSH utility to establish RDP over a reverse SSH Tunnel. This can be used by attackers to enable routing of network packets that would otherwise not reach their intended destination. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Tactic: Lateral Movement], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
 
-|<<unusual-sudo-activity, Unusual Sudo Activity>> |Looks for sudo activity from an unusual user context. An unusual sudo user could be due to troubleshooting activity or it could be a sign of credentialed access via compromised accounts. |[Elastic] [Host] [Linux] [Threat Detection] [ML]  |7.10.0 |100 <<unusual-sudo-activity-history, Version history>>
+|<<potential-remote-file-execution-via-msiexec, Potential Remote File Execution via MSIEXEC>> |Identifies the execution of the built-in Windows Installer, msiexec.exe, to install a remote package. Adversaries may abuse msiexec.exe to launch local or network accessible MSI files. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |3
 
-|<<unusual-web-request, Unusual Web Request>> |A machine learning job detected a rare and unusual URL that indicates unusual web browsing activity. This can be due to initial access, persistence, command-and-control, or exfiltration activity. For example, in a strategic web compromise or watering hole attack, when a trusted website is compromised to target a particular sector or organization, targeted users may receive emails with uncommon URLs for trusted websites. These URLs can be used to download and run a payload. When malware is already running, it may send requests to uncommon URLs on trusted websites the malware uses for command-and-control communication. When rare URLs are observed being requested for a local web server by a remote source, these can be due to web scanning, enumeration or attack traffic, or they can be due to bots and web scrapers which are part of common Internet background traffic. |[Elastic] [Network] [Threat Detection] [ML] [Command and Control]  |7.7.0 |100 <<unusual-web-request-history, Version history>>
+|<<potential-reverse-shell, Potential Reverse Shell>> |This detection rule identifies suspicious network traffic patterns associated with TCP reverse shell activity. This activity consists of a parent-child relationship where a network event is followed by the creation of a shell process. An attacker may establish a Linux TCP reverse shell to gain remote access to a target system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |8
 
-|<<unusual-web-user-agent, Unusual Web User Agent>> |A machine learning job detected a rare and unusual user agent indicating web browsing activity by an unusual process other than a web browser. This can be due to persistence, command-and-control, or exfiltration activity. Uncommon user agents coming from remote sources to local destinations are often the result of scanners, bots, and web scrapers, which are part of common Internet background traffic. Much of this is noise, but more targeted attacks on websites using tools like Burp or SQLmap can sometimes be discovered by spotting uncommon user agents. Uncommon user agents in traffic from local sources to remote destinations can be any number of things, including harmless programs like weather monitoring or stock-trading programs. However, uncommon user agents from local sources can also be due to malware or scanning activity. |[Elastic] [Network] [Threat Detection] [ML] [Command and Control]  |7.7.0 |100 <<unusual-web-user-agent-history, Version history>>
+|<<potential-reverse-shell-activity-via-terminal, Potential Reverse Shell Activity via Terminal>> |Identifies the execution of a shell process with suspicious arguments which may be indicative of reverse shell activity. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<unusual-windows-network-activity, Unusual Windows Network Activity>> |Identifies Windows processes that do not usually use the network but have unexpected network activity, which can indicate command-and-control, lateral movement, persistence, or data exfiltration activity. A process with unusual network activity can denote process exploitation or injection, where the process is used to run persistence mechanisms that allow a malicious actor remote access or control of the host, data exfiltration, and execution of unauthorized network applications. |[Elastic] [Host] [Windows] [Threat Detection] [ML]  |7.7.0 |100 <<unusual-windows-network-activity-history, Version history>>
+|<<potential-reverse-shell-via-background-process, Potential Reverse Shell via Background Process>> |Monitors for the execution of background processes with process arguments capable of opening a socket in the /dev/tcp channel. This may indicate the creation of a backdoor reverse connection, and should be investigated further. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |4
 
-|<<unusual-windows-path-activity, Unusual Windows Path Activity>> |Identifies processes started from atypical folders in the file system, which might indicate malware execution or persistence mechanisms. In corporate Windows environments, software installation is centrally managed and it is unusual for programs to be executed from user or temporary directories. Processes executed from these locations can denote that a user downloaded software directly from the Internet or a malicious script or macro executed malware. |[Elastic] [Host] [Windows] [Threat Detection] [ML] [Persistence]  |7.7.0 |100 <<unusual-windows-path-activity-history, Version history>>
+|<<potential-reverse-shell-via-child, Potential Reverse Shell via Child>> |This detection rule identifies suspicious network traffic patterns associated with TCP reverse shell activity. This activity consists of a network event that is followed by the creation of a shell process with suspicious command line arguments. An attacker may establish a Linux TCP reverse shell to gain remote access to a target system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |2
 
-|<<unusual-windows-process-calling-the-metadata-service, Unusual Windows Process Calling the Metadata Service>> |Looks for anomalous access to the metadata service by an unusual process. The metadata service may be targeted in order to harvest credentials or user data scripts containing secrets. |[Elastic] [Host] [Windows] [Threat Detection] [ML] [Credential Access]  |7.10.0 |100 <<unusual-windows-process-calling-the-metadata-service-history, Version history>>
+|<<potential-reverse-shell-via-java, Potential Reverse Shell via Java>> |This detection rule identifies the execution of a Linux shell process from a Java JAR application post an incoming network connection. This behavior may indicate reverse shell activity via a Java application. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |8
 
-|<<unusual-windows-remote-user, Unusual Windows Remote User>> |A machine learning job detected an unusual remote desktop protocol (RDP) username, which can indicate account takeover or credentialed persistence using compromised accounts. RDP attacks, such as BlueKeep, also tend to use unusual usernames. |[Elastic] [Host] [Windows] [Threat Detection] [ML] [Initial Access]  |7.7.0 |100 <<unusual-windows-remote-user-history, Version history>>
+|<<potential-reverse-shell-via-suspicious-binary, Potential Reverse Shell via Suspicious Binary>> |This detection rule detects the creation of a shell through a chain consisting of the execution of a suspicious binary (located in a commonly abused location or executed manually) followed by a network event and ending with a shell being spawned. Stageless reverse tcp shells display this behaviour. Attackers may spawn reverse shells to establish persistence onto a target system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |7
 
-|<<unusual-windows-service, Unusual Windows Service>> |A machine learning job detected an unusual Windows service, This can indicate execution of unauthorized services, malware, or persistence mechanisms. In corporate Windows environments, hosts do not generally run many rare or unique services. This job helps detect malware and persistence mechanisms that have been installed and run as a service. |[Elastic] [Host] [Windows] [Threat Detection] [ML] [Persistence]  |7.7.0 |100 <<unusual-windows-service-history, Version history>>
+|<<potential-reverse-shell-via-suspicious-child-process, Potential Reverse Shell via Suspicious Child Process>> |This detection rule detects the creation of a shell through a suspicious process chain. Any reverse shells spawned by the specified utilities that are initialized from a single process followed by a network connection attempt will be captured through this rule. Attackers may spawn reverse shells to establish persistence onto a target system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |9
 
-|<<unusual-windows-user-calling-the-metadata-service, Unusual Windows User Calling the Metadata Service>> |Looks for anomalous access to the cloud platform metadata service by an unusual user. The metadata service may be targeted in order to harvest credentials or user data scripts containing secrets. |[Elastic] [Host] [Windows] [Threat Detection] [ML] [Credential Access]  |7.10.0 |100 <<unusual-windows-user-calling-the-metadata-service-history, Version history>>
+|<<potential-reverse-shell-via-udp, Potential Reverse Shell via UDP>> |This detection rule identifies suspicious network traffic patterns associated with UDP reverse shell activity. This activity consists of a sample of an execve, socket and connect syscall executed by the same process, where the auditd.data.a0-1 indicate a UDP connection, ending with an egress connection event. An attacker may establish a Linux UDP reverse shell to bypass traditional firewall restrictions and gain remote access to a target system covertly. |[Data Source: Auditd Manager], [Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution] |8.6.0 |6
 
-|<<unusual-windows-user-privilege-elevation-activity, Unusual Windows User Privilege Elevation Activity>> |A machine learning job detected an unusual user context switch, using the runas command or similar techniques, which can indicate account takeover or privilege escalation using compromised accounts. Privilege elevation using tools like runas are more commonly used by domain and network administrators than by regular Windows users. |[Elastic] [Host] [Windows] [Threat Detection] [ML] [Privilege Escalation]  |7.7.0 |100 <<unusual-windows-user-privilege-elevation-activity-history, Version history>>
+|<<potential-ssh-it-ssh-worm-downloaded, Potential SSH-IT SSH Worm Downloaded>> |Identifies processes that are capable of downloading files with command line arguments containing URLs to SSH-IT's autonomous SSH worm. This worm intercepts outgoing SSH connections every time a user uses ssh. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |3
 
-|<<unusual-windows-username, Unusual Windows Username>> |A machine learning job detected activity for a username that is not normally active, which can indicate unauthorized changes, activity by unauthorized users, lateral movement, or compromised credentials. In many organizations, new usernames are not often created apart from specific types of system activities, such as creating new accounts for new employees. These user accounts quickly become active and routine. Events from rarely used usernames can point to suspicious activity. Additionally, automated Linux fleets tend to see activity from rarely used usernames only when personnel log in to make authorized or unauthorized changes, or threat actors have acquired credentials and log in for malicious purposes. Unusual usernames can also indicate pivoting, where compromised credentials are used to try and move laterally from one host to another. |[Elastic] [Host] [Windows] [Threat Detection] [ML] [Initial Access]  |7.7.0 |100 <<unusual-windows-username-history, Version history>>
+|<<potential-syn-based-network-scan-detected, Potential SYN-Based Network Scan Detected>> |This rule identifies a potential SYN-Based port scan. A SYN port scan is a technique employed by attackers to scan a target network for open ports by sending SYN packets to multiple ports and observing the response. Attackers use this method to identify potential entry points or services that may be vulnerable to exploitation, allowing them to launch targeted attacks or gain unauthorized access to the system or network, compromising its security and potentially leading to data breaches or further malicious activities. This rule proposes threshold logic to check for connection attempts from one source host to 10 or more destination ports using 2 or less packets per port. |[Domain: Network], [Tactic: Discovery], [Tactic: Reconnaissance], [Use Case: Network Security Monitoring] |8.3.0 |5
 
-|<<user-account-creation, User Account Creation>> |Identifies attempts to create new users. This is sometimes done by attackers to increase access or establish persistence on a system or domain. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.6.0 |102 <<user-account-creation-history, Version history>>
+|<<potential-secure-file-deletion-via-sdelete-utility, Potential Secure File Deletion via SDelete Utility>> |Detects file name patterns generated by the use of Sysinternals SDelete utility to securely delete a file via multiple file overwrite and rename operations. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Impact], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|<<user-added-as-owner-for-azure-application, User Added as Owner for Azure Application>> |Identifies when a user is added as an owner for an Azure application. An adversary may add a user account as an owner for an Azure application in order to grant additional permissions and modify the application's configuration using another account. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.10.0 |101 <<user-added-as-owner-for-azure-application-history, Version history>>
+|<<potential-shadow-credentials-added-to-ad-object, Potential Shadow Credentials added to AD Object>> |Identify the modification of the msDS-KeyCredentialLink attribute in an Active Directory Computer or User Object. Attackers can abuse control over the object and create a key pair, append to raw public key in the attribute, and obtain persistent and stealthy access to the target user or computer object. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Active Directory], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring] |8.3.0 |108
 
-|<<user-added-as-owner-for-azure-service-principal, User Added as Owner for Azure Service Principal>> |Identifies when a user is added as an owner for an Azure service principal. The service principal object defines what the application can do in the specific tenant, who can access the application, and what resources the app can access. A service principal object is created when an application is given permission to access resources in a tenant. An adversary may add a user account as an owner for a service principal and use that account in order to define what an application can do in the Azure AD tenant. |[Elastic] [Cloud] [Azure] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.10.0 |101 <<user-added-as-owner-for-azure-service-principal-history, Version history>>
+|<<potential-shadow-file-read-via-command-line-utilities, Potential Shadow File Read via Command Line Utilities>> |Identifies access to the /etc/shadow file via the commandline using standard system utilities. After elevating privileges to root, threat actors may attempt to read or dump this file in order to gain valid credentials. They may utilize these to move laterally undetected and access additional resources. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.6.0 |208
 
-|<<user-added-to-privileged-group, User Added to Privileged Group>> |Identifies a user being added to a privileged group in Active Directory. Privileged accounts and groups in Active Directory are those to which powerful rights, privileges, and permissions are granted that allow them to perform nearly any action in Active Directory and on domain-joined systems. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.12.0 |102 <<user-added-to-privileged-group-history, Version history>>
+|<<potential-sharprdp-behavior, Potential SharpRDP Behavior>> |Identifies potential behavior of SharpRDP, which is a tool that can be used to perform authenticated command execution against a remote target via Remote Desktop Protocol (RDP) for the purposes of lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend] |8.3.0 |106
 
-|<<user-account-exposed-to-kerberoasting, User account exposed to Kerberoasting>> |Detects when a user account has the servicePrincipalName attribute modified. Attackers can abuse write privileges over a user to configure Service Principle Names (SPNs) so that they can perform Kerberoasting. Administrators can also configure this for legitimate purposes, exposing the account to Kerberoasting. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Active Directory] [Investigation Guide]  |8.2.0 |102 <<user-account-exposed-to-kerberoasting-history, Version history>>
+|<<potential-shell-via-wildcard-injection-detected, Potential Shell via Wildcard Injection Detected>> |This rule monitors for the execution of a set of linux binaries, that are potentially vulnerable to wildcard injection, with suspicious command line flags followed by a shell spawn event. Linux wildcard injection is a type of security vulnerability where attackers manipulate commands or input containing wildcards (e.g., *, ?, []) to execute unintended operations or access sensitive data by tricking the system into interpreting the wildcard characters in unexpected ways. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |5
 
-|<<vnc-virtual-network-computing-from-the-internet, VNC (Virtual Network Computing) from the Internet>> |This rule detects network events that may indicate the use of VNC traffic from the Internet. VNC is commonly used by system administrators to remotely control a system for maintenance or to use shared resources. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. |[Elastic] [Host] [Network] [Threat Detection] [Command and Control] [Host]  |7.6.0 |100 <<vnc-virtual-network-computing-from-the-internet-history, Version history>>
+|<<potential-successful-linux-ftp-brute-force-attack-detected, Potential Successful Linux FTP Brute Force Attack Detected>> |An FTP (file transfer protocol) brute force attack is a method where an attacker systematically tries different combinations of usernames and passwords to gain unauthorized access to an FTP server, and if successful, the impact can include unauthorized data access, manipulation, or theft, compromising the security and integrity of the server and potentially exposing sensitive information. This rule identifies multiple consecutive authentication failures targeting a specific user account from the same source address and within a short time interval, followed by a successful authentication. |[Data Source: Auditd Manager], [Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access] |8.3.0 |7
 
-|<<vnc-virtual-network-computing-to-the-internet, VNC (Virtual Network Computing) to the Internet>> |This rule detects network events that may indicate the use of VNC traffic to the Internet. VNC is commonly used by system administrators to remotely control a system for maintenance or to use shared resources. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. |[Elastic] [Host] [Network] [Threat Detection] [Command and Control] [Host]  |7.6.0 |100 <<vnc-virtual-network-computing-to-the-internet-history, Version history>>
+|<<potential-successful-linux-rdp-brute-force-attack-detected, Potential Successful Linux RDP Brute Force Attack Detected>> |An RDP (Remote Desktop Protocol) brute force attack involves an attacker repeatedly attempting various username and password combinations to gain unauthorized access to a remote computer via RDP, and if successful, the potential impact can include unauthorized control over the compromised system, data theft, or the ability to launch further attacks within the network, jeopardizing the security and confidentiality of the targeted system and potentially compromising the entire network infrastructure. This rule identifies multiple consecutive authentication failures targeting a specific user account within a short time interval, followed by a successful authentication. |[Data Source: Auditd Manager], [Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access] |8.3.0 |7
 
-|<<virtual-machine-fingerprinting, Virtual Machine Fingerprinting>> |An adversary may attempt to get detailed information about the operating system and hardware. This rule identifies common locations used to discover virtual machine hardware by a non-root user. This technique has been used by the Pupy RAT and other malware. |[Elastic] [Host] [Linux] [Threat Detection] [Discovery]  |7.8.0 |100 <<virtual-machine-fingerprinting-history, Version history>>
+|<<potential-successful-ssh-brute-force-attack, Potential Successful SSH Brute Force Attack>> |Identifies multiple SSH login failures followed by a successful one from the same source address. Adversaries can attempt to login into multiple users with a common or known password to gain access to accounts. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access] |8.3.0 |11
 
-|<<virtual-machine-fingerprinting-via-grep, Virtual Machine Fingerprinting via Grep>> |An adversary may attempt to get detailed information about the operating system and hardware. This rule identifies common locations used to discover virtual machine hardware by a non-root user. This technique has been used by the Pupy RAT and other malware. |[Elastic] [Host] [macOS] [Linux] [Threat Detection] [Discovery]  |7.16.0 |100 <<virtual-machine-fingerprinting-via-grep-history, Version history>>
+|<<potential-sudo-hijacking-detected, Potential Sudo Hijacking Detected>> |Identifies the creation of a sudo binary located at /usr/bin/sudo. Attackers may hijack the default sudo binary and replace it with a custom binary or script that can read the user's password in clear text to escalate privileges or enable persistence onto the system every time the sudo binary is executed. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.6.0 |105
 
-|<<virtual-private-network-connection-attempt, Virtual Private Network Connection Attempt>> |Identifies the execution of macOS built-in commands to connect to an existing Virtual Private Network (VPN). Adversaries may use VPN connections to laterally move and control remote systems on a network. |[Elastic] [Host] [macOS] [Threat Detection] [Lateral Movement]  |7.12.0 |100 <<virtual-private-network-connection-attempt-history, Version history>>
+|<<potential-sudo-privilege-escalation-via-cve-2019-14287, Potential Sudo Privilege Escalation via CVE-2019-14287>> |This rule monitors for the execution of a suspicious sudo command that is leveraged in CVE-2019-14287 to escalate privileges to root. Sudo does not verify the presence of the designated user ID and proceeds to execute using a user ID that can be chosen arbitrarily. By using the sudo privileges, the command "sudo -u#-1" translates to an ID of 0, representing the root user. This exploit may work for sudo versions prior to v1.28. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend], [Use Case: Vulnerability], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |4
 
-|<<volume-shadow-copy-deleted-or-resized-via-vssadmin, Volume Shadow Copy Deleted or Resized via VssAdmin>> |Identifies use of vssadmin.exe for shadow copy deletion or resizing on endpoints. This commonly occurs in tandem with ransomware or other destructive attacks. |[Elastic] [Host] [Windows] [Threat Detection] [Impact] [Investigation Guide]  |7.6.0 |102 <<volume-shadow-copy-deleted-or-resized-via-vssadmin-history, Version history>>
+|<<potential-sudo-token-manipulation-via-process-injection, Potential Sudo Token Manipulation via Process Injection>> |This rule detects potential sudo token manipulation attacks through process injection by monitoring the use of a debugger (gdb) process followed by a successful uid change event during the execution of the sudo process. A sudo token manipulation attack is performed by injecting into a process that has a valid sudo token, which can then be used by attackers to activate their own sudo token. This attack requires ptrace to be enabled in conjunction with the existence of a living process that has a valid sudo token with the same uid as the current user. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.3.0 |5
 
-|<<volume-shadow-copy-deletion-via-powershell, Volume Shadow Copy Deletion via PowerShell>> |Identifies the use of the Win32_ShadowCopy class and related cmdlets to achieve shadow copy deletion. This commonly occurs in tandem with ransomware or other destructive attacks. |[Elastic] [Host] [Windows] [Threat Detection] [Impact] [Investigation Guide]  |7.16.0 |102 <<volume-shadow-copy-deletion-via-powershell-history, Version history>>
+|<<potential-suspicious-clipboard-activity-detected, Potential Suspicious Clipboard Activity Detected>> |This rule monitors for the usage of the most common clipboard utilities on unix systems by an uncommon process group leader. Adversaries may collect data stored in the clipboard from users copying information within or between applications. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Collection], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.6.0 |4
 
-|<<volume-shadow-copy-deletion-via-wmic, Volume Shadow Copy Deletion via WMIC>> |Identifies use of wmic.exe for shadow copy deletion on endpoints. This commonly occurs in tandem with ransomware or other destructive attacks. |[Elastic] [Host] [Windows] [Threat Detection] [Impact] [Investigation Guide]  |7.6.0 |102 <<volume-shadow-copy-deletion-via-wmic-history, Version history>>
+|<<potential-suspicious-debugfs-root-device-access, Potential Suspicious DebugFS Root Device Access>> |This rule monitors for the usage of the built-in Linux DebugFS utility to access a disk device without root permissions. Linux users that are part of the "disk" group have sufficient privileges to access all data inside of the machine through DebugFS. Attackers may leverage DebugFS in conjunction with "disk" permissions to read sensitive files owned by root, such as the shadow file, root ssh private keys or other sensitive files that may allow them to further escalate privileges. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |5
 
-|<<wmi-incoming-lateral-movement, WMI Incoming Lateral Movement>> |Identifies processes executed via Windows Management Instrumentation (WMI) on a remote host. This could be indicative of adversary lateral movement, but could be noisy if administrators use WMI to remotely manage hosts. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement]  |7.11.0 |101 <<wmi-incoming-lateral-movement-history, Version history>>
+|<<potential-suspicious-file-edit, Potential Suspicious File Edit>> |This rule monitors for the potential edit of a suspicious file. In Linux, when editing a file through an editor, a temporary .swp file is created. By monitoring for the creation of this .swp file, we can detect potential file edits of suspicious files. The execution of this rule is not a clear sign of the file being edited, as just opening the file through an editor will trigger this event. Attackers may alter any of the files added in this rule to establish persistence, escalate privileges or perform reconnaisance on the system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |4
 
-|<<web-application-suspicious-activity-post-request-declined, Web Application Suspicious Activity: POST Request Declined>> |A POST request to a web application returned a 403 response, which indicates the web application declined to process the request because the action requested was not allowed. |[Elastic] [APM]  |7.6.0 |100 <<web-application-suspicious-activity-post-request-declined-history, Version history>>
+|<<potential-unauthorized-access-via-wildcard-injection-detected, Potential Unauthorized Access via Wildcard Injection Detected>> |This rule monitors for the execution of the "chown" and "chmod" commands with command line flags that could indicate a wildcard injection attack. Linux wildcard injection is a type of security vulnerability where attackers manipulate commands or input containing wildcards (e.g., *, ?, []) to execute unintended operations or access sensitive data by tricking the system into interpreting the wildcard characters in unexpected ways. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |5
 
-|<<web-application-suspicious-activity-unauthorized-method, Web Application Suspicious Activity: Unauthorized Method>> |A request to a web application returned a 405 response, which indicates the web application declined to process the request because the HTTP method is not allowed for the resource. |[Elastic] [APM]  |7.6.0 |100 <<web-application-suspicious-activity-unauthorized-method-history, Version history>>
+|<<potential-upgrade-of-non-interactive-shell, Potential Upgrade of Non-interactive Shell>> |Identifies when a non-interactive terminal (tty) is being upgraded to a fully interactive shell. Attackers may upgrade a simple reverse shell to a fully interactive tty after obtaining initial access to a host, in order to obtain a more stable connection. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |3
 
-|<<web-application-suspicious-activity-sqlmap-user-agent, Web Application Suspicious Activity: sqlmap User Agent>> |This is an example of how to detect an unwanted web client user agent. This search matches the user agent for sqlmap 1.3.11, which is a popular FOSS tool for testing web applications for SQL injection vulnerabilities. |[Elastic] [APM]  |7.6.0 |100 <<web-application-suspicious-activity-sqlmap-user-agent-history, Version history>>
+|<<potential-veeam-credential-access-command, Potential Veeam Credential Access Command>> |Identifies commands that can access and decrypt Veeam credentials stored in MSSQL databases. Attackers can use Veeam Credentials to target backups as part of destructive operations such as Ransomware attacks. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |1
 
-|<<web-shell-detection-script-process-child-of-common-web-processes, Web Shell Detection: Script Process Child of Common Web Processes>> |Identifies suspicious commands executed via a web server, which may suggest a vulnerability and remote shell access. |[Elastic] [Host] [Windows] [Threat Detection] [Persistence] [Investigation Guide]  |7.15.0 |102 <<web-shell-detection-script-process-child-of-common-web-processes-history, Version history>>
+|<<potential-widespread-malware-infection-across-multiple-hosts, Potential Widespread Malware Infection Across Multiple Hosts>> |This rule uses alert data to determine when a malware signature is triggered in multiple hosts. Analysts can use this to prioritize triage and response, as this can potentially indicate a widespread malware infection. |[Domain: Endpoint], [Data Source: Elastic Defend], [Use Case: Threat Detection], [Tactic: Execution], [Rule Type: Higher-Order Rule] |8.13.0 |1
 
-|<<webproxy-settings-modification, WebProxy Settings Modification>> |Identifies the use of the built-in networksetup command to configure webproxy settings. This may indicate an attempt to hijack web browser traffic for credential access via traffic sniffing or redirection. |[Elastic] [Host] [macOS] [Threat Detection] [Credential Access]  |7.12.0 |100 <<webproxy-settings-modification-history, Version history>>
+|<<potential-windows-error-manager-masquerading, Potential Windows Error Manager Masquerading>> |Identifies suspicious instances of the Windows Error Reporting process (WerFault.exe or Wermgr.exe) with matching command-line and process executable values performing outgoing network connections. This may be indicative of a masquerading attempt to evade suspicious child process behavior detections. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
 
-|<<webserver-access-logs-deleted, WebServer Access Logs Deleted>> |Identifies the deletion of WebServer access logs. This may indicate an attempt to evade detection or destroy forensic evidence on a system. |[Elastic] [Host] [Linux] [Windows] [macOS] [Threat Detection] [Defense Evasion]  |7.11.0 |100 <<webserver-access-logs-deleted-history, Version history>>
+|<<potential-windows-session-hijacking-via-ccmexec, Potential Windows Session Hijacking via CcmExec>> |This detection rule identifies when 'SCNotification.exe' loads an untrusted DLL, which is a potential indicator of an attacker attempt to hijack/impersonate a Windows user session. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |1
 
-|<<whoami-process-activity, Whoami Process Activity>> |Identifies suspicious use of whoami.exe which displays user, group, and privileges information for the user who is currently logged on to the local system. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide] [Elastic Endgame]  |7.6.0 |102 <<whoami-process-activity-history, Version history>>
+|<<potential-curl-cve-2023-38545-exploitation, Potential curl CVE-2023-38545 Exploitation>> |Detects potential exploitation of curl CVE-2023-38545 by monitoring for vulnerable command line arguments in conjunction with an unusual command line length. A flaw in curl version <= 8.3 makes curl vulnerable to a heap based buffer overflow during the SOCKS5 proxy handshake. Upgrade to curl version >= 8.4 to patch this vulnerability. This exploit can be executed with and without the use of environment variables. For increased visibility, enable the collection of http_proxy, HTTPS_PROXY and ALL_PROXY environment variables based on the instructions provided in the setup guide of this rule. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Use Case: Vulnerability], [Tactic: Execution], [Data Source: Elastic Defend] |8.6.0 |5
 
-|<<windows-cryptoapi-spoofing-vulnerability-cve-2020-0601-curveball, Windows CryptoAPI Spoofing Vulnerability (CVE-2020-0601 - CurveBall)>> |A spoofing vulnerability exists in the way Windows CryptoAPI (Crypt32.dll) validates Elliptic Curve Cryptography (ECC) certificates. An attacker could exploit the vulnerability by using a spoofed code-signing certificate to sign a malicious executable, making it appear the file was from a trusted, legitimate source. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion]  |7.7.0 |100 <<windows-cryptoapi-spoofing-vulnerability-cve-2020-0601-curveball-history, Version history>>
+|<<potential-macos-ssh-brute-force-detected, Potential macOS SSH Brute Force Detected>> |Identifies a high number (20) of macOS SSH KeyGen process executions from the same host. An adversary may attempt a brute force attack to obtain unauthorized access to user accounts. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.3.0 |108
 
-|<<windows-defender-disabled-via-registry-modification, Windows Defender Disabled via Registry Modification>> |Identifies modifications to the Windows Defender registry settings to disable the service or set the service to be started manually. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.12.0 |102 <<windows-defender-disabled-via-registry-modification-history, Version history>>
+|<<potential-privilege-escalation-via-cve-2022-38028, Potential privilege escalation via CVE-2022-38028>> |Identifies a privilege escalation attempt via exploiting CVE-2022-38028 to hijack the print spooler service execution. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |1
 
-|<<windows-defender-exclusions-added-via-powershell, Windows Defender Exclusions Added via PowerShell>> |Identifies modifications to the Windows Defender configuration settings using PowerShell to add exclusions at the folder directory or process level. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |7.14.0 |102 <<windows-defender-exclusions-added-via-powershell-history, Version history>>
+|<<potentially-successful-mfa-bombing-via-push-notifications, Potentially Successful MFA Bombing via Push Notifications>> |Detects when an attacker abuses the Multi-Factor authentication mechanism by repeatedly issuing login requests until the user eventually accepts the Okta push notification. An adversary may attempt to bypass the Okta MFA policies configured for an organization to obtain unauthorized access. |[Use Case: Identity and Access Audit], [Tactic: Credential Access], [Data Source: Okta] |8.10.0 |209
 
-|<<windows-event-logs-cleared, Windows Event Logs Cleared>> |Identifies attempts to clear Windows event log stores. This is often done by attackers in an attempt to evade detection or destroy forensic evidence on a system. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide]  |7.12.0 |102 <<windows-event-logs-cleared-history, Version history>>
+|<<potentially-suspicious-process-started-via-tmux-or-screen, Potentially Suspicious Process Started via tmux or screen>> |This rule monitors for the execution of suspicious commands via screen and tmux. When launching a command and detaching directly, the commands will be executed in the background via its parent process. Attackers may leverage screen or tmux to execute commands while attempting to evade detection. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |4
 
-|<<windows-firewall-disabled-via-powershell, Windows Firewall Disabled via PowerShell>> |Identifies when the Windows Firewall is disabled using PowerShell cmdlets, which can help attackers evade network constraints, like internet and network lateral communication restrictions. |[Elastic] [Host] [Windows] [Threat Detection] [Defense Evasion] [Investigation Guide] [Elastic Endgame]  |8.0.0 |102 <<windows-firewall-disabled-via-powershell-history, Version history>>
+|<<powershell-invoke-ninjacopy-script, PowerShell Invoke-NinjaCopy script>> |Detects PowerShell scripts that contain the default exported functions used on Invoke-NinjaCopy. Attackers can use Invoke-NinjaCopy to read SYSTEM files that are normally locked, such as the NTDS.dit file or registry hives. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: PowerShell Logs], [Resources: Investigation Guide] |8.3.0 |5
 
-|<<windows-network-enumeration, Windows Network Enumeration>> |Identifies attempts to enumerate hosts in a network using the built-in Windows net.exe tool. |[Elastic] [Host] [Windows] [Threat Detection] [Discovery] [Investigation Guide] [Elastic Endgame]  |7.11.0 |102 <<windows-network-enumeration-history, Version history>>
+|<<powershell-kerberos-ticket-dump, PowerShell Kerberos Ticket Dump>> |Detects PowerShell scripts that have the capability of dumping Kerberos tickets from LSA, which potentially indicates an attacker's attempt to acquire credentials for lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: PowerShell Logs] |8.3.0 |4
 
-|<<windows-registry-file-creation-in-smb-share, Windows Registry File Creation in SMB Share>> |Identifies the creation or modification of a medium-size registry hive file on a Server Message Block (SMB) share, which may indicate an exfiltration attempt of a previously dumped Security Account Manager (SAM) registry hive for credential extraction on an attacker-controlled system. |[Elastic] [Host] [Windows] [Threat Detection] [Lateral Movement] [Credential Access] [Investigation Guide]  |8.2.0 |102 <<windows-registry-file-creation-in-smb-share-history, Version history>>
+|<<powershell-kerberos-ticket-request, PowerShell Kerberos Ticket Request>> |Detects PowerShell scripts that have the capability of requesting kerberos tickets, which is a common step in Kerberoasting toolkits to crack service accounts. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.3.0 |111
 
-|<<windows-script-executing-powershell, Windows Script Executing PowerShell>> |Identifies a PowerShell process launched by either cscript.exe or wscript.exe. Observing Windows scripting processes executing a PowerShell script, may be indicative of malicious activity. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access] [Investigation Guide]  |7.6.0 |102 <<windows-script-executing-powershell-history, Version history>>
+|<<powershell-keylogging-script, PowerShell Keylogging Script>> |Detects the use of Win32 API Functions that can be used to capture user keystrokes in PowerShell scripts. Attackers use this technique to capture user input, looking for credentials and/or other valuable data. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.3.0 |112
 
-|<<windows-script-interpreter-executing-process-via-wmi, Windows Script Interpreter Executing Process via WMI>> |Identifies use of the built-in Windows script interpreters (cscript.exe or wscript.exe) being used to execute a process via Windows Management Instrumentation (WMI). This may be indicative of malicious activity. |[Elastic] [Host] [Windows] [Threat Detection] [Initial Access]  |7.11.0 |101 <<windows-script-interpreter-executing-process-via-wmi-history, Version history>>
+|<<powershell-mailbox-collection-script, PowerShell Mailbox Collection Script>> |Detects PowerShell scripts that can be used to collect data from mailboxes. Adversaries may target user email to collect sensitive information. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Data Source: PowerShell Logs], [Resources: Investigation Guide] |8.3.0 |7
 
-|<<windows-service-installed-via-an-unusual-client, Windows Service Installed via an Unusual Client>> |Identifies the creation of a Windows service by an unusual client process. Services may be created with administrator privileges but are executed under SYSTEM privileges, so an adversary may also use a service to escalate privileges from administrator to SYSTEM. |[Elastic] [Host] [Windows] [Threat Detection] [Privilege Escalation]  |8.1.0 |100 <<windows-service-installed-via-an-unusual-client-history, Version history>>
+|<<powershell-minidump-script, PowerShell MiniDump Script>> |This rule detects PowerShell scripts capable of dumping process memory using WindowsErrorReporting or Dbghelp.dll MiniDumpWriteDump. Attackers can use this tooling to dump LSASS and get access to credentials. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.3.0 |108
 
-|<<wireless-credential-dumping-using-netsh-command, Wireless Credential Dumping using Netsh Command>> |Identifies attempts to dump Wireless saved access keys in clear text using the Windows built-in utility Netsh. |[Elastic] [Host] [Windows] [Threat Detection] [Credential Access] [Discovery] [Elastic Endgame]  |8.6.0 |1
+|<<powershell-psreflect-script, PowerShell PSReflect Script>> |Detects the use of PSReflect in PowerShell scripts. Attackers leverage PSReflect as a library that enables PowerShell to access win32 API functions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.12.0 |210
 
-|<<zoom-meeting-with-no-passcode, Zoom Meeting with no Passcode>> |This rule identifies Zoom meetings that are created without a passcode. Meetings without a passcode are susceptible to Zoombombing. Zoombombing is carried out by taking advantage of Zoom sessions that are not protected with a passcode. Zoombombing refers to the unwanted, disruptive intrusion, generally by Internet trolls and hackers, into a video conference call. In a typical Zoombombing incident, a teleconferencing session is hijacked by the insertion of material that is lewd, obscene, racist, or antisemitic in nature, typically resulting of the shutdown of the session. |[Elastic] [Application] [Communication] [Zoom] [Continuous Monitoring] [SecOps] [Configuration Audit]  |7.10.0 |100 <<zoom-meeting-with-no-passcode-history, Version history>>
+|<<powershell-script-block-logging-disabled, PowerShell Script Block Logging Disabled>> |Identifies attempts to disable PowerShell Script Block Logging via registry modification. Attackers may disable this logging to conceal their activities in the host and evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
 
-|==============================================
\ No newline at end of file
+|<<powershell-script-with-archive-compression-capabilities, PowerShell Script with Archive Compression Capabilities>> |Identifies the use of Cmdlets and methods related to archive compression activities. Adversaries will often compress and encrypt data in preparation for exfiltration. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Data Source: PowerShell Logs], [Rule Type: BBR] |8.12.0 |105
+
+|<<powershell-script-with-discovery-capabilities, PowerShell Script with Discovery Capabilities>> |Identifies the use of Cmdlets and methods related to discovery activities. Attackers can use these to perform various situational awareness related activities, like enumerating users, shares, sessions, domain trusts, groups, etc. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Tactic: Discovery], [Data Source: PowerShell Logs], [Rule Type: BBR] |8.12.0 |107
+
+|<<powershell-script-with-encryption-decryption-capabilities, PowerShell Script with Encryption/Decryption Capabilities>> |Identifies the use of Cmdlets and methods related to encryption/decryption of files in PowerShell scripts, which malware and offensive security tools can abuse to encrypt data or decrypt payloads to bypass security solutions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: PowerShell Logs], [Resources: Investigation Guide] |8.3.0 |6
+
+|<<powershell-script-with-log-clear-capabilities, PowerShell Script with Log Clear Capabilities>> |Identifies the use of Cmdlets and methods related to Windows event log deletion activities. This is often done by attackers in an attempt to evade detection or destroy forensic evidence on a system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: PowerShell Logs], [Rule Type: BBR] |8.12.0 |105
+
+|<<powershell-script-with-password-policy-discovery-capabilities, PowerShell Script with Password Policy Discovery Capabilities>> |Identifies the use of Cmdlets and methods related to remote execution activities using WinRM. Attackers can abuse WinRM to perform lateral movement using built-in tools. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Tactic: Execution], [Data Source: PowerShell Logs], [Rule Type: BBR] |8.3.0 |5
+
+|<<powershell-script-with-remote-execution-capabilities-via-winrm, PowerShell Script with Remote Execution Capabilities via WinRM>> |Identifies the use of Cmdlets and methods related to remote execution activities using WinRM. Attackers can abuse WinRM to perform lateral movement using built-in tools. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Execution], [Data Source: PowerShell Logs], [Rule Type: BBR] |8.12.0 |106
+
+|<<powershell-script-with-token-impersonation-capabilities, PowerShell Script with Token Impersonation Capabilities>> |Detects scripts that contain PowerShell functions, structures, or Windows API functions related to token impersonation/theft. Attackers may duplicate then impersonate another user's token to escalate privileges and bypass access controls. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: PowerShell Logs] |8.3.0 |11
+
+|<<powershell-script-with-veeam-credential-access-capabilities, PowerShell Script with Veeam Credential Access Capabilities>> |Identifies PowerShell scripts that can access and decrypt Veeam credentials stored in MSSQL databases. Attackers can use Veeam Credentials to target backups as part of destructive operations such as Ransomware attacks. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: PowerShell Logs] |8.3.0 |1
+
+|<<powershell-script-with-webcam-video-capture-capabilities, PowerShell Script with Webcam Video Capture Capabilities>> |Detects PowerShell scripts that can be used to record webcam video. Attackers can capture this information to extort or spy on victims. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Data Source: PowerShell Logs] |8.3.0 |4
+
+|<<powershell-share-enumeration-script, PowerShell Share Enumeration Script>> |Detects scripts that contain PowerShell functions, structures, or Windows API functions related to windows share enumeration activities. Attackers, mainly ransomware groups, commonly identify and inspect network shares, looking for critical information for encryption and/or exfiltration. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Tactic: Collection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.3.0 |9
+
+|<<powershell-suspicious-discovery-related-windows-api-functions, PowerShell Suspicious Discovery Related Windows API Functions>> |This rule detects the use of discovery-related Windows API functions in PowerShell Scripts. Attackers can use these functions to perform various situational awareness related activities, like enumerating users, shares, sessions, domain trusts, groups, etc. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Tactic: Collection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.12.0 |213
+
+|<<powershell-suspicious-payload-encoded-and-compressed, PowerShell Suspicious Payload Encoded and Compressed>> |Identifies the use of .NET functionality for decompression and base64 decoding combined in PowerShell scripts, which malware and security tools heavily use to deobfuscate payloads and load them directly in memory to bypass defenses. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.12.0 |211
+
+|<<powershell-suspicious-script-with-audio-capture-capabilities, PowerShell Suspicious Script with Audio Capture Capabilities>> |Detects PowerShell scripts that can record audio, a common feature in popular post-exploitation tooling. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.3.0 |110
+
+|<<powershell-suspicious-script-with-clipboard-retrieval-capabilities, PowerShell Suspicious Script with Clipboard Retrieval Capabilities>> |Detects PowerShell scripts that can get the contents of the clipboard, which attackers can abuse to retrieve sensitive information like credentials, messages, etc. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Data Source: PowerShell Logs], [Resources: Investigation Guide] |8.12.0 |108
+
+|<<powershell-suspicious-script-with-screenshot-capabilities, PowerShell Suspicious Script with Screenshot Capabilities>> |Detects PowerShell scripts that can take screenshots, which is a common feature in post-exploitation kits and remote access tools (RATs). |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.3.0 |108
+
+|<<privilege-escalation-via-cap-chown-cap-fowner-capabilities, Privilege Escalation via CAP_CHOWN/CAP_FOWNER Capabilities>> |Identifies instances where a processes (granted CAP_CHOWN and/or CAP_FOWNER capabilities) is executed, after which the ownership of a suspicious file or binary is changed. In Linux, the CAP_CHOWN capability allows a process to change the owner of a file, while CAP_FOWNER permits it to bypass permission checks on operations that require file ownership (like reading, writing, and executing). Attackers may abuse these capabilities to obtain unauthorized access to files. |[Data Source: Auditd Manager], [Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.11.0 |3
+
+|<<privilege-escalation-via-cap-setuid-setgid-capabilities, Privilege Escalation via CAP_SETUID/SETGID Capabilities>> |Identifies instances where a process (granted CAP_SETUID and/or CAP_SETGID capabilities) is executed, after which the user's access is elevated to UID/GID 0 (root). In Linux, the CAP_SETUID and CAP_SETGID capabilities allow a process to change its UID and GID, respectively, providing control over user and group identity management. Attackers may leverage a misconfiguration for exploitation in order to escalate their privileges to root. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.11.0 |2
+
+|<<privilege-escalation-via-gdb-cap-sys-ptrace, Privilege Escalation via GDB CAP_SYS_PTRACE>> |Identifies instances where GDB (granted the CAP_SYS_PTRACE capability) is executed, after which the user's access is elevated to UID/GID 0 (root). In Linux, the CAP_SYS_PTRACE capability grants a process the ability to use the ptrace system call, which is typically used for debugging and allows the process to trace and control other processes. Attackers may leverage this capability to hook and inject into a process that is running with root permissions in order to escalate their privileges to root. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.11.0 |2
+
+|<<privilege-escalation-via-named-pipe-impersonation, Privilege Escalation via Named Pipe Impersonation>> |Identifies a privilege escalation attempt via named pipe impersonation. An adversary may abuse this technique by utilizing a framework such Metasploit's meterpreter getsystem command. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<privilege-escalation-via-rogue-named-pipe-impersonation, Privilege Escalation via Rogue Named Pipe Impersonation>> |Identifies a privilege escalation attempt via rogue named pipe impersonation. An adversary may abuse this technique by masquerading as a known named pipe and manipulating a privileged process to connect to it. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Sysmon] |8.3.0 |106
+
+|<<privilege-escalation-via-root-crontab-file-modification, Privilege Escalation via Root Crontab File Modification>> |Identifies modifications to the root crontab file. Adversaries may overwrite this file to gain code execution with root privileges by exploiting privileged file write or move related vulnerabilities. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.3.0 |106
+
+|<<privilege-escalation-via-windir-environment-variable, Privilege Escalation via Windir Environment Variable>> |Identifies a privilege escalation attempt via a rogue Windows directory (Windir) environment variable. This is a known primitive that is often combined with other vulnerabilities to elevate privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |106
+
+|<<privileged-account-brute-force, Privileged Account Brute Force>> |Identifies multiple consecutive logon failures targeting an Admin account from the same source address and within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to accounts. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide] |8.3.0 |9
+
+|<<privileges-elevation-via-parent-process-pid-spoofing, Privileges Elevation via Parent Process PID Spoofing>> |Identifies parent process spoofing used to create an elevated child process. Adversaries may spoof the parent process identifier (PPID) of a new process to evade process-monitoring defenses or to elevate privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.3.0 |7
+
+|<<process-activity-via-compiled-html-file, Process Activity via Compiled HTML File>> |Compiled HTML files (.chm) are commonly distributed as part of the Microsoft HTML Help system. Adversaries may conceal malicious code in a CHM file and deliver it to a victim for execution. CHM content is loaded by the HTML Help executable program (hh.exe). |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<process-capability-enumeration, Process Capability Enumeration>> |Identifies recursive process capability enumeration of the entire filesystem through the getcap command. Malicious users may manipulate identified capabilities to gain root privileges. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.11.0 |2
+
+|<<process-created-with-a-duplicated-token, Process Created with a Duplicated Token>> |Identifies the creation of a process impersonating the token of another user logon session. Adversaries may create a new process with a different token to escalate privileges and bypass access controls. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.4.0 |3
+
+|<<process-created-with-an-elevated-token, Process Created with an Elevated Token>> |Identifies the creation of a process running as SYSTEM and impersonating a Windows core binary privileges. Adversaries may create a new process with a different token to escalate privileges and bypass access controls. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.4.0 |6
+
+|<<process-creation-via-secondary-logon, Process Creation via Secondary Logon>> |Identifies process creation with alternate credentials. Adversaries may create a new process with a different token to escalate privileges and bypass access controls. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |9
+
+|<<process-discovery-using-built-in-tools, Process Discovery Using Built-in Tools>> |This rule identifies the execution of commands that can be used to enumerate running processes. Adversaries may enumerate processes to identify installed applications and security solutions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |4
+
+|<<process-discovery-via-built-in-applications, Process Discovery via Built-In Applications>> |Identifies the use of built-in tools attackers can use to discover running processes on an endpoint. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |3
+
+|<<process-execution-from-an-unusual-directory, Process Execution from an Unusual Directory>> |Identifies process execution from suspicious default Windows directories. This is sometimes done by adversaries to hide malware in trusted paths. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<process-injection-detected-elastic-endgame, Process Injection - Detected - Elastic Endgame>> |Elastic Endgame detected Process Injection. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |103
+
+|<<process-injection-prevented-elastic-endgame, Process Injection - Prevented - Elastic Endgame>> |Elastic Endgame prevented Process Injection. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |103
+
+|<<process-injection-by-the-microsoft-build-engine, Process Injection by the Microsoft Build Engine>> |An instance of MSBuild, the Microsoft Build Engine, created a thread in another process. This technique is sometimes used to evade detection or elevate privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Privilege Escalation], [Data Source: Sysmon] |8.3.0 |106
+
+|<<process-started-from-process-id-pid-file, Process Started from Process ID (PID) File>> |Identifies a new process starting from a process ID (PID), lock or reboot file within the temporary file storage paradigm (tmpfs) directory /var/run directory. On Linux, the PID files typically hold the process ID to track previous copies running and manage other tasks. Certain Linux malware use the /var/run directory for holding data, executables and other tasks, disguising itself or these files as legitimate PID files. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Threat: BPFDoor], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Auditd Manager] |8.3.0 |109
+
+|<<process-termination-followed-by-deletion, Process Termination followed by Deletion>> |Identifies a process termination event quickly followed by the deletion of its executable file. Malware tools and other non-native files dropped or created on a system by an adversary may leave traces to indicate to what occurred. Removal of these files can occur during an intrusion, or as part of a post-intrusion process to minimize the adversary's footprint. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |109
+
+|<<processes-with-trailing-spaces, Processes with Trailing Spaces>> |Identify instances where adversaries include trailing space characters to mimic regular files, disguising their activity to evade default file handling mechanisms. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |2
+
+|<<program-files-directory-masquerading, Program Files Directory Masquerading>> |Identifies execution from a directory masquerading as the Windows Program Files directories. These paths are trusted and usually host trusted third party programs. An adversary may leverage masquerading, along with low privileges to bypass detections allowlisting those folders. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
+
+|<<prompt-for-credentials-with-osascript, Prompt for Credentials with OSASCRIPT>> |Identifies the use of osascript to execute scripts via standard input that may prompt a user with a rogue dialog for credentials. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.7.0 |207
+
+|<<proxychains-activity, ProxyChains Activity>> |This rule monitors for the execution of the ProxyChains utility. ProxyChains is a command-line tool that enables the routing of network connections through intermediary proxies, enhancing anonymity and enabling access to restricted resources. Attackers can exploit the ProxyChains utility to hide their true source IP address, evade detection, and perform malicious activities through a chain of proxy servers, potentially masking their identity and intentions. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |4
+
+|<<psexec-network-connection, PsExec Network Connection>> |Identifies use of the SysInternals tool PsExec.exe making a network connection. This could be an indication of lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Lateral Movement], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<python-script-execution-via-command-line, Python Script Execution via Command Line>> |Identifies when a Python script is executed using command line input and imports the sys module. Attackers often use this method to execute malicious scripts and avoiding writing it to disk. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |1
+
+|<<quarantine-attrib-removed-by-unsigned-or-untrusted-process, Quarantine Attrib Removed by Unsigned or Untrusted Process>> |Detects deletion of the quarantine attribute by an unusual process (xattr). In macOS, when applications or programs are downloaded from the internet, there is a quarantine flag set on the file. This attribute is read by Apple's Gatekeeper defense program at execution time. An adversary may disable this attribute to evade defenses. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |108
+
+|<<query-registry-using-built-in-tools, Query Registry using Built-in Tools>> |This rule identifies the execution of commands that can be used to query the Windows Registry. Adversaries may query the registry to gain situational awareness about the host, like installed security software, programs and settings. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend] |8.6.0 |105
+
+|<<rdp-remote-desktop-protocol-from-the-internet, RDP (Remote Desktop Protocol) from the Internet>> |This rule detects network events that may indicate the use of RDP traffic from the Internet. RDP is commonly used by system administrators to remotely control a system for maintenance or to use shared resources. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. |[Tactic: Command and Control], [Domain: Endpoint], [Use Case: Threat Detection] |8.3.0 |103
+
+|<<rdp-enabled-via-registry, RDP Enabled via Registry>> |Identifies registry write modifications to enable Remote Desktop Protocol (RDP) access. This could be indicative of adversary lateral movement preparation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
+
+|<<rpc-remote-procedure-call-from-the-internet, RPC (Remote Procedure Call) from the Internet>> |This rule detects network events that may indicate the use of RPC traffic from the Internet. RPC is commonly used by system administrators to remotely control a system for maintenance or to use shared resources. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. |[Tactic: Initial Access], [Domain: Endpoint], [Use Case: Threat Detection] |8.3.0 |103
+
+|<<rpc-remote-procedure-call-to-the-internet, RPC (Remote Procedure Call) to the Internet>> |This rule detects network events that may indicate the use of RPC traffic to the Internet. RPC is commonly used by system administrators to remotely control a system for maintenance or to use shared resources. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. |[Tactic: Initial Access], [Domain: Endpoint], [Use Case: Threat Detection] |8.3.0 |103
+
+|<<ransomware-detected-elastic-endgame, Ransomware - Detected - Elastic Endgame>> |Elastic Endgame detected ransomware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame] |8.3.0 |103
+
+|<<ransomware-prevented-elastic-endgame, Ransomware - Prevented - Elastic Endgame>> |Elastic Endgame prevented ransomware. Click the Elastic Endgame icon in the event.module column or the link in the rule.reference column for additional information. |[Data Source: Elastic Endgame] |8.3.0 |103
+
+|<<rare-aws-error-code, Rare AWS Error Code>> |A machine learning job detected an unusual error in a CloudTrail message. These can be byproducts of attempted or successful persistence, privilege escalation, defense evasion, discovery, lateral movement, or collection. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Rule Type: ML], [Rule Type: Machine Learning], [Resources: Investigation Guide] |8.9.0 |208
+
+|<<rare-smb-connection-to-the-internet, Rare SMB Connection to the Internet>> |This rule detects rare internet network connections via the SMB protocol. SMB is commonly used to leak NTLM credentials via rogue UNC path injection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Exfiltration], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |3
+
+|<<rare-user-logon, Rare User Logon>> |A machine learning job found an unusual user name in the authentication logs. An unusual user name is one way of detecting credentialed access by means of a new or dormant user account. An inactive user account (because the user has left the organization) that becomes active may be due to credentialed access using a compromised account password. Threat actors will sometimes also create new users as a means of persisting in a compromised web application. |[Use Case: Identity and Access Audit], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Initial Access], [Resources: Investigation Guide] |8.3.0 |104
+
+|<<registry-persistence-via-appcert-dll, Registry Persistence via AppCert DLL>> |Detects attempts to maintain persistence by creating registry keys using AppCert DLLs. AppCert DLLs are loaded by every process using the common API functions to create processes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
+
+|<<registry-persistence-via-appinit-dll, Registry Persistence via AppInit DLL>> |AppInit DLLs are dynamic-link libraries (DLLs) that are loaded into every process that creates a user interface (loads user32.dll) on Microsoft Windows operating systems. The AppInit DLL mechanism is used to load custom code into user-mode processes, allowing for the customization of the user interface and the behavior of Windows-based applications. Attackers who add those DLLs to the registry locations can execute code with elevated privileges, similar to process injection, and provide a solid and constant persistence on the machine. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
+
+|<<remote-computer-account-dnshostname-update, Remote Computer Account DnsHostName Update>> |Identifies the remote update to a computer account's DnsHostName attribute. If the new value set is a valid domain controller DNS hostname and the subject computer name is not a domain controller, then it's highly likely a preparation step to exploit CVE-2022-26923 in an attempt to elevate privileges from a standard domain user to domain admin privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Use Case: Active Directory Monitoring], [Data Source: Active Directory], [Use Case: Vulnerability] |8.3.0 |107
+
+|<<remote-desktop-enabled-in-windows-firewall-by-netsh, Remote Desktop Enabled in Windows Firewall by Netsh>> |Identifies use of the network shell utility (netsh.exe) to enable inbound Remote Desktop Protocol (RDP) connections in the Windows Firewall. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<remote-execution-via-file-shares, Remote Execution via File Shares>> |Identifies the execution of a file that was created by the virtual system process. This may indicate lateral movement via network file shares. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<remote-file-copy-to-a-hidden-share, Remote File Copy to a Hidden Share>> |Identifies a remote file copy attempt to a hidden network share. This may indicate lateral movement or data staging activity. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
+
+|<<remote-file-copy-via-teamviewer, Remote File Copy via TeamViewer>> |Identifies an executable or script file remotely downloaded via a TeamViewer transfer session. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<remote-file-download-via-desktopimgdownldr-utility, Remote File Download via Desktopimgdownldr Utility>> |Identifies the desktopimgdownldr utility being used to download a remote file. An adversary may use desktopimgdownldr to download arbitrary files as an alternative to certutil. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
+
+|<<remote-file-download-via-mpcmdrun, Remote File Download via MpCmdRun>> |Identifies the Windows Defender configuration utility (MpCmdRun.exe) being used to download a remote file. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
+
+|<<remote-file-download-via-powershell, Remote File Download via PowerShell>> |Identifies powershell.exe being used to download an executable file from an untrusted remote destination. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<remote-file-download-via-script-interpreter, Remote File Download via Script Interpreter>> |Identifies built-in Windows script interpreters (cscript.exe or wscript.exe) being used to download an executable file from a remote destination. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
+
+|<<remote-ssh-login-enabled-via-systemsetup-command, Remote SSH Login Enabled via systemsetup Command>> |Detects use of the systemsetup command to enable remote SSH Login. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend] |8.3.0 |106
+
+|<<remote-scheduled-task-creation, Remote Scheduled Task Creation>> |Identifies remote scheduled task creations on a target host. This could be indicative of adversary lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
+
+|<<remote-scheduled-task-creation-via-rpc, Remote Scheduled Task Creation via RPC>> |Identifies scheduled task creation from a remote source. This could be indicative of adversary lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement] |8.3.0 |8
+
+|<<remote-system-discovery-commands, Remote System Discovery Commands>> |Discovery of remote system information using built-in commands, which may be used to move laterally. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Rule Type: BBR] |8.3.0 |112
+
+|<<remote-windows-service-installed, Remote Windows Service Installed>> |Identifies a network logon followed by Windows service creation with same LogonId. This could be indicative of lateral movement, but will be noisy if commonly done by administrators." |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Persistence] |8.3.0 |6
+
+|<<remote-xsl-script-execution-via-com, Remote XSL Script Execution via COM>> |Identifies the execution of a hosted XSL script using the Microsoft.XMLDOM COM interface via Microsoft Office processes. This behavior may indicate adversarial activity to execute malicious JScript or VBScript on the system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |3
+
+|<<remotely-started-services-via-rpc, Remotely Started Services via RPC>> |Identifies remote execution of Windows services over remote procedure call (RPC). This could be indicative of lateral movement, but will be noisy if commonly done by administrators. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |112
+
+|<<renamed-autoit-scripts-interpreter, Renamed AutoIt Scripts Interpreter>> |Identifies a suspicious AutoIt process execution. Malware written as an AutoIt script tends to rename the AutoIt executable to avoid detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
+
+|<<renamed-utility-executed-with-short-program-name, Renamed Utility Executed with Short Program Name>> |Identifies the execution of a process with a single character process name, differing from the original file name. This is often done by adversaries while staging, executing temporary utilities, or trying to bypass security detections based on the process name. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<root-network-connection-via-gdb-cap-sys-ptrace, Root Network Connection via GDB CAP_SYS_PTRACE>> |Identifies instances where GDB (granted the CAP_SYS_PTRACE capability) is executed, after which an outbound network connection is initiated by UID/GID 0 (root). In Linux, the CAP_SYS_PTRACE capability grants a process the ability to use the ptrace system call, which is typically used for debugging and allows the process to trace and control other processes. Attackers may leverage this capability to hook and inject into a process that is running with root permissions in order to execute shell code and gain a reverse shell with root privileges. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Execution], [Tactic: Command and Control], [Data Source: Elastic Defend] |8.11.0 |2
+
+|<<roshal-archive-rar-or-powershell-file-downloaded-from-the-internet, Roshal Archive (RAR) or PowerShell File Downloaded from the Internet>> |Detects a Roshal Archive (RAR) file or PowerShell script downloaded from the internet by an internal host. Gaining initial access to a system and then downloading encoded or encrypted tools to move laterally is a common practice for adversaries as a way to protect their more valuable tools and tactics, techniques, and procedures (TTPs). This may be atypical behavior for a managed network and can be indicative of malware, exfiltration, or command and control. |[Use Case: Threat Detection], [Tactic: Command and Control], [Domain: Endpoint] |8.3.0 |103
+
+|<<route53-resolver-query-log-configuration-deleted, Route53 Resolver Query Log Configuration Deleted>> |Identifies when a Route53 Resolver Query Log Configuration is deleted. When a Route53 Resolver query log configuration is deleted, Resolver stops logging DNS queries and responses for the specified configuration. Adversaries may delete query log configurations to evade detection or cover their tracks. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Data Source: Amazon Route53], [Use Case: Log Auditing], [Resources: Investigation Guide], [Tactic: Defense Evasion] |8.9.0 |1
+
+|<<sip-provider-modification, SIP Provider Modification>> |Identifies modifications to the registered Subject Interface Package (SIP) providers. SIP providers are used by the Windows cryptographic system to validate file signatures on the system. This may be an attempt to bypass signature validation checks or inject code into critical processes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
+
+|<<smb-windows-file-sharing-activity-to-the-internet, SMB (Windows File Sharing) Activity to the Internet>> |This rule detects network events that may indicate the use of Windows file sharing (also called SMB or CIFS) traffic to the Internet. SMB is commonly used within networks to share files, printers, and other system resources amongst trusted systems. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector or for data exfiltration. |[Tactic: Initial Access], [Domain: Endpoint], [Use Case: Threat Detection] |8.3.0 |103
+
+|<<smtp-on-port-26-tcp, SMTP on Port 26/TCP>> |This rule detects events that may indicate use of SMTP on TCP port 26. This port is commonly used by several popular mail transfer agents to deconflict with the default SMTP port 25. This port has also been used by a malware family called BadPatch for command and control of Windows systems. |[Tactic: Command and Control], [Domain: Endpoint], [Use Case: Threat Detection] |8.3.0 |104
+
+|<<ssh-authorized-keys-file-modification, SSH Authorized Keys File Modification>> |The Secure Shell (SSH) authorized_keys file specifies which users are allowed to log into a server using public key authentication. Adversaries may modify it to maintain persistence on a victim host by adding their own public key(s). |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Persistence], [Data Source: Elastic Defend] |8.6.0 |205
+
+|<<ssh-authorized-keys-file-modified-inside-a-container, SSH Authorized Keys File Modified Inside a Container>> |This rule detects the creation or modification of an authorized_keys or sshd_config file inside a container. The Secure Shell (SSH) authorized_keys file specifies which users are allowed to log into a server using public key authentication. Adversaries may modify it to maintain persistence on a victim host by adding their own public key(s). Unexpected and unauthorized SSH usage inside a container can be an indicator of compromise and should be investigated. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Lateral Movement] |8.8.0 |2
+
+|<<ssh-connection-established-inside-a-running-container, SSH Connection Established Inside A Running Container>> |This rule detects an incoming SSH connection established inside a running container. Running an ssh daemon inside a container should be avoided and monitored closely if necessary. If an attacker gains valid credentials they can use it to gain initial access or establish persistence within a compromised environment. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Lateral Movement] |8.8.0 |2
+
+|<<ssh-process-launched-from-inside-a-container, SSH Process Launched From Inside A Container>> |This rule detects an SSH or SSHD process executed from inside a container. This includes both the client ssh binary and server ssh daemon process. SSH usage inside a container should be avoided and monitored closely when necessary. With valid credentials an attacker may move laterally to other containers or to the underlying host through container breakout. They may also use valid SSH credentials as a persistence mechanism. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Persistence] |8.8.0 |2
+
+|<<suid-sguid-enumeration-detected, SUID/SGUID Enumeration Detected>> |This rule monitors for the usage of the "find" command in conjunction with SUID and SGUID permission arguments. SUID (Set User ID) and SGID (Set Group ID) are special permissions in Linux that allow a program to execute with the privileges of the file owner or group, respectively, rather than the privileges of the user running the program. In case an attacker is able to enumerate and find a binary that is misconfigured, they might be able to leverage this misconfiguration to escalate privileges by exploiting vulnerabilities or built-in features in the privileged program. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.3.0 |5
+
+|<<sunburst-command-and-control-activity, SUNBURST Command and Control Activity>> |The malware known as SUNBURST targets the SolarWind's Orion business software for command and control. This rule detects post-exploitation command and control activity of the SUNBURST backdoor. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |108
+
+|<<scheduled-task-created-by-a-windows-script, Scheduled Task Created by a Windows Script>> |A scheduled task was created by a Windows script via cscript.exe, wscript.exe or powershell.exe. This can be abused by an adversary to establish persistence. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
+
+|<<scheduled-task-execution-at-scale-via-gpo, Scheduled Task Execution at Scale via GPO>> |Detects the modification of Group Policy Object attributes to execute a scheduled task in the objects controlled by the GPO. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Lateral Movement], [Data Source: Active Directory], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring] |8.3.0 |110
+
+|<<scheduled-tasks-at-command-enabled, Scheduled Tasks AT Command Enabled>> |Identifies attempts to enable the Windows scheduled tasks AT command via the registry. Attackers may use this method to move laterally or persist locally. The AT command has been deprecated since Windows 8 and Windows Server 2012, but still exists for backwards compatibility. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<screenconnect-server-spawning-suspicious-processes, ScreenConnect Server Spawning Suspicious Processes>> |Identifies suspicious processes being spawned by the ScreenConnect server process (ScreenConnect.Service.exe). This activity may indicate exploitation activity or access to an existing web shell backdoor. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |1
+
+|<<screensaver-plist-file-modified-by-unexpected-process, Screensaver Plist File Modified by Unexpected Process>> |Identifies when a screensaver plist file is modified by an unexpected process. An adversary can maintain persistence on a macOS endpoint by creating a malicious screensaver (.saver) file and configuring the screensaver plist file to execute code each time the screensaver is activated. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |107
+
+|<<sedebugprivilege-enabled-by-a-suspicious-process, SeDebugPrivilege Enabled by a Suspicious Process>> |Identifies the creation of a process running as SYSTEM and impersonating a Windows core binary privileges. Adversaries may create a new process with a different token to escalate privileges and bypass access controls. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |7
+
+|<<searching-for-saved-credentials-via-vaultcmd, Searching for Saved Credentials via VaultCmd>> |Windows Credential Manager allows you to create, view, or delete saved credentials for signing into websites, connected applications, and networks. An adversary may abuse this to list or dump credentials stored in the Credential Manager for saved usernames and passwords. This may also be performed in preparation of lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
+
+|<<security-software-discovery-using-wmic, Security Software Discovery using WMIC>> |Identifies the use of Windows Management Instrumentation Command (WMIC) to discover certain System Security Settings such as AntiVirus or Host Firewall details. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |111
+
+|<<security-software-discovery-via-grep, Security Software Discovery via Grep>> |Identifies the use of the grep command to discover known third-party macOS and Linux security tools, such as Antivirus or Host Firewall details. |[Domain: Endpoint], [OS: macOS], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |109
+
+|<<segfault-detected, Segfault Detected>> |Monitors kernel logs for segfault messages. A segfault, or segmentation fault, is an error that occurs when a program tries to access a memory location that it's not allowed to access, typically leading to program termination. A segfault can be an indication of malicious behavior if it results from attempts to exploit buffer overflows or other vulnerabilities in software to execute arbitrary code or disrupt its normal operation. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Rule Type: BBR] |8.3.0 |1
+
+|<<sensitive-files-compression, Sensitive Files Compression>> |Identifies the use of a compression utility to collect known files containing sensitive information, such as credentials and system configurations. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Collection], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.6.0 |208
+
+|<<sensitive-files-compression-inside-a-container, Sensitive Files Compression Inside A Container>> |Identifies the use of a compression utility to collect known files containing sensitive information, such as credentials and system configurations inside a container. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Collection], [Tactic: Credential Access] |8.8.0 |2
+
+|<<sensitive-keys-or-passwords-searched-for-inside-a-container, Sensitive Keys Or Passwords Searched For Inside A Container>> |This rule detects the use of system search utilities like grep and find to search for private SSH keys or passwords inside a container. Unauthorized access to these sensitive files could lead to further compromise of the container environment or facilitate a container breakout to the underlying host machine. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Credential Access] |8.8.0 |2
+
+|<<sensitive-privilege-seenabledelegationprivilege-assigned-to-a-user, Sensitive Privilege SeEnableDelegationPrivilege assigned to a User>> |Identifies the assignment of the SeEnableDelegationPrivilege sensitive "user right" to a user. The SeEnableDelegationPrivilege "user right" enables computer and user accounts to be trusted for delegation. Attackers can abuse this right to compromise Active Directory accounts and elevate their privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Persistence], [Data Source: Active Directory], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring] |8.3.0 |110
+
+|<<service-command-lateral-movement, Service Command Lateral Movement>> |Identifies use of sc.exe to create, modify, or start services on remote hosts. This could be indicative of adversary lateral movement but will be noisy if commonly done by admins. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
+
+|<<service-control-spawned-via-script-interpreter, Service Control Spawned via Script Interpreter>> |Identifies Service Control (sc.exe) spawning from script interpreter processes to create, modify, or start services. This can potentially indicate an attempt to elevate privileges or maintain persistence. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |108
+
+|<<service-creation-via-local-kerberos-authentication, Service Creation via Local Kerberos Authentication>> |Identifies a suspicious local successful logon event where the Logon Package is Kerberos, the remote address is set to localhost, followed by a sevice creation from the same LogonId. This may indicate an attempt to leverage a Kerberos relay attack variant that can be used to elevate privilege locally from a domain joined user to local System privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Credential Access], [Use Case: Active Directory Monitoring], [Data Source: Active Directory] |8.3.0 |105
+
+|<<service-disabled-via-registry-modification, Service Disabled via Registry Modification>> |Identifies attempts to modify services start settings using processes other than services.exe. Attackers may attempt to modify security and monitoring services to avoid detection or delay response. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |3
+
+|<<service-path-modification, Service Path Modification>> |Identifies attempts to modify a service path by an unusual process. Attackers may attempt to modify existing services for persistence or privilege escalation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |2
+
+|<<service-path-modification-via-sc-exe, Service Path Modification via sc.exe>> |Identifies attempts to modify a service path setting using sc.exe. Attackers may attempt to modify existing services for persistence or privilege escalation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |3
+
+|<<setcap-setuid-setgid-capability-set, Setcap setuid/setgid Capability Set>> |This rule monitors for the addition of the cap_setuid+ep or cap_setgid+ep capabilities via setcap. Setuid (Set User ID) and setgid (Set Group ID) are Unix-like OS features that enable processes to run with elevated privileges, based on the file owner or group. Threat actors can exploit these attributes to achieve persistence by creating malicious binaries, allowing them to maintain control over a compromised system with elevated permissions. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |5
+
+|<<setuid-setgid-bit-set-via-chmod, Setuid / Setgid Bit Set via chmod>> |An adversary may add the setuid or setgid bit to a file or directory in order to run a file with the privileges of the owning user or group. An adversary can take advantage of this to either do a shell escape or exploit a vulnerability in an application with the setuid or setgid bit to get code running in a different user’s context. Additionally, adversaries can use this mechanism on their own malware to make sure they're able to execute in elevated contexts in the future. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.3.0 |103
+
+|<<sharepoint-malware-file-upload, SharePoint Malware File Upload>> |Identifies the occurence of files uploaded to SharePoint being detected as Malware by the file scanning engine. Attackers can use File Sharing and Organization Repositories to spread laterally within the company and amplify their access. Users can inadvertently share these files without knowing their maliciousness, giving adversaries opportunities to gain initial access to other endpoints in the environment. |[Domain: Cloud], [Data Source: Microsoft 365], [Tactic: Lateral Movement] |8.8.0 |206
+
+|<<shared-object-created-or-changed-by-previously-unknown-process, Shared Object Created or Changed by Previously Unknown Process>> |This rule monitors the creation of shared object files by previously unknown processes. The creation of a shared object file involves compiling code into a dynamically linked library that can be loaded by other programs at runtime. While this process is typically used for legitimate purposes, malicious actors can leverage shared object files to execute unauthorized code, inject malicious functionality into legitimate processes, or bypass security controls. This allows malware to persist on the system, evade detection, and potentially compromise the integrity and confidentiality of the affected system and its data. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.6.0 |7
+
+|<<shell-configuration-modification, Shell Configuration Modification>> |This rule monitors the creation/alteration of a shell configuration by a previously unknown process executable using the new terms rule type. Unix systems use shell configuration files to set environment variables, create aliases, and customize the user's environment. Adversaries may modify or add a shell configuration file to execute malicious code and gain persistence in the system. This behavior is consistent with the Kaiji malware family. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.6.0 |1
+
+|<<shell-execution-via-apple-scripting, Shell Execution via Apple Scripting>> |Identifies the execution of the shell process (sh) via scripting (JXA or AppleScript). Adversaries may use the doShellScript functionality in JXA or do shell script in AppleScript to execute system commands. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |107
+
+|<<shortcut-file-written-or-modified-on-startup-folder, Shortcut File Written or Modified on Startup Folder>> |Identifies shortcut files written to or modified in the startup folder. Adversaries may use this technique to maintain persistence. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |2
+
+|<<signed-proxy-execution-via-ms-work-folders, Signed Proxy Execution via MS Work Folders>> |Identifies the use of Windows Work Folders to execute a potentially masqueraded control.exe file in the current working directory. Misuse of Windows Work Folders could indicate malicious activity. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame] |8.3.0 |108
+
+|<<softwareupdate-preferences-modification, SoftwareUpdate Preferences Modification>> |Identifies changes to the SoftwareUpdate preferences using the built-in defaults command. Adversaries may abuse this in an attempt to disable security updates. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |106
+
+|<<solarwinds-process-disabling-services-via-registry, SolarWinds Process Disabling Services via Registry>> |Identifies a SolarWinds binary modifying the start type of a service to be disabled. An adversary may abuse this technique to manipulate relevant security services. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Initial Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<spike-in-aws-error-messages, Spike in AWS Error Messages>> |A machine learning job detected a significant spike in the rate of a particular error in the CloudTrail messages. Spikes in error messages may accompany attempts at privilege escalation, lateral movement, or discovery. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Rule Type: ML], [Rule Type: Machine Learning], [Resources: Investigation Guide] |8.9.0 |208
+
+|<<spike-in-bytes-sent-to-an-external-device, Spike in Bytes Sent to an External Device>> |A machine learning job has detected high bytes of data written to an external device. In a typical operational setting, there is usually a predictable pattern or a certain range of data that is written to external devices. An unusually large amount of data being written is anomalous and can signal illicit data copying or transfer activities. |[Use Case: Data Exfiltration Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Exfiltration] |8.9.0 |3
+
+|<<spike-in-bytes-sent-to-an-external-device-via-airdrop, Spike in Bytes Sent to an External Device via Airdrop>> |A machine learning job has detected high bytes of data written to an external device via Airdrop. In a typical operational setting, there is usually a predictable pattern or a certain range of data that is written to external devices. An unusually large amount of data being written is anomalous and can signal illicit data copying or transfer activities. |[Use Case: Data Exfiltration Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Exfiltration] |8.9.0 |3
+
+|<<spike-in-failed-logon-events, Spike in Failed Logon Events>> |A machine learning job found an unusually large spike in authentication failure events. This can be due to password spraying, user enumeration or brute force activity and may be a precursor to account takeover or credentialed access. |[Use Case: Identity and Access Audit], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Credential Access], [Resources: Investigation Guide] |8.3.0 |104
+
+|<<spike-in-firewall-denies, Spike in Firewall Denies>> |A machine learning job detected an unusually large spike in network traffic that was denied by network access control lists (ACLs) or firewall rules. Such a burst of denied traffic is usually caused by either 1) a mis-configured application or firewall or 2) suspicious or malicious activity. Unsuccessful attempts at network transit, in order to connect to command-and-control (C2), or engage in data exfiltration, may produce a burst of failed connections. This could also be due to unusually large amounts of reconnaissance or enumeration traffic. Denial-of-service attacks or traffic floods may also produce such a surge in traffic. |[Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning] |8.3.0 |103
+
+|<<spike-in-logon-events, Spike in Logon Events>> |A machine learning job found an unusually large spike in successful authentication events. This can be due to password spraying, user enumeration or brute force activity. |[Use Case: Identity and Access Audit], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Credential Access] |8.3.0 |103
+
+|<<spike-in-network-traffic, Spike in Network Traffic>> |A machine learning job detected an unusually large spike in network traffic. Such a burst of traffic, if not caused by a surge in business activity, can be due to suspicious or malicious activity. Large-scale data exfiltration may produce a burst of network traffic; this could also be due to unusually large amounts of reconnaissance or enumeration traffic. Denial-of-service attacks or traffic floods may also produce such a surge in traffic. |[Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning] |8.3.0 |103
+
+|<<spike-in-network-traffic-to-a-country, Spike in Network Traffic To a Country>> |A machine learning job detected an unusually large spike in network activity to one destination country in the network logs. This could be due to unusually large amounts of reconnaissance or enumeration traffic. Data exfiltration activity may also produce such a surge in traffic to a destination country that does not normally appear in network traffic or business workflows. Malware instances and persistence mechanisms may communicate with command-and-control (C2) infrastructure in their country of origin, which may be an unusual destination country for the source network. |[Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning] |8.3.0 |104
+
+|<<spike-in-number-of-connections-made-from-a-source-ip, Spike in Number of Connections Made from a Source IP>> |A machine learning job has detected a high count of destination IPs establishing an RDP connection with a single source IP. Once an attacker has gained access to one system, they might attempt to access more in the network in search of valuable assets, data, or further access points. |[Use Case: Lateral Movement Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Lateral Movement] |8.9.0 |3
+
+|<<spike-in-number-of-connections-made-to-a-destination-ip, Spike in Number of Connections Made to a Destination IP>> |A machine learning job has detected a high count of source IPs establishing an RDP connection with a single destination IP. Attackers might use multiple compromised systems to attack a target to ensure redundancy in case a source IP gets detected and blocked. |[Use Case: Lateral Movement Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Lateral Movement] |8.9.0 |3
+
+|<<spike-in-number-of-processes-in-an-rdp-session, Spike in Number of Processes in an RDP Session>> |A machine learning job has detected unusually high number of processes started in a single RDP session. Executing a large number of processes remotely on other machines can be an indicator of lateral movement activity. |[Use Case: Lateral Movement Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Lateral Movement] |8.9.0 |3
+
+|<<spike-in-remote-file-transfers, Spike in Remote File Transfers>> |A machine learning job has detected an abnormal volume of remote files shared on the host indicating potential lateral movement activity. One of the primary goals of attackers after gaining access to a network is to locate and exfiltrate valuable information. Attackers might perform multiple small transfers to match normal egress activity in the network, to evade detection. |[Use Case: Lateral Movement Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Lateral Movement] |8.9.0 |3
+
+|<<spike-in-successful-logon-events-from-a-source-ip, Spike in Successful Logon Events from a Source IP>> |A machine learning job found an unusually large spike in successful authentication events from a particular source IP address. This can be due to password spraying, user enumeration or brute force activity. |[Use Case: Identity and Access Audit], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Credential Access], [Tactic: Defense Evasion], [Resources: Investigation Guide] |8.3.0 |104
+
+|<<startup-folder-persistence-via-unsigned-process, Startup Folder Persistence via Unsigned Process>> |Identifies files written or modified in the startup folder by unsigned processes. Adversaries may abuse this technique to maintain persistence in an environment. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |109
+
+|<<startup-persistence-by-a-suspicious-process, Startup Persistence by a Suspicious Process>> |Identifies files written to or modified in the startup folder by commonly abused processes. Adversaries may use this technique to maintain persistence. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
+
+|<<startup-or-run-key-registry-modification, Startup or Run Key Registry Modification>> |Identifies run key or startup key registry modifications. In order to survive reboots and other system interrupts, attackers will modify run keys within the registry or leverage startup folder items as a form of persistence. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<startup-logon-script-added-to-group-policy-object, Startup/Logon Script added to Group Policy Object>> |Detects the modification of Group Policy Objects (GPO) to add a startup/logon script to users or computer objects. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Active Directory], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring] |8.3.0 |109
+
+|<<statistical-model-detected-c2-beaconing-activity, Statistical Model Detected C2 Beaconing Activity>> |A statistical model has identified command-and-control (C2) beaconing activity. Beaconing can help attackers maintain stealthy communication with their C2 servers, receive instructions and payloads, exfiltrate data and maintain persistence in a network. |[Domain: Network], [Use Case: C2 Beaconing Detection], [Tactic: Command and Control] |8.10.1 |4
+
+|<<statistical-model-detected-c2-beaconing-activity-with-high-confidence, Statistical Model Detected C2 Beaconing Activity with High Confidence>> |A statistical model has identified command-and-control (C2) beaconing activity with high confidence. Beaconing can help attackers maintain stealthy communication with their C2 servers, receive instructions and payloads, exfiltrate data and maintain persistence in a network. |[Domain: Network], [Use Case: C2 Beaconing Detection], [Tactic: Command and Control] |8.10.1 |4
+
+|<<stolen-credentials-used-to-login-to-okta-account-after-mfa-reset, Stolen Credentials Used to Login to Okta Account After MFA Reset>> |Detects a sequence of suspicious activities on Windows hosts indicative of credential compromise, followed by efforts to undermine multi-factor authentication (MFA) and single sign-on (SSO) mechanisms for an Okta user account. |[Tactic: Persistence], [Use Case: Identity and Access Audit], [Data Source: Okta], [Data Source: Elastic Defend], [Rule Type: Higher-Order Rule], [Domain: Endpoint], [Domain: Cloud] |8.10.0 |1
+
+|<<sublime-plugin-or-application-script-modification, Sublime Plugin or Application Script Modification>> |Adversaries may create or modify the Sublime application plugins or scripts to execute a malicious payload each time the Sublime application is started. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |107
+
+|<<sudo-command-enumeration-detected, Sudo Command Enumeration Detected>> |This rule monitors for the usage of the sudo -l command, which is used to list the allowed and forbidden commands for the invoking user. Attackers may execute this command to enumerate commands allowed to be executed with sudo permissions, potentially allowing to escalate privileges to root. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend] |8.3.0 |5
+
+|<<sudo-heap-based-buffer-overflow-attempt, Sudo Heap-Based Buffer Overflow Attempt>> |Identifies the attempted use of a heap-based buffer overflow vulnerability for the Sudo binary in Unix-like systems (CVE-2021-3156). Successful exploitation allows an unprivileged user to escalate to the root user. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |104
+
+|<<sudoers-file-modification, Sudoers File Modification>> |A sudoers file specifies the commands that users or groups can run and from which terminals. Adversaries can take advantage of these configurations to execute commands as other users or spawn processes with higher privileges. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.6.0 |204
+
+|<<suspicious-net-code-compilation, Suspicious .NET Code Compilation>> |Identifies executions of .NET compilers with suspicious parent processes, which can indicate an attacker's attempt to compile code after delivery in order to bypass security mechanisms. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<suspicious-net-reflection-via-powershell, Suspicious .NET Reflection via PowerShell>> |Detects the use of Reflection.Assembly to load PEs and DLLs in memory in PowerShell scripts. Attackers use this method to load executables and DLLs without writing to the disk, bypassing security solutions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.12.0 |212
+
+|<<suspicious-proc-maps-discovery, Suspicious /proc/maps Discovery>> |Monitors for /proc/*/maps file reads. The /proc/*/maps file in Linux provides a memory map for a specific process, detailing the memory segments, permissions, and what files are mapped to these segments. Attackers may read a process's memory map to identify memory addresses for code injection or process hijacking. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend] |8.3.0 |2
+
+|<<suspicious-apt-package-manager-execution, Suspicious APT Package Manager Execution>> |Detects suspicious process events executed by the APT package manager, potentially indicating persistence through an APT backdoor. In Linux, APT (Advanced Package Tool) is a command-line utility used for handling packages on Debian-based systems, providing functions for installing, updating, upgrading, and removing software along with managing package repositories. Attackers can backdoor APT to gain persistence by injecting malicious code into scripts that APT runs, thereby ensuring continued unauthorized access or control each time APT is used for package management. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Execution], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |2
+
+|<<suspicious-apt-package-manager-network-connection, Suspicious APT Package Manager Network Connection>> |Detects suspicious network events executed by the APT package manager, potentially indicating persistence through an APT backdoor. In Linux, APT (Advanced Package Tool) is a command-line utility used for handling packages on Debian-based systems, providing functions for installing, updating, upgrading, and removing software along with managing package repositories. Attackers can backdoor APT to gain persistence by injecting malicious code into scripts that APT runs, thereby ensuring continued unauthorized access or control each time APT is used for package management. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Command and Control], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |2
+
+|<<suspicious-access-to-ldap-attributes, Suspicious Access to LDAP Attributes>> |Identify read access to a high number of Active Directory object attributes. The knowledge of objects properties can help adversaries find vulnerabilities, elevate privileges or collect sensitive information. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: System], [Data Source: Active Directory], [Data Source: Windows] |8.3.0 |1
+
+|<<suspicious-activity-reported-by-okta-user, Suspicious Activity Reported by Okta User>> |Detects when a user reports suspicious activity for their Okta account. These events should be investigated, as they can help security teams identify when an adversary is attempting to gain access to their network. |[Use Case: Identity and Access Audit], [Data Source: Okta], [Tactic: Initial Access] |8.10.0 |205
+
+|<<suspicious-antimalware-scan-interface-dll, Suspicious Antimalware Scan Interface DLL>> |Identifies the creation of the Antimalware Scan Interface (AMSI) DLL in an unusual location. This may indicate an attempt to bypass AMSI by loading a rogue AMSI module instead of the legit one. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |9
+
+|<<suspicious-automator-workflows-execution, Suspicious Automator Workflows Execution>> |Identifies the execution of the Automator Workflows process followed by a network connection from it's XPC service. Adversaries may drop a custom workflow template that hosts malicious JavaScript for Automation (JXA) code as an alternative to using osascript. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |106
+
+|<<suspicious-browser-child-process, Suspicious Browser Child Process>> |Identifies the execution of a suspicious browser child process. Adversaries may gain access to a system through a user visiting a website over the normal course of browsing. With this technique, the user's web browser is typically targeted for exploitation. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |107
+
+|<<suspicious-calendar-file-modification, Suspicious Calendar File Modification>> |Identifies suspicious modifications of the calendar file by an unusual process. Adversaries may create a custom calendar notification procedure to execute a malicious program at a recurring interval to establish persistence. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |106
+
+|<<suspicious-certutil-commands, Suspicious CertUtil Commands>> |Identifies suspicious commands being used with certutil.exe. CertUtil is a native Windows component which is part of Certificate Services. CertUtil is often abused by attackers to live off the land for stealthier command and control or data exfiltration. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |108
+
+|<<suspicious-child-process-of-adobe-acrobat-reader-update-service, Suspicious Child Process of Adobe Acrobat Reader Update Service>> |Detects attempts to exploit privilege escalation vulnerabilities related to the Adobe Acrobat Reader PrivilegedHelperTool responsible for installing updates. For more information, refer to CVE-2020-9615, CVE-2020-9614 and CVE-2020-9613 and verify that the impacted system is patched. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |106
+
+|<<suspicious-cmd-execution-via-wmi, Suspicious Cmd Execution via WMI>> |Identifies suspicious command execution (cmd) via Windows Management Instrumentation (WMI) on a remote host. This could be indicative of adversary lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<suspicious-communication-app-child-process, Suspicious Communication App Child Process>> |Identifies suspicious child processes of communications apps, which can indicate a potential masquerading as the communication app or the exploitation of a vulnerability on the application causing it to execute code. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Persistence], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |4
+
+|<<suspicious-content-extracted-or-decompressed-via-funzip, Suspicious Content Extracted or Decompressed via Funzip>> |Identifies when suspicious content is extracted from a file and subsequently decompressed using the funzip utility. Malware may execute the tail utility using the "-c" option to read a sequence of bytes from the end of a file. The output from tail can be piped to funzip in order to decompress malicious code before it is executed. This behavior is consistent with malware families such as Bundlore. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |5
+
+|<<suspicious-crontab-creation-or-modification, Suspicious CronTab Creation or Modification>> |Identifies attempts to create or modify a crontab via a process that is not crontab (i.e python, osascript, etc.). This activity should not be highly prevalent and could indicate the use of cron as a persistence mechanism by a threat actor. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |106
+
+|<<suspicious-dll-loaded-for-persistence-or-privilege-escalation, Suspicious DLL Loaded for Persistence or Privilege Escalation>> |Identifies the loading of a non Microsoft signed DLL that is missing on a default Windows install (phantom DLL) or one that can be loaded from a different location by a native Windows process. This may be abused to persist or elevate privileges via privileged file write vulnerabilities. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
+
+|<<suspicious-data-encryption-via-openssl-utility, Suspicious Data Encryption via OpenSSL Utility>> |Identifies when the openssl command-line utility is used to encrypt multiple files on a host within a short time window. Adversaries may encrypt data on a single or multiple systems in order to disrupt the availability of their target's data and may attempt to hold the organization's data to ransom for the purposes of extortion. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Impact], [Data Source: Elastic Defend] |8.3.0 |6
+
+|<<suspicious-dynamic-linker-discovery-via-od, Suspicious Dynamic Linker Discovery via od>> |Monitors for dynamic linker discovery via the od utility. od (octal dump) is a command-line utility in Unix operating systems used for displaying data in various formats, including octal, hexadecimal, decimal, and ASCII, primarily used for examining and debugging binary files or data streams. Attackers can leverage od to analyze the dynamic linker by identifying injection points and craft exploits based on the observed behaviors and structures within these files. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |2
+
+|<<suspicious-emond-child-process, Suspicious Emond Child Process>> |Identifies the execution of a suspicious child process of the Event Monitor Daemon (emond). Adversaries may abuse this service by writing a rule to execute commands when a defined event occurs, such as system start up or user authentication. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |106
+
+|<<suspicious-endpoint-security-parent-process, Suspicious Endpoint Security Parent Process>> |A suspicious Endpoint Security parent process was detected. This may indicate a process hollowing or other form of code injection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<suspicious-execution-from-inet-cache, Suspicious Execution from INET Cache>> |Identifies the execution of a process with arguments pointing to the INetCache Folder. Adversaries may deliver malicious content via WININET during initial access. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Command and Control], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |2
+
+|<<suspicious-execution-from-a-mounted-device, Suspicious Execution from a Mounted Device>> |Identifies when a script interpreter or signed binary is launched via a non-standard working directory. An attacker may use this technique to evade defenses. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
+
+|<<suspicious-execution-via-msiexec, Suspicious Execution via MSIEXEC>> |Identifies suspicious execution of the built-in Windows Installer, msiexec.exe, to install a package from usual paths or parent process. Adversaries may abuse msiexec.exe to launch malicious local MSI files. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |2
+
+|<<suspicious-execution-via-microsoft-office-add-ins, Suspicious Execution via Microsoft Office Add-Ins>> |Identifies execution of common Microsoft Office applications to launch an Office Add-In from a suspicious path or with an unusual parent process. This may indicate an attempt to get initial access via a malicious phishing MS Office Add-In. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |5
+
+|<<suspicious-execution-via-scheduled-task, Suspicious Execution via Scheduled Task>> |Identifies execution of a suspicious program via scheduled tasks by looking at process lineage and command line usage. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Execution], [Data Source: Elastic Defend] |8.3.0 |108
+
+|<<suspicious-execution-via-windows-subsystem-for-linux, Suspicious Execution via Windows Subsystem for Linux>> |Detects Linux Bash commands from the the Windows Subsystem for Linux. Adversaries may enable and use WSL for Linux to avoid detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |6
+
+|<<suspicious-explorer-child-process, Suspicious Explorer Child Process>> |Identifies a suspicious Windows explorer child process. Explorer.exe can be abused to launch malicious scripts or executables from a trusted parent process. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<suspicious-file-changes-activity-detected, Suspicious File Changes Activity Detected>> |This rule identifies a sequence of 100 file extension rename events within a set of common file paths by the same process in a timespan of 1 second. Ransomware is a type of malware that encrypts a victim's files or systems and demands payment (usually in cryptocurrency) in exchange for the decryption key. One important indicator of a ransomware attack is the mass encryption of the file system, after which a new file extension is added to the file. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Impact], [Data Source: Elastic Defend] |8.3.0 |8
+
+|<<suspicious-file-creation-in-etc-for-persistence, Suspicious File Creation in /etc for Persistence>> |Detects the manual creation of files in specific etc directories, via user root, used by Linux malware to persist and elevate privileges on compromised systems. File creation in these directories should not be entirely common and could indicate a malicious binary or script installing persistence mechanisms for long term access. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Threat: Orbit], [Threat: Lightning Framework], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |113
+
+|<<suspicious-file-creation-via-kworker, Suspicious File Creation via Kworker>> |This rule monitors for a file creation event originating from a kworker parent process. kworker, or kernel worker, processes are part of the kernel's workqueue mechanism. They are responsible for executing work that has been scheduled to be done in kernel space, which might include tasks like handling interrupts, background activities, and other kernel-related tasks. Attackers may attempt to evade detection by masquerading as a kernel worker process. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |3
+
+|<<suspicious-file-downloaded-from-google-drive, Suspicious File Downloaded from Google Drive>> |Identifies suspicious file download activity from a Google Drive URL. This could indicate an attempt to deliver phishing payloads via a trusted webservice. |[Domain: Endpoint], [OS: Linux], [OS: Windows], [OS: macOS], [Use Case: Threat Detection], [Tactic: Command and Control] |8.3.0 |3
+
+|<<suspicious-file-renamed-via-smb, Suspicious File Renamed via SMB>> |Identifies an incoming SMB connection followed by a suspicious file rename operation. This may indicate a remote ransomware attack via the SMB protocol. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Impact], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |1
+
+|<<suspicious-html-file-creation, Suspicious HTML File Creation>> |Identifies the execution of a browser process to open an HTML file with high entropy and size. Adversaries may smuggle data and files past content filters by hiding malicious payloads inside of seemingly benign HTML files. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Data Source: Elastic Defend] |8.3.0 |107
+
+|<<suspicious-hidden-child-process-of-launchd, Suspicious Hidden Child Process of Launchd>> |Identifies the execution of a launchd child process with a hidden file. An adversary can establish persistence by installing a new logon item, launch agent, or daemon that executes upon login. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |106
+
+|<<suspicious-image-load-taskschd-dll-from-ms-office, Suspicious Image Load (taskschd.dll) from MS Office>> |Identifies a suspicious image load (taskschd.dll) from Microsoft Office processes. This behavior may indicate adversarial activity where a scheduled task is configured via Windows Component Object Model (COM). This technique can be used to configure persistence and evade monitoring by avoiding the usage of the traditional Windows binary (schtasks.exe) used to manage scheduled tasks. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<suspicious-imagepath-service-creation, Suspicious ImagePath Service Creation>> |Identifies the creation of a suspicious ImagePath value. This could be an indication of an adversary attempting to stealthily persist or escalate privileges through abnormal service creation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
+
+|<<suspicious-inter-process-communication-via-outlook, Suspicious Inter-Process Communication via Outlook>> |Detects Inter-Process Communication with Outlook via Component Object Model from an unusual process. Adversaries may target user email to collect sensitive information or send email on their behalf via API. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Collection], [Data Source: Elastic Defend] |8.4.0 |6
+
+|<<suspicious-interactive-shell-spawned-from-inside-a-container, Suspicious Interactive Shell Spawned From Inside A Container>> |This rule detects when an interactive shell is spawned inside a running container. This could indicate a potential container breakout attempt or an attacker's attempt to gain unauthorized access to the underlying host. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution] |8.8.0 |2
+
+|<<suspicious-java-child-process, Suspicious JAVA Child Process>> |Identifies suspicious child processes of the Java interpreter process. This may indicate an attempt to execute a malicious JAR file or an exploitation attempt via a JAVA specific vulnerability. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Execution], [Resources: Investigation Guide], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.6.0 |208
+
+|<<suspicious-jetbrains-teamcity-child-process, Suspicious JetBrains TeamCity Child Process>> |Identifies suspicious processes being spawned by the JetBrain TeamCity process. This activity could be related to JetBrains remote code execution vulnerabilities. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Data Source: Elastic Endgame], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |1
+
+|<<suspicious-kworker-uid-elevation, Suspicious Kworker UID Elevation>> |Monitors for the elevation of regular user permissions to root permissions through the kworker process. kworker, or kernel worker, processes are part of the kernel's workqueue mechanism. They are responsible for executing work that has been scheduled to be done in kernel space, which might include tasks like handling interrupts, background activities, and other kernel-related tasks. Attackers may attempt to evade detection by masquerading as a kernel worker process, and hijack the execution flow by hooking certain functions/syscalls through a rootkit in order to provide easy access to root via a special modified command. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |2
+
+|<<suspicious-lsass-access-via-malseclogon, Suspicious LSASS Access via MalSecLogon>> |Identifies suspicious access to LSASS handle from a call trace pointing to seclogon.dll and with a suspicious access rights value. This may indicate an attempt to leak an LSASS handle via abusing the Secondary Logon service in preparation for credential access. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Sysmon] |8.8.0 |208
+
+|<<suspicious-lsass-process-access, Suspicious Lsass Process Access>> |Identifies access attempts to LSASS handle, this may indicate an attempt to dump credentials from Lsass memory. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Sysmon] |8.8.0 |107
+
+|<<suspicious-ms-office-child-process, Suspicious MS Office Child Process>> |Identifies suspicious child processes of frequently targeted Microsoft Office applications (Word, PowerPoint, Excel). These child processes are often launched during exploitation of Office applications or from documents with malicious macros. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Defense Evasion], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
+
+|<<suspicious-ms-outlook-child-process, Suspicious MS Outlook Child Process>> |Identifies suspicious child processes of Microsoft Outlook. These child processes are often associated with spear phishing activity. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Defense Evasion], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<suspicious-managed-code-hosting-process, Suspicious Managed Code Hosting Process>> |Identifies a suspicious managed code hosting process which could indicate code injection or other form of suspicious code execution. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
+
+|<<suspicious-memory-grep-activity, Suspicious Memory grep Activity>> |Monitors for grep activity related to memory mapping. The /proc/*/maps file in Linux provides a memory map for a specific process, detailing the memory segments, permissions, and what files are mapped to these segments. Attackers may read a process's memory map to identify memory addresses for code injection or process hijacking. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |2
+
+|<<suspicious-microsoft-365-mail-access-by-clientappid, Suspicious Microsoft 365 Mail Access by ClientAppId>> |Identifies when a Microsoft 365 Mailbox is accessed by a ClientAppId that was observed for the fist time during the last 10 days. |[Domain: Cloud], [Data Source: Microsoft 365], [Use Case: Configuration Audit], [Tactic: Initial Access] |8.8.0 |105
+
+|<<suspicious-microsoft-diagnostics-wizard-execution, Suspicious Microsoft Diagnostics Wizard Execution>> |Identifies potential abuse of the Microsoft Diagnostics Troubleshooting Wizard (MSDT) to proxy malicious command or binary execution via malicious process arguments. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
+
+|<<suspicious-mining-process-creation-event, Suspicious Mining Process Creation Event>> |Identifies service creation events of common mining services, possibly indicating the infection of a system with a cryptominer. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |6
+
+|<<suspicious-modprobe-file-event, Suspicious Modprobe File Event>> |Detects file events involving kernel modules in modprobe configuration files, which may indicate unauthorized access or manipulation of critical kernel modules. Attackers may tamper with the modprobe files to load malicious or unauthorized kernel modules, potentially bypassing security measures, escalating privileges, or hiding their activities within the system. |[Data Source: Auditd Manager], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR] |8.6.0 |107
+
+|<<suspicious-module-loaded-by-lsass, Suspicious Module Loaded by LSASS>> |Identifies LSASS loading an unsigned or untrusted DLL. Windows Security Support Provider (SSP) DLLs are loaded into LSSAS process at system start. Once loaded into the LSA, SSP DLLs have access to encrypted and plaintext passwords that are stored in Windows, such as any logged-on user's Domain password or smart card PINs. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.3.0 |8
+
+|<<suspicious-network-activity-to-the-internet-by-previously-unknown-executable, Suspicious Network Activity to the Internet by Previously Unknown Executable>> |This rule monitors for network connectivity to the internet from a previously unknown executable located in a suspicious directory to a previously unknown destination ip. An alert from this rule can indicate the presence of potentially malicious activity, such as the execution of unauthorized or suspicious processes attempting to establish connections to unknown or suspicious destinations such as a command and control server. Detecting and investigating such behavior can help identify and mitigate potential security threats, protecting the system and its data from potential compromise. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.6.0 |8
+
+|<<suspicious-network-connection-via-sudo-binary, Suspicious Network Connection via Sudo Binary>> |Detects network connections initiated by the "sudo" binary. This behavior is uncommon and may occur in instances where reverse shell shellcode is injected into a process run with elevated permissions via "sudo". Attackers may attempt to inject shellcode into processes running as root, to escalate privileges. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |2
+
+|<<suspicious-network-connection-via-systemd, Suspicious Network Connection via systemd>> |Detects suspicious network events executed by systemd, potentially indicating persistence through a systemd backdoor. Systemd is a system and service manager for Linux operating systems, used to initialize and manage system processes. Attackers can backdoor systemd for persistence by creating or modifying systemd unit files to execute malicious scripts or commands, or by replacing legitimate systemd binaries with compromised ones, ensuring that their malicious code is automatically executed at system startup or during certain system events. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Command and Control], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |2
+
+|<<suspicious-network-tool-launched-inside-a-container, Suspicious Network Tool Launched Inside A Container>> |This rule detects commonly abused network utilities running inside a container. Network utilities like nc, nmap, dig, tcpdump, ngrep, telnet, mitmproxy, zmap can be used for malicious purposes such as network reconnaissance, monitoring, or exploitation, and should be monitored closely within a container. |[Data Source: Elastic Defend for Containers], [Domain: Container], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Tactic: Command and Control], [Tactic: Reconnaissance] |8.8.0 |2
+
+|<<suspicious-pdf-reader-child-process, Suspicious PDF Reader Child Process>> |Identifies suspicious child processes of PDF reader applications. These child processes are often launched via exploitation of PDF applications or social engineering. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Initial Access], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<suspicious-passwd-file-event-action, Suspicious Passwd File Event Action>> |Monitors for the generation of a passwd password entry via openssl, followed by a file write activity on the "/etc/passwd" file. The "/etc/passwd" file in Linux stores user account information, including usernames, user IDs, group IDs, home directories, and default shell paths. Attackers may exploit a misconfiguration in the "/etc/passwd" file permissions or other privileges to add a new entry to the "/etc/passwd" file with root permissions, and leverage this new user account to login as root. |[Data Source: Auditd Manager], [Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |8.3.0 |3
+
+|<<suspicious-portable-executable-encoded-in-powershell-script, Suspicious Portable Executable Encoded in Powershell Script>> |Detects the presence of a portable executable (PE) in a PowerShell script by looking for its encoded header. Attackers embed PEs into PowerShell scripts to inject them into memory, avoiding defences by not writing to disk. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: PowerShell Logs] |8.3.0 |110
+
+|<<suspicious-powershell-engine-imageload, Suspicious PowerShell Engine ImageLoad>> |Identifies the PowerShell engine being invoked by unexpected processes. Rather than executing PowerShell functionality with powershell.exe, some attackers do this to operate more stealthily. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.6.0 |210
+
+|<<suspicious-powershell-script, Suspicious Powershell Script>> |A machine learning job detected a PowerShell script with unusual data characteristics, such as obfuscation, that may be a characteristic of malicious PowerShell script text blocks. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Execution] |8.3.0 |104
+
+|<<suspicious-print-spooler-file-deletion, Suspicious Print Spooler File Deletion>> |Detects deletion of print driver files by an unusual process. This may indicate a clean up attempt post successful privilege escalation via Print Spooler service related vulnerabilities. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Use Case: Vulnerability], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
+
+|<<suspicious-print-spooler-point-and-print-dll, Suspicious Print Spooler Point and Print DLL>> |Detects attempts to exploit a privilege escalation vulnerability (CVE-2020-1030) related to the print spooler service. Exploitation involves chaining multiple primitives to load an arbitrary DLL into the print spooler process running as SYSTEM. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Use Case: Vulnerability], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |106
+
+|<<suspicious-print-spooler-spl-file-created, Suspicious Print Spooler SPL File Created>> |Detects attempts to exploit privilege escalation vulnerabilities related to the Print Spooler service including CVE-2020-1048 and CVE-2020-1337. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<suspicious-printspooler-service-executable-file-creation, Suspicious PrintSpooler Service Executable File Creation>> |Detects attempts to exploit privilege escalation vulnerabilities related to the Print Spooler service. For more information refer to the following CVE's - CVE-2020-1048, CVE-2020-1337 and CVE-2020-1300 and verify that the impacted system is patched. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Use Case: Vulnerability], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
+
+|<<suspicious-proc-pseudo-file-system-enumeration, Suspicious Proc Pseudo File System Enumeration>> |This rule monitors for a rapid enumeration of 25 different proc cmd, stat, and exe files, which suggests an abnormal activity pattern. Such behavior could be an indicator of a malicious process scanning or gathering information about running processes, potentially for reconnaissance, privilege escalation, or identifying vulnerable targets. |[Data Source: Auditd Manager], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR] |8.3.0 |7
+
+|<<suspicious-process-access-via-direct-system-call, Suspicious Process Access via Direct System Call>> |Identifies suspicious process access events from an unknown memory region. Endpoint security solutions usually hook userland Windows APIs in order to decide if the code that is being executed is malicious or not. It's possible to bypass hooked functions by writing malicious functions that call syscalls directly. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Sysmon] |8.8.0 |211
+
+|<<suspicious-process-creation-calltrace, Suspicious Process Creation CallTrace>> |Identifies when a process is created and immediately accessed from an unknown memory code region and by the same parent process. This may indicate a code injection attempt. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Sysmon] |8.8.0 |208
+
+|<<suspicious-process-execution-via-renamed-psexec-executable, Suspicious Process Execution via Renamed PsExec Executable>> |Identifies suspicious psexec activity which is executing from the psexec service that has been renamed, possibly to evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
+
+|<<suspicious-process-spawned-from-motd-detected, Suspicious Process Spawned from MOTD Detected>> |Message of the day (MOTD) is the message that is presented to the user when a user connects to a Linux server via SSH or a serial connection. Linux systems contain several default MOTD files located in the "/etc/update-motd.d/" and "/usr/lib/update-notifier/" directories. These scripts run as the root user every time a user connects over SSH or a serial connection. Adversaries may create malicious MOTD files that grant them persistence onto the target every time a user connects to the system by executing a backdoor script or command. This rule detects the execution of potentially malicious processes through the MOTD utility. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |8
+
+|<<suspicious-rdp-activex-client-loaded, Suspicious RDP ActiveX Client Loaded>> |Identifies suspicious Image Loading of the Remote Desktop Services ActiveX Client (mstscax), this may indicate the presence of RDP lateral movement capability. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<suspicious-remote-registry-access-via-sebackupprivilege, Suspicious Remote Registry Access via SeBackupPrivilege>> |Identifies remote access to the registry using an account with Backup Operators group membership. This may indicate an attempt to exfiltrate credentials by dumping the Security Account Manager (SAM) registry hive in preparation for credential access and privileges elevation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Credential Access], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring], [Data Source: Active Directory] |8.3.0 |110
+
+|<<suspicious-renaming-of-esxi-files, Suspicious Renaming of ESXI Files>> |Identifies instances where VMware-related files, such as those with extensions like ".vmdk", ".vmx", ".vmxf", ".vmsd", ".vmsn", ".vswp", ".vmss", ".nvram", and ".vmem", are renamed on a Linux system. The rule monitors for the "rename" event action associated with these file types, which could indicate malicious activity. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.5.0 |6
+
+|<<suspicious-renaming-of-esxi-index-html-file, Suspicious Renaming of ESXI index.html File>> |Identifies instances where the "index.html" file within the "/usr/lib/vmware/*" directory is renamed on a Linux system. The rule monitors for the "rename" event action associated with this specific file and path, which could indicate malicious activity. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.5.0 |6
+
+|<<suspicious-screenconnect-client-child-process, Suspicious ScreenConnect Client Child Process>> |Identifies suspicious processes being spawned by the ScreenConnect client processes. This activity may indicate execution abusing unauthorized access to the ScreenConnect remote access software. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |1
+
+|<<suspicious-script-object-execution, Suspicious Script Object Execution>> |Identifies scrobj.dll loaded into unusual Microsoft processes. This usually means a malicious scriptlet is being executed in the target process. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
+
+|<<suspicious-service-was-installed-in-the-system, Suspicious Service was Installed in the System>> |Identifies the creation of a new Windows service with suspicious Service command values. Windows services typically run as SYSTEM and can be used for privilege escalation and persistence. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide] |8.3.0 |8
+
+|<<suspicious-solarwinds-child-process, Suspicious SolarWinds Child Process>> |A suspicious SolarWinds child process was detected, which may indicate an attempt to execute malicious programs. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<suspicious-startup-shell-folder-modification, Suspicious Startup Shell Folder Modification>> |Identifies suspicious startup shell folder modifications to change the default Startup directory in order to bypass detections monitoring file creation in the Windows Startup folder. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
+
+|<<suspicious-symbolic-link-created, Suspicious Symbolic Link Created>> |Identifies the creation of a symbolic link to a suspicious file or location. A symbolic link is a reference to a file or directory that acts as a pointer or shortcut, allowing users to access the target file or directory from a different location in the file system. An attacker can potentially leverage symbolic links for privilege escalation by tricking a privileged process into following the symbolic link to a sensitive file, giving the attacker access to data or capabilities they would not normally have. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Credential Access], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |5
+
+|<<suspicious-sysctl-file-event, Suspicious Sysctl File Event>> |Monitors file events on sysctl configuration files (e.g., /etc/sysctl.conf, /etc/sysctl.d/*.conf) to identify potential unauthorized access or manipulation of system-level configuration settings. Attackers may tamper with the sysctl configuration files to modify kernel parameters, potentially compromising system stability, performance, or security. |[Data Source: Auditd Manager], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR] |8.6.0 |107
+
+|<<suspicious-system-commands-executed-by-previously-unknown-executable, Suspicious System Commands Executed by Previously Unknown Executable>> |This rule monitors for the execution of several commonly used system commands executed by a previously unknown executable located in commonly abused directories. An alert from this rule can indicate the presence of potentially malicious activity, such as the execution of unauthorized or suspicious processes attempting to run malicious code. Detecting and investigating such behavior can help identify and mitigate potential security threats, protecting the system and its data from potential compromise. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.6.0 |105
+
+|<<suspicious-termination-of-esxi-process, Suspicious Termination of ESXI Process>> |Identifies instances where VMware processes, such as "vmware-vmx" or "vmx," are terminated on a Linux system by a "kill" command. The rule monitors for the "end" event type, which signifies the termination of a process. The presence of a "kill" command as the parent process for terminating VMware processes may indicate that a threat actor is attempting to interfere with the virtualized environment on the targeted system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Impact], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.5.0 |6
+
+|<<suspicious-troubleshooting-pack-cabinet-execution, Suspicious Troubleshooting Pack Cabinet Execution>> |Identifies the execution of the Microsoft Diagnostic Wizard to open a diagcab file from a suspicious path and with an unusual parent process. This may indicate an attempt to execute malicious Troubleshooting Pack Cabinet files. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |2
+
+|<<suspicious-utility-launched-via-proxychains, Suspicious Utility Launched via ProxyChains>> |This rule monitors for the execution of suspicious linux tools through ProxyChains. ProxyChains is a command-line tool that enables the routing of network connections through intermediary proxies, enhancing anonymity and enabling access to restricted resources. Attackers can exploit the ProxyChains utility to hide their true source IP address, evade detection, and perform malicious activities through a chain of proxy servers, potentially masking their identity and intentions. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Command and Control], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |7
+
+|<<suspicious-wmi-event-subscription-created, Suspicious WMI Event Subscription Created>> |Detects the creation of a WMI Event Subscription. Attackers can abuse this mechanism for persistence or to elevate to SYSTEM privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Sysmon] |8.8.0 |106
+
+|<<suspicious-wmi-image-load-from-ms-office, Suspicious WMI Image Load from MS Office>> |Identifies a suspicious image load (wmiutils.dll) from Microsoft Office processes. This behavior may indicate adversarial activity where child processes are spawned via Windows Management Instrumentation (WMI). This technique can be used to execute code and evade traditional parent/child processes spawned from Microsoft Office products. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
+
+|<<suspicious-wmic-xsl-script-execution, Suspicious WMIC XSL Script Execution>> |Identifies WMIC allowlist bypass techniques by alerting on suspicious execution of scripts. When WMIC loads scripting libraries it may be indicative of an allowlist bypass. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<suspicious-web-browser-sensitive-file-access, Suspicious Web Browser Sensitive File Access>> |Identifies the access or file open of web browser sensitive files by an untrusted/unsigned process or osascript. Adversaries may acquire credentials from web browsers by reading files specific to the target browser. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.11.0 |207
+
+|<<suspicious-werfault-child-process, Suspicious WerFault Child Process>> |A suspicious WerFault child process was detected, which may indicate an attempt to run via the SilentProcessExit registry key manipulation. Verify process details such as command line, network connections and file writes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Persistence], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
+
+|<<suspicious-windows-process-cluster-spawned-by-a-host, Suspicious Windows Process Cluster Spawned by a Host>> |A machine learning job combination has detected a set of one or more suspicious Windows processes with unusually high scores for malicious probability. These process(es) have been classified as malicious in several ways. The process(es) were predicted to be malicious by the ProblemChild supervised ML model. If the anomaly contains a cluster of suspicious processes, each process has the same host name, and the aggregate score of the event cluster was calculated to be unusually high by an unsupervised ML model. Such a cluster often contains suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules. |[Use Case: Living off the Land Attack Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Defense Evasion] |8.9.0 |4
+
+|<<suspicious-windows-process-cluster-spawned-by-a-parent-process, Suspicious Windows Process Cluster Spawned by a Parent Process>> |A machine learning job combination has detected a set of one or more suspicious Windows processes with unusually high scores for malicious probability. These process(es) have been classified as malicious in several ways. The process(es) were predicted to be malicious by the ProblemChild supervised ML model. If the anomaly contains a cluster of suspicious processes, each process has the same parent process name, and the aggregate score of the event cluster was calculated to be unusually high by an unsupervised ML model. Such a cluster often contains suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules. |[Domain: Endpoint], [OS: Windows], [Use Case: Living off the Land Attack Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Defense Evasion] |8.9.0 |4
+
+|<<suspicious-windows-process-cluster-spawned-by-a-user, Suspicious Windows Process Cluster Spawned by a User>> |A machine learning job combination has detected a set of one or more suspicious Windows processes with unusually high scores for malicious probability. These process(es) have been classified as malicious in several ways. The process(es) were predicted to be malicious by the ProblemChild supervised ML model. If the anomaly contains a cluster of suspicious processes, each process has the same user name, and the aggregate score of the event cluster was calculated to be unusually high by an unsupervised ML model. Such a cluster often contains suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules. |[Domain: Endpoint], [OS: Windows], [Use Case: Living off the Land Attack Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Defense Evasion] |8.9.0 |4
+
+|<<suspicious-zoom-child-process, Suspicious Zoom Child Process>> |A suspicious Zoom child process was detected, which may indicate an attempt to run unnoticed. Verify process details such as command line, network connections, file writes and associated file signature details as well. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<suspicious-macos-ms-office-child-process, Suspicious macOS MS Office Child Process>> |Identifies suspicious child processes of frequently targeted Microsoft Office applications (Word, PowerPoint, and Excel). These child processes are often launched during exploitation of Office applications or by documents with malicious macros. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Initial Access], [Data Source: Elastic Defend] |8.11.0 |206
+
+|<<suspicious-which-enumeration, Suspicious which Enumeration>> |This rule monitors for the usage of the which command with an unusual amount of process arguments. Attackers may leverage the which command to enumerate the system for useful installed utilities that may be used after compromising a system to escalate privileges or move latteraly across the network. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |5
+
+|<<svchost-spawning-cmd, Svchost spawning Cmd>> |Identifies a suspicious parent child process relationship with cmd.exe descending from svchost.exe |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.6.0 |212
+
+|<<symbolic-link-to-shadow-copy-created, Symbolic Link to Shadow Copy Created>> |Identifies the creation of symbolic links to a shadow copy. Symbolic links can be used to access files in the shadow copy, including sensitive files such as ntds.dit, System Boot Key and browser offline credentials. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<system-binary-copied-and-or-moved-to-suspicious-directory, System Binary Copied and/or Moved to Suspicious Directory>> |This rule monitors for the copying or moving of a system binary to a suspicious directory. Adversaries may copy/move and rename system binaries to evade detection. Copying a system binary to a different location should not occur often, so if it does, the activity should be investigated. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |7
+
+|<<system-hosts-file-access, System Hosts File Access>> |Identifies the use of built-in tools to read the contents of \etc\hosts on a local machine. Attackers may use this data to discover remote machines in an environment that may be used for Lateral Movement from the current system. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |3
+
+|<<system-information-discovery-via-windows-command-shell, System Information Discovery via Windows Command Shell>> |Identifies the execution of discovery commands to enumerate system information, files, and folders using the Windows Command Shell. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |10
+
+|<<system-log-file-deletion, System Log File Deletion>> |Identifies the deletion of sensitive Linux system logs. This may indicate an attempt to evade detection or destroy forensic evidence on a system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<system-network-connections-discovery, System Network Connections Discovery>> |Adversaries may attempt to get a listing of network connections to or from a compromised system. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |3
+
+|<<system-owner-user-discovery-linux, System Owner/User Discovery Linux>> |Identifies the use of built-in tools which adversaries may use to enumerate the system owner/user of a compromised system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |3
+
+|<<system-service-discovery-through-built-in-windows-utilities, System Service Discovery through built-in Windows Utilities>> |Detects the usage of commonly used system service discovery techniques, which attackers may use during the reconnaissance phase after compromising a system in order to gain a better understanding of the environment and/or escalate privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Rule Type: BBR] |8.3.0 |6
+
+|<<system-shells-via-services, System Shells via Services>> |Windows services typically run as SYSTEM and can be used as a privilege escalation opportunity. Malware or penetration testers may run a shell as a service to gain SYSTEM permissions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<system-time-discovery, System Time Discovery>> |Detects the usage of commonly used system time discovery techniques, which attackers may use during the reconnaissance phase after compromising a system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Rule Type: BBR] |8.3.0 |7
+
+|<<systemkey-access-via-command-line, SystemKey Access via Command Line>> |Keychains are the built-in way for macOS to keep track of users' passwords and credentials for many services and features, including Wi-Fi and website passwords, secure notes, certificates, and Kerberos. Adversaries may collect the keychain storage data from a system to acquire credentials. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.7.0 |206
+
+|<<tcc-bypass-via-mounted-apfs-snapshot-access, TCC Bypass via Mounted APFS Snapshot Access>> |Identifies the use of the mount_apfs command to mount the entire file system through Apple File System (APFS) snapshots as read-only and with the noowners flag set. This action enables the adversary to access almost any file in the file system, including all user data and files protected by Apple’s privacy framework (TCC). |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |106
+
+|<<tainted-kernel-module-load, Tainted Kernel Module Load>> |This rule monitors the syslog log file for messages related to instances of a tainted kernel module load. Rootkits often leverage kernel modules as their main defense evasion technique. Detecting tainted kernel module loads is crucial for ensuring system security and integrity, as malicious or unauthorized modules can compromise the kernel and lead to system vulnerabilities or unauthorized access. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion] |8.3.0 |4
+
+|<<tainted-out-of-tree-kernel-module-load, Tainted Out-Of-Tree Kernel Module Load>> |This rule monitors the syslog log file for messages related to instances of a out-of-tree kernel module load, indicating the taining of the kernel. Rootkits often leverage kernel modules as their main defense evasion technique. Detecting tainted kernel module loads is crucial for ensuring system security and integrity, as malicious or unauthorized modules can compromise the kernel and lead to system vulnerabilities or unauthorized access. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion] |8.3.0 |2
+
+|<<tampering-of-shell-command-line-history, Tampering of Shell Command-Line History>> |Adversaries may attempt to clear or disable the Bash command-line history in an attempt to evade detection or forensic investigations. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |105
+
+|<<temporarily-scheduled-task-creation, Temporarily Scheduled Task Creation>> |Indicates the creation and deletion of a scheduled task within a short time interval. Adversaries can use these to proxy malicious execution via the schedule service and perform clean up. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Execution] |8.3.0 |7
+
+|<<third-party-backup-files-deleted-via-unexpected-process, Third-party Backup Files Deleted via Unexpected Process>> |Identifies the deletion of backup files, saved using third-party software, by a process outside of the backup suite. Adversaries may delete Backup files to ensure that recovery from a ransomware attack is less likely. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Impact], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
+
+|<<threat-intel-hash-indicator-match, Threat Intel Hash Indicator Match>> |This rule is triggered when a hash indicator from the Threat Intel Filebeat module or integrations has a match against an event that contains file hashes, such as antivirus alerts, process creation, library load, and file operation events. |[OS: Windows], [Data Source: Elastic Endgame], [Rule Type: Indicator Match] |8.5.0 |7
+
+|<<threat-intel-ip-address-indicator-match, Threat Intel IP Address Indicator Match>> |This rule is triggered when an IP address indicator from the Threat Intel Filebeat module or integrations has a match against a network event. |[OS: Windows], [Data Source: Elastic Endgame], [Rule Type: Indicator Match] |8.5.0 |6
+
+|<<threat-intel-url-indicator-match, Threat Intel URL Indicator Match>> |This rule is triggered when a URL indicator from the Threat Intel Filebeat module or integrations has a match against an event that contains URL data, like DNS events, network logs, etc. |[OS: Windows], [Data Source: Elastic Endgame], [Rule Type: Indicator Match] |8.5.0 |6
+
+|<<threat-intel-windows-registry-indicator-match, Threat Intel Windows Registry Indicator Match>> |This rule is triggered when a Windows registry indicator from the Threat Intel Filebeat module or integrations has a match against an event that contains registry data. |[OS: Windows], [Data Source: Elastic Endgame], [Rule Type: Indicator Match] |8.5.0 |6
+
+|<<timestomping-using-touch-command, Timestomping using Touch Command>> |Timestomping is an anti-forensics technique which is used to modify the timestamps of a file, often to mimic files that are in the same folder. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.3.0 |106
+
+|<<trap-signals-execution, Trap Signals Execution>> |Identify activity related where adversaries can include a trap command which then allows programs and shells to specify commands that will be executed upon receiving interrupt signals. |[Domain: Endpoint], [OS: Linux], [OS: macOS], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |2
+
+|<<uac-bypass-attempt-via-elevated-com-internet-explorer-add-on-installer, UAC Bypass Attempt via Elevated COM Internet Explorer Add-On Installer>> |Identifies User Account Control (UAC) bypass attempts by abusing an elevated COM Interface to launch a malicious program. Attackers may attempt to bypass UAC to stealthily execute code with elevated permissions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<uac-bypass-attempt-via-privileged-ifileoperation-com-interface, UAC Bypass Attempt via Privileged IFileOperation COM Interface>> |Identifies attempts to bypass User Account Control (UAC) via DLL side-loading. Attackers may attempt to bypass UAC to stealthily execute code with elevated permissions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<uac-bypass-attempt-via-windows-directory-masquerading, UAC Bypass Attempt via Windows Directory Masquerading>> |Identifies an attempt to bypass User Account Control (UAC) by masquerading as a Microsoft trusted Windows directory. Attackers may bypass UAC to stealthily execute code with elevated permissions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |112
+
+|<<uac-bypass-attempt-with-ieditionupgrademanager-elevated-com-interface, UAC Bypass Attempt with IEditionUpgradeManager Elevated COM Interface>> |Identifies attempts to bypass User Account Control (UAC) by abusing an elevated COM Interface to launch a rogue Windows ClipUp program. Attackers may attempt to bypass UAC to stealthily execute code with elevated permissions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<uac-bypass-via-diskcleanup-scheduled-task-hijack, UAC Bypass via DiskCleanup Scheduled Task Hijack>> |Identifies User Account Control (UAC) bypass via hijacking DiskCleanup Scheduled Task. Attackers bypass UAC to stealthily execute code with elevated permissions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
+
+|<<uac-bypass-via-icmluautil-elevated-com-interface, UAC Bypass via ICMLuaUtil Elevated COM Interface>> |Identifies User Account Control (UAC) bypass attempts via the ICMLuaUtil Elevated COM interface. Attackers may attempt to bypass UAC to stealthily execute code with elevated permissions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<uac-bypass-via-windows-firewall-snap-in-hijack, UAC Bypass via Windows Firewall Snap-In Hijack>> |Identifies attempts to bypass User Account Control (UAC) by hijacking the Microsoft Management Console (MMC) Windows Firewall snap-in. Attackers bypass UAC to stealthily execute code with elevated permissions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
+
+|<<uid-elevation-from-previously-unknown-executable, UID Elevation from Previously Unknown Executable>> |Monitors for the elevation of regular user permissions to root permissions through a previously unknown executable. Attackers may attempt to evade detection by hijacking the execution flow and hooking certain functions/syscalls through a rootkit in order to provide easy access to root via a special modified command. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.6.0 |2
+
+|<<unauthorized-access-to-an-okta-application, Unauthorized Access to an Okta Application>> |Identifies unauthorized access attempts to Okta applications. |[Tactic: Initial Access], [Use Case: Identity and Access Audit], [Data Source: Okta] |8.10.0 |206
+
+|<<uncommon-registry-persistence-change, Uncommon Registry Persistence Change>> |Detects changes to registry persistence keys that are not commonly used or modified by legitimate programs. This could be an indication of an adversary's attempt to persist in a stealthy manner. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
+
+|<<unexpected-child-process-of-macos-screensaver-engine, Unexpected Child Process of macOS Screensaver Engine>> |Identifies when a child process is spawned by the screensaver engine process, which is consistent with an attacker's malicious payload being executed after the screensaver activated on the endpoint. An adversary can maintain persistence on a macOS endpoint by creating a malicious screensaver (.saver) file and configuring the screensaver plist file to execute code each time the screensaver is activated. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Defend] |8.3.0 |107
+
+|<<unix-socket-connection, Unix Socket Connection>> |This rule monitors for inter-process communication via Unix sockets. Adversaries may attempt to communicate with local Unix sockets to enumerate application details, find vulnerabilities/configuration mistakes and potentially escalate privileges or set up malicious communication channels via Unix sockets for inter-process communication to attempt to evade detection. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend], [Rule Type: BBR], [Data Source: Elastic Endgame], [Data Source: Auditd Manager] |8.3.0 |2
+
+|<<unknown-execution-of-binary-with-rwx-memory-region, Unknown Execution of Binary with RWX Memory Region>> |Monitors for the execution of a previously unknown unix binary with read, write and execute memory region permissions. The mprotect() system call is used to change the access protections on a region of memory that has already been allocated. This syscall allows a process to modify the permissions of pages in its virtual address space, enabling or disabling permissions such as read, write, and execute for those pages. RWX permissions on memory is in many cases overly permissive, and should be analyzed thoroughly. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Auditd Manager] |8.6.0 |1
+
+|<<unsigned-bits-service-client-process, Unsigned BITS Service Client Process>> |Identifies an unsigned Windows Background Intelligent Transfer Service (BITS) client process. Attackers may abuse BITS functionality to download or upload data using the BITS service. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |2
+
+|<<unsigned-dll-loaded-by-svchost, Unsigned DLL Loaded by Svchost>> |Identifies an unsigned library created in the last 5 minutes and subsequently loaded by a shared windows service (svchost). Adversaries may use this technique to maintain persistence or run with System privileges. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Tactic: Execution], [Data Source: Elastic Defend] |8.4.0 |6
+
+|<<unsigned-dll-loaded-by-a-trusted-process, Unsigned DLL Loaded by a Trusted Process>> |Identifies digitally signed (trusted) processes loading unsigned DLLs. Attackers may plant their payloads into the application folder and invoke the legitimate application to execute the payload, masking actions they perform under a legitimate, trusted, and potentially elevated system or software process. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend] |8.4.0 |102
+
+|<<unsigned-dll-side-loading-from-a-suspicious-folder, Unsigned DLL Side-Loading from a Suspicious Folder>> |Identifies a Windows trusted program running from locations often abused by adversaries to masquerade as a trusted program and loading a recently dropped DLL. This behavior may indicate an attempt to evade defenses via side-loading a malicious DLL within the memory space of a signed processes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend] |8.4.0 |8
+
+|<<untrusted-driver-loaded, Untrusted Driver Loaded>> |Identifies attempt to load an untrusted driver. Adversaries may modify code signing policies to enable execution of unsigned or self-signed code. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |8
+
+|<<unusual-aws-command-for-a-user, Unusual AWS Command for a User>> |A machine learning job detected an AWS API command that, while not inherently suspicious or abnormal, is being made by a user context that does not normally use the command. This can be the result of compromised credentials or keys as someone uses a valid account to persist, move laterally, or exfiltrate data. |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Rule Type: ML], [Rule Type: Machine Learning], [Resources: Investigation Guide] |8.9.0 |208
+
+|<<unusual-child-process-from-a-system-virtual-process, Unusual Child Process from a System Virtual Process>> |Identifies a suspicious child process of the Windows virtual system process, which could indicate code injection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<unusual-child-process-of-dns-exe, Unusual Child Process of dns.exe>> |Identifies an unexpected process spawning from dns.exe, the process responsible for Windows DNS server services, which may indicate activity related to remote code execution or other forms of exploitation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<unusual-child-processes-of-rundll32, Unusual Child Processes of RunDLL32>> |Identifies child processes of unusual instances of RunDLL32 where the command line parameters were suspicious. Misuse of RunDLL32 could indicate malicious activity. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
+
+|<<unusual-city-for-an-aws-command, Unusual City For an AWS Command>> |A machine learning job detected AWS command activity that, while not inherently suspicious or abnormal, is sourcing from a geolocation (city) that is unusual for the command. This can be the result of compromised credentials or keys being used by a threat actor in a different geography than the authorized user(s). |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Rule Type: ML], [Rule Type: Machine Learning], [Resources: Investigation Guide] |8.9.0 |208
+
+|<<unusual-country-for-an-aws-command, Unusual Country For an AWS Command>> |A machine learning job detected AWS command activity that, while not inherently suspicious or abnormal, is sourcing from a geolocation (country) that is unusual for the command. This can be the result of compromised credentials or keys being used by a threat actor in a different geography than the authorized user(s). |[Domain: Cloud], [Data Source: AWS], [Data Source: Amazon Web Services], [Rule Type: ML], [Rule Type: Machine Learning], [Resources: Investigation Guide] |8.9.0 |208
+
+|<<unusual-dns-activity, Unusual DNS Activity>> |A machine learning job detected a rare and unusual DNS query that indicate network activity with unusual DNS domains. This can be due to initial access, persistence, command-and-control, or exfiltration activity. For example, when a user clicks on a link in a phishing email or opens a malicious document, a request may be sent to download and run a payload from an uncommon domain. When malware is already running, it may send requests to an uncommon DNS domain the malware uses for command-and-control communication. |[Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Command and Control] |8.3.0 |103
+
+|<<unusual-discovery-activity-by-user, Unusual Discovery Activity by User>> |This rule leverages alert data from various Discovery building block rules to alert on signals with unusual unique host.id and user.id entries. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: Higher-Order Rule] |8.6.0 |1
+
+|<<unusual-discovery-signal-alert-with-unusual-process-command-line, Unusual Discovery Signal Alert with Unusual Process Command Line>> |This rule leverages alert data from various Discovery building block rules to alert on signals with unusual unique host.id, user.id and process.command_line entries. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: Higher-Order Rule] |8.6.0 |1
+
+|<<unusual-discovery-signal-alert-with-unusual-process-executable, Unusual Discovery Signal Alert with Unusual Process Executable>> |This rule leverages Discovery building block rule alert data to alert on signals with unusual unique host.id, user.id and process.executable entries. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: Higher-Order Rule] |8.6.0 |2
+
+|<<unusual-executable-file-creation-by-a-system-critical-process, Unusual Executable File Creation by a System Critical Process>> |Identifies an unexpected executable file being created or modified by a Windows system critical process, which may indicate activity related to remote code execution or other forms of exploitation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
+
+|<<unusual-execution-via-microsoft-common-console-file, Unusual Execution via Microsoft Common Console File>> |Identifies the execution of a child process from a Microsoft Common Console file. Adversaries may embed a malicious command in an MSC file in order to trick victims into executing malicious commands. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Tactic: Initial Access], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |1
+
+|<<unusual-file-creation-alternate-data-stream, Unusual File Creation - Alternate Data Stream>> |Identifies suspicious creation of Alternate Data Streams on highly targeted files. This is uncommon for legitimate files and sometimes done by adversaries to hide malware. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |114
+
+|<<unusual-file-modification-by-dns-exe, Unusual File Modification by dns.exe>> |Identifies an unexpected file being modified by dns.exe, the process responsible for Windows DNS Server services, which may indicate activity related to remote code execution or other forms of exploitation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Endgame], [Use Case: Vulnerability], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
+
+|<<unusual-high-confidence-misconduct-blocks-detected, Unusual High Confidence Misconduct Blocks Detected>> |Detects repeated high-confidence 'BLOCKED' actions coupled with specific violation codes such as 'MISCONDUCT', indicating persistent misuse or attempts to probe the model's ethical boundaries. |[Domain: LLM], [Data Source: AWS Bedrock], [Data Source: AWS S3], [Use Case: Policy Violation], [Mitre Atlas: T0051], [Mitre Atlas: T0054] |8.13.0 |1
+
+|<<unusual-hour-for-a-user-to-logon, Unusual Hour for a User to Logon>> |A machine learning job detected a user logging in at a time of day that is unusual for the user. This can be due to credentialed access via a compromised account when the user and the threat actor are in different time zones. In addition, unauthorized user activity often takes place during non-business hours. |[Use Case: Identity and Access Audit], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Initial Access], [Resources: Investigation Guide] |8.3.0 |104
+
+|<<unusual-linux-network-activity, Unusual Linux Network Activity>> |Identifies Linux processes that do not usually use the network but have unexpected network activity, which can indicate command-and-control, lateral movement, persistence, or data exfiltration activity. A process with unusual network activity can denote process exploitation or injection, where the process is used to run persistence mechanisms that allow a malicious actor remote access or control of the host, data exfiltration, and execution of unauthorized network applications. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning] |8.3.0 |103
+
+|<<unusual-linux-network-configuration-discovery, Unusual Linux Network Configuration Discovery>> |Looks for commands related to system network configuration discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used by a threat actor to engage in system network configuration discovery in order to increase their understanding of connected networks and hosts. This information may be used to shape follow-up behaviors such as lateral movement or additional discovery. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Discovery] |8.3.0 |104
+
+|<<unusual-linux-network-connection-discovery, Unusual Linux Network Connection Discovery>> |Looks for commands related to system network connection discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used by a threat actor to engage in system network connection discovery in order to increase their understanding of connected services and systems. This information may be used to shape follow-up behaviors such as lateral movement or additional discovery. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Discovery] |8.3.0 |103
+
+|<<unusual-linux-network-port-activity, Unusual Linux Network Port Activity>> |Identifies unusual destination port activity that can indicate command-and-control, persistence mechanism, or data exfiltration activity. Rarely used destination port activity is generally unusual in Linux fleets, and can indicate unauthorized access or threat actor activity. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning] |8.3.0 |103
+
+|<<unusual-linux-process-calling-the-metadata-service, Unusual Linux Process Calling the Metadata Service>> |Looks for anomalous access to the metadata service by an unusual process. The metadata service may be targeted in order to harvest credentials or user data scripts containing secrets. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Credential Access] |8.3.0 |103
+
+|<<unusual-linux-process-discovery-activity, Unusual Linux Process Discovery Activity>> |Looks for commands related to system process discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used by a threat actor to engage in system process discovery in order to increase their understanding of software applications running on a target host or network. This may be a precursor to selection of a persistence mechanism or a method of privilege elevation. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Discovery] |8.3.0 |103
+
+|<<unusual-linux-system-information-discovery-activity, Unusual Linux System Information Discovery Activity>> |Looks for commands related to system information discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used to engage in system information discovery in order to gather detailed information about system configuration and software versions. This may be a precursor to selection of a persistence mechanism or a method of privilege elevation. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Discovery] |8.3.0 |103
+
+|<<unusual-linux-user-calling-the-metadata-service, Unusual Linux User Calling the Metadata Service>> |Looks for anomalous access to the cloud platform metadata service by an unusual user. The metadata service may be targeted in order to harvest credentials or user data scripts containing secrets. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Credential Access] |8.3.0 |103
+
+|<<unusual-linux-user-discovery-activity, Unusual Linux User Discovery Activity>> |Looks for commands related to system user or owner discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used to engage in system owner or user discovery in order to identify currently active or primary users of a system. This may be a precursor to additional discovery, credential dumping or privilege elevation activity. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Discovery] |8.3.0 |104
+
+|<<unusual-linux-username, Unusual Linux Username>> |A machine learning job detected activity for a username that is not normally active, which can indicate unauthorized changes, activity by unauthorized users, lateral movement, or compromised credentials. In many organizations, new usernames are not often created apart from specific types of system activities, such as creating new accounts for new employees. These user accounts quickly become active and routine. Events from rarely used usernames can point to suspicious activity. Additionally, automated Linux fleets tend to see activity from rarely used usernames only when personnel log in to make authorized or unauthorized changes, or threat actors have acquired credentials and log in for malicious purposes. Unusual usernames can also indicate pivoting, where compromised credentials are used to try and move laterally from one host to another. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Initial Access] |8.3.0 |103
+
+|<<unusual-login-activity, Unusual Login Activity>> |Identifies an unusually high number of authentication attempts. |[Use Case: Identity and Access Audit], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Credential Access] |8.3.0 |103
+
+|<<unusual-network-activity-from-a-windows-system-binary, Unusual Network Activity from a Windows System Binary>> |Identifies network activity from unexpected system applications. This may indicate adversarial activity as these applications are often leveraged by adversaries to execute code and evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
+
+|<<unusual-network-connection-via-dllhost, Unusual Network Connection via DllHost>> |Identifies unusual instances of dllhost.exe making outbound network connections. This may indicate adversarial Command and Control activity. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |107
+
+|<<unusual-network-connection-via-rundll32, Unusual Network Connection via RunDLL32>> |Identifies unusual instances of rundll32.exe making outbound network connections. This may indicate adversarial Command and Control activity. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Command and Control], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<unusual-network-destination-domain-name, Unusual Network Destination Domain Name>> |A machine learning job detected an unusual network destination domain name. This can be due to initial access, persistence, command-and-control, or exfiltration activity. For example, when a user clicks on a link in a phishing email or opens a malicious document, a request may be sent to download and run a payload from an uncommon web server name. When malware is already running, it may send requests to an uncommon DNS domain the malware uses for command-and-control communication. |[Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning] |8.3.0 |103
+
+|<<unusual-parent-process-for-cmd-exe, Unusual Parent Process for cmd.exe>> |Identifies a suspicious parent child process relationship with cmd.exe descending from an unusual process. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
+
+|<<unusual-parent-child-relationship, Unusual Parent-Child Relationship>> |Identifies Windows programs run from unexpected parent processes. This could indicate masquerading or other strange activity on a system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<unusual-persistence-via-services-registry, Unusual Persistence via Services Registry>> |Identifies processes modifying the services registry key directly, instead of through the expected Windows APIs. This could be an indication of an adversary attempting to stealthily persist through abnormal service creation or modification of an existing service. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
+
+|<<unusual-print-spooler-child-process, Unusual Print Spooler Child Process>> |Detects unusual Print Spooler service (spoolsv.exe) child processes. This may indicate an attempt to exploit privilege escalation vulnerabilities related to the Printing Service on Windows. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Use Case: Vulnerability], [Data Source: Elastic Defend] |8.3.0 |108
+
+|<<unusual-process-execution-path-alternate-data-stream, Unusual Process Execution Path - Alternate Data Stream>> |Identifies processes running from an Alternate Data Stream. This is uncommon for legitimate processes and sometimes done by adversaries to hide malware. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<unusual-process-execution-on-wbem-path, Unusual Process Execution on WBEM Path>> |Identifies unusual processes running from the WBEM path, uncommon outside WMI-related Windows processes. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Rule Type: BBR], [Data Source: Elastic Endgame] |8.3.0 |2
+
+|<<unusual-process-extension, Unusual Process Extension>> |Identifies processes running with unusual extensions that are not typically valid for Windows executables. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |4
+
+|<<unusual-process-for-mssql-service-accounts, Unusual Process For MSSQL Service Accounts>> |Identifies unusual process executions using MSSQL Service accounts, which can indicate the exploitation/compromise of SQL instances. Attackers may exploit exposed MSSQL instances for initial access or lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Persistence], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |4
+
+|<<unusual-process-for-a-linux-host, Unusual Process For a Linux Host>> |Identifies rare processes that do not usually run on individual hosts, which can indicate execution of unauthorized services, malware, or persistence mechanisms. Processes are considered rare when they only run occasionally as compared with other processes running on the host. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Persistence] |8.3.0 |104
+
+|<<unusual-process-for-a-windows-host, Unusual Process For a Windows Host>> |Identifies rare processes that do not usually run on individual hosts, which can indicate execution of unauthorized services, malware, or persistence mechanisms. Processes are considered rare when they only run occasionally as compared with other processes running on the host. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Persistence], [Resources: Investigation Guide] |8.3.0 |107
+
+|<<unusual-process-network-connection, Unusual Process Network Connection>> |Identifies network activity from unexpected system applications. This may indicate adversarial activity as these applications are often leveraged by adversaries to execute code and evade detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |108
+
+|<<unusual-process-spawned-by-a-host, Unusual Process Spawned by a Host>> |A machine learning job has detected a suspicious Windows process. This process has been classified as suspicious in two ways. It was predicted to be suspicious by the ProblemChild supervised ML model, and it was found to be an unusual process, on a host that does not commonly manifest malicious activity. Such a process may be an instance of suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules. |[Domain: Endpoint], [OS: Windows], [Use Case: Living off the Land Attack Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Defense Evasion] |8.9.0 |4
+
+|<<unusual-process-spawned-by-a-parent-process, Unusual Process Spawned by a Parent Process>> |A machine learning job has detected a suspicious Windows process. This process has been classified as malicious in two ways. It was predicted to be malicious by the ProblemChild supervised ML model, and it was found to be an unusual child process name, for the parent process, by an unsupervised ML model. Such a process may be an instance of suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules. |[Domain: Endpoint], [OS: Windows], [Use Case: Living off the Land Attack Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Defense Evasion] |8.9.0 |4
+
+|<<unusual-process-spawned-by-a-user, Unusual Process Spawned by a User>> |A machine learning job has detected a suspicious Windows process. This process has been classified as malicious in two ways. It was predicted to be malicious by the ProblemChild supervised ML model, and it was found to be suspicious given that its user context is unusual and does not commonly manifest malicious activity,by an unsupervised ML model. Such a process may be an instance of suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules. |[Domain: Endpoint], [OS: Windows], [Use Case: Living off the Land Attack Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Defense Evasion] |8.9.0 |4
+
+|<<unusual-process-writing-data-to-an-external-device, Unusual Process Writing Data to an External Device>> |A machine learning job has detected a rare process writing data to an external device. Malicious actors often use benign-looking processes to mask their data exfiltration activities. The discovery of such a process that has no legitimate reason to write data to external devices can indicate exfiltration. |[Use Case: Data Exfiltration Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Exfiltration] |8.9.0 |3
+
+|<<unusual-remote-file-directory, Unusual Remote File Directory>> |An anomaly detection job has detected a remote file transfer on an unusual directory indicating a potential lateral movement activity on the host. Many Security solutions monitor well-known directories for suspicious activities, so attackers might use less common directories to bypass monitoring. |[Use Case: Lateral Movement Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Lateral Movement] |8.9.0 |3
+
+|<<unusual-remote-file-extension, Unusual Remote File Extension>> |An anomaly detection job has detected a remote file transfer with a rare extension, which could indicate potential lateral movement activity on the host. |[Use Case: Lateral Movement Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Lateral Movement] |8.9.0 |3
+
+|<<unusual-remote-file-size, Unusual Remote File Size>> |A machine learning job has detected an unusually high file size shared by a remote host indicating potential lateral movement activity. One of the primary goals of attackers after gaining access to a network is to locate and exfiltrate valuable information. Instead of multiple small transfers that can raise alarms, attackers might choose to bundle data into a single large file transfer. |[Use Case: Lateral Movement Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Lateral Movement] |8.9.0 |3
+
+|<<unusual-service-host-child-process-childless-service, Unusual Service Host Child Process - Childless Service>> |Identifies unusual child processes of Service Host (svchost.exe) that traditionally do not spawn any child processes. This may indicate a code injection or an equivalent form of exploitation. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Privilege Escalation], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
+
+|<<unusual-source-ip-for-a-user-to-logon-from, Unusual Source IP for a User to Logon from>> |A machine learning job detected a user logging in from an IP address that is unusual for the user. This can be due to credentialed access via a compromised account when the user and the threat actor are in different locations. An unusual source IP address for a username could also be due to lateral movement when a compromised account is used to pivot between hosts. |[Use Case: Identity and Access Audit], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Initial Access] |8.3.0 |103
+
+|<<unusual-sudo-activity, Unusual Sudo Activity>> |Looks for sudo activity from an unusual user context. An unusual sudo user could be due to troubleshooting activity or it could be a sign of credentialed access via compromised accounts. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Privilege Escalation] |8.3.0 |103
+
+|<<unusual-time-or-day-for-an-rdp-session, Unusual Time or Day for an RDP Session>> |A machine learning job has detected an RDP session started at an usual time or weekday. An RDP session at an unusual time could be followed by other suspicious activities, so catching this is a good first step in detecting a larger attack. |[Use Case: Lateral Movement Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Lateral Movement] |8.9.0 |3
+
+|<<unusual-user-privilege-enumeration-via-id, Unusual User Privilege Enumeration via id>> |This rule monitors for a sequence of 20 "id" command executions within 1 second by the same parent process. This behavior is unusual, and may be indicative of the execution of an enumeration script such as LinPEAS or LinEnum. These scripts leverage the "id" command to enumerate the privileges of all users present on the system. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend] |8.3.0 |4
+
+|<<unusual-web-request, Unusual Web Request>> |A machine learning job detected a rare and unusual URL that indicates unusual web browsing activity. This can be due to initial access, persistence, command-and-control, or exfiltration activity. For example, in a strategic web compromise or watering hole attack, when a trusted website is compromised to target a particular sector or organization, targeted users may receive emails with uncommon URLs for trusted websites. These URLs can be used to download and run a payload. When malware is already running, it may send requests to uncommon URLs on trusted websites the malware uses for command-and-control communication. When rare URLs are observed being requested for a local web server by a remote source, these can be due to web scanning, enumeration or attack traffic, or they can be due to bots and web scrapers which are part of common Internet background traffic. |[Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Command and Control] |8.3.0 |103
+
+|<<unusual-web-user-agent, Unusual Web User Agent>> |A machine learning job detected a rare and unusual user agent indicating web browsing activity by an unusual process other than a web browser. This can be due to persistence, command-and-control, or exfiltration activity. Uncommon user agents coming from remote sources to local destinations are often the result of scanners, bots, and web scrapers, which are part of common Internet background traffic. Much of this is noise, but more targeted attacks on websites using tools like Burp or SQLmap can sometimes be discovered by spotting uncommon user agents. Uncommon user agents in traffic from local sources to remote destinations can be any number of things, including harmless programs like weather monitoring or stock-trading programs. However, uncommon user agents from local sources can also be due to malware or scanning activity. |[Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Command and Control] |8.3.0 |103
+
+|<<unusual-windows-network-activity, Unusual Windows Network Activity>> |Identifies Windows processes that do not usually use the network but have unexpected network activity, which can indicate command-and-control, lateral movement, persistence, or data exfiltration activity. A process with unusual network activity can denote process exploitation or injection, where the process is used to run persistence mechanisms that allow a malicious actor remote access or control of the host, data exfiltration, and execution of unauthorized network applications. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning] |8.3.0 |103
+
+|<<unusual-windows-path-activity, Unusual Windows Path Activity>> |Identifies processes started from atypical folders in the file system, which might indicate malware execution or persistence mechanisms. In corporate Windows environments, software installation is centrally managed and it is unusual for programs to be executed from user or temporary directories. Processes executed from these locations can denote that a user downloaded software directly from the Internet or a malicious script or macro executed malware. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Persistence], [Tactic: Execution] |8.3.0 |104
+
+|<<unusual-windows-process-calling-the-metadata-service, Unusual Windows Process Calling the Metadata Service>> |Looks for anomalous access to the metadata service by an unusual process. The metadata service may be targeted in order to harvest credentials or user data scripts containing secrets. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Credential Access] |8.3.0 |103
+
+|<<unusual-windows-remote-user, Unusual Windows Remote User>> |A machine learning job detected an unusual remote desktop protocol (RDP) username, which can indicate account takeover or credentialed persistence using compromised accounts. RDP attacks, such as BlueKeep, also tend to use unusual usernames. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Initial Access] |8.3.0 |103
+
+|<<unusual-windows-service, Unusual Windows Service>> |A machine learning job detected an unusual Windows service, This can indicate execution of unauthorized services, malware, or persistence mechanisms. In corporate Windows environments, hosts do not generally run many rare or unique services. This job helps detect malware and persistence mechanisms that have been installed and run as a service. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Persistence] |8.3.0 |103
+
+|<<unusual-windows-user-calling-the-metadata-service, Unusual Windows User Calling the Metadata Service>> |Looks for anomalous access to the cloud platform metadata service by an unusual user. The metadata service may be targeted in order to harvest credentials or user data scripts containing secrets. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Credential Access] |8.3.0 |103
+
+|<<unusual-windows-user-privilege-elevation-activity, Unusual Windows User Privilege Elevation Activity>> |A machine learning job detected an unusual user context switch, using the runas command or similar techniques, which can indicate account takeover or privilege escalation using compromised accounts. Privilege elevation using tools like runas are more commonly used by domain and network administrators than by regular Windows users. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Privilege Escalation] |8.3.0 |103
+
+|<<unusual-windows-username, Unusual Windows Username>> |A machine learning job detected activity for a username that is not normally active, which can indicate unauthorized changes, activity by unauthorized users, lateral movement, or compromised credentials. In many organizations, new usernames are not often created apart from specific types of system activities, such as creating new accounts for new employees. These user accounts quickly become active and routine. Events from rarely used usernames can point to suspicious activity. Additionally, automated Linux fleets tend to see activity from rarely used usernames only when personnel log in to make authorized or unauthorized changes, or threat actors have acquired credentials and log in for malicious purposes. Unusual usernames can also indicate pivoting, where compromised credentials are used to try and move laterally from one host to another. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Rule Type: ML], [Rule Type: Machine Learning], [Tactic: Initial Access] |8.3.0 |104
+
+|<<user-account-creation, User Account Creation>> |Identifies attempts to create new users. This is sometimes done by attackers to increase access or establish persistence on a system or domain. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |109
+
+|<<user-added-as-owner-for-azure-application, User Added as Owner for Azure Application>> |Identifies when a user is added as an owner for an Azure application. An adversary may add a user account as an owner for an Azure application in order to grant additional permissions and modify the application's configuration using another account. |[Domain: Cloud], [Data Source: Azure], [Use Case: Configuration Audit], [Tactic: Persistence] |8.3.0 |102
+
+|<<user-added-as-owner-for-azure-service-principal, User Added as Owner for Azure Service Principal>> |Identifies when a user is added as an owner for an Azure service principal. The service principal object defines what the application can do in the specific tenant, who can access the application, and what resources the app can access. A service principal object is created when an application is given permission to access resources in a tenant. An adversary may add a user account as an owner for a service principal and use that account in order to define what an application can do in the Azure AD tenant. |[Domain: Cloud], [Data Source: Azure], [Use Case: Configuration Audit], [Tactic: Persistence] |8.3.0 |102
+
+|<<user-added-to-privileged-group, User Added to Privileged Group>> |Identifies a user being added to a privileged group in Active Directory. Privileged accounts and groups in Active Directory are those to which powerful rights, privileges, and permissions are granted that allow them to perform nearly any action in Active Directory and on domain-joined systems. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring], [Data Source: Active Directory] |8.3.0 |109
+
+|<<user-account-exposed-to-kerberoasting, User account exposed to Kerberoasting>> |Detects when a user account has the servicePrincipalName attribute modified. Attackers can abuse write privileges over a user to configure Service Principle Names (SPNs) so that they can perform Kerberoasting. Administrators can also configure this for legitimate purposes, exposing the account to Kerberoasting. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Active Directory], [Resources: Investigation Guide], [Use Case: Active Directory Monitoring] |8.3.0 |109
+
+|<<vnc-virtual-network-computing-from-the-internet, VNC (Virtual Network Computing) from the Internet>> |This rule detects network events that may indicate the use of VNC traffic from the Internet. VNC is commonly used by system administrators to remotely control a system for maintenance or to use shared resources. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. |[Tactic: Command and Control], [Domain: Endpoint], [Use Case: Threat Detection] |8.3.0 |104
+
+|<<vnc-virtual-network-computing-to-the-internet, VNC (Virtual Network Computing) to the Internet>> |This rule detects network events that may indicate the use of VNC traffic to the Internet. VNC is commonly used by system administrators to remotely control a system for maintenance or to use shared resources. It should almost never be directly exposed to the Internet, as it is frequently targeted and exploited by threat actors as an initial access or backdoor vector. |[Tactic: Command and Control], [Domain: Endpoint], [Use Case: Threat Detection] |8.3.0 |104
+
+|<<veeam-backup-library-loaded-by-unusual-process, Veeam Backup Library Loaded by Unusual Process>> |Identifies potential credential decrypt operations by PowerShell or unsigned processes using the Veeam.Backup.Common.dll library. Attackers can use Veeam Credentials to target backups as part of destructive operations such as Ransomware attacks. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.3.0 |2
+
+|<<virtual-machine-fingerprinting, Virtual Machine Fingerprinting>> |An adversary may attempt to get detailed information about the operating system and hardware. This rule identifies common locations used to discover virtual machine hardware by a non-root user. This technique has been used by the Pupy RAT and other malware. |[Domain: Endpoint], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |108
+
+|<<virtual-machine-fingerprinting-via-grep, Virtual Machine Fingerprinting via Grep>> |An adversary may attempt to get detailed information about the operating system and hardware. This rule identifies common locations used to discover virtual machine hardware by a non-root user. This technique has been used by the Pupy RAT and other malware. |[Domain: Endpoint], [OS: macOS], [OS: Linux], [Use Case: Threat Detection], [Tactic: Discovery], [Data Source: Elastic Defend] |8.3.0 |105
+
+|<<virtual-private-network-connection-attempt, Virtual Private Network Connection Attempt>> |Identifies the execution of macOS built-in commands to connect to an existing Virtual Private Network (VPN). Adversaries may use VPN connections to laterally move and control remote systems on a network. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend] |8.3.0 |107
+
+|<<volume-shadow-copy-deleted-or-resized-via-vssadmin, Volume Shadow Copy Deleted or Resized via VssAdmin>> |Identifies use of vssadmin.exe for shadow copy deletion or resizing on endpoints. This commonly occurs in tandem with ransomware or other destructive attacks. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Impact], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<volume-shadow-copy-deletion-via-powershell, Volume Shadow Copy Deletion via PowerShell>> |Identifies the use of the Win32_ShadowCopy class and related cmdlets to achieve shadow copy deletion. This commonly occurs in tandem with ransomware or other destructive attacks. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Impact], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<volume-shadow-copy-deletion-via-wmic, Volume Shadow Copy Deletion via WMIC>> |Identifies use of wmic.exe for shadow copy deletion on endpoints. This commonly occurs in tandem with ransomware or other destructive attacks. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Impact], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<wmi-incoming-lateral-movement, WMI Incoming Lateral Movement>> |Identifies processes executed via Windows Management Instrumentation (WMI) on a remote host. This could be indicative of adversary lateral movement, but could be noisy if administrators use WMI to remotely manage hosts. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |110
+
+|<<wmi-wbemtest-utility-execution, WMI WBEMTEST Utility Execution>> |Adversaries may abuse the WMI diagnostic tool, wbemtest.exe, to enumerate WMI object instances or invoke methods against local or remote endpoints. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Execution], [Data Source: Elastic Defend], [Rule Type: BBR], [Data Source: Elastic Endgame] |8.3.0 |2
+
+|<<wmic-remote-command, WMIC Remote Command>> |Identifies the use of wmic.exe to run commands on remote hosts. While this can be used by administrators legitimately, attackers can abuse this built-in utility to achieve lateral movement. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |4
+
+|<<wpad-service-exploit, WPAD Service Exploit>> |Identifies probable exploitation of the Web Proxy Auto-Discovery Protocol (WPAD) service. Attackers who have access to the local network or upstream DNS traffic can inject malicious JavaScript to the WPAD service which can lead to a full system compromise. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation], [Data Source: Elastic Defend] |None |1
+
+|<<writedac-access-on-active-directory-object, WRITEDAC Access on Active Directory Object>> |Identifies the access on an object with WRITEDAC permissions. With the WRITEDAC permission, the user can perform a Write Discretionary Access Control List (WriteDACL) operation, which is used to modify the access control rules associated with a specific object within Active Directory. Attackers may abuse this privilege to grant themselves or other compromised accounts additional rights, ultimately compromising the target object, resulting in privilege escalation, lateral movement, and persistence. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Active Directory], [Use Case: Active Directory Monitoring], [Rule Type: BBR] |8.3.0 |4
+
+|<<web-application-suspicious-activity-post-request-declined, Web Application Suspicious Activity: POST Request Declined>> |A POST request to a web application returned a 403 response, which indicates the web application declined to process the request because the action requested was not allowed. |[Data Source: APM] |8.3.0 |102
+
+|<<web-application-suspicious-activity-unauthorized-method, Web Application Suspicious Activity: Unauthorized Method>> |A request to a web application returned a 405 response, which indicates the web application declined to process the request because the HTTP method is not allowed for the resource. |[Data Source: APM] |8.3.0 |102
+
+|<<web-application-suspicious-activity-sqlmap-user-agent, Web Application Suspicious Activity: sqlmap User Agent>> |This is an example of how to detect an unwanted web client user agent. This search matches the user agent for sqlmap 1.3.11, which is a popular FOSS tool for testing web applications for SQL injection vulnerabilities. |[Data Source: APM] |8.3.0 |102
+
+|<<web-shell-detection-script-process-child-of-common-web-processes, Web Shell Detection: Script Process Child of Common Web Processes>> |Identifies suspicious commands executed via a web server, which may suggest a vulnerability and remote shell access. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Tactic: Initial Access], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<webproxy-settings-modification, WebProxy Settings Modification>> |Identifies the use of the built-in networksetup command to configure webproxy settings. This may indicate an attempt to hijack web browser traffic for credential access via traffic sniffing or redirection. |[Domain: Endpoint], [OS: macOS], [Use Case: Threat Detection], [Tactic: Credential Access], [Data Source: Elastic Defend] |8.7.0 |206
+
+|<<webserver-access-logs-deleted, WebServer Access Logs Deleted>> |Identifies the deletion of WebServer access logs. This may indicate an attempt to evade detection or destroy forensic evidence on a system. |[Domain: Endpoint], [OS: Linux], [OS: Windows], [OS: macOS], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |105
+
+|<<werfault-reflectdebugger-persistence, Werfault ReflectDebugger Persistence>> |Identifies the registration of a Werfault Debugger. Attackers may abuse this mechanism to execute malicious payloads every time the utility is executed with the "-pr" parameter. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |2
+
+|<<whoami-process-activity, Whoami Process Activity>> |Identifies suspicious use of whoami.exe which displays user, group, and privileges information for the user who is currently logged on to the local system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |111
+
+|<<windows-account-or-group-discovery, Windows Account or Group Discovery>> |This rule identifies the execution of commands that enumerates account or group information. Adversaries may use built-in applications to get a listing of local system or domain accounts and groups. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |4
+
+|<<windows-cryptoapi-spoofing-vulnerability-cve-2020-0601-curveball, Windows CryptoAPI Spoofing Vulnerability (CVE-2020-0601 - CurveBall)>> |A spoofing vulnerability exists in the way Windows CryptoAPI (Crypt32.dll) validates Elliptic Curve Cryptography (ECC) certificates. An attacker could exploit the vulnerability by using a spoofed code-signing certificate to sign a malicious executable, making it appear the file was from a trusted, legitimate source. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Use Case: Vulnerability] |8.3.0 |104
+
+|<<windows-defender-disabled-via-registry-modification, Windows Defender Disabled via Registry Modification>> |Identifies modifications to the Windows Defender registry settings to disable the service or set the service to be started manually. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
+
+|<<windows-defender-exclusions-added-via-powershell, Windows Defender Exclusions Added via PowerShell>> |Identifies modifications to the Windows Defender configuration settings using PowerShell to add exclusions at the folder directory or process level. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<windows-event-logs-cleared, Windows Event Logs Cleared>> |Identifies attempts to clear Windows event log stores. This is often done by attackers in an attempt to evade detection or destroy forensic evidence on a system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Resources: Investigation Guide] |8.3.0 |108
+
+|<<windows-firewall-disabled-via-powershell, Windows Firewall Disabled via PowerShell>> |Identifies when the Windows Firewall is disabled using PowerShell cmdlets, which can help attackers evade network constraints, like internet and network lateral communication restrictions. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |110
+
+|<<windows-installer-with-suspicious-properties, Windows Installer with Suspicious Properties>> |Identifies the execution of an installer from an archive or with suspicious properties. Adversaries may abuse msiexec.exe to launch local or network accessible MSI files in an attempt to bypass application whitelisting. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |1
+
+|<<windows-network-enumeration, Windows Network Enumeration>> |Identifies attempts to enumerate hosts in a network using the built-in Windows net.exe tool. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Tactic: Collection], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Rule Type: BBR] |8.3.0 |111
+
+|<<windows-registry-file-creation-in-smb-share, Windows Registry File Creation in SMB Share>> |Identifies the creation or modification of a medium-size registry hive file on a Server Message Block (SMB) share, which may indicate an exfiltration attempt of a previously dumped Security Account Manager (SAM) registry hive for credential extraction on an attacker-controlled system. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Lateral Movement], [Tactic: Credential Access], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |108
+
+|<<windows-script-executing-powershell, Windows Script Executing PowerShell>> |Identifies a PowerShell process launched by either cscript.exe or wscript.exe. Observing Windows scripting processes executing a PowerShell script, may be indicative of malicious activity. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Execution], [Resources: Investigation Guide], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |111
+
+|<<windows-script-interpreter-executing-process-via-wmi, Windows Script Interpreter Executing Process via WMI>> |Identifies use of the built-in Windows script interpreters (cscript.exe or wscript.exe) being used to execute a process via Windows Management Instrumentation (WMI). This may be indicative of malicious activity. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Initial Access], [Tactic: Execution], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |109
+
+|<<windows-service-installed-via-an-unusual-client, Windows Service Installed via an Unusual Client>> |Identifies the creation of a Windows service by an unusual client process. Services may be created with administrator privileges but are executed under SYSTEM privileges, so an adversary may also use a service to escalate privileges from administrator to SYSTEM. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Privilege Escalation] |8.3.0 |109
+
+|<<windows-subsystem-for-linux-distribution-installed, Windows Subsystem for Linux Distribution Installed>> |Detects changes to the registry that indicates the install of a new Windows Subsystem for Linux distribution by name. Adversaries may enable and use WSL for Linux to avoid detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend], [Data Source: Sysmon] |8.3.0 |7
+
+|<<windows-subsystem-for-linux-enabled-via-dism-utility, Windows Subsystem for Linux Enabled via Dism Utility>> |Detects attempts to enable the Windows Subsystem for Linux using Microsoft Dism utility. Adversaries may enable and use WSL for Linux to avoid detection. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Defense Evasion], [Data Source: Elastic Endgame], [Data Source: Elastic Defend] |8.3.0 |7
+
+|<<windows-system-information-discovery, Windows System Information Discovery>> |Detects the execution of commands used to discover information about the system, which attackers may use after compromising a system to gain situational awareness. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend], [Data Source: Elastic Endgame] |8.3.0 |4
+
+|<<windows-system-network-connections-discovery, Windows System Network Connections Discovery>> |This rule identifies the execution of commands that can be used to enumerate network connections. Adversaries may attempt to get a listing of network connections to or from a compromised system to identify targets within an environment. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Discovery], [Rule Type: BBR], [Data Source: Elastic Defend] |8.3.0 |4
+
+|<<windows-user-account-creation, Windows User Account Creation>> |Identifies attempts to create a Windows User Account. This is sometimes done by attackers to persist or increase access to a system or domain. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Persistence] |None |1
+
+|<<wireless-credential-dumping-using-netsh-command, Wireless Credential Dumping using Netsh Command>> |Identifies attempts to dump Wireless saved access keys in clear text using the Windows built-in utility Netsh. |[Domain: Endpoint], [OS: Windows], [Use Case: Threat Detection], [Tactic: Credential Access], [Tactic: Discovery], [Data Source: Elastic Endgame], [Resources: Investigation Guide], [Data Source: Elastic Defend] |8.3.0 |8
+
+|<<zoom-meeting-with-no-passcode, Zoom Meeting with no Passcode>> |This rule identifies Zoom meetings that are created without a passcode. Meetings without a passcode are susceptible to Zoombombing. Zoombombing is carried out by taking advantage of Zoom sessions that are not protected with a passcode. Zoombombing refers to the unwanted, disruptive intrusion, generally by Internet trolls and hackers, into a video conference call. In a typical Zoombombing incident, a teleconferencing session is hijacked by the insertion of material that is lewd, obscene, racist, or antisemitic in nature, typically resulting of the shutdown of the session. |[Data Source: Zoom], [Use Case: Configuration Audit], [Tactic: Initial Access] |8.3.0 |103
+
+|==============================================
diff --git a/docs/detections/prebuilt-rules/rule-desc-index.asciidoc b/docs/detections/prebuilt-rules/rule-desc-index.asciidoc
index 8887ec2357..3677aa188c 100644
--- a/docs/detections/prebuilt-rules/rule-desc-index.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-desc-index.asciidoc
@@ -1,6 +1,8 @@
 include::rule-details/a-scheduled-task-was-created.asciidoc[]
 include::rule-details/a-scheduled-task-was-updated.asciidoc[]
-include::rule-details/aws-access-secret-in-secrets-manager.asciidoc[]
+include::rule-details/aws-bedrock-detected-multiple-attempts-to-use-denied-models-by-a-single-user.asciidoc[]
+include::rule-details/aws-bedrock-guardrails-detected-multiple-policy-violations-within-a-single-blocked-request.asciidoc[]
+include::rule-details/aws-bedrock-guardrails-detected-multiple-violations-by-a-single-user-over-a-session.asciidoc[]
 include::rule-details/aws-cloudtrail-log-created.asciidoc[]
 include::rule-details/aws-cloudtrail-log-deleted.asciidoc[]
 include::rule-details/aws-cloudtrail-log-suspended.asciidoc[]
@@ -10,7 +12,9 @@ include::rule-details/aws-cloudwatch-log-group-deletion.asciidoc[]
 include::rule-details/aws-cloudwatch-log-stream-deletion.asciidoc[]
 include::rule-details/aws-config-resource-deletion.asciidoc[]
 include::rule-details/aws-configuration-recorder-stopped.asciidoc[]
+include::rule-details/aws-credentials-searched-for-inside-a-container.asciidoc[]
 include::rule-details/aws-deletion-of-rds-instance-or-cluster.asciidoc[]
+include::rule-details/aws-ec2-admin-credential-fetch-via-assumed-role.asciidoc[]
 include::rule-details/aws-ec2-encryption-disabled.asciidoc[]
 include::rule-details/aws-ec2-full-network-packet-capture-detected.asciidoc[]
 include::rule-details/aws-ec2-network-access-control-list-creation.asciidoc[]
@@ -28,6 +32,7 @@ include::rule-details/aws-iam-brute-force-of-assume-role-policy.asciidoc[]
 include::rule-details/aws-iam-deactivation-of-mfa-device.asciidoc[]
 include::rule-details/aws-iam-group-creation.asciidoc[]
 include::rule-details/aws-iam-group-deletion.asciidoc[]
+include::rule-details/aws-iam-login-profile-added-to-user.asciidoc[]
 include::rule-details/aws-iam-password-recovery-requested.asciidoc[]
 include::rule-details/aws-iam-user-addition-to-group.asciidoc[]
 include::rule-details/aws-kms-customer-managed-key-disabled-or-scheduled-for-deletion.asciidoc[]
@@ -48,6 +53,7 @@ include::rule-details/aws-route-table-created.asciidoc[]
 include::rule-details/aws-route-table-modified-or-deleted.asciidoc[]
 include::rule-details/aws-route53-private-hosted-zone-associated-with-a-vpc.asciidoc[]
 include::rule-details/aws-s3-bucket-configuration-deletion.asciidoc[]
+include::rule-details/aws-s3-bucket-enumeration-or-brute-force.asciidoc[]
 include::rule-details/aws-saml-activity.asciidoc[]
 include::rule-details/aws-sts-getsessiontoken-abuse.asciidoc[]
 include::rule-details/aws-security-group-configuration-change-detection.asciidoc[]
@@ -58,12 +64,13 @@ include::rule-details/aws-waf-rule-or-rule-group-deletion.asciidoc[]
 include::rule-details/abnormal-process-id-or-lock-file-created.asciidoc[]
 include::rule-details/abnormally-large-dns-response.asciidoc[]
 include::rule-details/accepted-default-telnet-port-connection.asciidoc[]
-include::rule-details/access-of-stored-browser-credentials.asciidoc[]
 include::rule-details/access-to-keychain-credentials-directories.asciidoc[]
 include::rule-details/access-to-a-sensitive-ldap-attribute.asciidoc[]
+include::rule-details/accessing-outlook-data-files.asciidoc[]
 include::rule-details/account-configured-with-never-expiring-password.asciidoc[]
 include::rule-details/account-discovery-command-via-system-account.asciidoc[]
 include::rule-details/account-password-reset-remotely.asciidoc[]
+include::rule-details/account-or-group-discovery-via-built-in-tools.asciidoc[]
 include::rule-details/adfind-command-activity.asciidoc[]
 include::rule-details/adding-hidden-file-attribute-via-attrib.asciidoc[]
 include::rule-details/adminsdholder-backdoor.asciidoc[]
@@ -74,6 +81,7 @@ include::rule-details/adobe-hijack-persistence.asciidoc[]
 include::rule-details/adversary-behavior-detected-elastic-endgame.asciidoc[]
 include::rule-details/agent-spoofing-mismatched-agent-id.asciidoc[]
 include::rule-details/agent-spoofing-multiple-hosts-using-same-agent.asciidoc[]
+include::rule-details/alternate-data-stream-creation-execution-at-volume-root-directory.asciidoc[]
 include::rule-details/anomalous-linux-compiler-activity.asciidoc[]
 include::rule-details/anomalous-process-for-a-linux-population.asciidoc[]
 include::rule-details/anomalous-process-for-a-windows-population.asciidoc[]
@@ -82,8 +90,10 @@ include::rule-details/apple-script-execution-followed-by-network-connection.asci
 include::rule-details/apple-scripting-execution-with-administrator-privileges.asciidoc[]
 include::rule-details/application-added-to-google-workspace-domain.asciidoc[]
 include::rule-details/application-removed-from-blocklist-in-google-workspace.asciidoc[]
+include::rule-details/archive-file-with-unusual-extension.asciidoc[]
+include::rule-details/at-exe-command-lateral-movement.asciidoc[]
+include::rule-details/attempt-to-clear-kernel-ring-buffer.asciidoc[]
 include::rule-details/attempt-to-create-okta-api-token.asciidoc[]
-include::rule-details/attempt-to-deactivate-mfa-for-an-okta-user-account.asciidoc[]
 include::rule-details/attempt-to-deactivate-an-okta-application.asciidoc[]
 include::rule-details/attempt-to-deactivate-an-okta-network-zone.asciidoc[]
 include::rule-details/attempt-to-deactivate-an-okta-policy.asciidoc[]
@@ -93,19 +103,21 @@ include::rule-details/attempt-to-delete-an-okta-network-zone.asciidoc[]
 include::rule-details/attempt-to-delete-an-okta-policy.asciidoc[]
 include::rule-details/attempt-to-delete-an-okta-policy-rule.asciidoc[]
 include::rule-details/attempt-to-disable-gatekeeper.asciidoc[]
+include::rule-details/attempt-to-disable-iptables-or-firewall.asciidoc[]
 include::rule-details/attempt-to-disable-syslog-service.asciidoc[]
 include::rule-details/attempt-to-enable-the-root-account.asciidoc[]
+include::rule-details/attempt-to-install-kali-linux-via-wsl.asciidoc[]
 include::rule-details/attempt-to-install-root-certificate.asciidoc[]
 include::rule-details/attempt-to-modify-an-okta-application.asciidoc[]
 include::rule-details/attempt-to-modify-an-okta-network-zone.asciidoc[]
 include::rule-details/attempt-to-modify-an-okta-policy.asciidoc[]
 include::rule-details/attempt-to-modify-an-okta-policy-rule.asciidoc[]
 include::rule-details/attempt-to-mount-smb-share-via-command-line.asciidoc[]
-include::rule-details/attempt-to-remove-file-quarantine-attribute.asciidoc[]
 include::rule-details/attempt-to-reset-mfa-factors-for-an-okta-user-account.asciidoc[]
 include::rule-details/attempt-to-revoke-okta-api-token.asciidoc[]
 include::rule-details/attempt-to-unload-elastic-endpoint-security-kernel-extension.asciidoc[]
 include::rule-details/attempted-bypass-of-okta-mfa.asciidoc[]
+include::rule-details/attempted-private-key-access.asciidoc[]
 include::rule-details/attempts-to-brute-force-a-microsoft-365-user-account.asciidoc[]
 include::rule-details/attempts-to-brute-force-an-okta-user-account.asciidoc[]
 include::rule-details/authorization-plugin-modification.asciidoc[]
@@ -145,26 +157,38 @@ include::rule-details/azure-virtual-network-device-modified-or-deleted.asciidoc[
 include::rule-details/bpf-filter-applied-using-tc.asciidoc[]
 include::rule-details/base16-or-base32-encoding-decoding-activity.asciidoc[]
 include::rule-details/bash-shell-profile-modification.asciidoc[]
+include::rule-details/binary-content-copy-via-cmd-exe.asciidoc[]
 include::rule-details/binary-executed-from-shared-memory-directory.asciidoc[]
+include::rule-details/bitsadmin-activity.asciidoc[]
+include::rule-details/browser-extension-install.asciidoc[]
 include::rule-details/bypass-uac-via-event-viewer.asciidoc[]
+include::rule-details/cap-sys-admin-assigned-to-binary.asciidoc[]
 include::rule-details/chkconfig-service-add.asciidoc[]
 include::rule-details/clearing-windows-console-history.asciidoc[]
 include::rule-details/clearing-windows-event-logs.asciidoc[]
 include::rule-details/cobalt-strike-command-and-control-beacon.asciidoc[]
+include::rule-details/code-signing-policy-modification-through-built-in-tools.asciidoc[]
+include::rule-details/code-signing-policy-modification-through-registry.asciidoc[]
 include::rule-details/command-execution-via-solarwinds-process.asciidoc[]
 include::rule-details/command-prompt-network-connection.asciidoc[]
 include::rule-details/command-shell-activity-started-via-rundll32.asciidoc[]
 include::rule-details/component-object-model-hijacking.asciidoc[]
+include::rule-details/compression-dll-loaded-by-unusual-process.asciidoc[]
 include::rule-details/conhost-spawned-by-suspicious-parent-process.asciidoc[]
 include::rule-details/connection-to-commonly-abused-free-ssl-certificate-providers.asciidoc[]
 include::rule-details/connection-to-commonly-abused-web-services.asciidoc[]
 include::rule-details/connection-to-external-network-via-telnet.asciidoc[]
 include::rule-details/connection-to-internal-network-via-telnet.asciidoc[]
+include::rule-details/container-management-utility-run-inside-a-container.asciidoc[]
+include::rule-details/container-workload-protection.asciidoc[]
 include::rule-details/control-panel-process-with-unusual-arguments.asciidoc[]
 include::rule-details/creation-of-hidden-files-and-directories-via-commandline.asciidoc[]
 include::rule-details/creation-of-hidden-launch-agent-or-daemon.asciidoc[]
 include::rule-details/creation-of-hidden-login-item-via-apple-script.asciidoc[]
 include::rule-details/creation-of-hidden-shared-object-file.asciidoc[]
+include::rule-details/creation-of-kernel-module.asciidoc[]
+include::rule-details/creation-of-settingcontent-ms-files.asciidoc[]
+include::rule-details/creation-of-a-dns-named-record.asciidoc[]
 include::rule-details/creation-of-a-hidden-local-user-account.asciidoc[]
 include::rule-details/creation-or-modification-of-domain-backup-dpapi-private-key.asciidoc[]
 include::rule-details/creation-or-modification-of-root-certificate.asciidoc[]
@@ -174,11 +198,13 @@ include::rule-details/credential-dumping-detected-elastic-endgame.asciidoc[]
 include::rule-details/credential-dumping-prevented-elastic-endgame.asciidoc[]
 include::rule-details/credential-manipulation-detected-elastic-endgame.asciidoc[]
 include::rule-details/credential-manipulation-prevented-elastic-endgame.asciidoc[]
+include::rule-details/cron-job-created-or-changed-by-previously-unknown-process.asciidoc[]
 include::rule-details/cyberark-privileged-access-security-error.asciidoc[]
 include::rule-details/cyberark-privileged-access-security-recommended-monitor.asciidoc[]
 include::rule-details/dns-tunneling.asciidoc[]
 include::rule-details/dns-over-https-enabled-via-registry.asciidoc[]
 include::rule-details/default-cobalt-strike-team-server-certificate.asciidoc[]
+include::rule-details/delayed-execution-via-ping.asciidoc[]
 include::rule-details/delete-volume-usn-journal-with-fsutil.asciidoc[]
 include::rule-details/deleting-backup-catalogs-with-wbadmin.asciidoc[]
 include::rule-details/direct-outbound-smb-connection.asciidoc[]
@@ -186,10 +212,18 @@ include::rule-details/disable-windows-event-and-security-logs-using-built-in-too
 include::rule-details/disable-windows-firewall-rules-via-netsh.asciidoc[]
 include::rule-details/disabling-user-account-control-via-registry-modification.asciidoc[]
 include::rule-details/disabling-windows-defender-security-settings-via-powershell.asciidoc[]
+include::rule-details/discovery-of-domain-groups.asciidoc[]
+include::rule-details/discovery-of-internet-capabilities-via-built-in-tools.asciidoc[]
 include::rule-details/domain-added-to-google-workspace-trusted-domains.asciidoc[]
+include::rule-details/downloaded-shortcut-files.asciidoc[]
+include::rule-details/downloaded-url-files.asciidoc[]
 include::rule-details/dumping-account-hashes-via-built-in-commands.asciidoc[]
 include::rule-details/dumping-of-keychain-content-via-security-command.asciidoc[]
 include::rule-details/dynamic-linker-copy.asciidoc[]
+include::rule-details/ec2-ami-shared-with-another-account.asciidoc[]
+include::rule-details/esxi-discovery-via-find.asciidoc[]
+include::rule-details/esxi-discovery-via-grep.asciidoc[]
+include::rule-details/esxi-timestomping-using-touch-command.asciidoc[]
 include::rule-details/eggshell-backdoor-execution.asciidoc[]
 include::rule-details/elastic-agent-service-terminated.asciidoc[]
 include::rule-details/emond-rules-creation-or-modification.asciidoc[]
@@ -197,33 +231,72 @@ include::rule-details/enable-host-network-discovery-via-netsh.asciidoc[]
 include::rule-details/encoded-executable-stored-in-the-registry.asciidoc[]
 include::rule-details/encrypting-files-with-winrar-or-7z.asciidoc[]
 include::rule-details/endpoint-security.asciidoc[]
-include::rule-details/enumerating-domain-trusts-via-nltest.exe.asciidoc[]
+include::rule-details/enumerating-domain-trusts-via-dsquery-exe.asciidoc[]
+include::rule-details/enumerating-domain-trusts-via-nltest-exe.asciidoc[]
 include::rule-details/enumeration-command-spawned-via-wmiprvse.asciidoc[]
 include::rule-details/enumeration-of-administrator-accounts.asciidoc[]
 include::rule-details/enumeration-of-kernel-modules.asciidoc[]
+include::rule-details/enumeration-of-kernel-modules-via-proc.asciidoc[]
 include::rule-details/enumeration-of-privileged-local-groups-membership.asciidoc[]
 include::rule-details/enumeration-of-users-or-groups-via-built-in-commands.asciidoc[]
+include::rule-details/exchange-mailbox-export-via-powershell.asciidoc[]
 include::rule-details/executable-file-creation-with-multiple-extensions.asciidoc[]
+include::rule-details/executable-file-with-unusual-extension.asciidoc[]
+include::rule-details/executable-masquerading-as-kernel-process.asciidoc[]
 include::rule-details/execution-from-unusual-directory-command-line.asciidoc[]
+include::rule-details/execution-from-a-removable-media-with-network-connection.asciidoc[]
 include::rule-details/execution-of-com-object-via-xwizard.asciidoc[]
 include::rule-details/execution-of-file-written-or-modified-by-microsoft-office.asciidoc[]
 include::rule-details/execution-of-file-written-or-modified-by-pdf-reader.asciidoc[]
 include::rule-details/execution-of-persistent-suspicious-program.asciidoc[]
-include::rule-details/execution-via-electron-child-process-node.js-module.asciidoc[]
-include::rule-details/execution-via-mssql-xp_cmdshell-stored-procedure.asciidoc[]
+include::rule-details/execution-of-an-unsigned-service.asciidoc[]
+include::rule-details/execution-via-electron-child-process-node-js-module.asciidoc[]
+include::rule-details/execution-via-ms-visualstudio-pre-post-build-events.asciidoc[]
+include::rule-details/execution-via-mssql-xp-cmdshell-stored-procedure.asciidoc[]
+include::rule-details/execution-via-microsoft-dotnet-clickonce-host.asciidoc[]
 include::rule-details/execution-via-tsclient-mountpoint.asciidoc[]
+include::rule-details/execution-via-windows-subsystem-for-linux.asciidoc[]
 include::rule-details/execution-via-local-sxs-shared-module.asciidoc[]
 include::rule-details/execution-with-explicit-credentials-via-scripting.asciidoc[]
+include::rule-details/expired-or-revoked-driver-loaded.asciidoc[]
 include::rule-details/exploit-detected-elastic-endgame.asciidoc[]
 include::rule-details/exploit-prevented-elastic-endgame.asciidoc[]
 include::rule-details/exporting-exchange-mailbox-via-powershell.asciidoc[]
 include::rule-details/external-alerts.asciidoc[]
 include::rule-details/external-ip-lookup-from-non-browser-process.asciidoc[]
+include::rule-details/external-user-added-to-google-workspace-group.asciidoc[]
+include::rule-details/file-compressed-or-archived-into-common-format.asciidoc[]
+include::rule-details/file-creation-time-changed.asciidoc[]
+include::rule-details/file-creation-execution-and-self-deletion-in-suspicious-directory.asciidoc[]
 include::rule-details/file-deletion-via-shred.asciidoc[]
+include::rule-details/file-made-executable-via-chmod-inside-a-container.asciidoc[]
 include::rule-details/file-permission-modification-in-writable-directory.asciidoc[]
+include::rule-details/file-staged-in-root-folder-of-recycle-bin.asciidoc[]
+include::rule-details/file-system-debugger-launched-inside-a-privileged-container.asciidoc[]
 include::rule-details/file-transfer-or-listener-established-via-netcat.asciidoc[]
+include::rule-details/file-and-directory-permissions-modification.asciidoc[]
 include::rule-details/file-made-immutable-by-chattr.asciidoc[]
+include::rule-details/file-or-directory-deletion-command.asciidoc[]
+include::rule-details/file-with-suspicious-extension-downloaded.asciidoc[]
 include::rule-details/finder-sync-plugin-registered-and-enabled.asciidoc[]
+include::rule-details/first-occurrence-github-event-for-a-personal-access-token-pat.asciidoc[]
+include::rule-details/first-occurrence-of-github-repo-interaction-from-a-new-ip.asciidoc[]
+include::rule-details/first-occurrence-of-github-user-interaction-with-private-repo.asciidoc[]
+include::rule-details/first-occurrence-of-ip-address-for-github-personal-access-token-pat.asciidoc[]
+include::rule-details/first-occurrence-of-ip-address-for-github-user.asciidoc[]
+include::rule-details/first-occurrence-of-okta-user-session-started-via-proxy.asciidoc[]
+include::rule-details/first-occurrence-of-personal-access-token-pat-use-for-a-github-user.asciidoc[]
+include::rule-details/first-occurrence-of-private-repo-event-from-specific-github-personal-access-token-pat.asciidoc[]
+include::rule-details/first-occurrence-of-user-agent-for-a-github-personal-access-token-pat.asciidoc[]
+include::rule-details/first-occurrence-of-user-agent-for-a-github-user.asciidoc[]
+include::rule-details/first-time-seen-aws-secret-value-accessed-in-secrets-manager.asciidoc[]
+include::rule-details/first-time-seen-commonly-abused-remote-access-tool-execution.asciidoc[]
+include::rule-details/first-time-seen-driver-loaded.asciidoc[]
+include::rule-details/first-time-seen-google-workspace-oauth-login-from-third-party-application.asciidoc[]
+include::rule-details/first-time-seen-newcredentials-logon-process.asciidoc[]
+include::rule-details/first-time-seen-removable-device.asciidoc[]
+include::rule-details/firsttime-seen-account-performing-dcsync.asciidoc[]
+include::rule-details/forwarded-google-workspace-security-alert.asciidoc[]
 include::rule-details/full-user-mode-dumps-enabled-system-wide.asciidoc[]
 include::rule-details/gcp-firewall-rule-creation.asciidoc[]
 include::rule-details/gcp-firewall-rule-deletion.asciidoc[]
@@ -248,6 +321,14 @@ include::rule-details/gcp-storage-bucket-permissions-modification.asciidoc[]
 include::rule-details/gcp-virtual-private-cloud-network-deletion.asciidoc[]
 include::rule-details/gcp-virtual-private-cloud-route-creation.asciidoc[]
 include::rule-details/gcp-virtual-private-cloud-route-deletion.asciidoc[]
+include::rule-details/github-app-deleted.asciidoc[]
+include::rule-details/github-owner-role-granted-to-user.asciidoc[]
+include::rule-details/github-pat-access-revoked.asciidoc[]
+include::rule-details/github-protected-branch-settings-changed.asciidoc[]
+include::rule-details/github-repo-created.asciidoc[]
+include::rule-details/github-repository-deleted.asciidoc[]
+include::rule-details/github-ueba-multiple-alerts-from-a-github-account.asciidoc[]
+include::rule-details/github-user-blocked-from-organization.asciidoc[]
 include::rule-details/google-drive-ownership-transferred-via-google-workspace.asciidoc[]
 include::rule-details/google-workspace-2sv-policy-disabled.asciidoc[]
 include::rule-details/google-workspace-api-access-granted-via-domain-wide-delegation-of-authority.asciidoc[]
@@ -256,22 +337,32 @@ include::rule-details/google-workspace-admin-role-deletion.asciidoc[]
 include::rule-details/google-workspace-bitlocker-setting-disabled.asciidoc[]
 include::rule-details/google-workspace-custom-admin-role-created.asciidoc[]
 include::rule-details/google-workspace-custom-gmail-route-created-or-modified.asciidoc[]
+include::rule-details/google-workspace-drive-encryption-key-s-accessed-from-anonymous-user.asciidoc[]
 include::rule-details/google-workspace-mfa-enforcement-disabled.asciidoc[]
+include::rule-details/google-workspace-object-copied-from-external-drive-and-access-granted-to-custom-application.asciidoc[]
 include::rule-details/google-workspace-password-policy-modified.asciidoc[]
 include::rule-details/google-workspace-restrictions-for-google-marketplace-modified-to-allow-any-app.asciidoc[]
 include::rule-details/google-workspace-role-modified.asciidoc[]
-include::rule-details/google-workspace-user-group-access-modified-to-allow-external-access.asciidoc[]
+include::rule-details/google-workspace-suspended-user-account-renewed.asciidoc[]
 include::rule-details/google-workspace-user-organizational-unit-changed.asciidoc[]
 include::rule-details/group-policy-abuse-for-privilege-addition.asciidoc[]
+include::rule-details/group-policy-discovery-via-microsoft-gpresult-utility.asciidoc[]
 include::rule-details/halfbaked-command-and-control-beacon.asciidoc[]
+include::rule-details/hidden-files-and-directories-via-hidden-flag.asciidoc[]
+include::rule-details/high-mean-of-process-arguments-in-an-rdp-session.asciidoc[]
+include::rule-details/high-mean-of-rdp-session-duration.asciidoc[]
+include::rule-details/high-number-of-cloned-github-repos-from-pat.asciidoc[]
 include::rule-details/high-number-of-okta-user-password-reset-or-unlock-attempts.asciidoc[]
 include::rule-details/high-number-of-process-terminations.asciidoc[]
 include::rule-details/high-number-of-process-and-or-service-terminations.asciidoc[]
+include::rule-details/high-variance-in-rdp-session-duration.asciidoc[]
+include::rule-details/host-files-system-changes-via-windows-subsystem-for-linux.asciidoc[]
 include::rule-details/hosts-file-modified.asciidoc[]
 include::rule-details/hping-process-activity.asciidoc[]
 include::rule-details/iis-http-logging-disabled.asciidoc[]
 include::rule-details/ipsec-nat-traversal-port-activity.asciidoc[]
 include::rule-details/image-file-execution-options-injection.asciidoc[]
+include::rule-details/image-loaded-with-invalid-signature.asciidoc[]
 include::rule-details/imageload-via-windows-update-auto-update-client.asciidoc[]
 include::rule-details/inbound-connection-to-an-unsecure-elasticsearch-node.asciidoc[]
 include::rule-details/incoming-dcom-lateral-movement-via-mshta.asciidoc[]
@@ -279,18 +370,27 @@ include::rule-details/incoming-dcom-lateral-movement-with-mmc.asciidoc[]
 include::rule-details/incoming-dcom-lateral-movement-with-shellbrowserwindow-or-shellwindows.asciidoc[]
 include::rule-details/incoming-execution-via-powershell-remoting.asciidoc[]
 include::rule-details/incoming-execution-via-winrm-remote-shell.asciidoc[]
+include::rule-details/indirect-command-execution-via-forfiles-pcalua.asciidoc[]
+include::rule-details/ingress-transfer-via-windows-bits.asciidoc[]
+include::rule-details/installutil-activity.asciidoc[]
 include::rule-details/installutil-process-making-network-connections.asciidoc[]
 include::rule-details/installation-of-custom-shim-databases.asciidoc[]
 include::rule-details/installation-of-security-support-provider.asciidoc[]
+include::rule-details/interactive-exec-command-launched-against-a-running-container.asciidoc[]
+include::rule-details/interactive-logon-by-an-unusual-process.asciidoc[]
 include::rule-details/interactive-terminal-spawned-via-perl.asciidoc[]
 include::rule-details/interactive-terminal-spawned-via-python.asciidoc[]
 include::rule-details/krbtgt-delegation-backdoor.asciidoc[]
 include::rule-details/kerberos-cached-credentials-dumping.asciidoc[]
 include::rule-details/kerberos-pre-authentication-disabled-for-user.asciidoc[]
 include::rule-details/kerberos-traffic-from-unusual-process.asciidoc[]
-include::rule-details/kernel-module-removal.asciidoc[]
+include::rule-details/kernel-driver-load.asciidoc[]
+include::rule-details/kernel-driver-load-by-non-root-user.asciidoc[]
+include::rule-details/kernel-load-or-unload-via-kexec-detected.asciidoc[]
 include::rule-details/kernel-module-load-via-insmod.asciidoc[]
+include::rule-details/kernel-module-removal.asciidoc[]
 include::rule-details/keychain-password-retrieval-via-command-line.asciidoc[]
+include::rule-details/kirbi-file-creation.asciidoc[]
 include::rule-details/kubernetes-anonymous-request-authorized.asciidoc[]
 include::rule-details/kubernetes-container-created-with-excessive-linux-capabilities.asciidoc[]
 include::rule-details/kubernetes-denied-service-account-request.asciidoc[]
@@ -305,18 +405,33 @@ include::rule-details/kubernetes-suspicious-self-subject-review.asciidoc[]
 include::rule-details/kubernetes-user-exec-into-pod.asciidoc[]
 include::rule-details/lsass-memory-dump-creation.asciidoc[]
 include::rule-details/lsass-memory-dump-handle-access.asciidoc[]
+include::rule-details/lsass-process-access-via-windows-api.asciidoc[]
 include::rule-details/lateral-movement-via-startup-folder.asciidoc[]
 include::rule-details/launch-agent-creation-or-modification-and-immediate-loading.asciidoc[]
 include::rule-details/launchdaemon-creation-or-modification-and-immediate-loading.asciidoc[]
-include::rule-details/linux-restricted-shell-breakout-via-linux-binarys.asciidoc[]
+include::rule-details/linux-group-creation.asciidoc[]
+include::rule-details/linux-process-hooking-via-gdb.asciidoc[]
+include::rule-details/linux-restricted-shell-breakout-via-linux-binary-s.asciidoc[]
+include::rule-details/linux-system-information-discovery.asciidoc[]
+include::rule-details/linux-user-account-creation.asciidoc[]
+include::rule-details/linux-user-added-to-privileged-group.asciidoc[]
+include::rule-details/linux-init-pid-1-secret-dump-via-gdb.asciidoc[]
 include::rule-details/local-account-tokenfilter-policy-disabled.asciidoc[]
 include::rule-details/local-scheduled-task-creation.asciidoc[]
+include::rule-details/mfa-deactivation-with-no-re-activation-for-okta-user-account.asciidoc[]
 include::rule-details/mfa-disabled-for-google-workspace-organization.asciidoc[]
 include::rule-details/ms-office-macro-security-registry-modifications.asciidoc[]
 include::rule-details/macos-installer-package-spawns-network-event.asciidoc[]
+include::rule-details/machine-learning-detected-dga-activity-using-a-known-sunburst-dns-domain.asciidoc[]
+include::rule-details/machine-learning-detected-a-dns-request-predicted-to-be-a-dga-domain.asciidoc[]
+include::rule-details/machine-learning-detected-a-dns-request-with-a-high-dga-probability-score.asciidoc[]
+include::rule-details/machine-learning-detected-a-suspicious-windows-event-predicted-to-be-malicious-activity.asciidoc[]
+include::rule-details/machine-learning-detected-a-suspicious-windows-event-with-a-high-malicious-probability-score.asciidoc[]
 include::rule-details/malware-detected-elastic-endgame.asciidoc[]
 include::rule-details/malware-prevented-elastic-endgame.asciidoc[]
 include::rule-details/masquerading-space-after-filename.asciidoc[]
+include::rule-details/member-removed-from-github-organization.asciidoc[]
+include::rule-details/memory-dump-file-with-unusual-extension.asciidoc[]
 include::rule-details/microsoft-365-exchange-anti-phish-policy-deletion.asciidoc[]
 include::rule-details/microsoft-365-exchange-anti-phish-rule-modification.asciidoc[]
 include::rule-details/microsoft-365-exchange-dkim-signing-configuration-disabled.asciidoc[]
@@ -329,7 +444,9 @@ include::rule-details/microsoft-365-exchange-safe-link-policy-disabled.asciidoc[
 include::rule-details/microsoft-365-exchange-transport-rule-creation.asciidoc[]
 include::rule-details/microsoft-365-exchange-transport-rule-modification.asciidoc[]
 include::rule-details/microsoft-365-global-administrator-role-assigned.asciidoc[]
+include::rule-details/microsoft-365-impossible-travel-activity.asciidoc[]
 include::rule-details/microsoft-365-inbox-forwarding-rule-created.asciidoc[]
+include::rule-details/microsoft-365-mass-download-by-a-single-user.asciidoc[]
 include::rule-details/microsoft-365-potential-ransomware-activity.asciidoc[]
 include::rule-details/microsoft-365-teams-custom-application-interaction-allowed.asciidoc[]
 include::rule-details/microsoft-365-teams-external-access-enabled.asciidoc[]
@@ -343,6 +460,7 @@ include::rule-details/microsoft-build-engine-started-by-an-office-application.as
 include::rule-details/microsoft-build-engine-using-an-alternate-name.asciidoc[]
 include::rule-details/microsoft-exchange-server-um-spawning-suspicious-processes.asciidoc[]
 include::rule-details/microsoft-exchange-server-um-writing-suspicious-files.asciidoc[]
+include::rule-details/microsoft-exchange-transport-agent-install-script.asciidoc[]
 include::rule-details/microsoft-exchange-worker-spawning-suspicious-processes.asciidoc[]
 include::rule-details/microsoft-iis-connection-strings-decryption.asciidoc[]
 include::rule-details/microsoft-iis-service-account-password-dumped.asciidoc[]
@@ -351,32 +469,55 @@ include::rule-details/mimikatz-memssp-log-file-detected.asciidoc[]
 include::rule-details/modification-of-amsienable-registry-key.asciidoc[]
 include::rule-details/modification-of-boot-configuration.asciidoc[]
 include::rule-details/modification-of-dynamic-linker-preload-shared-object.asciidoc[]
-include::rule-details/modification-of-environment-variable-via-launchctl.asciidoc[]
+include::rule-details/modification-of-dynamic-linker-preload-shared-object-inside-a-container.asciidoc[]
+include::rule-details/modification-of-environment-variable-via-unsigned-or-untrusted-parent.asciidoc[]
 include::rule-details/modification-of-openssh-binaries.asciidoc[]
 include::rule-details/modification-of-safari-settings-via-defaults-command.asciidoc[]
 include::rule-details/modification-of-standard-authentication-module-or-configuration.asciidoc[]
 include::rule-details/modification-of-wdigest-security-provider.asciidoc[]
 include::rule-details/modification-of-the-mspkiaccountcredentials.asciidoc[]
 include::rule-details/modification-or-removal-of-an-okta-application-sign-on-policy.asciidoc[]
+include::rule-details/mofcomp-activity.asciidoc[]
+include::rule-details/mount-launched-inside-a-privileged-container.asciidoc[]
 include::rule-details/mounting-hidden-or-webdav-remote-shares.asciidoc[]
 include::rule-details/msbuild-making-network-connections.asciidoc[]
 include::rule-details/mshta-making-network-connections.asciidoc[]
 include::rule-details/multi-factor-authentication-disabled-for-an-azure-user.asciidoc[]
+include::rule-details/multiple-alerts-involving-a-user.asciidoc[]
 include::rule-details/multiple-alerts-in-different-att-ck-tactics-on-a-single-host.asciidoc[]
 include::rule-details/multiple-logon-failure-followed-by-logon-success.asciidoc[]
 include::rule-details/multiple-logon-failure-from-the-same-source-address.asciidoc[]
+include::rule-details/multiple-okta-client-addresses-for-a-single-user-session.asciidoc[]
+include::rule-details/multiple-okta-sessions-detected-for-a-single-user.asciidoc[]
+include::rule-details/multiple-okta-user-auth-events-with-same-device-token-hash-behind-a-proxy.asciidoc[]
 include::rule-details/multiple-vault-web-credentials-read.asciidoc[]
-include::rule-details/my-first-alert.asciidoc[]
+include::rule-details/my-first-rule.asciidoc[]
 include::rule-details/ntds-or-sam-database-file-copied.asciidoc[]
 include::rule-details/namespace-manipulation-using-unshare.asciidoc[]
+include::rule-details/netcat-listener-established-inside-a-container.asciidoc[]
+include::rule-details/netcat-listener-established-via-rlwrap.asciidoc[]
+include::rule-details/netsh-helper-dll.asciidoc[]
+include::rule-details/network-activity-detected-via-kworker.asciidoc[]
+include::rule-details/network-activity-detected-via-cat.asciidoc[]
+include::rule-details/network-connection-from-binary-with-rwx-memory-region.asciidoc[]
 include::rule-details/network-connection-via-certutil.asciidoc[]
 include::rule-details/network-connection-via-compiled-html-file.asciidoc[]
 include::rule-details/network-connection-via-msxsl.asciidoc[]
+include::rule-details/network-connection-via-recently-compiled-executable.asciidoc[]
 include::rule-details/network-connection-via-registration-utility.asciidoc[]
 include::rule-details/network-connection-via-signed-binary.asciidoc[]
 include::rule-details/network-logon-provider-registry-modification.asciidoc[]
+include::rule-details/network-traffic-capture-via-cap-net-raw.asciidoc[]
 include::rule-details/network-traffic-to-rare-destination-country.asciidoc[]
+include::rule-details/network-level-authentication-nla-disabled.asciidoc[]
 include::rule-details/new-activesyncalloweddeviceid-added-via-powershell.asciidoc[]
+include::rule-details/new-github-app-installed.asciidoc[]
+include::rule-details/new-github-owner-added.asciidoc[]
+include::rule-details/new-okta-authentication-behavior-detected.asciidoc[]
+include::rule-details/new-okta-identity-provider-idp-added-by-admin.asciidoc[]
+include::rule-details/new-systemd-service-created-by-previously-unknown-process.asciidoc[]
+include::rule-details/new-systemd-timer-created.asciidoc[]
+include::rule-details/new-user-added-to-github-organization.asciidoc[]
 include::rule-details/new-or-modified-federation-domain.asciidoc[]
 include::rule-details/nping-process-activity.asciidoc[]
 include::rule-details/nullsessionpipe-registry-modification.asciidoc[]
@@ -384,8 +525,13 @@ include::rule-details/o365-email-reported-by-user-as-malware-or-phish.asciidoc[]
 include::rule-details/o365-excessive-single-sign-on-logon-errors.asciidoc[]
 include::rule-details/o365-exchange-suspicious-mailbox-right-delegation.asciidoc[]
 include::rule-details/o365-mailbox-audit-logging-bypass.asciidoc[]
+include::rule-details/office-test-registry-persistence.asciidoc[]
 include::rule-details/okta-brute-force-or-password-spraying-attack.asciidoc[]
+include::rule-details/okta-fastpass-phishing-detection.asciidoc[]
+include::rule-details/okta-sign-in-events-via-third-party-idp.asciidoc[]
+include::rule-details/okta-threatinsight-threat-suspected-promotion.asciidoc[]
 include::rule-details/okta-user-session-impersonation.asciidoc[]
+include::rule-details/okta-user-sessions-started-from-different-geolocations.asciidoc[]
 include::rule-details/onedrive-malware-file-upload.asciidoc[]
 include::rule-details/outbound-scheduled-task-activity-via-powershell.asciidoc[]
 include::rule-details/parent-process-pid-spoofing.asciidoc[]
@@ -412,24 +558,49 @@ include::rule-details/port-forwarding-rule-addition.asciidoc[]
 include::rule-details/possible-consent-grant-attack-via-azure-registered-application.asciidoc[]
 include::rule-details/possible-fin7-dga-command-and-control-behavior.asciidoc[]
 include::rule-details/possible-okta-dos-attack.asciidoc[]
-include::rule-details/potential-abuse-of-repeated-mfa-push-notifications.asciidoc[]
+include::rule-details/potential-adidns-poisoning-via-wildcard-record-creation.asciidoc[]
+include::rule-details/potential-abuse-of-resources-by-high-token-count-and-large-response-sizes.asciidoc[]
 include::rule-details/potential-admin-group-account-addition.asciidoc[]
+include::rule-details/potential-antimalware-scan-interface-bypass-via-powershell.asciidoc[]
 include::rule-details/potential-application-shimming-via-sdbinst.asciidoc[]
+include::rule-details/potential-buffer-overflow-attack-detected.asciidoc[]
+include::rule-details/potential-chroot-container-escape-via-mount.asciidoc[]
+include::rule-details/potential-code-execution-via-postgresql.asciidoc[]
 include::rule-details/potential-command-and-control-via-internet-explorer.asciidoc[]
+include::rule-details/potential-container-escape-via-modified-notify-on-release-file.asciidoc[]
+include::rule-details/potential-container-escape-via-modified-release-agent-file.asciidoc[]
 include::rule-details/potential-cookies-theft-via-browser-debugging.asciidoc[]
 include::rule-details/potential-credential-access-via-dcsync.asciidoc[]
 include::rule-details/potential-credential-access-via-duplicatehandle-in-lsass.asciidoc[]
 include::rule-details/potential-credential-access-via-lsass-memory-dump.asciidoc[]
+include::rule-details/potential-credential-access-via-memory-dump-file-creation.asciidoc[]
 include::rule-details/potential-credential-access-via-renamed-com-services-dll.asciidoc[]
 include::rule-details/potential-credential-access-via-trusted-developer-utility.asciidoc[]
 include::rule-details/potential-credential-access-via-windows-utilities.asciidoc[]
+include::rule-details/potential-cross-site-scripting-xss.asciidoc[]
+include::rule-details/potential-dga-activity.asciidoc[]
 include::rule-details/potential-dll-side-loading-via-microsoft-antimalware-service-executable.asciidoc[]
-include::rule-details/potential-dll-sideloading-via-trusted-microsoft-programs.asciidoc[]
-include::rule-details/potential-dns-tunneling-via-iodine.asciidoc[]
+include::rule-details/potential-dll-side-loading-via-trusted-microsoft-programs.asciidoc[]
 include::rule-details/potential-dns-tunneling-via-nslookup.asciidoc[]
+include::rule-details/potential-data-exfiltration-activity-to-an-unusual-destination-port.asciidoc[]
+include::rule-details/potential-data-exfiltration-activity-to-an-unusual-ip-address.asciidoc[]
+include::rule-details/potential-data-exfiltration-activity-to-an-unusual-iso-code.asciidoc[]
+include::rule-details/potential-data-exfiltration-activity-to-an-unusual-region.asciidoc[]
+include::rule-details/potential-defense-evasion-via-cmstp-exe.asciidoc[]
+include::rule-details/potential-defense-evasion-via-proot.asciidoc[]
+include::rule-details/potential-disabling-of-apparmor.asciidoc[]
 include::rule-details/potential-disabling-of-selinux.asciidoc[]
+include::rule-details/potential-enumeration-via-active-directory-web-service.asciidoc[]
 include::rule-details/potential-evasion-via-filter-manager.asciidoc[]
+include::rule-details/potential-evasion-via-windows-filtering-platform.asciidoc[]
+include::rule-details/potential-execution-via-xzbackdoor.asciidoc[]
+include::rule-details/potential-exploitation-of-an-unquoted-service-path-vulnerability.asciidoc[]
+include::rule-details/potential-external-linux-ssh-brute-force-detected.asciidoc[]
+include::rule-details/potential-file-download-via-a-headless-browser.asciidoc[]
+include::rule-details/potential-file-transfer-via-certreq.asciidoc[]
 include::rule-details/potential-hidden-local-user-account-creation.asciidoc[]
+include::rule-details/potential-hidden-process-via-mount-hidepid.asciidoc[]
+include::rule-details/potential-internal-linux-ssh-brute-force-detected.asciidoc[]
 include::rule-details/potential-invoke-mimikatz-powershell-script.asciidoc[]
 include::rule-details/potential-java-jndi-exploitation-attempt.asciidoc[]
 include::rule-details/potential-kerberos-attack-via-bifrost.asciidoc[]
@@ -437,51 +608,137 @@ include::rule-details/potential-lsa-authentication-package-abuse.asciidoc[]
 include::rule-details/potential-lsass-clone-creation-via-psscapturesnapshot.asciidoc[]
 include::rule-details/potential-lsass-memory-dump-via-psscapturesnapshot.asciidoc[]
 include::rule-details/potential-lateral-tool-transfer-via-smb-share.asciidoc[]
-include::rule-details/potential-linux-ssh-brute-force-detected.asciidoc[]
+include::rule-details/potential-linux-backdoor-user-account-creation.asciidoc[]
+include::rule-details/potential-linux-credential-dumping-via-proc-filesystem.asciidoc[]
+include::rule-details/potential-linux-credential-dumping-via-unshadow.asciidoc[]
+include::rule-details/potential-linux-hack-tool-launched.asciidoc[]
+include::rule-details/potential-linux-local-account-brute-force-detected.asciidoc[]
+include::rule-details/potential-linux-ransomware-note-creation-detected.asciidoc[]
+include::rule-details/potential-linux-ssh-x11-forwarding.asciidoc[]
+include::rule-details/potential-linux-tunneling-and-or-port-forwarding.asciidoc[]
 include::rule-details/potential-local-ntlm-relay-via-http.asciidoc[]
+include::rule-details/potential-masquerading-as-browser-process.asciidoc[]
+include::rule-details/potential-masquerading-as-business-app-installer.asciidoc[]
+include::rule-details/potential-masquerading-as-communication-apps.asciidoc[]
+include::rule-details/potential-masquerading-as-system32-dll.asciidoc[]
+include::rule-details/potential-masquerading-as-system32-executable.asciidoc[]
+include::rule-details/potential-masquerading-as-vlc-dll.asciidoc[]
+include::rule-details/potential-memory-seeking-activity.asciidoc[]
+include::rule-details/potential-meterpreter-reverse-shell.asciidoc[]
 include::rule-details/potential-microsoft-office-sandbox-evasion.asciidoc[]
 include::rule-details/potential-modification-of-accessibility-binaries.asciidoc[]
+include::rule-details/potential-network-scan-detected.asciidoc[]
+include::rule-details/potential-network-scan-executed-from-host.asciidoc[]
+include::rule-details/potential-network-share-discovery.asciidoc[]
+include::rule-details/potential-network-sweep-detected.asciidoc[]
+include::rule-details/potential-non-standard-port-http-https-connection.asciidoc[]
 include::rule-details/potential-non-standard-port-ssh-connection.asciidoc[]
+include::rule-details/potential-okta-mfa-bombing-via-push-notifications.asciidoc[]
 include::rule-details/potential-openssh-backdoor-logging-activity.asciidoc[]
+include::rule-details/potential-outgoing-rdp-connection-by-unusual-process.asciidoc[]
+include::rule-details/potential-pass-the-hash-pth-attempt.asciidoc[]
 include::rule-details/potential-password-spraying-of-microsoft-365-user-accounts.asciidoc[]
+include::rule-details/potential-persistence-through-motd-file-creation-detected.asciidoc[]
+include::rule-details/potential-persistence-through-run-control-detected.asciidoc[]
+include::rule-details/potential-persistence-through-systemd-udevd.asciidoc[]
+include::rule-details/potential-persistence-through-init-d-detected.asciidoc[]
 include::rule-details/potential-persistence-via-atom-init-script-modification.asciidoc[]
 include::rule-details/potential-persistence-via-login-hook.asciidoc[]
 include::rule-details/potential-persistence-via-periodic-tasks.asciidoc[]
 include::rule-details/potential-persistence-via-time-provider-modification.asciidoc[]
 include::rule-details/potential-port-monitor-or-print-processor-registration-abuse.asciidoc[]
+include::rule-details/potential-powershell-hacktool-script-by-author.asciidoc[]
+include::rule-details/potential-powershell-hacktool-script-by-function-names.asciidoc[]
+include::rule-details/potential-powershell-pass-the-hash-relay-script.asciidoc[]
 include::rule-details/potential-privacy-control-bypass-via-localhost-secure-copy.asciidoc[]
 include::rule-details/potential-privacy-control-bypass-via-tccdb-modification.asciidoc[]
+include::rule-details/potential-privilege-escalation-through-writable-docker-socket.asciidoc[]
+include::rule-details/potential-privilege-escalation-via-cve-2023-4911.asciidoc[]
+include::rule-details/potential-privilege-escalation-via-container-misconfiguration.asciidoc[]
+include::rule-details/potential-privilege-escalation-via-enlightenment.asciidoc[]
 include::rule-details/potential-privilege-escalation-via-installerfiletakeover.asciidoc[]
+include::rule-details/potential-privilege-escalation-via-linux-dac-permissions.asciidoc[]
+include::rule-details/potential-privilege-escalation-via-overlayfs.asciidoc[]
 include::rule-details/potential-privilege-escalation-via-pkexec.asciidoc[]
+include::rule-details/potential-privilege-escalation-via-python-cap-setuid.asciidoc[]
+include::rule-details/potential-privilege-escalation-via-recently-compiled-executable.asciidoc[]
 include::rule-details/potential-privilege-escalation-via-sudoers-file-modification.asciidoc[]
+include::rule-details/potential-privilege-escalation-via-uid-int-max-bug-detected.asciidoc[]
 include::rule-details/potential-privileged-escalation-via-samaccountname-spoofing.asciidoc[]
-include::rule-details/potential-process-herpaderping-attempt.asciidoc[]
+include::rule-details/potential-process-injection-from-malicious-document.asciidoc[]
 include::rule-details/potential-process-injection-via-powershell.asciidoc[]
+include::rule-details/potential-protocol-tunneling-via-chisel-client.asciidoc[]
+include::rule-details/potential-protocol-tunneling-via-chisel-server.asciidoc[]
 include::rule-details/potential-protocol-tunneling-via-earthworm.asciidoc[]
+include::rule-details/potential-pspy-process-monitoring-detected.asciidoc[]
+include::rule-details/potential-ransomware-behavior-high-count-of-readme-files-by-system.asciidoc[]
+include::rule-details/potential-ransomware-note-file-dropped-via-smb.asciidoc[]
+include::rule-details/potential-remote-code-execution-via-web-server.asciidoc[]
 include::rule-details/potential-remote-credential-access-via-registry.asciidoc[]
 include::rule-details/potential-remote-desktop-shadowing-activity.asciidoc[]
 include::rule-details/potential-remote-desktop-tunneling-detected.asciidoc[]
+include::rule-details/potential-remote-file-execution-via-msiexec.asciidoc[]
+include::rule-details/potential-reverse-shell.asciidoc[]
 include::rule-details/potential-reverse-shell-activity-via-terminal.asciidoc[]
-include::rule-details/potential-ssh-brute-force-detected-on-privileged-account.asciidoc[]
-include::rule-details/potential-ssh-password-guessing.asciidoc[]
+include::rule-details/potential-reverse-shell-via-background-process.asciidoc[]
+include::rule-details/potential-reverse-shell-via-child.asciidoc[]
+include::rule-details/potential-reverse-shell-via-java.asciidoc[]
+include::rule-details/potential-reverse-shell-via-suspicious-binary.asciidoc[]
+include::rule-details/potential-reverse-shell-via-suspicious-child-process.asciidoc[]
+include::rule-details/potential-reverse-shell-via-udp.asciidoc[]
+include::rule-details/potential-ssh-it-ssh-worm-downloaded.asciidoc[]
+include::rule-details/potential-syn-based-network-scan-detected.asciidoc[]
 include::rule-details/potential-secure-file-deletion-via-sdelete-utility.asciidoc[]
 include::rule-details/potential-shadow-credentials-added-to-ad-object.asciidoc[]
 include::rule-details/potential-shadow-file-read-via-command-line-utilities.asciidoc[]
 include::rule-details/potential-sharprdp-behavior.asciidoc[]
-include::rule-details/potential-shell-via-web-server.asciidoc[]
+include::rule-details/potential-shell-via-wildcard-injection-detected.asciidoc[]
+include::rule-details/potential-successful-linux-ftp-brute-force-attack-detected.asciidoc[]
+include::rule-details/potential-successful-linux-rdp-brute-force-attack-detected.asciidoc[]
+include::rule-details/potential-successful-ssh-brute-force-attack.asciidoc[]
+include::rule-details/potential-sudo-hijacking-detected.asciidoc[]
+include::rule-details/potential-sudo-privilege-escalation-via-cve-2019-14287.asciidoc[]
+include::rule-details/potential-sudo-token-manipulation-via-process-injection.asciidoc[]
+include::rule-details/potential-suspicious-clipboard-activity-detected.asciidoc[]
+include::rule-details/potential-suspicious-debugfs-root-device-access.asciidoc[]
+include::rule-details/potential-suspicious-file-edit.asciidoc[]
+include::rule-details/potential-unauthorized-access-via-wildcard-injection-detected.asciidoc[]
+include::rule-details/potential-upgrade-of-non-interactive-shell.asciidoc[]
+include::rule-details/potential-veeam-credential-access-command.asciidoc[]
+include::rule-details/potential-widespread-malware-infection-across-multiple-hosts.asciidoc[]
 include::rule-details/potential-windows-error-manager-masquerading.asciidoc[]
+include::rule-details/potential-windows-session-hijacking-via-ccmexec.asciidoc[]
+include::rule-details/potential-curl-cve-2023-38545-exploitation.asciidoc[]
 include::rule-details/potential-macos-ssh-brute-force-detected.asciidoc[]
+include::rule-details/potential-privilege-escalation-via-cve-2022-38028.asciidoc[]
+include::rule-details/potentially-successful-mfa-bombing-via-push-notifications.asciidoc[]
+include::rule-details/potentially-suspicious-process-started-via-tmux-or-screen.asciidoc[]
+include::rule-details/powershell-invoke-ninjacopy-script.asciidoc[]
+include::rule-details/powershell-kerberos-ticket-dump.asciidoc[]
 include::rule-details/powershell-kerberos-ticket-request.asciidoc[]
 include::rule-details/powershell-keylogging-script.asciidoc[]
+include::rule-details/powershell-mailbox-collection-script.asciidoc[]
 include::rule-details/powershell-minidump-script.asciidoc[]
 include::rule-details/powershell-psreflect-script.asciidoc[]
 include::rule-details/powershell-script-block-logging-disabled.asciidoc[]
+include::rule-details/powershell-script-with-archive-compression-capabilities.asciidoc[]
+include::rule-details/powershell-script-with-discovery-capabilities.asciidoc[]
+include::rule-details/powershell-script-with-encryption-decryption-capabilities.asciidoc[]
+include::rule-details/powershell-script-with-log-clear-capabilities.asciidoc[]
+include::rule-details/powershell-script-with-password-policy-discovery-capabilities.asciidoc[]
+include::rule-details/powershell-script-with-remote-execution-capabilities-via-winrm.asciidoc[]
 include::rule-details/powershell-script-with-token-impersonation-capabilities.asciidoc[]
+include::rule-details/powershell-script-with-veeam-credential-access-capabilities.asciidoc[]
+include::rule-details/powershell-script-with-webcam-video-capture-capabilities.asciidoc[]
 include::rule-details/powershell-share-enumeration-script.asciidoc[]
 include::rule-details/powershell-suspicious-discovery-related-windows-api-functions.asciidoc[]
 include::rule-details/powershell-suspicious-payload-encoded-and-compressed.asciidoc[]
 include::rule-details/powershell-suspicious-script-with-audio-capture-capabilities.asciidoc[]
+include::rule-details/powershell-suspicious-script-with-clipboard-retrieval-capabilities.asciidoc[]
 include::rule-details/powershell-suspicious-script-with-screenshot-capabilities.asciidoc[]
+include::rule-details/privilege-escalation-via-cap-chown-cap-fowner-capabilities.asciidoc[]
+include::rule-details/privilege-escalation-via-cap-setuid-setgid-capabilities.asciidoc[]
+include::rule-details/privilege-escalation-via-gdb-cap-sys-ptrace.asciidoc[]
 include::rule-details/privilege-escalation-via-named-pipe-impersonation.asciidoc[]
 include::rule-details/privilege-escalation-via-rogue-named-pipe-impersonation.asciidoc[]
 include::rule-details/privilege-escalation-via-root-crontab-file-modification.asciidoc[]
@@ -489,17 +746,26 @@ include::rule-details/privilege-escalation-via-windir-environment-variable.ascii
 include::rule-details/privileged-account-brute-force.asciidoc[]
 include::rule-details/privileges-elevation-via-parent-process-pid-spoofing.asciidoc[]
 include::rule-details/process-activity-via-compiled-html-file.asciidoc[]
+include::rule-details/process-capability-enumeration.asciidoc[]
+include::rule-details/process-created-with-a-duplicated-token.asciidoc[]
 include::rule-details/process-created-with-an-elevated-token.asciidoc[]
 include::rule-details/process-creation-via-secondary-logon.asciidoc[]
+include::rule-details/process-discovery-using-built-in-tools.asciidoc[]
+include::rule-details/process-discovery-via-built-in-applications.asciidoc[]
 include::rule-details/process-execution-from-an-unusual-directory.asciidoc[]
 include::rule-details/process-injection-detected-elastic-endgame.asciidoc[]
 include::rule-details/process-injection-prevented-elastic-endgame.asciidoc[]
 include::rule-details/process-injection-by-the-microsoft-build-engine.asciidoc[]
 include::rule-details/process-started-from-process-id-pid-file.asciidoc[]
 include::rule-details/process-termination-followed-by-deletion.asciidoc[]
+include::rule-details/processes-with-trailing-spaces.asciidoc[]
 include::rule-details/program-files-directory-masquerading.asciidoc[]
 include::rule-details/prompt-for-credentials-with-osascript.asciidoc[]
+include::rule-details/proxychains-activity.asciidoc[]
 include::rule-details/psexec-network-connection.asciidoc[]
+include::rule-details/python-script-execution-via-command-line.asciidoc[]
+include::rule-details/quarantine-attrib-removed-by-unsigned-or-untrusted-process.asciidoc[]
+include::rule-details/query-registry-using-built-in-tools.asciidoc[]
 include::rule-details/rdp-remote-desktop-protocol-from-the-internet.asciidoc[]
 include::rule-details/rdp-enabled-via-registry.asciidoc[]
 include::rule-details/rpc-remote-procedure-call-from-the-internet.asciidoc[]
@@ -507,6 +773,7 @@ include::rule-details/rpc-remote-procedure-call-to-the-internet.asciidoc[]
 include::rule-details/ransomware-detected-elastic-endgame.asciidoc[]
 include::rule-details/ransomware-prevented-elastic-endgame.asciidoc[]
 include::rule-details/rare-aws-error-code.asciidoc[]
+include::rule-details/rare-smb-connection-to-the-internet.asciidoc[]
 include::rule-details/rare-user-logon.asciidoc[]
 include::rule-details/registry-persistence-via-appcert-dll.asciidoc[]
 include::rule-details/registry-persistence-via-appinit-dll.asciidoc[]
@@ -519,83 +786,141 @@ include::rule-details/remote-file-download-via-desktopimgdownldr-utility.asciido
 include::rule-details/remote-file-download-via-mpcmdrun.asciidoc[]
 include::rule-details/remote-file-download-via-powershell.asciidoc[]
 include::rule-details/remote-file-download-via-script-interpreter.asciidoc[]
-include::rule-details/remote-logon-followed-by-scheduled-task-creation.asciidoc[]
 include::rule-details/remote-ssh-login-enabled-via-systemsetup-command.asciidoc[]
 include::rule-details/remote-scheduled-task-creation.asciidoc[]
+include::rule-details/remote-scheduled-task-creation-via-rpc.asciidoc[]
 include::rule-details/remote-system-discovery-commands.asciidoc[]
 include::rule-details/remote-windows-service-installed.asciidoc[]
+include::rule-details/remote-xsl-script-execution-via-com.asciidoc[]
 include::rule-details/remotely-started-services-via-rpc.asciidoc[]
 include::rule-details/renamed-autoit-scripts-interpreter.asciidoc[]
-include::rule-details/reverse-shell-created-via-named-pipe.asciidoc[]
+include::rule-details/renamed-utility-executed-with-short-program-name.asciidoc[]
+include::rule-details/root-network-connection-via-gdb-cap-sys-ptrace.asciidoc[]
 include::rule-details/roshal-archive-rar-or-powershell-file-downloaded-from-the-internet.asciidoc[]
+include::rule-details/route53-resolver-query-log-configuration-deleted.asciidoc[]
 include::rule-details/sip-provider-modification.asciidoc[]
 include::rule-details/smb-windows-file-sharing-activity-to-the-internet.asciidoc[]
 include::rule-details/smtp-on-port-26-tcp.asciidoc[]
 include::rule-details/ssh-authorized-keys-file-modification.asciidoc[]
+include::rule-details/ssh-authorized-keys-file-modified-inside-a-container.asciidoc[]
+include::rule-details/ssh-connection-established-inside-a-running-container.asciidoc[]
+include::rule-details/ssh-process-launched-from-inside-a-container.asciidoc[]
+include::rule-details/suid-sguid-enumeration-detected.asciidoc[]
 include::rule-details/sunburst-command-and-control-activity.asciidoc[]
 include::rule-details/scheduled-task-created-by-a-windows-script.asciidoc[]
 include::rule-details/scheduled-task-execution-at-scale-via-gpo.asciidoc[]
 include::rule-details/scheduled-tasks-at-command-enabled.asciidoc[]
+include::rule-details/screenconnect-server-spawning-suspicious-processes.asciidoc[]
 include::rule-details/screensaver-plist-file-modified-by-unexpected-process.asciidoc[]
 include::rule-details/sedebugprivilege-enabled-by-a-suspicious-process.asciidoc[]
 include::rule-details/searching-for-saved-credentials-via-vaultcmd.asciidoc[]
 include::rule-details/security-software-discovery-using-wmic.asciidoc[]
 include::rule-details/security-software-discovery-via-grep.asciidoc[]
+include::rule-details/segfault-detected.asciidoc[]
 include::rule-details/sensitive-files-compression.asciidoc[]
+include::rule-details/sensitive-files-compression-inside-a-container.asciidoc[]
+include::rule-details/sensitive-keys-or-passwords-searched-for-inside-a-container.asciidoc[]
 include::rule-details/sensitive-privilege-seenabledelegationprivilege-assigned-to-a-user.asciidoc[]
 include::rule-details/service-command-lateral-movement.asciidoc[]
 include::rule-details/service-control-spawned-via-script-interpreter.asciidoc[]
 include::rule-details/service-creation-via-local-kerberos-authentication.asciidoc[]
+include::rule-details/service-disabled-via-registry-modification.asciidoc[]
+include::rule-details/service-path-modification.asciidoc[]
+include::rule-details/service-path-modification-via-sc-exe.asciidoc[]
+include::rule-details/setcap-setuid-setgid-capability-set.asciidoc[]
 include::rule-details/setuid-setgid-bit-set-via-chmod.asciidoc[]
 include::rule-details/sharepoint-malware-file-upload.asciidoc[]
+include::rule-details/shared-object-created-or-changed-by-previously-unknown-process.asciidoc[]
+include::rule-details/shell-configuration-modification.asciidoc[]
 include::rule-details/shell-execution-via-apple-scripting.asciidoc[]
+include::rule-details/shortcut-file-written-or-modified-on-startup-folder.asciidoc[]
 include::rule-details/signed-proxy-execution-via-ms-work-folders.asciidoc[]
 include::rule-details/softwareupdate-preferences-modification.asciidoc[]
 include::rule-details/solarwinds-process-disabling-services-via-registry.asciidoc[]
 include::rule-details/spike-in-aws-error-messages.asciidoc[]
+include::rule-details/spike-in-bytes-sent-to-an-external-device.asciidoc[]
+include::rule-details/spike-in-bytes-sent-to-an-external-device-via-airdrop.asciidoc[]
 include::rule-details/spike-in-failed-logon-events.asciidoc[]
 include::rule-details/spike-in-firewall-denies.asciidoc[]
 include::rule-details/spike-in-logon-events.asciidoc[]
-include::rule-details/spike-in-logon-events-from-a-source-ip.asciidoc[]
 include::rule-details/spike-in-network-traffic.asciidoc[]
 include::rule-details/spike-in-network-traffic-to-a-country.asciidoc[]
+include::rule-details/spike-in-number-of-connections-made-from-a-source-ip.asciidoc[]
+include::rule-details/spike-in-number-of-connections-made-to-a-destination-ip.asciidoc[]
+include::rule-details/spike-in-number-of-processes-in-an-rdp-session.asciidoc[]
+include::rule-details/spike-in-remote-file-transfers.asciidoc[]
+include::rule-details/spike-in-successful-logon-events-from-a-source-ip.asciidoc[]
 include::rule-details/startup-folder-persistence-via-unsigned-process.asciidoc[]
 include::rule-details/startup-persistence-by-a-suspicious-process.asciidoc[]
 include::rule-details/startup-or-run-key-registry-modification.asciidoc[]
 include::rule-details/startup-logon-script-added-to-group-policy-object.asciidoc[]
+include::rule-details/statistical-model-detected-c2-beaconing-activity.asciidoc[]
+include::rule-details/statistical-model-detected-c2-beaconing-activity-with-high-confidence.asciidoc[]
+include::rule-details/stolen-credentials-used-to-login-to-okta-account-after-mfa-reset.asciidoc[]
 include::rule-details/sublime-plugin-or-application-script-modification.asciidoc[]
+include::rule-details/sudo-command-enumeration-detected.asciidoc[]
 include::rule-details/sudo-heap-based-buffer-overflow-attempt.asciidoc[]
 include::rule-details/sudoers-file-modification.asciidoc[]
-include::rule-details/suspicious-.net-code-compilation.asciidoc[]
-include::rule-details/suspicious-.net-reflection-via-powershell.asciidoc[]
+include::rule-details/suspicious-net-code-compilation.asciidoc[]
+include::rule-details/suspicious-net-reflection-via-powershell.asciidoc[]
+include::rule-details/suspicious-proc-maps-discovery.asciidoc[]
+include::rule-details/suspicious-apt-package-manager-execution.asciidoc[]
+include::rule-details/suspicious-apt-package-manager-network-connection.asciidoc[]
+include::rule-details/suspicious-access-to-ldap-attributes.asciidoc[]
 include::rule-details/suspicious-activity-reported-by-okta-user.asciidoc[]
+include::rule-details/suspicious-antimalware-scan-interface-dll.asciidoc[]
 include::rule-details/suspicious-automator-workflows-execution.asciidoc[]
 include::rule-details/suspicious-browser-child-process.asciidoc[]
 include::rule-details/suspicious-calendar-file-modification.asciidoc[]
 include::rule-details/suspicious-certutil-commands.asciidoc[]
 include::rule-details/suspicious-child-process-of-adobe-acrobat-reader-update-service.asciidoc[]
 include::rule-details/suspicious-cmd-execution-via-wmi.asciidoc[]
+include::rule-details/suspicious-communication-app-child-process.asciidoc[]
+include::rule-details/suspicious-content-extracted-or-decompressed-via-funzip.asciidoc[]
 include::rule-details/suspicious-crontab-creation-or-modification.asciidoc[]
 include::rule-details/suspicious-dll-loaded-for-persistence-or-privilege-escalation.asciidoc[]
+include::rule-details/suspicious-data-encryption-via-openssl-utility.asciidoc[]
+include::rule-details/suspicious-dynamic-linker-discovery-via-od.asciidoc[]
 include::rule-details/suspicious-emond-child-process.asciidoc[]
 include::rule-details/suspicious-endpoint-security-parent-process.asciidoc[]
-include::rule-details/suspicious-execution-short-program-name.asciidoc[]
+include::rule-details/suspicious-execution-from-inet-cache.asciidoc[]
 include::rule-details/suspicious-execution-from-a-mounted-device.asciidoc[]
+include::rule-details/suspicious-execution-via-msiexec.asciidoc[]
+include::rule-details/suspicious-execution-via-microsoft-office-add-ins.asciidoc[]
 include::rule-details/suspicious-execution-via-scheduled-task.asciidoc[]
+include::rule-details/suspicious-execution-via-windows-subsystem-for-linux.asciidoc[]
 include::rule-details/suspicious-explorer-child-process.asciidoc[]
+include::rule-details/suspicious-file-changes-activity-detected.asciidoc[]
 include::rule-details/suspicious-file-creation-in-etc-for-persistence.asciidoc[]
+include::rule-details/suspicious-file-creation-via-kworker.asciidoc[]
+include::rule-details/suspicious-file-downloaded-from-google-drive.asciidoc[]
+include::rule-details/suspicious-file-renamed-via-smb.asciidoc[]
 include::rule-details/suspicious-html-file-creation.asciidoc[]
 include::rule-details/suspicious-hidden-child-process-of-launchd.asciidoc[]
-include::rule-details/suspicious-image-load-taskschd.dll-from-ms-office.asciidoc[]
+include::rule-details/suspicious-image-load-taskschd-dll-from-ms-office.asciidoc[]
 include::rule-details/suspicious-imagepath-service-creation.asciidoc[]
+include::rule-details/suspicious-inter-process-communication-via-outlook.asciidoc[]
+include::rule-details/suspicious-interactive-shell-spawned-from-inside-a-container.asciidoc[]
 include::rule-details/suspicious-java-child-process.asciidoc[]
+include::rule-details/suspicious-jetbrains-teamcity-child-process.asciidoc[]
+include::rule-details/suspicious-kworker-uid-elevation.asciidoc[]
 include::rule-details/suspicious-lsass-access-via-malseclogon.asciidoc[]
+include::rule-details/suspicious-lsass-process-access.asciidoc[]
 include::rule-details/suspicious-ms-office-child-process.asciidoc[]
 include::rule-details/suspicious-ms-outlook-child-process.asciidoc[]
 include::rule-details/suspicious-managed-code-hosting-process.asciidoc[]
+include::rule-details/suspicious-memory-grep-activity.asciidoc[]
+include::rule-details/suspicious-microsoft-365-mail-access-by-clientappid.asciidoc[]
 include::rule-details/suspicious-microsoft-diagnostics-wizard-execution.asciidoc[]
-include::rule-details/suspicious-network-connection-attempt-by-root.asciidoc[]
+include::rule-details/suspicious-mining-process-creation-event.asciidoc[]
+include::rule-details/suspicious-modprobe-file-event.asciidoc[]
+include::rule-details/suspicious-module-loaded-by-lsass.asciidoc[]
+include::rule-details/suspicious-network-activity-to-the-internet-by-previously-unknown-executable.asciidoc[]
+include::rule-details/suspicious-network-connection-via-sudo-binary.asciidoc[]
+include::rule-details/suspicious-network-connection-via-systemd.asciidoc[]
+include::rule-details/suspicious-network-tool-launched-inside-a-container.asciidoc[]
 include::rule-details/suspicious-pdf-reader-child-process.asciidoc[]
+include::rule-details/suspicious-passwd-file-event-action.asciidoc[]
 include::rule-details/suspicious-portable-executable-encoded-in-powershell-script.asciidoc[]
 include::rule-details/suspicious-powershell-engine-imageload.asciidoc[]
 include::rule-details/suspicious-powershell-script.asciidoc[]
@@ -603,34 +928,61 @@ include::rule-details/suspicious-print-spooler-file-deletion.asciidoc[]
 include::rule-details/suspicious-print-spooler-point-and-print-dll.asciidoc[]
 include::rule-details/suspicious-print-spooler-spl-file-created.asciidoc[]
 include::rule-details/suspicious-printspooler-service-executable-file-creation.asciidoc[]
+include::rule-details/suspicious-proc-pseudo-file-system-enumeration.asciidoc[]
 include::rule-details/suspicious-process-access-via-direct-system-call.asciidoc[]
 include::rule-details/suspicious-process-creation-calltrace.asciidoc[]
 include::rule-details/suspicious-process-execution-via-renamed-psexec-executable.asciidoc[]
+include::rule-details/suspicious-process-spawned-from-motd-detected.asciidoc[]
 include::rule-details/suspicious-rdp-activex-client-loaded.asciidoc[]
 include::rule-details/suspicious-remote-registry-access-via-sebackupprivilege.asciidoc[]
+include::rule-details/suspicious-renaming-of-esxi-files.asciidoc[]
+include::rule-details/suspicious-renaming-of-esxi-index-html-file.asciidoc[]
+include::rule-details/suspicious-screenconnect-client-child-process.asciidoc[]
 include::rule-details/suspicious-script-object-execution.asciidoc[]
+include::rule-details/suspicious-service-was-installed-in-the-system.asciidoc[]
 include::rule-details/suspicious-solarwinds-child-process.asciidoc[]
 include::rule-details/suspicious-startup-shell-folder-modification.asciidoc[]
+include::rule-details/suspicious-symbolic-link-created.asciidoc[]
+include::rule-details/suspicious-sysctl-file-event.asciidoc[]
+include::rule-details/suspicious-system-commands-executed-by-previously-unknown-executable.asciidoc[]
+include::rule-details/suspicious-termination-of-esxi-process.asciidoc[]
+include::rule-details/suspicious-troubleshooting-pack-cabinet-execution.asciidoc[]
+include::rule-details/suspicious-utility-launched-via-proxychains.asciidoc[]
+include::rule-details/suspicious-wmi-event-subscription-created.asciidoc[]
 include::rule-details/suspicious-wmi-image-load-from-ms-office.asciidoc[]
 include::rule-details/suspicious-wmic-xsl-script-execution.asciidoc[]
+include::rule-details/suspicious-web-browser-sensitive-file-access.asciidoc[]
 include::rule-details/suspicious-werfault-child-process.asciidoc[]
+include::rule-details/suspicious-windows-process-cluster-spawned-by-a-host.asciidoc[]
+include::rule-details/suspicious-windows-process-cluster-spawned-by-a-parent-process.asciidoc[]
+include::rule-details/suspicious-windows-process-cluster-spawned-by-a-user.asciidoc[]
 include::rule-details/suspicious-zoom-child-process.asciidoc[]
 include::rule-details/suspicious-macos-ms-office-child-process.asciidoc[]
-include::rule-details/suspicious-service-was-installed-in-the-system.asciidoc[]
+include::rule-details/suspicious-which-enumeration.asciidoc[]
 include::rule-details/svchost-spawning-cmd.asciidoc[]
 include::rule-details/symbolic-link-to-shadow-copy-created.asciidoc[]
+include::rule-details/system-binary-copied-and-or-moved-to-suspicious-directory.asciidoc[]
+include::rule-details/system-hosts-file-access.asciidoc[]
 include::rule-details/system-information-discovery-via-windows-command-shell.asciidoc[]
 include::rule-details/system-log-file-deletion.asciidoc[]
+include::rule-details/system-network-connections-discovery.asciidoc[]
+include::rule-details/system-owner-user-discovery-linux.asciidoc[]
+include::rule-details/system-service-discovery-through-built-in-windows-utilities.asciidoc[]
 include::rule-details/system-shells-via-services.asciidoc[]
+include::rule-details/system-time-discovery.asciidoc[]
 include::rule-details/systemkey-access-via-command-line.asciidoc[]
 include::rule-details/tcc-bypass-via-mounted-apfs-snapshot-access.asciidoc[]
-include::rule-details/tampering-of-bash-command-line-history.asciidoc[]
+include::rule-details/tainted-kernel-module-load.asciidoc[]
+include::rule-details/tainted-out-of-tree-kernel-module-load.asciidoc[]
+include::rule-details/tampering-of-shell-command-line-history.asciidoc[]
 include::rule-details/temporarily-scheduled-task-creation.asciidoc[]
 include::rule-details/third-party-backup-files-deleted-via-unexpected-process.asciidoc[]
-include::rule-details/threat-detected-by-okta-threatinsight.asciidoc[]
-include::rule-details/threat-intel-filebeat-module-v8.x-indicator-match.asciidoc[]
-include::rule-details/threat-intel-indicator-match.asciidoc[]
+include::rule-details/threat-intel-hash-indicator-match.asciidoc[]
+include::rule-details/threat-intel-ip-address-indicator-match.asciidoc[]
+include::rule-details/threat-intel-url-indicator-match.asciidoc[]
+include::rule-details/threat-intel-windows-registry-indicator-match.asciidoc[]
 include::rule-details/timestomping-using-touch-command.asciidoc[]
+include::rule-details/trap-signals-execution.asciidoc[]
 include::rule-details/uac-bypass-attempt-via-elevated-com-internet-explorer-add-on-installer.asciidoc[]
 include::rule-details/uac-bypass-attempt-via-privileged-ifileoperation-com-interface.asciidoc[]
 include::rule-details/uac-bypass-attempt-via-windows-directory-masquerading.asciidoc[]
@@ -638,46 +990,71 @@ include::rule-details/uac-bypass-attempt-with-ieditionupgrademanager-elevated-co
 include::rule-details/uac-bypass-via-diskcleanup-scheduled-task-hijack.asciidoc[]
 include::rule-details/uac-bypass-via-icmluautil-elevated-com-interface.asciidoc[]
 include::rule-details/uac-bypass-via-windows-firewall-snap-in-hijack.asciidoc[]
+include::rule-details/uid-elevation-from-previously-unknown-executable.asciidoc[]
 include::rule-details/unauthorized-access-to-an-okta-application.asciidoc[]
 include::rule-details/uncommon-registry-persistence-change.asciidoc[]
 include::rule-details/unexpected-child-process-of-macos-screensaver-engine.asciidoc[]
+include::rule-details/unix-socket-connection.asciidoc[]
+include::rule-details/unknown-execution-of-binary-with-rwx-memory-region.asciidoc[]
+include::rule-details/unsigned-bits-service-client-process.asciidoc[]
+include::rule-details/unsigned-dll-loaded-by-svchost.asciidoc[]
+include::rule-details/unsigned-dll-loaded-by-a-trusted-process.asciidoc[]
+include::rule-details/unsigned-dll-side-loading-from-a-suspicious-folder.asciidoc[]
+include::rule-details/untrusted-driver-loaded.asciidoc[]
 include::rule-details/unusual-aws-command-for-a-user.asciidoc[]
 include::rule-details/unusual-child-process-from-a-system-virtual-process.asciidoc[]
-include::rule-details/unusual-child-process-of-dns.exe.asciidoc[]
+include::rule-details/unusual-child-process-of-dns-exe.asciidoc[]
 include::rule-details/unusual-child-processes-of-rundll32.asciidoc[]
 include::rule-details/unusual-city-for-an-aws-command.asciidoc[]
 include::rule-details/unusual-country-for-an-aws-command.asciidoc[]
 include::rule-details/unusual-dns-activity.asciidoc[]
+include::rule-details/unusual-discovery-activity-by-user.asciidoc[]
+include::rule-details/unusual-discovery-signal-alert-with-unusual-process-command-line.asciidoc[]
+include::rule-details/unusual-discovery-signal-alert-with-unusual-process-executable.asciidoc[]
 include::rule-details/unusual-executable-file-creation-by-a-system-critical-process.asciidoc[]
+include::rule-details/unusual-execution-via-microsoft-common-console-file.asciidoc[]
 include::rule-details/unusual-file-creation-alternate-data-stream.asciidoc[]
-include::rule-details/unusual-file-modification-by-dns.exe.asciidoc[]
+include::rule-details/unusual-file-modification-by-dns-exe.asciidoc[]
+include::rule-details/unusual-high-confidence-misconduct-blocks-detected.asciidoc[]
 include::rule-details/unusual-hour-for-a-user-to-logon.asciidoc[]
 include::rule-details/unusual-linux-network-activity.asciidoc[]
+include::rule-details/unusual-linux-network-configuration-discovery.asciidoc[]
 include::rule-details/unusual-linux-network-connection-discovery.asciidoc[]
 include::rule-details/unusual-linux-network-port-activity.asciidoc[]
 include::rule-details/unusual-linux-process-calling-the-metadata-service.asciidoc[]
 include::rule-details/unusual-linux-process-discovery-activity.asciidoc[]
 include::rule-details/unusual-linux-system-information-discovery-activity.asciidoc[]
-include::rule-details/unusual-linux-system-network-configuration-discovery.asciidoc[]
-include::rule-details/unusual-linux-system-owner-or-user-discovery-activity.asciidoc[]
 include::rule-details/unusual-linux-user-calling-the-metadata-service.asciidoc[]
+include::rule-details/unusual-linux-user-discovery-activity.asciidoc[]
 include::rule-details/unusual-linux-username.asciidoc[]
 include::rule-details/unusual-login-activity.asciidoc[]
 include::rule-details/unusual-network-activity-from-a-windows-system-binary.asciidoc[]
 include::rule-details/unusual-network-connection-via-dllhost.asciidoc[]
 include::rule-details/unusual-network-connection-via-rundll32.asciidoc[]
 include::rule-details/unusual-network-destination-domain-name.asciidoc[]
-include::rule-details/unusual-parent-process-for-cmd.exe.asciidoc[]
+include::rule-details/unusual-parent-process-for-cmd-exe.asciidoc[]
 include::rule-details/unusual-parent-child-relationship.asciidoc[]
 include::rule-details/unusual-persistence-via-services-registry.asciidoc[]
 include::rule-details/unusual-print-spooler-child-process.asciidoc[]
 include::rule-details/unusual-process-execution-path-alternate-data-stream.asciidoc[]
+include::rule-details/unusual-process-execution-on-wbem-path.asciidoc[]
+include::rule-details/unusual-process-extension.asciidoc[]
+include::rule-details/unusual-process-for-mssql-service-accounts.asciidoc[]
 include::rule-details/unusual-process-for-a-linux-host.asciidoc[]
 include::rule-details/unusual-process-for-a-windows-host.asciidoc[]
 include::rule-details/unusual-process-network-connection.asciidoc[]
+include::rule-details/unusual-process-spawned-by-a-host.asciidoc[]
+include::rule-details/unusual-process-spawned-by-a-parent-process.asciidoc[]
+include::rule-details/unusual-process-spawned-by-a-user.asciidoc[]
+include::rule-details/unusual-process-writing-data-to-an-external-device.asciidoc[]
+include::rule-details/unusual-remote-file-directory.asciidoc[]
+include::rule-details/unusual-remote-file-extension.asciidoc[]
+include::rule-details/unusual-remote-file-size.asciidoc[]
 include::rule-details/unusual-service-host-child-process-childless-service.asciidoc[]
 include::rule-details/unusual-source-ip-for-a-user-to-logon-from.asciidoc[]
 include::rule-details/unusual-sudo-activity.asciidoc[]
+include::rule-details/unusual-time-or-day-for-an-rdp-session.asciidoc[]
+include::rule-details/unusual-user-privilege-enumeration-via-id.asciidoc[]
 include::rule-details/unusual-web-request.asciidoc[]
 include::rule-details/unusual-web-user-agent.asciidoc[]
 include::rule-details/unusual-windows-network-activity.asciidoc[]
@@ -695,6 +1072,7 @@ include::rule-details/user-added-to-privileged-group.asciidoc[]
 include::rule-details/user-account-exposed-to-kerberoasting.asciidoc[]
 include::rule-details/vnc-virtual-network-computing-from-the-internet.asciidoc[]
 include::rule-details/vnc-virtual-network-computing-to-the-internet.asciidoc[]
+include::rule-details/veeam-backup-library-loaded-by-unusual-process.asciidoc[]
 include::rule-details/virtual-machine-fingerprinting.asciidoc[]
 include::rule-details/virtual-machine-fingerprinting-via-grep.asciidoc[]
 include::rule-details/virtual-private-network-connection-attempt.asciidoc[]
@@ -702,22 +1080,34 @@ include::rule-details/volume-shadow-copy-deleted-or-resized-via-vssadmin.asciido
 include::rule-details/volume-shadow-copy-deletion-via-powershell.asciidoc[]
 include::rule-details/volume-shadow-copy-deletion-via-wmic.asciidoc[]
 include::rule-details/wmi-incoming-lateral-movement.asciidoc[]
+include::rule-details/wmi-wbemtest-utility-execution.asciidoc[]
+include::rule-details/wmic-remote-command.asciidoc[]
+include::rule-details/wpad-service-exploit.asciidoc[]
+include::rule-details/writedac-access-on-active-directory-object.asciidoc[]
 include::rule-details/web-application-suspicious-activity-post-request-declined.asciidoc[]
 include::rule-details/web-application-suspicious-activity-unauthorized-method.asciidoc[]
 include::rule-details/web-application-suspicious-activity-sqlmap-user-agent.asciidoc[]
 include::rule-details/web-shell-detection-script-process-child-of-common-web-processes.asciidoc[]
 include::rule-details/webproxy-settings-modification.asciidoc[]
 include::rule-details/webserver-access-logs-deleted.asciidoc[]
+include::rule-details/werfault-reflectdebugger-persistence.asciidoc[]
 include::rule-details/whoami-process-activity.asciidoc[]
+include::rule-details/windows-account-or-group-discovery.asciidoc[]
 include::rule-details/windows-cryptoapi-spoofing-vulnerability-cve-2020-0601-curveball.asciidoc[]
 include::rule-details/windows-defender-disabled-via-registry-modification.asciidoc[]
 include::rule-details/windows-defender-exclusions-added-via-powershell.asciidoc[]
 include::rule-details/windows-event-logs-cleared.asciidoc[]
 include::rule-details/windows-firewall-disabled-via-powershell.asciidoc[]
+include::rule-details/windows-installer-with-suspicious-properties.asciidoc[]
 include::rule-details/windows-network-enumeration.asciidoc[]
 include::rule-details/windows-registry-file-creation-in-smb-share.asciidoc[]
 include::rule-details/windows-script-executing-powershell.asciidoc[]
 include::rule-details/windows-script-interpreter-executing-process-via-wmi.asciidoc[]
 include::rule-details/windows-service-installed-via-an-unusual-client.asciidoc[]
+include::rule-details/windows-subsystem-for-linux-distribution-installed.asciidoc[]
+include::rule-details/windows-subsystem-for-linux-enabled-via-dism-utility.asciidoc[]
+include::rule-details/windows-system-information-discovery.asciidoc[]
+include::rule-details/windows-system-network-connections-discovery.asciidoc[]
+include::rule-details/windows-user-account-creation.asciidoc[]
 include::rule-details/wireless-credential-dumping-using-netsh-command.asciidoc[]
-include::rule-details/zoom-meeting-with-no-passcode.asciidoc[]
+include::rule-details/zoom-meeting-with-no-passcode.asciidoc[]
\ No newline at end of file
diff --git a/docs/detections/prebuilt-rules/rule-details/a-scheduled-task-was-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/a-scheduled-task-was-created.asciidoc
index 8fd21dc402..cc08b9165d 100644
--- a/docs/detections/prebuilt-rules/rule-details/a-scheduled-task-was-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/a-scheduled-task-was-created.asciidoc
@@ -5,62 +5,65 @@ Indicates the creation of a scheduled task using Windows event logs. Adversaries
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4698
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 2 (<<a-scheduled-task-was-created-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
 
-*Added ({stack} release)*: 8.5.0
+*Version*: 8
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Legitimate scheduled tasks may be created during installation of new software.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-iam where event.action == "scheduled-task-created" and /* excluding
-tasks created by the computer account */ not user.name : "*$" and
-/* TaskContent is not parsed, exclude by full taskname noisy ones */
-not winlog.event_data.TaskName : ("\\OneDrive Standalone
-Update Task-S-1-5-21*", "\\OneDrive Standalone Update
-Task-S-1-12-1-*", "\\Hewlett-Packard\\HP Web Products
-Detection", "\\Hewlett-Packard\\HPDeviceCheck")
+[source, js]
 ----------------------------------
+iam where event.action == "scheduled-task-created" and
+
+ /* excluding tasks created by the computer account */
+ not user.name : "*$" and
+
+ /* TaskContent is not parsed, exclude by full taskname noisy ones */
+ not winlog.event_data.TaskName : (
+              "\\CreateExplorerShellUnelevatedTask",
+              "\\Hewlett-Packard\\HPDeviceCheck",
+              "\\Hewlett-Packard\\HP Support Assistant\\WarrantyChecker",
+              "\\Hewlett-Packard\\HP Support Assistant\\WarrantyChecker_backup",
+              "\\Hewlett-Packard\\HP Web Products Detection",
+              "\\Microsoft\\VisualStudio\\Updates\\BackgroundDownload",
+              "\\OneDrive Standalone Update Task-S-1-5-21*",
+              "\\OneDrive Standalone Update Task-S-1-12-1-*"
+ )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,20 +75,7 @@ Detection", "\\Hewlett-Packard\\HPDeviceCheck")
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[a-scheduled-task-was-created-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-iam where event.action == "scheduled-task-created" and /* excluding
-tasks created by the computer account */ not user.name : "*$" and
-/* TaskContent is not parsed, exclude by full taskname noisy ones */
-not winlog.event_data.TaskName : ("\\OneDrive Standalone
-Update Task-S-1-5-21*", "\\Hewlett-Packard\\HP Web
-Products Detection", "\\Hewlett-Packard\\HPDeviceCheck")
-----------------------------------
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/a-scheduled-task-was-updated.asciidoc b/docs/detections/prebuilt-rules/rule-details/a-scheduled-task-was-updated.asciidoc
index a19ae291ba..ada909e83f 100644
--- a/docs/detections/prebuilt-rules/rule-details/a-scheduled-task-was-updated.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/a-scheduled-task-was-updated.asciidoc
@@ -5,62 +5,68 @@ Indicates the update of a scheduled task using Windows event logs. Adversaries c
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
-*Severity*: low
+*Severity*: medium
 
-*Risk score*: 21
+*Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4698
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 2 (<<a-scheduled-task-was-updated-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
 
-*Added ({stack} release)*: 8.5.0
+*Version*: 8
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Legitimate scheduled tasks may be created during installation of new software.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-iam where event.action == "scheduled-task-updated" and /* excluding
-tasks created by the computer account */ not user.name : "*$" and
-not winlog.event_data.TaskName :
-("\\User_Feed_Synchronization-*", "\\OneDrive Reporting
-Task-S-1-5-21*", "\\OneDrive Reporting Task-S-1-12-1-*",
-"\\Hewlett-Packard\\HP Web Products Detection", "\\Hewlett-
-Packard\\HPDeviceCheck")
+[source, js]
 ----------------------------------
+iam where event.action == "scheduled-task-updated" and
+
+ /* excluding tasks created by the computer account */
+ not user.name : "*$" and 
+ not winlog.event_data.TaskName : "*Microsoft*" and 
+ not winlog.event_data.TaskName :
+          ("\\User_Feed_Synchronization-*",
+           "\\OneDrive Reporting Task-S-1-5-21*",
+           "\\OneDrive Reporting Task-S-1-12-1-*",
+           "\\Hewlett-Packard\\HP Web Products Detection",
+           "\\Hewlett-Packard\\HPDeviceCheck", 
+           "\\Microsoft\\Windows\\UpdateOrchestrator\\UpdateAssistant", 
+           "\\IpamDnsProvisioning",  
+           "\\Microsoft\\Windows\\UpdateOrchestrator\\UpdateAssistantAllUsersRun", 
+           "\\Microsoft\\Windows\\UpdateOrchestrator\\UpdateAssistantCalendarRun", 
+           "\\Microsoft\\Windows\\UpdateOrchestrator\\UpdateAssistantWakeupRun", 
+           "\\Microsoft\\Windows\\.NET Framework\\.NET Framework NGEN v*", 
+           "\\Microsoft\\VisualStudio\\Updates\\BackgroundDownload") and 
+  not winlog.event_data.SubjectUserSid :  ("S-1-5-18", "S-1-5-19", "S-1-5-20")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,20 +78,7 @@ Packard\\HPDeviceCheck")
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[a-scheduled-task-was-updated-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-iam where event.action == "scheduled-task-updated" and /* excluding
-tasks created by the computer account */ not user.name : "*$" and
-not winlog.event_data.TaskName :
-("\\User_Feed_Synchronization-*", "\\OneDrive Reporting
-Task-S-1-5-21*", "\\Hewlett-Packard\\HP Web Products
-Detection", "\\Hewlett-Packard\\HPDeviceCheck")
-----------------------------------
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/abnormal-process-id-or-lock-file-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/abnormal-process-id-or-lock-file-created.asciidoc
index baad36dd16..723ba62336 100644
--- a/docs/detections/prebuilt-rules/rule-details/abnormal-process-id-or-lock-file-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/abnormal-process-id-or-lock-file-created.asciidoc
@@ -3,133 +3,159 @@
 
 Identifies the creation of a Process ID (PID), lock or reboot file created in temporary file storage paradigm (tmpfs) directory /var/run. On Linux, the PID files typically hold the process ID to track previous copies running and manage other tasks. Certain Linux malware use the /var/run directory for holding data, executables and other tasks, disguising itself or these files as legitimate PID files.
 
-*Rule type*: eql
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.sandflysecurity.com/blog/linux-file-masquerading-and-malicious-pids-sandfly-1-2-6-update/
 * https://twitter.com/GossiTheDog/status/1522964028284411907
 * https://exatrack.com/public/Tricephalic_Hellkeeper.pdf
 * https://www.elastic.co/security-labs/a-peek-behind-the-bpfdoor
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Execution
-* BPFDoor
-* Investigation Guide
-
-*Version*: 102 (<<abnormal-process-id-or-lock-file-created-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Threat: BPFDoor
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
 
-*Added ({stack} release)*: 8.3.0
+*Version*: 213
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-False-Positives (FP) can appear if the PID file is legitimate and holding a process ID as intended. To differentiate, if the PID file is an executable or larger than 10 bytes, it should be ruled suspicious.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Abnormal Process ID or Lock File Created
+*Triage and analysis*
+
 
-Linux applications may need to save their process identification number (PID) for various purposes: from signaling that
-a program is running to serving as a signal that a previous instance of an application didn't exit successfully. PID
-files contain its creator process PID in an integer value.
+
+*Investigating Abnormal Process ID or Lock File Created*
+
+
+Linux applications may need to save their process identification number (PID) for various purposes: from signaling that a program is running to serving as a signal that a previous instance of an application didn't exit successfully. PID files contain its creator process PID in an integer value.
 
 Linux lock files are used to coordinate operations in files so that conflicts and race conditions are prevented.
 
-This rule identifies the creation of PID, lock, or reboot files in the /var/run/ directory. Attackers can masquerade
-malware, payloads, staged data for exfiltration, and more as legitimate PID files.
+This rule identifies the creation of PID, lock, or reboot files in the /var/run/ directory. Attackers can masquerade malware, payloads, staged data for exfiltration, and more as legitimate PID files.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Retrieve the file and determine if it is malicious:
     - Check the contents of the PID files. They should only contain integer strings.
-    - Check the file type of the lock and PID files to determine if they are executables. This is only observed in
-    malicious files.
+    - Check the file type of the lock and PID files to determine if they are executables. This is only observed in     malicious files.
     - Check the size of the subject file. Legitimate PID files should be under 10 bytes.
     - Check if the lock or PID file has high entropy. This typically indicates an encrypted payload.
         - Analysts can use tools like `ent` to measure entropy.
-    - Examine the reputation of the SHA-256 hash in the PID file. Use a database like VirusTotal to identify additional
-    pivots and artifacts for investigation.
+    - Examine the reputation of the SHA-256 hash in the PID file. Use a database like VirusTotal to identify additional pivots and artifacts for investigation.
 - Trace the file's creation to ensure it came from a legitimate or authorized process.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
-- Investigate any abnormal behavior by the subject process such as network connections, file modifications, and any
-spawned child processes.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+- Investigate any abnormal behavior by the subject process such as network connections, file modifications, and any spawned child processes.
+
 
-### False positive analysis
+*False positive analysis*
 
-- False positives can appear if the PID file is legitimate and holding a process ID as intended. If the PID file is
-an executable or has a file size that's larger than 10 bytes, it should be ruled suspicious.
-- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination
-of file name and process executable conditions.
 
-### Response and remediation
+- False positives can appear if the PID file is legitimate and holding a process ID as intended. If the PID file is an executable or has a file size that's larger than 10 bytes, it should be ruled suspicious.
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of file name and process executable conditions.
+
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Block the identified indicators of compromise (IoCs).
 - Take actions to terminate processes and connections used by the attacker.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
 
-----------------------------------
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-/* add file size filters when data is available */ file where
-event.type == "creation" and user.id == "0" and file.path regex~
-"""/var/run/\w+\.(pid|lock|reboot)""" and file.extension in
-("pid","lock","reboot") and /* handle common legitimate files */
-not file.name in ( "auditd.pid", "python*", "apport.pid",
-"apport.lock", "kworker*", "gdm3.pid", "sshd.pid",
-"acpid.pid", "unattended-upgrades.lock", "unattended-
-upgrades.pid", "cmd.pid", "cron*.pid", "yum.pid",
-"netconfig.pid", "docker.pid", "atd.pid", "lfd.pid",
-"atop.pid", "nginx.pid", "dhclient.pid", "smtpd.pid",
-"stunnel.pid", "1_waagent.pid" )
+[source, js]
 ----------------------------------
+host.os.type:linux and event.category:file and event.action:(creation or file_create_event) and
+user.id:0 and file.extension:(pid or lock or reboot) and file.path:(/var/run/* or /run/*) and (
+  (process.name : (
+    bash or dash or sh or tcsh or csh or zsh or ksh or fish or ash or touch or nano or vim or vi or editor or mv or cp)
+  ) or (
+  process.executable : (
+    ./* or /tmp/* or /var/tmp/* or /dev/shm/* or /var/run/* or /boot/* or /srv/* or /run/*
+  ))
+) and not process.name : (go or git or containerd* or snap-confine or cron or crond or sshd or unattended-upgrade or 
+vzctl or ifup or rpcbind or runc or gitlab-runner-helper or elastic-agent or metricbeat) and
+not file.name : (jem.*.pid)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -141,43 +167,3 @@ upgrades.pid", "cmd.pid", "cron*.pid", "yum.pid",
 ** Name: Native API
 ** ID: T1106
 ** Reference URL: https://attack.mitre.org/techniques/T1106/
-
-[[abnormal-process-id-or-lock-file-created-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* add file size filters when data is available */ file where
-event.type == "creation" and user.id == "0" and file.path regex~
-"""/var/run/\w+\.(pid|lock|reboot)""" and file.extension in
-("pid","lock","reboot") and /* handle common legitimate files */
-not file.name in ( "auditd.pid", "python*", "apport.pid",
-"apport.lock", "kworker*", "gdm3.pid", "sshd.pid",
-"acpid.pid", "unattended-upgrades.lock", "unattended-
-upgrades.pid", "cmd.pid", "cron*.pid", "yum.pid",
-"netconfig.pid", "docker.pid", "atd.pid", "lfd.pid",
-"atop.pid", "nginx.pid", "dhclient.pid", "smtpd.pid",
-"stunnel.pid" )
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* add file size filters when data is available */ file where
-event.type == "creation" and user.id == "0" and file.path regex~
-"""/var/run/\w+\.(pid|lock|reboot)""" and file.extension in
-("pid","lock","reboot") and /* handle common legitimate files */
-not file.name in ( "auditd.pid", "python*", "apport.pid",
-"apport.lock", "kworker*", "gdm3.pid", "sshd.pid",
-"acpid.pid", "unattended-upgrades.lock", "unattended-
-upgrades.pid", "cmd.pid", "cron*.pid" )
-----------------------------------
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/abnormally-large-dns-response.asciidoc b/docs/detections/prebuilt-rules/rule-details/abnormally-large-dns-response.asciidoc
index a3c6f3125a..977bb45f63 100644
--- a/docs/detections/prebuilt-rules/rule-details/abnormally-large-dns-response.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/abnormally-large-dns-response.asciidoc
@@ -5,111 +5,102 @@ Specially crafted DNS requests can manipulate a known overflow vulnerability in
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * packetbeat-*
 * filebeat-*
+* logs-network_traffic.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://research.checkpoint.com/2020/resolving-your-way-into-domain-admin-exploiting-a-17-year-old-bug-in-windows-dns-servers/
 * https://msrc-blog.microsoft.com/2020/07/14/july-2020-security-update-cve-2020-1350-vulnerability-in-windows-domain-name-system-dns-server/
 * https://github.com/maxpl0it/CVE-2020-1350-DoS
 * https://www.elastic.co/security-labs/detection-rules-for-sigred-vulnerability
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Resources: Investigation Guide
+* Use Case: Vulnerability
+
+*Version*: 105
+
+*Rule authors*: 
 
 * Elastic
-* Network
-* Threat Detection
-* Lateral Movement
-* Investigation Guide
 
-*Version*: 102 (<<abnormally-large-dns-response-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.10.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Environments that leverage DNS responses over 60k bytes will result in false positives - if this traffic is predictable and expected, it should be filtered out. Additionally, this detection rule could be triggered by an authorized vulnerability scan or compromise assessment.
 
-==== Investigation guide
 
+*Investigating Abnormally Large DNS Response*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Abnormally Large DNS Response
+Detection alerts from this rule indicate possible anomalous activity around large byte DNS responses from a Windows DNS server. This detection rule was created based on activity represented in exploitation of vulnerability (CVE-2020-1350) also known as https://www.elastic.co/blog/detection-rules-for-sigred-vulnerability[SigRed] during July 2020.
 
-Detection alerts from this rule indicate possible anomalous activity around large byte DNS responses from a Windows DNS
-server. This detection rule was created based on activity represented in exploitation of vulnerability (CVE-2020-1350)
-also known as [SigRed](https://www.elastic.co/blog/detection-rules-for-sigred-vulnerability) during July 2020.
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- This specific rule is sourced from network log activity such as DNS or network level data. It's important to validate
-the source of the incoming traffic and determine if this activity has been observed previously within an environment.
+
+- This specific rule is sourced from network log activity such as DNS or network level data. It's important to validate the source of the incoming traffic and determine if this activity has been observed previously within an environment.
 - Activity can be further investigated and validated by reviewing any associated Intrusion Detection Signatures (IDS) alerts.
-- Further examination can include a review of the `dns.question_type` network fieldset with a protocol analyzer, such as
-Zeek, Packetbeat, or Suricata, for `SIG` or `RRSIG` data.
-- Validate the patch level and OS of the targeted DNS server to validate the observed activity was not large-scale
-internet vulnerability scanning.
+- Further examination can include a review of the `dns.question_type` network fieldset with a protocol analyzer, such as Zeek, Packetbeat, or Suricata, for `SIG` or `RRSIG` data.
+- Validate the patch level and OS of the targeted DNS server to validate the observed activity was not large-scale internet vulnerability scanning.
 - Validate that the source of the network activity was not from an authorized vulnerability scan or compromise assessment.
 
-#### False positive analysis
 
-- Based on this rule, which looks for a threshold of 60k bytes, it is possible for activity to be generated under 65k bytes
-and related to legitimate behavior.  In packet capture files received by the [SANS Internet Storm Center](https://isc.sans.edu/forums/diary/PATCH+NOW+SIGRed+CVE20201350+Microsoft+DNS+Server+Vulnerability/26356/), byte responses
-were all observed as greater than 65k bytes.
-- This activity can be triggered by compliance/vulnerability scanning or compromise assessment; it's important to
-determine the source of the activity and potentially allowlist the source host.
+*False positive analysis*
+
+
+- Based on this rule, which looks for a threshold of 60k bytes, it is possible for activity to be generated under 65k bytes and related to legitimate behavior. In packet capture files received by the https://isc.sans.edu/forums/diary/PATCH+NOW+SIGRed+CVE20201350+Microsoft+DNS+Server+Vulnerability/26356/[SANS Internet Storm Center], byte responses were all observed as greater than 65k bytes.
+- This activity can be triggered by compliance/vulnerability scanning or compromise assessment; it's important to determine the source of the activity and potentially allowlist the source host.
+
+
+*Related rules*
 
-### Related rules
 
 - Unusual Child Process of dns.exe - 8c37dc0e-e3ac-4c97-8aa0-cf6a9122de45
 - Unusual File Modification by dns.exe - c7ce36c0-32ff-4f9a-bfc2-dcb242bf99f9
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
-- Ensure that you have deployed the latest Microsoft [Security Update](https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1350)
-(Monthly Rollup or Security Only) and restarted the patched machines. If unable to patch immediately, Microsoft [released](https://support.microsoft.com/en-us/help/4569509/windows-dns-server-remote-code-execution-vulnerability)
-a registry-based workaround that doesn’t require a restart. This can be used as a temporary solution before the patch is applied.
+- Ensure that you have deployed the latest Microsoft https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1350[Security Update] (Monthly Rollup or Security Only) and restarted the patched machines. If unable to patch immediately, Microsoft https://support.microsoft.com/en-us/help/4569509/windows-dns-server-remote-code-execution-vulnerability[released] a registry-based workaround that doesn’t require a restart. This can be used as a temporary solution before the patch is applied.
 - Maintain backups of your critical systems to aid in quick recovery.
-- Perform routine vulnerability scans of your systems, monitor [CISA advisories](https://us-cert.cisa.gov/ncas/current-activity) and patch identified vulnerabilities.
+- Perform routine vulnerability scans of your systems, monitor https://us-cert.cisa.gov/ncas/current-activity[CISA advisories] and patch identified vulnerabilities.
 - If you observe a true positive, implement a remediation plan and monitor host-based artifacts for additional post-exploitation behavior.
 
-----------------------------------
-
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and destination.port:53
-and (event.dataset:zeek.dns or type:dns or event.type:connection)
-and network.bytes > 60000
+[source, js]
 ----------------------------------
+(event.dataset: network_traffic.dns or (event.category: (network or network_traffic) and destination.port: 53)) and
+  (event.dataset:zeek.dns or type:dns or event.type:connection) and network.bytes > 60000
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -121,34 +112,3 @@ and network.bytes > 60000
 ** Name: Exploitation of Remote Services
 ** ID: T1210
 ** Reference URL: https://attack.mitre.org/techniques/T1210/
-
-[[abnormally-large-dns-response-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.16.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/accepted-default-telnet-port-connection.asciidoc b/docs/detections/prebuilt-rules/rule-details/accepted-default-telnet-port-connection.asciidoc
index 2dc6b628be..2e1b0dc314 100644
--- a/docs/detections/prebuilt-rules/rule-details/accepted-default-telnet-port-connection.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/accepted-default-telnet-port-connection.asciidoc
@@ -5,60 +5,54 @@ This rule detects network events that may indicate the use of Telnet traffic. Te
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Network
-* Threat Detection
-* Command and Control
-* Host
-* Lateral Movement
-* Initial Access
+*Tags*: 
 
-*Version*: 101 (<<accepted-default-telnet-port-connection-history, version history>>)
+* Domain: Endpoint
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Tactic: Lateral Movement
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-IoT (Internet of Things) devices and networks may use telnet and can be excluded if desired. Some business work-flows may use Telnet for administration of older devices. These often have a predictable behavior. Telnet activity involving an unusual source or destination may be more suspicious. Telnet activity involving a production server that has no known associated Telnet work-flow or business requirement is often suspicious.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and destination.port:23
-and network.direction:(inbound or ingress or outbound or egress) and
-not event.action:( flow_dropped or denied or deny or
-flow_terminated or timeout or Reject or network_flow)
+[source, js]
 ----------------------------------
+(event.dataset:network_traffic.flow or event.category:(network or network_traffic))
+    and event.type:connection and not event.action:(
+        flow_dropped or denied or deny or
+        flow_terminated or timeout or Reject or network_flow)
+    and destination.port:23
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,8 +60,6 @@ flow_terminated or timeout or Reject or network_flow)
 ** Name: Command and Control
 ** ID: TA0011
 ** Reference URL: https://attack.mitre.org/tactics/TA0011/
-
-
 * Tactic:
 ** Name: Lateral Movement
 ** ID: TA0008
@@ -76,8 +68,6 @@ flow_terminated or timeout or Reject or network_flow)
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -86,65 +76,3 @@ flow_terminated or timeout or Reject or network_flow)
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[accepted-default-telnet-port-connection-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Rule name changed from: Telnet Port Activity
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and destination.port:23
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 13 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 9 (7.15.0 release)::
-* Formatting only
-
-Version 8 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and destination.port:23
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport:tcp and destination.port:23
-----------------------------------
-
-Version 2 (7.6.1 release)::
-* Removed auditbeat-\*, packetbeat-*, and winlogbeat-* from the rule indices.
-
diff --git a/docs/detections/prebuilt-rules/rule-details/access-to-a-sensitive-ldap-attribute.asciidoc b/docs/detections/prebuilt-rules/rule-details/access-to-a-sensitive-ldap-attribute.asciidoc
index a45ff0440c..438f8f4359 100644
--- a/docs/detections/prebuilt-rules/rule-details/access-to-a-sensitive-ldap-attribute.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/access-to-a-sensitive-ldap-attribute.asciidoc
@@ -5,50 +5,55 @@ Identify access to sensitive Active Directory object attributes that contains cr
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.mandiant.com/resources/blog/apt29-windows-credential-roaming
 * https://social.technet.microsoft.com/wiki/contents/articles/11483.windows-credential-roaming.aspx
 * https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-5136
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Active Directory
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Privilege Escalation
+* Use Case: Active Directory Monitoring
+* Data Source: Active Directory
 
-*Version*: 1
+*Version*: 10
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
-The 'Audit Directory Service Changes' logging policy must be configured for (Success, Failure).
+
+
+*Setup*
+
+
+The 'Audit Directory Service Access' logging policy must be configured for (Success, Failure).
 Steps to implement the logging policy with Advanced Audit Configuration:
 
 ```
@@ -59,28 +64,41 @@ Security Settings >
 Advanced Audit Policies Configuration >
 Audit Policies >
 DS Access >
-Audit Directory Service Changes (Success,Failure)
+Audit Directory Service Access (Success,Failure)
 ```
-----------------------------------
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-any where event.action == "Directory Service Access" and event.code ==
-"4662" and not winlog.event_data.SubjectUserSid : "S-1-5-18" and
-winlog.event_data.Properties : ( /* unixUserPassword */
-"*612cb747-c0e8-4f92-9221-fdd5f15b550d*", /* ms-PKI-
-AccountCredentials */ "*b8dfa744-31dc-4ef1-ac7c-84baf7ef9da7*",
-/* ms-PKI-DPAPIMasterKeys */
-"*b3f93023-9239-4f7c-b99c-6745d87adbc2*", /* msPKI-
-CredentialRoamingTokens */ "*b7ff5a38-0818-42b0-8110-d3d154c97f24*"
-)
+[source, js]
 ----------------------------------
+any where event.action == "Directory Service Access" and event.code == "4662" and
+
+  not winlog.event_data.SubjectUserSid : "S-1-5-18" and
 
-==== Threat mapping
+  winlog.event_data.Properties : (
+   /* unixUserPassword */
+  "*612cb747-c0e8-4f92-9221-fdd5f15b550d*",
+
+  /* ms-PKI-AccountCredentials */
+  "*b8dfa744-31dc-4ef1-ac7c-84baf7ef9da7*",
+
+  /*  ms-PKI-DPAPIMasterKeys */
+  "*b3f93023-9239-4f7c-b99c-6745d87adbc2*",
+
+  /* msPKI-CredentialRoamingTokens */
+  "*b7ff5a38-0818-42b0-8110-d3d154c97f24*"
+  ) and
+
+  /*
+   Excluding noisy AccessMasks
+   0x0 undefined and 0x100 Control Access
+   https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4662
+   */
+  not winlog.event_data.AccessMask in ("0x0", "0x100")
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -92,3 +110,23 @@ CredentialRoamingTokens */ "*b7ff5a38-0818-42b0-8110-d3d154c97f24*"
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Technique:
+** Name: Unsecured Credentials
+** ID: T1552
+** Reference URL: https://attack.mitre.org/techniques/T1552/
+* Sub-technique:
+** Name: Private Keys
+** ID: T1552.004
+** Reference URL: https://attack.mitre.org/techniques/T1552/004/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Domain Accounts
+** ID: T1078.002
+** Reference URL: https://attack.mitre.org/techniques/T1078/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/access-to-keychain-credentials-directories.asciidoc b/docs/detections/prebuilt-rules/rule-details/access-to-keychain-credentials-directories.asciidoc
index a9dd29face..a712107d26 100644
--- a/docs/detections/prebuilt-rules/rule-details/access-to-keychain-credentials-directories.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/access-to-keychain-credentials-directories.asciidoc
@@ -5,147 +5,132 @@ Adversaries may collect the keychain storage data from a system to acquire crede
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://objective-see.com/blog/blog_0x25.html
 * https://securelist.com/calisto-trojan-for-macos/86543/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 207
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Credential Access
 
-*Version*: 100 (<<access-to-keychain-credentials-directories-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.10.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This rule requires data coming in from Elastic Defend.
 
-----------------------------------
 
+*Elastic Defend Integration Setup*
 
-==== Rule query
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.args : ( "/Users/*/Library/Keychains/*",
-"/Library/Keychains/*", "/Network/Library/Keychains/*",
-"System.keychain", "login.keychain-db", "login.keychain"
-) and not process.args : ("find-certificate",
-"add-trusted-cert", "set-keychain-settings",
-"delete-certificate",
-"/Users/*/Library/Keychains/openvpn.keychain-db",
-"show-keychain-info", "lock-keychain",
-"set-key-partition-list", "import",
-"find-identity") and not process.parent.executable : (
-"/Applications/OpenVPN Connect/OpenVPN
-Connect.app/Contents/MacOS/OpenVPN Connect",
-"/Applications/Microsoft Defender.app/Contents/MacOS/wdavdaemon_enterp
-rise.app/Contents/MacOS/wdavdaemon_enterprise",
-"/opt/jc/bin/jumpcloud-agent" ) and not process.executable :
-"/opt/jc/bin/jumpcloud-agent"
-----------------------------------
+*Prerequisite Requirements:*
 
-==== Threat mapping
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Credential Access
-** ID: TA0006
-** Reference URL: https://attack.mitre.org/tactics/TA0006/
-* Technique:
-** Name: Credentials from Password Stores
-** ID: T1555
-** Reference URL: https://attack.mitre.org/techniques/T1555/
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
 
-[[access-to-keychain-credentials-directories-history]]
-==== Rule version history
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.args : ( "/Users/*/Library/Keychains/*",
-"/Library/Keychains/*", "/Network/Library/Keychains/*",
-"System.keychain", "login.keychain-db", "login.keychain"
-) and not process.args : ("find-certificate",
-"add-trusted-cert", "set-keychain-settings",
-"delete-certificate",
-"/Users/*/Library/Keychains/openvpn.keychain-db",
-"show-keychain-info", "lock-keychain",
-"set-key-partition-list", "import",
-"find-identity") and not process.parent.executable :
-"/Applications/OpenVPN Connect/OpenVPN
-Connect.app/Contents/MacOS/OpenVPN Connect"
-----------------------------------
+==== Rule query
 
-Version 6 (8.2.0 release)::
-* Formatting only
 
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-process where event.type in ("start", "process_started") and
-process.args : ( "/Users/*/Library/Keychains/*",
-"/Library/Keychains/*", "/Network/Library/Keychains/*",
-"System.keychain", "login.keychain-db", "login.keychain"
-)
-----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and
+  process.args :
+    (
+      "/Users/*/Library/Keychains/*",
+      "/Library/Keychains/*",
+      "/Network/Library/Keychains/*",
+      "System.keychain",
+      "login.keychain-db",
+      "login.keychain"
+    ) and
+    not process.args : ("find-certificate",
+                        "add-trusted-cert",
+                        "set-keychain-settings",
+                        "delete-certificate",
+                        "/Users/*/Library/Keychains/openvpn.keychain-db",
+                        "show-keychain-info",
+                        "lock-keychain",
+                        "set-key-partition-list",
+                        "import",
+                        "find-identity") and
+    not process.parent.executable :
+      (
+        "/Applications/OpenVPN Connect/OpenVPN Connect.app/Contents/MacOS/OpenVPN Connect",
+        "/Applications/Microsoft Defender.app/Contents/MacOS/wdavdaemon_enterprise.app/Contents/MacOS/wdavdaemon_enterprise",
+        "/opt/jc/bin/jumpcloud-agent"
+      ) and
+    not process.executable : ("/opt/jc/bin/jumpcloud-agent", "/usr/bin/basename") and
+    not process.Ext.effective_parent.executable : ("/opt/rapid7/ir_agent/ir_agent",
+                                                   "/Library/Elastic/Endpoint/elastic-endpoint.app/Contents/MacOS/elastic-endpoint",
+                                                   "/Applications/QualysCloudAgent.app/Contents/MacOS/qualys-cloud-agent",
+                                                   "/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfDaemon.app/Contents/MacOS/JamfDaemon",
+                                                   "/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfManagementService.app/Contents/MacOS/JamfManagementService",
+                                                   "/usr/local/jamf/bin/jamf",
+                                                   "/Applications/Microsoft Defender.app/Contents/MacOS/wdavdaemon")
 
-Version 4 (7.12.0 release)::
-* Rule name changed from: Compression of Keychain Credentials Directories
-+
-* Updated query, changed from:
-+
-[source, js]
 ----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:(zip or tar or gzip or 7za or hdiutil) and
-process.args:("/Library/Keychains/" or "/Network/Library/Keychains/"
-or "~/Library/Keychains/")
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
 
-Version 2 (7.11.0 release)::
-* Formatting only
+*Framework*: MITRE ATT&CK^TM^
 
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Sub-technique:
+** Name: Keychain
+** ID: T1555.001
+** Reference URL: https://attack.mitre.org/techniques/T1555/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/accessing-outlook-data-files.asciidoc b/docs/detections/prebuilt-rules/rule-details/accessing-outlook-data-files.asciidoc
new file mode 100644
index 0000000000..5c79c58212
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/accessing-outlook-data-files.asciidoc
@@ -0,0 +1,69 @@
+[[accessing-outlook-data-files]]
+=== Accessing Outlook Data Files
+
+Identifies commands containing references to Outlook data files extensions, which can potentially indicate the search, access, or modification of these files.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.args : ("*.ost", "*.pst") and
+  not process.name : "outlook.exe" and
+  not (
+        process.name : "rundll32.exe" and
+        process.args : "*davclnt.dll,DavSetCookie*"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Email Collection
+** ID: T1114
+** Reference URL: https://attack.mitre.org/techniques/T1114/
+* Sub-technique:
+** Name: Local Email Collection
+** ID: T1114.001
+** Reference URL: https://attack.mitre.org/techniques/T1114/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/account-configured-with-never-expiring-password.asciidoc b/docs/detections/prebuilt-rules/rule-details/account-configured-with-never-expiring-password.asciidoc
index 169b574fc0..447b9dfd54 100644
--- a/docs/detections/prebuilt-rules/rule-details/account-configured-with-never-expiring-password.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/account-configured-with-never-expiring-password.asciidoc
@@ -5,108 +5,100 @@ Detects the creation and modification of an account with the "Don't Expire Passw
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.cert.ssi.gouv.fr/uploads/guide-ad.html#dont_expire
-* https://web.archive.org/web/20230329171952/https://blog.menasec.net/2019/02/threat-hunting-26-persistent-password.html
+* http://web.archive.org/web/20230329171952/https://blog.menasec.net/2019/02/threat-hunting-26-persistent-password.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Active Directory
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Active Directory
-* Investigation Guide
 
-*Version*: 102 (<<account-configured-with-never-expiring-password-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.2.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-User accounts can be used as service accounts and have their password set never to expire. This is a bad security practice that exposes the account to Credential Access attacks. For cases in which user accounts cannot be avoided, Microsoft provides the Group Managed Service Accounts (gMSA) feature, which ensures that the account password is robust and changed regularly and automatically.
 
-==== Investigation guide
 
+*Investigating Account Configured with Never-Expiring Password*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Account Configured with Never-Expiring Password
+Active Directory provides a setting that prevents users' passwords from expiring. Enabling this setting is bad practice and can expose environments to vulnerabilities that weaken security posture, especially when these accounts are privileged.
+
+The setting is usually configured so a user account can act as a service account. Attackers can abuse these accounts to persist in the domain and maintain long-term access using compromised accounts with a never-expiring password set.
 
-Active Directory provides a setting that prevents users' passwords from expiring. Enabling this setting is bad practice and can expose
-environments to vulnerabilities that weaken security posture, especially when these accounts are privileged.
 
-The setting is usually configured so a user account can act as a service account. Attackers can abuse these accounts to
-persist in the domain and maintain long-term access using compromised accounts with a never-expiring password set.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/source host during the past 48 hours.
 - Inspect the account for suspicious or abnormal behaviors in the alert timeframe.
 
-### False positive analysis
 
-- This activity should not happen legitimately. The security team should address any potential benign true positive
-(B-TP), as this configuration can put the user and the domain at risk.
-- Using user accounts as service accounts is a bad security practice and should not be allowed in the domain. The
-security team should map and monitor potential benign true positives (B-TPs), especially if the account is privileged.
-For cases in which user accounts cannot be avoided, Microsoft provides the Group Managed Service Accounts (gMSA) feature,
-which ensures that the account password is robust and changed regularly and automatically.
+*False positive analysis*
+
+
+- This activity should not happen legitimately. The security team should address any potential benign true positive (B-TP), as this configuration can put the user and the domain at risk.
+- Using user accounts as service accounts is a bad security practice and should not be allowed in the domain. The security team should map and monitor potential benign true positives (B-TPs), especially if the account is privileged. For cases in which user accounts cannot be avoided, Microsoft provides the Group Managed Service Accounts (gMSA) feature, which ensures that the account password is robust and changed regularly and automatically.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Review the privileges assigned to the user to ensure that the least privilege principle is being followed.
 - Reset the password of the account and update its password settings.
 - Search for other occurrences on the domain.
-    - Using the [Active Directory PowerShell module](https://docs.microsoft.com/en-us/powershell/module/activedirectory/get-aduser):
+    - Using the https://docs.microsoft.com/en-us/powershell/module/activedirectory/get-aduser[Active Directory PowerShell module]:
         - `get-aduser -filter { passwordNeverExpires -eq $true  -and enabled -eq $true } | ft`
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts, if
-any, are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email,
-business systems, and web services.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.action:"modified-user-account" and event.code:"4738" and
-message:"'Don't Expire Password' - Enabled" and not user.id:"S-1-5-18"
+[source, js]
 ----------------------------------
+event.action:"modified-user-account" and winlog.api:"wineventlog" and event.code:"4738" and
+  message:"'Don't Expire Password' - Enabled" and not user.id:"S-1-5-18"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -118,18 +110,3 @@ message:"'Don't Expire Password' - Enabled" and not user.id:"S-1-5-18"
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[account-configured-with-never-expiring-password-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.3.0 release)::
-* Rule name changed from: Account configured with never Expiring Password
diff --git a/docs/detections/prebuilt-rules/rule-details/account-discovery-command-via-system-account.asciidoc b/docs/detections/prebuilt-rules/rule-details/account-discovery-command-via-system-account.asciidoc
index e43adf0689..c3516fad7a 100644
--- a/docs/detections/prebuilt-rules/rule-details/account-discovery-command-via-system-account.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/account-discovery-command-via-system-account.asciidoc
@@ -5,211 +5,137 @@ Identifies when the SYSTEM account uses an account discovery utility. This could
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<account-discovery-command-via-system-account-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Tactic: Privilege Escalation
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Account Discovery Command via SYSTEM Account
+*Triage and analysis*
 
-After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps.
-This can happen by running commands to enumerate network resources, users, connections, files, and installed security
-software.
 
-This rule looks for the execution of account discovery utilities using the SYSTEM account, which is commonly observed
-after attackers successfully perform privilege escalation or exploit web applications.
 
-#### Possible investigation steps
+*Investigating Account Discovery Command via SYSTEM Account*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-  - If the process tree includes a web-application server process such as w3wp, httpd.exe, nginx.exe and alike,
-  investigate any suspicious file creation or modification in the last 48 hours to assess the presence of any potential
-  webshell backdoor.
-- Investigate other alerts associated with the user/host during the past 48 hours.
-- Determine how the SYSTEM account is being used. For example, users with administrator privileges can spawn a system
-shell using Windows services, scheduled tasks or other third party utilities.
 
-### False positive analysis
+After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
 
-- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify
-suspicious activity related to the user or host, such alerts can be dismissed.
+This rule looks for the execution of account discovery utilities using the SYSTEM account, which is commonly observed after attackers successfully perform privilege escalation or exploit web applications.
 
-### Response and remediation
 
-- Initiate the incident response process based on the outcome of the triage.
-- Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-- Use the data collected through the analysis to investigate other machines affected in the environment.
-----------------------------------
+*Possible investigation steps*
 
 
-==== Rule query
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - If the process tree includes a web-application server process such as w3wp, httpd.exe, nginx.exe and alike, investigate any suspicious file creation or modification in the last 48 hours to assess the presence of any potential webshell backdoor.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Determine how the SYSTEM account is being used. For example, users with administrator privileges can spawn a system shell using Windows services, scheduled tasks or other third party utilities.
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and
-(?process.Ext.token.integrity_level_name : "System" or
-?winlog.event_data.IntegrityLevel : "System") and (process.name :
-"whoami.exe" or (process.name : "net1.exe" and not
-process.parent.name : "net.exe"))
-----------------------------------
+*False positive analysis*
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
 
-* Tactic:
-** Name: Discovery
-** ID: TA0007
-** Reference URL: https://attack.mitre.org/tactics/TA0007/
-* Technique:
-** Name: System Owner/User Discovery
-** ID: T1033
-** Reference URL: https://attack.mitre.org/techniques/T1033/
 
-[[account-discovery-command-via-system-account-history]]
-==== Rule version history
+*Response and remediation*
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(?process.Ext.token.integrity_level_name : "System" or
-?winlog.event_data.IntegrityLevel : "System") and (process.name :
-"whoami.exe" or (process.name : "net1.exe" and not
-process.parent.name : "net.exe"))
-----------------------------------
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+- Use the data collected through the analysis to investigate other machines affected in the environment.
 
-Version 14 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(?process.Ext.token.integrity_level_name : "System" or
-?winlog.event_data.IntegrityLevel : "System") and (process.name :
-"whoami.exe" or (process.name : "net1.exe" and not
-process.parent.name : "net.exe"))
-----------------------------------
 
-Version 12 (8.3.0 release)::
-* Formatting only
+==== Setup
 
-Version 11 (8.2.0 release)::
-* Rule name changed from: Net command via SYSTEM account
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.Ext.token.integrity_level_name : "System" or
-winlog.event_data.IntegrityLevel : "System") and process.name :
-"whoami.exe" or (process.name : "net1.exe" and not
-process.parent.name : "net.exe")
-----------------------------------
 
-Version 9 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-user.id in ("S-1-5-18", "S-1-5-19", "S-1-5-20") and process.name :
-"whoami.exe" or (process.name : "net1.exe" and not
-process.parent.name : "net.exe")
-----------------------------------
 
-Version 8 (7.16.0 release)::
-* Formatting only
+*Setup*
 
-Version 7 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-(process.name:(whoami.exe or net.exe) or process.name:net1.exe and not
-process.parent.name:net.exe) and user.name:SYSTEM
-----------------------------------
 
-Version 6 (7.12.0 release)::
-* Formatting only
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
-Version 5 (7.11.2 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-(process.name:net.exe or process.name:net1.exe and not
-process.parent.name:net.exe) and user.name:SYSTEM
-----------------------------------
+==== Rule query
 
-Version 3 (7.9.1 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-(process.name:net.exe or process.name:net1.exe and not
-process.parent.name:net.exe) and user.name:SYSTEM and
-event.action:"Process Create (rule: ProcessCreate)"
+process where host.os.type == "windows" and event.type == "start" and
+  (?process.Ext.token.integrity_level_name : "System" or
+  ?winlog.event_data.IntegrityLevel : "System") and
+  (
+    process.name : "whoami.exe" or
+    (
+      process.name : "net1.exe" and not process.parent.name : "net.exe" and not process.args : ("start", "stop", "/active:*")
+    )
+  )
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Owner/User Discovery
+** ID: T1033
+** Reference URL: https://attack.mitre.org/techniques/T1033/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Local Accounts
+** ID: T1078.003
+** Reference URL: https://attack.mitre.org/techniques/T1078/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/account-or-group-discovery-via-built-in-tools.asciidoc b/docs/detections/prebuilt-rules/rule-details/account-or-group-discovery-via-built-in-tools.asciidoc
new file mode 100644
index 0000000000..a3fe5ae5b2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/account-or-group-discovery-via-built-in-tools.asciidoc
@@ -0,0 +1,92 @@
+[[account-or-group-discovery-via-built-in-tools]]
+=== Account or Group Discovery via Built-In Tools
+
+Adversaries may use built-in applications to get a listing of local system or domain accounts and groups.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started") and ( 
+  (process.name in ("groups", "id")) or 
+  (process.name == "dscl" and process.args : ("/Active Directory/*", "/Users*", "/Groups*")) or
+  (process.name == "dscacheutil" and process.args in ("user", "group")) or
+  (process.args in ("/etc/passwd", "/etc/master.passwd", "/etc/sudoers")) or
+  (process.name == "getent" and process.args in ("passwd", "group"))
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Permission Groups Discovery
+** ID: T1069
+** Reference URL: https://attack.mitre.org/techniques/T1069/
+* Sub-technique:
+** Name: Local Groups
+** ID: T1069.001
+** Reference URL: https://attack.mitre.org/techniques/T1069/001/
+* Sub-technique:
+** Name: Domain Groups
+** ID: T1069.002
+** Reference URL: https://attack.mitre.org/techniques/T1069/002/
+* Technique:
+** Name: Account Discovery
+** ID: T1087
+** Reference URL: https://attack.mitre.org/techniques/T1087/
+* Sub-technique:
+** Name: Local Account
+** ID: T1087.001
+** Reference URL: https://attack.mitre.org/techniques/T1087/001/
+* Sub-technique:
+** Name: Domain Account
+** ID: T1087.002
+** Reference URL: https://attack.mitre.org/techniques/T1087/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/account-password-reset-remotely.asciidoc b/docs/detections/prebuilt-rules/rule-details/account-password-reset-remotely.asciidoc
index edb406066b..dff16ebc71 100644
--- a/docs/detections/prebuilt-rules/rule-details/account-password-reset-remotely.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/account-password-reset-remotely.asciidoc
@@ -5,71 +5,80 @@ Identifies an attempt to reset a potentially privileged account password remotel
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-system.*
+* logs-system.security*
+* logs-windows.forwarded*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4724
 * https://stealthbits.com/blog/manipulating-user-passwords-with-mimikatz/
 * https://github.com/sbousseaden/EVTX-ATTACK-SAMPLES/blob/master/Credential%20Access/remote_pwd_reset_rpc_mimikatz_postzerologon_target_DC.evtx
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Impact
+
+*Version*: 114
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
 
-*Version*: 101 (<<account-password-reset-remotely-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.0.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Legitimate remote account administration.
+*Performance*
+
+This rule may cause medium to high performance impact due to logic scoping all remote Windows logon activity.
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=5m [authentication where
-event.action == "logged-in" and /* event 4624 need to be logged */
-winlog.logon.type : "Network" and event.outcome == "success" and
-source.ip != null and source.ip != "127.0.0.1" and source.ip !=
-"::1"] by winlog.event_data.TargetLogonId /* event 4724 need to be
-logged */ [iam where event.action == "reset-password" and (
-/* This rule is very noisy if not scoped to privileged
-accounts, duplicate the rule and add your own naming convention
-and accounts of interest here. */
-winlog.event_data.TargetUserName: ("*Admin*", "*super*", "*SVC*",
-"*DC0*", "*service*", "*DMZ*", "*ADM*") or
-winlog.event_data.TargetSid : ("S-1-5-21-*-500", "S-1-12-1-*-500")
-) ] by winlog.event_data.SubjectLogonId
+[source, js]
 ----------------------------------
+sequence by winlog.computer_name with maxspan=1m
+  [authentication where event.action == "logged-in" and
+    /* event 4624 need to be logged */
+    winlog.logon.type : "Network" and event.outcome == "success" and source.ip != null and
+    source.ip != "127.0.0.1" and source.ip != "::1" and
+    not winlog.event_data.TargetUserName : ("svc*", "PIM_*", "_*_", "*-*-*", "*$")] by winlog.event_data.TargetLogonId
+   /* event 4724 need to be logged */
+  [iam where event.action == "reset-password" and
+   (
+    /*
+       This rule is very noisy if not scoped to privileged accounts, duplicate the
+       rule and add your own naming convention and accounts of interest here.
+     */
+    winlog.event_data.TargetUserName: ("*Admin*", "*super*", "*SVC*", "*DC0*", "*service*", "*DMZ*", "*ADM*") or
+    winlog.event_data.TargetSid : ("S-1-5-21-*-500", "S-1-12-1-*-500")
+    )
+  ] by winlog.event_data.SubjectLogonId
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,61 +90,11 @@ winlog.event_data.TargetSid : ("S-1-5-21-*-500", "S-1-12-1-*-500")
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[account-password-reset-remotely-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5m [authentication where
-event.action == "logged-in" and /* event 4624 need to be logged */
-winlog.logon.type : "Network" and event.outcome == "success" and
-source.ip != null and source.ip != "127.0.0.1" and source.ip !=
-"::1"] by winlog.event_data.TargetLogonId /* event 4724 need to be
-logged */ [iam where event.action == "reset-password" and (
-/* This rule is very noisy if not scoped to privileged
-accounts, duplicate the rule and add your own naming convention
-and accounts of interest here. */
-winlog.event_data.TargetUserName: ("*Admin*", "*super*", "*SVC*",
-"*DC0*", "*service*", "*DMZ*", "*ADM*") or
-winlog.event_data.TargetSid : "S-1-5-21-*-500" ) ] by
-winlog.event_data.SubjectLogonId
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5m [authentication where
-event.action == "logged-in" and /* event 4624 need to be logged */
-winlog.logon.type : "Network" and event.outcome == "success" and
-source.ip != null and source.ip != "127.0.0.1" and source.ip !=
-"::1"] by winlog.event_data.TargetLogonId /* event 4724 need to be
-logged */ [iam where event.action == "reset-password"] by
-winlog.event_data.SubjectLogonId
-----------------------------------
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5m [authentication where
-event.action == "logged-in" and /* event 4624 need to be logged */
-winlog.logon.type : "Network" and event.outcome == "success" and
-source.ip != null and not source.ip in ("127.0.0.1", "::1")] by
-winlog.event_data.TargetLogonId /* event 4724 need to be logged */
-[iam where event.action == "reset-password"] by
-winlog.event_data.SubjectLogonId
-----------------------------------
-
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Account Access Removal
+** ID: T1531
+** Reference URL: https://attack.mitre.org/techniques/T1531/
diff --git a/docs/detections/prebuilt-rules/rule-details/adding-hidden-file-attribute-via-attrib.asciidoc b/docs/detections/prebuilt-rules/rule-details/adding-hidden-file-attribute-via-attrib.asciidoc
index 46a504be3a..ef7eb94205 100644
--- a/docs/detections/prebuilt-rules/rule-details/adding-hidden-file-attribute-via-attrib.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/adding-hidden-file-attribute-via-attrib.asciidoc
@@ -5,142 +5,147 @@ Adversaries can add the 'hidden' attribute to files to hide them from the user i
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<adding-hidden-file-attribute-via-attrib-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Adding Hidden File Attribute via Attrib*
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "attrib.exe"
-and process.args : "+h"
-----------------------------------
 
-==== Threat mapping
+The `Hidden` attribute is a file or folder attribute that makes the file or folder invisible to regular directory listings when the attribute is set. 
 
-*Framework*: MITRE ATT&CK^TM^
+Attackers can use this attribute to conceal tooling and malware to prevent administrators and users from finding it, even if they are looking specifically for it.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Hide Artifacts
-** ID: T1564
-** Reference URL: https://attack.mitre.org/techniques/T1564/
+This rule looks for the execution of the `attrib.exe` utility with a command line that indicates the modification of the `Hidden` attribute.
 
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-* Tactic:
-** Name: Persistence
-** ID: TA0003
-** Reference URL: https://attack.mitre.org/tactics/TA0003/
 
-[[adding-hidden-file-attribute-via-attrib-history]]
-==== Rule version history
+*Possible investigation steps*
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "attrib.exe" and process.args : "+h"
-----------------------------------
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Examine the command line to identify the target file or folder.
+  - Examine the file, which process created it, header, etc.
+  - If suspicious, retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Observe and collect information about the following activities in the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
 
-Version 15 (8.4.0 release)::
-* Formatting only
 
-Version 13 (8.3.0 release)::
-* Formatting only
+*False positive analysis*
 
-Version 11 (8.2.0 release)::
-* Formatting only
 
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:attrib.exe and process.args:+h
-----------------------------------
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-Version 8 (7.12.0 release)::
-* Formatting only
 
-Version 7 (7.11.2 release)::
-* Formatting only
+*Response and remediation*
 
-Version 6 (7.11.0 release)::
-* Formatting only
 
-Version 5 (7.10.0 release)::
-* Formatting only
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 4 (7.9.1 release)::
-* Formatting only
 
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:attrib.exe and process.args:+h
-----------------------------------
+==== Rule query
+
 
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:"attrib.exe" and process.args:"+h"
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "attrib.exe" or ?process.pe.original_file_name == "ATTRIB.EXE") and process.args : "+h" and
+  not (process.parent.name: "cmd.exe" and process.command_line: "attrib  +R +H +S +A *.cui")
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hide Artifacts
+** ID: T1564
+** Reference URL: https://attack.mitre.org/techniques/T1564/
+* Sub-technique:
+** Name: Hidden Files and Directories
+** ID: T1564.001
+** Reference URL: https://attack.mitre.org/techniques/T1564/001/
+* Technique:
+** Name: File and Directory Permissions Modification
+** ID: T1222
+** Reference URL: https://attack.mitre.org/techniques/T1222/
+* Sub-technique:
+** Name: Windows File and Directory Permissions Modification
+** ID: T1222.001
+** Reference URL: https://attack.mitre.org/techniques/T1222/001/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
diff --git a/docs/detections/prebuilt-rules/rule-details/adfind-command-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/adfind-command-activity.asciidoc
index ede9845877..d115b66d5e 100644
--- a/docs/detections/prebuilt-rules/rule-details/adfind-command-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/adfind-command-activity.asciidoc
@@ -5,24 +5,25 @@ This rule detects the Active Directory query tool, AdFind.exe. AdFind has legiti
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * http://www.joeware.net/freetools/tools/adfind/
 * https://thedfirreport.com/2020/05/08/adfind-recon/
@@ -31,98 +32,106 @@ This rule detects the Active Directory query tool, AdFind.exe. AdFind has legiti
 * https://www.fireeye.com/blog/threat-research/2019/04/pick-six-intercepting-a-fin6-intrusion.html
 * https://usa.visa.com/dam/VCOM/global/support-legal/documents/fin6-cybercrime-group-expands-threat-To-ecommerce-merchants.pdf
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<adfind-command-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AdFind Command Activity
+*Triage and analysis*
+
+
 
-[AdFind](http://www.joeware.net/freetools/tools/adfind/) is a freely available command-line tool used to retrieve information
-from Active Directory (AD). Network discovery and enumeration tools like `AdFind` are useful to adversaries in the same
-ways they are effective for network administrators. This tool provides quick ability to scope AD person/computer objects
-and understand subnets and domain information. There are many [examples](https://thedfirreport.com/category/adfind/) of
-this tool being adopted by ransomware and criminal groups and used in compromises.
+*Investigating AdFind Command Activity*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+http://www.joeware.net/freetools/tools/adfind/[AdFind] is a freely available command-line tool used to retrieve information from Active Directory (AD). Network discovery and enumeration tools like `AdFind` are useful to adversaries in the same ways they are effective for network administrators. This tool provides quick ability to scope AD person/computer objects and understand subnets and domain information. There are many https://thedfirreport.com/category/adfind/[examples] of this tool being adopted by ransomware and criminal groups and used in compromises.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Examine the command line to determine what information was retrieved by the tool.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This rule has a high chance to produce false positives as it is a legitimate tool used by network administrators.
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination
-of user and command line conditions.
-- Malicious behavior with `AdFind` should be investigated as part of a step within an attack chain. It doesn't happen in
-isolation, so reviewing previous logs/activity from impacted machines can be very telling.
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- Malicious behavior with `AdFind` should be investigated as part of a step within an attack chain. It doesn't happen in isolation, so reviewing previous logs/activity from impacted machines can be very telling.
+
+
+*Related rules*
 
-### Related rules
 
 - Windows Network Enumeration - 7b8bfc26-81d2-435e-965c-d722ee397ef1
 - Enumeration of Administrator Accounts - 871ea072-1b71-4def-b016-6278b505138d
 - Enumeration Command Spawned via WMIPrvSE - 770e0c4d-b998-41e5-a62e-c7901fd7f470
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name : "AdFind.exe"
-or process.pe.original_file_name == "AdFind.exe") and process.args :
-("objectcategory=computer", "(objectcategory=computer)",
-"objectcategory=person", "(objectcategory=person)",
-"objectcategory=subnet", "(objectcategory=subnet)",
-"objectcategory=group", "(objectcategory=group)",
-"objectcategory=organizationalunit",
-"(objectcategory=organizationalunit)",
-"objectcategory=attributeschema", "(objectcategory=attributeschema)",
-"domainlist", "dcmodes", "adinfo", "dclist", "computers_pwnotreqd",
-"trustdmp")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "AdFind.exe" or ?process.pe.original_file_name == "AdFind.exe") and
+  process.args : ("objectcategory=computer", "(objectcategory=computer)",
+                  "objectcategory=person", "(objectcategory=person)",
+                  "objectcategory=subnet", "(objectcategory=subnet)",
+                  "objectcategory=group", "(objectcategory=group)",
+                  "objectcategory=organizationalunit", "(objectcategory=organizationalunit)",
+                  "objectcategory=attributeschema", "(objectcategory=attributeschema)",
+                  "domainlist", "dcmodes", "adinfo", "dclist", "computers_pwnotreqd", "trustdmp")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -134,69 +143,27 @@ or process.pe.original_file_name == "AdFind.exe") and process.args :
 ** Name: Remote System Discovery
 ** ID: T1018
 ** Reference URL: https://attack.mitre.org/techniques/T1018/
-
-[[adfind-command-activity-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "AdFind.exe" or process.pe.original_file_name ==
-"AdFind.exe") and process.args : ("objectcategory=computer",
-"(objectcategory=computer)",
-"objectcategory=person", "(objectcategory=person)",
-"objectcategory=subnet", "(objectcategory=subnet)",
-"objectcategory=group", "(objectcategory=group)",
-"objectcategory=organizationalunit",
-"(objectcategory=organizationalunit)",
-"objectcategory=attributeschema", "(objectcategory=attributeschema)",
-"domainlist", "dcmodes", "adinfo", "dclist", "computers_pwnotreqd",
-"trustdmp")
-----------------------------------
-
-Version 10 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "AdFind.exe" or process.pe.original_file_name ==
-"AdFind.exe") and process.args : ("objectcategory=computer",
-"(objectcategory=computer)",
-"objectcategory=person", "(objectcategory=person)",
-"objectcategory=subnet", "(objectcategory=subnet)",
-"objectcategory=group", "(objectcategory=group)",
-"objectcategory=organizationalunit",
-"(objectcategory=organizationalunit)",
-"objectcategory=attributeschema", "(objectcategory=attributeschema)",
-"domainlist", "dcmodes", "adinfo", "dclist", "computers_pwnotreqd",
-"trustdmp")
-----------------------------------
-
-Version 8 (8.3.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.16.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Technique:
+** Name: Permission Groups Discovery
+** ID: T1069
+** Reference URL: https://attack.mitre.org/techniques/T1069/
+* Sub-technique:
+** Name: Domain Groups
+** ID: T1069.002
+** Reference URL: https://attack.mitre.org/techniques/T1069/002/
+* Technique:
+** Name: Account Discovery
+** ID: T1087
+** Reference URL: https://attack.mitre.org/techniques/T1087/
+* Sub-technique:
+** Name: Domain Account
+** ID: T1087.002
+** Reference URL: https://attack.mitre.org/techniques/T1087/002/
+* Technique:
+** Name: Domain Trust Discovery
+** ID: T1482
+** Reference URL: https://attack.mitre.org/techniques/T1482/
+* Technique:
+** Name: System Network Configuration Discovery
+** ID: T1016
+** Reference URL: https://attack.mitre.org/techniques/T1016/
diff --git a/docs/detections/prebuilt-rules/rule-details/administrator-privileges-assigned-to-an-okta-group.asciidoc b/docs/detections/prebuilt-rules/rule-details/administrator-privileges-assigned-to-an-okta-group.asciidoc
index 4154fe61c5..875c0f4f08 100644
--- a/docs/detections/prebuilt-rules/rule-details/administrator-privileges-assigned-to-an-okta-group.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/administrator-privileges-assigned-to-an-okta-group.asciidoc
@@ -5,7 +5,7 @@ Detects when an administrator role is assigned to an Okta group. An adversary ma
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,60 +14,52 @@ Detects when an administrator role is assigned to an Okta group. An adversary ma
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Security/administrators-admin-comparison.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 102 (<<administrator-privileges-assigned-to-an-okta-group-history, version history>>)
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 205
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Administrator roles may be assigned to Okta users by a Super Admin user. Verify that the behavior was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:okta.system and event.action:group.privilege.grant
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,36 +71,3 @@ event.dataset:okta.system and event.action:group.privilege.grant
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[administrator-privileges-assigned-to-an-okta-group-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Rule name changed from: Administrator Privileges Assigned to Okta Group
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:group.privilege.grant
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/administrator-role-assigned-to-an-okta-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/administrator-role-assigned-to-an-okta-user.asciidoc
index bfdc18880c..65db21d0b5 100644
--- a/docs/detections/prebuilt-rules/rule-details/administrator-role-assigned-to-an-okta-user.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/administrator-role-assigned-to-an-okta-user.asciidoc
@@ -5,7 +5,7 @@ Identifies when an administrator role is assigned to an Okta user. An adversary
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,60 +14,52 @@ Identifies when an administrator role is assigned to an Okta user. An adversary
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Security/administrators-admin-comparison.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Okta
-* SecOps
-* Monitoring
-* Continuous Monitoring
-
-*Version*: 102 (<<administrator-role-assigned-to-an-okta-user-history, version history>>)
+* Data Source: Okta
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 205
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Administrator roles may be assigned to Okta users by a Super Admin user. Verify that the behavior was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and
-event.action:user.account.privilege.grant
+[source, js]
 ----------------------------------
+event.dataset:okta.system and event.action:user.account.privilege.grant
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,25 +71,3 @@ event.action:user.account.privilege.grant
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[administrator-role-assigned-to-an-okta-user-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/adminsdholder-backdoor.asciidoc b/docs/detections/prebuilt-rules/rule-details/adminsdholder-backdoor.asciidoc
index f1a7235e00..57c3ce56af 100644
--- a/docs/detections/prebuilt-rules/rule-details/adminsdholder-backdoor.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/adminsdholder-backdoor.asciidoc
@@ -5,55 +5,54 @@ Detects modifications in the AdminSDHolder object. Attackers can abuse the SDPro
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://adsecurity.org/?p=1906
 * https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/appendix-c--protected-accounts-and-groups-in-active-directory#adminsdholder
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Active Directory
-
-*Version*: 100 (<<adminsdholder-backdoor-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Use Case: Active Directory Monitoring
+* Data Source: Active Directory
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.action:"Directory Service Changes" and event.code:5136 and
-winlog.event_data.ObjectDN:CN=AdminSDHolder,CN=System*
-----------------------------------
+  winlog.event_data.ObjectDN:CN=AdminSDHolder,CN=System*
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -61,16 +60,15 @@ winlog.event_data.ObjectDN:CN=AdminSDHolder,CN=System*
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-[[adminsdholder-backdoor-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Domain Accounts
+** ID: T1078.002
+** Reference URL: https://attack.mitre.org/techniques/T1078/002/
+* Technique:
+** Name: Account Manipulation
+** ID: T1098
+** Reference URL: https://attack.mitre.org/techniques/T1098/
diff --git a/docs/detections/prebuilt-rules/rule-details/adminsdholder-sdprop-exclusion-added.asciidoc b/docs/detections/prebuilt-rules/rule-details/adminsdholder-sdprop-exclusion-added.asciidoc
index 6b95d7ed48..1427d3a97c 100644
--- a/docs/detections/prebuilt-rules/rule-details/adminsdholder-sdprop-exclusion-added.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/adminsdholder-sdprop-exclusion-added.asciidoc
@@ -5,75 +5,72 @@ Identifies a modification on the dsHeuristics attribute on the bit that holds th
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.cert.ssi.gouv.fr/uploads/guide-ad.html#dsheuristics_bad
 * https://petri.com/active-directory-security-understanding-adminsdholder-object
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Active Directory
-* Investigation Guide
-
-*Version*: 102 (<<adminsdholder-sdprop-exclusion-added-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Active Directory
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
 
-*Added ({stack} release)*: 8.2.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AdminSDHolder SDProp Exclusion Added
+*Triage and analysis*
+
+
+
+*Investigating AdminSDHolder SDProp Exclusion Added*
+
 
-The SDProp process compares the permissions on protected objects with those defined on the AdminSDHolder object. If the
-permissions on any of the protected accounts and groups do not match, it resets the permissions on the protected
-accounts and groups to match those defined in the domain AdminSDHolder object.
+The SDProp process compares the permissions on protected objects with those defined on the AdminSDHolder object. If the permissions on any of the protected accounts and groups do not match, it resets the permissions on the protected accounts and groups to match those defined in the domain AdminSDHolder object.
 
-The dSHeuristics is a Unicode string attribute, in which each character in the string represents a heuristic that is
-used to determine the behavior of Active Directory.
+The dSHeuristics is a Unicode string attribute, in which each character in the string represents a heuristic that is used to determine the behavior of Active Directory.
 
-Administrators can use the dSHeuristics attribute to exclude privilege groups from the SDProp process by setting the
-16th bit (dwAdminSDExMask) of the string to a certain value, which represents the group(s):
+Administrators can use the dSHeuristics attribute to exclude privilege groups from the SDProp process by setting the 16th bit (dwAdminSDExMask) of the string to a certain value, which represents the group(s):
 
-* For example, to exclude the Account Operators group, an administrator would modify the string, so the 16th character
-is set to 1 (i.e., 0000000001000001).
+- For example, to exclude the Account Operators group, an administrator would modify the string, so the 16th character is set to 1 (i.e., 0000000001000001).
 
-The usage of this exclusion can leave the accounts unprotected and facilitate the misconfiguration of privileges for the
-excluded groups, enabling attackers to add accounts to these groups to maintain long-term persistence with high
-privileges.
+The usage of this exclusion can leave the accounts unprotected and facilitate the misconfiguration of privileges for the excluded groups, enabling attackers to add accounts to these groups to maintain long-term persistence with high privileges.
 
 This rule matches changes of the dsHeuristics object where the 16th bit is set to a value other than zero.
 
-#### Possible investigation steps
+
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account and system owners and confirm whether they are aware of this activity.
@@ -83,61 +80,78 @@ This rule matches changes of the dsHeuristics object where the 16th bit is set t
     - Server Operators eq 2
     - Print Operators eq 4
     - Backup Operators eq 8
-    The field value can range from 0 to f (15). If more than one group is specified, the values will be summed together;
-    for example, Backup Operators and Print Operators will set the `c` value on the bit.
+    The field value can range from 0 to f (15). If more than one group is specified, the values will be summed together; for example, Backup Operators and Print Operators will set the `c` value on the bit.
+
+
+*False positive analysis*
 
-### False positive analysis
 
-- While this modification can be done legitimately, it is not a best practice. Any potential benign true positive (B-TP)
-should be mapped and reviewed by the security team for alternatives as this weakens the security of the privileged group.
+- While this modification can be done legitimately, it is not a best practice. Any potential benign true positive (B-TP) should be mapped and reviewed by the security team for alternatives as this weakens the security of the privileged group.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - The change can be reverted by setting the dwAdminSDExMask (16th bit) to 0 in dSHeuristics.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
-==== Rule query
+==== Setup
 
 
-[source,js]
-----------------------------------
-any where event.action == "Directory Service Changes" and event.code
-== "5136" and winlog.event_data.AttributeLDAPDisplayName :
-"dSHeuristics" and length(winlog.event_data.AttributeValue) > 15 and
-winlog.event_data.AttributeValue regex~ "[0-9]{15}([1-9a-f]).*"
-----------------------------------
 
-==== Threat mapping
+*Setup*
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Persistence
-** ID: TA0003
-** Reference URL: https://attack.mitre.org/tactics/TA0003/
+The 'Audit Directory Service Changes' logging policy must be configured for (Success).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Changes (Success)
+```
 
-[[adminsdholder-sdprop-exclusion-added-history]]
-==== Rule version history
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 101 (8.5.0 release)::
-* Formatting only
+==== Rule query
 
-Version 4 (8.4.0 release)::
-* Formatting only
 
-Version 2 (8.3.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-any where event.action == "Directory Service Changes" and event.code
-== "5136" and length(winlog.event_data.AttributeValue) > 15 and
-winlog.event_data.AttributeValue regex~ "[0-9]{15}([1-9a-f]).*"
+any where event.action == "Directory Service Changes" and
+  event.code == "5136" and
+  winlog.event_data.AttributeLDAPDisplayName : "dSHeuristics" and
+  length(winlog.event_data.AttributeValue) > 15 and
+  winlog.event_data.AttributeValue regex~ "[0-9]{15}([1-9a-f]).*"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Domain Accounts
+** ID: T1078.002
+** Reference URL: https://attack.mitre.org/techniques/T1078/002/
+* Technique:
+** Name: Account Manipulation
+** ID: T1098
+** Reference URL: https://attack.mitre.org/techniques/T1098/
diff --git a/docs/detections/prebuilt-rules/rule-details/adobe-hijack-persistence.asciidoc b/docs/detections/prebuilt-rules/rule-details/adobe-hijack-persistence.asciidoc
index 398558d659..b84db7c4b0 100644
--- a/docs/detections/prebuilt-rules/rule-details/adobe-hijack-persistence.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/adobe-hijack-persistence.asciidoc
@@ -5,89 +5,95 @@ Detects writing executable files that will be automatically launched by Adobe on
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://twitter.com/pabraeken/status/997997818362155008
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
-
-*Version*: 102 (<<adobe-hijack-persistence-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Adobe Hijack Persistence
+*Triage and analysis*
+
+
 
-Attackers can replace the `RdrCEF.exe` executable with their own to maintain their access, which will be launched
-whenever Adobe Acrobat Reader is executed.
+*Investigating Adobe Hijack Persistence*
+
+
+Attackers can replace the `RdrCEF.exe` executable with their own to maintain their access, which will be launched whenever Adobe Acrobat Reader is executed.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -95,33 +101,39 @@ for prevalence, whether they are located in expected locations, and if they are
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type == "creation" and file.path : ("?:\\Program
-Files (x86)\\Adobe\\Acrobat Reader DC\\Reader\\AcroCEF\\RdrCEF.exe",
-"?:\\Program Files\\Adobe\\Acrobat Reader
-DC\\Reader\\AcroCEF\\RdrCEF.exe") and not process.name :
-"msiexec.exe"
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and
+  file.path : ("?:\\Program Files (x86)\\Adobe\\Acrobat Reader DC\\Reader\\AcroCEF\\RdrCEF.exe",
+               "?:\\Program Files\\Adobe\\Acrobat Reader DC\\Reader\\AcroCEF\\RdrCEF.exe") and
+  not process.name : "msiexec.exe"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -133,70 +145,11 @@ DC\\Reader\\AcroCEF\\RdrCEF.exe") and not process.name :
 ** Name: Hijack Execution Flow
 ** ID: T1574
 ** Reference URL: https://attack.mitre.org/techniques/T1574/
-
-[[adobe-hijack-persistence-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 13 (8.4.0 release)::
-* Formatting only
-
-Version 11 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and event.type:creation and file.path:("C:\Program
-Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroCEF\RdrCEF.exe" or
-"C:\Program Files\Adobe\Acrobat Reader DC\Reader\AcroCEF\RdrCEF.exe")
-and not process.name:msiexec.exe
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file.path:("C:\Program Files (x86)\Adobe\Acrobat Reader
-DC\Reader\AcroCEF\RdrCEF.exe" or "C:\Program Files\Adobe\Acrobat
-Reader DC\Reader\AcroCEF\RdrCEF.exe") and event.action:"File created
-(rule: FileCreate)" and not process.name:msiexec.exe
-----------------------------------
-
-Version 2 (7.6.2 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file.path:("C:\Program Files (x86)\Adobe\Acrobat Reader
-DC\Reader\AcroCEF\RdrCEF.exe" or "C:\Program Files\Adobe\Acrobat
-Reader DC\Reader\AcroCEF\RdrCEF.exe") and event.action:"File created
-(rule: FileCreate)" and not process.name:msiexeec.exe
-----------------------------------
-
+* Sub-technique:
+** Name: Services File Permissions Weakness
+** ID: T1574.010
+** Reference URL: https://attack.mitre.org/techniques/T1574/010/
+* Technique:
+** Name: Compromise Client Software Binary
+** ID: T1554
+** Reference URL: https://attack.mitre.org/techniques/T1554/
diff --git a/docs/detections/prebuilt-rules/rule-details/adversary-behavior-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/adversary-behavior-detected-elastic-endgame.asciidoc
index 707b4b560c..ec02014840 100644
--- a/docs/detections/prebuilt-rules/rule-details/adversary-behavior-detected-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/adversary-behavior-detected-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame detected an Adversary Behavior. Click the Elastic Endgame icon i
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,75 +13,47 @@ Elastic Endgame detected an Adversary Behavior. Click the Elastic Endgame icon i
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 101 (<<adversary-behavior-detected-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
 
+==== Setup
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-(event.action:behavior_protection_event or
-endgame.event_subtype_full:behavior_protection_event)
-----------------------------------
 
 
-[[adversary-behavior-detected-elastic-endgame-history]]
-==== Rule version history
+*Setup*
 
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-(event.action:rules_engine_event or
-endgame.event_subtype_full:rules_engine_event)
-----------------------------------
 
-Version 100 (8.5.0 release)::
-* Formatting only
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
 
-Version 8 (8.4.0 release)::
-* Formatting only
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
 
-Version 7 (8.0.0 release)::
-* Formatting only
+==== Rule query
 
-Version 6 (7.12.1 release)::
-* Formatting only
 
-Version 5 (7.12.0 release)::
-* Rule name changed from: Adversary Behavior - Detected - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Adversary Behavior - Detected - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Adversary Behavior - Detected - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:rules_engine_event
-----------------------------------
+event.kind:alert and event.module:endgame and (event.action:behavior_protection_event or endgame.event_subtype_full:behavior_protection_event)
 
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/agent-spoofing-mismatched-agent-id.asciidoc b/docs/detections/prebuilt-rules/rule-details/agent-spoofing-mismatched-agent-id.asciidoc
index 8ebe94d572..773f386d75 100644
--- a/docs/detections/prebuilt-rules/rule-details/agent-spoofing-mismatched-agent-id.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/agent-spoofing-mismatched-agent-id.asciidoc
@@ -5,7 +5,7 @@ Detects events that have a mismatch on the expected event agent ID. The status "
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-*
 * metrics-*
@@ -15,41 +15,36 @@ Detects events that have a mismatch on the expected event agent ID. The status "
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<agent-spoofing-mismatched-agent-id-history, version history>>)
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 101
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-This is meant to run only on datasources using Elastic Agent 7.14+ since versions prior to that will be missing the necessary field, resulting in false positives.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.agent_id_status:agent_id_mismatch
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -61,19 +56,3 @@ event.agent_id_status:agent_id_mismatch
 ** Name: Masquerading
 ** ID: T1036
 ** Reference URL: https://attack.mitre.org/techniques/T1036/
-
-[[agent-spoofing-mismatched-agent-id-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/agent-spoofing-multiple-hosts-using-same-agent.asciidoc b/docs/detections/prebuilt-rules/rule-details/agent-spoofing-multiple-hosts-using-same-agent.asciidoc
index d2658fbb4a..519b95923d 100644
--- a/docs/detections/prebuilt-rules/rule-details/agent-spoofing-multiple-hosts-using-same-agent.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/agent-spoofing-multiple-hosts-using-same-agent.asciidoc
@@ -5,7 +5,7 @@ Detects when multiple hosts are using the same agent ID. This could occur in the
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-*
 * metrics-*
@@ -15,41 +15,36 @@ Detects when multiple hosts are using the same agent ID. This could occur in the
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<agent-spoofing-multiple-hosts-using-same-agent-history, version history>>)
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 101
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-This is meant to run only on datasources using Elastic Agent 7.14+ since versions prior to that will be missing the necessary field, resulting in false positives.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.agent_id_status:*
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -61,16 +56,3 @@ event.agent_id_status:*
 ** Name: Masquerading
 ** ID: T1036
 ** Reference URL: https://attack.mitre.org/techniques/T1036/
-
-[[agent-spoofing-multiple-hosts-using-same-agent-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/alternate-data-stream-creation-execution-at-volume-root-directory.asciidoc b/docs/detections/prebuilt-rules/rule-details/alternate-data-stream-creation-execution-at-volume-root-directory.asciidoc
new file mode 100644
index 0000000000..a38f2c4156
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/alternate-data-stream-creation-execution-at-volume-root-directory.asciidoc
@@ -0,0 +1,73 @@
+[[alternate-data-stream-creation-execution-at-volume-root-directory]]
+=== Alternate Data Stream Creation/Execution at Volume Root Directory
+
+Identifies the creation of an Alternate Data Stream (ADS) at a volume root directory, which can indicate the attempt to hide tools and malware, as ADSs created in this directory are not displayed by system utilities.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.crowdstrike.com/blog/anatomy-of-alpha-spider-ransomware/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+any where host.os.type == "windows" and event.category in ("file", "process") and 
+  (
+    (event.type == "creation" and file.path regex~ """[A-Z]:\\:.+""") or 
+    (event.type == "start" and process.executable regex~ """[A-Z]:\\:.+""")
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hide Artifacts
+** ID: T1564
+** Reference URL: https://attack.mitre.org/techniques/T1564/
+* Sub-technique:
+** Name: NTFS File Attributes
+** ID: T1564.004
+** Reference URL: https://attack.mitre.org/techniques/T1564/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/anomalous-linux-compiler-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/anomalous-linux-compiler-activity.asciidoc
index 15b8f1d04c..0dd52130b1 100644
--- a/docs/detections/prebuilt-rules/rule-details/anomalous-linux-compiler-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/anomalous-linux-compiler-activity.asciidoc
@@ -5,44 +5,37 @@ Looks for compiler activity by a user context which does not normally run compil
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_linux_rare_user_compiler
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
-* Resource Development
+*Tags*: 
 
-*Version*: 100 (<<anomalous-linux-compiler-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Resource Development
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Uncommon compiler activity can be due to an engineer running a local build on a production or staging instance in the course of troubleshooting or fixing a software issue.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -54,22 +47,7 @@ Uncommon compiler activity can be due to an engineer running a local build on a
 ** Name: Obtain Capabilities
 ** ID: T1588
 ** Reference URL: https://attack.mitre.org/techniques/T1588/
-
-[[anomalous-linux-compiler-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (7.15.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Malware
+** ID: T1588.001
+** Reference URL: https://attack.mitre.org/techniques/T1588/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/anomalous-process-for-a-linux-population.asciidoc b/docs/detections/prebuilt-rules/rule-details/anomalous-process-for-a-linux-population.asciidoc
index f6f378cd80..8799f4758f 100644
--- a/docs/detections/prebuilt-rules/rule-details/anomalous-process-for-a-linux-population.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/anomalous-process-for-a-linux-population.asciidoc
@@ -5,102 +5,103 @@ Searches for rare processes running on multiple Linux hosts in an entire fleet o
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_linux_anomalous_process_all_hosts
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Persistence
+* Resources: Investigation Guide
+
+*Version*: 104
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
-* Persistence
 
-*Version*: 100 (<<anomalous-process-for-a-linux-population-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.7.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-A newly installed program or one that runs rarely as part of a monthly or quarterly workflow could trigger this alert.
 
-==== Investigation guide
 
+*Investigating Anomalous Process For a Linux Population*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating an Unusual Linux Process
-Detection alerts from this rule indicate the presence of a Linux process that is rare and unusual for all of the monitored Linux hosts for which Auditbeat data is available. Here are some possible avenues of investigation:
-- Consider the user as identified by the username field. Is this program part of an expected workflow for the user who ran this program on this host?
-- Examine the history of execution. If this process only manifested recently, it might be part of a new software package. If it has a consistent cadence (for example if it runs monthly or quarterly), it might be part of a monthly or quarterly business process.
-- Examine the process arguments, title and working directory. These may provide indications as to the source of the program or the nature of the tasks it is performing.
-----------------------------------
+Searching for abnormal Linux processes is a good methodology to find potentially malicious activity within a network. Understanding what is commonly run within an environment and developing baselines for legitimate activity can help uncover potential malware and suspicious behaviors.
 
-==== Threat mapping
+This rule uses a machine learning job to detect a Linux process that is rare and unusual for all of the monitored Linux hosts in your fleet.
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Persistence
-** ID: TA0003
-** Reference URL: https://attack.mitre.org/tactics/TA0003/
-* Technique:
-** Name: Create or Modify System Process
-** ID: T1543
-** Reference URL: https://attack.mitre.org/techniques/T1543/
+*Possible investigation steps*
+
 
-[[anomalous-process-for-a-linux-population-history]]
-==== Rule version history
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, and whether they are located in expected locations.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Consider the user as identified by the `user.name` field. Is this program part of an expected workflow for the user who ran this program on this host?
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Validate if the activity has a consistent cadence (for example, if it runs monthly or quarterly), as it could be part of a monthly or quarterly business process.
+- Examine the arguments and working directory of the process. These may provide indications as to the source of the program or the nature of the tasks it is performing.
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 9 (8.4.0 release)::
-* Formatting only
+*False Positive Analysis*
 
-Version 8 (8.3.0 release)::
-* Formatting only
 
-Version 7 (7.15.0 release)::
-* Formatting only
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
 
-Version 6 (7.14.0 release)::
-* Formatting only
 
-Version 5 (7.13.0 release)::
-* Formatting only
+*Response and Remediation*
 
-Version 4 (7.12.0 release)::
-* Formatting only
 
-Version 3 (7.10.0 release)::
-* Formatting only
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that   attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 2 (7.9.0 release)::
-* Formatting only
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/anomalous-process-for-a-windows-population.asciidoc b/docs/detections/prebuilt-rules/rule-details/anomalous-process-for-a-windows-population.asciidoc
index 48f087013f..8c0a537aa3 100644
--- a/docs/detections/prebuilt-rules/rule-details/anomalous-process-for-a-windows-population.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/anomalous-process-for-a-windows-population.asciidoc
@@ -5,105 +5,137 @@ Searches for rare processes running on multiple hosts in an entire fleet or netw
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_windows_anomalous_process_all_hosts
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Persistence
+* Tactic: Execution
+
+*Version*: 105
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
-* Persistence
 
-*Version*: 100 (<<anomalous-process-for-a-windows-population-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.7.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-A newly installed program or one that runs rarely as part of a monthly or quarterly workflow could trigger this alert.
 
-==== Investigation guide
 
+*Investigating Anomalous Process For a Windows Population*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating an Unusual Windows Process
-Detection alerts from this rule indicate the presence of a Windows process that is rare and unusual for all of the Windows hosts for which Winlogbeat data is available. Here are some possible avenues of investigation:
-- Consider the user as identified by the username field. Is this program part of an expected workflow for the user who ran this program on this host?
-- Examine the history of execution. If this process only manifested recently, it might be part of a new software package. If it has a consistent cadence (for example if it runs monthly or quarterly), it might be part of a monthly or quarterly business process.
-- Examine the process metadata like the values of the Company, Description and Product fields which may indicate whether the program is associated with an expected software vendor or package.
-- Examine arguments and working directory. These may provide indications as to the source of the program or the nature of the tasks it is performing.
-- Consider the same for the parent process. If the parent process is a legitimate system utility or service, this could be related to software updates or system management. If the parent process is something user-facing like an Office application, this process could be more suspicious.
-- If you have file hash values in the event data, and you suspect malware, you can optionally run a search for the file hash to see if the file is identified as malware by anti-malware tools. 
-----------------------------------
+Searching for abnormal Windows processes is a good methodology to find potentially malicious activity within a network. Understanding what is commonly run within an environment and developing baselines for legitimate activity can help uncover potential malware and suspicious behaviors.
 
-==== Threat mapping
+This rule uses a machine learning job to detect a Windows process that is rare and unusual for all of the monitored Windows hosts in your environment.
 
-*Framework*: MITRE ATT&CK^TM^
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-* Tactic:
-** Name: Persistence
-** ID: TA0003
-** Reference URL: https://attack.mitre.org/tactics/TA0003/
-* Technique:
-** Name: Create or Modify System Process
-** ID: T1543
-** Reference URL: https://attack.mitre.org/techniques/T1543/
 
-[[anomalous-process-for-a-windows-population-history]]
-==== Rule version history
+*Possible investigation steps*
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 9 (8.4.0 release)::
-* Formatting only
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - If the parent process is a legitimate system utility or service, this could be related to software updates or system management. If the parent process is something user-facing like an Office application, this process could be more suspicious.
+  - Investigate the process metadata — such as the digital signature, directory, etc. — to obtain more context that can indicate whether the executable is associated with an expected software vendor or package.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Consider the user as identified by the `user.name` field. Is this program part of an expected workflow for the user who ran this program on this host?
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Validate if the activity has a consistent cadence (for example, if it runs monthly or quarterly), as it could be part of a monthly or quarterly business process.
+- Examine the arguments and working directory of the process. These may provide indications as to the source of the program or the nature of the tasks it is performing.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSyste' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Retrieve Service Unisgned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-Version 8 (8.3.0 release)::
-* Formatting only
 
-Version 7 (7.15.0 release)::
-* Formatting only
+*False Positive Analysis*
 
-Version 6 (7.14.0 release)::
-* Formatting only
 
-Version 5 (7.13.0 release)::
-* Formatting only
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
 
-Version 4 (7.12.0 release)::
-* Formatting only
 
-Version 3 (7.10.0 release)::
-* Formatting only
+*Related Rules*
 
-Version 2 (7.9.0 release)::
-* Formatting only
 
+- Unusual Process For a Windows Host - 6d448b96-c922-4adb-b51c-b767f1ea5b76
+- Unusual Windows Path Activity - 445a342e-03fb-42d0-8656-0367eb2dead5
+- Unusual Windows Process Calling the Metadata Service - abae61a8-c560-4dbd-acca-1e1438bff36b
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: User Execution
+** ID: T1204
+** Reference URL: https://attack.mitre.org/techniques/T1204/
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/anomalous-windows-process-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/anomalous-windows-process-creation.asciidoc
index c8cabd8853..9fc581fe54 100644
--- a/docs/detections/prebuilt-rules/rule-details/anomalous-windows-process-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/anomalous-windows-process-creation.asciidoc
@@ -5,81 +5,125 @@ Identifies unusual parent-child process relationships that can indicate malware
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_windows_anomalous_process_creation
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Persistence
+* Resources: Investigation Guide
+
+*Version*: 105
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
-* Persistence
 
-*Version*: 100 (<<anomalous-windows-process-creation-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.7.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Users running scripts in the course of technical support operations of software upgrades could trigger this alert. A newly installed program or one that runs rarely as part of a monthly or quarterly workflow could trigger this alert.
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Persistence
-** ID: TA0003
-** Reference URL: https://attack.mitre.org/tactics/TA0003/
-* Technique:
-** Name: Create or Modify System Process
-** ID: T1543
-** Reference URL: https://attack.mitre.org/techniques/T1543/
+*Investigating Anomalous Windows Process Creation*
+
+
+Searching for abnormal Windows processes is a good methodology to find potentially malicious activity within a network. Understanding what is commonly run within an environment and developing baselines for legitimate activity can help uncover potential malware and suspicious behaviors.
+
+This rule uses a machine learning job to detect an anomalous Windows process with an unusual parent-child relationship, which could indicate malware execution or persistence activities on the host machine.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-[[anomalous-windows-process-creation-history]]
-==== Rule version history
 
-Version 100 (8.5.0 release)::
-* Formatting only
+*Possible investigation steps*
 
-Version 7 (8.4.0 release)::
-* Formatting only
 
-Version 6 (8.3.0 release)::
-* Formatting only
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - If the parent process is a legitimate system utility or service, this could be related to software updates or system management. If the parent process is something user-facing like an Office application, this process could be more suspicious.
+  - Investigate the process metadata — such as the digital signature, directory, etc. — to obtain more context that can indicate whether the executable is associated with an expected software vendor or package.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Consider the user as identified by the `user.name` field. Is this program part of an expected workflow for the user who ran this program on this host?
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Validate if the activity has a consistent cadence (for example, if it runs monthly or quarterly), as it could be part of a monthly or quarterly business process.
+- Examine the arguments and working directory of the process. These may provide indications as to the source of the program or the nature of the tasks it is performing.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Retrieve Service Unisgned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-Version 5 (7.14.0 release)::
-* Formatting only
 
-Version 4 (7.12.0 release)::
-* Formatting only
+*False Positive Analysis*
 
-Version 3 (7.10.0 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Formatting only
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
 
+
+*Related Rules*
+
+
+- Unusual Process For a Windows Host - 6d448b96-c922-4adb-b51c-b767f1ea5b76
+- Unusual Windows Path Activity - 445a342e-03fb-42d0-8656-0367eb2dead5
+- Unusual Windows Process Calling the Metadata Service - abae61a8-c560-4dbd-acca-1e1438bff36b
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
diff --git a/docs/detections/prebuilt-rules/rule-details/apple-script-execution-followed-by-network-connection.asciidoc b/docs/detections/prebuilt-rules/rule-details/apple-script-execution-followed-by-network-connection.asciidoc
index 5150f20762..31c33c4b3b 100644
--- a/docs/detections/prebuilt-rules/rule-details/apple-script-execution-followed-by-network-connection.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/apple-script-execution-followed-by-network-connection.asciidoc
@@ -5,64 +5,95 @@ Detects execution via the Apple script interpreter (osascript) followed by a net
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.apple.com/library/archive/documentation/LanguagesUtilities/Conceptual/MacAutomationScriptingGuide/index.html
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Command and Control
-* Execution
 
-*Version*: 100 (<<apple-script-execution-followed-by-network-connection-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.11.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=30s [process
-where event.type == "start" and process.name == "osascript"] [network
-where event.type != "end" and process.name == "osascript" and
-destination.ip != "::1" and not cidrmatch(destination.ip,
-"10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12",
-"192.0.0.0/24", "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32",
-"192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
-"192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16",
-"192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10", "192.175.48.0/24",
-"198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4",
-"::1", "FE80::/10", "FF00::/8")]
+[source, js]
 ----------------------------------
+sequence by host.id, process.entity_id with maxspan=30s
+ [process where host.os.type == "macos" and event.type == "start" and process.name == "osascript"]
+ [network where host.os.type == "macos" and event.type != "end" and process.name == "osascript" and destination.ip != "::1" and
+  not cidrmatch(destination.ip,
+    "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.0.0.0/29", "192.0.0.8/32",
+    "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24", "192.31.196.0/24",
+    "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10", "192.175.48.0/24",
+    "198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10", "FF00::/8")]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,8 +105,10 @@ destination.ip != "::1" and not cidrmatch(destination.ip,
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-
+* Sub-technique:
+** Name: AppleScript
+** ID: T1059.002
+** Reference URL: https://attack.mitre.org/techniques/T1059/002/
 * Tactic:
 ** Name: Command and Control
 ** ID: TA0011
@@ -84,31 +117,3 @@ destination.ip != "::1" and not cidrmatch(destination.ip,
 ** Name: Ingress Tool Transfer
 ** ID: T1105
 ** Reference URL: https://attack.mitre.org/techniques/T1105/
-
-[[apple-script-execution-followed-by-network-connection-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=30s [process
-where event.type == "start" and process.name == "osascript"] [network
-where event.type != "end" and process.name == "osascript" and
-destination.ip != "::1" and not cidrmatch(destination.ip,
-"10.0.0.0/8", "172.16.0.0/12",
-"192.168.0.0/16", "127.0.0.0/8",
-"169.254.0.0/16", "224.0.0.0/4",
-"FE80::/10", "FF00::/8") ]
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/apple-scripting-execution-with-administrator-privileges.asciidoc b/docs/detections/prebuilt-rules/rule-details/apple-scripting-execution-with-administrator-privileges.asciidoc
index 5be1d5e28c..b8338409c5 100644
--- a/docs/detections/prebuilt-rules/rule-details/apple-scripting-execution-with-administrator-privileges.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/apple-scripting-execution-with-administrator-privileges.asciidoc
@@ -5,64 +5,91 @@ Identifies execution of the Apple script interpreter (osascript) without a passw
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://discussions.apple.com/thread/2266150
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 207
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Execution
-* Privilege Escalation
 
-*Version*: 100 (<<apple-scripting-execution-with-administrator-privileges-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This rule requires data coming in from Elastic Defend.
 
-----------------------------------
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "osascript" and process.command_line :
-"osascript*with administrator privileges"
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and process.name : "osascript" and
+  process.command_line : "osascript*with administrator privileges" and
+  not process.parent.name : "Electron" and
+  not process.Ext.effective_parent.executable : ("/Applications/Visual Studio Code.app/Contents/MacOS/Electron",
+                                                 "/Applications/OpenVPN Connect/Uninstall OpenVPN Connect.app/Contents/MacOS/uninstaller")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,8 +101,6 @@ process.name : "osascript" and process.command_line :
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -84,16 +109,3 @@ process.name : "osascript" and process.command_line :
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[apple-scripting-execution-with-administrator-privileges-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/application-added-to-google-workspace-domain.asciidoc b/docs/detections/prebuilt-rules/rule-details/application-added-to-google-workspace-domain.asciidoc
index 7896ab45cf..42ea5614e7 100644
--- a/docs/detections/prebuilt-rules/rule-details/application-added-to-google-workspace-domain.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/application-added-to-google-workspace-domain.asciidoc
@@ -5,7 +5,7 @@ Detects when a Google marketplace application is added to the Google Workspace d
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,46 +14,94 @@ Detects when a Google marketplace application is added to the Google Workspace d
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/6328701?hl=en#
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Configuration Audit
+* Tactic: Persistence
+* Resources: Investigation Guide
+
+*Version*: 205
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Persistence
 
-*Version*: 101 (<<application-added-to-google-workspace-domain-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Applications can be added to a Google Workspace domain by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
-==== Investigation guide
 
+*Investigating Application Added to Google Workspace Domain*
+
+
+Google Workspace Marketplace is an online store for free and paid web applications that work with Google Workspace services and third-party software. Listed applications are based on Google APIs or on Google Apps Script and created by both Google and third-party developers.
+
+Marketplace applications require access to specific Google Workspace resources. Applications can be installed by individual users, if they have permission, or can be installed for an entire Google Workspace domain by administrators. Consent screens typically display what permissions and privileges the application requires during installation. As a result, malicious Marketplace applications may require more permissions than necessary or have malicious intent.
+
+Google clearly states that they are not responsible for any product on the Marketplace that originates from a source other than Google.
+
+This rule checks for applications that were manually added to the Marketplace by a Google Workspace account.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
+- This rule relies on data from `google_workspace.admin`, thus indicating the associated user has administrative privileges to the Marketplace.
+- With access to the Google Workspace admin console, visit the `Security > Investigation tool` with filters for the user email and event is `Assign Role` or `Update Role` to determine if new cloud roles were recently updated.
+- With the user account, review other potentially related events within the last 48 hours.
+- Re-assess the permissions and reviews of the Marketplace applications to determine if they violate organizational policies or introduce unexpected risks.
+- With access to the Google Workspace admin console, determine if the application was installed domain-wide or individually by visiting `Apps > Google Workspace Marketplace Apps`.
+
+
+*False positive analysis*
+
+
+- Google Workspace administrators might intentionally remove an application from the blocklist due to a re-assessment or a domain-wide required need for the application.
+- Identify the user account associated with this action and assess their administrative privileges with Google Workspace Marketplace.
+- Contact the user to verify that they intentionally removed the application from the blocklist and their reasoning.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -61,19 +109,20 @@ Applications can be added to a Google Workspace domain by system administrators.
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
 
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:google_workspace.admin and event.provider:admin and
-event.category:iam and event.action:ADD_APPLICATION
+[source, js]
 ----------------------------------
+event.dataset:google_workspace.admin and event.provider:admin and event.category:iam and event.action:ADD_APPLICATION
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,44 +130,3 @@ event.category:iam and event.action:ADD_APPLICATION
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-[[application-added-to-google-workspace-domain-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 14 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:ADD_APPLICATION
-----------------------------------
-
-Version 5 (7.15.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/application-removed-from-blocklist-in-google-workspace.asciidoc b/docs/detections/prebuilt-rules/rule-details/application-removed-from-blocklist-in-google-workspace.asciidoc
index 9557092ec7..b7c8fbac35 100644
--- a/docs/detections/prebuilt-rules/rule-details/application-removed-from-blocklist-in-google-workspace.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/application-removed-from-blocklist-in-google-workspace.asciidoc
@@ -5,7 +5,7 @@ Google Workspace administrators may be aware of malicious applications within th
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,46 +14,94 @@ Google Workspace administrators may be aware of malicious applications within th
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/6328701?hl=en#
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Configuration Audit
+* Resources: Investigation Guide
+* Tactic: Defense Evasion
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Impair Defenses
 
-*Version*: 2 (<<application-removed-from-blocklist-in-google-workspace-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Last modified ({stack} release)*: 8.6.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Triage and analysis*
 
-==== Potential false positives
 
-Applications can be added and removed from blocklists by Google Workspace administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
-==== Investigation guide
+*Investigating Application Removed from Blocklist in Google Workspace*
 
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
+Google Workspace Marketplace is an online store for free and paid web applications that work with Google Workspace services and third-party software. Listed applications are based on Google APIs or Google Apps Script and created by both Google and third-party developers.
+
+Marketplace applications require access to specific Google Workspace resources. Individual users with the appropriate permissions can install applications in their Google Workspace domain. Administrators have additional permissions that allow them to install applications for an entire Google Workspace domain. Consent screens typically display permissions and privileges the user needs to install an application. As a result, malicious Marketplace applications may require more permissions than necessary or have malicious intent.
+
+Google clearly states that they are not responsible for any Marketplace product that originates from a source that isn't Google.
+
+This rule identifies a Marketplace blocklist update that consists of a Google Workspace account with administrative privileges manually removing a previously blocked application.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
+- This rule relies on data from `google_workspace.admin`, thus indicating the associated user has administrative privileges to the Marketplace.
+- With access to the Google Workspace admin console, visit the `Security > Investigation` tool with filters for the user email and event is `Assign Role` or `Update Role` to determine if new cloud roles were recently updated.
+- After identifying the involved user account, review other potentially related events within the last 48 hours.
+- Re-assess the permissions and reviews of the Marketplace applications to determine if they violate organizational policies or introduce unexpected risks.
+- With access to the Google Workspace admin console, determine if the application was installed domain-wide or individually by visiting `Apps > Google Workspace Marketplace Apps`.
+
+
+*False positive analysis*
+
+
+- Google Workspace administrators might intentionally remove an application from the blocklist due to a re-assessment or a domain-wide required need for the application.
+- Identify the user account associated with this action and assess their administrative privileges with Google Workspace Marketplace.
+- Contact the user to verify that they intentionally removed the application from the blocklist and their reasoning.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
+
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -61,22 +109,23 @@ Applications can be added and removed from blocklists by Google Workspace admini
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
+
+==== Setup
 
 
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:"google_workspace.admin" and event.category:"iam" and
-event.type:"change" and event.action:"CHANGE_APPLICATION_SETTING"
-and google_workspace.admin.application.name:"Google Workspace
-Marketplace" and google_workspace.admin.old_value: *allowed*false*
-and google_workspace.admin.new_value: *allowed*true*
+[source, js]
 ----------------------------------
+event.dataset:"google_workspace.admin" and event.category:"iam" and event.type:"change"  and
+  event.action:"CHANGE_APPLICATION_SETTING" and
+  google_workspace.admin.application.name:"Google Workspace Marketplace" and
+  google_workspace.admin.old_value: *allowed*false* and google_workspace.admin.new_value: *allowed*true*
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -88,10 +137,7 @@ and google_workspace.admin.new_value: *allowed*true*
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[application-removed-from-blocklist-in-google-workspace-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/archive-file-with-unusual-extension.asciidoc b/docs/detections/prebuilt-rules/rule-details/archive-file-with-unusual-extension.asciidoc
new file mode 100644
index 0000000000..e3cb6b1fcd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/archive-file-with-unusual-extension.asciidoc
@@ -0,0 +1,83 @@
+[[archive-file-with-unusual-extension]]
+=== Archive File with Unusual Extension
+
+Identifies the creation of an archive file with an unusual extension. Attackers may attempt to evade detection by masquerading files using the file extension values used by image, audio, or document file types.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.action != "deletion" and
+
+  /* common archive file headers - Rar, 7z, GZIP, MSCF, XZ, ZIP */
+  file.Ext.header_bytes : ("52617221*", "377ABCAF271C*", "1F8B*", "4d534346*", "FD377A585A00*", "504B0304*", "504B0708*") and
+
+  (
+    /* common image file extensions */
+    file.extension : ("jpg", "jpeg", "emf", "tiff", "gif", "png", "bmp", "ico", "fpx", "eps", "inf") or
+
+    /* common audio and video file extensions */
+    file.extension : ("mp3", "wav", "avi", "mpeg", "flv", "wma", "wmv", "mov", "mp4", "3gp") or
+
+    /* common document file extensions */
+    (file.extension : ("doc", "docx", "rtf", "ppt", "pptx", "xls", "xlsx") and
+
+    /* exclude ZIP file header values for OPENXML documents */
+    not file.Ext.header_bytes : ("504B0304*", "504B0708*"))
+  ) and
+
+  not (process.executable : "?:\\Windows\\System32\\inetsrv\\w3wp.exe" and file.path : "?:\\inetpub\\temp\\IIS Temporary Compressed Files\\*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Masquerade File Type
+** ID: T1036.008
+** Reference URL: https://attack.mitre.org/techniques/T1036/008/
diff --git a/docs/detections/prebuilt-rules/rule-details/at-exe-command-lateral-movement.asciidoc b/docs/detections/prebuilt-rules/rule-details/at-exe-command-lateral-movement.asciidoc
new file mode 100644
index 0000000000..13083badb3
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/at-exe-command-lateral-movement.asciidoc
@@ -0,0 +1,81 @@
+[[at-exe-command-lateral-movement]]
+=== At.exe Command Lateral Movement
+
+Identifies use of at.exe to interact with the task scheduler on remote hosts. Remote task creations, modifications or execution could be indicative of adversary lateral movement.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* winlogbeat-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+* Rule Type: BBR
+* Data Source: Elastic Endgame
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.name : "at.exe" and process.args : "\\\\*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: At
+** ID: T1053.002
+** Reference URL: https://attack.mitre.org/techniques/T1053/002/
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-clear-kernel-ring-buffer.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-clear-kernel-ring-buffer.asciidoc
new file mode 100644
index 0000000000..a14b6de570
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-clear-kernel-ring-buffer.asciidoc
@@ -0,0 +1,114 @@
+[[attempt-to-clear-kernel-ring-buffer]]
+=== Attempt to Clear Kernel Ring Buffer
+
+Monitors for the deletion of the kernel ring buffer events through dmesg. Attackers may clear kernel ring buffer events to evade detection after installing a Linux kernel module (LKM).
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "dmesg" and process.args == "-c"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
+* Technique:
+** Name: Indicator Removal
+** ID: T1070
+** Reference URL: https://attack.mitre.org/techniques/T1070/
+* Sub-technique:
+** Name: Clear Linux or Mac System Logs
+** ID: T1070.002
+** Reference URL: https://attack.mitre.org/techniques/T1070/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-create-okta-api-token.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-create-okta-api-token.asciidoc
index 868dc54142..4ac3045c47 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-create-okta-api-token.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-create-okta-api-token.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to create an Okta API token. An adversary may create an Okta AP
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,59 +14,51 @@ Detects attempts to create an Okta API token. An adversary may create an Okta AP
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 102 (<<attempt-to-create-okta-api-token-history, version history>>)
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 205
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-If the behavior of creating Okta API tokens is expected, consider adding exceptions to this rule to filter false positives.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:okta.system and event.action:system.api_token.create
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,37 +70,3 @@ event.dataset:okta.system and event.action:system.api_token.create
 ** Name: Create Account
 ** ID: T1136
 ** Reference URL: https://attack.mitre.org/techniques/T1136/
-
-[[attempt-to-create-okta-api-token-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:system.api_token.create
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-application.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-application.asciidoc
index fbb83637ee..d5693fd9b8 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-application.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-application.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to deactivate an Okta application. An adversary may attempt to
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,62 +14,87 @@ Detects attempts to deactivate an Okta application. An adversary may attempt to
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Apps.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Impact
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-* Impact
 
-*Version*: 102 (<<attempt-to-deactivate-an-okta-application-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Consider adding exceptions to this rule to filter false positives if your organization's Okta applications are regularly deactivated and the behavior is expected.
 
-==== Investigation guide
 
+*Investigating Attempt to Deactivate an Okta Application*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+This rule detects attempts to deactivate an Okta application. Unauthorized deactivation could lead to disruption of services and pose a significant risk to the organization.
+
+
+*Possible investigation steps:*
+
+- Identify the actor associated with the deactivation attempt by examining the `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, and `okta.actor.display_name` fields.
+- Determine the client used by the actor. Review the `okta.client.ip`, `okta.client.user_agent.raw_user_agent`, `okta.client.zone`, `okta.client.device`, and `okta.client.id` fields.
+- If the client is a device, check the `okta.device.id`, `okta.device.name`, `okta.device.os_platform`, `okta.device.os_version`, and `okta.device.managed` fields.
+- Understand the context of the event from the `okta.debug_context.debug_data` and `okta.authentication_context` fields.
+- Check the `okta.outcome.result` and `okta.outcome.reason` fields to see if the attempt was successful or failed.
+- Review the past activities of the actor involved in this action by checking their previous actions logged in the `okta.target` field.
+- Analyze the `okta.transaction.id` and `okta.transaction.type` fields to understand the context of the transaction.
+- Evaluate the actions that happened just before and after this event in the `okta.event_type` field to help understand the full context of the activity.
+
+
+*False positive analysis:*
+
+- It might be a false positive if the action was part of a planned activity, performed by an authorized person, or if the `okta.outcome.result` field shows a failure.
+- An unsuccessful attempt might also indicate an authorized user having trouble rather than a malicious activity.
 
 
+*Response and remediation:*
+
+- If unauthorized deactivation attempts are confirmed, initiate the incident response process.
+- Block the IP address or device used in the attempts if they appear suspicious, using the data from the `okta.client.ip` and `okta.device.id` fields.
+- Reset the user's password and enforce MFA re-enrollment, if applicable.
+- Conduct a review of Okta policies and ensure they are in accordance with security best practices.
+- If the deactivated application was crucial for business operations, coordinate with the relevant team to reactivate it and minimize the impact.
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and
-event.action:application.lifecycle.deactivate
+[source, js]
 ----------------------------------
+event.dataset:okta.system and event.action:application.lifecycle.deactivate
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,25 +106,3 @@ event.action:application.lifecycle.deactivate
 ** Name: Service Stop
 ** ID: T1489
 ** Reference URL: https://attack.mitre.org/techniques/T1489/
-
-[[attempt-to-deactivate-an-okta-application-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-network-zone.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-network-zone.asciidoc
index 3e994e73fd..cd212f2a27 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-network-zone.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-network-zone.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to deactivate an Okta network zone. Okta network zones can be c
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,61 +14,90 @@ Detects attempts to deactivate an Okta network zone. Okta network zones can be c
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Security/network/network-zones.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Use Case: Network Security Monitoring
+* Tactic: Defense Evasion
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Network Security
-* Defense Evasion
 
-*Version*: 102 (<<attempt-to-deactivate-an-okta-network-zone-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Consider adding exceptions to this rule to filter false positives if your organization's Okta network zones are regularly modified.
 
-==== Investigation guide
 
+*Investigating Attempt to Deactivate an Okta Network Zone*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+The Okta network zones can be configured to restrict or limit access to a network based on IP addresses or geolocations. Deactivating a network zone in Okta may remove or weaken the security controls of an organization, which might be an indicator of an adversary's attempt to evade defenses.
+
+
+*Possible investigation steps*
+
+
+- Identify the actor related to the alert by reviewing the `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields.
+- Examine the `event.action` field to confirm the deactivation of a network zone.
+- Check the `okta.target.id`, `okta.target.type`, `okta.target.alternate_id`, or `okta.target.display_name` to identify the network zone that was deactivated.
+- Investigate the `event.time` field to understand when the event happened.
+- Review the actor's activities before and after the event to understand the context of this event.
+
+
+*False positive analysis*
+
+
+- Check the `okta.client.user_agent.raw_user_agent` field to understand the device and software used by the actor. If these match the actor's normal behavior, it might be a false positive.
+- Check if the actor is a known administrator or part of the IT team who might have a legitimate reason to deactivate a network zone.
+- Verify the actor's actions with any known planned changes or maintenance activities.
 
 
+*Response and remediation*
+
+
+- If unauthorized access or actions are confirmed, immediately lock the affected actor account and require a password change.
+- Re-enable the deactivated network zone if it was deactivated without authorization.
+- Review and update the privileges of the actor who initiated the deactivation.
+- Check the security policies and procedures to identify any gaps and update them as necessary.
+- Implement additional monitoring and logging of Okta events to improve visibility of user actions.
+- Communicate and train the employees about the importance of following proper procedures for modifying network zone settings.
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:okta.system and event.action:zone.deactivate
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,25 +109,7 @@ event.dataset:okta.system and event.action:zone.deactivate
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[attempt-to-deactivate-an-okta-network-zone-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-policy-rule.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-policy-rule.asciidoc
index 2152c437b9..65c554124b 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-policy-rule.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-policy-rule.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to deactivate a rule within an Okta policy. An adversary may at
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,102 +14,109 @@ Detects attempts to deactivate a rule within an Okta policy. An adversary may at
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Security/Security_Policies.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Tactic: Defense Evasion
+* Data Source: Okta
+
+*Version*: 207
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Defense Evasion
 
-*Version*: 102 (<<attempt-to-deactivate-an-okta-policy-rule-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Consider adding exceptions to this rule to filter false positives if Okta MFA rules are regularly deactivated in your organization.
 
-==== Investigation guide
 
+*Investigating Attempt to Deactivate an Okta Policy Rule*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+Identity and Access Management (IAM) systems like Okta serve as the first line of defense for an organization's network, and are often targeted by adversaries. By disabling security rules, adversaries can circumvent multi-factor authentication, access controls, or other protective measures enforced by these policies, enabling unauthorized access, privilege escalation, or other malicious activities.
 
+This rule detects attempts to deactivate a rule within an Okta policy, which could be indicative of an adversary's attempt to weaken an organization's security controls. A threat actor may do this to remove barriers to their activities or enable future attacks.
 
-==== Rule query
 
+*Possible investigation steps:*
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and event.action:policy.rule.deactivate
-----------------------------------
 
-==== Threat mapping
+- Identify the actor related to the alert by reviewing `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields in the alert.
+- Review the `okta.client.user_agent.raw_user_agent` field to understand the device and software used by the actor.
+- Examine the `okta.outcome.reason` field for additional context around the deactivation attempt.
+- Check the `okta.outcome.result` field to confirm the policy rule deactivation attempt.
+- Check if there are multiple policy rule deactivation attempts from the same actor or IP address (`okta.client.ip`).
+- Check for successful logins immediately following the policy rule deactivation attempt.
+- Verify whether the actor's activity aligns with typical behavior or if any unusual activity took place around the time of the deactivation attempt.
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Impair Defenses
-** ID: T1562
-** Reference URL: https://attack.mitre.org/techniques/T1562/
+*False positive analysis:*
+
+
+- Check if there were issues with the Okta system at the time of the deactivation attempt. This could indicate a system error rather than a genuine threat activity.
+- Check the geographical location (`okta.request.ip_chain.geographical_context`) and time of the deactivation attempt. If these match the actor's normal behavior, it might be a false positive.
+- Verify the actor's administrative rights to ensure they are correctly configured.
+
 
-[[attempt-to-deactivate-an-okta-policy-rule-history]]
-==== Rule version history
+*Response and remediation:*
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 100 (8.5.0 release)::
-* Formatting only
+- If unauthorized policy rule deactivation is confirmed, initiate the incident response process.
+- Immediately lock the affected actor account and require a password change.
+- Consider resetting MFA tokens for the actor and require re-enrollment.
+- Check if the compromised account was used to access or alter any sensitive data or systems.
+- If a specific deactivation technique was used, ensure your systems are patched or configured to prevent such techniques.
+- Assess the criticality of affected services and servers.
+- Work with your IT team to minimize the impact on users and maintain business continuity.
+- If multiple accounts are affected, consider a broader reset or audit of MFA tokens.
+- Implement security best practices https://www.okta.com/blog/2019/10/9-admin-best-practices-to-keep-your-org-secure/[outlined] by Okta.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 8 (8.4.0 release)::
-* Formatting only
+==== Setup
 
-Version 6 (7.13.0 release)::
-* Formatting only
 
-Version 5 (7.12.0 release)::
-* Formatting only
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
 
-Version 4 (7.11.2 release)::
-* Formatting only
 
-Version 3 (7.11.0 release)::
-* Rule name changed from: Attempt to Deactivate Okta MFA Rule
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:policy.rule.deactivate
+event.dataset:okta.system and event.action:policy.rule.deactivate
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-policy.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-policy.asciidoc
index b1710b9123..519d19c5f4 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-policy.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-deactivate-an-okta-policy.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to deactivate an Okta policy. An adversary may attempt to deact
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,102 +14,109 @@ Detects attempts to deactivate an Okta policy. An adversary may attempt to deact
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Security/Security_Policies.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Defense Evasion
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-* Defense Evasion
 
-*Version*: 102 (<<attempt-to-deactivate-an-okta-policy-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-If the behavior of deactivating Okta policies is expected, consider adding exceptions to this rule to filter false positives.
 
-==== Investigation guide
 
+*Investigating Attempt to Deactivate an Okta Policy*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+Okta policies define rules to manage user access to resources. Policies such as multi-factor authentication (MFA) are critical for enforcing strong security measures. Deactivation of an Okta policy could potentially weaken the security posture, allowing for unauthorized access or facilitating other malicious activities.
 
+This rule is designed to detect attempts to deactivate an Okta policy, which could be indicative of an adversary's attempt to weaken an organization's security controls. For example, disabling an MFA policy could lower the security of user authentication processes.
 
-==== Rule query
 
+*Possible investigation steps:*
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and event.action:policy.lifecycle.deactivate
-----------------------------------
 
-==== Threat mapping
+- Identify the actor related to the alert by reviewing `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields in the alert.
+- Review the `okta.client.user_agent.raw_user_agent` field to understand the device and software used by the actor.
+- Examine the `okta.outcome.reason` field for additional context around the deactivation attempt.
+- Check the `okta.outcome.result` field to confirm the policy deactivation attempt.
+- Check if there are multiple policy deactivation attempts from the same actor or IP address (`okta.client.ip`).
+- Check for successful logins immediately following the policy deactivation attempt.
+- Verify whether the actor's activity aligns with typical behavior or if any unusual activity took place around the time of the deactivation attempt.
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Impair Defenses
-** ID: T1562
-** Reference URL: https://attack.mitre.org/techniques/T1562/
+*False positive analysis:*
+
+
+- Check if there were issues with the Okta system at the time of the deactivation attempt. This could indicate a system error rather than a genuine threat activity.
+- Check the geographical location (`okta.request.ip_chain.geographical_context`) and time of the deactivation attempt. If these match the actor's normal behavior, it might be a false positive.
+- Verify the actor's administrative rights to ensure they are correctly configured.
+
 
-[[attempt-to-deactivate-an-okta-policy-history]]
-==== Rule version history
+*Response and remediation:*
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 100 (8.5.0 release)::
-* Formatting only
+- If unauthorized policy deactivation is confirmed, initiate the incident response process.
+- Immediately lock the affected actor account and require a password change.
+- Consider resetting MFA tokens for the actor and require re-enrollment.
+- Check if the compromised account was used to access or alter any sensitive data or systems.
+- If a specific deactivation technique was used, ensure your systems are patched or configured to prevent such techniques.
+- Assess the criticality of affected services and servers.
+- Work with your IT team to minimize the impact on users and maintain business continuity.
+- If multiple accounts are affected, consider a broader reset or audit of MFA tokens.
+- Implement security best practices https://www.okta.com/blog/2019/10/9-admin-best-practices-to-keep-your-org-secure/[outlined] by Okta.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 8 (8.4.0 release)::
-* Formatting only
+==== Setup
 
-Version 6 (7.13.0 release)::
-* Formatting only
 
-Version 5 (7.12.0 release)::
-* Formatting only
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
 
-Version 4 (7.11.2 release)::
-* Formatting only
 
-Version 3 (7.11.0 release)::
-* Rule name changed from: Attempt to Deactivate Okta Policy
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:policy.lifecycle.deactivate
+event.dataset:okta.system and event.action:policy.lifecycle.deactivate
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-application.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-application.asciidoc
index 737005516a..5138fb532f 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-application.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-application.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to delete an Okta application. An adversary may attempt to modi
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,61 +14,51 @@ Detects attempts to delete an Okta application. An adversary may attempt to modi
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-* Impact
-
-*Version*: 102 (<<attempt-to-delete-an-okta-application-history, version history>>)
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 205
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Consider adding exceptions to this rule to filter false positives if your organization's Okta applications are regularly deleted and the behavior is expected.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and
-event.action:application.lifecycle.delete
+[source, js]
 ----------------------------------
+event.dataset:okta.system and event.action:application.lifecycle.delete
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,25 +70,3 @@ event.action:application.lifecycle.delete
 ** Name: Service Stop
 ** ID: T1489
 ** Reference URL: https://attack.mitre.org/techniques/T1489/
-
-[[attempt-to-delete-an-okta-application-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-network-zone.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-network-zone.asciidoc
index 20e49f705e..9a223c4d54 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-network-zone.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-network-zone.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to delete an Okta network zone. Okta network zones can be confi
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,61 +14,90 @@ Detects attempts to delete an Okta network zone. Okta network zones can be confi
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Security/network/network-zones.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Use Case: Network Security Monitoring
+* Tactic: Defense Evasion
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Network Security
-* Defense Evasion
 
-*Version*: 102 (<<attempt-to-delete-an-okta-network-zone-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Consider adding exceptions to this rule to filter false positives if Oyour organization's Okta network zones are regularly deleted.
 
-==== Investigation guide
 
+*Investigating Attempt to Delete an Okta Network Zone*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+Okta network zones can be configured to limit or restrict access to a network based on IP addresses or geolocations. Deleting a network zone in Okta might remove or weaken the security controls of an organization, which might be an indicator of an adversary's attempt to evade defenses.
+
+
+*Possible investigation steps:*
+
+
+- Identify the actor associated with the alert by examining the `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields.
+- Examine the `event.action` field to confirm the deletion of a network zone.
+- Investigate the `okta.target.id`, `okta.target.type`, `okta.target.alternate_id`, or `okta.target.display_name` fields to identify the network zone that was deleted.
+- Review the `event.time` field to understand when the event happened.
+- Check the actor's activities before and after the event to understand the context of this event.
+
+
+*False positive analysis:*
+
+
+- Verify the `okta.client.user_agent.raw_user_agent` field to understand the device and software used by the actor. If these match the actor's typical behavior, it might be a false positive.
+- Check if the actor is a known administrator or a member of the IT team who might have a legitimate reason to delete a network zone.
+- Cross-verify the actor's actions with any known planned changes or maintenance activities.
 
 
+*Response and remediation:*
+
+
+- If unauthorized access or actions are confirmed, immediately lock the affected actor's account and require a password change.
+- If a network zone was deleted without authorization, create a new network zone with similar settings as the deleted one.
+- Review and update the privileges of the actor who initiated the deletion.
+- Identify any gaps in the security policies and procedures and update them as necessary.
+- Implement additional monitoring and logging of Okta events to improve visibility of user actions.
+- Communicate and train the employees about the importance of following proper procedures for modifying network zone settings.
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:okta.system and event.action:zone.delete
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,25 +109,7 @@ event.dataset:okta.system and event.action:zone.delete
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[attempt-to-delete-an-okta-network-zone-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-policy-rule.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-policy-rule.asciidoc
index af20405ef0..94b59a6aad 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-policy-rule.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-policy-rule.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to delete a rule within an Okta policy. An adversary may attemp
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,61 +14,97 @@ Detects attempts to delete a rule within an Okta policy. An adversary may attemp
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Security/Security_Policies.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Defense Evasion
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-* Defense Evasion
 
-*Version*: 102 (<<attempt-to-delete-an-okta-policy-rule-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Consider adding exceptions to this rule to filter false positives if Okta MFA rules are regularly modified in your organization.
 
-==== Investigation guide
 
+*Investigating Attempt to Delete an Okta Policy Rule*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+Okta policy rules are integral components of an organization's security controls, as they define how user access to resources is managed. Deletion of a rule within an Okta policy could potentially weaken the organization's security posture, allowing for unauthorized access or facilitating other malicious activities.
+
+This rule detects attempts to delete an Okta policy rule, which could indicate an adversary's attempt to weaken an organization's security controls. Adversaries may do this to circumvent security measures and enable further malicious activities.
+
+
+*Possible investigation steps:*
+
+
+- Identify the actor related to the alert by reviewing `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields in the alert.
+- Review the `okta.client.user_agent.raw_user_agent` field to understand the device and software used by the actor.
+- Examine the `okta.outcome.reason` field for additional context around the deletion attempt.
+- Check the `okta.outcome.result` field to confirm the policy rule deletion attempt.
+- Check if there are multiple policy rule deletion attempts from the same actor or IP address (`okta.client.ip`).
+- Check for successful logins immediately following the policy rule deletion attempt.
+- Verify whether the actor's activity aligns with typical behavior or if any unusual activity took place around the time of the deletion attempt.
+
+
+*False positive analysis:*
+
 
+- Check if there were issues with the Okta system at the time of the deletion attempt. This could indicate a system error rather than a genuine threat activity.
+- Check the geographical location (`okta.request.ip_chain.geographical_context`) and time of the deletion attempt. If these match the actor's normal behavior, it might be a false positive.
+- Verify the actor's administrative rights to ensure they are correctly configured.
+
+
+*Response and remediation:*
+
+
+- If unauthorized policy rule deletion is confirmed, initiate the incident response process.
+- Immediately lock the affected actor account and require a password change.
+- Consider resetting MFA tokens for the actor and require re-enrollment.
+- Check if the compromised account was used to access or alter any sensitive data or systems.
+- If a specific deletion technique was used, ensure your systems are patched or configured to prevent such techniques.
+- Assess the criticality of affected services and servers.
+- Work with your IT team to minimize the impact on users and maintain business continuity.
+- If multiple accounts are affected, consider a broader reset or audit of MFA tokens.
+- Implement security best practices https://www.okta.com/blog/2019/10/9-admin-best-practices-to-keep-your-org-secure/[outlined] by Okta.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:okta.system and event.action:policy.rule.delete
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,25 +116,7 @@ event.dataset:okta.system and event.action:policy.rule.delete
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[attempt-to-delete-an-okta-policy-rule-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-policy.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-policy.asciidoc
index 6625545619..8cc75e4de8 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-policy.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-delete-an-okta-policy.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to delete an Okta policy. An adversary may attempt to delete an
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,102 +14,109 @@ Detects attempts to delete an Okta policy. An adversary may attempt to delete an
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Security/Security_Policies.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Defense Evasion
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-* Defense Evasion
 
-*Version*: 102 (<<attempt-to-delete-an-okta-policy-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Consider adding exceptions to this rule to filter false positives if Okta policies are regularly deleted in your organization.
 
-==== Investigation guide
 
+*Investigating Attempt to Delete an Okta Policy*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+Okta policies are critical to managing user access and enforcing security controls within an organization. The deletion of an Okta policy could drastically weaken an organization's security posture by allowing unrestricted access or facilitating other malicious activities.
 
+This rule detects attempts to delete an Okta policy, which could be indicative of an adversary's attempt to weaken an organization's security controls. Adversaries may do this to bypass security barriers and enable further malicious activities.
 
-==== Rule query
 
+*Possible investigation steps:*
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and event.action:policy.lifecycle.delete
-----------------------------------
 
-==== Threat mapping
+- Identify the actor related to the alert by reviewing `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields in the alert.
+- Review the `okta.client.user_agent.raw_user_agent` field to understand the device and software used by the actor.
+- Examine the `okta.outcome.reason` field for additional context around the deletion attempt.
+- Check the `okta.outcome.result` field to confirm the policy deletion attempt.
+- Check if there are multiple policy deletion attempts from the same actor or IP address (`okta.client.ip`).
+- Check for successful logins immediately following the policy deletion attempt.
+- Verify whether the actor's activity aligns with typical behavior or if any unusual activity took place around the time of the deletion attempt.
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Impair Defenses
-** ID: T1562
-** Reference URL: https://attack.mitre.org/techniques/T1562/
+*False positive analysis:*
+
+
+- Check if there were issues with the Okta system at the time of the deletion attempt. This could indicate a system error rather than a genuine threat activity.
+- Check the geographical location (`okta.request.ip_chain.geographical_context`) and time of the deletion attempt. If these match the actor's normal behavior, it might be a false positive.
+- Verify the actor's administrative rights to ensure they are correctly configured.
+
 
-[[attempt-to-delete-an-okta-policy-history]]
-==== Rule version history
+*Response and remediation:*
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 100 (8.5.0 release)::
-* Formatting only
+- If unauthorized policy deletion is confirmed, initiate the incident response process.
+- Immediately lock the affected actor account and require a password change.
+- Consider resetting MFA tokens for the actor and require re-enrollment.
+- Check if the compromised account was used to access or alter any sensitive data or systems.
+- If a specific deletion technique was used, ensure your systems are patched or configured to prevent such techniques.
+- Assess the criticality of affected services and servers.
+- Work with your IT team to minimize the impact on users and maintain business continuity.
+- If multiple accounts are affected, consider a broader reset or audit of MFA tokens.
+- Implement security best practices https://www.okta.com/blog/2019/10/9-admin-best-practices-to-keep-your-org-secure/[outlined] by Okta.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 8 (8.4.0 release)::
-* Formatting only
+==== Setup
 
-Version 6 (7.13.0 release)::
-* Formatting only
 
-Version 5 (7.12.0 release)::
-* Formatting only
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
 
-Version 4 (7.11.2 release)::
-* Formatting only
 
-Version 3 (7.11.0 release)::
-* Rule name changed from: Attempt to Delete Okta Policy
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:policy.lifecycle.delete
+event.dataset:okta.system and event.action:policy.lifecycle.delete
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-disable-gatekeeper.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-disable-gatekeeper.asciidoc
index 3cd2f2346c..e76bce00e8 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-disable-gatekeeper.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-disable-gatekeeper.asciidoc
@@ -5,54 +5,88 @@ Detects attempts to disable Gatekeeper on macOS. Gatekeeper is a security featur
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.apple.com/en-us/HT202491
 * https://community.carbonblack.com/t5/Threat-Advisories-Documents/TAU-TIN-Shlayer-OSX/ta-p/68397
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Defense Evasion
 
-*Version*: 100 (<<attempt-to-disable-gatekeeper-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.12.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.args:(spctl and "--master-disable")
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+  process.args:(spctl and "--master-disable")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,22 +98,3 @@ process.args:(spctl and "--master-disable")
 ** Name: Subvert Trust Controls
 ** ID: T1553
 ** Reference URL: https://attack.mitre.org/techniques/T1553/
-
-[[attempt-to-disable-gatekeeper-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.args:(spctl and "--master-disable")
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.3.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-disable-iptables-or-firewall.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-disable-iptables-or-firewall.asciidoc
new file mode 100644
index 0000000000..9e4ace867c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-disable-iptables-or-firewall.asciidoc
@@ -0,0 +1,117 @@
+[[attempt-to-disable-iptables-or-firewall]]
+=== Attempt to Disable IPTables or Firewall
+
+Adversaries may attempt to disable the iptables or firewall service in an attempt to affect how a host is allowed to receive or send network traffic.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
+ (
+   /* disable FW */
+   (
+     (process.name == "ufw" and process.args == "disable") or
+     (process.name == "iptables" and process.args == "-F" and process.args_count == 2)
+   ) or
+
+   /* stop FW service */
+   (
+     ((process.name == "service" and process.args == "stop") or
+       (process.name == "chkconfig" and process.args == "off") or
+       (process.name == "systemctl" and process.args in ("disable", "stop", "kill"))) and
+    process.args in ("firewalld", "ip6tables", "iptables")
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-disable-syslog-service.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-disable-syslog-service.asciidoc
index 5c5b086785..2b01d0d1e9 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-disable-syslog-service.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-disable-syslog-service.asciidoc
@@ -3,98 +3,121 @@
 
 Adversaries may attempt to disable the syslog service in an attempt to an attempt to disrupt event logging and evade detection by security controls.
 
-*Rule type*: query
+*Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<attempt-to-disable-syslog-service-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.8.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
 
+==== Setup
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-((process.name:service and process.args:stop) or
-(process.name:chkconfig and process.args:off) or
-(process.name:systemctl and process.args:(disable or stop or kill)))
-and process.args:(syslog or rsyslog or "syslog-ng")
-----------------------------------
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Impair Defenses
-** ID: T1562
-** Reference URL: https://attack.mitre.org/techniques/T1562/
 
-[[attempt-to-disable-syslog-service-history]]
-==== Rule version history
+*Prerequisite Requirements:*
 
-Version 100 (8.5.0 release)::
-* Formatting only
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 8 (8.4.0 release)::
-* Formatting only
 
-Version 7 (7.12.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
 
-Version 6 (7.11.2 release)::
-* Formatting only
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Version 5 (7.11.0 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Formatting only
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
 
-Version 3 (7.9.1 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:(executed or process_started) and ((process.name:service
-and process.args:stop) or (process.name:chkconfig and
-process.args:off) or (process.name:systemctl and process.args:(disable
-or stop or kill))) and process.args:(syslog or rsyslog or "syslog-ng")
+process where host.os.type == "linux" and event.action in ("exec", "exec_event") and
+ ( (process.name == "service" and process.args == "stop") or
+   (process.name == "chkconfig" and process.args == "off") or
+   (process.name == "systemctl" and process.args in ("disable", "stop", "kill"))
+ ) and process.args in ("syslog", "rsyslog", "syslog-ng")
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-enable-the-root-account.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-enable-the-root-account.asciidoc
index 6b77ccbed3..cdadef7731 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-enable-the-root-account.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-enable-the-root-account.asciidoc
@@ -5,53 +5,87 @@ Identifies attempts to enable the root account using the dsenableroot command. T
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://ss64.com/osx/dsenableroot.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<attempt-to-enable-the-root-account-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:dsenableroot and not process.args:"-d"
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+ process.name:dsenableroot and not process.args:"-d"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -63,13 +97,7 @@ process.name:dsenableroot and not process.args:"-d"
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[attempt-to-enable-the-root-account-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Local Accounts
+** ID: T1078.003
+** Reference URL: https://attack.mitre.org/techniques/T1078/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-install-kali-linux-via-wsl.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-install-kali-linux-via-wsl.asciidoc
new file mode 100644
index 0000000000..0717806d6d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-install-kali-linux-via-wsl.asciidoc
@@ -0,0 +1,73 @@
+[[attempt-to-install-kali-linux-via-wsl]]
+=== Attempt to Install Kali Linux via WSL
+
+Detects attempts to install or use Kali Linux via Windows Subsystem for Linux. Adversaries may enable and use WSL for Linux to avoid detection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://learn.microsoft.com/en-us/windows/wsl/wsl-config
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+(
+ (process.name : "wsl.exe" and process.args : ("-d", "--distribution", "-i", "--install") and process.args : "kali*") or 
+ process.executable : 
+        ("?:\\Users\\*\\AppData\\Local\\packages\\kalilinux*", 
+         "?:\\Users\\*\\AppData\\Local\\Microsoft\\WindowsApps\\kali.exe",
+         "?:\\Program Files*\\WindowsApps\\KaliLinux.*\\kali.exe")
+ )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indirect Command Execution
+** ID: T1202
+** Reference URL: https://attack.mitre.org/techniques/T1202/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-install-root-certificate.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-install-root-certificate.asciidoc
index fc9371c86a..4d9b50dbef 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-install-root-certificate.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-install-root-certificate.asciidoc
@@ -5,60 +5,89 @@ Adversaries may install a root certificate on a compromised system to avoid warn
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://ss64.com/osx/security-cert.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Defense Evasion
 
-*Version*: 100 (<<attempt-to-install-root-certificate-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Certain applications may install root certificates for the purpose of inspecting SSL traffic.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:security and process.args:"add-trusted-cert" and not pr
-ocess.parent.executable:("/Library/Bitdefender/AVP/product/bin/BDCoreI
-ssues" or "/Applications/Bitdefender/SecurityNetworkInstallerApp.app/C
-ontents/MacOS/SecurityNetworkInstallerApp" )
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+  process.name:security and process.args:"add-trusted-cert" and
+  not process.parent.executable:("/Library/Bitdefender/AVP/product/bin/BDCoreIssues" or "/Applications/Bitdefender/SecurityNetworkInstallerApp.app/Contents/MacOS/SecurityNetworkInstallerApp"
+)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,19 +99,7 @@ ontents/MacOS/SecurityNetworkInstallerApp" )
 ** Name: Subvert Trust Controls
 ** ID: T1553
 ** Reference URL: https://attack.mitre.org/techniques/T1553/
-
-[[attempt-to-install-root-certificate-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:security and process.args:"add-trusted-cert"
-----------------------------------
-
+* Sub-technique:
+** Name: Install Root Certificate
+** ID: T1553.004
+** Reference URL: https://attack.mitre.org/techniques/T1553/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-application.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-application.asciidoc
index 42e0a5721d..1c9d6d0415 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-application.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-application.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to modify an Okta application. An adversary may attempt to modi
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,62 +14,52 @@ Detects attempts to modify an Okta application. An adversary may attempt to modi
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Apps.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-* Impact
-
-*Version*: 102 (<<attempt-to-modify-an-okta-application-history, version history>>)
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 205
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Consider adding exceptions to this rule to filter false positives if your organization's Okta applications are regularly modified and the behavior is expected.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and
-event.action:application.lifecycle.update
+[source, js]
 ----------------------------------
+event.dataset:okta.system and event.action:application.lifecycle.update
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,25 +67,3 @@ event.action:application.lifecycle.update
 ** Name: Impact
 ** ID: TA0040
 ** Reference URL: https://attack.mitre.org/tactics/TA0040/
-
-[[attempt-to-modify-an-okta-application-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-network-zone.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-network-zone.asciidoc
index 13f2fe6e07..772dd39c98 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-network-zone.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-network-zone.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to modify an Okta network zone. Okta network zones can be confi
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,114 +14,108 @@ Detects attempts to modify an Okta network zone. Okta network zones can be confi
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Security/network/network-zones.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Use Case: Network Security Monitoring
+* Tactic: Defense Evasion
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Network Security
-* Defense Evasion
 
-*Version*: 102 (<<attempt-to-modify-an-okta-network-zone-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Consider adding exceptions to this rule to filter false positives if Oyour organization's Okta network zones are regularly modified.
 
-==== Investigation guide
 
+*Investigating Attempt to Modify an Okta Network Zone*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+The modification of an Okta network zone is a critical event as it could potentially allow an adversary to gain unrestricted access to your network. This rule detects attempts to modify, delete, or deactivate an Okta network zone, which may suggest an attempt to remove or weaken an organization's security controls.
 
 
-==== Rule query
+*Possible investigation steps:*
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and event.action:(zone.update or
-network_zone.rule.disabled or zone.remove_blacklist)
-----------------------------------
+- Identify the actor related to the alert by reviewing `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields in the alert.
+- Review the `okta.client.user_agent.raw_user_agent` field to understand the device and software used by the actor.
+- Examine the `okta.outcome.reason` field for additional context around the modification attempt.
+- Check the `okta.outcome.result` field to confirm the network zone modification attempt.
+- Check if there are multiple network zone modification attempts from the same actor or IP address (`okta.client.ip`).
+- Check for successful logins immediately following the modification attempt.
+- Verify whether the actor's activity aligns with typical behavior or if any unusual activity took place around the time of the modification attempt.
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+*False positive analysis:*
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Impair Defenses
-** ID: T1562
-** Reference URL: https://attack.mitre.org/techniques/T1562/
 
-[[attempt-to-modify-an-okta-network-zone-history]]
-==== Rule version history
+- Check if there were issues with the Okta system at the time of the modification attempt. This could indicate a system error rather than a genuine threat activity.
+- Check the geographical location (`okta.request.ip_chain.geographical_context`) and time of the modification attempt. If these match the actor's normal behavior, it might be a false positive.
+- Verify the actor's administrative rights to ensure they are correctly configured.
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 100 (8.5.0 release)::
-* Formatting only
+*Response and remediation:*
 
-Version 8 (8.4.0 release)::
-* Formatting only
 
-Version 6 (7.13.0 release)::
-* Formatting only
+- If unauthorized modification is confirmed, initiate the incident response process.
+- Immediately lock the affected actor account and require a password change.
+- Consider resetting MFA tokens for the actor and require re-enrollment.
+- Check if the compromised account was used to access or alter any sensitive data or systems.
+- If a specific modification technique was used, ensure your systems are patched or configured to prevent such techniques.
+- Assess the criticality of affected services and servers.
+- Work with your IT team to minimize the impact on users and maintain business continuity.
+- If multiple accounts are affected, consider a broader reset or audit of MFA tokens.
+- Implement security best practices https://www.okta.com/blog/2019/10/9-admin-best-practices-to-keep-your-org-secure/[outlined] by Okta.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 5 (7.12.0 release)::
-* Formatting only
+==== Setup
 
-Version 4 (7.11.2 release)::
-* Formatting only
 
-Version 3 (7.11.0 release)::
-* Rule name changed from: Attempt to Modify Okta Network Zone
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:okta.system and event.action:(zone.update or
-zone.deactivate or zone.delete or network_zone.rule.disabled or
-zone.remove_blacklist)
-----------------------------------
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
 
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:(zone.update or zone.deactivate or zone.delete or
-network_zone.rule.disabled or zone.remove_blacklist)
+event.dataset:okta.system and event.action:(zone.update or network_zone.rule.disabled or zone.remove_blacklist)
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-policy-rule.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-policy-rule.asciidoc
index 0c8709564e..5f371097c9 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-policy-rule.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-policy-rule.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to modify a rule within an Okta policy. An adversary may attemp
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,111 +14,107 @@ Detects attempts to modify a rule within an Okta policy. An adversary may attemp
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Security/Security_Policies.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Tactic: Defense Evasion
+* Data Source: Okta
+
+*Version*: 207
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Defense Evasion
 
-*Version*: 102 (<<attempt-to-modify-an-okta-policy-rule-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Consider adding exceptions to this rule to filter false positives if Okta MFA rules are regularly modified in your organization.
 
-==== Investigation guide
 
+*Investigating Attempt to Modify an Okta Policy Rule*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+The modification of an Okta policy rule can be an indication of malicious activity as it may aim to weaken an organization's security controls.
 
 
-==== Rule query
+*Possible investigation steps:*
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and event.action:policy.rule.update
-----------------------------------
+- Identify the actor related to the alert by reviewing `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields in the alert.
+- Review the `okta.client.user_agent.raw_user_agent` field to understand the device and software used by the actor.
+- Examine the `okta.outcome.reason` field for additional context around the modification attempt.
+- Check the `okta.outcome.result` field to confirm the rule modification attempt.
+- Check if there are multiple rule modification attempts from the same actor or IP address (`okta.client.ip`).
+- Check for successful logins immediately following the modification attempt.
+- Verify whether the actor's activity aligns with typical behavior or if any unusual activity took place around the time of the modification attempt.
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+*False positive analysis:*
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Impair Defenses
-** ID: T1562
-** Reference URL: https://attack.mitre.org/techniques/T1562/
 
-[[attempt-to-modify-an-okta-policy-rule-history]]
-==== Rule version history
+- Check if there were issues with the Okta system at the time of the modification attempt. This could indicate a system error rather than a genuine threat activity.
+- Check the geographical location (`okta.request.ip_chain.geographical_context`) and time of the modification attempt. If these match the actor's normal behavior, it might be a false positive.
+- Verify the actor's administrative rights to ensure they are correctly configured.
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 100 (8.5.0 release)::
-* Formatting only
+*Response and remediation:*
 
-Version 8 (8.4.0 release)::
-* Formatting only
 
-Version 6 (7.13.0 release)::
-* Formatting only
+- If unauthorized modification is confirmed, initiate the incident response process.
+- Immediately lock the affected actor account and require a password change.
+- Consider resetting MFA tokens for the actor and require re-enrollment.
+- Check if the compromised account was used to access or alter any sensitive data or systems.
+- If a specific modification technique was used, ensure your systems are patched or configured to prevent such techniques.
+- Assess the criticality of affected services and servers.
+- Work with your IT team to minimize the impact on users and maintain business continuity.
+- If multiple accounts are affected, consider a broader reset or audit of MFA tokens.
+- Implement security best practices https://www.okta.com/blog/2019/10/9-admin-best-practices-to-keep-your-org-secure/[outlined] by Okta.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 5 (7.12.0 release)::
-* Formatting only
+==== Setup
 
-Version 4 (7.11.2 release)::
-* Formatting only
 
-Version 3 (7.11.0 release)::
-* Rule name changed from: Attempt to Modify Okta MFA Rule
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:okta.system and event.action:(policy.rule.update or
-policy.rule.delete)
-----------------------------------
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
 
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:(policy.rule.update or policy.rule.delete)
+event.dataset:okta.system and event.action:policy.rule.update
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-policy.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-policy.asciidoc
index b714b8c9e0..7e685a47d8 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-policy.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-modify-an-okta-policy.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to modify an Okta policy. An adversary may attempt to modify an
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,101 +14,97 @@ Detects attempts to modify an Okta policy. An adversary may attempt to modify an
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Defense Evasion
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-* Defense Evasion
 
-*Version*: 102 (<<attempt-to-modify-an-okta-policy-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Consider adding exceptions to this rule to filter false positives if Okta policies are regularly modified in your organization.
 
-==== Investigation guide
 
+*Investigating Attempt to Modify an Okta Policy*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+Modifications to Okta policies may indicate attempts to weaken an organization's security controls. If such an attempt is detected, consider the following steps for investigation.
 
 
-==== Rule query
+*Possible investigation steps:*
 
+- Identify the actor associated with the event. Check the fields `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, and `okta.actor.display_name`.
+- Determine the client used by the actor. You can look at `okta.client.device`, `okta.client.ip`, `okta.client.user_agent.raw_user_agent`, `okta.client.ip_chain.ip`, and `okta.client.geographical_context`.
+- Check the nature of the policy modification. You can review the `okta.target` field, especially `okta.target.display_name` and `okta.target.id`.
+- Examine the `okta.outcome.result` and `okta.outcome.reason` fields to understand the outcome of the modification attempt.
+- Check if there have been other similar modification attempts in a short time span from the same actor or IP address.
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and event.action:policy.lifecycle.update
-----------------------------------
 
-==== Threat mapping
+*False positive analysis:*
 
-*Framework*: MITRE ATT&CK^TM^
+- This alert might be a false positive if Okta policies are regularly updated in your organization as a part of normal operations.
+- Check if the actor associated with the event has legitimate rights to modify the Okta policies.
+- Verify the actor's geographical location and the time of the modification attempt. If these align with the actor's regular behavior, it could be a false positive.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Impair Defenses
-** ID: T1562
-** Reference URL: https://attack.mitre.org/techniques/T1562/
 
-[[attempt-to-modify-an-okta-policy-history]]
-==== Rule version history
+*Response and remediation:*
 
-Version 102 (8.6.0 release)::
-* Formatting only
+- If unauthorized modification is confirmed, initiate the incident response process.
+- Lock the actor's account and enforce password change as an immediate response.
+- Reset MFA tokens for the actor and enforce re-enrollment, if applicable.
+- Review any other actions taken by the actor to assess the overall impact.
+- If the attack was facilitated by a particular technique, ensure your systems are patched or configured to prevent such techniques.
+- Consider a security review of your Okta policies and rules to ensure they follow security best practices.
 
-Version 100 (8.5.0 release)::
-* Formatting only
+==== Setup
 
-Version 8 (8.4.0 release)::
-* Formatting only
 
-Version 6 (7.13.0 release)::
-* Formatting only
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
-Version 5 (7.12.0 release)::
-* Formatting only
+==== Rule query
 
-Version 4 (7.11.2 release)::
-* Formatting only
 
-Version 3 (7.11.0 release)::
-* Rule name changed from: Attempt to Modify Okta Policy
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:policy.lifecycle.update
+event.dataset:okta.system and event.action:policy.lifecycle.update
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-mount-smb-share-via-command-line.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-mount-smb-share-via-command-line.asciidoc
index 66ad97c8b1..f585b736cf 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-mount-smb-share-via-command-line.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-mount-smb-share-via-command-line.asciidoc
@@ -5,68 +5,94 @@ Identifies the execution of macOS built-in commands to mount a Server Message Bl
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.freebsd.org/cgi/man.cgi?mount_smbfs
 * https://ss64.com/osx/mount.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Lateral Movement
 
-*Version*: 100 (<<attempt-to-mount-smb-share-via-command-line-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-----------------------------------
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and (
-process.name : "mount_smbfs" or (process.name : "open" and
-process.args : "smb://*") or (process.name : "mount" and
-process.args : "smbfs") or (process.name : "osascript" and
-process.command_line : "osascript*mount volume*smb://*") ) and not
-process.parent.executable : "/Applications/Google
-Drive.app/Contents/MacOS/Google Drive"
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and
+  (
+    process.name : "mount_smbfs" or
+    (process.name : "open" and process.args : "smb://*") or
+    (process.name : "mount" and process.args : "smbfs") or
+    (process.name : "osascript" and process.command_line : "osascript*mount volume*smb://*")
+  ) and
+  not process.parent.executable : "/Applications/Google Drive.app/Contents/MacOS/Google Drive"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,25 +104,7 @@ Drive.app/Contents/MacOS/Google Drive"
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[attempt-to-mount-smb-share-via-command-line-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and (
-process.name : "mount_smbfs" or (process.name : "open" and
-process.args : "smb://*") or (process.name : "mount" and
-process.args : "smbfs") or (process.name : "osascript" and
-process.command_line : "osascript*mount volume*smb://*") )
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-reset-mfa-factors-for-an-okta-user-account.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-reset-mfa-factors-for-an-okta-user-account.asciidoc
index b25799db16..8a3938e058 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-reset-mfa-factors-for-an-okta-user-account.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-reset-mfa-factors-for-an-okta-user-account.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to reset an Okta user's enrolled multi-factor authentication (M
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,59 +14,51 @@ Detects attempts to reset an Okta user's enrolled multi-factor authentication (M
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<attempt-to-reset-mfa-factors-for-an-okta-user-account-history, version history>>)
+* Tactic: Persistence
+* Use Case: Identity and Access Audit
+* Data Source: Okta
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Consider adding exceptions to this rule to filter false positives if the MFA factors for Okta user accounts are regularly reset in your organization.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:okta.system and event.action:user.mfa.factor.reset_all
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,36 +70,3 @@ event.dataset:okta.system and event.action:user.mfa.factor.reset_all
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[attempt-to-reset-mfa-factors-for-an-okta-user-account-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Rule name changed from: Attempt to Reset MFA Factors for Okta User Account
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:user.mfa.factor.reset_all
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-revoke-okta-api-token.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-revoke-okta-api-token.asciidoc
index 6ca6cacfa1..08b010a324 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-revoke-okta-api-token.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-revoke-okta-api-token.asciidoc
@@ -5,7 +5,7 @@ Identifies attempts to revoke an Okta API token. An adversary may attempt to rev
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,101 +14,91 @@ Identifies attempts to revoke an Okta API token. An adversary may attempt to rev
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 102 (<<attempt-to-revoke-okta-api-token-history, version history>>)
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-If the behavior of revoking Okta API tokens is expected, consider adding exceptions to this rule to filter false positives.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Attempt to Revoke Okta API Token*
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and event.action:system.api_token.revoke
-----------------------------------
 
-==== Threat mapping
+The rule alerts when attempts are made to revoke an Okta API token. The API tokens are critical for integration services, and revoking them may lead to disruption in services. Therefore, it's important to validate these activities.
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Impact
-** ID: TA0040
-** Reference URL: https://attack.mitre.org/tactics/TA0040/
-* Technique:
-** Name: Account Access Removal
-** ID: T1531
-** Reference URL: https://attack.mitre.org/techniques/T1531/
+*Possible investigation steps:*
+
+- Identify the actor associated with the API token revocation attempt. You can use the `okta.actor.alternate_id` field for this purpose.
+- Determine the client used by the actor. Review the `okta.client.device`, `okta.client.ip`, `okta.client.user_agent.raw_user_agent`, `okta.client.ip_chain.ip`, and `okta.client.geographical_context` fields.
+- Verify if the API token revocation was authorized or part of some planned activity.
+- Check the `okta.outcome.result` and `okta.outcome.reason` fields to see if the attempt was successful or failed.
+- Analyze the past activities of the actor involved in this action. An actor who usually performs such activities may indicate a legitimate reason.
+- Evaluate the actions that happened just before and after this event. It can help understand the full context of the activity.
+
 
-[[attempt-to-revoke-okta-api-token-history]]
-==== Rule version history
+*False positive analysis:*
 
-Version 102 (8.6.0 release)::
-* Formatting only
+- It might be a false positive if the action was part of a planned activity or was performed by an authorized person.
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 8 (8.4.0 release)::
-* Formatting only
+*Response and remediation:*
 
-Version 6 (7.13.0 release)::
-* Formatting only
+- If unauthorized revocation attempts are confirmed, initiate the incident response process.
+- Block the IP address or device used in the attempts, if they appear suspicious.
+- Reset the user's password and enforce MFA re-enrollment, if applicable.
+- Conduct a review of Okta policies and ensure they are in accordance with security best practices.
+- If the revoked token was used for critical integrations, coordinate with the relevant team to minimize the impact.
 
-Version 5 (7.12.0 release)::
-* Formatting only
+==== Setup
 
-Version 4 (7.11.2 release)::
-* Formatting only
 
-Version 3 (7.11.0 release)::
-* Formatting only
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
 
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:system.api_token.revoke
+event.dataset:okta.system and event.action:system.api_token.revoke
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Account Access Removal
+** ID: T1531
+** Reference URL: https://attack.mitre.org/techniques/T1531/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempt-to-unload-elastic-endpoint-security-kernel-extension.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempt-to-unload-elastic-endpoint-security-kernel-extension.asciidoc
index 47ad65af7b..1365169d02 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempt-to-unload-elastic-endpoint-security-kernel-extension.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempt-to-unload-elastic-endpoint-security-kernel-extension.asciidoc
@@ -5,51 +5,85 @@ Identifies attempts to unload the Elastic Endpoint Security kernel extension via
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* macOS
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<attempt-to-unload-elastic-endpoint-security-kernel-extension-history, version history>>)
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:kextunload and
-process.args:("/System/Library/Extensions/EndpointSecurity.kext" or
-"EndpointSecurity.kext")
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+ process.name:kextunload and process.args:("/System/Library/Extensions/EndpointSecurity.kext" or "EndpointSecurity.kext")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -61,8 +95,10 @@ process.args:("/System/Library/Extensions/EndpointSecurity.kext" or
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -71,13 +107,7 @@ process.args:("/System/Library/Extensions/EndpointSecurity.kext" or
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[attempt-to-unload-elastic-endpoint-security-kernel-extension-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Kernel Modules and Extensions
+** ID: T1547.006
+** Reference URL: https://attack.mitre.org/techniques/T1547/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempted-bypass-of-okta-mfa.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempted-bypass-of-okta-mfa.asciidoc
index 4352580d6c..ea3909be9f 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempted-bypass-of-okta-mfa.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempted-bypass-of-okta-mfa.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to bypass Okta multi-factor authentication (MFA). An adversary
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,97 +14,104 @@ Detects attempts to bypass Okta multi-factor authentication (MFA). An adversary
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<attempted-bypass-of-okta-mfa-history, version history>>)
+* Data Source: Okta
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Attempted Bypass of Okta MFA*
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and event.action:user.mfa.attempt_bypass
-----------------------------------
 
-==== Threat mapping
+Multi-factor authentication (MFA) is a crucial security measure in preventing unauthorized access. Okta MFA, like other MFA solutions, requires the user to provide multiple means of identification at login. An adversary might attempt to bypass Okta MFA to gain unauthorized access to an application.
 
-*Framework*: MITRE ATT&CK^TM^
+This rule detects attempts to bypass Okta MFA. It might indicate a serious attempt to compromise a user account within the organization's network.
 
-* Tactic:
-** Name: Credential Access
-** ID: TA0006
-** Reference URL: https://attack.mitre.org/tactics/TA0006/
-* Technique:
-** Name: Multi-Factor Authentication Interception
-** ID: T1111
-** Reference URL: https://attack.mitre.org/techniques/T1111/
 
-[[attempted-bypass-of-okta-mfa-history]]
-==== Rule version history
+*Possible investigation steps*
+
 
-Version 102 (8.6.0 release)::
-* Formatting only
+- Identify the actor related to the alert by reviewing `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields in the alert.
+- Review the `okta.client.user_agent.raw_user_agent` field to understand the device and software used by the actor.
+- Examine the `okta.outcome.reason` field for additional context around the bypass attempt.
+- Check the `okta.outcome.result` field to confirm the MFA bypass attempt.
+- Check if there are multiple unsuccessful MFA attempts from the same actor or IP address (`okta.client.ip`).
+- Check for successful logins immediately following the MFA bypass attempt.
+- Verify whether the actor's activity aligns with typical behavior or if any unusual activity took place around the time of the bypass attempt.
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 8 (8.4.0 release)::
-* Formatting only
+*False positive analysis*
 
-Version 6 (7.13.0 release)::
-* Formatting only
 
-Version 5 (7.12.0 release)::
-* Formatting only
+- Check if there were issues with the MFA system at the time of the bypass attempt. This could indicate a system error rather than a genuine bypass attempt.
+- Check the geographical location (`okta.request.ip_chain.geographical_context`) and time of the login attempt. If these match the actor's normal behavior, it might be a false positive.
+- Verify the actor's MFA settings to ensure they are correctly configured.
 
-Version 4 (7.11.2 release)::
-* Formatting only
 
-Version 3 (7.11.0 release)::
-* Formatting only
+*Response and remediation*
+
+
+- If unauthorized access is confirmed, initiate the incident response process.
+- Immediately lock the affected actor account and require a password change.
+- Consider resetting MFA tokens for the actor and require re-enrollment.
+- Check if the compromised account was used to access or alter any sensitive data or systems.
+- If a specific MFA bypass technique was used, ensure your systems are patched or configured to prevent such techniques.
+- Assess the criticality of affected services and servers.
+- Work with your IT team to minimize the impact on users and maintain business continuity.
+- If multiple accounts are affected, consider a broader reset or audit of MFA tokens.
+- Implement security best practices https://www.okta.com/blog/2019/10/9-admin-best-practices-to-keep-your-org-secure/[outlined] by Okta.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
 
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:user.mfa.attempt_bypass
+event.dataset:okta.system and event.action:user.mfa.attempt_bypass
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Multi-Factor Authentication Interception
+** ID: T1111
+** Reference URL: https://attack.mitre.org/techniques/T1111/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempted-private-key-access.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempted-private-key-access.asciidoc
new file mode 100644
index 0000000000..23d6d1e7d7
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/attempted-private-key-access.asciidoc
@@ -0,0 +1,82 @@
+[[attempted-private-key-access]]
+=== Attempted Private Key Access
+
+Attackers may try to access private keys, e.g. ssh, in order to gain further authenticated access to the environment.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.args : ("*.pem *", "*.pem", "*.id_rsa*") and
+  not process.args: ("--tls-cert", "--ssl-cert") and
+  not process.executable : (
+    "?:\\ProgramData\\Logishrd\\LogiOptions\\Software\\*\\LogiLuUpdater.exe",
+    "?:\\Program Files\\Elastic\\Agent\\data\\*\\osqueryd.exe",
+    "?:\\Program Files\\Guardicore\\gc-controller.exe",
+    "?:\\Program Files\\Guardicore\\gc-deception-agent.exe",
+    "?:\\Program Files\\Guardicore\\gc-detection-agent.exe",
+    "?:\\Program Files\\Guardicore\\gc-enforcement-agent.exe",
+    "?:\\Program Files\\Guardicore\\gc-guest-agent.exe",
+    "?:\\Program Files\\Logi\\LogiBolt\\LogiBoltUpdater.exe",
+    "?:\\Program Files (x86)\\Schneider Electric EcoStruxure\\Building Operation 5.0\\Device Administrator\\Python\\python.exe",
+    "?:\\Program Files\\Splunk\\bin\\openssl.exe",
+    "?:\\Program Files\\SplunkUniversalForwarder\\bin\\openssl.exe",
+    "?:\\Users\\*\\AppData\\Local\\Logi\\LogiBolt\\LogiBoltUpdater.exe",
+    "?:\\Windows\\system32\\icacls.exe",
+    "?:\\Windows\\System32\\OpenSSH\\*"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Unsecured Credentials
+** ID: T1552
+** Reference URL: https://attack.mitre.org/techniques/T1552/
+* Sub-technique:
+** Name: Private Keys
+** ID: T1552.004
+** Reference URL: https://attack.mitre.org/techniques/T1552/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/attempts-to-brute-force-a-microsoft-365-user-account.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempts-to-brute-force-a-microsoft-365-user-account.asciidoc
index 6bc07ccf1f..e353b3d292 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempts-to-brute-force-a-microsoft-365-user-account.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempts-to-brute-force-a-microsoft-365-user-account.asciidoc
@@ -5,7 +5,7 @@ Identifies attempts to brute force a Microsoft 365 user account. An adversary ma
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,63 +14,55 @@ Identifies attempts to brute force a Microsoft 365 user account. An adversary ma
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blueteamblog.com/7-ways-to-monitor-your-office-365-logs-using-siem
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<attempts-to-brute-force-a-microsoft-365-user-account-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Willem D'Haese, Austin Songer
+* Elastic
+* Willem D'Haese
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Automated processes that attempt to authenticate using expired credentials and unbounded retries may lead to false positives.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:(AzureActiveDirectory or
-Exchange) and event.category:authentication and
-event.action:(UserLoginFailed or
-PasswordLogonInitialAuthUsingPassword) and not
-o365.audit.LogonError:(UserAccountNotFound or
-EntitlementGrantsNotFound or UserStrongAuthEnrollmentRequired or
-UserStrongAuthClientAuthNRequired or InvalidReplyTo)
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:(AzureActiveDirectory or Exchange) and
+  event.category:authentication and event.action:(UserLoginFailed or PasswordLogonInitialAuthUsingPassword) and
+  not o365.audit.LogonError:(UserAccountNotFound or EntitlementGrantsNotFound or UserStrongAuthEnrollmentRequired or
+                             UserStrongAuthClientAuthNRequired or InvalidReplyTo)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -82,62 +74,3 @@ UserStrongAuthClientAuthNRequired or InvalidReplyTo)
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
-
-[[attempts-to-brute-force-a-microsoft-365-user-account-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.3.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:(AzureActiveDirectory or
-Exchange) and event.category:authentication and
-event.action:(UserLoginFailed or
-PasswordLogonInitialAuthUsingPassword) and not
-o365.audit.LogonError:(UserAccountNotFound or
-EntitlementGrantsNotFound or UserStrongAuthEnrollmentRequired or
-UserStrongAuthClientAuthNRequired or InvalidReplyTo) and
-event.outcome:success
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:(AzureActiveDirectory or
-Exchange) and event.category:authentication and
-event.action:(UserLoginFailed or
-PasswordLogonInitialAuthUsingPassword) and not
-o365.audit.LogonError:(UserAccountNotFound or
-EntitlementGrantsNotFound or UserStrongAuthEnrollmentRequired or
-UserStrongAuthClientAuthNRequired or InvalidReplyTo) and
-event.outcome:failure
-----------------------------------
-
-Version 5 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:AzureActiveDirectory and
-event.category:authentication and event.action:UserLoginFailed and
-event.outcome:failure
-----------------------------------
-
-Version 3 (7.13.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/attempts-to-brute-force-an-okta-user-account.asciidoc b/docs/detections/prebuilt-rules/rule-details/attempts-to-brute-force-an-okta-user-account.asciidoc
index ddc260bc87..53cbe29f84 100644
--- a/docs/detections/prebuilt-rules/rule-details/attempts-to-brute-force-an-okta-user-account.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/attempts-to-brute-force-an-okta-user-account.asciidoc
@@ -5,7 +5,7 @@ Identifies when an Okta user account is locked out 3 times within a 3 hour windo
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,55 +14,95 @@ Identifies when an Okta user account is locked out 3 times within a 3 hour windo
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-180m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<attempts-to-brute-force-an-okta-user-account-history, version history>>)
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
+* Data Source: Okta
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 208
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, @BenB196, Austin Songer
+* Elastic
+* @BenB196
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating Attempts to Brute Force an Okta User Account*
+
+
+Brute force attacks aim to guess user credentials through exhaustive trial-and-error attempts. In this context, Okta accounts are targeted.
+
+This rule fires when an Okta user account has been locked out 3 times within a 3-hour window. This could indicate an attempted brute force or password spraying attack to gain unauthorized access to the user account. Okta's default authentication policy locks a user account after 10 failed authentication attempts.
+
+
+*Possible investigation steps:*
+
+
+- Identify the actor related to the alert by reviewing `okta.actor.alternate_id` field in the alert. This should give the username of the account being targeted.
+- Review the `okta.event_type` field to understand the nature of the events that led to the account lockout.
+- Check the `okta.severity` and `okta.display_message` fields for more context around the lockout events.
+- Look for correlation of events from the same IP address. Multiple lockouts from the same IP address might indicate a single source for the attack.
+- If the IP is not familiar, investigate it. The IP could be a proxy, VPN, Tor node, cloud datacenter, or a legitimate IP turned malicious.
+- Determine if the lockout events occurred during the user's regular activity hours. Unusual timing may indicate malicious activity.
+- Examine the authentication methods used during the lockout events by checking the `okta.authentication_context.credential_type` field.
+
+
+*False positive analysis:*
+
+
+- Determine whether the account owner or an internal user made repeated mistakes in entering their credentials, leading to the account lockout.
+- Ensure there are no known network or application issues that might cause these events.
+
 
+*Response and remediation:*
+
+
+- Alert the user and your IT department immediately.
+- If unauthorized access is confirmed, initiate your incident response process.
+- Investigate the source of the attack. If a specific machine or network is compromised, additional steps may need to be taken to address the issue.
+- Require the affected user to change their password.
+- If the attack is ongoing, consider blocking the IP address initiating the brute force attack.
+- Implement account lockout policies to limit the impact of brute force attacks.
+- Encourage users to use complex, unique passwords and consider implementing multi-factor authentication.
+- Check if the compromised account was used to access or alter any sensitive data or systems.
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:okta.system and event.action:user.account.lock
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,33 +114,3 @@ event.dataset:okta.system and event.action:user.account.lock
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
-
-[[attempts-to-brute-force-an-okta-user-account-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:okta.system and event.action:user.account.lock
-----------------------------------
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/authorization-plugin-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/authorization-plugin-modification.asciidoc
index 3617e719d3..0414487c8b 100644
--- a/docs/detections/prebuilt-rules/rule-details/authorization-plugin-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/authorization-plugin-modification.asciidoc
@@ -5,56 +5,90 @@ Authorization plugins are used to extend the authorization services API and impl
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.apple.com/documentation/security/authorization_plug-ins
 * https://www.xorrior.com/persistent-credential-theft/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<authorization-plugin-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:file and not event.type:deletion and
-file.path:(/Library/Security/SecurityAgentPlugins/* and not
-/Library/Security/SecurityAgentPlugins/TeamViewerAuthPlugin.bundle/*)
-and not process.name:shove and process.code_signature.trusted:true
+[source, js]
 ----------------------------------
+event.category:file and host.os.type:macos and not event.type:deletion and
+  file.path:(/Library/Security/SecurityAgentPlugins/* and
+  not (/Library/Security/SecurityAgentPlugins/KandjiPassport.bundle/* or /Library/Security/SecurityAgentPlugins/TeamViewerAuthPlugin.bundle/*)) and
+  not (process.name:shove and process.code_signature.trusted:true)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,20 +100,7 @@ and not process.name:shove and process.code_signature.trusted:true
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[authorization-plugin-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and not event.type:deletion and
-file.path:(/Library/Security/SecurityAgentPlugins/* and not /Library
-/Security/SecurityAgentPlugins/TeamViewerAuthPlugin.bundle/Contents/*)
-----------------------------------
-
+* Sub-technique:
+** Name: Authentication Package
+** ID: T1547.002
+** Reference URL: https://attack.mitre.org/techniques/T1547/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-bedrock-detected-multiple-attempts-to-use-denied-models-by-a-single-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-bedrock-detected-multiple-attempts-to-use-denied-models-by-a-single-user.asciidoc
new file mode 100644
index 0000000000..22ed004221
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/aws-bedrock-detected-multiple-attempts-to-use-denied-models-by-a-single-user.asciidoc
@@ -0,0 +1,69 @@
+[[aws-bedrock-detected-multiple-attempts-to-use-denied-models-by-a-single-user]]
+=== AWS Bedrock Detected Multiple Attempts to use Denied Models by a Single User
+
+Identifies multiple successive failed attempts to use denied model resources within AWS Bedrock. This could indicated attempts to bypass limitations of other approved models, or to force an impact on the environment by incurring exhorbitant costs.
+
+*Rule type*: esql
+
+*Rule indices*: None
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 10m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-components.html
+* https://atlas.mitre.org/techniques/AML.T0015
+* https://atlas.mitre.org/techniques/AML.T0034
+* https://www.elastic.co/security-labs/elastic-advances-llm-security
+
+*Tags*: 
+
+* Domain: LLM
+* Data Source: AWS Bedrock
+* Data Source: AWS S3
+* Resources: Investigation Guide
+* Use Case: Policy Violation
+* Mitre Atlas: T0015
+* Mitre Atlas: T0034
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires that guardrails are configured in AWS Bedrock. For more information, see the AWS Bedrock documentation:
+
+https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-create.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+from logs-aws_bedrock.invocation-*
+| where gen_ai.response.error_code == "AccessDeniedException"
+| stats total_denials = count(*) by user.id, gen_ai.request.model.id, cloud.account.id
+| where total_denials > 3
+| sort total_denials desc
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-bedrock-guardrails-detected-multiple-policy-violations-within-a-single-blocked-request.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-bedrock-guardrails-detected-multiple-policy-violations-within-a-single-blocked-request.asciidoc
new file mode 100644
index 0000000000..d64780e042
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/aws-bedrock-guardrails-detected-multiple-policy-violations-within-a-single-blocked-request.asciidoc
@@ -0,0 +1,70 @@
+[[aws-bedrock-guardrails-detected-multiple-policy-violations-within-a-single-blocked-request]]
+=== AWS Bedrock Guardrails Detected Multiple Policy Violations Within a Single Blocked Request
+
+Identifies multiple violations of AWS Bedrock guardrails within a single request, resulting in a block action, increasing the likelihood of malicious intent. Multiple violations implies that a user may be intentionally attempting to cirvumvent security controls, access sensitive information, or possibly exploit a vulnerability in the system.
+
+*Rule type*: esql
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 10m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-components.html
+* https://atlas.mitre.org/techniques/AML.T0051
+* https://atlas.mitre.org/techniques/AML.T0054
+* https://www.elastic.co/security-labs/elastic-advances-llm-security
+
+*Tags*: 
+
+* Domain: LLM
+* Data Source: AWS Bedrock
+* Data Source: AWS S3
+* Resources: Investigation Guide
+* Use Case: Policy Violation
+* Mitre Atlas: T0051
+* Mitre Atlas: T0054
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires that guardrails are configured in AWS Bedrock. For more information, see the AWS Bedrock documentation:
+
+https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-create.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+from logs-aws_bedrock.invocation-*
+| where gen_ai.policy.action == "BLOCKED"
+| eval policy_violations = mv_count(gen_ai.policy.name)
+| where policy_violations > 1
+| stats total_unique_request_violations = count(*) by policy_violations, user.id, gen_ai.request.model.id, cloud.account.id
+| sort total_unique_request_violations desc
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-bedrock-guardrails-detected-multiple-violations-by-a-single-user-over-a-session.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-bedrock-guardrails-detected-multiple-violations-by-a-single-user-over-a-session.asciidoc
new file mode 100644
index 0000000000..2e495a3d37
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/aws-bedrock-guardrails-detected-multiple-violations-by-a-single-user-over-a-session.asciidoc
@@ -0,0 +1,69 @@
+[[aws-bedrock-guardrails-detected-multiple-violations-by-a-single-user-over-a-session]]
+=== AWS Bedrock Guardrails Detected Multiple Violations by a Single User Over a Session
+
+Identifies multiple violations of AWS Bedrock guardrails by the same user in the same account over a session. Multiple violations implies that a user may be intentionally attempting to cirvumvent security controls, access sensitive information, or possibly exploit a vulnerability in the system.
+
+*Rule type*: esql
+
+*Rule indices*: None
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-components.html
+* https://atlas.mitre.org/techniques/AML.T0051
+* https://atlas.mitre.org/techniques/AML.T0054
+* https://www.elastic.co/security-labs/elastic-advances-llm-security
+
+*Tags*: 
+
+* Domain: LLM
+* Data Source: AWS Bedrock
+* Data Source: AWS S3
+* Resources: Investigation Guide
+* Use Case: Policy Violation
+* Mitre Atlas: T0051
+* Mitre Atlas: T0054
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires that guardrails are configured in AWS Bedrock. For more information, see the AWS Bedrock documentation:
+
+https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-create.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+from logs-aws_bedrock.invocation-*
+| where gen_ai.compliance.violation_detected
+| stats violations = count(*) by user.id, gen_ai.model.id, cloud.account.id
+| where violations > 1
+| sort violations desc
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-created.asciidoc
index 1b1cf28792..9df0d0feb5 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-created.asciidoc
@@ -5,69 +5,61 @@ Identifies the creation of an AWS log trail that specifies the settings for deli
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/awscloudtrail/latest/APIReference/API_CreateTrail.html
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudtrail/create-trail.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 101 (<<aws-cloudtrail-log-created-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Log Auditing
+* Tactic: Collection
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Trail creations may be made by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Trail creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:cloudtrail.amazonaws.com and event.action:CreateTrail
-and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:cloudtrail.amazonaws.com and event.action:CreateTrail and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,40 +68,6 @@ and event.outcome:success
 ** ID: TA0009
 ** Reference URL: https://attack.mitre.org/tactics/TA0009/
 * Technique:
-** Name: Data from Cloud Storage Object
+** Name: Data from Cloud Storage
 ** ID: T1530
 ** Reference URL: https://attack.mitre.org/techniques/T1530/
-
-[[aws-cloudtrail-log-created-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:CreateTrail and event.dataset:aws.cloudtrail and
-event.provider:cloudtrail.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-deleted.asciidoc
index 4581182774..a7441e83d5 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-deleted.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-deleted.asciidoc
@@ -5,70 +5,62 @@ Identifies the deletion of an AWS log trail. An adversary may delete trails in a
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/awscloudtrail/latest/APIReference/API_DeleteTrail.html
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudtrail/delete-trail.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Log Auditing
+* Resources: Investigation Guide
+* Tactic: Defense Evasion
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-* Investigation Guide
 
-*Version*: 103 (<<aws-cloudtrail-log-deleted-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Trail deletions may be made by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Trail deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating AWS CloudTrail Log Deleted*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS CloudTrail Log Deleted
+Amazon CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your Amazon Web Services account. With CloudTrail, you can log, continuously monitor, and retain account activity related to actions across your Amazon Web Services infrastructure. CloudTrail provides event history of your Amazon Web Services account activity, including actions taken through the Amazon Management Console, Amazon SDKs, command line tools, and other Amazon Web Services services. This event history simplifies security analysis, resource change tracking, and troubleshooting.
+
+This rule identifies the deletion of an AWS log trail using the API `DeleteTrail` action. Attackers can do this to cover their tracks and impact security monitoring that relies on this source.
 
-Amazon CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your
-Amazon Web Services account. With CloudTrail, you can log, continuously monitor, and retain account activity related to
-actions across your Amazon Web Services infrastructure. CloudTrail provides event history of your Amazon Web Services
-account activity, including actions taken through the Amazon Management Console, Amazon SDKs, command line tools, and
-other Amazon Web Services services. This event history simplifies security analysis, resource change tracking, and
-troubleshooting.
 
-This rule identifies the deletion of an AWS log trail using the API `DeleteTrail` action. Attackers can do this to
-cover their tracks and impact security monitoring that relies on this source.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
@@ -76,20 +68,20 @@ cover their tracks and impact security monitoring that relies on this source.
 - Check if this operation was approved and performed according to the organization's change management policy.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
 - Investigate the deleted log trail's criticality and whether the responsible team is aware of the deletion.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
 
-### False positive analysis
 
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and IP address conditions.
+*False positive analysis*
+
+
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -99,31 +91,28 @@ combination of user and IP address conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:cloudtrail.amazonaws.com and event.action:DeleteTrail
-and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:cloudtrail.amazonaws.com and event.action:DeleteTrail and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -135,40 +124,7 @@ and event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-cloudtrail-log-deleted-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:DeleteTrail and event.dataset:aws.cloudtrail and
-event.provider:cloudtrail.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-suspended.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-suspended.asciidoc
index 6ec5495d2f..47c9ec18c6 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-suspended.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-suspended.asciidoc
@@ -5,70 +5,62 @@ Identifies suspending the recording of AWS API calls and log file delivery for t
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/awscloudtrail/latest/APIReference/API_StopLogging.html
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudtrail/stop-logging.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Log Auditing
+* Resources: Investigation Guide
+* Tactic: Defense Evasion
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-* Investigation Guide
 
-*Version*: 103 (<<aws-cloudtrail-log-suspended-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Suspending the recording of a trail may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Trail suspensions from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating AWS CloudTrail Log Suspended*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS CloudTrail Log Suspended
+Amazon CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your Amazon Web Services account. With CloudTrail, you can log, continuously monitor, and retain account activity related to actions across your Amazon Web Services infrastructure. CloudTrail provides event history of your Amazon Web Services account activity, including actions taken through the Amazon Management Console, Amazon SDKs, command line tools, and other Amazon Web Services services. This event history simplifies security analysis, resource change tracking, and troubleshooting.
 
-Amazon CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your
-Amazon Web Services account. With CloudTrail, you can log, continuously monitor, and retain account activity related to
-actions across your Amazon Web Services infrastructure. CloudTrail provides event history of your Amazon Web Services
-account activity, including actions taken through the Amazon Management Console, Amazon SDKs, command line tools, and
-other Amazon Web Services services. This event history simplifies security analysis, resource change tracking, and
-troubleshooting.
+This rule identifies the suspension of an AWS log trail using the API `StopLogging` action. Attackers can do this to cover their tracks and impact security monitoring that relies on this source.
 
-This rule identifies the suspension of an AWS log trail using the API `StopLogging` action. Attackers can do this to
-cover their tracks and impact security monitoring that relies on this source.
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
@@ -76,20 +68,20 @@ cover their tracks and impact security monitoring that relies on this source.
 - Check if this operation was approved and performed according to the organization's change management policy.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
 - Investigate the deleted log trail's criticality and whether the responsible team is aware of the deletion.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.
 
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and IP address conditions.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -99,31 +91,28 @@ combination of user and IP address conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:cloudtrail.amazonaws.com and event.action:StopLogging
-and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:cloudtrail.amazonaws.com and event.action:StopLogging and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -135,37 +124,7 @@ and event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-cloudtrail-log-suspended-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:StopLogging and event.dataset:aws.cloudtrail and
-event.provider:cloudtrail.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-updated.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-updated.asciidoc
index f9a70d5f2c..e7745a3dd1 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-updated.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-cloudtrail-log-updated.asciidoc
@@ -5,70 +5,63 @@ Identifies an update to an AWS log trail setting that specifies the delivery of
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/awscloudtrail/latest/APIReference/API_UpdateTrail.html
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudtrail/update-trail.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS Cloudtrail
+* Use Case: Log Auditing
+* Resources: Investigation Guide
+* Tactic: Impact
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-* Investigation Guide
 
-*Version*: 103 (<<aws-cloudtrail-log-updated-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Trail updates may be made by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Trail updates from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating AWS CloudTrail Log Updated*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS CloudTrail Log Updated
+Amazon CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your Amazon Web Services account. With CloudTrail, you can log, continuously monitor, and retain account activity related to actions across your Amazon Web Services infrastructure. CloudTrail provides event history of your Amazon Web Services account activity, including actions taken through the Amazon Management Console, Amazon SDKs, command line tools, and other Amazon Web Services services. This event history simplifies security analysis, resource change tracking, and troubleshooting.
+
+This rule identifies a modification on CloudTrail settings using the API `UpdateTrail` action. Attackers can do this to cover their tracks and impact security monitoring that relies on this source.
 
-Amazon CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your
-Amazon Web Services account. With CloudTrail, you can log, continuously monitor, and retain account activity related to
-actions across your Amazon Web Services infrastructure. CloudTrail provides event history of your Amazon Web Services
-account activity, including actions taken through the Amazon Management Console, Amazon SDKs, command line tools, and
-other Amazon Web Services services. This event history simplifies security analysis, resource change tracking, and
-troubleshooting.
 
-This rule identifies a modification on CloudTrail settings using the API `UpdateTrail` action. Attackers can do this to
-cover their tracks and impact security monitoring that relies on this source.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Examine the response elements of the event to determine the scope of the changes.
@@ -77,19 +70,19 @@ cover their tracks and impact security monitoring that relies on this source.
 - Check if this operation was approved and performed according to the organization's change management policy.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
 
-### False positive analysis
 
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and IP address conditions.
+*False positive analysis*
+
+
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -99,31 +92,28 @@ combination of user and IP address conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:cloudtrail.amazonaws.com and event.action:UpdateTrail
-and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:cloudtrail.amazonaws.com and event.action:UpdateTrail and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -135,47 +125,15 @@ and event.outcome:success
 ** Name: Data Manipulation
 ** ID: T1565
 ** Reference URL: https://attack.mitre.org/techniques/T1565/
-
-
+* Sub-technique:
+** Name: Stored Data Manipulation
+** ID: T1565.001
+** Reference URL: https://attack.mitre.org/techniques/T1565/001/
 * Tactic:
 ** Name: Collection
 ** ID: TA0009
 ** Reference URL: https://attack.mitre.org/tactics/TA0009/
 * Technique:
-** Name: Data from Cloud Storage Object
+** Name: Data from Cloud Storage
 ** ID: T1530
 ** Reference URL: https://attack.mitre.org/techniques/T1530/
-
-[[aws-cloudtrail-log-updated-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:UpdateTrail and event.dataset:aws.cloudtrail and
-event.provider:cloudtrail.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-alarm-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-alarm-deletion.asciidoc
index 799cccc9db..5d46d875f2 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-alarm-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-alarm-deletion.asciidoc
@@ -5,58 +5,53 @@ Identifies the deletion of an AWS CloudWatch alarm. An adversary may delete alar
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudwatch/delete-alarms.html
 * https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_DeleteAlarms.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Monitoring
-* Investigation Guide
-
-*Version*: 103 (<<aws-cloudwatch-alarm-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Resources: Investigation Guide
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 209
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Alarm deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS CloudWatch Alarm Deletion
+*Triage and analysis*
+
+
+
+*Investigating AWS CloudWatch Alarm Deletion*
+
 
 Amazon CloudWatch is a monitoring and observability service that collects monitoring and operational data in the form of
 logs, metrics, and events for resources and applications. This data can be used to detect anomalous behavior in your environments, set alarms, visualize
@@ -69,7 +64,9 @@ fall outside of the levels (high or low thresholds) that you configure.
 This rule looks for the deletion of a alarm using the API `DeleteAlarms` action. Attackers can do this to cover their
 tracks and evade security defenses.
 
-#### Possible investigation steps
+
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
@@ -77,19 +74,19 @@ tracks and evade security defenses.
 - Check if there is a justification for this behavior.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.
 
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and IP address conditions.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -99,31 +96,28 @@ combination of user and IP address conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:monitoring.amazonaws.com and event.action:DeleteAlarms
-and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:monitoring.amazonaws.com and event.action:DeleteAlarms and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -135,40 +129,7 @@ and event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-cloudwatch-alarm-deletion-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:DeleteAlarms and event.dataset:aws.cloudtrail and
-event.provider:monitoring.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-log-group-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-log-group-deletion.asciidoc
index 2d4604591b..34ddcdad95 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-log-group-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-log-group-deletion.asciidoc
@@ -5,72 +5,65 @@ Identifies the deletion of a specified AWS CloudWatch log group. When a log grou
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/logs/delete-log-group.html
 * https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_DeleteLogGroup.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS CloudWatch
+* Use Case: Log Auditing
+* Resources: Investigation Guide
+* Tactic: Impact
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-* Investigation Guide
 
-*Version*: 103 (<<aws-cloudwatch-log-group-deletion-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Log group deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating AWS CloudWatch Log Group Deletion*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS CloudWatch Log Group Deletion
+Amazon CloudWatch is a monitoring and observability service that collects monitoring and operational data in the form of logs, metrics, and events for resources and applications. This data can be used to detect anomalous behavior in your environments, set alarms, visualize logs and metrics side by side, take automated actions, troubleshoot issues, and discover insights to keep your applications running smoothly.
+
+A log group is a group of log streams that share the same retention, monitoring, and access control settings. You can define log groups and specify which streams to put into each group. There is no limit on the number of log streams that can belong to one log group.
 
-Amazon CloudWatch is a monitoring and observability service that collects monitoring and operational data in the form of
-logs, metrics, and events for resources and applications. This data can be used to detect anomalous behavior in your environments, set alarms, visualize
-logs and metrics side by side, take automated actions, troubleshoot issues, and discover insights to keep your
-applications running smoothly.
+This rule looks for the deletion of a log group using the API `DeleteLogGroup` action. Attackers can do this to cover their tracks and impact security monitoring that relies on these sources.
 
-A log group is a group of log streams that share the same retention, monitoring, and access control settings. You can
-define log groups and specify which streams to put into each group. There is no limit on the number of log streams that
-can belong to one log group.
 
-This rule looks for the deletion of a log group using the API `DeleteLogGroup` action. Attackers can do this to cover
-their tracks and impact security monitoring that relies on these sources.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
@@ -78,20 +71,20 @@ their tracks and impact security monitoring that relies on these sources.
 - Check if this operation was approved and performed according to the organization's change management policy.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
 - Investigate the deleted log group's criticality and whether the responsible team is aware of the deletion.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
 
-### False positive analysis
 
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and IP address conditions.
+*False positive analysis*
+
+
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -101,30 +94,28 @@ combination of user and IP address conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:logs.amazonaws.com and
-event.action:DeleteLogGroup and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:logs.amazonaws.com and event.action:DeleteLogGroup and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -136,8 +127,6 @@ event.action:DeleteLogGroup and event.outcome:success
 ** Name: Data Destruction
 ** ID: T1485
 ** Reference URL: https://attack.mitre.org/techniques/T1485/
-
-
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -146,40 +135,7 @@ event.action:DeleteLogGroup and event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-cloudwatch-log-group-deletion-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:DeleteLogGroup and event.dataset:aws.cloudtrail and
-event.provider:logs.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-log-stream-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-log-stream-deletion.asciidoc
index 1ee285caff..b44dca37b4 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-log-stream-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-cloudwatch-log-stream-deletion.asciidoc
@@ -5,72 +5,65 @@ Identifies the deletion of an AWS CloudWatch log stream, which permanently delet
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/logs/delete-log-stream.html
 * https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_DeleteLogStream.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS CloudWatch
+* Use Case: Log Auditing
+* Tactic: Impact
+* Resources: Investigation Guide
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-* Impact
-* Investigation Guide
 
-*Version*: 103 (<<aws-cloudwatch-log-stream-deletion-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-A log stream may be deleted by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Log stream deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating AWS CloudWatch Log Stream Deletion*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS CloudWatch Log Stream Deletion
+Amazon CloudWatch is a monitoring and observability service that collects monitoring and operational data in the form of logs, metrics, and events for resources and applications. This data can be used to detect anomalous behavior in your environments, set alarms, visualize logs and metrics side by side, take automated actions, troubleshoot issues, and discover insights to keep your applications running smoothly.
+
+A log stream is a sequence of log events that share the same source. Each separate source of logs in CloudWatch Logs makes up a separate log stream.
 
-Amazon CloudWatch is a monitoring and observability service that collects monitoring and operational data in the form of
-logs, metrics, and events for resources and applications. This data can be used to detect anomalous behavior in your environments, set alarms, visualize
-logs and metrics side by side, take automated actions, troubleshoot issues, and discover insights to keep your
-applications running smoothly.
+This rule looks for the deletion of a log stream using the API `DeleteLogStream` action. Attackers can do this to cover their tracks and impact security monitoring that relies on these sources.
 
-A log stream is a sequence of log events that share the same source. Each separate source of logs in CloudWatch Logs
-makes up a separate log stream.
 
-This rule looks for the deletion of a log stream using the API `DeleteLogStream` action. Attackers can do this to cover
-their tracks and impact security monitoring that relies on these sources.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
@@ -78,20 +71,20 @@ their tracks and impact security monitoring that relies on these sources.
 - Check if this operation was approved and performed according to the organization's change management policy.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the calling user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
 - Investigate the deleted log stream's criticality and whether the responsible team is aware of the deletion.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
 
-### False positive analysis
 
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and IP address conditions.
+*False positive analysis*
+
+
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -101,30 +94,28 @@ combination of user and IP address conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:logs.amazonaws.com and
-event.action:DeleteLogStream and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:logs.amazonaws.com and event.action:DeleteLogStream and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -136,8 +127,6 @@ event.action:DeleteLogStream and event.outcome:success
 ** Name: Data Destruction
 ** ID: T1485
 ** Reference URL: https://attack.mitre.org/techniques/T1485/
-
-
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -146,40 +135,7 @@ event.action:DeleteLogStream and event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-cloudwatch-log-stream-deletion-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:DeleteLogStream and event.dataset:aws.cloudtrail and
-event.provider:logs.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-config-resource-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-config-resource-deletion.asciidoc
index 5eb70f2acc..213ed5ea60 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-config-resource-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-config-resource-deletion.asciidoc
@@ -5,89 +5,83 @@ Identifies attempts to delete an AWS Config Service resource. An adversary may t
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/config/latest/developerguide/how-does-config-work.html
 * https://docs.aws.amazon.com/config/latest/APIReference/API_Operations.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Resources: Investigation Guide
+* Tactic: Defense Evasion
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Monitoring
-* Investigation Guide
+* Austin Songer
 
-*Version*: 103 (<<aws-config-resource-deletion-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic, Austin Songer
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Privileged IAM users with security responsibilities may be expected to make changes to the Config service in order to align with local security policies and requirements. Automation, orchestration, and security tools may also make changes to the Config service, where they are used to automate setup or configuration of AWS accounts. Other kinds of user or service contexts do not commonly make changes to this service.
 
-==== Investigation guide
 
+*Investigating AWS Config Resource Deletion*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS Config Resource Deletion
+AWS Config provides a detailed view of the configuration of AWS resources in your AWS account. This includes how the resources are related to one another and how they were configured in the past so that you can see how the configurations and relationships change over time.
 
-AWS Config provides a detailed view of the configuration of AWS resources in your AWS account. This includes how the
-resources are related to one another and how they were configured in the past so that you can see how the configurations
-and relationships change over time.
+This rule looks for the deletion of AWS Config resources using various API actions. Attackers can do this to cover their tracks and impact security monitoring that relies on these sources.
 
-This rule looks for the deletion of AWS Config resources using various API actions. Attackers can do this to cover their
-tracks and impact security monitoring that relies on these sources.
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
-- Identify the AWS resource that was involved and its criticality, ownership, and role in the environment. Also investigate
-if the resource is security-related.
+- Identify the AWS resource that was involved and its criticality, ownership, and role in the environment. Also investigate if the resource is security-related.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Contact the account and resource owners and confirm whether they are aware of this activity.
 - Check if this operation was approved and performed according to the organization's change management policy.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the calling user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.
 
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and IP address conditions.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -97,34 +91,31 @@ combination of user and IP address conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:config.amazonaws.com
-and event.action:(DeleteConfigRule or DeleteOrganizationConfigRule
-or DeleteConfigurationAggregator or DeleteConfigurationRecorder or
-DeleteConformancePack or DeleteOrganizationConformancePack or
-DeleteDeliveryChannel or DeleteRemediationConfiguration or
-DeleteRetentionConfiguration)
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:config.amazonaws.com and
+    event.action:(DeleteConfigRule or DeleteOrganizationConfigRule or DeleteConfigurationAggregator or
+    DeleteConfigurationRecorder or DeleteConformancePack or DeleteOrganizationConformancePack or
+    DeleteDeliveryChannel or DeleteRemediationConfiguration or DeleteRetentionConfiguration)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -136,36 +127,7 @@ DeleteRetentionConfiguration)
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-config-resource-deletion-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Rule name changed from: AWS Config Service Tampering
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset: aws.cloudtrail and event.action: DeleteConfigRule and
-event.provider: config.amazonaws.com
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-configuration-recorder-stopped.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-configuration-recorder-stopped.asciidoc
index 7c2b5dd1b0..cac222d06d 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-configuration-recorder-stopped.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-configuration-recorder-stopped.asciidoc
@@ -5,68 +5,60 @@ Identifies an AWS configuration change to stop recording a designated set of res
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/configservice/stop-configuration-recorder.html
 * https://docs.aws.amazon.com/config/latest/APIReference/API_StopConfigurationRecorder.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 101 (<<aws-configuration-recorder-stopped-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Recording changes from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:config.amazonaws.com
-and event.action:StopConfigurationRecorder and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:config.amazonaws.com and event.action:StopConfigurationRecorder and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,38 +70,7 @@ and event.action:StopConfigurationRecorder and event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-configuration-recorder-stopped-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:StopConfigurationRecorder and
-event.dataset:aws.cloudtrail and event.provider:config.amazonaws.com
-and event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-credentials-searched-for-inside-a-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-credentials-searched-for-inside-a-container.asciidoc
new file mode 100644
index 0000000000..9d5a8dd5c6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/aws-credentials-searched-for-inside-a-container.asciidoc
@@ -0,0 +1,70 @@
+[[aws-credentials-searched-for-inside-a-container]]
+=== AWS Credentials Searched For Inside A Container
+
+This rule detects the use of system search utilities like grep and find to search for AWS credentials inside a container. Unauthorized access to these sensitive files could lead to further compromise of the container environment or facilitate a container breakout to the underlying cloud environment.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://sysdig.com/blog/threat-detection-aws-cloud-containers/
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.module == "cloud_defend" and     
+  event.type == "start" and
+  
+/*account for tools that execute utilities as a subprocess, in this case the target utility name will appear as a process arg*/
+(process.name : ("grep", "egrep", "fgrep", "find", "locate", "mlocate") or process.args : ("grep", "egrep", "fgrep", "find", "locate", "mlocate")) and 
+process.args : ("*aws_access_key_id*", "*aws_secret_access_key*", "*aws_session_token*", "*accesskeyid*", "*secretaccesskey*", "*access_key*", "*.aws/credentials*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Unsecured Credentials
+** ID: T1552
+** Reference URL: https://attack.mitre.org/techniques/T1552/
+* Sub-technique:
+** Name: Credentials In Files
+** ID: T1552.001
+** Reference URL: https://attack.mitre.org/techniques/T1552/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-deletion-of-rds-instance-or-cluster.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-deletion-of-rds-instance-or-cluster.asciidoc
index 2ed6e8beac..91e3189970 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-deletion-of-rds-instance-or-cluster.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-deletion-of-rds-instance-or-cluster.asciidoc
@@ -5,22 +5,22 @@ Identifies the deletion of an Amazon Relational Database Service (RDS) Aurora da
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/delete-db-cluster.html
 * https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DeleteDBCluster.html
@@ -29,49 +29,43 @@ Identifies the deletion of an Amazon Relational Database Service (RDS) Aurora da
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/delete-db-instance.html
 * https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DeleteDBInstance.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-
-*Version*: 101 (<<aws-deletion-of-rds-instance-or-cluster-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS RDS
+* Use Case: Asset Visibility
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Clusters or instances may be deleted by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Cluster or instance deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.action:(DeleteDBCluster or DeleteGlobalCluster or
-DeleteDBInstance) and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and event.action:(DeleteDBCluster or DeleteGlobalCluster or DeleteDBInstance)
+and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -83,57 +77,3 @@ DeleteDBInstance) and event.outcome:success
 ** Name: Data Destruction
 ** ID: T1485
 ** Reference URL: https://attack.mitre.org/techniques/T1485/
-
-[[aws-deletion-of-rds-instance-or-cluster-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.action:(DeleteDBCluster or DeleteGlobalCluster or
-DeleteDBInstance) and event.outcome:success
-----------------------------------
-
-Version 7 (8.2.0 release)::
-* Rule name changed from: AWS RDS Cluster Deletion
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.action:(DeleteDBCluster or DeleteGlobalCluster) and
-event.outcome:success
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:(DeleteDBCluster or DeleteGlobalCluster) and
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.outcome:success
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-ec2-admin-credential-fetch-via-assumed-role.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-ec2-admin-credential-fetch-via-assumed-role.asciidoc
new file mode 100644
index 0000000000..7babe60235
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/aws-ec2-admin-credential-fetch-via-assumed-role.asciidoc
@@ -0,0 +1,124 @@
+[[aws-ec2-admin-credential-fetch-via-assumed-role]]
+=== AWS EC2 Admin Credential Fetch via Assumed Role
+
+Identifies the first occurrence of a user identity in AWS using `GetPassword` for the administrator password of an EC2 instance with an assumed role. Adversaries may use this API call to escalate privileges or move laterally within EC2 instances.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-aws.cloudtrail*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://cloud.hacktricks.xyz/pentesting-cloud/aws-security/aws-privilege-escalation/aws-ec2-privesc
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: Amazon EC2
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Credential Access
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+*Triage and Analysis*
+
+
+
+*Investigating AWS EC2 Admin Credential Fetch via Assumed Role*
+
+
+This rule detects the first occurrence of a user identity using the `GetPasswordData` API call in AWS, which retrieves the administrator password of an EC2 instance. This can be an indicator of an adversary attempting to escalate privileges or move laterally within EC2 instances.
+
+This is a New Terms rule, which means it will only trigger once for each unique value of the `aws.cloudtrail.user_identity.session_context.session_issuer.arn` field that has not been seen making this API request within the last 7 days. This field contains the Amazon Resource Name (ARN) of the assumed role that triggered the API call.
+
+
+*Possible Investigation Steps*
+
+
+- **Identify the User Identity and Role**: Examine the AWS CloudTrail logs to determine the user identity that made the `GetPasswordData` request. Pay special attention to the role and permissions associated with the user.
+- **Review Request and Response Parameters**: Analyze the `aws.cloudtrail.request_parameters` and `aws.cloudtrail.response_elements` fields to understand the context of the API call and the retrieved password.
+- **Contextualize with User Behavior**: Compare this activity against the user's typical behavior patterns. Look for unusual login times, IP addresses, or other anomalous actions taken by the user or role prior to and following the incident.
+- **Review EC2 Instance Details**: Check the details of the EC2 instance from which the password was retrieved. Assess the criticality and sensitivity of the applications running on this instance.
+- **Examine Related CloudTrail Events**: Search for other API calls made by the same user identity, especially those modifying security groups, network access controls, or instance metadata.
+- **Check for Lateral Movement**: Look for evidence that the obtained credentials have been used to access other resources or services within AWS.
+- **Investigate the Origin of the API Call**: Analyze the IP address and geographical location from which the request originated. Determine if it aligns with expected locations for legitimate administrative activity.
+
+
+*False Positive Analysis*
+
+
+- **Legitimate Administrative Actions**: Ensure that the activity was not part of legitimate administrative tasks such as system maintenance or updates.
+- **Automation Scripts**: Verify if the activity was generated by automation or deployment scripts that are authorized to use `GetPasswordData` for legitimate purposes.
+
+
+*Response and Remediation*
+
+
+- **Immediate Isolation**: If suspicious, isolate the affected instance to prevent any potential lateral movement or further unauthorized actions.
+- **Credential Rotation**: Rotate credentials of the affected instance or assumed role and any other potentially compromised credentials.
+- **User Account Review**: Review the permissions of the implicated user identity. Apply the principle of least privilege by adjusting permissions to prevent misuse.
+- **Enhanced Monitoring**: Increase monitoring on the user identity that triggered the rule and similar EC2 instances.
+- **Incident Response**: If malicious intent is confirmed, initiate the incident response protocol. This includes further investigation, containment of the threat, eradication of any threat actor presence, and recovery of affected systems.
+- **Preventative Measures**: Implement or enhance security measures such as multi-factor authentication and continuous audits of sensitive operations like `GetPasswordData`.
+
+
+*Additional Information*
+
+
+Refer to resources like https://cloud.hacktricks.xyz/pentesting-cloud/aws-security/aws-privilege-escalation/aws-ec2-privesc[AWS privilege escalation methods] and the MITRE ATT&CK technique https://attack.mitre.org/techniques/T1552/005/[T1552.005 - Cloud Instance Metadata API] for more details on potential vulnerabilities and mitigation strategies.
+
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"aws.cloudtrail"
+    and event.provider:"ec2.amazonaws.com" and event.action:"GetPasswordData"
+    and aws.cloudtrail.user_identity.type:"AssumedRole" and aws.cloudtrail.error_code:"Client.UnauthorizedOperation"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Unsecured Credentials
+** ID: T1552
+** Reference URL: https://attack.mitre.org/techniques/T1552/
+* Sub-technique:
+** Name: Cloud Instance Metadata API
+** ID: T1552.005
+** Reference URL: https://attack.mitre.org/techniques/T1552/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-ec2-encryption-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-ec2-encryption-disabled.asciidoc
index 4899175576..88498af549 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-ec2-encryption-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-ec2-encryption-disabled.asciidoc
@@ -5,69 +5,62 @@ Identifies disabling of Amazon Elastic Block Store (EBS) encryption by default i
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/disable-ebs-encryption-by-default.html
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DisableEbsEncryptionByDefault.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Data Protection
-
-*Version*: 101 (<<aws-ec2-encryption-disabled-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS EC2
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Disabling encryption may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Disabling encryption by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.action:DisableEbsEncryptionByDefault and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and event.action:DisableEbsEncryptionByDefault and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,38 +72,7 @@ event.action:DisableEbsEncryptionByDefault and event.outcome:success
 ** Name: Data Manipulation
 ** ID: T1565
 ** Reference URL: https://attack.mitre.org/techniques/T1565/
-
-[[aws-ec2-encryption-disabled-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:DisableEbsEncryptionByDefault and
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Stored Data Manipulation
+** ID: T1565.001
+** Reference URL: https://attack.mitre.org/techniques/T1565/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-ec2-full-network-packet-capture-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-ec2-full-network-packet-capture-detected.asciidoc
index 5387cc9ee9..32bb87dfca 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-ec2-full-network-packet-capture-detected.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-ec2-full-network-packet-capture-detected.asciidoc
@@ -5,70 +5,65 @@ Identifies potential Traffic Mirroring in an Amazon Elastic Compute Cloud (EC2)
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_TrafficMirrorFilter.html
 * https://github.com/easttimor/aws-incident-response
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Network Security
-
-*Version*: 101 (<<aws-ec2-full-network-packet-capture-detected-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Network Security Monitoring
+* Tactic: Exfiltration
+* Tactic: Collection
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Traffic Mirroring may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Traffic Mirroring from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.action:(CreateTrafficMirrorFilter or
-CreateTrafficMirrorFilterRule or CreateTrafficMirrorSession or
-CreateTrafficMirrorTarget) and event.outcome:success
-----------------------------------
+event.action:(CreateTrafficMirrorFilter or CreateTrafficMirrorFilterRule or CreateTrafficMirrorSession or CreateTrafficMirrorTarget) and
+event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,8 +75,6 @@ CreateTrafficMirrorTarget) and event.outcome:success
 ** Name: Automated Exfiltration
 ** ID: T1020
 ** Reference URL: https://attack.mitre.org/techniques/T1020/
-
-
 * Tactic:
 ** Name: Collection
 ** ID: TA0009
@@ -90,27 +83,3 @@ CreateTrafficMirrorTarget) and event.outcome:success
 ** Name: Data Staged
 ** ID: T1074
 ** Reference URL: https://attack.mitre.org/techniques/T1074/
-
-[[aws-ec2-full-network-packet-capture-detected-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.action:(CreateTrafficMirrorFilter or
-CreateTrafficMirrorFilterRule or CreateTrafficMirrorSession or
-CreateTrafficMirrorTarget) and event.outcome:success
-----------------------------------
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-ec2-network-access-control-list-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-ec2-network-access-control-list-creation.asciidoc
index 4b0d6435af..e9bc7e1db4 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-ec2-network-access-control-list-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-ec2-network-access-control-list-creation.asciidoc
@@ -5,71 +5,64 @@ Identifies the creation of an AWS Elastic Compute Cloud (EC2) network access con
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/create-network-acl.html
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateNetworkAcl.html
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/create-network-acl-entry.html
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateNetworkAclEntry.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Network Security
-
-*Version*: 101 (<<aws-ec2-network-access-control-list-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS EC2
+* Use Case: Network Security Monitoring
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Network ACL's may be created by a network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Network ACL creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.action:(CreateNetworkAcl or CreateNetworkAclEntry) and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and event.action:(CreateNetworkAcl or CreateNetworkAclEntry) and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,41 +74,3 @@ event.outcome:success
 ** Name: External Remote Services
 ** ID: T1133
 ** Reference URL: https://attack.mitre.org/techniques/T1133/
-
-[[aws-ec2-network-access-control-list-creation-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:(CreateNetworkAcl or CreateNetworkAclEntry) and
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-ec2-network-access-control-list-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-ec2-network-access-control-list-deletion.asciidoc
index 9a0c8bb3f3..405ac974b0 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-ec2-network-access-control-list-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-ec2-network-access-control-list-deletion.asciidoc
@@ -5,71 +5,63 @@ Identifies the deletion of an Amazon Elastic Compute Cloud (EC2) network access
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/delete-network-acl.html
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DeleteNetworkAcl.html
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/delete-network-acl-entry.html
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DeleteNetworkAclEntry.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Network Security
-
-*Version*: 101 (<<aws-ec2-network-access-control-list-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Network Security Monitoring
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Network ACL's may be deleted by a network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Network ACL deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.action:(DeleteNetworkAcl or DeleteNetworkAclEntry) and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and event.action:(DeleteNetworkAcl or DeleteNetworkAclEntry) and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,41 +73,7 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-ec2-network-access-control-list-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:(DeleteNetworkAcl or DeleteNetworkAclEntry) and
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-ec2-snapshot-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-ec2-snapshot-activity.asciidoc
index ecbb677a37..8e694f8eed 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-ec2-snapshot-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-ec2-snapshot-activity.asciidoc
@@ -5,67 +5,62 @@ An attempt was made to modify AWS EC2 snapshot attributes. Snapshots are sometim
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/modify-snapshot-attribute.html
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ModifySnapshotAttribute.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Asset Visibility
+* Tactic: Exfiltration
+* Resources: Investigation Guide
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-* Exfiltration
-* Investigation Guide
 
-*Version*: 103 (<<aws-ec2-snapshot-activity-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-IAM users may occasionally share EC2 snapshots with another AWS account belonging to the same organization. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating AWS EC2 Snapshot Activity*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS EC2 Snapshot Activity
+Amazon EC2 snapshots are a mechanism to create point-in-time references to data that reside in storage volumes. System administrators commonly use this for backup operations and data recovery.
 
-Amazon EC2 snapshots are a mechanism to create point-in-time references to data that reside in storage volumes. System
-administrators commonly use this for backup operations and data recovery.
+This rule looks for the modification of snapshot attributes using the API `ModifySnapshotAttribute` action. This can be used to share snapshots with unauthorized third parties, giving others access to all the data on the snapshot.
 
-This rule looks for the modification of snapshot attributes using the API `ModifySnapshotAttribute` action. This can be
-used to share snapshots with unauthorized third parties, giving others access to all the data on the snapshot.
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Search for dry run attempts against the resource ID of the snapshot from other user accounts within CloudTrail.
@@ -74,21 +69,21 @@ used to share snapshots with unauthorized third parties, giving others access to
 - Contact the account owner and confirm whether they are aware of this activity.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the calling user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
 - Check if this operation was approved and performed according to the organization's change management policy.
 - Check if the shared permissions of the snapshot were modified to `Public` or include unknown account IDs.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.
 
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and IP address conditions.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -98,30 +93,28 @@ combination of user and IP address conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.action:ModifySnapshotAttribute
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and event.action:ModifySnapshotAttribute
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -133,35 +126,3 @@ event.action:ModifySnapshotAttribute
 ** Name: Transfer Data to Cloud Account
 ** ID: T1537
 ** Reference URL: https://attack.mitre.org/techniques/T1537/
-
-[[aws-ec2-snapshot-activity-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:aws and event.dataset:aws.cloudtrail and
-event.provider:ec2.amazonaws.com and
-event.action:ModifySnapshotAttribute
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-ec2-vm-export-failure.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-ec2-vm-export-failure.asciidoc
index e84dd10d4b..7052c52da1 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-ec2-vm-export-failure.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-ec2-vm-export-failure.asciidoc
@@ -5,67 +5,62 @@ Identifies an attempt to export an AWS EC2 instance. A virtual machine (VM) expo
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/vm-import/latest/userguide/vmexport.html#export-instance
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-
-*Version*: 101 (<<aws-ec2-vm-export-failure-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Asset Visibility
+* Tactic: Exfiltration
+* Tactic: Collection
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-VM exports may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. VM exports from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.action:CreateInstanceExportTask and event.outcome:failure
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and event.action:CreateInstanceExportTask and event.outcome:failure
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,8 +72,6 @@ event.action:CreateInstanceExportTask and event.outcome:failure
 ** Name: Transfer Data to Cloud Account
 ** ID: T1537
 ** Reference URL: https://attack.mitre.org/techniques/T1537/
-
-
 * Tactic:
 ** Name: Collection
 ** ID: TA0009
@@ -87,16 +80,3 @@ event.action:CreateInstanceExportTask and event.outcome:failure
 ** Name: Data from Local System
 ** ID: T1005
 ** Reference URL: https://attack.mitre.org/techniques/T1005/
-
-[[aws-ec2-vm-export-failure-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-efs-file-system-or-mount-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-efs-file-system-or-mount-deleted.asciidoc
index b0ae301228..7464e91967 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-efs-file-system-or-mount-deleted.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-efs-file-system-or-mount-deleted.asciidoc
@@ -5,70 +5,61 @@ Detects when an EFS File System or Mount is deleted. An adversary could break an
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/efs/latest/ug/API_DeleteFileSystem.html
 * https://docs.aws.amazon.com/efs/latest/ug/API_DeleteMountTarget.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Data Protection
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Tactic: Impact
 
-*Version*: 101 (<<aws-efs-file-system-or-mount-deleted-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-File System or Mount being deleted may be performed by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. File System Mount deletion by unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:elasticfilesystem.amazonaws.com and
-event.action:(DeleteMountTarget or DeleteFileSystem) and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:elasticfilesystem.amazonaws.com and
+event.action:(DeleteMountTarget or DeleteFileSystem) and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,30 +71,3 @@ event.outcome:success
 ** Name: Data Destruction
 ** ID: T1485
 ** Reference URL: https://attack.mitre.org/techniques/T1485/
-
-[[aws-efs-file-system-or-mount-deleted-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:elasticfilesystem.amazonaws.com and
-event.action:(DeleteMountTarget or DeleteFileSystem) and
-event.outcome:success
-----------------------------------
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-elasticache-security-group-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-elasticache-security-group-created.asciidoc
index 73219d5474..53cdc9c183 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-elasticache-security-group-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-elasticache-security-group-created.asciidoc
@@ -5,68 +5,60 @@ Identifies when an ElastiCache security group has been created.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/AmazonElastiCache/latest/APIReference/API_CreateCacheSecurityGroup.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Monitoring
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Tactic: Defense Evasion
 
-*Version*: 101 (<<aws-elasticache-security-group-created-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A ElastiCache security group may be created by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Security group creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:elasticache.amazonaws.com and event.action:"Create
-Cache Security Group" and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:elasticache.amazonaws.com and event.action:"Create Cache Security Group" and
+event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,26 +70,7 @@ Cache Security Group" and event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-elasticache-security-group-created-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:elasticache.amazonaws.com and event.action:"Create
-Cache Security Group" and event.outcome:success
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-elasticache-security-group-modified-or-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-elasticache-security-group-modified-or-deleted.asciidoc
index d0477e4239..c90f217e9d 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-elasticache-security-group-modified-or-deleted.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-elasticache-security-group-modified-or-deleted.asciidoc
@@ -5,71 +5,61 @@ Identifies when an ElastiCache security group has been modified or deleted.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/AmazonElastiCache/latest/APIReference/Welcome.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Monitoring
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Tactic: Defense Evasion
 
-*Version*: 101 (<<aws-elasticache-security-group-modified-or-deleted-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A ElastiCache security group deletion may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Security Group deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:elasticache.amazonaws.com and event.action:("Delete
-Cache Security Group" or "Authorize Cache Security Group Ingress" or
-"Revoke Cache Security Group Ingress" or
-"AuthorizeCacheSecurityGroupEgress" or
+event.dataset:aws.cloudtrail and event.provider:elasticache.amazonaws.com and event.action:("Delete Cache Security Group" or
+"Authorize Cache Security Group Ingress" or  "Revoke Cache Security Group Ingress" or "AuthorizeCacheSecurityGroupEgress" or
 "RevokeCacheSecurityGroupEgress") and event.outcome:success
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,29 +71,7 @@ Cache Security Group" or "Authorize Cache Security Group Ingress" or
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-elasticache-security-group-modified-or-deleted-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:elasticache.amazonaws.com and event.action:("Delete
-Cache Security Group" or "Authorize Cache Security Group Ingress" or
-"Revoke Cache Security Group Ingress" or
-"AuthorizeCacheSecurityGroupEgress" or
-"RevokeCacheSecurityGroupEgress") and event.outcome:success
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-eventbridge-rule-disabled-or-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-eventbridge-rule-disabled-or-deleted.asciidoc
index 897affc2f2..ca74620f9e 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-eventbridge-rule-disabled-or-deleted.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-eventbridge-rule-disabled-or-deleted.asciidoc
@@ -5,70 +5,61 @@ Identifies when a user has disabled or deleted an EventBridge rule. This activit
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-20m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/eventbridge/latest/APIReference/API_DeleteRule.html
 * https://docs.aws.amazon.com/eventbridge/latest/APIReference/API_DisableRule.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Monitoring
-* Impact
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Tactic: Impact
 
-*Version*: 101 (<<aws-eventbridge-rule-disabled-or-deleted-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-EventBridge Rules could be deleted or disabled by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. EventBridge Rules being deleted or disabled by unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:eventbridge.amazonaws.com and event.action:(DeleteRule
-or DisableRule) and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:eventbridge.amazonaws.com and event.action:(DeleteRule or DisableRule) and
+event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,29 +71,3 @@ or DisableRule) and event.outcome:success
 ** Name: Service Stop
 ** ID: T1489
 ** Reference URL: https://attack.mitre.org/techniques/T1489/
-
-[[aws-eventbridge-rule-disabled-or-deleted-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:eventbridge.amazonaws.com and event.action:(DeleteRule
-or DisableRule) and event.outcome:success
-----------------------------------
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
-Version 2 (8.0.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-execution-via-system-manager.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-execution-via-system-manager.asciidoc
index d1f52a5322..90de4d0957 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-execution-via-system-manager.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-execution-via-system-manager.asciidoc
@@ -5,90 +5,85 @@ Identifies the execution of commands and scripts via System Manager. Execution m
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/systems-manager/latest/userguide/ssm-plugins.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS SSM
+* Use Case: Log Auditing
+* Tactic: Initial Access
+* Resources: Investigation Guide
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-* Initial Access
-* Investigation Guide
 
-*Version*: 103 (<<aws-execution-via-system-manager-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Suspicious commands from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating AWS Execution via System Manager*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS Execution via System Manager
+Amazon EC2 Systems Manager is a management service designed to help users automatically collect software inventory, apply operating system patches, create system images, and configure Windows and Linux operating systems.
 
-Amazon EC2 Systems Manager is a management service designed to help users automatically collect software inventory, apply
-operating system patches, create system images, and configure Windows and Linux operating systems.
+This rule looks for the execution of commands and scripts using System Manager. Note that the actual contents of these scripts and commands are not included in the event, so analysts must gain visibility using an host-level security product.
 
-This rule looks for the execution of commands and scripts using System Manager. Note that the actual contents of these
-scripts and commands are not included in the event, so analysts must gain visibility using an host-level security product.
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
-- Validate that the activity is not related to planned patches, updates, network administrator activity, or legitimate
-software installations.
+- Validate that the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
 - Investigate the commands or scripts using host-level visibility.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the calling user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences involving other users.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Check if this operation was approved and performed according to the organization's change management policy.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.
 
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and IP address conditions.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -98,30 +93,28 @@ combination of user and IP address conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:ssm.amazonaws.com and
-event.action:SendCommand and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:ssm.amazonaws.com and event.action:SendCommand and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -133,38 +126,7 @@ event.action:SendCommand and event.outcome:success
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[aws-execution-via-system-manager-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:aws and event.dataset:aws.cloudtrail and
-event.provider:ssm.amazonaws.com and event.action:SendCommand and
-event.outcome:success
-----------------------------------
-
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-guardduty-detector-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-guardduty-detector-deletion.asciidoc
index 48b7cb375a..d2d74ce6f0 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-guardduty-detector-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-guardduty-detector-deletion.asciidoc
@@ -5,69 +5,60 @@ Identifies the deletion of an Amazon GuardDuty detector. Upon deletion, GuardDut
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/guardduty/delete-detector.html
 * https://docs.aws.amazon.com/guardduty/latest/APIReference/API_DeleteDetector.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 101 (<<aws-guardduty-detector-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-The GuardDuty detector may be deleted by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Detector deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:guardduty.amazonaws.com and event.action:DeleteDetector
-and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:guardduty.amazonaws.com and event.action:DeleteDetector and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,40 +70,7 @@ and event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-guardduty-detector-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:DeleteDetector and event.dataset:aws.cloudtrail and
-event.provider:guardduty.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-iam-assume-role-policy-update.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-iam-assume-role-policy-update.asciidoc
index 743db51e90..d9fb102c64 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-iam-assume-role-policy-update.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-iam-assume-role-policy-update.asciidoc
@@ -5,84 +5,78 @@ Identifies attempts to modify an AWS IAM Assume Role Policy. An adversary may at
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://labs.bishopfox.com/tech-blog/5-privesc-attack-vectors-in-aws
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS STS
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Privilege Escalation
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Investigation Guide
 
-*Version*: 103 (<<aws-iam-assume-role-policy-update-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Policy updates from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating AWS IAM Assume Role Policy Update*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS IAM Assume Role Policy Update
+An IAM role is an IAM identity that you can create in your account that has specific permissions. An IAM role is similar to an IAM user, in that it is an AWS identity with permission policies that determine what the identity can and cannot do in AWS. However, instead of being uniquely associated with one person, a role is intended to be assumable by anyone who needs it. Also, a role does not have standard long-term credentials such as a password or access keys associated with it. Instead, when you assume a role, it provides you with temporary security credentials for your role session.
 
-An IAM role is an IAM identity that you can create in your account that has specific permissions. An IAM role is similar
-to an IAM user, in that it is an AWS identity with permission policies that determine what the identity can and cannot
-do in AWS. However, instead of being uniquely associated with one person, a role is intended to be assumable by anyone
-who needs it. Also, a role does not have standard long-term credentials such as a password or access keys associated
-with it. Instead, when you assume a role, it provides you with temporary security credentials for your role session.
+The role trust policy is a JSON document in which you define the principals you trust to assume the role. This policy is a required resource-based policy that is attached to a role in IAM. An attacker may attempt to modify this policy by using the `UpdateAssumeRolePolicy` API action to gain the privileges of that role.
 
-The role trust policy is a JSON document in which you define the principals you trust to assume the role. This policy is
-a required resource-based policy that is attached to a role in IAM. An attacker may attempt to modify this policy by
-using the `UpdateAssumeRolePolicy` API action to gain the privileges of that role.
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Contact the account and resource owners and confirm whether they are aware of this activity.
 - Check if this operation was approved and performed according to the organization's change management policy.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- False positives may occur due to the intended usage of the service. Tuning is needed in order to have higher confidence. Consider adding exceptions — preferably with a combination of the user agent and user ID conditions — to cover administrator activities and infrastructure as code tooling.
 
-- False positives may occur due to the intended usage of the service. Tuning is needed in order to have higher
-confidence. Consider adding exceptions — preferably with a combination of the user agent and user ID conditions — to
-cover administrator activities and infrastructure as code tooling.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -92,31 +86,28 @@ cover administrator activities and infrastructure as code tooling.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Use AWS [policy versioning](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-versioning.html) to restore the trust policy to the desired state.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
-- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other
-IAM users.
+- Use AWS https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-versioning.html[policy versioning] to restore the trust policy to the desired state.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and
-event.action:UpdateAssumeRolePolicy and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and event.action:UpdateAssumeRolePolicy and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -128,35 +119,3 @@ event.action:UpdateAssumeRolePolicy and event.outcome:success
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[aws-iam-assume-role-policy-update-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:aws and event.dataset:aws.cloudtrail and
-event.provider:iam.amazonaws.com and
-event.action:UpdateAssumeRolePolicy and event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-iam-brute-force-of-assume-role-policy.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-iam-brute-force-of-assume-role-policy.asciidoc
index b25af8e64f..ab73986598 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-iam-brute-force-of-assume-role-policy.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-iam-brute-force-of-assume-role-policy.asciidoc
@@ -5,86 +5,82 @@ Identifies a high number of failed attempts to assume an AWS Identity and Access
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-20m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.praetorian.com/blog/aws-iam-assume-role-vulnerabilities
 * https://rhinosecuritylabs.com/aws/assume-worst-aws-assume-role-enumeration/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Investigation Guide
-
-*Version*: 103 (<<aws-iam-brute-force-of-assume-role-policy-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 210
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS IAM Brute Force of Assume Role Policy
+*Triage and analysis*
+
+
+
+*Investigating AWS IAM Brute Force of Assume Role Policy*
+
 
-An IAM role is an IAM identity that you can create in your account that has specific permissions. An IAM role is similar
-to an IAM user, in that it is an AWS identity with permission policies that determine what the identity can and cannot
-do in AWS. However, instead of being uniquely associated with one person, a role is intended to be assumable by anyone
-who needs it. Also, a role does not have standard long-term credentials such as a password or access keys associated
-with it. Instead, when you assume a role, it provides you with temporary security credentials for your role session.
+An IAM role is an IAM identity that you can create in your account that has specific permissions. An IAM role is similar to an IAM user, in that it is an AWS identity with permission policies that determine what the identity can and cannot do in AWS. However, instead of being uniquely associated with one person, a role is intended to be assumable by anyone who needs it. Also, a role does not have standard long-term credentials such as a password or access keys associated with it. Instead, when you assume a role, it provides you with temporary security credentials for your role session.
 
-Attackers may attempt to enumerate IAM roles in order to determine if a role exists before attempting to assume or
-hijack the discovered role.
+Attackers may attempt to enumerate IAM roles in order to determine if a role exists before attempting to assume or hijack the discovered role.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
-- Verify if the `RoleName` parameter contains a unique value in all requests or if the activity is potentially a brute
-force attack.
+- Verify if the `RoleName` parameter contains a unique value in all requests or if the activity is potentially a brute force attack.
 - Verify if the user account successfully updated a trust policy in the last 24 hours.
 - Examine whether this role existed in the environment by looking for past occurrences in your logs.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Contact the account and resource owners and confirm whether they are aware of this activity.
-- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal
-time of day?
+- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal time of day?
 - Examine the account's commands, API calls, and data management actions in the last 24 hours.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
 
-### False positive analysis
 
-- Verify the roles targeted in the failed attempts, and whether the subject role previously existed in the environment.
-If only one role was targeted in the requests and that role previously existed, it may be a false positive, since
-automations can continue targeting roles that existed in the environment in the past and cause false positives (FPs).
+- Verify the roles targeted in the failed attempts, and whether the subject role previously existed in the environment. If only one role was targeted in the requests and that role previously existed, it may be a false positive, since automations can continue targeting roles that existed in the environment in the past and cause false positives (FPs).
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -94,32 +90,29 @@ automations can continue targeting roles that existed in the environment in the
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
-- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other
-IAM users.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com
-and event.action:UpdateAssumeRolePolicy and
-aws.cloudtrail.error_code:MalformedPolicyDocumentException and
-event.outcome:failure
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and
+  event.provider:iam.amazonaws.com and event.action:UpdateAssumeRolePolicy and
+  aws.cloudtrail.error_code:MalformedPolicyDocumentException and event.outcome:failure
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -131,37 +124,3 @@ event.outcome:failure
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
-
-[[aws-iam-brute-force-of-assume-role-policy-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.1 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:aws and event.dataset:aws.cloudtrail and
-event.provider:iam.amazonaws.com and
-event.action:UpdateAssumeRolePolicy and
-aws.cloudtrail.error_code:MalformedPolicyDocumentException and
-event.outcome:failure
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-iam-deactivation-of-mfa-device.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-iam-deactivation-of-mfa-device.asciidoc
index b70ae5c9a5..c885897288 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-iam-deactivation-of-mfa-device.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-iam-deactivation-of-mfa-device.asciidoc
@@ -5,85 +5,81 @@ Identifies the deactivation of a specified multi-factor authentication (MFA) dev
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/iam/deactivate-mfa-device.html
 * https://docs.aws.amazon.com/IAM/latest/APIReference/API_DeactivateMFADevice.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS IAM
+* Resources: Investigation Guide
+* Tactic: Impact
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Monitoring
-* Investigation Guide
+* Austin Songer
 
-*Version*: 103 (<<aws-iam-deactivation-of-mfa-device-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic, Austin Songer
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-A MFA device may be deactivated by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. MFA device deactivations from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating AWS IAM Deactivation of MFA Device*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS IAM Deactivation of MFA Device
+Multi-factor authentication (MFA) in AWS is a simple best practice that adds an extra layer of protection on top of your user name and password. With MFA enabled, when a user signs in to an AWS Management Console, they will be prompted for their user name and password (the first factor—what they know), as well as for an authentication code from their AWS MFA device (the second factor—what they have). Taken together, these multiple factors provide increased security for your AWS account settings and resources.
 
-Multi-factor authentication (MFA) in AWS is a simple best practice that adds an extra layer of protection on top of your
-user name and password. With MFA enabled, when a user signs in to an AWS Management Console, they will be prompted for
-their user name and password (the first factor—what they know), as well as for an authentication code from their AWS MFA
-device (the second factor—what they have). Taken together, these multiple factors provide increased security for your
-AWS account settings and resources.
+For more information about using MFA in AWS, access the https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa.html[official documentation].
 
-For more information about using MFA in AWS, access the [official documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa.html).
+This rule looks for the deactivation or deletion of AWS MFA devices. These modifications weaken account security and can lead to the compromise of accounts and other assets.
 
-This rule looks for the deactivation or deletion of AWS MFA devices. These modifications weaken account security and can
-lead to the compromise of accounts and other assets.
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Contact the account and resource owners and confirm whether they are aware of this activity.
 - Check if this operation was approved and performed according to the organization's change management policy.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- While this activity can be done by administrators, all users must use MFA. The security team should address any potential benign true positive (B-TP), as this configuration can risk the user and domain.
 
-- While this activity can be done by administrators, all users must use MFA. The security team should address any
-potential benign true positive (B-TP), as this configuration can risk the user and domain.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -93,29 +89,26 @@ potential benign true positive (B-TP), as this configuration can risk the user a
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Reactivate multi-factor authentication for the user.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and
-event.action:(DeactivateMFADevice or DeleteVirtualMFADevice) and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and event.action:(DeactivateMFADevice or DeleteVirtualMFADevice) and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -127,34 +120,3 @@ event.outcome:success
 ** Name: Account Access Removal
 ** ID: T1531
 ** Reference URL: https://attack.mitre.org/techniques/T1531/
-
-[[aws-iam-deactivation-of-mfa-device-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:DeactivateMFADevice and event.dataset:aws.cloudtrail and
-event.provider:iam.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-iam-group-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-iam-group-creation.asciidoc
index f91392d28c..08503c020f 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-iam-group-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-iam-group-creation.asciidoc
@@ -5,68 +5,62 @@ Identifies the creation of a group in AWS Identity and Access Management (IAM).
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/iam/create-group.html
 * https://docs.aws.amazon.com/IAM/latest/APIReference/API_CreateGroup.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<aws-iam-group-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS IAM
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A group may be created by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Group creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and
-event.action:CreateGroup and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and event.action:CreateGroup and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,40 +72,7 @@ event.action:CreateGroup and event.outcome:success
 ** Name: Create Account
 ** ID: T1136
 ** Reference URL: https://attack.mitre.org/techniques/T1136/
-
-[[aws-iam-group-creation-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:CreateGroup and event.dataset:aws.cloudtrail and
-event.provider:iam.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Cloud Account
+** ID: T1136.003
+** Reference URL: https://attack.mitre.org/techniques/T1136/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-iam-group-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-iam-group-deletion.asciidoc
index 0e5c91a7bc..11aec75762 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-iam-group-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-iam-group-deletion.asciidoc
@@ -5,68 +5,61 @@ Identifies the deletion of a specified AWS Identity and Access Management (IAM)
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/iam/delete-group.html
 * https://docs.aws.amazon.com/IAM/latest/APIReference/API_DeleteGroup.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 101 (<<aws-iam-group-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS IAM
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A resource group may be deleted by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Resource group deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and
-event.action:DeleteGroup and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and event.action:DeleteGroup and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,37 +71,3 @@ event.action:DeleteGroup and event.outcome:success
 ** Name: Account Access Removal
 ** ID: T1531
 ** Reference URL: https://attack.mitre.org/techniques/T1531/
-
-[[aws-iam-group-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:DeleteGroup and event.dataset:aws.cloudtrail and
-event.provider:iam.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-iam-login-profile-added-to-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-iam-login-profile-added-to-user.asciidoc
new file mode 100644
index 0000000000..b6a7f84d3b
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/aws-iam-login-profile-added-to-user.asciidoc
@@ -0,0 +1,75 @@
+[[aws-iam-login-profile-added-to-user]]
+=== AWS IAM Login Profile Added to User
+
+Identifies when an AWS IAM login profile is added to a user. Adversaries may add a login profile to an IAM user who typically does not have one and is used only for programmatic access. This can be used to maintain access to the account even if the original access key is rotated or disabled. This is a building block rule and does not generate alerts on its own. It is meant to be used for correlation with other rules to detect suspicious activity.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-aws.cloudtrail-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 10m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS IAM
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
+* Rule Type: BBR
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset: aws.cloudtrail and event.provider: "iam.amazonaws.com"
+    and event.action: "CreateLoginProfile" and event.outcome: success
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Account Manipulation
+** ID: T1098
+** Reference URL: https://attack.mitre.org/techniques/T1098/
+* Sub-technique:
+** Name: Additional Cloud Roles
+** ID: T1098.003
+** Reference URL: https://attack.mitre.org/techniques/T1098/003/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Cloud Accounts
+** ID: T1078.004
+** Reference URL: https://attack.mitre.org/techniques/T1078/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-iam-password-recovery-requested.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-iam-password-recovery-requested.asciidoc
index ca91e8b129..28043f675d 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-iam-password-recovery-requested.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-iam-password-recovery-requested.asciidoc
@@ -5,67 +5,61 @@ Identifies AWS IAM password recovery requests. An adversary may attempt to gain
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.cadosecurity.com/an-ongoing-aws-phishing-campaign/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<aws-iam-password-recovery-requested-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS Signin
+* Use Case: Identity and Access Audit
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Verify whether the user identity, user agent, and/or hostname should be requesting changes in your environment. Password reset attempts from unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:signin.amazonaws.com
-and event.action:PasswordRecoveryRequested and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:signin.amazonaws.com and event.action:PasswordRecoveryRequested and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,37 +71,3 @@ and event.action:PasswordRecoveryRequested and event.outcome:success
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[aws-iam-password-recovery-requested-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:PasswordRecoveryRequested and
-event.provider:signin.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-iam-user-addition-to-group.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-iam-user-addition-to-group.asciidoc
index 3df76db1e6..ada52d2a16 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-iam-user-addition-to-group.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-iam-user-addition-to-group.asciidoc
@@ -5,82 +5,78 @@ Identifies the addition of a user to a specified group in AWS Identity and Acces
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/IAM/latest/APIReference/API_AddUserToGroup.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Credential Access
-* Persistence
-* Investigation Guide
-
-*Version*: 103 (<<aws-iam-user-addition-to-group-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
+* Tactic: Persistence
+* Resources: Investigation Guide
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 209
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Adding users to a specified group may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. User additions from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS IAM User Addition to Group
+*Triage and analysis*
+
+
+
+*Investigating AWS IAM User Addition to Group*
+
 
-AWS Identity and Access Management (IAM) provides fine-grained access control across all of AWS. With IAM, you can specify
-who can access which services and resources, and under which conditions. With IAM policies, you manage permissions to
-your workforce and systems to ensure least-privilege permissions.
+AWS Identity and Access Management (IAM) provides fine-grained access control across all of AWS. With IAM, you can specify who can access which services and resources, and under which conditions. With IAM policies, you manage permissions to your workforce and systems to ensure least-privilege permissions.
 
 This rule looks for the addition of users to a specified user group.
 
-#### Possible investigation steps
+
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Contact the account and resource owners and confirm whether they are aware of this activity.
 - Check if this operation was approved and performed according to the organization's change management policy.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- False positives may occur due to the intended usage of the service. Tuning is needed in order to have higher confidence. Consider adding exceptions — preferably with a combination of user agent and IP address conditions — to reduce noise from onboarding processes and administrator activities.
 
-- False positives may occur due to the intended usage of the service. Tuning is needed in order to have higher
-confidence. Consider adding exceptions — preferably with a combination of user agent and IP address conditions — to
-reduce noise from onboarding processes and administrator activities.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -90,30 +86,27 @@ reduce noise from onboarding processes and administrator activities.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
-- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other
-IAM users.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and
-event.action:AddUserToGroup and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and event.action:AddUserToGroup and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -121,8 +114,6 @@ event.action:AddUserToGroup and event.outcome:success
 ** Name: Credential Access
 ** ID: TA0006
 ** Reference URL: https://attack.mitre.org/tactics/TA0006/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -131,37 +122,3 @@ event.action:AddUserToGroup and event.outcome:success
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[aws-iam-user-addition-to-group-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:AddUserToGroup and event.dataset:aws.cloudtrail and
-event.provider:iam.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-kms-customer-managed-key-disabled-or-scheduled-for-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-kms-customer-managed-key-disabled-or-scheduled-for-deletion.asciidoc
index 49322696a3..d0e7f0ed84 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-kms-customer-managed-key-disabled-or-scheduled-for-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-kms-customer-managed-key-disabled-or-scheduled-for-deletion.asciidoc
@@ -5,68 +5,62 @@ Identifies attempts to disable or schedule the deletion of an AWS KMS Customer M
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/cli/latest/reference/kms/disable-key.html
 * https://docs.aws.amazon.com/cli/latest/reference/kms/schedule-key-deletion.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-* Impact
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS KMS
+* Use Case: Log Auditing
+* Tactic: Impact
 
-*Version*: 1
+*Version*: 106
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Xavier Pich
+* Xavier Pich
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A KMS customer managed key may be disabled or scheduled for deletion by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Key deletions by unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:kms.amazonaws.com and
-event.action:("DisableKey" or "ScheduleKeyDeletion") and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:kms.amazonaws.com and event.action:("DisableKey" or "ScheduleKeyDeletion") and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-management-console-brute-force-of-root-user-identity.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-management-console-brute-force-of-root-user-identity.asciidoc
index 51391b1327..04e2ecd80c 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-management-console-brute-force-of-root-user-identity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-management-console-brute-force-of-root-user-identity.asciidoc
@@ -5,68 +5,60 @@ Identifies a high number of failed authentication attempts to the AWS management
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-20m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<aws-management-console-brute-force-of-root-user-identity-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Automated processes that attempt to authenticate using expired credentials and unbounded retries may lead to false positives.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:signin.amazonaws.com
-and event.action:ConsoleLogin and
-aws.cloudtrail.user_identity.type:Root and event.outcome:failure
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:signin.amazonaws.com and event.action:ConsoleLogin and aws.cloudtrail.user_identity.type:Root and event.outcome:failure
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,22 +70,3 @@ aws.cloudtrail.user_identity.type:Root and event.outcome:failure
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
-
-[[aws-management-console-brute-force-of-root-user-identity-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (7.13.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-management-console-root-login.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-management-console-root-login.asciidoc
index ca7965778e..9c8981453f 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-management-console-root-login.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-management-console-root-login.asciidoc
@@ -5,83 +5,80 @@ Identifies a successful login to the AWS Management Console by the Root user.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Investigation Guide
-
-*Version*: 103 (<<aws-management-console-root-login-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS Signin
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 209
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-It's strongly recommended that the root user is not used for everyday tasks, including the administrative ones. Verify whether the IP address, location, and/or hostname should be logging in as root in your environment. Unfamiliar root logins should be investigated immediately. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS Management Console Root Login
+*Triage and analysis*
 
-The AWS root account is the one identity that has complete access to all AWS services and resources in the account,
-which is created when the AWS account is created. AWS strongly recommends that you do not use the root user for your
-everyday tasks, even the administrative ones. Instead, adhere to the best practice of using the root user only to create
-your first IAM user. Then securely lock away the root user credentials and use them to perform only a few account and
-service management tasks. AWS provides a [list of the tasks that require root user](https://docs.aws.amazon.com/general/latest/gr/root-vs-iam.html#aws_tasks-that-require-root).
+
+
+*Investigating AWS Management Console Root Login*
+
+
+The AWS root account is the one identity that has complete access to all AWS services and resources in the account, which is created when the AWS account is created. AWS strongly recommends that you do not use the root user for your everyday tasks, even the administrative ones. Instead, adhere to the best practice of using the root user only to create your first IAM user. Then securely lock away the root user credentials and use them to perform only a few account and service management tasks. AWS provides a https://docs.aws.amazon.com/general/latest/gr/root-vs-iam.html#aws_tasks-that-require-root[list of the tasks that require root user].
 
 This rule looks for attempts to log in to the AWS Management Console as the root user.
 
-#### Possible investigation steps
+
+*Possible investigation steps*
+
 
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Examine whether this activity is common in the environment by looking for past occurrences on your logs.
-- Consider the source IP address and geolocation for the calling user who issued the command. Do they look normal for the
-  calling user?
+- Consider the source IP address and geolocation for the calling user who issued the command. Do they look normal for the calling user?
 - Examine the commands, API calls, and data management actions performed by the account in the last 24 hours.
 - Contact the account owner and confirm whether they are aware of this activity.
 - If you suspect the account has been compromised, scope potentially compromised assets by tracking access to servers,
 services, and data accessed by the account in the last 24 hours.
 
-### False positive analysis
 
-- The alert can be dismissed if this operation is done under change management and approved according to the
-organization's policy for performing a task that needs this privilege level.
+*False positive analysis*
+
+
+- The alert can be dismissed if this operation is done under change management and approved according to the organization's policy for performing a task that needs this privilege level.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
@@ -91,23 +88,22 @@ organization's policy for performing a task that needs this privilege level.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify if there are any regulatory or legal ramifications related to this activity.
 - Configure multi-factor authentication for the user.
-- Follow security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Follow security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:signin.amazonaws.com
-and event.action:ConsoleLogin and
-aws.cloudtrail.user_identity.type:Root and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:signin.amazonaws.com and event.action:ConsoleLogin and aws.cloudtrail.user_identity.type:Root and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -119,8 +115,6 @@ aws.cloudtrail.user_identity.type:Root and event.outcome:success
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -129,42 +123,3 @@ aws.cloudtrail.user_identity.type:Root and event.outcome:success
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[aws-management-console-root-login-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:ConsoleLogin and event.dataset:aws.cloudtrail and
-event.provider:signin.amazonaws.com and
-aws.cloudtrail.user_identity.type:Root and event.outcome:success
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:ConsoleLogin and event.module:aws and
-event.dataset:aws.cloudtrail and event.provider:signin.amazonaws.com
-and aws.cloudtrail.user_identity.type:Root and event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-rds-cluster-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-rds-cluster-creation.asciidoc
index eedcf275aa..1f42213622 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-rds-cluster-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-rds-cluster-creation.asciidoc
@@ -5,71 +5,64 @@ Identifies the creation of a new Amazon Relational Database Service (RDS) Aurora
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/create-db-cluster.html
 * https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateDBCluster.html
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/create-global-cluster.html
 * https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateGlobalCluster.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-
-*Version*: 101 (<<aws-rds-cluster-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS RDS
+* Use Case: Asset Visibility
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Valid clusters may be created by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Cluster creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.action:(CreateDBCluster or CreateGlobalCluster) and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and event.action:(CreateDBCluster or CreateGlobalCluster) and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,47 +74,7 @@ event.outcome:success
 ** Name: External Remote Services
 ** ID: T1133
 ** Reference URL: https://attack.mitre.org/techniques/T1133/
-
-
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
-
-[[aws-rds-cluster-creation-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:(CreateDBCluster or CreateGlobalCluster) and
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-rds-instance-cluster-stoppage.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-rds-instance-cluster-stoppage.asciidoc
index 49d7ddf4d6..6abfb66e3e 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-rds-instance-cluster-stoppage.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-rds-instance-cluster-stoppage.asciidoc
@@ -5,71 +5,64 @@ Identifies that an Amazon Relational Database Service (RDS) cluster or instance
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/stop-db-cluster.html
 * https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_StopDBCluster.html
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/stop-db-instance.html
 * https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_StopDBInstance.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-
-*Version*: 101 (<<aws-rds-instance-cluster-stoppage-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS RDS
+* Use Case: Asset Visibility
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Valid clusters or instances may be stopped by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Cluster or instance stoppages from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.action:(StopDBCluster or StopDBInstance) and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and event.action:(StopDBCluster or StopDBInstance) and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,35 +74,3 @@ event.outcome:success
 ** Name: Service Stop
 ** ID: T1489
 ** Reference URL: https://attack.mitre.org/techniques/T1489/
-
-[[aws-rds-instance-cluster-stoppage-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:(StopDBCluster or StopDBInstance) and
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.outcome:success
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-rds-instance-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-rds-instance-creation.asciidoc
index 1686c1be7e..9d0fa70a74 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-rds-instance-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-rds-instance-creation.asciidoc
@@ -5,68 +5,62 @@ Identifies the creation of an Amazon Relational Database Service (RDS) Aurora da
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateDBInstance.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-* Persistence
-
-*Version*: 101 (<<aws-rds-instance-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS RDS
+* Use Case: Asset Visibility
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A database instance may be created by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Instances creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.action:CreateDBInstance and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and event.action:CreateDBInstance and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,22 +68,3 @@ event.action:CreateDBInstance and event.outcome:success
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-[[aws-rds-instance-creation-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-rds-security-group-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-rds-security-group-creation.asciidoc
index ee3aa7f291..ff3639eb65 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-rds-security-group-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-rds-security-group-creation.asciidoc
@@ -5,67 +5,61 @@ Identifies the creation of an Amazon Relational Database Service (RDS) Security
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateDBSecurityGroup.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 101 (<<aws-rds-security-group-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS RDS
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-An RDS security group may be created by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Security group creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.action:CreateDBSecurityGroup and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and event.action:CreateDBSecurityGroup and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,22 +71,7 @@ event.action:CreateDBSecurityGroup and event.outcome:success
 ** Name: Create Account
 ** ID: T1136
 ** Reference URL: https://attack.mitre.org/techniques/T1136/
-
-[[aws-rds-security-group-creation-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Cloud Account
+** ID: T1136.003
+** Reference URL: https://attack.mitre.org/techniques/T1136/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-rds-security-group-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-rds-security-group-deletion.asciidoc
index c7fcde3306..a408b76ca5 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-rds-security-group-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-rds-security-group-deletion.asciidoc
@@ -5,67 +5,61 @@ Identifies the deletion of an Amazon Relational Database Service (RDS) Security
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DeleteDBSecurityGroup.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 101 (<<aws-rds-security-group-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS RDS
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-An RDS security group deletion may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Security group deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.action:DeleteDBSecurityGroup and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and event.action:DeleteDBSecurityGroup and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,22 +71,3 @@ event.action:DeleteDBSecurityGroup and event.outcome:success
 ** Name: Account Access Removal
 ** ID: T1531
 ** Reference URL: https://attack.mitre.org/techniques/T1531/
-
-[[aws-rds-security-group-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-rds-snapshot-export.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-rds-snapshot-export.asciidoc
index cd63737dfe..8a445ba0de 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-rds-snapshot-export.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-rds-snapshot-export.asciidoc
@@ -5,68 +5,61 @@ Identifies the export of an Amazon Relational Database Service (RDS) Aurora data
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_StartExportTask.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-* Exfiltration
-
-*Version*: 101 (<<aws-rds-snapshot-export-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Asset Visibility
+* Tactic: Exfiltration
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Exporting snapshots may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Snapshot exports from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.action:StartExportTask and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and event.action:StartExportTask and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,16 +67,3 @@ event.action:StartExportTask and event.outcome:success
 ** Name: Exfiltration
 ** ID: TA0010
 ** Reference URL: https://attack.mitre.org/tactics/TA0010/
-
-[[aws-rds-snapshot-export-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-rds-snapshot-restored.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-rds-snapshot-restored.asciidoc
index 8a318676e3..32710a1730 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-rds-snapshot-restored.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-rds-snapshot-restored.asciidoc
@@ -5,69 +5,62 @@ Identifies when an attempt was made to restore an RDS Snapshot. Snapshots are so
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBInstanceFromDBSnapshot.html
 * https://github.com/RhinoSecurityLabs/pacu/blob/master/pacu/modules/rds__explore_snapshots/main.py
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-* Defense Evasion
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Asset Visibility
+* Tactic: Defense Evasion
 
-*Version*: 101 (<<aws-rds-snapshot-restored-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Restoring snapshots may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Snapshot restoration by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and
-event.action:RestoreDBInstanceFromDBSnapshot and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:rds.amazonaws.com and event.action:RestoreDBInstanceFromDBSnapshot and
+event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,22 +72,7 @@ event.action:RestoreDBInstanceFromDBSnapshot and event.outcome:success
 ** Name: Modify Cloud Compute Infrastructure
 ** ID: T1578
 ** Reference URL: https://attack.mitre.org/techniques/T1578/
-
-[[aws-rds-snapshot-restored-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
-Version 2 (8.0.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Revert Cloud Instance
+** ID: T1578.004
+** Reference URL: https://attack.mitre.org/techniques/T1578/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-redshift-cluster-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-redshift-cluster-creation.asciidoc
index 1af914b762..ab0260bff2 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-redshift-cluster-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-redshift-cluster-creation.asciidoc
@@ -5,68 +5,61 @@ Identifies the creation of an Amazon Redshift cluster. Unexpected creation of th
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/redshift/latest/APIReference/API_CreateCluster.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-* Persistence
-
-*Version*: 101 (<<aws-redshift-cluster-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS Redshift
+* Use Case: Asset Visibility
+* Tactic: Persistence
 
-*Added ({stack} release)*: 8.3.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Valid clusters may be created by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Cluster creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:redshift.amazonaws.com
-and event.action:CreateCluster and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:redshift.amazonaws.com and event.action:CreateCluster and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,16 +67,3 @@ and event.action:CreateCluster and event.outcome:success
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-[[aws-redshift-cluster-creation-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-root-login-without-mfa.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-root-login-without-mfa.asciidoc
index 3190281b82..9dec13ff56 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-root-login-without-mfa.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-root-login-without-mfa.asciidoc
@@ -5,91 +5,84 @@ Identifies attempts to login to AWS as the root user without using multi-factor
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS Route53
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Privilege Escalation
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Investigation Guide
 
-*Version*: 103 (<<aws-root-login-without-mfa-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Some organizations allow login with the root user without MFA, however, this is not considered best practice by AWS and increases the risk of compromised credentials.
 
-==== Investigation guide
 
+*Investigating AWS Root Login Without MFA*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS Root Login Without MFA
+Multi-factor authentication (MFA) in AWS is a simple best practice that adds an extra layer of protection on top of your user name and password. With MFA enabled, when a user signs in to an AWS Management Console, they will be prompted for their user name and password, as well as for an authentication code from their AWS MFA device. Taken together, these multiple factors provide increased security for your AWS account settings and resources.
 
-Multi-factor authentication (MFA) in AWS is a simple best practice that adds an extra layer of protection on top of your
-user name and password. With MFA enabled, when a user signs in to an AWS Management Console, they will be prompted for
-their user name and password, as well as for an authentication code from their AWS MFA device. Taken together, these
-multiple factors provide increased security for your AWS account settings and resources.
+For more information about using MFA in AWS, access the https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa.html[official documentation].
 
-For more information about using MFA in AWS, access the [official documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa.html).
+The AWS root account is the one identity that has complete access to all AWS services and resources in the account, which is created when the AWS account is created. AWS strongly recommends that you do not use the root user for your everyday tasks, even the administrative ones. Instead, adhere to the best practice of using the root user only to create your first IAM user. Then securely lock away the root user credentials and use them to perform only a few account and service management tasks. Amazon provides a https://docs.aws.amazon.com/general/latest/gr/root-vs-iam.html#aws_tasks-that-require-root[list of the tasks that require root user].
 
-The AWS root account is the one identity that has complete access to all AWS services and resources in the account,
-which is created when the AWS account is created. AWS strongly recommends that you do not use the root user for your
-everyday tasks, even the administrative ones. Instead, adhere to the best practice of using the root user only to create
-your first IAM user. Then securely lock away the root user credentials and use them to perform only a few account and
-service management tasks. Amazon provides a [list of the tasks that require root user](https://docs.aws.amazon.com/general/latest/gr/root-vs-iam.html#aws_tasks-that-require-root).
+This rule looks for attempts to log in to AWS as the root user without using multi-factor authentication (MFA), meaning the account is not secured properly.
 
-This rule looks for attempts to log in to AWS as the root user without using multi-factor authentication (MFA), meaning
-the account is not secured properly.
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Examine whether this activity is common in the environment by looking for past occurrences on your logs.
-- Consider the source IP address and geolocation for the calling user who issued the command. Do they look normal for the
-  calling user?
+- Consider the source IP address and geolocation for the calling user who issued the command. Do they look normal for the calling user?
 - Examine the commands, API calls, and data management actions performed by the account in the last 24 hours.
 - Contact the account owner and confirm whether they are aware of this activity.
 - If you suspect the account has been compromised, scope potentially compromised assets by tracking access to servers,
 services, and data accessed by the account in the last 24 hours.
 
-### False positive analysis
 
-- While this activity is not inherently malicious, the root account must use MFA. The security team should address any
-potential benign true positive (B-TP), as this configuration can risk the entire cloud environment.
+*False positive analysis*
+
+
+- While this activity is not inherently malicious, the root account must use MFA. The security team should address any potential benign true positive (B-TP), as this configuration can risk the entire cloud environment.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
@@ -99,25 +92,25 @@ potential benign true positive (B-TP), as this configuration can risk the entire
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify if there are any regulatory or legal ramifications related to this activity.
 - Configure multi-factor authentication for the user.
-- Follow security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Follow security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:signin.amazonaws.com
-and event.action:ConsoleLogin and
-aws.cloudtrail.user_identity.type:Root and
-aws.cloudtrail.console_login.additional_eventdata.mfa_used:false and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:signin.amazonaws.com and event.action:ConsoleLogin and
+  aws.cloudtrail.user_identity.type:Root and
+  aws.cloudtrail.console_login.additional_eventdata.mfa_used:false and
+  event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -129,37 +122,3 @@ event.outcome:success
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[aws-root-login-without-mfa-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:aws and event.dataset:aws.cloudtrail and
-event.provider:signin.amazonaws.com and event.action:ConsoleLogin and
-aws.cloudtrail.user_identity.type:Root and
-aws.cloudtrail.console_login.additional_eventdata.mfa_used:false and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-route-53-domain-transfer-lock-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-route-53-domain-transfer-lock-disabled.asciidoc
index b7ec991bda..3579018948 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-route-53-domain-transfer-lock-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-route-53-domain-transfer-lock-disabled.asciidoc
@@ -5,68 +5,63 @@ Identifies when a transfer lock was removed from a Route 53 domain. It is recomm
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/Route53/latest/APIReference/API_Operations_Amazon_Route_53.html
 * https://docs.aws.amazon.com/Route53/latest/APIReference/API_domains_DisableDomainTransferLock.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-
-*Version*: 101 (<<aws-route-53-domain-transfer-lock-disabled-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS Route53
+* Use Case: Asset Visibility
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A domain transfer lock may be disabled by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Activity from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:route53.amazonaws.com
-and event.action:DisableDomainTransferLock and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:route53.amazonaws.com and event.action:DisableDomainTransferLock and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,22 +73,7 @@ and event.action:DisableDomainTransferLock and event.outcome:success
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-
 * Tactic:
 ** Name: Credential Access
 ** ID: TA0006
 ** Reference URL: https://attack.mitre.org/tactics/TA0006/
-
-[[aws-route-53-domain-transfer-lock-disabled-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-route-53-domain-transferred-to-another-account.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-route-53-domain-transferred-to-another-account.asciidoc
index 6fbe1670db..777e92fc72 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-route-53-domain-transferred-to-another-account.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-route-53-domain-transferred-to-another-account.asciidoc
@@ -5,68 +5,62 @@ Identifies when a request has been made to transfer a Route 53 domain to another
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/Route53/latest/APIReference/API_Operations_Amazon_Route_53.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-
-*Version*: 101 (<<aws-route-53-domain-transferred-to-another-account-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS Route53
+* Use Case: Asset Visibility
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A domain may be transferred to another AWS account by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Domain transfers from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:route53.amazonaws.com
-and event.action:TransferDomainToAnotherAwsAccount and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:route53.amazonaws.com and event.action:TransferDomainToAnotherAwsAccount and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,22 +72,7 @@ event.outcome:success
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-
 * Tactic:
 ** Name: Credential Access
 ** ID: TA0006
 ** Reference URL: https://attack.mitre.org/tactics/TA0006/
-
-[[aws-route-53-domain-transferred-to-another-account-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-route-table-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-route-table-created.asciidoc
index 7396c3fc71..d058cc0b4d 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-route-table-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-route-table-created.asciidoc
@@ -5,71 +5,65 @@ Identifies when an AWS Route Table has been created.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.datadoghq.com/security_platform/default_rules/aws-ec2-route-table-modified/
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateRoute.html
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateRouteTable
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Network Security
-* Persistence
-
-*Version*: 101 (<<aws-route-table-created-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS Route53
+* Use Case: Network Security Monitoring
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Route Tables may be created by a system or network administrators. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Route Table creation by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule. Automated processes that use Terraform may lead to false positives.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:cloudtrail.amazonaws.com and event.action:(CreateRoute
-or CreateRouteTable) and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and event.action:(CreateRoute or CreateRouteTable) and
+event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,29 +71,3 @@ or CreateRouteTable) and event.outcome:success
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-[[aws-route-table-created-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:cloudtrail.amazonaws.com and event.action:(CreateRoute
-or CreateRouteTable) and event.outcome:success
-----------------------------------
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-route-table-modified-or-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-route-table-modified-or-deleted.asciidoc
index a926f78323..6112140f07 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-route-table-modified-or-deleted.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-route-table-modified-or-deleted.asciidoc
@@ -5,22 +5,22 @@ Identifies when an AWS Route Table has been modified or deleted.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/easttimor/aws-incident-response#network-routing
 * https://docs.datadoghq.com/security_platform/default_rules/aws-ec2-route-table-modified/
@@ -30,51 +30,44 @@ Identifies when an AWS Route Table has been modified or deleted.
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DeleteRoute.html
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DisassociateRouteTable.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Network Security
-* Persistence
-
-*Version*: 101 (<<aws-route-table-modified-or-deleted-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS Route53
+* Use Case: Network Security Monitoring
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Route Table could be modified or deleted by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Route Table being modified from unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule. Also automated processes that use Terraform may lead to false positives.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and
-event.provider:cloudtrail.amazonaws.com and event.action:(ReplaceRoute
-or ReplaceRouteTableAssociation or DeleteRouteTable or DeleteRoute or
-DisassociateRouteTable) and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and event.action:(ReplaceRoute or ReplaceRouteTableAssociation or
+DeleteRouteTable or DeleteRoute or DisassociateRouteTable) and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -82,22 +75,3 @@ DisassociateRouteTable) and event.outcome:success
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-[[aws-route-table-modified-or-deleted-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-route53-private-hosted-zone-associated-with-a-vpc.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-route53-private-hosted-zone-associated-with-a-vpc.asciidoc
index 455b41fa13..98dccc62dd 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-route53-private-hosted-zone-associated-with-a-vpc.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-route53-private-hosted-zone-associated-with-a-vpc.asciidoc
@@ -5,67 +5,62 @@ Identifies when a Route53 private hosted zone has been associated with VPC.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/Route53/latest/APIReference/API_AssociateVPCWithHostedZone.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS Route53
+* Use Case: Asset Visibility
+* Tactic: Persistence
 
-*Version*: 101 (<<aws-route53-private-hosted-zone-associated-with-a-vpc-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A private hosted zone may be asssociated with a VPC by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:route53.amazonaws.com
-and event.action:AssociateVPCWithHostedZone and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:route53.amazonaws.com and event.action:AssociateVPCWithHostedZone and
+event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,22 +72,3 @@ and event.action:AssociateVPCWithHostedZone and event.outcome:success
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[aws-route53-private-hosted-zone-associated-with-a-vpc-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:route53.amazonaws.com
-and event.action:AssociateVPCWithHostedZone and event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-s3-bucket-configuration-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-s3-bucket-configuration-deletion.asciidoc
index 1cbfc38206..eca05212e7 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-s3-bucket-configuration-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-s3-bucket-configuration-deletion.asciidoc
@@ -5,22 +5,22 @@ Identifies the deletion of various Amazon Simple Storage Service (S3) bucket con
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketPolicy.html
 * https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketReplication.html
@@ -28,50 +28,44 @@ Identifies the deletion of various Amazon Simple Storage Service (S3) bucket con
 * https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketEncryption.html
 * https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-
-*Version*: 101 (<<aws-s3-bucket-configuration-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Asset Visibility
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Bucket components may be deleted by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Bucket component deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:aws.cloudtrail and event.provider:s3.amazonaws.com and
-event.action:(DeleteBucketPolicy or DeleteBucketReplication or
-DeleteBucketCors or DeleteBucketEncryption or
-DeleteBucketLifecycle) and event.outcome:success
-----------------------------------
+  event.action:(DeleteBucketPolicy or DeleteBucketReplication or DeleteBucketCors or
+                DeleteBucketEncryption or DeleteBucketLifecycle)
+  and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,42 +74,6 @@ DeleteBucketLifecycle) and event.outcome:success
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
 * Technique:
-** Name: Indicator Removal on Host
+** Name: Indicator Removal
 ** ID: T1070
 ** Reference URL: https://attack.mitre.org/techniques/T1070/
-
-[[aws-s3-bucket-configuration-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:(DeleteBucketPolicy or DeleteBucketReplication or
-DeleteBucketCors or DeleteBucketEncryption or DeleteBucketLifecycle)
-and event.dataset:aws.cloudtrail and event.provider:s3.amazonaws.com
-and event.outcome:success
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-s3-bucket-enumeration-or-brute-force.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-s3-bucket-enumeration-or-brute-force.asciidoc
new file mode 100644
index 0000000000..83d4a0e161
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/aws-s3-bucket-enumeration-or-brute-force.asciidoc
@@ -0,0 +1,147 @@
+[[aws-s3-bucket-enumeration-or-brute-force]]
+=== AWS S3 Bucket Enumeration or Brute Force
+
+Identifies a high number of failed S3 operations from a single source and account (or anonymous account) within a short timeframe. This activity can be indicative of attempting to cause an increase in billing to an account for excessive random operations, cause resource exhaustion, or enumerating bucket names for discovery.
+
+*Rule type*: esql
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-10m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://medium.com/@maciej.pocwierz/how-an-empty-s3-bucket-can-make-your-aws-bill-explode-934a383cb8b1
+* https://docs.aws.amazon.com/cli/latest/reference/s3api/
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS S3
+* Resources: Investigation Guide
+* Use Case: Log Auditing
+* Tactic: Impact
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating AWS S3 Bucket Enumeration or Brute Force*
+
+
+AWS S3 buckets can be be brute forced to cause financial impact against the resource owner. What makes this even riskier is that even private, locked down buckets can still trigger a potential cost, even with an "Access Denied", while also being accessible from unauthenticated, anonymous accounts. This also appears to work on several or all https://docs.aws.amazon.com/cli/latest/reference/s3api/[operations] (GET, PUT, list-objects, etc.). Additionally, buckets are trivially discoverable by default as long as the bucket name is known, making it vulnerable to enumeration for discovery.
+
+Attackers may attempt to enumerate names until a valid bucket is discovered and then pivot to cause financial impact, enumerate for more information, or brute force in other ways to attempt to exfil data.
+
+
+*Possible investigation steps*
+
+
+- Examine the history of the operation requests from the same `source.address` and `cloud.account.id` to determine if there is other suspicious activity.
+- Review similar requests and look at the `user.agent` info to ascertain the source of the requests (though do not overly rely on this since it is controlled by the requestor).
+- Review other requests to the same `aws.s3.object.key` as well as other `aws.s3.object.key` accessed by the same `cloud.account.id` or `source.address`.
+- Investigate other alerts associated with the user account during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, or network administrator activity.
+- Examine the request parameters. These may indicate the source of the program or the nature of the task being performed when the error occurred.
+    - Check whether the error is related to unsuccessful attempts to enumerate or access objects, data, or secrets.
+- Considering the source IP address and geolocation of the user who issued the command:
+    - Do they look normal for the calling user?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
+- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal time of day?
+- Contact the account owner and confirm whether they are aware of this activity if suspicious.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
+
+- Verify the `source.address` and `cloud.account.id` - there are some valid operations from within AWS directly that can cause failures and false positives. Additionally, failed automation can also caeuse false positives, but should be identifiable by reviewing the `source.address` and `cloud.account.id`.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
+- Consider enabling multi-factor authentication for users.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
+- Take the actions needed to return affected systems, data, or services to their normal operational levels.
+- Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+- Check for PutBucketPolicy event actions as well to see if they have been tampered with. While we monitor for denied, a single successful action to add a backdoor into the bucket via policy updates (however they got permissions) may be critical to identify during TDIR.
+
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+from logs-aws.cloudtrail*
+| where event.provider == "s3.amazonaws.com" and aws.cloudtrail.error_code == "AccessDenied"
+| stats failed_requests = count(*) by tls.client.server_name, source.address, cloud.account.id
+  // can modify the failed request count or tweak time window to fit environment
+  // can add `not cloud.account.id in (KNOWN)` or specify in exceptions
+| where failed_requests > 40
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Financial Theft
+** ID: T1657
+** Reference URL: https://attack.mitre.org/techniques/T1657/
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Cloud Infrastructure Discovery
+** ID: T1580
+** Reference URL: https://attack.mitre.org/techniques/T1580/
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Data from Cloud Storage
+** ID: T1530
+** Reference URL: https://attack.mitre.org/techniques/T1530/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-saml-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-saml-activity.asciidoc
index 643fd0a857..5c38d0195b 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-saml-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-saml-activity.asciidoc
@@ -5,69 +5,62 @@ Identifies when SAML activity has occurred in AWS. An adversary could manipulate
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/IAM/latest/APIReference/API_UpdateSAMLProvider.html
 * https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithSAML.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Identity and Access
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Identity and Access Audit
+* Tactic: Defense Evasion
 
-*Version*: 101 (<<aws-saml-activity-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-SAML Provider could be updated by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. SAML Provider updates by unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
-event.dataset:aws.cloudtrail and event.provider:(iam.amazonaws.com or
-sts.amazonaws.com) and event.action:(Assumerolewithsaml or
+event.dataset:aws.cloudtrail and event.provider:(iam.amazonaws.com or sts.amazonaws.com) and event.action:(Assumerolewithsaml or
 UpdateSAMLProvider) and event.outcome:success
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,8 +72,10 @@ UpdateSAMLProvider) and event.outcome:success
 ** Name: Use Alternate Authentication Material
 ** ID: T1550
 ** Reference URL: https://attack.mitre.org/techniques/T1550/
-
-
+* Sub-technique:
+** Name: Application Access Token
+** ID: T1550.001
+** Reference URL: https://attack.mitre.org/techniques/T1550/001/
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -89,26 +84,3 @@ UpdateSAMLProvider) and event.outcome:success
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[aws-saml-activity-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:(iam.amazonaws.com or
-sts.amazonaws.com) and event.action:(Assumerolewithsaml or
-UpdateSAMLProvider) and event.outcome:success
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-security-group-configuration-change-detection.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-security-group-configuration-change-detection.asciidoc
index 079699dc7a..07f79c1ced 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-security-group-configuration-change-detection.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-security-group-configuration-change-detection.asciidoc
@@ -5,70 +5,64 @@ Identifies a change to an AWS Security Group Configuration. A security group is
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2-security-groups.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Network Security
-
-*Version*: 101 (<<aws-security-group-configuration-change-detection-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS EC2
+* Use Case: Network Security Monitoring
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.15.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A security group may be created by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Security group creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.action:(AuthorizeSecurityGroupEgress or CreateSecurityGroup or
-ModifyInstanceAttribute or ModifySecurityGroupRules or
-RevokeSecurityGroupEgress or RevokeSecurityGroupIngress) and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and event.action:(AuthorizeSecurityGroupEgress or
+CreateSecurityGroup or ModifyInstanceAttribute or ModifySecurityGroupRules or RevokeSecurityGroupEgress or
+RevokeSecurityGroupIngress) and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,8 +70,6 @@ event.outcome:success
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -86,43 +78,7 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-security-group-configuration-change-detection-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.action:(AuthorizeSecurityGroupEgress or CreateSecurityGroup or
-ModifyInstanceAttribute or ModifySecurityGroupRules or
-RevokeSecurityGroupEgress or RevokeSecurityGroupIngress) and
-event.outcome:success
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:iam.amazonaws.com and
-event.action:(AuthorizeSecurityGroupEgress or CreateSecurityGroup or
-ModifyInstanceAttribute or ModifySecurityGroupRules or
-RevokeSecurityGroupEgress or RevokeSecurityGroupIngress) and
-event.outcome:success
-----------------------------------
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-security-token-service-sts-assumerole-usage.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-security-token-service-sts-assumerole-usage.asciidoc
index b0f74f5beb..26946a1974 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-security-token-service-sts-assumerole-usage.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-security-token-service-sts-assumerole-usage.asciidoc
@@ -5,69 +5,62 @@ Identifies the use of AssumeRole. AssumeRole returns a set of temporary security
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Identity and Access
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS STS
+* Use Case: Identity and Access Audit
+* Tactic: Privilege Escalation
 
-*Version*: 101 (<<aws-security-token-service-sts-assumerole-usage-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Automated processes that use Terraform may lead to false positives.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:sts.amazonaws.com and
-event.action:AssumedRole and
-aws.cloudtrail.user_identity.session_context.session_issuer.type:Role
-and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:sts.amazonaws.com and event.action:AssumedRole and
+aws.cloudtrail.user_identity.session_context.session_issuer.type:Role and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,8 +72,6 @@ and event.outcome:success
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-
 * Tactic:
 ** Name: Lateral Movement
 ** ID: TA0008
@@ -89,27 +80,7 @@ and event.outcome:success
 ** Name: Use Alternate Authentication Material
 ** ID: T1550
 ** Reference URL: https://attack.mitre.org/techniques/T1550/
-
-[[aws-security-token-service-sts-assumerole-usage-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:sts.amazonaws.com and
-event.action:AssumedRole and
-aws.cloudtrail.user_identity.session_context.session_issuer.type:Role
-and event.outcome:success
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Application Access Token
+** ID: T1550.001
+** Reference URL: https://attack.mitre.org/techniques/T1550/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-sts-getsessiontoken-abuse.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-sts-getsessiontoken-abuse.asciidoc
index f53a713f82..188924f406 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-sts-getsessiontoken-abuse.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-sts-getsessiontoken-abuse.asciidoc
@@ -5,68 +5,62 @@ Identifies the suspicious use of GetSessionToken. Tokens could be created and us
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.aws.amazon.com/STS/latest/APIReference/API_GetSessionToken.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Identity and Access
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS STS
+* Use Case: Identity and Access Audit
+* Tactic: Privilege Escalation
 
-*Version*: 101 (<<aws-sts-getsessiontoken-abuse-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-GetSessionToken may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. GetSessionToken from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
-event.dataset:aws.cloudtrail and event.provider:sts.amazonaws.com and
-event.action:GetSessionToken and
+event.dataset:aws.cloudtrail and event.provider:sts.amazonaws.com and event.action:GetSessionToken and
 aws.cloudtrail.user_identity.type:IAMUser and event.outcome:success
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,8 +72,6 @@ aws.cloudtrail.user_identity.type:IAMUser and event.outcome:success
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-
 * Tactic:
 ** Name: Lateral Movement
 ** ID: TA0008
@@ -88,23 +80,7 @@ aws.cloudtrail.user_identity.type:IAMUser and event.outcome:success
 ** Name: Use Alternate Authentication Material
 ** ID: T1550
 ** Reference URL: https://attack.mitre.org/techniques/T1550/
-
-[[aws-sts-getsessiontoken-abuse-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:sts.amazonaws.com and
-event.action:GetSessionToken and
-aws.cloudtrail.user_identity.type:IAMUser and event.outcome:success
-----------------------------------
-
+* Sub-technique:
+** Name: Application Access Token
+** ID: T1550.001
+** Reference URL: https://attack.mitre.org/techniques/T1550/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-vpc-flow-logs-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-vpc-flow-logs-deletion.asciidoc
index b7de6a6d41..111da1075a 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-vpc-flow-logs-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-vpc-flow-logs-deletion.asciidoc
@@ -5,66 +5,62 @@ Identifies the deletion of one or more flow logs in AWS Elastic Compute Cloud (E
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/delete-flow-logs.html
 * https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DeleteFlowLogs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Log Auditing
+* Resources: Investigation Guide
+* Tactic: Defense Evasion
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-* Investigation Guide
 
-*Version*: 103 (<<aws-vpc-flow-logs-deletion-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Flow log deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating AWS VPC Flow Logs Deletion*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating AWS VPC Flow Logs Deletion
+VPC Flow Logs is an AWS feature that enables you to capture information about the IP traffic going to and from network interfaces in your virtual private cloud (VPC). Flow log data can be published to Amazon CloudWatch Logs or Amazon S3.
 
-VPC Flow Logs is an AWS feature that enables you to capture information about the IP traffic going to and from network
-interfaces in your virtual private cloud (VPC). Flow log data can be published to Amazon CloudWatch Logs or Amazon S3.
+This rule identifies the deletion of VPC flow logs using the API `DeleteFlowLogs` action. Attackers can do this to cover their tracks and impact security monitoring that relies on this source.
 
-This rule identifies the deletion of VPC flow logs using the API `DeleteFlowLogs` action. Attackers can do this to cover
-their tracks and impact security monitoring that relies on this source.
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
@@ -72,21 +68,20 @@ their tracks and impact security monitoring that relies on this source.
 - Check if this operation was approved and performed according to the organization's change management policy.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and IP address conditions.
+- Administrators may rotate these logs after a certain period as part of their retention policy or after importing them to a SIEM.
 
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and IP address conditions.
-- Administrators may rotate these logs after a certain period as part of their retention policy or after importing them
-to a SIEM.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -96,30 +91,28 @@ to a SIEM.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and
-event.action:DeleteFlowLogs and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and event.action:DeleteFlowLogs and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -131,39 +124,7 @@ event.action:DeleteFlowLogs and event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-vpc-flow-logs-deletion-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Rule name changed from: AWS EC2 Flow Log Deletion
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:DeleteFlowLogs and event.dataset:aws.cloudtrail and
-event.provider:ec2.amazonaws.com and event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-waf-access-control-list-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-waf-access-control-list-deletion.asciidoc
index ba6b9624bf..56e2ae3af6 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-waf-access-control-list-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-waf-access-control-list-deletion.asciidoc
@@ -5,68 +5,61 @@ Identifies the deletion of a specified AWS Web Application Firewall (WAF) access
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/waf-regional/delete-web-acl.html
 * https://docs.aws.amazon.com/waf/latest/APIReference/API_wafRegional_DeleteWebACL.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Network Security
-
-*Version*: 101 (<<aws-waf-access-control-list-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Network Security Monitoring
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Firewall ACL's may be deleted by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Web ACL deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.action:DeleteWebACL and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.action:DeleteWebACL and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,40 +71,7 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-waf-access-control-list-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:DeleteWebACL and event.dataset:aws.cloudtrail and
-event.outcome:success
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/aws-waf-rule-or-rule-group-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/aws-waf-rule-or-rule-group-deletion.asciidoc
index bf214030e1..6f6b1f6733 100644
--- a/docs/detections/prebuilt-rules/rule-details/aws-waf-rule-or-rule-group-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/aws-waf-rule-or-rule-group-deletion.asciidoc
@@ -5,69 +5,61 @@ Identifies the deletion of a specified AWS Web Application Firewall (WAF) rule o
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
-* logs-aws*
+* logs-aws.cloudtrail-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://awscli.amazonaws.com/v2/documentation/api/latest/reference/waf/delete-rule-group.html
 * https://docs.aws.amazon.com/waf/latest/APIReference/API_waf_DeleteRuleGroup.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* AWS
-* Continuous Monitoring
-* SecOps
-* Network Security
-
-*Version*: 101 (<<aws-waf-rule-or-rule-group-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Use Case: Network Security Monitoring
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-WAF rules or rule groups may be deleted by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Rule deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.provider:(waf.amazonaws.com or
-waf-regional.amazonaws.com or wafv2.amazonaws.com) and
-event.action:(DeleteRule or DeleteRuleGroup) and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:aws.cloudtrail and event.provider:(waf.amazonaws.com or waf-regional.amazonaws.com or wafv2.amazonaws.com) and event.action:(DeleteRule or DeleteRuleGroup) and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,49 +71,7 @@ event.action:(DeleteRule or DeleteRuleGroup) and event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[aws-waf-rule-or-rule-group-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 10 (8.4.0 release)::
-* Formatting only
-
-Version 8 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:aws.cloudtrail and event.action:(DeleteRule or
-DeleteRuleGroup) and event.outcome:success
-----------------------------------
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:aws and event.dataset:aws.cloudtrail and
-event.action:(DeleteRule or DeleteRuleGroup) and event.outcome:success
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-active-directory-high-risk-sign-in.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-active-directory-high-risk-sign-in.asciidoc
index 5567cc8263..529072efc1 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-active-directory-high-risk-sign-in.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-active-directory-high-risk-sign-in.asciidoc
@@ -5,7 +5,7 @@ Identifies high risk Azure Active Directory (AD) sign-ins by leveraging Microsof
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,69 +14,73 @@ Identifies high risk Azure Active Directory (AD) sign-ins by leveraging Microsof
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/howto-conditional-access-policy-risk
 * https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/overview-identity-protection
 * https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/howto-identity-protection-investigate-risk
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Investigation Guide
-
-*Version*: 103 (<<azure-active-directory-high-risk-sign-in-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Willem D'Haese
+* Elastic
+* Willem D'Haese
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Azure Active Directory High Risk Sign-in
+*Triage and analysis*
+
+
+
+*Investigating Azure Active Directory High Risk Sign-in*
+
 
 Microsoft Identity Protection is an Azure AD security tool that detects various types of identity risks and attacks.
 
 This rule identifies events produced by Microsoft Identity Protection with high risk levels or high aggregated risk level.
 
-#### Possible investigation steps
 
-- Identify the Risk Detection that triggered the event. A list with descriptions can be found [here](https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/concept-identity-protection-risks#risk-types-and-detection).
+*Possible investigation steps*
+
+
+- Identify the Risk Detection that triggered the event. A list with descriptions can be found https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/concept-identity-protection-risks#risk-types-and-detection[here].
 - Identify the user account involved and validate whether the suspicious activity is normal for that user.
   - Consider the source IP address and geolocation for the involved user account. Do they look normal?
   - Consider the device used to sign in. Is it registered and compliant?
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Check if this operation was approved and performed according to the organization's change management policy.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
 
-### False positive analysis
 
-If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and device conditions.
+If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and device conditions.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -86,31 +90,31 @@ combination of user and device conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
-- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other
-IAM users.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
-- Follow security best practices [outlined](https://docs.microsoft.com/en-us/azure/security/fundamentals/identity-management-best-practices) by Microsoft.
+- Follow security best practices https://docs.microsoft.com/en-us/azure/security/fundamentals/identity-management-best-practices[outlined] by Microsoft.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+Note that details for `azure.signinlogs.properties.risk_level_during_signin` and `azure.signinlogs.properties.risk_level_aggregated`
+are only available for Azure AD Premium P2 customers. All other customers will be returned `hidden`.
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:azure.signinlogs and
-(azure.signinlogs.properties.risk_level_during_signin:high or
-azure.signinlogs.properties.risk_level_aggregated:high) and
-event.outcome:(success or Success)
-----------------------------------
+  (azure.signinlogs.properties.risk_level_during_signin:high or azure.signinlogs.properties.risk_level_aggregated:high) and
+  event.outcome:(success or Success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -122,29 +126,3 @@ event.outcome:(success or Success)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[azure-active-directory-high-risk-sign-in-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (7.15.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.signinlogs and
-azure.signinlogs.properties.risk_level_during_signin:high and
-event.outcome:(success or Success)
-----------------------------------
-
-Version 2 (7.13.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-active-directory-high-risk-user-sign-in-heuristic.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-active-directory-high-risk-user-sign-in-heuristic.asciidoc
index 8ee40cc5c4..cfe91e75a9 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-active-directory-high-risk-user-sign-in-heuristic.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-active-directory-high-risk-user-sign-in-heuristic.asciidoc
@@ -5,7 +5,7 @@ Identifies high risk Azure Active Directory (AD) sign-ins by leveraging Microsof
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,71 +14,73 @@ Identifies high risk Azure Active Directory (AD) sign-ins by leveraging Microsof
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/active-directory/reports-monitoring/reference-azure-monitor-sign-ins-log-schema
 * https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/overview-identity-protection
 * https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/howto-identity-protection-investigate-risk
 * https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/howto-identity-protection-investigate-risk#investigation-framework
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Investigation Guide
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Initial Access
 
-*Version*: 103 (<<azure-active-directory-high-risk-user-sign-in-heuristic-history, version history>>)
+*Version*: 105
 
-*Added ({stack} release)*: 8.0.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Azure Active Directory High Risk User Sign-in Heuristic
+*Triage and analysis*
+
+
+
+*Investigating Azure Active Directory High Risk User Sign-in Heuristic*
+
 
 Microsoft Identity Protection is an Azure AD security tool that detects various types of identity risks and attacks.
 
-This rule identifies events produced by the Microsoft Identity Protection with a risk state equal to `confirmedCompromised`
-or `atRisk`.
+This rule identifies events produced by the Microsoft Identity Protection with a risk state equal to `confirmedCompromised` or `atRisk`.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Identify the Risk Detection that triggered the event. A list with descriptions can be found [here](https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/concept-identity-protection-risks#risk-types-and-detection).
+- Identify the Risk Detection that triggered the event. A list with descriptions can be found https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/concept-identity-protection-risks#risk-types-and-detection[here].
 - Identify the user account involved and validate whether the suspicious activity is normal for that user.
   - Consider the source IP address and geolocation for the involved user account. Do they look normal?
   - Consider the device used to sign in. Is it registered and compliant?
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Check if this operation was approved and performed according to the organization's change management policy.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and device conditions.
 
-If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and device conditions.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -88,30 +90,27 @@ combination of user and device conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
-- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other
-IAM users.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
-- Follow security best practices [outlined](https://docs.microsoft.com/en-us/azure/security/fundamentals/identity-management-best-practices) by Microsoft.
+- Follow security best practices https://docs.microsoft.com/en-us/azure/security/fundamentals/identity-management-best-practices[outlined] by Microsoft.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:azure.signinlogs and
-azure.signinlogs.properties.risk_state:("confirmedCompromised" or
-"atRisk") and event.outcome:(success or Success)
-----------------------------------
+  azure.signinlogs.properties.risk_state:("confirmedCompromised" or "atRisk") and event.outcome:(success or Success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -123,16 +122,3 @@ azure.signinlogs.properties.risk_state:("confirmedCompromised" or
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[azure-active-directory-high-risk-user-sign-in-heuristic-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-active-directory-powershell-sign-in.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-active-directory-powershell-sign-in.asciidoc
index 13c5c9ef8d..ec0bfa36ee 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-active-directory-powershell-sign-in.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-active-directory-powershell-sign-in.asciidoc
@@ -5,7 +5,7 @@ Identifies a sign-in using the Azure Active Directory PowerShell module. PowerSh
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,76 +14,70 @@ Identifies a sign-in using the Azure Active Directory PowerShell module. PowerSh
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://msrc-blog.microsoft.com/2020/12/13/customer-guidance-on-recent-nation-state-cyber-attacks/
 * https://docs.microsoft.com/en-us/microsoft-365/enterprise/connect-to-microsoft-365-powershell?view=o365-worldwide
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Initial Access
+
+*Version*: 105
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Investigation Guide
 
-*Version*: 103 (<<azure-active-directory-powershell-sign-in-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Sign-ins using PowerShell may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be signing into your environment. Sign-ins from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating Azure Active Directory PowerShell Sign-in*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Azure Active Directory PowerShell Sign-in
+Azure Active Directory PowerShell for Graph (Azure AD PowerShell) is a module IT professionals commonly use to manage their Azure Active Directory. The cmdlets in the Azure AD PowerShell module enable you to retrieve data from the directory, create new objects in the directory, update existing objects, remove objects, as well as configure the directory and its features.
+
+This rule identifies sign-ins that use the Azure Active Directory PowerShell module, which can indicate unauthorized access if done outside of IT or engineering.
 
-Azure Active Directory PowerShell for Graph (Azure AD PowerShell) is a module IT professionals commonly use to manage
-their Azure Active Directory. The cmdlets in the Azure AD PowerShell module enable you to retrieve data from the
-directory, create new objects in the directory, update existing objects, remove objects, as well as configure the
-directory and its features.
 
-This rule identifies sign-ins that use the Azure Active Directory PowerShell module, which can indicate unauthorized
-access if done outside of IT or engineering.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Evaluate whether the user needs to access Azure AD using PowerShell to complete its tasks.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Consider the source IP address and geolocation for the involved user account. Do they look normal?
 - Contact the account owner and confirm whether they are aware of this activity.
-- Investigate suspicious actions taken by the user using the module, for example, modifications in security settings
-that weakens the security policy, persistence-related tasks, and data access.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- Investigate suspicious actions taken by the user using the module, for example, modifications in security settings that weakens the security policy, persistence-related tasks, and data access.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
+
+- If this activity is expected and noisy in your environment, consider adding IT, Engineering, and other authorized users as exceptions — preferably with a combination of user and device conditions.
 
-### False positive analysis
 
-- If this activity is expected and noisy in your environment, consider adding IT, Engineering, and other authorized users
-as exceptions — preferably with a combination of user and device conditions.
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -93,32 +87,28 @@ as exceptions — preferably with a combination of user and device conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
-- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other
-IAM users.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
-- Follow security best practices [outlined](https://docs.microsoft.com/en-us/azure/security/fundamentals/identity-management-best-practices) by Microsoft.
+- Follow security best practices https://docs.microsoft.com/en-us/azure/security/fundamentals/identity-management-best-practices[outlined] by Microsoft.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:azure.signinlogs and
-azure.signinlogs.properties.app_display_name:"Azure Active Directory
-PowerShell" and
-azure.signinlogs.properties.token_issuer_type:AzureAD and
-event.outcome:(success or Success)
-----------------------------------
+  azure.signinlogs.properties.app_display_name:"Azure Active Directory PowerShell" and
+  azure.signinlogs.properties.token_issuer_type:AzureAD and event.outcome:(success or Success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -130,25 +120,7 @@ event.outcome:(success or Success)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[azure-active-directory-powershell-sign-in-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Cloud Accounts
+** ID: T1078.004
+** Reference URL: https://attack.mitre.org/techniques/T1078/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-ad-global-administrator-role-assigned.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-ad-global-administrator-role-assigned.asciidoc
index bb310074ee..d3b938651f 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-ad-global-administrator-role-assigned.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-ad-global-administrator-role-assigned.asciidoc
@@ -5,7 +5,7 @@ In Azure Active Directory (Azure AD), permissions to manage resources are assign
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,57 +14,52 @@ In Azure Active Directory (Azure AD), permissions to manage resources are assign
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/active-directory/roles/permissions-reference#global-administrator
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<azure-ad-global-administrator-role-assigned-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.auditlogs and
-azure.auditlogs.properties.category:RoleManagement and
-azure.auditlogs.operation_name:"Add member to role" and azure.auditlog
-s.properties.target_resources.0.modified_properties.1.new_value:"\"Glo
-bal Administrator\""
+[source, js]
 ----------------------------------
+event.dataset:azure.auditlogs and azure.auditlogs.properties.category:RoleManagement and
+azure.auditlogs.operation_name:"Add member to role" and
+azure.auditlogs.properties.target_resources.0.modified_properties.1.new_value:"\"Global Administrator\""
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,19 +71,7 @@ bal Administrator\""
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[azure-ad-global-administrator-role-assigned-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Additional Cloud Roles
+** ID: T1098.003
+** Reference URL: https://attack.mitre.org/techniques/T1098/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-alert-suppression-rule-created-or-modified.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-alert-suppression-rule-created-or-modified.asciidoc
index 3088d81dcb..4b5dc4df05 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-alert-suppression-rule-created-or-modified.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-alert-suppression-rule-created-or-modified.asciidoc
@@ -5,7 +5,7 @@ Identifies the creation of suppression rules in Azure. Suppression rules are a m
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,60 +14,52 @@ Identifies the creation of suppression rules in Azure. Suppression rules are a m
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations
 * https://docs.microsoft.com/en-us/rest/api/securitycenter/alerts-suppression-rules/update
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Version*: 101 (<<azure-alert-suppression-rule-created-or-modified-history, version history>>)
+*Version*: 102
 
-*Added ({stack} release)*: 8.0.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Suppression Rules can be created legitimately by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Suppression Rules created by unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.SECURITY/ALERTSSUPPRESSIONRULES/WRITE" and event.outcome:
-"success"
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.SECURITY/ALERTSSUPPRESSIONRULES/WRITE" and
+event.outcome: "success"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,26 +71,3 @@ event.dataset:azure.activitylogs and azure.activitylogs.operation_name
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[azure-alert-suppression-rule-created-or-modified-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.SECURITY/ALERTSSUPPRESSIONRULES/WRITE" and event.outcome:
-"success"
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-application-credential-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-application-credential-modification.asciidoc
index ebc700fc5f..5cc744d3f3 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-application-credential-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-application-credential-modification.asciidoc
@@ -5,7 +5,7 @@ Identifies when a new credential is added to an application in Azure. An applica
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,50 @@ Identifies when a new credential is added to an application in Azure. An applica
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://msrc-blog.microsoft.com/2020/12/13/customer-guidance-on-recent-nation-state-cyber-attacks/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<azure-application-credential-modification-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Application credential additions may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Application credential additions from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.auditlogs and
-azure.auditlogs.operation_name:"Update application - Certificates and
-secrets management" and event.outcome:(success or Success)
+[source, js]
 ----------------------------------
+event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Update application - Certificates and secrets management" and event.outcome:(success or Success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,25 +69,7 @@ secrets management" and event.outcome:(success or Success)
 ** Name: Use Alternate Authentication Material
 ** ID: T1550
 ** Reference URL: https://attack.mitre.org/techniques/T1550/
-
-[[azure-application-credential-modification-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Application Access Token
+** ID: T1550.001
+** Reference URL: https://attack.mitre.org/techniques/T1550/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-automation-account-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-automation-account-created.asciidoc
index 6d8f5a5ccf..519032bb63 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-automation-account-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-automation-account-created.asciidoc
@@ -5,7 +5,7 @@ Identifies when an Azure Automation account is created. Azure Automation account
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,58 +14,53 @@ Identifies when an Azure Automation account is created. Azure Automation account
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://powerzure.readthedocs.io/en/latest/Functions/operational.html#create-backdoor
 * https://github.com/hausec/PowerZure
 * https://posts.specterops.io/attacking-azure-azure-ad-and-introducing-powerzure-ca70b330511a
 * https://azure.microsoft.com/en-in/blog/azure-automation-runbook-management/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<azure-automation-account-created-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WRITE" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WRITE" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,8 +72,6 @@ event.outcome:(Success or success)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -87,42 +80,3 @@ event.outcome:(Success or success)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[azure-automation-account-created-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WRITE and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WRITE and
-event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-automation-runbook-created-or-modified.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-automation-runbook-created-or-modified.asciidoc
index 639c4a4344..4880ac8a61 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-automation-runbook-created-or-modified.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-automation-runbook-created-or-modified.asciidoc
@@ -5,7 +5,7 @@ Identifies when an Azure Automation runbook is created or modified. An adversary
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,100 +14,57 @@ Identifies when an Azure Automation runbook is created or modified. An adversary
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://powerzure.readthedocs.io/en/latest/Functions/operational.html#create-backdoor
 * https://github.com/hausec/PowerZure
 * https://posts.specterops.io/attacking-azure-azure-ad-and-introducing-powerzure-ca70b330511a
 * https://azure.microsoft.com/en-in/blog/azure-automation-runbook-management/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<azure-automation-runbook-created-or-modified-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Configuration Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
-
 
-[source,markdown]
-----------------------------------
-
-----------------------------------
-
-
-==== Rule query
+==== Investigation guide
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and
-azure.activitylogs.operation_name: (
-"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/DRAFT/WRITE" or
-"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/WRITE" or
-"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/PUBLISH/ACTION" )
-and event.outcome:(Success or success)
-----------------------------------
 
 
-[[azure-automation-runbook-created-or-modified-history]]
-==== Rule version history
+==== Setup
 
-Version 101 (8.6.0 release)::
-* Formatting only
 
-Version 100 (8.5.0 release)::
-* Formatting only
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
-Version 7 (8.4.0 release)::
-* Formatting only
+==== Rule query
 
-Version 5 (7.13.0 release)::
-* Formatting only
 
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:(MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/DRAFT/WRITE or
-MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/WRITE or
-MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/PUBLISH/ACTION) and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
+event.dataset:azure.activitylogs and
+  azure.activitylogs.operation_name:
+  (
+    "MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/DRAFT/WRITE" or
+    "MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/WRITE" or
+    "MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/PUBLISH/ACTION"
+  ) and
+  event.outcome:(Success or success)
 
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
 ----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:(MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/DRAFT/WRITE or
-MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/WRITE or
-MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/PUBLISH/ACTION) and
-event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-automation-runbook-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-automation-runbook-deleted.asciidoc
index 1021cad802..73fef69a8c 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-automation-runbook-deleted.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-automation-runbook-deleted.asciidoc
@@ -5,7 +5,7 @@ Identifies when an Azure Automation runbook is deleted. An adversary may delete
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,55 @@ Identifies when an Azure Automation runbook is deleted. An adversary may delete
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://powerzure.readthedocs.io/en/latest/Functions/operational.html#create-backdoor
 * https://github.com/hausec/PowerZure
 * https://posts.specterops.io/attacking-azure-azure-ad-and-introducing-powerzure-ca70b330511a
 * https://azure.microsoft.com/en-in/blog/azure-automation-runbook-management/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Defense Evasion
-
-*Version*: 101 (<<azure-automation-runbook-deleted-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_
-name:"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/DELETE" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and
+    azure.activitylogs.operation_name:"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/DELETE" and
+    event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,56 +70,3 @@ event.outcome:(Success or success)
 ** Name: Defense Evasion
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
-
-[[azure-automation-runbook-deleted-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_
-name:"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/DELETE" and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/DELETE" and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/DELETE and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/RUNBOOKS/DELETE and
-event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-automation-webhook-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-automation-webhook-created.asciidoc
index 8e87957426..194b7f2c7c 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-automation-webhook-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-automation-webhook-created.asciidoc
@@ -5,7 +5,7 @@ Identifies when an Azure Automation webhook is created. Azure Automation runbook
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,97 +14,56 @@ Identifies when an Azure Automation webhook is created. Azure Automation runbook
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://powerzure.readthedocs.io/en/latest/Functions/operational.html#create-backdoor
 * https://github.com/hausec/PowerZure
 * https://posts.specterops.io/attacking-azure-azure-ad-and-introducing-powerzure-ca70b330511a
 * https://www.ciraltos.com/webhooks-and-azure-automation-runbooks/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<azure-automation-webhook-created-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Configuration Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
-
 
-[source,markdown]
-----------------------------------
-
-----------------------------------
-
-
-==== Rule query
+==== Investigation guide
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and
-azure.activitylogs.operation_name: (
-"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WEBHOOKS/ACTION" or
-"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WEBHOOKS/WRITE" ) and
-event.outcome:(Success or success)
-----------------------------------
 
 
-[[azure-automation-webhook-created-history]]
-==== Rule version history
+==== Setup
 
-Version 101 (8.6.0 release)::
-* Formatting only
 
-Version 100 (8.5.0 release)::
-* Formatting only
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
-Version 7 (8.4.0 release)::
-* Formatting only
+==== Rule query
 
-Version 5 (7.13.0 release)::
-* Formatting only
 
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:(MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WEBHOOKS/ACTION or
-MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WEBHOOKS/WRITE) and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
+event.dataset:azure.activitylogs and
+  azure.activitylogs.operation_name:
+    (
+      "MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WEBHOOKS/ACTION" or
+      "MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WEBHOOKS/WRITE"
+    ) and
+  event.outcome:(Success or success)
 
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
 ----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:(MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WEBHOOKS/ACTION or
-MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WEBHOOKS/WRITE) and
-event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-blob-container-access-level-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-blob-container-access-level-modification.asciidoc
index 2ec5905d72..5840cf54b2 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-blob-container-access-level-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-blob-container-access-level-modification.asciidoc
@@ -5,7 +5,7 @@ Identifies changes to container access levels in Azure. Anonymous public read ac
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,50 @@ Identifies changes to container access levels in Azure. Anonymous public read ac
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/storage/blobs/anonymous-read-access-prevent
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
-
-*Version*: 101 (<<azure-blob-container-access-level-modification-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Asset Visibility
+* Tactic: Discovery
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Access level modifications may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Access level modifications from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.STORAGE/STORAGEACCOUNTS/BLOBSERVICES/CONTAINERS/WRITE" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.STORAGE/STORAGEACCOUNTS/BLOBSERVICES/CONTAINERS/WRITE" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,8 +69,6 @@ event.outcome:(Success or success)
 ** Name: Cloud Service Discovery
 ** ID: T1526
 ** Reference URL: https://attack.mitre.org/techniques/T1526/
-
-
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -88,42 +77,3 @@ event.outcome:(Success or success)
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[azure-blob-container-access-level-modification-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.STORAGE/STORAGEACCOUNTS/BLOBSERVICES/CONTAINERS/WRITE and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.STORAGE/STORAGEACCOUNTS/BLOBSERVICES/CONTAINERS/WRITE and
-event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-blob-permissions-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-blob-permissions-modification.asciidoc
index 323796feee..50d7162ba7 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-blob-permissions-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-blob-permissions-modification.asciidoc
@@ -5,7 +5,7 @@ Identifies when the Azure role-based access control (Azure RBAC) permissions are
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,61 +14,54 @@ Identifies when the Azure role-based access control (Azure RBAC) permissions are
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
 
-*Version*: 101 (<<azure-blob-permissions-modification-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Blob permissions may be modified by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and
-azure.activitylogs.operation_name:( "MICROSOFT.STORAGE/STORAGEACC
-OUNTS/BLOBSERVICES/CONTAINERS/BLOBS/MANAGEOWNERSHIP/ACTION" or "M
-ICROSOFT.STORAGE/STORAGEACCOUNTS/BLOBSERVICES/CONTAINERS/BLOBS/MODIFYP
-ERMISSIONS/ACTION") and event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:(
+     "MICROSOFT.STORAGE/STORAGEACCOUNTS/BLOBSERVICES/CONTAINERS/BLOBS/MANAGEOWNERSHIP/ACTION" or
+     "MICROSOFT.STORAGE/STORAGEACCOUNTS/BLOBSERVICES/CONTAINERS/BLOBS/MODIFYPERMISSIONS/ACTION") and
+  event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,25 +73,3 @@ ERMISSIONS/ACTION") and event.outcome:(Success or success)
 ** Name: File and Directory Permissions Modification
 ** ID: T1222
 ** Reference URL: https://attack.mitre.org/techniques/T1222/
-
-[[azure-blob-permissions-modification-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and
-azure.activitylogs.operation_name:( "MICROSOFT.STORAGE/STORAGEACC
-OUNTS/BLOBSERVICES/CONTAINERS/BLOBS/MANAGEOWNERSHIP/ACTION" or "M
-ICROSOFT.STORAGE/STORAGEACCOUNTS/BLOBSERVICES/CONTAINERS/BLOBS/MODIFYP
-ERMISSIONS/ACTION") and event.outcome:(Success or success)
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-command-execution-on-virtual-machine.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-command-execution-on-virtual-machine.asciidoc
index 14a62038b1..4b80d45043 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-command-execution-on-virtual-machine.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-command-execution-on-virtual-machine.asciidoc
@@ -5,7 +5,7 @@ Identifies command execution on a virtual machine (VM) in Azure. A Virtual Machi
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,61 +14,52 @@ Identifies command execution on a virtual machine (VM) in Azure. A Virtual Machi
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://adsecurity.org/?p=4277
 * https://posts.specterops.io/attacking-azure-azure-ad-and-introducing-powerzure-ca70b330511a
 * https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#virtual-machine-contributor
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 101 (<<azure-command-execution-on-virtual-machine-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Log Auditing
+* Tactic: Execution
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Command execution on a virtual machine may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Command execution from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.COMPUTE/VIRTUALMACHINES/RUNCOMMAND/ACTION" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.COMPUTE/VIRTUALMACHINES/RUNCOMMAND/ACTION" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,42 +71,3 @@ event.outcome:(Success or success)
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[azure-command-execution-on-virtual-machine-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.COMPUTE/VIRTUALMACHINES/RUNCOMMAND/ACTION and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.COMPUTE/VIRTUALMACHINES/RUNCOMMAND/ACTION and
-event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-conditional-access-policy-modified.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-conditional-access-policy-modified.asciidoc
index bf53ca2e54..241467380a 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-conditional-access-policy-modified.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-conditional-access-policy-modified.asciidoc
@@ -5,7 +5,7 @@ Identifies when an Azure Conditional Access policy is modified. Azure Conditiona
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,55 +14,51 @@ Identifies when an Azure Conditional Access policy is modified. Azure Conditiona
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/overview
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<azure-conditional-access-policy-modified-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Configuration Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:(azure.activitylogs or azure.auditlogs) and
-event.action:"Update conditional access policy" and
-event.outcome:(Success or success)
-----------------------------------
+event.action:"Update conditional access policy" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,47 +70,3 @@ event.outcome:(Success or success)
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[azure-conditional-access-policy-modified-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(azure.activitylogs or azure.auditlogs) and (
-azure.activitylogs.operation_name:"Update policy" or
-azure.auditlogs.operation_name:"Update policy" ) and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(azure.activitylogs or azure.auditlogs) and (
-azure.activitylogs.operation_name:"Update policy" or
-azure.auditlogs.operation_name:"Update policy" ) and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-diagnostic-settings-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-diagnostic-settings-deletion.asciidoc
index 7c1e5709db..b1db211369 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-diagnostic-settings-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-diagnostic-settings-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies the deletion of diagnostic settings in Azure, which send platform log
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,49 @@ Identifies the deletion of diagnostic settings in Azure, which send platform log
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostic-settings
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 101 (<<azure-diagnostic-settings-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Deletion of diagnostic settings may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Diagnostic settings deletion from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.INSIGHTS/DIAGNOSTICSETTINGS/DELETE" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.INSIGHTS/DIAGNOSTICSETTINGS/DELETE" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,42 +68,7 @@ event.outcome:(Success or success)
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[azure-diagnostic-settings-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.INSIGHTS/DIAGNOSTICSETTINGS/DELETE and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.INSIGHTS/DIAGNOSTICSETTINGS/DELETE and
-event.outcome:Success
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-event-hub-authorization-rule-created-or-updated.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-event-hub-authorization-rule-created-or-updated.asciidoc
index 7102e21784..c50bc8cba5 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-event-hub-authorization-rule-created-or-updated.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-event-hub-authorization-rule-created-or-updated.asciidoc
@@ -5,7 +5,7 @@ Identifies when an Event Hub Authorization Rule is created or updated in Azure.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,50 @@ Identifies when an Event Hub Authorization Rule is created or updated in Azure.
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/event-hubs/authorize-access-shared-access-signature
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 101 (<<azure-event-hub-authorization-rule-created-or-updated-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Log Auditing
+* Tactic: Collection
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Authorization rule additions or modifications may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Authorization rule additions or modifications from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.EVENTHUB/NAMESPACES/AUTHORIZATIONRULES/WRITE" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.EVENTHUB/NAMESPACES/AUTHORIZATIONRULES/WRITE" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,11 +66,9 @@ event.outcome:(Success or success)
 ** ID: TA0009
 ** Reference URL: https://attack.mitre.org/tactics/TA0009/
 * Technique:
-** Name: Data from Cloud Storage Object
+** Name: Data from Cloud Storage
 ** ID: T1530
 ** Reference URL: https://attack.mitre.org/techniques/T1530/
-
-
 * Tactic:
 ** Name: Exfiltration
 ** ID: TA0010
@@ -88,42 +77,3 @@ event.outcome:(Success or success)
 ** Name: Transfer Data to Cloud Account
 ** ID: T1537
 ** Reference URL: https://attack.mitre.org/techniques/T1537/
-
-[[azure-event-hub-authorization-rule-created-or-updated-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.EVENTHUB/NAMESPACES/AUTHORIZATIONRULES/WRITE and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.EVENTHUB/NAMESPACES/AUTHORIZATIONRULES/WRITE and
-event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-event-hub-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-event-hub-deletion.asciidoc
index f326214376..40100f4fa7 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-event-hub-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-event-hub-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies an Event Hub deletion in Azure. An Event Hub is an event processing s
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,61 +14,52 @@ Identifies an Event Hub deletion in Azure. An Event Hub is an event processing s
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-about
 * https://azure.microsoft.com/en-in/services/event-hubs/
 * https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-features
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 101 (<<azure-event-hub-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Log Auditing
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Event Hub deletions may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Event Hub deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.EVENTHUB/NAMESPACES/EVENTHUBS/DELETE" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.EVENTHUB/NAMESPACES/EVENTHUBS/DELETE" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,45 +71,7 @@ event.outcome:(Success or success)
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[azure-event-hub-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.EVENTHUB/NAMESPACES/EVENTHUBS/DELETE and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.EVENTHUB/NAMESPACES/EVENTHUBS/DELETE and
-event.outcome:Success
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-external-guest-user-invitation.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-external-guest-user-invitation.asciidoc
index 2fe41f6ec6..935f9289a3 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-external-guest-user-invitation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-external-guest-user-invitation.asciidoc
@@ -5,7 +5,7 @@ Identifies an invitation to an external user in Azure Active Directory (AD). Azu
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,60 +14,50 @@ Identifies an invitation to an external user in Azure Active Directory (AD). Azu
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/governance/policy/samples/cis-azure-1-1-0
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<azure-external-guest-user-invitation-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Guest user invitations may be sent out by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Guest user invitations from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.auditlogs and
-azure.auditlogs.operation_name:"Invite external user" and
-azure.auditlogs.properties.target_resources.*.display_name:guest and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Invite external user" and azure.auditlogs.properties.target_resources.*.display_name:guest and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,8 +69,6 @@ event.outcome:(Success or success)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -89,36 +77,3 @@ event.outcome:(Success or success)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[azure-external-guest-user-invitation-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.auditlogs and
-azure.auditlogs.operation_name:"Invite external user" and
-azure.auditlogs.properties.target_resources.*.display_name:guest and
-event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-firewall-policy-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-firewall-policy-deletion.asciidoc
index 3b324e105d..134b0fe1ad 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-firewall-policy-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-firewall-policy-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies the deletion of a firewall policy in Azure. An adversary may delete a
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,50 @@ Identifies the deletion of a firewall policy in Azure. An adversary may delete a
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/firewall-manager/policy-overview
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Network Security
-
-*Version*: 101 (<<azure-firewall-policy-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Network Security Monitoring
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Firewall policy deletions may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Firewall policy deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.NETWORK/FIREWALLPOLICIES/DELETE" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.NETWORK/FIREWALLPOLICIES/DELETE" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,44 +69,7 @@ event.outcome:(Success or success)
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[azure-firewall-policy-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.NETWORK/FIREWALLPOLICIES/DELETE and event.outcome:(Success
-or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.NETWORK/FIREWALLPOLICIES/DELETE and event.outcome:Success
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-frontdoor-web-application-firewall-waf-policy-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-frontdoor-web-application-firewall-waf-policy-deleted.asciidoc
index fe95988d6b..6096391642 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-frontdoor-web-application-firewall-waf-policy-deleted.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-frontdoor-web-application-firewall-waf-policy-deleted.asciidoc
@@ -5,7 +5,7 @@ Identifies the deletion of a Frontdoor Web Application Firewall (WAF) Policy in
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,50 @@ Identifies the deletion of a Frontdoor Web Application Firewall (WAF) Policy in
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#networking
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Network Security
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Network Security Monitoring
+* Tactic: Defense Evasion
 
-*Version*: 101 (<<azure-frontdoor-web-application-firewall-waf-policy-deleted-history, version history>>)
+*Version*: 102
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Azure Front Web Application Firewall (WAF) Policy deletions may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Azure Front Web Application Firewall (WAF) Policy deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.NETWORK/FRONTDOORWEBAPPLICATIONFIREWALLPOLICIES/DELETE"
-and event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.NETWORK/FRONTDOORWEBAPPLICATIONFIREWALLPOLICIES/DELETE" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,19 +69,7 @@ and event.outcome:(Success or success)
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[azure-frontdoor-web-application-firewall-waf-policy-deleted-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-full-network-packet-capture-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-full-network-packet-capture-detected.asciidoc
index 50b5cd80fe..a982b7fcb2 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-full-network-packet-capture-detected.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-full-network-packet-capture-detected.asciidoc
@@ -5,7 +5,7 @@ Identifies potential full network packet capture in Azure. Packet Capture is an
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,62 +14,55 @@ Identifies potential full network packet capture in Azure. Packet Capture is an
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Monitoring
+* Domain: Cloud
+* Data Source: Azure
+* Tactic: Credential Access
 
-*Version*: 101 (<<azure-full-network-packet-capture-detected-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Full Network Packet Capture may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Full Network Packet Capture from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
-event.dataset:azure.activitylogs and
-azure.activitylogs.operation_name: (
-"MICROSOFT.NETWORK/*/STARTPACKETCAPTURE/ACTION" or
-"MICROSOFT.NETWORK/*/VPNCONNECTIONS/STARTPACKETCAPTURE/ACTION" or
-"MICROSOFT.NETWORK/*/PACKETCAPTURES/WRITE" ) and
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:
+    (
+        MICROSOFT.NETWORK/*/STARTPACKETCAPTURE/ACTION or
+        MICROSOFT.NETWORK/*/VPNCONNECTIONS/STARTPACKETCAPTURE/ACTION or
+        MICROSOFT.NETWORK/*/PACKETCAPTURES/WRITE
+    ) and
 event.outcome:(Success or success)
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,26 +74,3 @@ event.outcome:(Success or success)
 ** Name: Network Sniffing
 ** ID: T1040
 ** Reference URL: https://attack.mitre.org/techniques/T1040/
-
-[[azure-full-network-packet-capture-detected-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and
-azure.activitylogs.operation_name: (
-"MICROSOFT.NETWORK/*/STARTPACKETCAPTURE/ACTION" or
-"MICROSOFT.NETWORK/*/VPNCONNECTIONS/STARTPACKETCAPTURE/ACTION" or
-"MICROSOFT.NETWORK/*/PACKETCAPTURES/WRITE" ) and
-event.outcome:(Success or success)
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-global-administrator-role-addition-to-pim-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-global-administrator-role-addition-to-pim-user.asciidoc
index a9575a261f..f0d4509d1d 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-global-administrator-role-addition-to-pim-user.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-global-administrator-role-addition-to-pim-user.asciidoc
@@ -5,7 +5,7 @@ Identifies an Azure Active Directory (AD) Global Administrator role addition to
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,63 +14,54 @@ Identifies an Azure Active Directory (AD) Global Administrator role addition to
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<azure-global-administrator-role-addition-to-pim-user-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Global administrator additions may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Global administrator additions from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.auditlogs and
-azure.auditlogs.properties.category:RoleManagement and
-azure.auditlogs.operation_name:("Add eligible member to role in PIM
-completed (permanent)" or "Add
-member to role in PIM completed (timebound)") and
-azure.auditlogs.properties.target_resources.*.display_name:"Global
-Administrator" and event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.auditlogs and azure.auditlogs.properties.category:RoleManagement and
+    azure.auditlogs.operation_name:("Add eligible member to role in PIM completed (permanent)" or
+                                    "Add member to role in PIM completed (timebound)") and
+    azure.auditlogs.properties.target_resources.*.display_name:"Global Administrator" and
+    event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -82,39 +73,3 @@ Administrator" and event.outcome:(Success or success)
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[azure-global-administrator-role-addition-to-pim-user-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.auditlogs and
-azure.auditlogs.properties.category:RoleManagement and
-azure.auditlogs.operation_name:("Add eligible member to role in PIM
-completed (permanent)" or "Add member to role in PIM completed
-(timebound)") and
-azure.auditlogs.properties.target_resources.*.display_name:"Global
-Administrator" and event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-key-vault-modified.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-key-vault-modified.asciidoc
index 2117884214..9bb8de5557 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-key-vault-modified.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-key-vault-modified.asciidoc
@@ -5,7 +5,7 @@ Identifies modifications to a Key Vault in Azure. The Key Vault is a service tha
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,61 +14,51 @@ Identifies modifications to a Key Vault in Azure. The Key Vault is a service tha
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/key-vault/general/basic-concepts
 * https://docs.microsoft.com/en-us/azure/key-vault/general/secure-your-key-vault
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Data Protection
-
-*Version*: 102 (<<azure-key-vault-modified-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Key vault modifications may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Key vault modifications from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and
-azure.activitylogs.operation_name:"MICROSOFT.KEYVAULT/VAULTS/WRITE"
-and event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.KEYVAULT/VAULTS/WRITE" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,42 +70,7 @@ and event.outcome:(Success or success)
 ** Name: Unsecured Credentials
 ** ID: T1552
 ** Reference URL: https://attack.mitre.org/techniques/T1552/
-
-[[azure-key-vault-modified-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and
-azure.activitylogs.operation_name:MICROSOFT.KEYVAULT/VAULTS/WRITE and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and
-azure.activitylogs.operation_name:MICROSOFT.KEYVAULT/VAULTS/WRITE and
-event.outcome:Success
-----------------------------------
-
+* Sub-technique:
+** Name: Credentials In Files
+** ID: T1552.001
+** Reference URL: https://attack.mitre.org/techniques/T1552/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-events-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-events-deleted.asciidoc
index 6c2d98644c..0c7d31b4e9 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-events-deleted.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-events-deleted.asciidoc
@@ -5,7 +5,7 @@ Identifies when events are deleted in Azure Kubernetes. Kubernetes events are ob
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,51 @@ Identifies when events are deleted in Azure Kubernetes. Kubernetes events are ob
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#microsoftkubernetes
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Log Auditing
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Log Auditing
+* Tactic: Defense Evasion
 
-*Version*: 101 (<<azure-kubernetes-events-deleted-history, version history>>)
+*Version*: 102
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Events deletions may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Events deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/EVENTS.K8S.IO/EVENTS/DELETE"
-and event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/EVENTS.K8S.IO/EVENTS/DELETE" and
+event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,32 +70,7 @@ and event.outcome:(Success or success)
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[azure-kubernetes-events-deleted-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/EVENTS.K8S.IO/EVENTS/DELETE"
-and event.outcome:(Success or success)
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
-Version 2 (8.0.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-pods-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-pods-deleted.asciidoc
index b8cd4a8191..95a4a94c60 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-pods-deleted.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-pods-deleted.asciidoc
@@ -5,7 +5,7 @@ Identifies the deletion of Azure Kubernetes Pods. Adversaries may delete a Kuber
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,51 @@ Identifies the deletion of Azure Kubernetes Pods. Adversaries may delete a Kuber
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#microsoftkubernetes
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Asset Visibility
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Asset Visibility
+* Tactic: Impact
 
-*Version*: 101 (<<azure-kubernetes-pods-deleted-history, version history>>)
+*Version*: 102
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Pods may be deleted by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Pods deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/PODS/DELETE" and
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/PODS/DELETE" and
 event.outcome:(Success or success)
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,29 +66,3 @@ event.outcome:(Success or success)
 ** Name: Impact
 ** ID: TA0040
 ** Reference URL: https://attack.mitre.org/tactics/TA0040/
-
-[[azure-kubernetes-pods-deleted-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/PODS/DELETE" and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
-Version 2 (8.0.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-rolebindings-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-rolebindings-created.asciidoc
index 57e3a6c92a..737d0a3ff3 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-rolebindings-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-kubernetes-rolebindings-created.asciidoc
@@ -5,7 +5,7 @@ Identifies the creation of role binding or cluster role bindings. You can assign
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,58 +14,54 @@ Identifies the creation of role binding or cluster role bindings. You can assign
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-20m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#microsoftkubernetes
 * https://www.microsoft.com/security/blog/2020/04/02/attack-matrix-kubernetes/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Tactic: Privilege Escalation
 
-*Version*: 101 (<<azure-kubernetes-rolebindings-created-history, version history>>)
+*Version*: 102
 
-*Added ({stack} release)*: 8.0.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and
-azure.activitylogs.operation_name: ("MICROSOFT.KUBERNETES/CONN
-ECTEDCLUSTERS/RBAC.AUTHORIZATION.K8S.IO/ROLEBINDINGS/WRITE" or
-"MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/RBAC.AUTHORIZATION.K8S.IO/CLUS
-TERROLEBINDINGS/WRITE") and event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:
+	("MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/RBAC.AUTHORIZATION.K8S.IO/ROLEBINDINGS/WRITE" or
+	 "MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/RBAC.AUTHORIZATION.K8S.IO/CLUSTERROLEBINDINGS/WRITE") and
+event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,25 +69,3 @@ TERROLEBINDINGS/WRITE") and event.outcome:(Success or success)
 ** Name: Privilege Escalation
 ** ID: TA0004
 ** Reference URL: https://attack.mitre.org/tactics/TA0004/
-
-[[azure-kubernetes-rolebindings-created-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and
-azure.activitylogs.operation_name: ("MICROSOFT.KUBERNETES/CONN
-ECTEDCLUSTERS/RBAC.AUTHORIZATION.K8S.IO/ROLEBINDINGS/WRITE" or
-"MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/RBAC.AUTHORIZATION.K8S.IO/CLUS
-TERROLEBINDINGS/WRITE") and event.outcome:(Success or success)
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-network-watcher-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-network-watcher-deletion.asciidoc
index 2abfa8985d..b8744e98e2 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-network-watcher-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-network-watcher-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies the deletion of a Network Watcher in Azure. Network Watchers are used
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,50 @@ Identifies the deletion of a Network Watcher in Azure. Network Watchers are used
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-monitoring-overview
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Network Security
-
-*Version*: 101 (<<azure-network-watcher-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Network Security Monitoring
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Network Watcher deletions may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Network Watcher deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.NETWORK/NETWORKWATCHERS/DELETE" and event.outcome:(Success
-or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.NETWORK/NETWORKWATCHERS/DELETE" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,44 +69,7 @@ or success)
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[azure-network-watcher-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.NETWORK/NETWORKWATCHERS/DELETE and event.outcome:(Success
-or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.NETWORK/NETWORKWATCHERS/DELETE and event.outcome:Success
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-privilege-identity-management-role-modified.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-privilege-identity-management-role-modified.asciidoc
index 8e47a8c9f3..e3e0e0c3d9 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-privilege-identity-management-role-modified.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-privilege-identity-management-role-modified.asciidoc
@@ -5,7 +5,7 @@ Azure Active Directory (AD) Privileged Identity Management (PIM) is a service th
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,71 +14,71 @@ Azure Active Directory (AD) Privileged Identity Management (PIM) is a service th
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pim-resource-roles-assign-roles
 * https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pim-configure
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Investigation Guide
-
-*Version*: 103 (<<azure-privilege-identity-management-role-modified-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Azure Privilege Identity Management Role Modified
+*Triage and analysis*
+
+
+
+*Investigating Azure Privilege Identity Management Role Modified*
+
 
-Azure Active Directory (AD) Privileged Identity Management (PIM) is a service that enables you to manage, control, and
-monitor access to important resources in an organization. PIM can be used to manage the built-in Azure resource roles
-such as Global Administrator and Application Administrator.
+Azure Active Directory (AD) Privileged Identity Management (PIM) is a service that enables you to manage, control, and monitor access to important resources in an organization. PIM can be used to manage the built-in Azure resource roles such as Global Administrator and Application Administrator.
 
-This rule identifies the update of PIM role settings, which can indicate that an attacker has already gained enough
-access to modify role assignment settings.
+This rule identifies the update of PIM role settings, which can indicate that an attacker has already gained enough access to modify role assignment settings.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Consider the source IP address and geolocation for the user who issued the command. Do they look normal for the user?
-- Consider the time of day. If the user is a human, not a program or script, did the activity take place during a normal
-time of day?
+- Consider the time of day. If the user is a human, not a program or script, did the activity take place during a normal time of day?
 - Check if this operation was approved and performed according to the organization's change management policy.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Examine the account's commands, API calls, and data management actions in the last 24 hours.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - If this activity didn't follow your organization's change management policies, it should be reviewed by the security team.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -88,31 +88,27 @@ and data accessed by the account in the last 24 hours.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
-- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other
-IAM users.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Restore the PIM roles to the desired state.
 - Consider enabling multi-factor authentication for users.
-- Follow security best practices [outlined](https://docs.microsoft.com/en-us/azure/security/fundamentals/identity-management-best-practices) by Microsoft.
+- Follow security best practices https://docs.microsoft.com/en-us/azure/security/fundamentals/identity-management-best-practices[outlined] by Microsoft.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.auditlogs and
-azure.auditlogs.operation_name:"Update role setting in PIM" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Update role setting in PIM" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -124,8 +120,6 @@ event.outcome:(Success or success)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -134,35 +128,3 @@ event.outcome:(Success or success)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[azure-privilege-identity-management-role-modified-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.auditlogs and
-azure.auditlogs.operation_name:"Update role setting in PIM" and
-event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-resource-group-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-resource-group-deletion.asciidoc
index b7f12bbdbf..e7df96f6bd 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-resource-group-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-resource-group-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies the deletion of a resource group in Azure, which includes all resourc
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,50 @@ Identifies the deletion of a resource group in Azure, which includes all resourc
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 101 (<<azure-resource-group-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Log Auditing
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Deletion of a resource group may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Resource group deletions from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.RESOURCES/SUBSCRIPTIONS/RESOURCEGROUPS/DELETE" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.RESOURCES/SUBSCRIPTIONS/RESOURCEGROUPS/DELETE" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,8 +69,6 @@ event.outcome:(Success or success)
 ** Name: Data Destruction
 ** ID: T1485
 ** Reference URL: https://attack.mitre.org/techniques/T1485/
-
-
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -88,42 +77,7 @@ event.outcome:(Success or success)
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[azure-resource-group-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.RESOURCES/SUBSCRIPTIONS/RESOURCEGROUPS/DELETE and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.RESOURCES/SUBSCRIPTIONS/RESOURCEGROUPS/DELETE and
-event.outcome:Success
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-service-principal-addition.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-service-principal-addition.asciidoc
index 95b59a3846..d344f3fa76 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-service-principal-addition.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-service-principal-addition.asciidoc
@@ -5,7 +5,7 @@ Identifies when a new service principal is added in Azure. An application, hoste
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,77 +14,71 @@ Identifies when a new service principal is added in Azure. An application, hoste
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://msrc-blog.microsoft.com/2020/12/13/customer-guidance-on-recent-nation-state-cyber-attacks/
 * https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Defense Evasion
+
+*Version*: 105
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Investigation Guide
 
-*Version*: 103 (<<azure-service-principal-addition-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-A service principal may be created by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Service principal additions from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
-==== Investigation guide
 
+*Investigating Azure Service Principal Addition*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Azure Service Principal Addition
+Service Principals are identities used by applications, services, and automation tools to access specific resources. They grant specific access based on the assigned API permissions. Most organizations that work a lot with Azure AD make use of service principals. Whenever an application is registered, it automatically creates an application object and a service principal in an Azure AD tenant.
+
+This rule looks for the addition of service principals. This behavior may enable attackers to impersonate legitimate service principals to camouflage their activities among noisy automations/apps.
 
-Service Principals are identities used by applications, services, and automation tools to access specific resources.
-They grant specific access based on the assigned API permissions. Most organizations that work a lot with Azure AD make
-use of service principals. Whenever an application is registered, it automatically creates an application object and a
-service principal in an Azure AD tenant.
 
-This rule looks for the addition of service principals. This behavior may enable attackers to impersonate legitimate
-service principals to camouflage their activities among noisy automations/apps.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Consider the source IP address and geolocation for the user who issued the command. Do they look normal for the user?
-- Consider the time of day. If the user is a human, not a program or script, did the activity take place during a normal
-time of day?
+- Consider the time of day. If the user is a human, not a program or script, did the activity take place during a normal time of day?
 - Check if this operation was approved and performed according to the organization's change management policy.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Examine the account's commands, API calls, and data management actions in the last 24 hours.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
+
+If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and device conditions.
 
-### False positive analysis
 
-If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a
-combination of user and device conditions.
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -94,29 +88,26 @@ combination of user and device conditions.
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
-- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other
-IAM users.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
-- Follow security best practices [outlined](https://docs.microsoft.com/en-us/azure/security/fundamentals/identity-management-best-practices) by Microsoft.
+- Follow security best practices https://docs.microsoft.com/en-us/azure/security/fundamentals/identity-management-best-practices[outlined] by Microsoft.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Add
-service principal" and event.outcome:(success or Success)
+[source, js]
 ----------------------------------
+event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Add service principal" and event.outcome:(success or Success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -128,25 +119,7 @@ service principal" and event.outcome:(success or Success)
 ** Name: Use Alternate Authentication Material
 ** ID: T1550
 ** Reference URL: https://attack.mitre.org/techniques/T1550/
-
-[[azure-service-principal-addition-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Application Access Token
+** ID: T1550.001
+** Reference URL: https://attack.mitre.org/techniques/T1550/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-service-principal-credentials-added.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-service-principal-credentials-added.asciidoc
index 48b8301538..53800ee2f7 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-service-principal-credentials-added.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-service-principal-credentials-added.asciidoc
@@ -5,7 +5,7 @@ Identifies when new Service Principal credentials have been added in Azure. In m
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,58 +14,51 @@ Identifies when new Service Principal credentials have been added in Azure. In m
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.fireeye.com/content/dam/collateral/en/wp-m-unc2452.pdf
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<azure-service-principal-credentials-added-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Service principal credential additions may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Credential additions from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Add
-service principal credentials" and event.outcome:(success or Success)
+[source, js]
 ----------------------------------
+event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Add service principal credentials" and event.outcome:(success or Success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,25 +70,3 @@ service principal credentials" and event.outcome:(success or Success)
 ** Name: Resource Hijacking
 ** ID: T1496
 ** Reference URL: https://attack.mitre.org/techniques/T1496/
-
-[[azure-service-principal-credentials-added-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Add
-service principal credentials." and event.outcome:(success or Success)
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-storage-account-key-regenerated.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-storage-account-key-regenerated.asciidoc
index 9682a2464c..8a90fd6d03 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-storage-account-key-regenerated.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-storage-account-key-regenerated.asciidoc
@@ -5,7 +5,7 @@ Identifies a rotation to storage account access keys in Azure. Regenerating acce
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,59 +14,50 @@ Identifies a rotation to storage account access keys in Azure. Regenerating acce
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<azure-storage-account-key-regenerated-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-It's recommended that you rotate your access keys periodically to help keep your storage account secure. Normal key rotation can be exempted from the rule. An abnormal time frame and/or a key rotation from unfamiliar users, hosts, or locations should be investigated.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:"MICROSOFT.STORAGE/STORAGEACCOUNTS/REGENERATEKEY/ACTION" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.STORAGE/STORAGEACCOUNTS/REGENERATEKEY/ACTION" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,42 +69,3 @@ event.outcome:(Success or success)
 ** Name: Steal Application Access Token
 ** ID: T1528
 ** Reference URL: https://attack.mitre.org/techniques/T1528/
-
-[[azure-storage-account-key-regenerated-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.STORAGE/STORAGEACCOUNTS/REGENERATEKEY/ACTION and
-event.outcome:(Success or success)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:MICROSOFT.STORAGE/STORAGEACCOUNTS/REGENERATEKEY/ACTION and
-event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/azure-virtual-network-device-modified-or-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/azure-virtual-network-device-modified-or-deleted.asciidoc
index 4d99614495..84e971662a 100644
--- a/docs/detections/prebuilt-rules/rule-details/azure-virtual-network-device-modified-or-deleted.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/azure-virtual-network-device-modified-or-deleted.asciidoc
@@ -5,7 +5,7 @@ Identifies when a virtual network device is modified or deleted. This can be a n
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,70 +14,56 @@ Identifies when a virtual network device is modified or deleted. This can be a n
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Network Security
-* Impact
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Network Security Monitoring
+* Tactic: Impact
 
-*Version*: 101 (<<azure-virtual-network-device-modified-or-deleted-history, version history>>)
+*Version*: 102
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Virtual Network Device modification or deletion may be performed by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Virtual Network Device modification or deletion by unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:("MICROSOFT.NETWORK/NETWORKINTERFACES/TAPCONFIGURATIONS/WRITE" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/TAPCONFIGURATIONS/DELETE" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/WRITE" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/JOIN/ACTION" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/DELETE" or
-"MICROSOFT.NETWORK/NETWORKVIRTUALAPPLIANCES/DELETE" or
-"MICROSOFT.NETWORK/NETWORKVIRTUALAPPLIANCES/WRITE" or
-"MICROSOFT.NETWORK/VIRTUALHUBS/DELETE" or
-"MICROSOFT.NETWORK/VIRTUALHUBS/WRITE" or
-"MICROSOFT.NETWORK/VIRTUALROUTERS/WRITE" or
-"MICROSOFT.NETWORK/VIRTUALROUTERS/DELETE") and event.outcome:(Success
-or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.activitylogs and azure.activitylogs.operation_name:("MICROSOFT.NETWORK/NETWORKINTERFACES/TAPCONFIGURATIONS/WRITE" or
+"MICROSOFT.NETWORK/NETWORKINTERFACES/TAPCONFIGURATIONS/DELETE" or "MICROSOFT.NETWORK/NETWORKINTERFACES/WRITE" or
+"MICROSOFT.NETWORK/NETWORKINTERFACES/JOIN/ACTION" or "MICROSOFT.NETWORK/NETWORKINTERFACES/DELETE" or
+"MICROSOFT.NETWORK/NETWORKVIRTUALAPPLIANCES/DELETE" or "MICROSOFT.NETWORK/NETWORKVIRTUALAPPLIANCES/WRITE" or
+"MICROSOFT.NETWORK/VIRTUALHUBS/DELETE" or "MICROSOFT.NETWORK/VIRTUALHUBS/WRITE" or
+"MICROSOFT.NETWORK/VIRTUALROUTERS/WRITE" or "MICROSOFT.NETWORK/VIRTUALROUTERS/DELETE") and
+event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -85,53 +71,3 @@ or success)
 ** Name: Impact
 ** ID: TA0040
 ** Reference URL: https://attack.mitre.org/tactics/TA0040/
-
-[[azure-virtual-network-device-modified-or-deleted-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:("MICROSOFT.NETWORK/NETWORKINTERFACES/TAPCONFIGURATIONS/WRITE" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/TAPCONFIGURATIONS/DELETE" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/WRITE" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/JOIN/ACTION" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/DELETE" or
-"MICROSOFT.NETWORK/NETWORKVIRTUALAPPLIANCES/DELETE" or
-"MICROSOFT.NETWORK/NETWORKVIRTUALAPPLIANCES/WRITE" or
-"MICROSOFT.NETWORK/VIRTUALHUBS/DELETE" or
-"MICROSOFT.NETWORK/VIRTUALHUBS/WRITE" or
-"MICROSOFT.NETWORK/VIRTUALROUTERS/WRITE" or
-"MICROSOFT.NETWORK/VIRTUALROUTERS/DELETE") and event.outcome:(Success
-or success)
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.activitylogs and azure.activitylogs.operation_name
-:("MICROSOFT.NETWORK/NETWORKINTERFACES/TAPCONFIGURATIONS/WRITE" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/TAPCONFIGURATIONS/DELETE" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/WRITE" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/JOIN/ACTION" or
-"MICROSOFT.NETWORK/NETWORKINTERFACES/DELETE"or
-"MICROSOFT.NETWORK/NETWORKVIRTUALAPPLIANCES/DELETE" or
-"MICROSOFT.NETWORK/NETWORKVIRTUALAPPLIANCES/WRITE" or
-"MICROSOFT.NETWORK/VIRTUALHUBS/DELETE" or
-"MICROSOFT.NETWORK/VIRTUALHUBS/WRITE" or
-"MICROSOFT.NETWORK/VIRTUALROUTERS/WRITE" or
-"MICROSOFT.NETWORK/VIRTUALROUTERS/DELETE") and event.outcome:(Success
-or success)
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/base16-or-base32-encoding-decoding-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/base16-or-base32-encoding-decoding-activity.asciidoc
index 5d3ee9f10a..38e7f73a4d 100644
--- a/docs/detections/prebuilt-rules/rule-details/base16-or-base32-encoding-decoding-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/base16-or-base32-encoding-decoding-activity.asciidoc
@@ -3,97 +3,121 @@
 
 Adversaries may encode/decode data in an attempt to evade detection by host- or network-based security controls.
 
-*Rule type*: query
+*Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<base16-or-base32-encoding-decoding-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
 
-*Added ({stack} release)*: 7.8.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Automated tools such as Jenkins may encode or decode files as part of their normal behavior. These events can be filtered by the process executable or username values.
+==== Setup
 
-==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:(base16 or base32 or base32plain or base32hex)
-----------------------------------
+*Setup*
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Deobfuscate/Decode Files or Information
-** ID: T1140
-** Reference URL: https://attack.mitre.org/techniques/T1140/
 
-[[base16-or-base32-encoding-decoding-activity-history]]
-==== Rule version history
+*Prerequisite Requirements:*
 
-Version 100 (8.5.0 release)::
-* Formatting only
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 8 (8.4.0 release)::
-* Formatting only
 
-Version 7 (7.12.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
 
-Version 6 (7.11.2 release)::
-* Formatting only
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Version 5 (7.11.0 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Formatting only
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
 
-Version 3 (7.9.1 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:(executed or process_started) and process.name:(base16 or
-base32 or base32plain or base32hex)
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name in ("base16", "base32", "base32plain", "base32hex") and
+not process.args in ("--help", "--version")
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Obfuscated Files or Information
+** ID: T1027
+** Reference URL: https://attack.mitre.org/techniques/T1027/
+* Technique:
+** Name: Deobfuscate/Decode Files or Information
+** ID: T1140
+** Reference URL: https://attack.mitre.org/techniques/T1140/
diff --git a/docs/detections/prebuilt-rules/rule-details/bash-shell-profile-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/bash-shell-profile-modification.asciidoc
index 0cdd466f03..458145c2bd 100644
--- a/docs/detections/prebuilt-rules/rule-details/bash-shell-profile-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/bash-shell-profile-modification.asciidoc
@@ -5,7 +5,7 @@ Both ~/.bash_profile and ~/.bashrc are files containing shell commands that are
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
 * auditbeat-*
@@ -14,61 +14,55 @@ Both ~/.bash_profile and ~/.bashrc are files containing shell commands that are
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.anomali.com/blog/pulling-linux-rabbit-rabbot-malware-out-of-a-hat
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* macOS
-* Linux
-* Threat Detection
-* Persistence
-
-*Version*: 100 (<<bash-shell-profile-modification-history, version history>>)
+* Domain: Endpoint
+* OS: macOS
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Changes to the Shell Profile tend to be noisy, a tuning per your environment will be required.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:file and event.type:change and process.name:(* and
-not (sudo or vim or
-zsh or env or
-nano or bash or
-Terminal or xpcproxy or
-login or cat or
-cp or launchctl or
-java)) and not process.executable:(/Applications/* or
-/private/var/folders/* or /usr/local/*) and
-file.path:(/private/etc/rc.local or /etc/rc.local or
-/home/*/.profile or /home/*/.profile1 or
-/home/*/.bash_profile or /home/*/.bash_profile1 or
-/home/*/.bashrc or /Users/*/.bash_profile or
-/Users/*/.zshenv)
+[source, js]
 ----------------------------------
+event.category:file and event.type:change and
+  process.name:(* and not (sudo or vim or zsh or env or nano or bash or Terminal or xpcproxy or login or cat or cp or
+  launchctl or java or dnf or tailwatchd or ldconfig or yum or semodule or cpanellogd or dockerd or authselect or chmod or
+  dnf-automatic or git or dpkg or platform-python)) and
+  not process.executable:(/Applications/* or /private/var/folders/* or /usr/local/* or /opt/saltstack/salt/bin/*) and
+  file.path:(/private/etc/rc.local or
+             /etc/rc.local or
+             /home/*/.profile or
+             /home/*/.profile1 or
+             /home/*/.bash_profile or
+             /home/*/.bash_profile1 or
+             /home/*/.bashrc or
+             /Users/*/.bash_profile or
+             /Users/*/.zshenv)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,16 +74,7 @@ file.path:(/private/etc/rc.local or /etc/rc.local or
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[bash-shell-profile-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Unix Shell Configuration Modification
+** ID: T1546.004
+** Reference URL: https://attack.mitre.org/techniques/T1546/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/binary-content-copy-via-cmd-exe.asciidoc b/docs/detections/prebuilt-rules/rule-details/binary-content-copy-via-cmd-exe.asciidoc
new file mode 100644
index 0000000000..04d2e60089
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/binary-content-copy-via-cmd-exe.asciidoc
@@ -0,0 +1,76 @@
+[[binary-content-copy-via-cmd-exe]]
+=== Binary Content Copy via Cmd.exe
+
+Attackers may abuse cmd.exe commands to reassemble binary fragments into a malicious payload.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "cmd.exe" and (
+    (process.args : "type" and process.args : (">", ">>")) or
+    (process.args : "copy" and process.args : "/b"))
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Deobfuscate/Decode Files or Information
+** ID: T1140
+** Reference URL: https://attack.mitre.org/techniques/T1140/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/binary-executed-from-shared-memory-directory.asciidoc b/docs/detections/prebuilt-rules/rule-details/binary-executed-from-shared-memory-directory.asciidoc
index 4f0003b650..0bd9b799c5 100644
--- a/docs/detections/prebuilt-rules/rule-details/binary-executed-from-shared-memory-directory.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/binary-executed-from-shared-memory-directory.asciidoc
@@ -5,62 +5,94 @@ Identifies the execution of a binary by root in Linux shared memory directories:
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://linuxsecurity.com/features/fileless-malware-on-linux
 * https://twitter.com/GossiTheDog/status/1522964028284411907
 * https://www.elastic.co/security-labs/a-peek-behind-the-bpfdoor
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Threat: BPFDoor
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 110
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Execution
-* BPFDoor
 
-*Version*: 101 (<<binary-executed-from-shared-memory-directory-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 8.3.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.6.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
 
-==== Potential false positives
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Directories /dev/shm and /run/shm are temporary file storage directories in Linux. They are intended to appear as a mounted file system, but uses virtual memory instead of a persistent storage device and thus are used for mounting file systems in legitimate purposes.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and event.action == "exec" and
-user.name == "root" and process.executable : (
-"/dev/shm/*", "/run/shm/*", "/var/run/*",
-"/var/lock/*" ) and not process.executable : (
-"/var/run/docker/*")
+[source, js]
 ----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
+user.id == "0" and process.executable : ("/dev/shm/*", "/run/shm/*", "/var/run/*", "/var/lock/*") and
+not process.executable : ("/var/run/docker/*", "/var/run/utsns/*", "/var/run/s6/*", "/var/run/cloudera-scm-agent/*", 
+"/var/run/argo/argoexec") and not process.parent.command_line : "/usr/bin/runc init"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,33 +104,3 @@ user.name == "root" and process.executable : (
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[binary-executed-from-shared-memory-directory-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and event.action == "exec"
-and user.name == "root" and process.executable : (
-"/dev/shm/*", "/run/shm/*", "/var/run/*",
-"/var/lock/*" ) and not process.executable : (
-"/var/run/docker/*")
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and event.action == "exec"
-and user.name == "root" and process.executable : (
-"/dev/shm/*", "/run/shm/*", "/var/run/*",
-"/var/lock/*" )
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/bitsadmin-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/bitsadmin-activity.asciidoc
new file mode 100644
index 0000000000..4b05a16b75
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/bitsadmin-activity.asciidoc
@@ -0,0 +1,86 @@
+[[bitsadmin-activity]]
+=== Bitsadmin Activity
+
+Windows Background Intelligent Transfer Service (BITS) is a low-bandwidth, asynchronous file transfer mechanism. Adversaries may abuse BITS to persist, download, execute, and even clean up after running malicious code.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (
+   (process.name : "bitsadmin.exe" and process.args : (
+        "*Transfer*", "*Create*", "AddFile", "*SetNotifyFlags*", "*SetNotifyCmdLine*",
+        "*SetMinRetryDelay*", "*SetCustomHeaders*", "*Resume*")
+   ) or
+   (process.name : "powershell.exe" and process.args : (
+        "*Start-BitsTransfer*", "*Add-BitsFile*",
+        "*Resume-BitsTransfer*", "*Set-BitsTransfer*", "*BITS.Manager*")
+   )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Ingress Tool Transfer
+** ID: T1105
+** Reference URL: https://attack.mitre.org/techniques/T1105/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: BITS Jobs
+** ID: T1197
+** Reference URL: https://attack.mitre.org/techniques/T1197/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: BITS Jobs
+** ID: T1197
+** Reference URL: https://attack.mitre.org/techniques/T1197/
diff --git a/docs/detections/prebuilt-rules/rule-details/bpf-filter-applied-using-tc.asciidoc b/docs/detections/prebuilt-rules/rule-details/bpf-filter-applied-using-tc.asciidoc
index 8a465acc84..3af50692db 100644
--- a/docs/detections/prebuilt-rules/rule-details/bpf-filter-applied-using-tc.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/bpf-filter-applied-using-tc.asciidoc
@@ -5,56 +5,92 @@ Detects when the tc (transmission control) binary is utilized to set a BPF (Berk
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-*
+* logs-endpoint.events.*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/h3xduck/TripleCross/blob/master/src/helpers/deployer.sh
 * https://man7.org/linux/man-pages/man8/tc.8.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Threat: TripleCross
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Execution
-* TripleCross
 
-*Version*: 100 (<<bpf-filter-applied-using-tc-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.4.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type != "end" and process.executable :
-"/usr/sbin/tc" and process.args : "filter" and process.args : "add"
-and process.args : "bpf" and not process.parent.executable:
-"/usr/sbin/libvirtd"
+[source, js]
 ----------------------------------
+process where host.os.type == "linux" and event.type != "end" and process.executable == "/usr/sbin/tc" and
+process.args == "filter" and process.args == "add" and process.args == "bpf" and
+not process.parent.executable == "/usr/sbin/libvirtd"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,10 +102,7 @@ and process.args : "bpf" and not process.parent.executable:
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[bpf-filter-applied-using-tc-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/browser-extension-install.asciidoc b/docs/detections/prebuilt-rules/rule-details/browser-extension-install.asciidoc
new file mode 100644
index 0000000000..2851a6251e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/browser-extension-install.asciidoc
@@ -0,0 +1,76 @@
+[[browser-extension-install]]
+=== Browser Extension Install
+
+Identifies the install of browser extensions. Malicious browser extensions can be installed via app store downloads masquerading as legitimate extensions, social engineering, or by an adversary that has already compromised a system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.action : "creation" and 
+(
+  /* Firefox-Based Browsers */
+  (
+    file.name : "*.xpi" and
+    file.path : "?:\\Users\\*\\AppData\\Roaming\\*\\Profiles\\*\\Extensions\\*.xpi" and
+    not 
+    (
+      process.name : "firefox.exe" and
+      file.name : ("langpack-*@firefox.mozilla.org.xpi", "*@dictionaries.addons.mozilla.org.xpi")
+    )
+  ) or
+  /* Chromium-Based Browsers */
+  (
+    file.name : "*.crx" and
+    file.path : "?:\\Users\\*\\AppData\\Local\\*\\*\\User Data\\Webstore Downloads\\*"
+  )
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Browser Extensions
+** ID: T1176
+** Reference URL: https://attack.mitre.org/techniques/T1176/
diff --git a/docs/detections/prebuilt-rules/rule-details/bypass-uac-via-event-viewer.asciidoc b/docs/detections/prebuilt-rules/rule-details/bypass-uac-via-event-viewer.asciidoc
index fd4480acc6..e2bbdb3e29 100644
--- a/docs/detections/prebuilt-rules/rule-details/bypass-uac-via-event-viewer.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/bypass-uac-via-event-viewer.asciidoc
@@ -5,97 +5,99 @@ Identifies User Account Control (UAC) bypass via eventvwr.exe. Attackers bypass
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<bypass-uac-via-event-viewer-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Bypass UAC via Event Viewer
+*Triage and analysis*
+
+
+
+*Investigating Bypass UAC via Event Viewer*
 
-Windows User Account Control (UAC) allows a program to elevate its privileges (tracked as low to high integrity levels)
-to perform a task under administrator-level permissions, possibly by prompting the user for confirmation.
-UAC can deny an operation under high-integrity enforcement, or allow the user to perform the action if they are in the
-local administrators group and enter an administrator password when prompted.
 
-For more information about the UAC and how it works, check the [official Microsoft docs page](https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/how-user-account-control-works).
+Windows User Account Control (UAC) allows a program to elevate its privileges (tracked as low to high integrity levels) to perform a task under administrator-level permissions, possibly by prompting the user for confirmation. UAC can deny an operation under high-integrity enforcement, or allow the user to perform the action if they are in the local administrators group and enter an administrator password when prompted.
 
-During startup, `eventvwr.exe` checks the registry value of the `HKCU\Software\Classes\mscfile\shell\open\command`
-registry key for the location of `mmc.exe`, which is used to open the `eventvwr.msc` saved console file. If the location
-of another binary or script is added to this registry value, it will be executed as a high-integrity process without a
-UAC prompt being displayed to the user. This rule detects this UAC bypass by monitoring processes spawned by
-`eventvwr.exe` other than `mmc.exe` and `werfault.exe`.
+For more information about the UAC and how it works, check the https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/how-user-account-control-works[official Microsoft docs page].
+
+During startup, `eventvwr.exe` checks the registry value of the `HKCU\Software\Classes\mscfile\shell\open\command` registry key for the location of `mmc.exe`, which is used to open the `eventvwr.msc` saved console file. If the location of another binary or script is added to this registry value, it will be executed as a high-integrity process without a UAC prompt being displayed to the user. This rule detects this UAC bypass by monitoring processes spawned by `eventvwr.exe` other than `mmc.exe` and `werfault.exe`.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Inspect the host for suspicious or abnormal behavior in the alert timeframe.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
 
 
-### False positive analysis
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -103,34 +105,42 @@ and any spawned child processes.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"eventvwr.exe" and not process.executable :
-("?:\\Windows\\SysWOW64\\mmc.exe",
-"?:\\Windows\\System32\\mmc.exe",
-"?:\\Windows\\SysWOW64\\WerFault.exe",
-"?:\\Windows\\System32\\WerFault.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : "eventvwr.exe" and
+  not process.executable :
+            ("?:\\Windows\\SysWOW64\\mmc.exe",
+             "?:\\Windows\\System32\\mmc.exe",
+             "?:\\Windows\\SysWOW64\\WerFault.exe",
+             "?:\\Windows\\System32\\WerFault.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -142,79 +152,19 @@ process where event.type == "start" and process.parent.name :
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[bypass-uac-via-event-viewer-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "eventvwr.exe" and not process.executable :
-("?:\\Windows\\SysWOW64\\mmc.exe",
-"?:\\Windows\\System32\\mmc.exe",
-"?:\\Windows\\SysWOW64\\WerFault.exe",
-"?:\\Windows\\System32\\WerFault.exe")
-----------------------------------
-
-Version 12 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "eventvwr.exe" and not process.executable :
-("?:\\Windows\\SysWOW64\\mmc.exe",
-"?:\\Windows\\System32\\mmc.exe",
-"?:\\Windows\\SysWOW64\\WerFault.exe",
-"?:\\Windows\\System32\\WerFault.exe")
-----------------------------------
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 9 (7.15.0 release)::
-* Formatting only
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:eventvwr.exe and not
-process.executable:("C:\Windows\SysWOW64\mmc.exe" or
-"C:\Windows\System32\mmc.exe")
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.parent.name:eventvwr.exe and event.action:"Process Create
-(rule: ProcessCreate)" and not
-process.executable:("C:\Windows\SysWOW64\mmc.exe" or
-"C:\Windows\System32\mmc.exe")
-----------------------------------
-
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/cap-sys-admin-assigned-to-binary.asciidoc b/docs/detections/prebuilt-rules/rule-details/cap-sys-admin-assigned-to-binary.asciidoc
new file mode 100644
index 0000000000..aa802491e7
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/cap-sys-admin-assigned-to-binary.asciidoc
@@ -0,0 +1,96 @@
+[[cap-sys-admin-assigned-to-binary]]
+=== CAP_SYS_ADMIN Assigned to Binary
+
+Identifies instances where a binary is granted the CAP_SYS_ADMIN capability. In Linux, the CAP_SYS_ADMIN capability is a powerful and broad capability that allows a process to perform a range of system administration operations, such as mounting and unmounting filesystems, configuring network interfaces, and accessing hardware devices. Attackers may leverage a misconfiguration for exploitation in order to escalate their privileges to root. The rule identifies previously unknown processes executing with CAP_SYS_ADMIN capabilities through the use of the new terms rule type.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:"process" and host.os.type:"linux" and event.type:"start" and event.action:"exec" and process.name:* and
+(process.thread.capabilities.effective:"CAP_SYS_ADMIN" or process.thread.capabilities.permitted:"CAP_SYS_ADMIN") and
+not user.id:"0"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
diff --git a/docs/detections/prebuilt-rules/rule-details/chkconfig-service-add.asciidoc b/docs/detections/prebuilt-rules/rule-details/chkconfig-service-add.asciidoc
index d3769dc8b8..d0e9bf9a5f 100644
--- a/docs/detections/prebuilt-rules/rule-details/chkconfig-service-add.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/chkconfig-service-add.asciidoc
@@ -5,54 +5,186 @@ Detects the use of the chkconfig binary to manually add a service for management
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-*
+* logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.intezer.com/blog/research/lightning-framework-new-linux-threat/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Threat: Lightning Framework
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 111
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Persistence
-* Lightning Framework
 
-*Version*: 100 (<<chkconfig-service-add-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.4.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Triage and analysis*
+
+
+
+*Investigating Chkconfig Service Add*
+
+Service files are configuration files in Linux systems used to define and manage system services. The `Chkconfig` binary can be used to manually add, delete or modify a service. 
+
+Malicious actors can leverage services to achieve persistence by creating or modifying service files to execute malicious commands or payloads during system startup. This allows them to maintain unauthorized access, execute additional malicious activities, or evade detection.
+
+This rule monitors the usage of the `chkconfig` binary to manually add a service for management by `chkconfig`, potentially indicating the creation of a persistence mechanism.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible Investigation Steps*
+
+
+- Investigate the service that was created or modified.
+- Investigate the currently enabled system services through the following commands `sudo chkconfig --list | grep on` and `sudo systemctl list-unit-files`.
+- Investigate the status of potentially suspicious services through the `chkconfig --list service_name` command. 
+- Search for the `rc.d` or `init.d` service files that were created or modified, and analyze their contents.
+- Investigate whether any other files in any of the available `rc.d` or `init.d` directories have been altered through OSQuery.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE (path LIKE '/etc/init.d/%' OR path LIKE '/etc/rc%.d/%')"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE (path LIKE '/etc/init.d/%' OR path LIKE '/etc/rc%.d/%')\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate syslog through the `sudo cat /var/log/syslog | grep 'LSB'` command to find traces of the LSB header of the script (if present). If syslog is being ingested into Elasticsearch, the same can be accomplished through Kibana.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+    - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+    - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+
+
+*False Positive Analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator who uses the `chkconfig` binary for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Related Rules*
+
+
+- Suspicious File Creation in /etc for Persistence - 1c84dd64-7e6c-4bad-ac73-a5014ee37042
+- Potential Persistence Through Run Control Detected - 0f4d35e4-925e-4959-ab24-911be207ee6f
+- Potential Persistence Through init.d Detected - 474fd20e-14cc-49c5-8160-d9ab4ba16c8b
+- New Systemd Timer Created - 7fb500fa-8e24-4bd1-9480-2a819352602c
+- New Systemd Service Created by Previously Unknown Process - 17b0a495-4d9f-414c-8ad0-92f018b8e001
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Delete the service/timer or restore its original configuration.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.executable :
-"/usr/sbin/chkconfig" and process.args : "--add") or (process.args
-: "*chkconfig" and process.args : "--add")
+[source, js]
 ----------------------------------
+process where host.os.type == "linux" and event.action in ("exec", "exec_event") and
+( 
+  (process.executable : "/usr/sbin/chkconfig" and process.args : "--add") or
+  (process.args : "*chkconfig" and process.args : "--add")
+) and 
+not process.parent.name in ("rpm", "qualys-scan-util", "qualys-cloud-agent", "update-alternatives") and
+not process.parent.args : ("/var/tmp/rpm*", "/var/lib/waagent/*")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,17 +196,7 @@ process where event.type == "start" and (process.executable :
 ** Name: Boot or Logon Initialization Scripts
 ** ID: T1037
 ** Reference URL: https://attack.mitre.org/techniques/T1037/
-
-[[chkconfig-service-add-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and (process.executable :
-"/usr/sbin/chkconfig" and process.args : "--add") or (process.args
-: "*chkconfig" and process.args : "--add")
-----------------------------------
-
+* Sub-technique:
+** Name: RC Scripts
+** ID: T1037.004
+** Reference URL: https://attack.mitre.org/techniques/T1037/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/clearing-windows-console-history.asciidoc b/docs/detections/prebuilt-rules/rule-details/clearing-windows-console-history.asciidoc
index dedd251583..d23dfc1c0c 100644
--- a/docs/detections/prebuilt-rules/rule-details/clearing-windows-console-history.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/clearing-windows-console-history.asciidoc
@@ -5,111 +5,121 @@ Identifies when a user attempts to clear console history. An adversary may clear
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://stefanos.cloud/kb/how-to-clear-the-powershell-command-history/
 * https://www.shellhacks.com/clear-history-powershell/
 * https://community.sophos.com/sophos-labs/b/blog/posts/powershell-command-history-forensics
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Version*: 102 (<<clearing-windows-console-history-history, version history>>)
+*Version*: 111
 
-*Added ({stack} release)*: 8.0.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Clearing Windows Console History
+*Triage and analysis*
+
+
+
+*Investigating Clearing Windows Console History*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+Attackers can try to cover their tracks by clearing PowerShell console history. PowerShell has two different ways of logging commands: the built-in history and the command history managed by the PSReadLine module. This rule looks for the execution of commands that can clear the built-in PowerShell logs or delete the `ConsoleHost_history.txt` file.
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This
-makes it available for use in various environments, and creates an attractive way for attackers to execute code.
 
-Attackers can try to cover their tracks by clearing PowerShell console history. PowerShell has two different ways of
-logging commands: the built-in history and the command history managed by the PSReadLine module. This rule looks for the
-execution of commands that can clear the built-in PowerShell logs or delete the `ConsoleHost_history.txt` file.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
   - Verify if any other anti-forensics behaviors were observed.
-- Investigate the PowerShell logs on the SIEM to determine if there was suspicious behavior that an attacker may be
-trying to cover up.
+- Investigate the PowerShell logs on the SIEM to determine if there was suspicious behavior that an attacker may be trying to cover up.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
   - Ensure that PowerShell auditing policies and log collection are in place to grant future visibility.
-----------------------------------
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-("powershell.exe", "pwsh.exe", "powershell_ise.exe") or
-process.pe.original_file_name == "PowerShell.EXE") and
-(process.args : "*Clear-History*" or (process.args : ("*Remove-
-Item*", "rm") and process.args : ("*ConsoleHost_history.txt*", "*(Get-
-PSReadlineOption).HistorySavePath*")) or (process.args : "*Set-
-PSReadlineOption*" and process.args : "*SaveNothing*"))
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe") or ?process.pe.original_file_name == "PowerShell.EXE") and
+     (process.args : "*Clear-History*" or
+     (process.args : ("*Remove-Item*", "rm") and process.args : ("*ConsoleHost_history.txt*", "*(Get-PSReadlineOption).HistorySavePath*")) or
+     (process.args : "*Set-PSReadlineOption*" and process.args : "*SaveNothing*"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -118,36 +128,22 @@ PSReadlineOption*" and process.args : "*SaveNothing*"))
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
 * Technique:
-** Name: Indicator Removal on Host
+** Name: Indicator Removal
 ** ID: T1070
 ** Reference URL: https://attack.mitre.org/techniques/T1070/
-
-[[clearing-windows-console-history-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.action == "start" and (process.name :
-("powershell.exe", "pwsh.exe", "powershell_ise.exe") or
-process.pe.original_file_name == "PowerShell.EXE") and
-(process.args : "*Clear-History*" or (process.args : ("*Remove-
-Item*", "rm") and process.args : ("*ConsoleHost_history.txt*", "*(Get-
-PSReadlineOption).HistorySavePath*")) or (process.args : "*Set-
-PSReadlineOption*" and process.args : "*SaveNothing*"))
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Clear Command History
+** ID: T1070.003
+** Reference URL: https://attack.mitre.org/techniques/T1070/003/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/clearing-windows-event-logs.asciidoc b/docs/detections/prebuilt-rules/rule-details/clearing-windows-event-logs.asciidoc
index d5bf56d453..1376cf864d 100644
--- a/docs/detections/prebuilt-rules/rule-details/clearing-windows-event-logs.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/clearing-windows-event-logs.asciidoc
@@ -5,207 +5,139 @@ Identifies attempts to clear or disable Windows event log stores using Windows w
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<clearing-windows-event-logs-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Clearing Windows Event Logs
+*Triage and analysis*
+
+
+
+*Investigating Clearing Windows Event Logs*
+
 
-Windows event logs are a fundamental data source for security monitoring, forensics, and incident response. Adversaries
-can tamper, clear, and delete this data to break SIEM detections, cover their tracks, and slow down incident response.
+Windows event logs are a fundamental data source for security monitoring, forensics, and incident response. Adversaries can tamper, clear, and delete this data to break SIEM detections, cover their tracks, and slow down incident response.
 
 This rule looks for the execution of the `wevtutil.exe` utility or the `Clear-EventLog` cmdlet to clear event logs.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
   - Verify if any other anti-forensics behaviors were observed.
 - Investigate the event logs prior to the action for suspicious behaviors that an attacker may be trying to cover up.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity
-and there are justifications for this action.
-- Analyze whether the cleared event log is pertinent to security and general monitoring. Administrators can clear
-non-relevant event logs using this mechanism. If this activity is expected and noisy in your environment, consider
-adding exceptions — preferably with a combination of user and command line conditions.
+*False positive analysis*
 
-### Response and remediation
 
-- Initiate the incident response process based on the outcome of the triage.
-  - This activity is potentially done after the adversary achieves its objectives on the host. Ensure that previous
-  actions, if any, are investigated accordingly with their response playbooks.
-- Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity and there are justifications for this action.
+- Analyze whether the cleared event log is pertinent to security and general monitoring. Administrators can clear non-relevant event logs using this mechanism. If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of user and command line conditions.
 
 
-==== Rule query
+*Response and remediation*
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and ( (process.name :
-"wevtutil.exe" or process.pe.original_file_name == "wevtutil.exe") and
-process.args : ("/e:false", "cl", "clear-log") ) or (
-process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe")
-and process.args : "Clear-EventLog" )
-----------------------------------
-
-==== Threat mapping
-
-*Framework*: MITRE ATT&CK^TM^
-
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Indicator Removal on Host
-** ID: T1070
-** Reference URL: https://attack.mitre.org/techniques/T1070/
+- Initiate the incident response process based on the outcome of the triage.
+  - This activity is potentially done after the adversary achieves its objectives on the host. Ensure that previous actions, if any, are investigated accordingly with their response playbooks.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-[[clearing-windows-event-logs-history]]
-==== Rule version history
 
-Version 102 (8.6.0 release)::
-* Formatting only
+==== Setup
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("process_started", "start") and
-(process.name : "wevtutil.exe" or process.pe.original_file_name ==
-"wevtutil.exe") and process.args : ("/e:false", "cl", "clear-log")
-or process.name : ("powershell.exe", "pwsh.exe",
-"powershell_ise.exe") and process.args : "Clear-EventLog"
-----------------------------------
 
-Version 15 (8.4.0 release)::
-* Formatting only
 
-Version 13 (8.3.0 release)::
-* Formatting only
+*Setup*
 
-Version 12 (8.2.0 release)::
-* Formatting only
 
-Version 11 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("process_started", "start") and
-(process.name : "wevtutil.exe" or process.pe.original_file_name ==
-"wevtutil.exe") and process.args : ("/e:false", "cl", "clear-log")
-or process.name : "powershell.exe" and process.args : "Clear-
-EventLog"
-----------------------------------
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(process_started or start) and
-(process.name:"wevtutil.exe" or
-process.pe.original_file_name:"wevtutil.exe") and
-process.args:("/e:false" or cl or "clear-log") or
-process.name:"powershell.exe" and process.args:"Clear-EventLog"
-----------------------------------
 
-Version 8 (7.12.0 release)::
-* Formatting only
+==== Rule query
 
-Version 7 (7.11.2 release)::
-* Formatting only
 
-Version 6 (7.11.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:wevtutil.exe and process.args:cl or
-process.name:powershell.exe and process.args:Clear-EventLog
-----------------------------------
-
-Version 5 (7.10.0 release)::
-* Formatting only
+process where host.os.type == "windows" and event.type == "start" and
+(
+  (
+    (process.name : "wevtutil.exe" or ?process.pe.original_file_name == "wevtutil.exe") and
+    process.args : ("/e:false", "cl", "clear-log")
+  ) or
+  (
+    process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe") and
+    process.args : "Clear-EventLog"
+  )
+)
 
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:wevtutil.exe and process.args:cl or
-process.name:powershell.exe and process.args:Clear-EventLog
 ----------------------------------
 
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-(process.name:"wevtutil.exe" and process.args:"cl") or
-(process.name:"powershell.exe" and process.args:"Clear-EventLog")
-----------------------------------
+*Framework*: MITRE ATT&CK^TM^
 
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indicator Removal
+** ID: T1070
+** Reference URL: https://attack.mitre.org/techniques/T1070/
+* Sub-technique:
+** Name: Clear Windows Event Logs
+** ID: T1070.001
+** Reference URL: https://attack.mitre.org/techniques/T1070/001/
+* Sub-technique:
+** Name: Disable Windows Event Logging
+** ID: T1562.002
+** Reference URL: https://attack.mitre.org/techniques/T1562/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/cobalt-strike-command-and-control-beacon.asciidoc b/docs/detections/prebuilt-rules/rule-details/cobalt-strike-command-and-control-beacon.asciidoc
index 7ea88dd65b..66b8182f29 100644
--- a/docs/detections/prebuilt-rules/rule-details/cobalt-strike-command-and-control-beacon.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/cobalt-strike-command-and-control-beacon.asciidoc
@@ -5,73 +5,63 @@ Cobalt Strike is a threat emulation platform commonly modified and used by adver
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.morphisec.com/fin7-attacks-restaurant-industry
 * https://www.fireeye.com/blog/threat-research/2017/04/fin7-phishing-lnk.html
 * https://www.elastic.co/security-labs/collecting-cobalt-strike-beacons-with-the-elastic-stack
 
-*Tags*:
-
-* Elastic
-* Network
-* Threat Detection
-* Command and Control
-* Host
+*Tags*: 
 
-*Version*: 101 (<<cobalt-strike-command-and-control-beacon-history, version history>>)
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Domain: Endpoint
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-This rule should be tailored to either exclude systems, as sources or destinations, in which this behavior is expected.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Threat intel
 
-This activity has been observed in FIN7 campaigns.
-----------------------------------
+*Threat intel*
 
 
+This activity has been observed in FIN7 campaigns.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network OR network_traffic) AND type:(tls OR http) AND
-network.transport:tcp AND
-destination.domain:/[a-z]{3}.stage.[0-9]{8}\..*/
+[source, js]
 ----------------------------------
+((event.category: (network OR network_traffic) AND type: (tls OR http))
+    OR event.dataset: (network_traffic.tls OR network_traffic.http)
+) AND destination.domain:/[a-z]{3}.stage.[0-9]{8}\..*/
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -83,35 +73,11 @@ destination.domain:/[a-z]{3}.stage.[0-9]{8}\..*/
 ** Name: Application Layer Protocol
 ** ID: T1071
 ** Reference URL: https://attack.mitre.org/techniques/T1071/
-
-[[cobalt-strike-command-and-control-beacon-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network OR network_traffic) AND type:(tls OR http) AND
-network.transport:tcp AND
-destination.domain:/[a-z]{3}.stage.[0-9]{8}\..*/
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Technique:
+** Name: Dynamic Resolution
+** ID: T1568
+** Reference URL: https://attack.mitre.org/techniques/T1568/
+* Sub-technique:
+** Name: Domain Generation Algorithms
+** ID: T1568.002
+** Reference URL: https://attack.mitre.org/techniques/T1568/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/code-signing-policy-modification-through-built-in-tools.asciidoc b/docs/detections/prebuilt-rules/rule-details/code-signing-policy-modification-through-built-in-tools.asciidoc
new file mode 100644
index 0000000000..f6f1772ef3
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/code-signing-policy-modification-through-built-in-tools.asciidoc
@@ -0,0 +1,135 @@
+[[code-signing-policy-modification-through-built-in-tools]]
+=== Code Signing Policy Modification Through Built-in tools
+
+Identifies attempts to disable/modify the code signing policy through system native utilities. Code signing provides authenticity on a program, and grants the user with the ability to check whether the program has been tampered with. By allowing the execution of unsigned or self-signed code, threat actors can craft and execute malicious code.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Code Signing Policy Modification Through Built-in tools*
+
+
+Windows Driver Signature Enforcement (DSE) is a security feature introduced by Microsoft to enforce that only signed drivers can be loaded and executed into the kernel (ring 0). This feature was introduced to prevent attackers from loading their malicious drivers on targets. If the driver has an invalid signature, the system will not allow it to be loaded.
+
+This protection is essential for maintaining the security of the system. However, attackers or even administrators can disable this feature and load untrusted drivers, as this can put the system at risk. Therefore, it is important to keep this feature enabled and only load drivers from trusted sources to ensure the integrity and security of the system.
+
+This rule identifies commands that can disable the Driver Signature Enforcement feature.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Use Osquery and endpoint driver events (`event.category = "driver"`) to investigate if suspicious drivers were loaded into the system after the command was executed.
+  - !{osquery{"label":"Osquery - Retrieve All Non-Microsoft Drivers with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, class, description, directory, image, issuer_name, manufacturer, service, signed, subject_name FROM drivers JOIN authenticode ON drivers.image = authenticode.path JOIN hash ON drivers.image = hash.path WHERE NOT (provider == \"Microsoft\" AND signed == \"1\")\n"}}
+  - !{osquery{"label":"Osquery - Retrieve All Unsigned Drivers with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, class, description, directory, image, issuer_name, manufacturer, service, signed, subject_name FROM drivers JOIN authenticode ON drivers.image = authenticode.path JOIN hash ON drivers.image = hash.path WHERE signed == \"0\"\n"}}
+- Identify the driver's `Device Name` and `Service Name`.
+- Check for alerts from the rules specified in the `Related Rules` section.
+
+
+*False positive analysis*
+
+
+- This activity should not happen legitimately. The security team should address any potential benign true positive (B-TP), as this configuration can put the user and the domain at risk.
+
+
+*Related Rules*
+
+
+- First Time Seen Driver Loaded - df0fd41e-5590-4965-ad5e-cd079ec22fa9
+- Untrusted Driver Loaded - d8ab1ec1-feeb-48b9-89e7-c12e189448aa
+- Code Signing Policy Modification Through Registry - da7733b1-fe08-487e-b536-0a04c6d8b0cd
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Disable and uninstall all suspicious drivers found in the system. This can be done via Device Manager. (Note that this step may require you to boot the system into Safe Mode.)
+- Remove the related services and registry keys found in the system. Note that the service will probably not stop if the driver is still installed.
+  - This can be done via PowerShell `Remove-Service` cmdlet.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Remove and block malicious artifacts identified during triage.
+- Ensure that the Driver Signature Enforcement is enabled on the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name: "bcdedit.exe" or ?process.pe.original_file_name == "bcdedit.exe") and process.args: ("-set", "/set") and 
+  process.args: ("TESTSIGNING", "nointegritychecks", "loadoptions", "DISABLE_INTEGRITY_CHECKS")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Subvert Trust Controls
+** ID: T1553
+** Reference URL: https://attack.mitre.org/techniques/T1553/
+* Sub-technique:
+** Name: Code Signing Policy Modification
+** ID: T1553.006
+** Reference URL: https://attack.mitre.org/techniques/T1553/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/code-signing-policy-modification-through-registry.asciidoc b/docs/detections/prebuilt-rules/rule-details/code-signing-policy-modification-through-registry.asciidoc
new file mode 100644
index 0000000000..d78859bdb9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/code-signing-policy-modification-through-registry.asciidoc
@@ -0,0 +1,146 @@
+[[code-signing-policy-modification-through-registry]]
+=== Code Signing Policy Modification Through Registry
+
+Identifies attempts to disable the code signing policy through the registry. Code signing provides authenticity on a program, and grants the user with the ability to check whether the program has been tampered with. By allowing the execution of unsigned or self-signed code, threat actors can craft and execute malicious code.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 9
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Code Signing Policy Modification Through Registry*
+
+
+Microsoft created the Windows Driver Signature Enforcement (DSE) security feature to prevent drivers with invalid signatures from loading and executing into the kernel (ring 0). DSE aims to protect systems by blocking attackers from loading malicious drivers on targets. 
+
+This protection is essential for maintaining system security. However, attackers or administrators can disable DSE and load untrusted drivers, which can put the system at risk. Therefore, it's important to keep this feature enabled and only load drivers from trusted sources to ensure system integrity and security.
+
+This rule identifies registry modifications that can disable DSE.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Use Osquery and endpoint driver events (`event.category = "driver"`) to investigate if suspicious drivers were loaded into the system after the registry was modified.
+  - !{osquery{"label":"Osquery - Retrieve All Non-Microsoft Drivers with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, class, description, directory, image, issuer_name, manufacturer, service, signed, subject_name FROM drivers JOIN authenticode ON drivers.image = authenticode.path JOIN hash ON drivers.image = hash.path WHERE NOT (provider == \"Microsoft\" AND signed == \"1\")\n"}}
+  - !{osquery{"label":"Osquery - Retrieve All Unsigned Drivers with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, class, description, directory, image, issuer_name, manufacturer, service, signed, subject_name FROM drivers JOIN authenticode ON drivers.image = authenticode.path JOIN hash ON drivers.image = hash.path WHERE signed == \"0\"\n"}}
+- Identify the driver's `Device Name` and `Service Name`.
+- Check for alerts from the rules specified in the `Related Rules` section.
+
+
+*False positive analysis*
+
+
+- This activity should not happen legitimately. The security team should address any potential benign true positive (B-TP), as this configuration can put the user and the domain at risk.
+
+
+*Related Rules*
+
+
+- First Time Seen Driver Loaded - df0fd41e-5590-4965-ad5e-cd079ec22fa9
+- Untrusted Driver Loaded - d8ab1ec1-feeb-48b9-89e7-c12e189448aa
+- Code Signing Policy Modification Through Built-in tools - b43570de-a908-4f7f-8bdb-b2df6ffd8c80
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Disable and uninstall all suspicious drivers found in the system. This can be done via Device Manager. (Note that this step may require you to boot the system into Safe Mode.)
+- Remove the related services and registry keys found in the system. Note that the service will probably not stop if the driver is still installed.
+  - This can be done via PowerShell `Remove-Service` cmdlet.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Remove and block malicious artifacts identified during triage.
+- Ensure that the Driver Signature Enforcement is enabled on the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+registry where host.os.type == "windows" and event.type : ("creation", "change") and
+(
+  registry.path : (
+    "HKEY_USERS\\*\\Software\\Policies\\Microsoft\\Windows NT\\Driver Signing\\BehaviorOnFailedVerify",
+    "HKU\\*\\Software\\Policies\\Microsoft\\Windows NT\\Driver Signing\\BehaviorOnFailedVerify",
+    "\\REGISTRY\\USER\\*\\Software\\Policies\\Microsoft\\Windows NT\\Driver Signing\\BehaviorOnFailedVerify"
+  ) and
+  registry.value: "BehaviorOnFailedVerify" and
+  registry.data.strings : ("0", "0x00000000", "1", "0x00000001")
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Subvert Trust Controls
+** ID: T1553
+** Reference URL: https://attack.mitre.org/techniques/T1553/
+* Sub-technique:
+** Name: Code Signing Policy Modification
+** ID: T1553.006
+** Reference URL: https://attack.mitre.org/techniques/T1553/006/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/command-execution-via-solarwinds-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/command-execution-via-solarwinds-process.asciidoc
index e799442337..c74b343b80 100644
--- a/docs/detections/prebuilt-rules/rule-details/command-execution-via-solarwinds-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/command-execution-via-solarwinds-process.asciidoc
@@ -5,74 +5,78 @@ A suspicious SolarWinds child process (Cmd.exe or Powershell.exe) was detected.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.fireeye.com/blog/threat-research/2020/12/evasive-attacker-leverages-solarwinds-supply-chain-compromises-with-sunburst-backdoor.html
 * https://github.com/mandiant/sunburst_countermeasures/blob/main/rules/SUNBURST/hxioc/SUNBURST%20SUSPICIOUS%20FILEWRITES%20(METHODOLOGY).ioc
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Elastic Endgame
-
-*Version*: 102 (<<command-execution-via-solarwinds-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Initial Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Trusted SolarWinds child processes. Verify process details such as network connections and file writes.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name: ("cmd.exe",
-"powershell.exe") and process.parent.name: (
-"ConfigurationWizard*.exe", "NetflowDatabaseMaintenance*.exe",
-"NetFlowService*.exe", "SolarWinds.Administration*.exe",
-"SolarWinds.Collector.Service*.exe", "SolarwindsDiagnostics*.exe"
-)
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.name: ("cmd.exe", "powershell.exe") and
+process.parent.name: (
+     "ConfigurationWizard*.exe",
+     "NetflowDatabaseMaintenance*.exe",
+     "NetFlowService*.exe",
+     "SolarWinds.Administration*.exe",
+     "SolarWinds.Collector.Service*.exe",
+     "SolarwindsDiagnostics*.exe"
+     )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,8 +88,14 @@ process where event.type == "start" and process.name: ("cmd.exe",
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -94,38 +104,7 @@ process where event.type == "start" and process.name: ("cmd.exe",
 ** Name: Supply Chain Compromise
 ** ID: T1195
 ** Reference URL: https://attack.mitre.org/techniques/T1195/
-
-[[command-execution-via-solarwinds-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name: ("cmd.exe", "powershell.exe") and process.parent.name: (
-"ConfigurationWizard*.exe", "NetflowDatabaseMaintenance*.exe",
-"NetFlowService*.exe", "SolarWinds.Administration*.exe",
-"SolarWinds.Collector.Service*.exe", "SolarwindsDiagnostics*.exe"
-)
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Compromise Software Supply Chain
+** ID: T1195.002
+** Reference URL: https://attack.mitre.org/techniques/T1195/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/command-prompt-network-connection.asciidoc b/docs/detections/prebuilt-rules/rule-details/command-prompt-network-connection.asciidoc
index bef3807975..d421dc7031 100644
--- a/docs/detections/prebuilt-rules/rule-details/command-prompt-network-connection.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/command-prompt-network-connection.asciidoc
@@ -5,67 +5,133 @@ Identifies cmd.exe making a network connection. Adversaries could abuse cmd.exe
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
 
-*Version*: 100 (<<command-prompt-network-connection-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.6.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
+
+
+
+*Investigating Command Prompt Network Connection*
+
+
+Attackers commonly transfer tooling or malware from external systems into a compromised environment using a command and control channel. However, they can also abuse signed utilities to drop these files.
+
+This rule looks for a network connection to an external address from the `cmd.exe` utility, which can indicate the abuse of the utility to download malicious files and tools.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+  - Investigate the file digital signature and process original filename, if suspicious, treat it as potential malware.
+- Investigate the target host that the signed binary is communicating with.
+  - Check if the domain is newly registered or unexpected.
+  - Check the reputation of the domain or IP address.
+- Examine if any file was downloaded and check if it is an executable or script.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the downloaded file using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of destination IP address and file name conditions.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Administrators may use the command prompt for regular administrative tasks. It's important to baseline your environment for network connections being made from the command prompt to determine any abnormal use of this tool.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where process.name :
-"cmd.exe" and event.type == "start"] [network where process.name :
-"cmd.exe" and not cidrmatch(destination.ip, "10.0.0.0/8",
-"127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
-"192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32",
-"192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24",
-"192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
-"192.175.48.0/24", "198.18.0.0/15",
-"198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
-"FE80::/10", "FF00::/8")]
+[source, js]
 ----------------------------------
+sequence by process.entity_id
+  [process where host.os.type == "windows" and process.name : "cmd.exe" and event.type == "start"]
+  [network where host.os.type == "windows" and process.name : "cmd.exe" and
+     not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
+                                  "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32",
+                                  "192.0.0.171/32", "192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24",
+                                  "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10", "192.175.48.0/24",
+                                  "198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
+                                  "FE80::/10", "FF00::/8") and
+    not dns.question.name : (
+          "wpad", "localhost", "ocsp.comodoca.com", "ocsp.digicert.com", "ocsp.sectigo.com", "crl.comodoca.com"
+    )]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,8 +143,6 @@ sequence by process.entity_id [process where process.name :
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-
 * Tactic:
 ** Name: Command and Control
 ** ID: TA0011
@@ -87,60 +151,3 @@ sequence by process.entity_id [process where process.name :
 ** Name: Ingress Tool Transfer
 ** ID: T1105
 ** Reference URL: https://attack.mitre.org/techniques/T1105/
-
-[[command-prompt-network-connection-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 7 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where process.name :
-"cmd.exe" and event.type == "start"] [network where process.name :
-"cmd.exe" and not cidrmatch(destination.ip, "10.0.0.0/8",
-"172.16.0.0/12", "192.168.0.0/16")]
-----------------------------------
-
-Version 6 (7.12.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:connection and
-process.name:cmd.exe and not destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:cmd.exe and event.action:"Network connection detected
-(rule: NetworkConnect)" and not destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:cmd.exe and event.action:"Network connection detected
-(rule: NetworkConnect)" and not destination.ip:10.0.0.0/8 and not
-destination.ip:172.16.0.0/12 and not destination.ip:192.168.0.0/16
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/command-shell-activity-started-via-rundll32.asciidoc b/docs/detections/prebuilt-rules/rule-details/command-shell-activity-started-via-rundll32.asciidoc
index cc4cb80b6e..cd4f9df9c6 100644
--- a/docs/detections/prebuilt-rules/rule-details/command-shell-activity-started-via-rundll32.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/command-shell-activity-started-via-rundll32.asciidoc
@@ -5,69 +5,73 @@ Identifies command shell activity started via RunDLL32, which is commonly abused
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 101 (<<command-shell-activity-started-via-rundll32-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Credential Access
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Microsoft Windows installers leveraging RunDLL32 for installation.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : ("cmd.exe",
-"powershell.exe") and process.parent.name : "rundll32.exe" and
-process.parent.command_line != null and /* common FPs can be added
-here */ not process.parent.args :
-("C:\\Windows\\System32\\SHELL32.dll,RunAsNewUser_RunDLL",
-"C:\\WINDOWS\\*.tmp,zzzzInvokeManagedCustomActionOutOfProc")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.name : ("cmd.exe", "powershell.exe") and
+  process.parent.name : "rundll32.exe" and process.parent.command_line != null and
+  /* common FPs can be added here */
+  not process.parent.args : ("C:\\Windows\\System32\\SHELL32.dll,RunAsNewUser_RunDLL",
+                             "C:\\WINDOWS\\*.tmp,zzzzInvokeManagedCustomActionOutOfProc")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,37 +83,31 @@ here */ not process.parent.args :
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[command-shell-activity-started-via-rundll32-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : ("cmd.exe", "powershell.exe") and process.parent.name
-: "rundll32.exe" and /* common FPs can be added here */ not
-process.parent.args :
-"C:\\Windows\\System32\\SHELL32.dll,RunAsNewUser_RunDLL"
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Unsecured Credentials
+** ID: T1552
+** Reference URL: https://attack.mitre.org/techniques/T1552/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: Rundll32
+** ID: T1218.011
+** Reference URL: https://attack.mitre.org/techniques/T1218/011/
diff --git a/docs/detections/prebuilt-rules/rule-details/component-object-model-hijacking.asciidoc b/docs/detections/prebuilt-rules/rule-details/component-object-model-hijacking.asciidoc
index 644915273e..a79ffc8512 100644
--- a/docs/detections/prebuilt-rules/rule-details/component-object-model-hijacking.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/component-object-model-hijacking.asciidoc
@@ -5,58 +5,63 @@ Identifies Component Object Model (COM) hijacking via registry modification. Adv
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://bohops.com/2018/08/18/abusing-the-com-registry-structure-part-2-loading-techniques-for-evasion-and-persistence/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
-
-*Version*: 102 (<<component-object-model-hijacking-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Tactic: Privilege Escalation
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 113
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Component Object Model Hijacking
+*Triage and analysis*
+
+
+
+*Investigating Component Object Model Hijacking*
+
 
 Adversaries can insert malicious code that can be executed in place of legitimate software through hijacking the COM references and relationships as a means of persistence.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
@@ -70,11 +75,15 @@ for prevalence, whether they are located in expected locations, and if they are
   - Use the PowerShell Get-FileHash cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - Some Microsoft executables will reference the LocalServer32 registry key value for the location of external COM objects.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -82,49 +91,86 @@ for prevalence, whether they are located in expected locations, and if they are
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where /* not necessary but good for filtering privileged
-installations */ user.domain != "NT AUTHORITY" and ( (registry.path
-: "HK*\\InprocServer32\\" and registry.data.strings: ("scrobj.dll",
-"C:\\*\\scrobj.dll") and not registry.path :
-"*\\{06290BD*-48AA-11D2-8432-006008C3FBFC}\\*") or /* in general COM
-Registry changes on Users Hive is less noisy and worth alerting */
-(registry.path : ("HKEY_USERS\\*\\InprocServer32\\*",
-"HKEY_USERS\\*\\LocalServer32\\*",
-"HKEY_USERS\\*\\DelegateExecute\\*",
-"HKEY_USERS\\*\\TreatAs\\*",
-"HKEY_USERS\\*\\ScriptletURL\\*") and not (process.executable :
-"?:\\Program Files*\\Veeam\\Backup and
-Replication\\Console\\veeam.backup.shell.exe" and registry.path
-: "HKEY_USERS\\S-1-*_Classes\\CLSID\\*\\LocalServer32\\")) or
-(registry.path : "HKLM\\*\\InProcServer32\\*" and
-registry.data.strings : ("*\\Users\\*", "*\\ProgramData\\*")) ) and
-/* removes false-positives generated by OneDrive and Teams */ not
-process.name :
-("OneDrive.exe","OneDriveSetup.exe","FileSyncConfig.exe","Teams.exe")
-and /* Teams DLL loaded by regsvr */ not (process.name:
-"regsvr32.exe" and registry.data.strings : "*Microsoft.Teams.*.dll")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and
+  /* not necessary but good for filtering privileged installations */
+  user.domain != "NT AUTHORITY" and process.executable != null and 
+  (
+    (
+      registry.path : "HK*\\InprocServer32\\" and
+      registry.data.strings: ("scrobj.dll", "?:\\*\\scrobj.dll") and
+      not registry.path : "*\\{06290BD*-48AA-11D2-8432-006008C3FBFC}\\*"
+    ) or
+
+    (
+      registry.path : "HKLM\\*\\InProcServer32\\*" and
+        registry.data.strings : ("*\\Users\\*", "*\\ProgramData\\*")
+    ) or
+
+    /* in general COM Registry changes on Users Hive is less noisy and worth alerting */
+    (
+      registry.path : (
+        "HKEY_USERS\\*\\InprocServer32\\",
+        "HKEY_USERS\\*\\LocalServer32\\",
+        "HKEY_USERS\\*\\DelegateExecute",
+        "HKEY_USERS\\*\\TreatAs\\",
+        "HKEY_USERS\\*\\ScriptletURL*"
+      )  
+    )
+  ) and 
+
+      not  (
+            process.code_signature.trusted == true and
+            process.code_signature.subject_name in 
+                         ("Island Technology Inc.", "Google LLC", "Grammarly, Inc.", "Dropbox, Inc", "REFINITIV US LLC", "HP Inc.",
+                          "Citrix Systems, Inc.", "Adobe Inc.", "Veeam Software Group GmbH", "Zhuhai Kingsoft Office Software Co., Ltd.",
+                          "Oracle America, Inc.")
+        ) and 
+
+  /* excludes Microsoft signed noisy processes */
+  not
+  (
+    process.name : ("OneDrive.exe", "OneDriveSetup.exe", "FileSyncConfig.exe", "Teams.exe", "MicrosoftEdgeUpdate.exe", "msrdcw.exe", "MicrosoftEdgeUpdateComRegisterShell64.exe") and
+    process.code_signature.trusted == true and process.code_signature.subject_name in ("Microsoft Windows", "Microsoft Corporation")
+  ) and
+  
+  not process.executable : 
+                  ("?:\\Program Files (x86)\\*.exe", 
+                   "?:\\Program Files\\*.exe",
+                   "?:\\Windows\\System32\\svchost.exe", 
+                   "?:\\Windows\\System32\\msiexec.exe", 
+                   "?:\\Windows\\SysWOW64\\regsvr32.exe",
+                   "?:\\Windows\\System32\\regsvr32.exe",
+                   "?:\\Windows\\System32\\DriverStore\\FileRepository\\*.exe", 
+                   "?:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\*\\MsMpEng.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -136,134 +182,27 @@ and /* Teams DLL loaded by regsvr */ not (process.name:
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[component-object-model-hijacking-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where (registry.path : "HK*}\\InprocServer32\\" and
-registry.data.strings: ("scrobj.dll", "C:\\*\\scrobj.dll") and not
-registry.path : "*\\{06290BD*-48AA-11D2-8432-006008C3FBFC}\\*") or
-/* in general COM Registry changes on Users Hive is less noisy and
-worth alerting */ (registry.path :
-("HKEY_USERS\\*Classes\\*\\InprocServer32\\",
-"HKEY_USERS\\*Classes\\*\\LocalServer32\\",
-"HKEY_USERS\\*Classes\\*\\DelegateExecute\\",
-"HKEY_USERS\\*Classes\\*\\TreatAs\\",
-"HKEY_USERS\\*Classes\\CLSID\\*\\ScriptletURL\\") and not
-(process.executable : "?:\\Program Files*\\Veeam\\Backup and
-Replication\\Console\\veeam.backup.shell.exe" and registry.path
-: "HKEY_USERS\\S-1-5-21-*_Classes\\CLSID\\*\\LocalServer32\\") and /*
-not necessary but good for filtering privileged installations */
-user.domain != "NT AUTHORITY" ) and /* removes false-positives
-generated by OneDrive and Teams */ not process.name :
-("OneDrive.exe","OneDriveSetup.exe","FileSyncConfig.exe","Teams.exe")
-and /* Teams DLL loaded by regsvr */ not (process.name:
-"regsvr32.exe" and registry.data.strings : "*Microsoft.Teams.*.dll")
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where (registry.path : "HK*}\\InprocServer32\\" and
-registry.data.strings: ("scrobj.dll", "C:\\*\\scrobj.dll") and not
-registry.path : "*\\{06290BD*-48AA-11D2-8432-006008C3FBFC}\\*") or
-/* in general COM Registry changes on Users Hive is less noisy and
-worth alerting */ (registry.path :
-("HKEY_USERS\\*Classes\\*\\InprocServer32\\",
-"HKEY_USERS\\*Classes\\*\\LocalServer32\\",
-"HKEY_USERS\\*Classes\\*\\DelegateExecute\\",
-"HKEY_USERS\\*Classes\\*\\TreatAs\\",
-"HKEY_USERS\\*Classes\\CLSID\\*\\ScriptletURL\\") and not
-(process.executable : "?:\\Program Files*\\Veeam\\Backup and
-Replication\\Console\\veeam.backup.shell.exe" and registry.path
-: "HKEY_USERS\\S-1-5-21-*_Classes\\CLSID\\*\\LocalServer32\\") and /*
-not necessary but good for filtering privileged installations */
-user.domain != "NT AUTHORITY" ) and /* removes false-positives
-generated by OneDrive and Teams */ not process.name :
-("OneDrive.exe","OneDriveSetup.exe","FileSyncConfig.exe","Teams.exe")
-and /* Teams DLL loaded by regsvr */ not (process.name:
-"regsvr32.exe" and registry.data.strings : "*Microsoft.Teams.*.dll")
-----------------------------------
-
-Version 7 (8.3.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where /* uncomment once length is stable
-length(bytes_written_string) > 0 and */ (registry.path :
-"HK*}\\InprocServer32\\" and registry.data.strings: ("scrobj.dll",
-"C:\\*\\scrobj.dll") and not registry.path :
-"*\\{06290BD*-48AA-11D2-8432-006008C3FBFC}\\*") or /* in general
-COM Registry changes on Users Hive is less noisy and worth alerting */
-(registry.path : ("HKEY_USERS\\*Classes\\*\\InprocServer32\\",
-"HKEY_USERS\\*Classes\\*\\LocalServer32\\",
-"HKEY_USERS\\*Classes\\*\\DelegateExecute\\",
-"HKEY_USERS\\*Classes\\*\\TreatAs\\",
-"HKEY_USERS\\*Classes\\CLSID\\*\\ScriptletURL\\") and not
-(process.executable : "?:\\Program Files*\\Veeam\\Backup and
-Replication\\Console\\veeam.backup.shell.exe" and registry.path
-: "HKEY_USERS\\S-1-5-21-*_Classes\\CLSID\\*\\LocalServer32\\") and /*
-not necessary but good for filtering privileged installations */
-user.domain != "NT AUTHORITY")
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where /* uncomment once length is stable
-length(bytes_written_string) > 0 and */ (registry.path :
-"HK*}\\InprocServer32\\" and registry.data.strings: ("scrobj.dll",
-"C:\\*\\scrobj.dll") and not registry.path :
-"*\\{06290BD*-48AA-11D2-8432-006008C3FBFC}\\*") or /* in general
-COM Registry changes on Users Hive is less noisy and worth alerting */
-(registry.path : ("HKEY_USERS\\*Classes\\*\\InprocServer32\\",
-"HKEY_USERS\\*Classes\\*\\LocalServer32\\",
-"HKEY_USERS\\*Classes\\*\\DelegateExecute\\",
-"HKEY_USERS\\*Classes\\*\\TreatAs\\",
-"HKEY_USERS\\*Classes\\CLSID\\*\\ScriptletURL\\") and /* not
-necessary but good for filtering privileged installations */
-user.domain != "NT AUTHORITY")
-----------------------------------
-
-Version 4 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where /* uncomment once length is stable
-length(bytes_written_string) > 0 and */ (registry.path :
-"HK*}\\InprocServer32\\" and registry.data.strings: ("scrobj.dll",
-"C:\\*\\scrobj.dll") and not registry.path :
-"*\\{06290BD*-48AA-11D2-8432-006008C3FBFC}\\*") or /* in general
-COM Registry changes on Users Hive is less noisy and worth alerting */
-(registry.path : ("HKEY_USERS\\*Classes\\*\\InprocXServer32\\",
-"HKEY_USERS\\*Classes\\*\\LocalServer32\\",
-"HKEY_USERS\\*Classes\\*\\DelegateExecute\\",
-"HKEY_USERS\\*Classes\\*\\TreatAs\\",
-"HKEY_USERS\\*Classes\\CLSID\\*\\ScriptletURL\\") and /* not
-necessary but good for filtering privileged installations */
-user.domain != "NT AUTHORITY")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Component Object Model Hijacking
+** ID: T1546.015
+** Reference URL: https://attack.mitre.org/techniques/T1546/015/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: Component Object Model Hijacking
+** ID: T1546.015
+** Reference URL: https://attack.mitre.org/techniques/T1546/015/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/compression-dll-loaded-by-unusual-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/compression-dll-loaded-by-unusual-process.asciidoc
new file mode 100644
index 0000000000..a2ee2d3fb0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/compression-dll-loaded-by-unusual-process.asciidoc
@@ -0,0 +1,78 @@
+[[compression-dll-loaded-by-unusual-process]]
+=== Compression DLL Loaded by Unusual Process
+
+Identifies the image load of a compression DLL. Adversaries will often compress and encrypt data in preparation for exfiltration.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+library where host.os.type == "windows" and event.action == "load" and
+  dll.name : ("System.IO.Compression.FileSystem.ni.dll", "System.IO.Compression.ni.dll") and
+  not 
+  (
+    (
+      process.executable : (
+        "?:\\Program Files\\*",
+        "?:\\Program Files (x86)\\*",
+        "?:\\Windows\\Microsoft.NET\\Framework*\\mscorsvw.exe",
+        "?:\\Windows\\System32\\sdiagnhost.exe",
+        "?:\\Windows\\System32\\inetsrv\\w3wp.exe",
+        "?:\\Windows\\SysWOW64\\inetsrv\\w3wp.exe",
+        "?:\\ProgramData\\Microsoft\\Windows Defender Advanced Threat Protection\\DataCollection\\*\\OpenHandleCollector.exe"
+      ) and process.code_signature.trusted == true
+    ) or
+    (
+      process.name : "NuGet.exe" and process.code_signature.trusted == true and user.id : ("S-1-5-18", "S-1-5-20")
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Archive Collected Data
+** ID: T1560
+** Reference URL: https://attack.mitre.org/techniques/T1560/
diff --git a/docs/detections/prebuilt-rules/rule-details/conhost-spawned-by-suspicious-parent-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/conhost-spawned-by-suspicious-parent-process.asciidoc
index f44786ef7f..c041903e06 100644
--- a/docs/detections/prebuilt-rules/rule-details/conhost-spawned-by-suspicious-parent-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/conhost-spawned-by-suspicious-parent-process.asciidoc
@@ -5,69 +5,70 @@ Detects when the Console Window Host (conhost.exe) process is spawned by a suspi
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.fireeye.com/blog/threat-research/2017/08/monitoring-windows-console-activity-part-one.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<conhost-spawned-by-suspicious-parent-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Defense Evasion
+* Tactic: Privilege Escalation
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Conhost Spawned By Suspicious Parent Process
+*Triage and analysis*
+
 
-The Windows Console Host, or `conhost.exe`, is both the server application for all of the Windows Console APIs as well as
-the classic Windows user interface for working with command-line applications.
 
-Attackers often rely on custom shell implementations to avoid using built-in command interpreters like `cmd.exe` and
-`PowerShell.exe` and bypass application allowlisting and security features. Attackers commonly inject these implementations into
-legitimate system processes.
+*Investigating Conhost Spawned By Suspicious Parent Process*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file
-modifications, and any spawned child processes.
+The Windows Console Host, or `conhost.exe`, is both the server application for all of the Windows Console APIs as well as the classic Windows user interface for working with command-line applications.
+
+Attackers often rely on custom shell implementations to avoid using built-in command interpreters like `cmd.exe` and `PowerShell.exe` and bypass application allowlisting and security features. Attackers commonly inject these implementations into legitimate system processes.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Inspect the host for suspicious or abnormal behavior in the alert timeframe.
 - Retrieve the parent process executable and determine if it is malicious:
@@ -80,16 +81,22 @@ modifications, and any spawned child processes.
   - Use the PowerShell `Get-FileHash` cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Related rules
+
+*Related rules*
+
 
 - Suspicious Process from Conhost - 28896382-7d4f-4d50-9b72-67091901fd26
 - Suspicious PowerShell Engine ImageLoad - 852c1f19-68e8-43a6-9dce-340771fe1be3
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
@@ -97,37 +104,43 @@ modifications, and any spawned child processes.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "conhost.exe"
-and process.parent.name : ("lsass.exe", "services.exe", "smss.exe",
-"winlogon.exe", "explorer.exe", "dllhost.exe", "rundll32.exe",
-"regsvr32.exe", "userinit.exe", "wininit.exe", "spoolsv.exe",
-"ctfmon.exe") and not (process.parent.name : "rundll32.exe" and
-process.parent.args : ("?:\\Windows\\Installer\\MSI*.tmp,zzzzInvokeMan
-agedCustomActionOutOfProc",
-"?:\\WINDOWS\\system32\\PcaSvc.dll,PcaPatchSdbTask",
-"?:\\WINDOWS\\system32\\davclnt.dll,DavSetCookie"))
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "conhost.exe" and
+  process.parent.name : ("lsass.exe", "services.exe", "smss.exe", "winlogon.exe", "explorer.exe", "dllhost.exe", "rundll32.exe",
+                         "regsvr32.exe", "userinit.exe", "wininit.exe", "spoolsv.exe", "ctfmon.exe") and
+  not (process.parent.name : "rundll32.exe" and
+       process.parent.args : ("?:\\Windows\\Installer\\MSI*.tmp,zzzzInvokeManagedCustomActionOutOfProc",
+                              "?:\\WINDOWS\\system32\\PcaSvc.dll,PcaPatchSdbTask",
+                              "?:\\WINDOWS\\system32\\davclnt.dll,DavSetCookie"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -139,51 +152,19 @@ agedCustomActionOutOfProc",
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[conhost-spawned-by-suspicious-parent-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "conhost.exe" and process.parent.name :
-("svchost.exe", "lsass.exe", "services.exe", "smss.exe",
-"winlogon.exe", "explorer.exe",
-"dllhost.exe", "rundll32.exe", "regsvr32.exe", "userinit.exe",
-"wininit.exe", "spoolsv.exe", "wermgr.exe",
-"csrss.exe", "ctfmon.exe")
-----------------------------------
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:conhost.exe and process.parent.name:(svchost.exe or
-lsass.exe or services.exe or smss.exe or winlogon.exe or explorer.exe
-or dllhost.exe or rundll32.exe or regsvr32.exe or userinit.exe or
-wininit.exe or spoolsv.exe or wermgr.exe or csrss.exe or ctfmon.exe)
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
diff --git a/docs/detections/prebuilt-rules/rule-details/connection-to-commonly-abused-free-ssl-certificate-providers.asciidoc b/docs/detections/prebuilt-rules/rule-details/connection-to-commonly-abused-free-ssl-certificate-providers.asciidoc
index 2784d42a73..200b3b1b65 100644
--- a/docs/detections/prebuilt-rules/rule-details/connection-to-commonly-abused-free-ssl-certificate-providers.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/connection-to-commonly-abused-free-ssl-certificate-providers.asciidoc
@@ -5,71 +5,77 @@ Identifies unusual processes connecting to domains using known free SSL certific
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
+*Tags*: 
 
-*Version*: 100 (<<connection-to-commonly-abused-free-ssl-certificate-providers-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-network where network.protocol == "dns" and /* Add new free SSL
-certificate provider domains here */ dns.question.name :
-("*letsencrypt.org", "*.sslforfree.com", "*.zerossl.com",
-"*.freessl.org") and /* Native Windows process paths that are
-unlikely to have network connections to domains secured using free SSL
-certificates */ process.executable :
-("C:\\Windows\\System32\\*.exe",
-"C:\\Windows\\System\\*.exe",
-"C:\\Windows\\SysWOW64\\*.exe",
-"C:\\Windows\\Microsoft.NET\\Framework*\\*.exe",
-"C:\\Windows\\explorer.exe",
-"C:\\Windows\\notepad.exe") and /* Insert noisy false positives
-here */ not process.name : ("svchost.exe", "MicrosoftEdge*.exe",
-"msedge.exe")
+[source, js]
 ----------------------------------
+network where host.os.type == "windows" and network.protocol == "dns" and
+  /* Add new free SSL certificate provider domains here */
+  dns.question.name : ("*letsencrypt.org", "*.sslforfree.com", "*.zerossl.com", "*.freessl.org") and
+
+  /* Native Windows process paths that are unlikely to have network connections to domains secured using free SSL certificates */
+  process.executable : ("C:\\Windows\\System32\\*.exe",
+                        "C:\\Windows\\System\\*.exe",
+	                  "C:\\Windows\\SysWOW64\\*.exe",
+		          "C:\\Windows\\Microsoft.NET\\Framework*\\*.exe",
+		          "C:\\Windows\\explorer.exe",
+		          "C:\\Windows\\notepad.exe") and
+
+  /* Insert noisy false positives here */
+  not process.name : ("svchost.exe", "MicrosoftEdge*.exe", "msedge.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,40 +87,3 @@ here */ not process.name : ("svchost.exe", "MicrosoftEdge*.exe",
 ** Name: Encrypted Channel
 ** ID: T1573
 ** Reference URL: https://attack.mitre.org/techniques/T1573/
-
-[[connection-to-commonly-abused-free-ssl-certificate-providers-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network where network.protocol == "dns" and /* Add new free SSL
-certificate provider domains here */ dns.question.name :
-("*letsencrypt.org", "*.sslforfree.com", "*.zerossl.com",
-"*.freessl.org") and /* Native Windows process paths that are
-unlikely to have network connections to domains secured using free SSL
-certificates */ process.executable :
-("C:\\Windows\\System32\\*.exe",
-"C:\\Windows\\System\\*.exe",
-"C:\\Windows\\SysWOW64\\*.exe",
-"C:\\Windows\\Microsoft.NET\\Framework*\\*.exe",
-"C:\\Windows\\explorer.exe",
-"C:\\Windows\\notepad.exe") and /* Insert noisy false positives
-here */ not process.name : ("svchost.exe", "MicrosoftEdge*.exe",
-"msedge.exe")
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/connection-to-commonly-abused-web-services.asciidoc b/docs/detections/prebuilt-rules/rule-details/connection-to-commonly-abused-web-services.asciidoc
index e58772d4f9..850e99d676 100644
--- a/docs/detections/prebuilt-rules/rule-details/connection-to-commonly-abused-web-services.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/connection-to-commonly-abused-web-services.asciidoc
@@ -5,88 +5,93 @@ Adversaries may implement command and control (C2) communications that use commo
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.network-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<connection-to-commonly-abused-web-services-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 113
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Connection to Commonly Abused Web Services
+*Triage and analysis*
+
+
+
+*Investigating Connection to Commonly Abused Web Services*
 
-Adversaries may use an existing, legitimate external Web service as a means for relaying data to/from a compromised
-system. Popular websites and social media acting as a mechanism for C2 may give a significant amount of cover due to the
-likelihood that hosts within a network are already communicating with them prior to a compromise.
 
-This rule looks for processes outside known legitimate program locations communicating with a list of services that can
-be abused for exfiltration or command and control.
+Adversaries may use an existing, legitimate external Web service as a means for relaying data to/from a compromised system. Popular websites and social media acting as a mechanism for C2 may give a significant amount of cover due to the likelihood that hosts within a network are already communicating with them prior to a compromise.
+
+This rule looks for processes outside known legitimate program locations communicating with a list of services that can be abused for exfiltration or command and control.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/interactive-investigation-guides.html[Investigate Markdown Plugin] introduced in Elastic Stack version 8.8.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
+  - !{investigate{"label":"Alerts associated with the user in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"user.id","queryType":"phrase","value":"{{user.id}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
+  - !{investigate{"label":"Alerts associated with the host in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"host.name","queryType":"phrase","value":"{{host.name}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
 - Verify whether the digital signature exists in the executable.
 - Identify the operation type (upload, download, tunneling, etc.).
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+        - !{investigate{"label":"Investigate the Subject Process Network Events","providers":[[{"excluded":false,"field":"process.entity_id","queryType":"phrase","value":"{{process.entity_id}}","valueType":"string"},{"excluded":false,"field":"event.category","queryType":"phrase","value":"network","valueType":"string"}]]}}
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- This rule has a high chance to produce false positives because it detects communication with legitimate services. Noisy false positives can be added as exceptions.
 
-- This rule has a high chance to produce false positives because it detects communication with legitimate services. Noisy
-false positives can be added as exceptions.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -94,55 +99,167 @@ false positives can be added as exceptions.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-network where network.protocol == "dns" and process.name != null
-and user.id not in ("S-1-5-18", "S-1-5-19", "S-1-5-20") and /* Add
-new WebSvc domains here */ dns.question.name : (
-"raw.githubusercontent.*", "*.pastebin.*",
-"*drive.google.*", "*docs.live.*",
-"*api.dropboxapi.*", "*dropboxusercontent.*",
-"*onedrive.*", "*4shared.*", "*.file.io",
-"*filebin.net", "*slack-files.com", "*ghostbin.*",
-"*ngrok.*", "*portmap.*", "*serveo.net",
-"*localtunnel.me", "*pagekite.me", "*localxpose.io",
-"*notabug.org", "rawcdn.githack.*",
-"paste.nrecom.net", "zerobin.net", "controlc.com",
-"requestbin.net", "cdn.discordapp.com",
-"discordapp.com", "discord.com", "script.google.com",
-"script.googleusercontent.com" ) and /* Insert noisy false
-positives here */ not process.executable : (
-"?:\\Program Files\\*.exe", "?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\WWAHost.exe",
-"?:\\Windows\\System32\\smartscreen.exe",
-"?:\\Windows\\System32\\MicrosoftEdgeCP.exe",
-"?:\\ProgramData\\Microsoft\\Windows
-Defender\\Platform\\*\\MsMpEng.exe", "?:\\Users\\*\\AppData\\Loc
-al\\Google\\Chrome\\Application\\chrome.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Fiddler\\Fiddler.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe",
-"?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\OneDrive.exe",
-"?:\\Windows\\system32\\mobsync.exe",
-"?:\\Windows\\SysWOW64\\mobsync.exe",
-"?:\\Users\\*\\AppData\\Local\\Discord\\app-*\\Discord.exe" )
+[source, js]
 ----------------------------------
+network where host.os.type == "windows" and network.protocol == "dns" and
+    process.name != null and user.id not in ("S-1-5-18", "S-1-5-19", "S-1-5-20") and
+    /* Add new WebSvc domains here */
+    dns.question.name :
+       (
+        "raw.githubusercontent.*",
+        "pastebin.*",
+        "paste4btc.com",
+        "paste.ee",
+        "ghostbin.com",
+        "drive.google.com",
+        "?.docs.live.net",
+        "api.dropboxapi.*",
+        "content.dropboxapi.*",
+        "dl.dropboxusercontent.*",
+        "api.onedrive.com",
+        "*.onedrive.org",
+        "onedrive.live.com",
+        "filebin.net",
+        "*.ngrok.io",
+        "ngrok.com",
+        "*.portmap.*",
+        "*serveo.net",
+        "*localtunnel.me",
+        "*pagekite.me",
+        "*localxpose.io",
+        "*notabug.org",
+        "rawcdn.githack.*",
+        "paste.nrecom.net",
+        "zerobin.net",
+        "controlc.com",
+        "requestbin.net",
+        "slack.com",
+        "api.slack.com",
+        "slack-redir.net",
+        "slack-files.com",
+        "cdn.discordapp.com",
+        "discordapp.com",
+        "discord.com",
+        "apis.azureedge.net",
+        "cdn.sql.gg",
+        "?.top4top.io",
+        "top4top.io",
+        "www.uplooder.net",
+        "*.cdnmegafiles.com",
+        "transfer.sh",
+        "gofile.io",
+        "updates.peer2profit.com",
+        "api.telegram.org",
+        "t.me",
+        "meacz.gq",
+        "rwrd.org",
+        "*.publicvm.com",
+        "*.blogspot.com",
+        "api.mylnikov.org",
+        "file.io",
+        "stackoverflow.com",
+        "*files.1drv.com",
+        "api.anonfile.com",
+        "*hosting-profi.de",
+        "ipbase.com",
+        "ipfs.io",
+        "*up.freeo*.space",
+        "api.mylnikov.org",
+        "script.google.com",
+        "script.googleusercontent.com",
+        "api.notion.com",
+        "graph.microsoft.com",
+        "*.sharepoint.com",
+        "mbasic.facebook.com",
+        "login.live.com",
+        "api.gofile.io",
+        "api.anonfiles.com",
+        "api.notion.com",
+        "api.trello.com",
+        "gist.githubusercontent.com",
+        "files.pythonhosted.org",
+        "g.live.com",
+        "*.zulipchat.com",
+        "webhook.site",
+        "run.mocky.io",
+        "mockbin.org") and
+        
+    /* Insert noisy false positives here */
+    not (
+      (
+        process.executable : (
+          "?:\\Program Files\\*.exe",
+          "?:\\Program Files (x86)\\*.exe",
+          "?:\\Windows\\System32\\WWAHost.exe",
+          "?:\\Windows\\System32\\smartscreen.exe",
+          "?:\\Windows\\System32\\MicrosoftEdgeCP.exe",
+          "?:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\*\\MsMpEng.exe",
+          "?:\\Users\\*\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe",
+          "?:\\Users\\*\\AppData\\Local\\BraveSoftware\\*\\Application\\brave.exe",
+          "?:\\Users\\*\\AppData\\Local\\Vivaldi\\Application\\vivaldi.exe",
+          "?:\\Users\\*\\AppData\\Local\\Programs\\Opera*\\opera.exe",
+          "?:\\Users\\*\\AppData\\Local\\Programs\\Fiddler\\Fiddler.exe",
+          "?:\\Users\\*\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe",
+          "?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\OneDrive.exe",
+          "?:\\Windows\\system32\\mobsync.exe",
+          "?:\\Windows\\SysWOW64\\mobsync.exe"
+        )
+      ) or
+    
+      /* Discord App */
+      (process.name : "Discord.exe" and (process.code_signature.subject_name : "Discord Inc." and
+       process.code_signature.trusted == true) and dns.question.name : ("discord.com", "cdn.discordapp.com", "discordapp.com")
+      ) or 
+
+      /* MS Sharepoint */
+      (process.name : "Microsoft.SharePoint.exe" and (process.code_signature.subject_name : "Microsoft Corporation" and
+       process.code_signature.trusted == true) and dns.question.name : "onedrive.live.com"
+      ) or 
+
+      /* Firefox */
+      (process.name : "firefox.exe" and (process.code_signature.subject_name : "Mozilla Corporation" and
+       process.code_signature.trusted == true)
+      ) or 
+
+      /* Dropbox */
+      (process.name : "Dropbox.exe" and (process.code_signature.subject_name : "Dropbox, Inc" and
+       process.code_signature.trusted == true) and dns.question.name : ("api.dropboxapi.com", "*.dropboxusercontent.com")
+      ) or 
+
+      /* Obsidian - Plugins are stored on raw.githubusercontent.com */
+      (process.name : "Obsidian.exe" and (process.code_signature.subject_name : "Dynalist Inc" and
+       process.code_signature.trusted == true) and dns.question.name : "raw.githubusercontent.com"
+      ) or 
+
+      /* WebExperienceHostApp */
+      (process.name : "WebExperienceHostApp.exe" and (process.code_signature.subject_name : "Microsoft Windows" and
+       process.code_signature.trusted == true) and dns.question.name : ("onedrive.live.com", "skyapi.onedrive.live.com")
+      ) or
+
+      (process.code_signature.subject_name : "Microsoft *" and process.code_signature.trusted == true and
+       dns.question.name : ("*.sharepoint.com", "graph.microsoft.com", "g.live.com", "login.live.com", "login.live.com")) or
+
+      (process.code_signature.trusted == true and
+       process.code_signature.subject_name :
+                             ("Johannes Schindelin",
+                              "Redis Inc.",
+                              "Slack Technologies, LLC",
+                              "Cisco Systems, Inc.",
+                              "Dropbox, Inc",
+                              "Amazon.com Services LLC"))
+    ) 
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -154,8 +271,14 @@ al\\Google\\Chrome\\Application\\chrome.exe",
 ** Name: Web Service
 ** ID: T1102
 ** Reference URL: https://attack.mitre.org/techniques/T1102/
-
-
+* Technique:
+** Name: Dynamic Resolution
+** ID: T1568
+** Reference URL: https://attack.mitre.org/techniques/T1568/
+* Sub-technique:
+** Name: Domain Generation Algorithms
+** ID: T1568.002
+** Reference URL: https://attack.mitre.org/techniques/T1568/002/
 * Tactic:
 ** Name: Exfiltration
 ** ID: TA0010
@@ -164,183 +287,11 @@ al\\Google\\Chrome\\Application\\chrome.exe",
 ** Name: Exfiltration Over Web Service
 ** ID: T1567
 ** Reference URL: https://attack.mitre.org/techniques/T1567/
-
-[[connection-to-commonly-abused-web-services-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network where network.protocol == "dns" and process.name != null
-and user.id not in ("S-1-5-18", "S-1-5-19", "S-1-5-20") and /* Add
-new WebSvc domains here */ dns.question.name : (
-"raw.githubusercontent.*", "*.pastebin.*",
-"*drive.google.*", "*docs.live.*",
-"*api.dropboxapi.*", "*dropboxusercontent.*",
-"*onedrive.*", "*4shared.*", "*.file.io",
-"*filebin.net", "*slack-files.com", "*ghostbin.*",
-"*ngrok.*", "*portmap.*", "*serveo.net",
-"*localtunnel.me", "*pagekite.me", "*localxpose.io",
-"*notabug.org", "rawcdn.githack.*",
-"paste.nrecom.net", "zerobin.net", "controlc.com",
-"requestbin.net", "cdn.discordapp.com",
-"discordapp.com", "discord.com" ) and /* Insert noisy
-false positives here */ not process.executable : (
-"?:\\Program Files\\*.exe", "?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\WWAHost.exe",
-"?:\\Windows\\System32\\smartscreen.exe",
-"?:\\Windows\\System32\\MicrosoftEdgeCP.exe",
-"?:\\ProgramData\\Microsoft\\Windows
-Defender\\Platform\\*\\MsMpEng.exe", "?:\\Users\\*\\AppData\\Loc
-al\\Google\\Chrome\\Application\\chrome.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Fiddler\\Fiddler.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe",
-"?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\OneDrive.exe",
-"?:\\Windows\\system32\\mobsync.exe",
-"?:\\Windows\\SysWOW64\\mobsync.exe",
-"?:\\Users\\*\\AppData\\Local\\Discord\\app-*\\Discord.exe" )
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 10 (8.4.0 release)::
-* Formatting only
-
-Version 9 (8.3.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network where network.protocol == "dns" and process.name != null
-and user.id not in ("S-1-5-18", "S-1-5-19", "S-1-5-20") and /* Add
-new WebSvc domains here */ dns.question.name : (
-"raw.githubusercontent.*", "*.pastebin.*",
-"*drive.google.*", "*docs.live.*",
-"*api.dropboxapi.*", "*dropboxusercontent.*",
-"*onedrive.*", "*4shared.*", "*.file.io",
-"*filebin.net", "*slack-files.com", "*ghostbin.*",
-"*ngrok.*", "*portmap.*", "*serveo.net",
-"*localtunnel.me", "*pagekite.me", "*localxpose.io",
-"*notabug.org", "rawcdn.githack.*",
-"paste.nrecom.net", "zerobin.net", "controlc.com",
-"requestbin.net", "cdn.discordapp.com",
-"discordapp.com", "discord.com" ) and /* Insert noisy
-false positives here */ not process.executable : (
-"?:\\Program Files\\*.exe", "?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\WWAHost.exe",
-"?:\\Windows\\System32\\smartscreen.exe",
-"?:\\Windows\\System32\\MicrosoftEdgeCP.exe",
-"?:\\ProgramData\\Microsoft\\Windows
-Defender\\Platform\\*\\MsMpEng.exe", "?:\\Users\\*\\AppData\\Loc
-al\\Google\\Chrome\\Application\\chrome.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Fiddler\\Fiddler.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe",
-"?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\OneDrive.exe",
-"?:\\Windows\\system32\\mobsync.exe",
-"?:\\Windows\\SysWOW64\\mobsync.exe",
-"?:\\Users\\*\\AppData\\Local\\Discord\\-*\\Discord.exe" )
-----------------------------------
-
-Version 8 (8.2.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network where network.protocol == "dns" and process.name != null
-and user.id not in ("S-1-5-18", "S-1-5-19", "S-1-5-20") and /* Add
-new WebSvc domains here */ dns.question.name : (
-"raw.githubusercontent.*", "*.pastebin.*",
-"*drive.google.*", "*docs.live.*",
-"*api.dropboxapi.*", "*dropboxusercontent.*",
-"*onedrive.*", "*4shared.*", "*.file.io",
-"*filebin.net", "*slack-files.com", "*ghostbin.*",
-"*ngrok.*", "*portmap.*", "*serveo.net",
-"*localtunnel.me", "*pagekite.me", "*localxpose.io",
-"*notabug.org", "rawcdn.githack.*",
-"paste.nrecom.net", "zerobin.net", "controlc.com",
-"requestbin.net" ) and /* Insert noisy false positives here */
-not process.executable : ( "?:\\Program Files\\*.exe",
-"?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\WWAHost.exe",
-"?:\\Windows\\System32\\smartscreen.exe",
-"?:\\Windows\\System32\\MicrosoftEdgeCP.exe",
-"?:\\ProgramData\\Microsoft\\Windows
-Defender\\Platform\\*\\MsMpEng.exe", "?:\\Users\\*\\AppData\\Loc
-al\\Google\\Chrome\\Application\\chrome.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Fiddler\\Fiddler.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe",
-"?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\OneDrive.exe",
-"?:\\Windows\\system32\\mobsync.exe",
-"?:\\Windows\\SysWOW64\\mobsync.exe" )
-----------------------------------
-
-Version 5 (7.16.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network where network.protocol == "dns" and /* Add new WebSvc
-domains here */ dns.question.name : (
-"*.githubusercontent.*", "*.pastebin.*",
-"*drive.google.*", "*docs.live.*",
-"*api.dropboxapi.*", "*dropboxusercontent.*",
-"*onedrive.*", "*4shared.*", "*.file.io",
-"*filebin.net", "*slack-files.com", "*ghostbin.*",
-"*ngrok.*", "*portmap.*", "*serveo.net",
-"*localtunnel.me", "*pagekite.me", "*localxpose.io",
-"*notabug.org" ) and /* Insert noisy false positives here */
-not process.name : ( "MicrosoftEdgeCP.exe",
-"MicrosoftEdge.exe", "iexplore.exe", "chrome.exe",
-"msedge.exe", "opera.exe", "firefox.exe",
-"Dropbox.exe", "slack.exe", "svchost.exe",
-"thunderbird.exe", "outlook.exe", "OneDrive.exe" )
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network where network.protocol == "dns" and /* Add new
-WebSvc domains here */ wildcard(dns.question.name,
-"*.githubusercontent.*",
-"*.pastebin.*",
-"*drive.google.*",
-"*docs.live.*",
-"*api.dropboxapi.*",
-"*dropboxusercontent.*",
-"*onedrive.*", "*4shared.*",
-"*.file.io", "*filebin.net",
-"*slack-files.com",
-"*ghostbin.*", "*ngrok.*",
-"*portmap.*", "*serveo.net",
-"*localtunnel.me",
-"*pagekite.me",
-"*localxpose.io",
-"*notabug.org" ) and
-/* Insert noisy false positives here */ not process.name
-in ("MicrosoftEdgeCP.exe",
-"MicrosoftEdge.exe",
-"iexplore.exe", "chrome.exe",
-"msedge.exe", "opera.exe",
-"firefox.exe", "Dropbox.exe",
-"slack.exe", "svchost.exe",
-"thunderbird.exe", "outlook.exe",
-"OneDrive.exe")
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Exfiltration to Code Repository
+** ID: T1567.001
+** Reference URL: https://attack.mitre.org/techniques/T1567/001/
+* Sub-technique:
+** Name: Exfiltration to Cloud Storage
+** ID: T1567.002
+** Reference URL: https://attack.mitre.org/techniques/T1567/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/connection-to-external-network-via-telnet.asciidoc b/docs/detections/prebuilt-rules/rule-details/connection-to-external-network-via-telnet.asciidoc
index 1c27e6bb1c..4e65b0fcbb 100644
--- a/docs/detections/prebuilt-rules/rule-details/connection-to-external-network-via-telnet.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/connection-to-external-network-via-telnet.asciidoc
@@ -5,122 +5,119 @@ Telnet provides a command line interface for communication with a remote device
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Lateral Movement
 
-*Version*: 100 (<<connection-to-external-network-via-telnet-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.8.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
 
-Telnet can be used for both benign or malicious purposes. Telnet is included by default in some Linux distributions, so its presence is not inherently suspicious. The use of Telnet to manage devices remotely has declined in recent years in favor of more secure protocols such as SSH. Telnet usage by non-automated tools or frameworks may be suspicious.
 
-==== Rule query
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where process.name ==
-"telnet" and event.type == "start"] [network where process.name ==
-"telnet" and not cidrmatch(destination.ip, "10.0.0.0/8",
-"127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
-"192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32",
-"192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24",
-"192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
-"192.175.48.0/24", "198.18.0.0/15",
-"198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
-"FE80::/10", "FF00::/8")]
-----------------------------------
+*Elastic Defend Integration Setup*
 
-==== Threat mapping
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Lateral Movement
-** ID: TA0008
-** Reference URL: https://attack.mitre.org/tactics/TA0008/
-* Technique:
-** Name: Remote Services
-** ID: T1021
-** Reference URL: https://attack.mitre.org/techniques/T1021/
+*Prerequisite Requirements:*
 
-[[connection-to-external-network-via-telnet-history]]
-==== Rule version history
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 7 (8.4.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
 
-Version 6 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where process.name ==
-"telnet" and event.type == "start"] [network where process.name ==
-"telnet" and not cidrmatch(destination.ip, "127.0.0.0/8",
-"10.0.0.0/8", "172.16.0.0/12",
-"192.168.0.0/16", "FE80::/10", "::1/128")]
-----------------------------------
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Version 5 (7.12.0 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:(connection or start) and
-process.name:telnet and not destination.ip:(127.0.0.0/8 or 10.0.0.0/8
-or 172.16.0.0/12 or 192.168.0.0/16 or "FE80::/10" or "::1/128")
-----------------------------------
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
 
-Version 3 (7.9.1 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:("connected-to" or "network_flow") and
-process.name:telnet and not destination.ip:(127.0.0.0/8 or 10.0.0.0/8
-or 172.16.0.0/12 or 192.168.0.0/16 or "FE80::/10" or "::1/128")
+sequence by process.entity_id
+  [process where host.os.type == "linux" and process.name == "telnet" and event.type == "start"]
+  [network where host.os.type == "linux" and process.name == "telnet" and not cidrmatch(
+     destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.0.0.0/29",
+     "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
+     "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
+     "192.175.48.0/24", "198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
+     "FF00::/8"
+    )
+  ]
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
diff --git a/docs/detections/prebuilt-rules/rule-details/connection-to-internal-network-via-telnet.asciidoc b/docs/detections/prebuilt-rules/rule-details/connection-to-internal-network-via-telnet.asciidoc
index a914137256..3a5179d833 100644
--- a/docs/detections/prebuilt-rules/rule-details/connection-to-internal-network-via-telnet.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/connection-to-internal-network-via-telnet.asciidoc
@@ -5,122 +5,119 @@ Telnet provides a command line interface for communication with a remote device
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Lateral Movement
 
-*Version*: 100 (<<connection-to-internal-network-via-telnet-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.8.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
 
-Telnet can be used for both benign or malicious purposes. Telnet is included by default in some Linux distributions, so its presence is not inherently suspicious. The use of Telnet to manage devices remotely has declined in recent years in favor of more secure protocols such as SSH. Telnet usage by non-automated tools or frameworks may be suspicious.
 
-==== Rule query
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where process.name ==
-"telnet" and event.type == "start"] [network where process.name ==
-"telnet" and cidrmatch(destination.ip, "10.0.0.0/8",
-"127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
-"192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32",
-"192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24",
-"192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
-"192.175.48.0/24", "198.18.0.0/15",
-"198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
-"FE80::/10", "FF00::/8")]
-----------------------------------
+*Elastic Defend Integration Setup*
 
-==== Threat mapping
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Lateral Movement
-** ID: TA0008
-** Reference URL: https://attack.mitre.org/tactics/TA0008/
-* Technique:
-** Name: Remote Services
-** ID: T1021
-** Reference URL: https://attack.mitre.org/techniques/T1021/
+*Prerequisite Requirements:*
 
-[[connection-to-internal-network-via-telnet-history]]
-==== Rule version history
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 7 (8.4.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
 
-Version 6 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where process.name ==
-"telnet" and event.type == "start"] [network where process.name ==
-"telnet" and cidrmatch(destination.ip, "10.0.0.0/8",
-"172.16.0.0/12", "192.168.0.0/16", "FE80::/10") and not
-cidrmatch(destination.ip, "127.0.0.0/8", "::1/128")]
-----------------------------------
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Version 5 (7.12.0 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:(connection or start) and
-process.name:telnet and destination.ip:((10.0.0.0/8 or 172.16.0.0/12
-or 192.168.0.0/16 or "FE80::/10") and not (127.0.0.0/8 or "::1/128"))
-----------------------------------
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
 
-Version 3 (7.9.1 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:("connected-to" or "network_flow") and
-process.name:telnet and destination.ip:((10.0.0.0/8 or 172.16.0.0/12
-or 192.168.0.0/16 or "FE80::/10") and not (127.0.0.0/8 or "::1/128"))
+sequence by process.entity_id
+  [process where host.os.type == "linux" and process.name == "telnet" and event.type == "start"]
+  [network where host.os.type == "linux" and process.name == "telnet" and cidrmatch(
+     destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.0.0.0/29",
+     "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
+     "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
+     "192.175.48.0/24", "198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
+     "FF00::/8"
+    )
+  ]
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
diff --git a/docs/detections/prebuilt-rules/rule-details/container-management-utility-run-inside-a-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/container-management-utility-run-inside-a-container.asciidoc
new file mode 100644
index 0000000000..d0120a87c2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/container-management-utility-run-inside-a-container.asciidoc
@@ -0,0 +1,60 @@
+[[container-management-utility-run-inside-a-container]]
+=== Container Management Utility Run Inside A Container
+
+This rule detects when a container management binary is run from inside a container. These binaries are critical components of many containerized environments, and their presence and execution in unauthorized containers could indicate compromise or a misconfiguration.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic Licence v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where container.id: "*" and event.type== "start" 
+  and process.name: ("dockerd", "docker", "kubelet", "kube-proxy", "kubectl", "containerd", "runc", "systemd", "crictl")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Container Administration Command
+** ID: T1609
+** Reference URL: https://attack.mitre.org/techniques/T1609/
diff --git a/docs/detections/prebuilt-rules/rule-details/container-workload-protection.asciidoc b/docs/detections/prebuilt-rules/rule-details/container-workload-protection.asciidoc
new file mode 100644
index 0000000000..3c5815c403
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/container-workload-protection.asciidoc
@@ -0,0 +1,60 @@
+[[container-workload-protection]]
+=== Container Workload Protection
+
+Generates a detection alert each time a 'Container Workload Protection' alert is received. Enabling this rule allows you to immediately begin triaging and investigating these alerts.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-cloud_defend.alerts-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-10m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 10000
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:cloud_defend
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/control-panel-process-with-unusual-arguments.asciidoc b/docs/detections/prebuilt-rules/rule-details/control-panel-process-with-unusual-arguments.asciidoc
index 63e16f1482..c90b391b6e 100644
--- a/docs/detections/prebuilt-rules/rule-details/control-panel-process-with-unusual-arguments.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/control-panel-process-with-unusual-arguments.asciidoc
@@ -5,71 +5,83 @@ Identifies unusual instances of Control Panel with suspicious keywords or paths
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.joesandbox.com/analysis/476188/1/html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
-
-*Version*: 102 (<<control-panel-process-with-unusual-arguments-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.executable :
-("?:\\Windows\\SysWOW64\\control.exe",
-"?:\\Windows\\System32\\control.exe") and process.command_line :
-("*.jpg*", "*.png*", "*.gif*",
-"*.bmp*", "*.jpeg*", "*.TIFF*",
-"*.inf*", "*.cpl:*/*", "*../../..*",
-"*/AppData/Local/*", "*:\\Users\\Public\\*",
-"*\\AppData\\Local\\*")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.executable : ("?:\\Windows\\SysWOW64\\control.exe", "?:\\Windows\\System32\\control.exe") and
+ process.command_line :
+          ("*.jpg*",
+           "*.png*",
+           "*.gif*",
+           "*.bmp*",
+           "*.jpeg*",
+           "*.TIFF*",
+           "*.inf*",
+           "*.cpl:*/*",
+           "*../../..*",
+           "*/AppData/Local/*",
+           "*:\\Users\\Public\\*",
+           "*\\AppData\\Local\\*")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,46 +93,7 @@ process where event.type == "start" and process.executable :
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[control-panel-process-with-unusual-arguments-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.executable : ("?:\\Windows\\SysWOW64\\control.exe",
-"?:\\Windows\\System32\\control.exe") and process.command_line :
-("*.jpg*", "*.png*", "*.gif*",
-"*.bmp*", "*.jpeg*", "*.TIFF*",
-"*.inf*", "*.cpl:*/*", "*../../..*",
-"*/AppData/Local/*", "*:\\Users\\Public\\*",
-"*\\AppData\\Local\\*")
-----------------------------------
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.executable : ("?:\\Windows\\SysWOW64\\control.exe",
-"?:\\Windows\\System32\\control.exe") and process.command_line :
-("*.jpg*", "*.png*", "*.gif*",
-"*.bmp*", "*.jpeg*", "*.TIFF*",
-"*.inf*", "*.dat*", "*.cpl:*/*",
-"*../../..*", "*/AppData/Local/*",
-"*:\\Users\\Public\\*", "*\\AppData\\Local\\*")
-----------------------------------
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.0.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Control Panel
+** ID: T1218.002
+** Reference URL: https://attack.mitre.org/techniques/T1218/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/creation-of-a-dns-named-record.asciidoc b/docs/detections/prebuilt-rules/rule-details/creation-of-a-dns-named-record.asciidoc
new file mode 100644
index 0000000000..d2e2d091d2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/creation-of-a-dns-named-record.asciidoc
@@ -0,0 +1,95 @@
+[[creation-of-a-dns-named-record]]
+=== Creation of a DNS-Named Record
+
+Active Directory Integrated DNS (ADIDNS) is one of the core components of AD DS, leveraging AD's access control and replication to maintain domain consistency. It stores DNS zones as AD objects, a feature that, while robust, introduces some security issues because of the default permission (Any authenticated users) to create DNS-named records. Attackers can perform Dynamic Spoofing attacks, where they monitor LLMNR/NBT-NS requests and create DNS-named records to target systems that are requested from multiple systems. They can also create specific records to target specific services, such as wpad, for spoofing attacks.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-system.*
+* logs-windows.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.netspi.com/blog/technical/network-penetration-testing/adidns-revisited/
+* https://www.thehacker.recipes/a-d/movement/mitm-and-coerced-authentications/wpad-spoofing
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Active Directory
+* Use Case: Active Directory Monitoring
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Directory Service Changes' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Changes (Success,Failure)
+```
+
+The above policy does not cover the target object by default (we still need it to be configured to generate events), so we need to set up an AuditRule using https://github.com/OTRF/Set-AuditRule.
+
+```
+Set-AuditRule -AdObjectPath 'AD:\CN=MicrosoftDNS,DC=DomainDNSZones,DC=Domain,DC=com' -WellKnownSidType WorldSid -Rights CreateChild -InheritanceFlags Descendents -AttributeGUID e0fa1e8c-9b45-11d0-afdd-00c04fd930c9 -AuditFlags Success
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+any where host.os.type == "windows" and event.action == "Directory Service Changes" and
+    event.code == "5137" and winlog.event_data.ObjectClass == "dnsNode" and
+    not winlog.event_data.SubjectUserName : "*$"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Adversary-in-the-Middle
+** ID: T1557
+** Reference URL: https://attack.mitre.org/techniques/T1557/
diff --git a/docs/detections/prebuilt-rules/rule-details/creation-of-a-hidden-local-user-account.asciidoc b/docs/detections/prebuilt-rules/rule-details/creation-of-a-hidden-local-user-account.asciidoc
index 30e0d78e29..1bfede9d42 100644
--- a/docs/detections/prebuilt-rules/rule-details/creation-of-a-hidden-local-user-account.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/creation-of-a-hidden-local-user-account.asciidoc
@@ -5,93 +5,114 @@ Identifies the creation of a hidden local user account by appending the dollar s
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
-* https://web.archive.org/web/20230329153858/https://blog.menasec.net/2019/02/threat-hunting-6-hiding-in-plain-sights_8.html
+* http://web.archive.org/web/20230329153858/https://blog.menasec.net/2019/02/threat-hunting-6-hiding-in-plain-sights_8.html
 * https://github.com/CyberMonitor/APT_CyberCriminal_Campagin_Collections/tree/master/2020/2020.12.15.Lazarus_Campaign
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
-
-*Version*: 102 (<<creation-of-a-hidden-local-user-account-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Creation of a Hidden Local User Account
+*Triage and analysis*
+
+
+
+*Investigating Creation of a Hidden Local User Account*
+
 
-Attackers can create accounts ending with a `$` symbol to make the account hidden to user enumeration utilities and
-bypass detections that identify computer accounts by this pattern to apply filters.
+Attackers can create accounts ending with a `$` symbol to make the account hidden to user enumeration utilities and bypass detections that identify computer accounts by this pattern to apply filters.
 
 This rule uses registry events to identify the creation of local hidden accounts.
 
-#### Possible investigation steps
+
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positive (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Delete the hidden account.
 - Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.path :
-"HKLM\\SAM\\SAM\\Domains\\Account\\Users\\Names\\*$\\"
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and registry.path : (
+    "HKLM\\SAM\\SAM\\Domains\\Account\\Users\\Names\\*$\\",
+    "\\REGISTRY\\MACHINE\\SAM\\SAM\\Domains\\Account\\Users\\Names\\*$\\"
+)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -103,25 +124,7 @@ registry where registry.path :
 ** Name: Create Account
 ** ID: T1136
 ** Reference URL: https://attack.mitre.org/techniques/T1136/
-
-[[creation-of-a-hidden-local-user-account-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Local Account
+** ID: T1136.001
+** Reference URL: https://attack.mitre.org/techniques/T1136/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-files-and-directories-via-commandline.asciidoc b/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-files-and-directories-via-commandline.asciidoc
index b5d713561f..a2baa22334 100644
--- a/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-files-and-directories-via-commandline.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-files-and-directories-via-commandline.asciidoc
@@ -5,64 +5,108 @@ Users can mark specific files as hidden simply by putting a "." as the first cha
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 33
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<creation-of-hidden-files-and-directories-via-commandline-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Certain tools may create hidden temporary files or directories upon installation or as part of their normal behavior. These events can be filtered by the process arguments, username, or process name values.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Custom Ingest Pipeline*
+
+For versions <8.2, you need to add a custom ingest pipeline to populate `event.ingested` with @timestamp for non-elastic-agent indexes, like auditbeats/filebeat/winlogbeat etc. For more details to add a custom ingest pipeline refer to the https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html[guide].
 
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
-process where event.type in ("start", "process_started") and
+process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
 process.working_directory in ("/tmp", "/var/tmp", "/dev/shm") and
-process.args regex~ """\.[a-z0-9_\-][a-z0-9_\-\.]{1,254}""" and not
-process.name in ("ls", "find", "grep")
-----------------------------------
+process.args regex~ """\.[a-z0-9_\-][a-z0-9_\-\.]{1,254}""" and
+not process.name in ("ls", "find", "grep", "git", "jq", "basename")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,58 +118,11 @@ process.name in ("ls", "find", "grep")
 ** Name: Hide Artifacts
 ** ID: T1564
 ** Reference URL: https://attack.mitre.org/techniques/T1564/
-
-
+* Sub-technique:
+** Name: Hidden Files and Directories
+** ID: T1564.001
+** Reference URL: https://attack.mitre.org/techniques/T1564/001/
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-[[creation-of-hidden-files-and-directories-via-commandline-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 10 (8.4.0 release)::
-* Rule name changed from: Creation of Hidden Files and Directories
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.working_directory in ("/tmp", "/var/tmp", "/dev/shm") and
-process.args regex~ """\.[a-z0-9_\-][a-z0-9_\-\.]{1,254}""" and not
-process.name in ("ls", "find")
-----------------------------------
-
-Version 8 (8.2.0 release)::
-* Formatting only
-
-Version 7 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process AND event.type:(start or process_started) AND
-process.working_directory:("/tmp" or "/var/tmp" or "/dev/shm") AND
-process.args:/\.[a-zA-Z0-9_\-][a-zA-Z0-9_\-\.]{1,254}/ AND NOT
-process.name:(ls or find)
-----------------------------------
-
-Version 6 (7.12.0 release)::
-* Formatting only
-
-Version 5 (7.11.2 release)::
-* Formatting only
-
-Version 4 (7.11.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.1 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-launch-agent-or-daemon.asciidoc b/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-launch-agent-or-daemon.asciidoc
index f156d3b8a3..c70981f0c1 100644
--- a/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-launch-agent-or-daemon.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-launch-agent-or-daemon.asciidoc
@@ -5,67 +5,95 @@ Identifies the creation of a hidden launch agent or daemon. An adversary may est
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
-* Defense Evasion
 
-*Version*: 100 (<<creation-of-hidden-launch-agent-or-daemon-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This rule requires data coming in from Elastic Defend.
 
-----------------------------------
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.path : (
-"/System/Library/LaunchAgents/.*.plist",
-"/Library/LaunchAgents/.*.plist",
-"/Users/*/Library/LaunchAgents/.*.plist",
-"/System/Library/LaunchDaemons/.*.plist",
-"/Library/LaunchDaemons/.*.plist" )
+[source, js]
 ----------------------------------
+file where host.os.type == "macos" and event.type != "deletion" and
+  file.path :
+  (
+    "/System/Library/LaunchAgents/.*.plist",
+    "/Library/LaunchAgents/.*.plist",
+    "/Users/*/Library/LaunchAgents/.*.plist",
+    "/System/Library/LaunchDaemons/.*.plist",
+    "/Library/LaunchDaemons/.*.plist"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,8 +105,10 @@ file where event.type != "deletion" and file.path : (
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-
+* Sub-technique:
+** Name: Launch Agent
+** ID: T1543.001
+** Reference URL: https://attack.mitre.org/techniques/T1543/001/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -87,26 +117,7 @@ file where event.type != "deletion" and file.path : (
 ** Name: Hide Artifacts
 ** ID: T1564
 ** Reference URL: https://attack.mitre.org/techniques/T1564/
-
-[[creation-of-hidden-launch-agent-or-daemon-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type != "deletion" and file.path : (
-"/System/Library/LaunchAgents/.*.plist",
-"/Library/LaunchAgents/.*.plist",
-"/Users/*/Library/LaunchAgents/.*.plist",
-"/System/Library/LaunchDaemons/.*.plist",
-"/Library/LaunchDaemons/.*.plist" )
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Hidden Files and Directories
+** ID: T1564.001
+** Reference URL: https://attack.mitre.org/techniques/T1564/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-login-item-via-apple-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-login-item-via-apple-script.asciidoc
index 41683d9a57..24511de289 100644
--- a/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-login-item-via-apple-script.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-login-item-via-apple-script.asciidoc
@@ -5,60 +5,86 @@ Identifies the execution of osascript to create a hidden login item. This may in
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
-* Execution
+*Tags*: 
 
-*Version*: 101 (<<creation-of-hidden-login-item-via-apple-script-history, version history>>)
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Execution
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "osascript" and process.command_line :
-"osascript*login item*hidden:true*"
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and process.name : "osascript" and
+ process.command_line : "osascript*login item*hidden:true*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,8 +96,6 @@ process.name : "osascript" and process.command_line :
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -80,8 +104,10 @@ process.name : "osascript" and process.command_line :
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-
+* Sub-technique:
+** Name: AppleScript
+** ID: T1059.002
+** Reference URL: https://attack.mitre.org/techniques/T1059/002/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -90,19 +116,3 @@ process.name : "osascript" and process.command_line :
 ** Name: Plist File Modification
 ** ID: T1647
 ** Reference URL: https://attack.mitre.org/techniques/T1647/
-
-[[creation-of-hidden-login-item-via-apple-script-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-shared-object-file.asciidoc b/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-shared-object-file.asciidoc
index 74fe91d664..78fcebc35c 100644
--- a/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-shared-object-file.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/creation-of-hidden-shared-object-file.asciidoc
@@ -5,58 +5,109 @@ Identifies the creation of a hidden shared object (.so) file. Users can mark spe
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 33
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<creation-of-hidden-shared-object-file-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Custom Ingest Pipeline*
+
+For versions <8.2, you need to add a custom ingest pipeline to populate `event.ingested` with @timestamp for non-elastic-agent indexes, like auditbeats/filebeat/winlogbeat etc. For more details to add a custom ingest pipeline refer to the https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html[guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.action : "creation" and file.extension == "so" and
-file.name : ".*.so"
+[source, js]
 ----------------------------------
+file where host.os.type == "linux" and event.type == "creation" and file.extension == "so" and file.name : ".*.so" and
+not process.name == "dockerd"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -68,16 +119,7 @@ file.name : ".*.so"
 ** Name: Hide Artifacts
 ** ID: T1564
 ** Reference URL: https://attack.mitre.org/techniques/T1564/
-
-[[creation-of-hidden-shared-object-file-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.action : "creation" and file.extension == "so" and
-file.name : ".*.so"
-----------------------------------
-
+* Sub-technique:
+** Name: Hidden Files and Directories
+** ID: T1564.001
+** Reference URL: https://attack.mitre.org/techniques/T1564/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/creation-of-kernel-module.asciidoc b/docs/detections/prebuilt-rules/rule-details/creation-of-kernel-module.asciidoc
new file mode 100644
index 0000000000..36c1cc4d9f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/creation-of-kernel-module.asciidoc
@@ -0,0 +1,69 @@
+[[creation-of-kernel-module]]
+=== Creation of Kernel Module
+
+Identifies activity related to loading kernel modules on Linux via creation of new ko files in the LKM directory.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "linux" and event.type in ("change", "creation") and file.path : "/lib/modules/*" and
+file.extension == "ko" and not process.name : (
+  "dpkg", "systemd", "falcon-sensor*", "dnf", "yum", "rpm", "cp"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Sub-technique:
+** Name: Kernel Modules and Extensions
+** ID: T1547.006
+** Reference URL: https://attack.mitre.org/techniques/T1547/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/creation-of-settingcontent-ms-files.asciidoc b/docs/detections/prebuilt-rules/rule-details/creation-of-settingcontent-ms-files.asciidoc
new file mode 100644
index 0000000000..aed6174c3b
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/creation-of-settingcontent-ms-files.asciidoc
@@ -0,0 +1,83 @@
+[[creation-of-settingcontent-ms-files]]
+=== Creation of SettingContent-ms Files
+
+Identifies the suspicious creation of SettingContents-ms files, which have been used in attacks to achieve code execution while evading defenses.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://posts.specterops.io/the-tale-of-settingcontent-ms-files-f1ea253e4d39
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and
+  file.extension : "settingcontent-ms" and
+  not file.path : (
+    "?:\\*\\AppData\\Local\\Packages\\windows.immersivecontrolpanel_*\\LocalState\\Indexed\\Settings\\*",
+    "\\Device\\HarddiskVolume*\\Windows\\WinSxS\\amd64_microsoft-windows-s..*\\*.settingcontent-ms"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: User Execution
+** ID: T1204
+** Reference URL: https://attack.mitre.org/techniques/T1204/
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-a-new-gpo-scheduled-task-or-service.asciidoc b/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-a-new-gpo-scheduled-task-or-service.asciidoc
index ab1e55ef8a..ad8b5a2d3e 100644
--- a/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-a-new-gpo-scheduled-task-or-service.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-a-new-gpo-scheduled-task-or-service.asciidoc
@@ -5,65 +5,85 @@ Detects the creation or modification of a new Group Policy based scheduled task
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 101 (<<creation-or-modification-of-a-new-gpo-scheduled-task-or-service-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.path : ("?:\\Windows\\S
-YSVOL\\domain\\Policies\\*\\MACHINE\\Preferences\\ScheduledTasks\\Sche
-duledTasks.xml", "?:\\Windows\\SYSVOL\\domain\\Policies
-\\*\\MACHINE\\Preferences\\Services\\Services.xml") and not
-process.name : "dfsrs.exe"
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and
+  file.path : ("?:\\Windows\\SYSVOL\\domain\\Policies\\*\\MACHINE\\Preferences\\ScheduledTasks\\ScheduledTasks.xml",
+               "?:\\Windows\\SYSVOL\\domain\\Policies\\*\\MACHINE\\Preferences\\Services\\Services.xml") and
+  not process.name : "dfsrs.exe"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Domain Policy Modification
+** ID: T1484
+** Reference URL: https://attack.mitre.org/techniques/T1484/
+* Sub-technique:
+** Name: Group Policy Modification
+** ID: T1484.001
+** Reference URL: https://attack.mitre.org/techniques/T1484/001/
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -72,49 +92,7 @@ process.name : "dfsrs.exe"
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[creation-or-modification-of-a-new-gpo-scheduled-task-or-service-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type != "deletion" and file.path : ("?:\\Windows\\S
-YSVOL\\domain\\Policies\\*\\MACHINE\\Preferences\\ScheduledTasks\\Sche
-duledTasks.xml", "?:\\Windows\\SYSVOL\\domain\\Policies
-\\*\\MACHINE\\Preferences\\Preferences\\Services\\Services.xml") and
-not process.name : "dfsrs.exe"
-----------------------------------
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (7.16.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and not event.type:deletion and file.path:(C\:\\Wi
-ndows\\SYSVOL\\domain\\Policies\\*\\MACHINE\\Preferences\\ScheduledTas
-ks\\ScheduledTasks.xml or C\:\\Windows\\SYSVOL\\domain\\Policies\\*\\M
-ACHINE\\Preferences\\Preferences\\Services\\Services.xml) and not
-process.name:dfsrs.exe
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-domain-backup-dpapi-private-key.asciidoc b/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-domain-backup-dpapi-private-key.asciidoc
index 6a7e638df7..737b8fa047 100644
--- a/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-domain-backup-dpapi-private-key.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-domain-backup-dpapi-private-key.asciidoc
@@ -5,68 +5,79 @@ Identifies the creation or modification of Domain Backup private keys. Adversari
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.dsinternals.com/en/retrieving-dpapi-backup-keys-from-active-directory/
 * https://posts.specterops.io/operational-guidance-for-offensive-user-dpapi-abuse-1fb7fac8b107
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Elastic Endgame
-
-*Version*: 101 (<<creation-or-modification-of-domain-backup-dpapi-private-key-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+
+*Triage and analysis*
+
 
 Domain DPAPI Backup keys are stored on domain controllers and can be dumped remotely with tools such as Mimikatz. The resulting .pvk private key can be used to decrypt ANY domain user masterkeys, which then can be used to decrypt any secrets protected by those keys.
-----------------------------------
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.name :
-("ntds_capi_*.pfx", "ntds_capi_*.pvk")
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and file.name : ("ntds_capi_*.pfx", "ntds_capi_*.pvk")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,43 +89,11 @@ file where event.type != "deletion" and file.name :
 ** Name: Unsecured Credentials
 ** ID: T1552
 ** Reference URL: https://attack.mitre.org/techniques/T1552/
-
-[[creation-or-modification-of-domain-backup-dpapi-private-key-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 10 (8.4.0 release)::
-* Formatting only
-
-Version 8 (8.3.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (7.16.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and not event.type:deletion and
-file.name:(ntds_capi_*.pfx or ntds_capi_*.pvk)
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Private Keys
+** ID: T1552.004
+** Reference URL: https://attack.mitre.org/techniques/T1552/004/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
diff --git a/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-root-certificate.asciidoc b/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-root-certificate.asciidoc
index fd7ac0af44..81dd066401 100644
--- a/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-root-certificate.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/creation-or-modification-of-root-certificate.asciidoc
@@ -5,78 +5,72 @@ Identifies the creation or modification of a local trusted root certificate in W
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://posts.specterops.io/code-signing-certificate-cloning-attacks-and-defenses-6f98657fc6ec
 * https://www.ired.team/offensive-security/persistence/t1130-install-root-certificate
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 110
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
 
-*Version*: 102 (<<creation-or-modification-of-root-certificate-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Certain applications may install root certificates for the purpose of inspecting SSL traffic.
 
-==== Investigation guide
 
+*Investigating Creation or Modification of Root Certificate*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Creation or Modification of Root Certificate
+Root certificates are the primary level of certifications that tell a browser that the communication is trusted and legitimate. This verification is based upon the identification of a certification authority. Windows adds several trusted root certificates so browsers can use them to communicate with websites.
+
+https://www.thewindowsclub.com/what-are-root-certificates-windows[Check out this post] for more details on root certificates and the involved cryptography.
 
-Root certificates are the primary level of certifications that tell a browser that the communication is trusted and
-legitimate. This verification is based upon the identification of a certification authority. Windows
-adds several trusted root certificates so browsers can use them to communicate with websites.
+This rule identifies the creation or modification of a root certificate by monitoring registry modifications. The installation of a malicious root certificate would allow an attacker the ability to masquerade malicious files as valid signed components from any entity (for example, Microsoft). It could also allow an attacker to decrypt SSL traffic.
 
-[Check out this post](https://www.thewindowsclub.com/what-are-root-certificates-windows) for more details on root certificates and the involved cryptography.
 
-This rule identifies the creation or modification of a root certificate by monitoring registry modifications. The
-installation of a malicious root certificate would allow an attacker the ability to masquerade malicious files as valid
-signed components from any entity (for example, Microsoft). It could also allow an attacker to decrypt SSL traffic.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate abnormal behaviors observed by the subject process such as network connections, other registry or file
-modifications, and any spawned child processes.
+- Investigate abnormal behaviors observed by the subject process such as network connections, other registry or file modifications, and any spawned child processes.
 - If one of the processes is suspicious, retrieve it and determine if it is malicious:
   - Use a private sandboxed malware analysis system to perform analysis.
     - Observe and collect information about the following activities:
@@ -87,12 +81,15 @@ modifications, and any spawned child processes.
   - Use the PowerShell `Get-FileHash` cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
 
-- This detection may be triggered by certain applications that install root certificates for the purpose of inspecting
-SSL traffic. Benign true positives (B-TPs) can be added as exceptions if necessary.
+*False positive analysis*
+
+
+- This detection may be triggered by certain applications that install root certificates for the purpose of inspecting SSL traffic. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -100,51 +97,68 @@ SSL traffic. Benign true positives (B-TPs) can be added as exceptions if necessa
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove the malicious certificate from the root certificate store.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-registry.path : ( "HKLM\\Software\\Microsoft\\SystemCertific
-ates\\Root\\Certificates\\*\\Blob", "HKLM\\Software\\Microsoft\\
-SystemCertificates\\AuthRoot\\Certificates\\*\\Blob", "HKLM\\Sof
-tware\\Policies\\Microsoft\\SystemCertificates\\Root\\Certificates\\*\
-\Blob", "HKLM\\Software\\Policies\\Microsoft\\SystemCertificates
-\\AuthRoot\\Certificates\\*\\Blob", "\\REGISTRY\\MACHINE\\Softwa
-re\\Microsoft\\SystemCertificates\\Root\\Certificates\\*\\Blob",
-"\\REGISTRY\\MACHINE\\Software\\Microsoft\\SystemCertificates\\AuthRoo
-t\\Certificates\\*\\Blob", "\\REGISTRY\\MACHINE\\Software\\Polic
-ies\\Microsoft\\SystemCertificates\\Root\\Certificates\\*\\Blob",
-"\\REGISTRY\\MACHINE\\Software\\Policies\\Microsoft\\SystemCertificate
-s\\AuthRoot\\Certificates\\*\\Blob" ) and not process.executable
-: ("?:\\Program Files\\*.exe",
-"?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\*.exe",
-"?:\\Windows\\SysWOW64\\*.exe",
-"?:\\Windows\\Sysmon64.exe", "?:\\Windows\\Sysmon.exe",
-"?:\\ProgramData\\Microsoft\\Windows
-Defender\\Platform\\*\\MsMpEng.exe",
-"?:\\Windows\\WinSxS\\*.exe",
-"?:\\Windows\\UUS\\amd64\\MoUsoCoreWorker.exe")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type in ("creation", "change") and
+  registry.path :
+    (
+      "HKLM\\Software\\Microsoft\\SystemCertificates\\Root\\Certificates\\*\\Blob",
+      "HKLM\\Software\\Microsoft\\SystemCertificates\\AuthRoot\\Certificates\\*\\Blob",
+      "HKLM\\Software\\Policies\\Microsoft\\SystemCertificates\\Root\\Certificates\\*\\Blob",
+      "HKLM\\Software\\Policies\\Microsoft\\SystemCertificates\\AuthRoot\\Certificates\\*\\Blob",
+      "\\REGISTRY\\MACHINE\\Software\\Microsoft\\SystemCertificates\\Root\\Certificates\\*\\Blob",
+      "\\REGISTRY\\MACHINE\\Software\\Microsoft\\SystemCertificates\\AuthRoot\\Certificates\\*\\Blob",
+      "\\REGISTRY\\MACHINE\\Software\\Policies\\Microsoft\\SystemCertificates\\Root\\Certificates\\*\\Blob",
+      "\\REGISTRY\\MACHINE\\Software\\Policies\\Microsoft\\SystemCertificates\\AuthRoot\\Certificates\\*\\Blob"
+    ) and
+  not process.executable : (
+          "?:\\ProgramData\\Lenovo\\Vantage\\Addins\\LenovoHardwareScanAddin\\*\\LdeApi.Server.exe",
+          "?:\\ProgramData\\Logishrd\\LogiOptionsPlus\\Plugins\\64\\certmgr.exe",
+          "?:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\*\\MsMpEng.exe",
+          "?:\\ProgramData\\Quest\\KACE\\modules\\clientidentifier\\clientidentifier.exe",
+          "?:\\Program Files (x86)\\*.exe",
+          "?:\\Program Files\\*.exe",
+          "?:\\Windows\\CCM\\CcmExec.exe",
+          "?:\\Windows\\ccmsetup\\cache\\ccmsetup.exe",
+          "?:\\Windows\\Cluster\\clussvc.exe",
+          "?:\\Windows\\ImmersiveControlPanel\\SystemSettings.exe",
+          "?:\\Windows\\Lenovo\\ImController\\PluginHost86\\Lenovo.Modern.ImController.PluginHost.Device.exe",
+          "?:\\Windows\\Lenovo\\ImController\\Service\\Lenovo.Modern.ImController.exe",
+          "?:\\Windows\\Sysmon.exe",
+          "?:\\Windows\\Sysmon64.exe",
+          "?:\\Windows\\System32\\*.exe",
+          "?:\\Windows\\SysWOW64\\*.exe",
+          "?:\\Windows\\UUS\\amd64\\MoUsoCoreWorker.exe",
+          "?:\\Windows\\WinSxS\\*.exe"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -156,50 +170,7 @@ Defender\\Platform\\*\\MsMpEng.exe",
 ** Name: Subvert Trust Controls
 ** ID: T1553
 ** Reference URL: https://attack.mitre.org/techniques/T1553/
-
-[[creation-or-modification-of-root-certificate-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-registry.path : ( "HKLM\\Software\\Microsoft\\SystemCertific
-ates\\Root\\Certificates\\*\\Blob", "HKLM\\Software\\Microsoft\\
-SystemCertificates\\AuthRoot\\Certificates\\*\\Blob", "HKLM\\Sof
-tware\\Policies\\Microsoft\\SystemCertificates\\Root\\Certificates\\*\
-\Blob", "HKLM\\Software\\Policies\\Microsoft\\SystemCertificates
-\\AuthRoot\\Certificates\\*\\Blob" ) and not process.executable
-: ("?:\\Program Files\\*.exe",
-"?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\*.exe",
-"?:\\Windows\\SysWOW64\\*.exe",
-"?:\\Windows\\Sysmon64.exe", "?:\\Windows\\Sysmon.exe",
-"?:\\ProgramData\\Microsoft\\Windows
-Defender\\Platform\\*\\MsMpEng.exe",
-"?:\\Windows\\WinSxS\\*.exe",
-"?:\\Windows\\UUS\\amd64\\MoUsoCoreWorker.exe")
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-registry.path : ( "HKLM\\Software\\Microsoft\\SystemCertific
-ates\\Root\\Certificates\\*\\Blob", "HKLM\\Software\\Microsoft\\
-SystemCertificates\\AuthRoot\\Certificates\\*\\Blob", "HKLM\\Sof
-tware\\Policies\\Microsoft\\SystemCertificates\\Root\\Certificates\\*\
-\Blob", "HKLM\\Software\\Policies\\Microsoft\\SystemCertificates
-\\AuthRoot\\Certificates\\*\\Blob" )
-----------------------------------
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Install Root Certificate
+** ID: T1553.004
+** Reference URL: https://attack.mitre.org/techniques/T1553/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/credential-acquisition-via-registry-hive-dumping.asciidoc b/docs/detections/prebuilt-rules/rule-details/credential-acquisition-via-registry-hive-dumping.asciidoc
index 71120b0377..1a13b17478 100644
--- a/docs/detections/prebuilt-rules/rule-details/credential-acquisition-via-registry-hive-dumping.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/credential-acquisition-via-registry-hive-dumping.asciidoc
@@ -5,114 +5,128 @@ Identifies attempts to export a registry hive which may contain credentials usin
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://medium.com/threatpunter/detecting-attempts-to-steal-passwords-from-the-registry-7512674487f8
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<credential-acquisition-via-registry-hive-dumping-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Credential Acquisition via Registry Hive Dumping
+*Triage and analysis*
+
+
+
+*Investigating Credential Acquisition via Registry Hive Dumping*
+
 
 Dumping registry hives is a common way to access credential information as some hives store credential material.
 
-For example, the SAM hive stores locally cached credentials (SAM Secrets), and the SECURITY hive stores domain cached
-credentials (LSA secrets).
+For example, the SAM hive stores locally cached credentials (SAM Secrets), and the SECURITY hive stores domain cached credentials (LSA secrets).
 
 Dumping these hives in combination with the SYSTEM hive enables the attacker to decrypt these secrets.
 
-This rule identifies the usage of `reg.exe` to dump SECURITY and/or SAM hives, which potentially indicates the
-compromise of the credentials stored in the host.
+This rule identifies the usage of `reg.exe` to dump SECURITY and/or SAM hives, which potentially indicates the compromise of the credentials stored in the host.
 
-#### Possible investigation steps
 
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Investigate if the credential material was exfiltrated or processed locally by other tools.
-- Investigate potentially compromised accounts. Analysts can do this by searching for login events (e.g., 4624) to the target
-host.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (e.g., 4624) to the target host.
+
 
-### False positive analysis
+*False positive analysis*
 
-- Administrators can export registry hives for backup purposes using command line tools like `reg.exe`. Check whether
-the user is legitamitely performing this kind of activity.
 
-### Related rules
+- Administrators can export registry hives for backup purposes using command line tools like `reg.exe`. Check whether the user is legitamitely performing this kind of activity.
+
+
+*Related rules*
+
 
 - Registry Hive File Creation via SMB - a4c7473a-5cb4-4bc1-9d06-e4a75adbc494
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Reimage the host operating system and restore compromised files to clean versions.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.pe.original_file_name
-== "reg.exe" and process.args : ("save", "export") and process.args
-: ("hklm\\sam", "hklm\\security")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ (?process.pe.original_file_name == "reg.exe" or process.name : "reg.exe") and
+ process.args : ("save", "export") and
+ process.args : ("hklm\\sam", "hklm\\security")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -124,58 +138,11 @@ process where event.type == "start" and process.pe.original_file_name
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[credential-acquisition-via-registry-hive-dumping-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.pe.original_file_name == "reg.exe" and process.args :
-("save", "export") and process.args : ("hklm\\sam", "hklm\\security")
-----------------------------------
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.pe.original_file_name == "reg.exe" and process.args :
-("save", "export") and process.args : ("hklm\\sam", "hklm\\security")
-and not process.parent.executable : "C:\\Program
-Files*\\Rapid7\\Insight
-Agent\\components\\insight_agent\\*\\ir_agent.exe"
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.pe.original_file_name == "reg.exe" and process.args :
-("save", "export") and process.args : ("hklm\\sam", "hklm\\security")
-and not process.parent.executable : "C:\\Program
-Files*\\Rapid7\\Insight
-Agent\\components\\insight_agent\\*\\ir_agent.exe"
-----------------------------------
-
+* Sub-technique:
+** Name: Security Account Manager
+** ID: T1003.002
+** Reference URL: https://attack.mitre.org/techniques/T1003/002/
+* Sub-technique:
+** Name: LSA Secrets
+** ID: T1003.004
+** Reference URL: https://attack.mitre.org/techniques/T1003/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/credential-dumping-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/credential-dumping-detected-elastic-endgame.asciidoc
index 3a44057c82..759c2fca80 100644
--- a/docs/detections/prebuilt-rules/rule-details/credential-dumping-detected-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/credential-dumping-detected-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame detected Credential Dumping. Click the Elastic Endgame icon in t
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,40 +13,52 @@ Elastic Endgame detected Credential Dumping. Click the Elastic Endgame icon in t
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
-* Threat Detection
-* Credential Access
+*Tags*: 
 
-*Version*: 100 (<<credential-dumping-detected-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:detection and (event.action:cred_theft_event or
-endgame.event_subtype_full:cred_theft_event)
+[source, js]
 ----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:cred_theft_event or endgame.event_subtype_full:cred_theft_event)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -58,34 +70,7 @@ endgame.event_subtype_full:cred_theft_event)
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[credential-dumping-detected-elastic-endgame-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Formatting only
-
-Version 6 (7.12.1 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Rule name changed from: Credential Dumping - Detected - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Credential Dumping - Detected - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Credential Dumping - Detected - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:cred_theft_event and endgame.metadata.type:detection
-----------------------------------
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/credential-dumping-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/credential-dumping-prevented-elastic-endgame.asciidoc
index 817e7dcbe0..947fad5c23 100644
--- a/docs/detections/prebuilt-rules/rule-details/credential-dumping-prevented-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/credential-dumping-prevented-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame prevented Credential Dumping. Click the Elastic Endgame icon in
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,40 +13,52 @@ Elastic Endgame prevented Credential Dumping. Click the Elastic Endgame icon in
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
-* Threat Detection
-* Credential Access
+*Tags*: 
 
-*Version*: 100 (<<credential-dumping-prevented-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:prevention and (event.action:cred_theft_event or
-endgame.event_subtype_full:cred_theft_event)
+[source, js]
 ----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:cred_theft_event or endgame.event_subtype_full:cred_theft_event)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -58,34 +70,7 @@ endgame.event_subtype_full:cred_theft_event)
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[credential-dumping-prevented-elastic-endgame-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Formatting only
-
-Version 6 (7.12.1 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Rule name changed from: Credential Dumping - Prevented - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Credential Dumping - Prevented - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Credential Dumping - Prevented - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:cred_theft_event and endgame.metadata.type:prevention
-----------------------------------
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/credential-manipulation-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/credential-manipulation-detected-elastic-endgame.asciidoc
index 7ecd795420..d7b9661798 100644
--- a/docs/detections/prebuilt-rules/rule-details/credential-manipulation-detected-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/credential-manipulation-detected-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame detected Credential Manipulation. Click the Elastic Endgame icon
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,41 +13,52 @@ Elastic Endgame detected Credential Manipulation. Click the Elastic Endgame icon
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<credential-manipulation-detected-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:detection and
-(event.action:token_manipulation_event or
-endgame.event_subtype_full:token_manipulation_event)
+[source, js]
 ----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:token_manipulation_event or endgame.event_subtype_full:token_manipulation_event)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -59,35 +70,3 @@ endgame.event_subtype_full:token_manipulation_event)
 ** Name: Access Token Manipulation
 ** ID: T1134
 ** Reference URL: https://attack.mitre.org/techniques/T1134/
-
-[[credential-manipulation-detected-elastic-endgame-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Formatting only
-
-Version 6 (7.12.1 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Rule name changed from: Credential Manipulation - Detected - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Credential Manipulation - Detected - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Credential Manipulation - Detected - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:token_manipulation_event and
-endgame.metadata.type:detection
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/credential-manipulation-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/credential-manipulation-prevented-elastic-endgame.asciidoc
index 62a8cdfb71..9845eeef5f 100644
--- a/docs/detections/prebuilt-rules/rule-details/credential-manipulation-prevented-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/credential-manipulation-prevented-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame prevented Credential Manipulation. Click the Elastic Endgame ico
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,41 +13,52 @@ Elastic Endgame prevented Credential Manipulation. Click the Elastic Endgame ico
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<credential-manipulation-prevented-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:prevention and
-(event.action:token_manipulation_event or
-endgame.event_subtype_full:token_manipulation_event)
+[source, js]
 ----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:token_manipulation_event or endgame.event_subtype_full:token_manipulation_event)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -59,35 +70,3 @@ endgame.event_subtype_full:token_manipulation_event)
 ** Name: Access Token Manipulation
 ** ID: T1134
 ** Reference URL: https://attack.mitre.org/techniques/T1134/
-
-[[credential-manipulation-prevented-elastic-endgame-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Formatting only
-
-Version 6 (7.12.1 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Rule name changed from: Credential Manipulation - Prevented - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Credential Manipulation - Prevented - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Credential Manipulation - Prevented - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:token_manipulation_event and
-endgame.metadata.type:prevention
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/cron-job-created-or-changed-by-previously-unknown-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/cron-job-created-or-changed-by-previously-unknown-process.asciidoc
new file mode 100644
index 0000000000..eb5cba29ad
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/cron-job-created-or-changed-by-previously-unknown-process.asciidoc
@@ -0,0 +1,226 @@
+[[cron-job-created-or-changed-by-previously-unknown-process]]
+=== Cron Job Created or Changed by Previously Unknown Process
+
+Linux cron jobs are scheduled tasks that can be leveraged by malicious actors for persistence, privilege escalation and command execution. By creating or modifying cron job configurations, attackers can execute malicious commands or scripts at predefined intervals, ensuring their continued presence and enabling unauthorized activities.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://pberba.github.io/security/2022/01/30/linux-threat-hunting-for-persistence-systemd-timers-cron/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 9
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Cron Job Created or Changed by Previously Unknown Process*
+
+Linux cron jobs are scheduled tasks that run at specified intervals or times, managed by the cron daemon. 
+
+By creating or modifying cron job configurations, attackers can execute malicious commands or scripts at predefined intervals, ensuring their continued presence and enabling unauthorized activities.
+
+This rule monitors the creation of previously unknown cron jobs by monitoring for file creation events in the most common cron job task location directories.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible Investigation Steps*
+
+
+- Investigate the cron job file that was created or modified.
+- Investigate whether any other files in any of the available cron job directories have been altered through OSQuery.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE (\n  path LIKE '/etc/cron.allow.d/%' OR\n  path LIKE '/etc/cron.d/%' OR\n  path LIKE '/etc/cron.hourly/%' OR\n  path LIKE '/etc/cron.daily/%' OR\n  path LIKE '/etc/cron.weekly/%' OR\n  path LIKE '/etc/cron.monthly/%'\n)\n"}}
+  - !{osquery{"label":"Osquery - Retrieve rc-local.service File Information","query":"SELECT * FROM file WHERE (\n  path = '/etc/cron.allow' OR\n  path = '/etc/cron.deny' OR\n  path = '/etc/crontab' OR\n  path = '/usr/sbin/cron' OR\n  path = '/usr/sbin/anacron'\n)\n"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE (\n  path LIKE '/etc/cron.allow.d/%' OR\n  path LIKE '/etc/cron.d/%' OR\n  path LIKE '/etc/cron.hourly/%' OR\n  path LIKE '/etc/cron.daily/%' OR\n  path LIKE '/etc/cron.weekly/%' OR\n  path LIKE '/etc/cron.monthly/%'\n)\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+    - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+    - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+
+
+*False Positive Analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator who uses cron jobs for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Related Rules*
+
+
+- Suspicious File Creation in /etc for Persistence - 1c84dd64-7e6c-4bad-ac73-a5014ee37042
+- Potential Persistence Through Run Control Detected - 0f4d35e4-925e-4959-ab24-911be207ee6f
+- Potential Persistence Through init.d Detected - 474fd20e-14cc-49c5-8160-d9ab4ba16c8b
+- New Systemd Timer Created - 7fb500fa-8e24-4bd1-9480-2a819352602c
+- New Systemd Service Created by Previously Unknown Process - 17b0a495-4d9f-414c-8ad0-92f018b8e001
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Delete the service/timer or restore its original configuration.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type : "linux" and event.action : ("change" or "file_modify_event" or "creation" or "file_create_event") and 
+file.path : (/etc/cron.allow or /etc/cron.deny or /etc/cron.d/* or /etc/cron.hourly/* or /etc/cron.daily/* or 
+/etc/cron.weekly/* or /etc/cron.monthly/* or /etc/crontab or /usr/sbin/cron or /usr/sbin/anacron) 
+and not (
+  (process.name : ("dpkg" or "dockerd" or "rpm" or "snapd" or "yum" or "exe" or "dnf" or "podman" or 
+  "dnf-automatic" or puppet or autossl_check )) or 
+  (file.extension : ("swp" or "swpx")) or 
+  (process.name : "sed" and file.name : sed*) or 
+  (process.name : "perl" and file.name : e2scrub_all.tmp*) or
+  (process.executable : /var/lib/dpkg*)
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: Cron
+** ID: T1053.003
+** Reference URL: https://attack.mitre.org/techniques/T1053/003/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: Cron
+** ID: T1053.003
+** Reference URL: https://attack.mitre.org/techniques/T1053/003/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: Cron
+** ID: T1053.003
+** Reference URL: https://attack.mitre.org/techniques/T1053/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/cyberark-privileged-access-security-error.asciidoc b/docs/detections/prebuilt-rules/rule-details/cyberark-privileged-access-security-error.asciidoc
index 22e3332c9d..81ec894e42 100644
--- a/docs/detections/prebuilt-rules/rule-details/cyberark-privileged-access-security-error.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/cyberark-privileged-access-security-error.asciidoc
@@ -5,7 +5,7 @@ Identifies the occurrence of a CyberArk Privileged Access Security (PAS) error l
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-cyberarkpas.audit*
@@ -14,60 +14,55 @@ Identifies the occurrence of a CyberArk Privileged Access Security (PAS) error l
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASREF/Vault%20Audit%20Action%20Codes.htm?tocpath=Administration%7CReferences%7C_____3
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* cyberarkpas
-* SecOps
-* Log Auditing
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 101 (<<cyberark-privileged-access-security-error-history, version history>>)
+* Data Source: CyberArk PAS
+* Use Case: Log Auditing
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-To tune this rule, add exceptions to exclude any event.code which should not trigger this rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+
+*Triage and analysis*
+
 
 This is a promotion rule for CyberArk error events, which are alertable events per the vendor.
 Consult vendor documentation on interpreting specific events.
-----------------------------------
 
+==== Setup
+
+
+The CyberArk Privileged Access Security (PAS) Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:cyberarkpas.audit and event.type:error
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,22 +74,7 @@ event.dataset:cyberarkpas.audit and event.type:error
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
 ** Reference URL: https://attack.mitre.org/tactics/TA0001/
-
-[[cyberark-privileged-access-security-error-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/cyberark-privileged-access-security-recommended-monitor.asciidoc b/docs/detections/prebuilt-rules/rule-details/cyberark-privileged-access-security-recommended-monitor.asciidoc
index 81045a918d..301ecf129f 100644
--- a/docs/detections/prebuilt-rules/rule-details/cyberark-privileged-access-security-recommended-monitor.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/cyberark-privileged-access-security-recommended-monitor.asciidoc
@@ -5,7 +5,7 @@ Identifies the occurrence of a CyberArk Privileged Access Security (PAS) non-err
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-cyberarkpas.audit*
@@ -14,63 +14,58 @@ Identifies the occurrence of a CyberArk Privileged Access Security (PAS) non-err
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASREF/Vault%20Audit%20Action%20Codes.htm?tocpath=Administration%7CReferences%7C_____3#RecommendedActionCodesforMonitoring
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* cyberarkpas
-* SecOps
-* Log Auditing
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 101 (<<cyberark-privileged-access-security-recommended-monitor-history, version history>>)
+* Data Source: CyberArk PAS
+* Use Case: Log Auditing
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-To tune this rule, add exceptions to exclude any event.code which should not trigger this rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+
+*Triage and analysis*
+
 
 This is a promotion rule for CyberArk events, which the vendor recommends should be monitored.
 Consult vendor documentation on interpreting specific events.
-----------------------------------
 
+==== Setup
+
+
+The CyberArk Privileged Access Security (PAS) Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:cyberarkpas.audit and event.code:(4 or 22 or 24 or 31
-or 38 or 57 or 60 or 130 or 295 or 300 or 302 or 308 or
-319 or 344 or 346 or 359 or 361 or 378 or 380 or 411) and not
-event.type:error
+[source, js]
 ----------------------------------
+event.dataset:cyberarkpas.audit and
+  event.code:(4 or 22 or 24 or 31 or 38 or 57 or 60 or 130 or 295 or 300 or 302 or
+              308 or 319 or 344 or 346 or 359 or 361 or 378 or 380 or 411) and
+  not event.type:error
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -82,22 +77,7 @@ event.type:error
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
 ** Reference URL: https://attack.mitre.org/tactics/TA0001/
-
-[[cyberark-privileged-access-security-recommended-monitor-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/default-cobalt-strike-team-server-certificate.asciidoc b/docs/detections/prebuilt-rules/rule-details/default-cobalt-strike-team-server-certificate.asciidoc
index c5494cbb1b..1c67b0915e 100644
--- a/docs/detections/prebuilt-rules/rule-details/default-cobalt-strike-team-server-certificate.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/default-cobalt-strike-team-server-certificate.asciidoc
@@ -5,24 +5,24 @@ This rule detects the use of the default Cobalt Strike Team Server TLS certifica
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: critical
 
 *Risk score*: 99
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://attack.mitre.org/software/S0154/
 * https://www.cobaltstrike.com/help-setup-collaboration
@@ -31,49 +31,42 @@ This rule detects the use of the default Cobalt Strike Team Server TLS certifica
 * https://www.elastic.co/guide/en/beats/filebeat/7.9/filebeat-module-zeek.html
 * https://www.elastic.co/security-labs/collecting-cobalt-strike-beacons-with-the-elastic-stack
 
-*Tags*:
-
-* Command and Control
-* Post-Execution
-* Threat Detection
-* Elastic
-* Network
-* Host
+*Tags*: 
 
-*Version*: 101 (<<default-cobalt-strike-team-server-certificate-history, version history>>)
+* Tactic: Command and Control
+* Threat: Cobalt Strike
+* Use Case: Threat Detection
+* Domain: Endpoint
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Threat intel
 
-While Cobalt Strike is intended to be used for penetration tests and IR training, it is frequently used by actual threat actors (TA) such as APT19, APT29, APT32, APT41, FIN6, DarkHydrus, CopyKittens, Cobalt Group, Leviathan, and many other unnamed criminal TAs. This rule uses high-confidence atomic indicators, so alerts should be investigated rapidly.
-----------------------------------
+*Threat intel*
 
 
+While Cobalt Strike is intended to be used for penetration tests and IR training, it is frequently used by actual threat actors (TA) such as APT19, APT29, APT32, APT41, FIN6, DarkHydrus, CopyKittens, Cobalt Group, Leviathan, and many other unnamed criminal TAs. This rule uses high-confidence atomic indicators, so alerts should be investigated rapidly.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and
-(tls.server.hash.md5:950098276A495286EB2A2556FBAB6D83 or
-tls.server.hash.sha1:6ECE5ECE4192683D2D84E25B0BA7E04F9CB7EB7C or tls
-.server.hash.sha256:87F2085C32B6A2CC709B365F55873E207A9CAA10BFFECF2FD1
-6D3CF9D94D390C)
+[source, js]
 ----------------------------------
+(event.dataset: network_traffic.tls or event.category: (network or network_traffic))
+  and (tls.server.hash.md5:950098276A495286EB2A2556FBAB6D83
+  or tls.server.hash.sha1:6ECE5ECE4192683D2D84E25B0BA7E04F9CB7EB7C
+  or tls.server.hash.sha256:87F2085C32B6A2CC709B365F55873E207A9CAA10BFFECF2FD16D3CF9D94D390C)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -85,40 +78,7 @@ tls.server.hash.sha1:6ECE5ECE4192683D2D84E25B0BA7E04F9CB7EB7C or tls
 ** Name: Application Layer Protocol
 ** ID: T1071
 ** Reference URL: https://attack.mitre.org/techniques/T1071/
-
-[[default-cobalt-strike-team-server-certificate-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.15.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and
-(tls.server.hash.md5:950098276A495286EB2A2556FBAB6D83 or
-tls.server.hash.sha1:6ECE5ECE4192683D2D84E25B0BA7E04F9CB7EB7C or tls.s
-erver.hash.sha256:87F2085C32B6A2CC709B365F55873E207A9CAA10BFFECF2FD16D
-3CF9D94D390C)
-----------------------------------
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Web Protocols
+** ID: T1071.001
+** Reference URL: https://attack.mitre.org/techniques/T1071/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/delayed-execution-via-ping.asciidoc b/docs/detections/prebuilt-rules/rule-details/delayed-execution-via-ping.asciidoc
new file mode 100644
index 0000000000..1ae574eb6f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/delayed-execution-via-ping.asciidoc
@@ -0,0 +1,148 @@
+[[delayed-execution-via-ping]]
+=== Delayed Execution via Ping
+
+Identifies the execution of commonly abused Windows utilities via a delayed Ping execution. This behavior is often observed during malware installation and is consistent with an attacker attempting to evade detection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by process.parent.entity_id with maxspan=1m
+  [process where host.os.type == "windows" and event.action == "start" and process.name : "ping.exe" and
+   process.args : "-n" and process.parent.name : "cmd.exe" and not user.id : "S-1-5-18"]
+  [process where host.os.type == "windows" and event.action == "start" and
+   process.parent.name : "cmd.exe" and
+   (
+        process.name : (
+            "rundll32.exe", "powershell.exe",
+            "mshta.exe", "msbuild.exe",
+            "certutil.exe", "regsvr32.exe",
+            "powershell.exe", "cscript.exe",
+            "wscript.exe", "wmic.exe",
+            "installutil.exe", "msxsl.exe",
+            "Microsoft.Workflow.Compiler.exe",
+            "ieexec.exe", "iexpress.exe",
+            "RegAsm.exe", "installutil.exe",
+            "RegSvcs.exe", "RegAsm.exe"
+        ) or
+        (process.executable : "?:\\Users\\*\\AppData\\*.exe" and not process.code_signature.trusted == true)
+    ) and
+
+    not process.args : ("?:\\Program Files\\*", "?:\\Program Files (x86)\\*") and
+    not (process.name : ("openssl.exe", "httpcfg.exe", "certutil.exe") and process.parent.command_line : "*ScreenConnectConfigurator.cmd*") and
+    not (process.pe.original_file_name : "DPInst.exe" and process.command_line : "driver\\DPInst_x64  /f ") and
+    not (process.name : "powershell.exe" and process.args : "Write-Host ======*") and
+    not (process.name : "wscript.exe" and process.args : "launchquiet_args.vbs" and process.parent.args : "?:\\Windows\\TempInst\\7z*") and
+    not (process.name : "regsvr32.exe" and process.args : ("?:\\windows\\syswow64\\msxml?.dll", "msxml?.dll", "?:\\Windows\\SysWOW64\\mschrt20.ocx")) and 
+    not (process.name : "wscript.exe" and
+         process.working_directory :
+                    ("?:\\Windows\\TempInst\\*",
+                     "?:\\Users\\*\\AppData\\Local\\Temp\\BackupBootstrapper\\Logs\\",
+                     "?:\\Users\\*\\AppData\\Local\\Temp\\QBTools\\"))
+    ]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Visual Basic
+** ID: T1059.005
+** Reference URL: https://attack.mitre.org/techniques/T1059/005/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Virtualization/Sandbox Evasion
+** ID: T1497
+** Reference URL: https://attack.mitre.org/techniques/T1497/
+* Sub-technique:
+** Name: Time Based Evasion
+** ID: T1497.003
+** Reference URL: https://attack.mitre.org/techniques/T1497/003/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: CMSTP
+** ID: T1218.003
+** Reference URL: https://attack.mitre.org/techniques/T1218/003/
+* Sub-technique:
+** Name: InstallUtil
+** ID: T1218.004
+** Reference URL: https://attack.mitre.org/techniques/T1218/004/
+* Sub-technique:
+** Name: Mshta
+** ID: T1218.005
+** Reference URL: https://attack.mitre.org/techniques/T1218/005/
+* Sub-technique:
+** Name: Regsvcs/Regasm
+** ID: T1218.009
+** Reference URL: https://attack.mitre.org/techniques/T1218/009/
+* Sub-technique:
+** Name: Regsvr32
+** ID: T1218.010
+** Reference URL: https://attack.mitre.org/techniques/T1218/010/
+* Sub-technique:
+** Name: Rundll32
+** ID: T1218.011
+** Reference URL: https://attack.mitre.org/techniques/T1218/011/
+* Technique:
+** Name: System Script Proxy Execution
+** ID: T1216
+** Reference URL: https://attack.mitre.org/techniques/T1216/
+* Technique:
+** Name: XSL Script Processing
+** ID: T1220
+** Reference URL: https://attack.mitre.org/techniques/T1220/
diff --git a/docs/detections/prebuilt-rules/rule-details/delete-volume-usn-journal-with-fsutil.asciidoc b/docs/detections/prebuilt-rules/rule-details/delete-volume-usn-journal-with-fsutil.asciidoc
index 3ce62f318e..c1a1806cd1 100644
--- a/docs/detections/prebuilt-rules/rule-details/delete-volume-usn-journal-with-fsutil.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/delete-volume-usn-journal-with-fsutil.asciidoc
@@ -5,144 +5,113 @@ Identifies use of the fsutil.exe to delete the volume USNJRNL. This technique is
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<delete-volume-usn-journal-with-fsutil-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Delete Volume USN Journal with Fsutil*
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name : "fsutil.exe"
-or process.pe.original_file_name == "fsutil.exe") and process.args :
-"deletejournal" and process.args : "usn"
-----------------------------------
 
-==== Threat mapping
+The Update Sequence Number (USN) Journal is a feature in the NTFS file system used by Microsoft Windows operating systems to keep track of changes made to files and directories on a disk volume. The journal records metadata for changes such as file creation, deletion, modification, and permission changes. It is used by the operating system for various purposes, including backup and recovery, file indexing, and file replication.
 
-*Framework*: MITRE ATT&CK^TM^
+This artifact can provide valuable information in forensic analysis, such as programs executed (prefetch file operations), file modification events in suspicious directories, deleted files, etc. Attackers may delete this artifact in an attempt to cover their tracks, and this rule identifies the usage of the `fsutil.exe` utility to accomplish it.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Indicator Removal on Host
-** ID: T1070
-** Reference URL: https://attack.mitre.org/techniques/T1070/
+Consider using the Elastic Defend integration instead of USN Journal, as the Elastic Defend integration provides more visibility and context in the file operations it records.
 
-[[delete-volume-usn-journal-with-fsutil-history]]
-==== Rule version history
 
-Version 102 (8.6.0 release)::
-* Formatting only
+*Possible investigation steps*
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "fsutil.exe" or process.pe.original_file_name ==
-"fsutil.exe") and process.args : "deletejournal" and process.args :
-"usn"
-----------------------------------
 
-Version 12 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "fsutil.exe" or process.pe.original_file_name ==
-"fsutil.exe") and process.args : "deletejournal" and process.args :
-"usn"
-----------------------------------
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - Verify if any other anti-forensics behaviors were observed.
+- Review file operation logs from Elastic Defend for suspicious activity the attacker tried to hide.
 
-Version 10 (8.2.0 release)::
-* Formatting only
 
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:fsutil.exe and process.args:(deletejournal and usn)
-----------------------------------
+*False positive analysis*
 
-Version 8 (7.12.0 release)::
-* Formatting only
 
-Version 7 (7.11.2 release)::
-* Formatting only
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-Version 6 (7.11.0 release)::
-* Formatting only
 
-Version 5 (7.10.0 release)::
-* Formatting only
+*Response and remediation*
 
-Version 4 (7.9.1 release)::
-* Formatting only
 
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:fsutil.exe and process.args:(deletejournal and usn)
-----------------------------------
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
 
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:"fsutil.exe" and process.args:("usn" and "deletejournal")
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "fsutil.exe" or ?process.pe.original_file_name == "fsutil.exe") and
+  process.args : "deletejournal" and process.args : "usn"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indicator Removal
+** ID: T1070
+** Reference URL: https://attack.mitre.org/techniques/T1070/
+* Sub-technique:
+** Name: File Deletion
+** ID: T1070.004
+** Reference URL: https://attack.mitre.org/techniques/T1070/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/deleting-backup-catalogs-with-wbadmin.asciidoc b/docs/detections/prebuilt-rules/rule-details/deleting-backup-catalogs-with-wbadmin.asciidoc
index 7225c736d2..b529b077f0 100644
--- a/docs/detections/prebuilt-rules/rule-details/deleting-backup-catalogs-with-wbadmin.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/deleting-backup-catalogs-with-wbadmin.asciidoc
@@ -5,105 +5,124 @@ Identifies use of the wbadmin.exe to delete the backup catalog. Ransomware and o
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Impact
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<deleting-backup-catalogs-with-wbadmin-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Deleting Backup Catalogs with Wbadmin
+*Triage and analysis*
+
+
+
+*Investigating Deleting Backup Catalogs with Wbadmin*
 
-Windows Server Backup stores the details about your backups (what volumes are backed up and where the backups are
-located) in a file called a backup catalog, which ransomware victims can use to recover corrupted backup files.
-Deleting these files is a common step in threat actor playbooks.
+
+Windows Server Backup stores the details about your backups (what volumes are backed up and where the backups are located) in a file called a backup catalog, which ransomware victims can use to recover corrupted backup files. Deleting these files is a common step in threat actor playbooks.
 
 This rule identifies the deletion of the backup catalog using the `wbadmin.exe` utility.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
 - Check if any files on the host machine have been encrypted.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - Administrators can use this command to delete corrupted catalogs, but overall the activity is unlikely to be legitimate.
 
-### Related rules
+
+*Related rules*
+
 
 - Third-party Backup Files Deleted via Unexpected Process - 11ea6bec-ebde-4d71-a8e9-784948f8e3e9
 - Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
 - Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
 - Volume Shadow Copy Deletion via WMIC - dc9c1f74-dac3-48e3-b47f-eb79db358f57
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look
-for ransomware preparation and execution activities.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look for ransomware preparation and execution activities.
 - If any backups were affected:
   - Perform data recovery locally or restore the backups from replicated copies (cloud, other servers, etc.).
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"wbadmin.exe" or process.pe.original_file_name == "WBADMIN.EXE") and
-process.args : "catalog" and process.args : "delete"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "wbadmin.exe" or ?process.pe.original_file_name == "WBADMIN.EXE") and
+  process.args : "catalog" and process.args : "delete"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -115,75 +134,7 @@ process.args : "catalog" and process.args : "delete"
 ** Name: Inhibit System Recovery
 ** ID: T1490
 ** Reference URL: https://attack.mitre.org/techniques/T1490/
-
-[[deleting-backup-catalogs-with-wbadmin-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "wbadmin.exe" or process.pe.original_file_name ==
-"WBADMIN.EXE") and process.args : "catalog" and process.args :
-"delete"
-----------------------------------
-
-Version 14 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 11 (8.2.0 release)::
-* Formatting only
-
-Version 10 (7.16.0 release)::
-* Formatting only
-
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:wbadmin.exe and process.args:(catalog and delete)
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:wbadmin.exe and process.args:(catalog and delete)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:"wbadmin.exe" and process.args:("delete" and "catalog")
-----------------------------------
-
+* Technique:
+** Name: Data Destruction
+** ID: T1485
+** Reference URL: https://attack.mitre.org/techniques/T1485/
diff --git a/docs/detections/prebuilt-rules/rule-details/direct-outbound-smb-connection.asciidoc b/docs/detections/prebuilt-rules/rule-details/direct-outbound-smb-connection.asciidoc
index 7346f25c71..4fcb5ddb94 100644
--- a/docs/detections/prebuilt-rules/rule-details/direct-outbound-smb-connection.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/direct-outbound-smb-connection.asciidoc
@@ -5,90 +5,90 @@ Identifies unexpected processes making network connections over port 445. Window
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<direct-outbound-smb-connection-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Direct Outbound SMB Connection
+*Triage and analysis*
+
+
 
-This rule looks for unexpected processes making network connections over port 445. Windows file sharing is typically
-implemented over Server Message Block (SMB), which communicates between hosts using port 445. When legitimate, these
-network connections are established by the kernel (PID 4). Occurrences of non-system processes using this port can indicate
-port scanners, exploits, and tools used to move laterally on the environment.
+*Investigating Direct Outbound SMB Connection*
+
+
+This rule looks for unexpected processes making network connections over port 445. Windows file sharing is typically implemented over Server Message Block (SMB), which communicates between hosts using port 445. When legitimate, these network connections are established by the kernel (PID 4). Occurrences of non-system processes using this port can indicate port scanners, exploits, and tools used to move laterally on the environment.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Contact the account owner and confirm whether they are aware of this activity.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
 
 
-### False positive analysis
+*False positive analysis*
 
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination
-of user and command line conditions.
 
-### Response and remediation
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -96,46 +96,28 @@ of user and command line conditions.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where event.type == "start"
-and host.os.name == "Windows" and process.pid != 4 and not
-(process.executable :
-"D:\\EnterpriseCare\\tools\\jre.1\\bin\\java.exe" and process.args :
-"com.emeraldcube.prism.launcher.Invoker") and not
-(process.executable : "C:\\Docusnap 11\\Tools\\nmap\\nmap.exe" and
-process.args : "smb-os-discovery.nse") and not process.executable :
-("?:\\Program Files\\SentinelOne\\Sentinel Agent
-*\\Ranger\\SentinelRanger.exe", "?:\\Program
-Files\\Ivanti\\Security Controls\\ST.EngineHost.exe",
-"?:\\Program Files (x86)\\Fortinet\\FSAE\\collectoragent.exe",
-"?:\\Program Files (x86)\\Nmap\\nmap.exe", "?:\\Program
-Files\\Azure Advanced Threat Protection
-Sensor\\*\\Microsoft.Tri.Sensor.exe", "?:\\Program
-Files\\CloudMatters\\auvik\\AuvikService-release-*\\AuvikService.exe",
-"?:\\Program Files\\uptime software\\uptime\\UptimeDataCollector.exe",
-"?:\\Program Files\\CloudMatters\\auvik\\AuvikAgentService.exe",
-"?:\\Program Files\\Rumble\\rumble-agent-*.exe")] [network where
-destination.port == 445 and process.pid != 4 and not
-cidrmatch(destination.ip, "127.0.0.1", "::1")]
+[source, js]
 ----------------------------------
+sequence by process.entity_id with maxspan=2m
+  [process where host.os.type == "windows" and event.type == "start" and process.pid != 4 and 
+   not user.id : ("S-1-5-19", "S-1-5-20") and 
+   not (process.code_signature.trusted == true and not process.code_signature.subject_name : "Microsoft *") and 
+   not (process.name : "powershell.exe" and process.args : "?:\\ProgramData\\Microsoft\\Windows Defender Advanced Threat Protection\\Downloads\\PSScript_*.ps1")]
+  [network where host.os.type == "windows" and destination.port == 445 and process.pid != 4 and
+     not cidrmatch(destination.ip, "127.0.0.1", "::1")]
+until [process where host.os.type == "windows" and event.type == "end"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -147,63 +129,7 @@ cidrmatch(destination.ip, "127.0.0.1", "::1")]
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[direct-outbound-smb-connection-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where event.type == "start"
-and process.pid != 4] [network where destination.port == 445 and
-process.pid != 4 and not cidrmatch(destination.ip, "127.0.0.1",
-"::1")]
-----------------------------------
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (7.16.0 release)::
-* Formatting only
-
-Version 6 (7.12.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:connection and
-destination.port:445 and not process.pid:4 and not
-destination.ip:(127.0.0.1 or "::1")
-----------------------------------
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Network connection detected (rule: NetworkConnect)" and
-destination.port:445 and not process.pid:4 and not
-destination.ip:(127.0.0.1 or "::1")
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Network connection detected (rule: NetworkConnect)" and
-destination.port:445 and not process.pid:4 and not
-destination.ip:("127.0.0.1" or "::1")
-----------------------------------
-
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/disable-windows-event-and-security-logs-using-built-in-tools.asciidoc b/docs/detections/prebuilt-rules/rule-details/disable-windows-event-and-security-logs-using-built-in-tools.asciidoc
index 1550121a06..e11ef3eef8 100644
--- a/docs/detections/prebuilt-rules/rule-details/disable-windows-event-and-security-logs-using-built-in-tools.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/disable-windows-event-and-security-logs-using-built-in-tools.asciidoc
@@ -5,168 +5,151 @@ Identifies attempts to disable EventLog via the logman Windows utility, PowerShe
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/logman
 * https://medium.com/palantir/tampering-with-windows-event-tracing-background-offense-and-defense-4be7ac62ac63
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<disable-windows-event-and-security-logs-using-built-in-tools-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Ivan Ninichuck, Austin Songer
+* Elastic
+* Ivan Ninichuck
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Disable Windows Event and Security Logs Using Built-in Tools
+*Triage and analysis*
+
 
-Windows event logs are a fundamental data source for security monitoring, forensics, and incident response. Adversaries
-can tamper, clear, and delete this data to break SIEM detections, cover their tracks, and slow down incident response.
+
+*Investigating Disable Windows Event and Security Logs Using Built-in Tools*
+
+
+Windows event logs are a fundamental data source for security monitoring, forensics, and incident response. Adversaries can tamper, clear, and delete this data to break SIEM detections, cover their tracks, and slow down incident response.
 
 This rule looks for the usage of different utilities to disable the EventLog service or specific event logs.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
   - Verify if any other anti-forensics behaviors were observed.
 - Investigate the event logs prior to the action for suspicious behaviors that an attacker may be trying to cover up.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
 - Re-enable affected logging components, services, and security monitoring.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
-==== Rule query
+==== Setup
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and ((process.name:"logman.exe"
-or process.pe.original_file_name == "Logman.exe") and
-process.args : "EventLog-*" and process.args : ("stop", "delete")) or
-((process.name : ("pwsh.exe", "powershell.exe", "powershell_ise.exe")
-or process.pe.original_file_name in ("pwsh.exe",
-"powershell.exe", "powershell_ise.exe")) and process.args :
-"Set-Service" and process.args: "EventLog" and process.args :
-"Disabled") or ((process.name:"auditpol.exe" or
-process.pe.original_file_name == "AUDITPOL.EXE") and process.args :
-"/success:disable")
-----------------------------------
 
-==== Threat mapping
+*Setup*
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Indicator Removal on Host
-** ID: T1070
-** Reference URL: https://attack.mitre.org/techniques/T1070/
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
-[[disable-windows-event-and-security-logs-using-built-in-tools-history]]
-==== Rule version history
 
-Version 102 (8.6.0 release)::
-* Formatting only
+==== Rule query
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-((process.name:"logman.exe" or process.pe.original_file_name ==
-"Logman.exe") and process.args : "EventLog-*" and process.args :
-("stop", "delete")) or ((process.name : ("pwsh.exe",
-"powershell.exe", "powershell_ise.exe") or
-process.pe.original_file_name in ("pwsh.exe", "powershell.exe",
-"powershell_ise.exe")) and process.args : "Set-Service" and
-process.args: "EventLog" and process.args : "Disabled") or
-((process.name:"auditpol.exe" or process.pe.original_file_name ==
-"AUDITPOL.EXE") and process.args : "/success:disable")
-----------------------------------
 
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-process where event.type in ("start", "process_started") and
-((process.name:"logman.exe" or process.pe.original_file_name ==
-"Logman.exe") and process.args : "EventLog-*" and process.args :
-("stop", "delete")) or ((process.name : ("pwsh.exe",
-"powershell.exe", "powershell_ise.exe") or
-process.pe.original_file_name in ("pwsh.exe", "powershell.exe",
-"powershell_ise.exe")) and process.args : "Set-Service" and
-process.args: "EventLog" and process.args : "Disabled") or
-((process.name:"auditpol.exe" or process.pe.original_file_name ==
-"AUDITPOL.EXE") and process.args : "/success:disable")
-----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+(
+  ((process.name:"logman.exe" or ?process.pe.original_file_name == "Logman.exe") and
+      process.args : "EventLog-*" and process.args : ("stop", "delete")) or
 
-Version 4 (8.3.0 release)::
-* Formatting only
+  ((process.name : ("pwsh.exe", "powershell.exe", "powershell_ise.exe") or ?process.pe.original_file_name in
+      ("pwsh.exe", "powershell.exe", "powershell_ise.exe")) and
+	process.args : "Set-Service" and process.args: "EventLog" and process.args : "Disabled")  or
 
-Version 3 (8.2.0 release)::
-* Formatting only
+  ((process.name:"auditpol.exe" or ?process.pe.original_file_name == "AUDITPOL.EXE") and process.args : "/success:disable")
+)
 
-Version 2 (7.16.0 release)::
-* Formatting only
+----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indicator Removal
+** ID: T1070
+** Reference URL: https://attack.mitre.org/techniques/T1070/
+* Sub-technique:
+** Name: Clear Windows Event Logs
+** ID: T1070.001
+** Reference URL: https://attack.mitre.org/techniques/T1070/001/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable Windows Event Logging
+** ID: T1562.002
+** Reference URL: https://attack.mitre.org/techniques/T1562/002/
+* Sub-technique:
+** Name: Indicator Blocking
+** ID: T1562.006
+** Reference URL: https://attack.mitre.org/techniques/T1562/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/disable-windows-firewall-rules-via-netsh.asciidoc b/docs/detections/prebuilt-rules/rule-details/disable-windows-firewall-rules-via-netsh.asciidoc
index 4370f15e79..04fbd6cb10 100644
--- a/docs/detections/prebuilt-rules/rule-details/disable-windows-firewall-rules-via-netsh.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/disable-windows-firewall-rules-via-netsh.asciidoc
@@ -5,96 +5,116 @@ Identifies use of the netsh.exe to disable or weaken the local firewall. Attacke
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<disable-windows-firewall-rules-via-netsh-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Disable Windows Firewall Rules via Netsh
+*Triage and analysis*
+
+
+
+*Investigating Disable Windows Firewall Rules via Netsh*
 
-The Windows Defender Firewall is a native component which provides host-based, two-way network traffic filtering for a
-device, and blocks unauthorized network traffic flowing into or out of the local device.
+
+The Windows Defender Firewall is a native component which provides host-based, two-way network traffic filtering for a device, and blocks unauthorized network traffic flowing into or out of the local device.
 
 Attackers can disable the Windows firewall or its rules to enable lateral movement and command and control activity.
 
 This rule identifies patterns related to disabling the Windows firewall or its rules using the `netsh.exe` utility.
 
-#### Possible investigation steps
+
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the user to check if they are aware of the operation.
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Check whether the user is an administrator and is legitimately performing
-troubleshooting.
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Check whether the user is an administrator and is legitimately performing troubleshooting.
 - In case of an allowed benign true positive (B-TP), assess adding rules to allow needed traffic and re-enable the firewall.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "netsh.exe"
-and ( (process.args : "disable" and process.args : "firewall"
-and process.args : "set") or (process.args : "advfirewall" and
-process.args : "off" and process.args : "state") )
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "netsh.exe" and
+  (
+    (process.args : "disable" and process.args : "firewall" and process.args : "set") or
+    (process.args : "advfirewall" and process.args : "off" and process.args : "state")
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -106,78 +126,7 @@ process.args : "off" and process.args : "state") )
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[disable-windows-firewall-rules-via-netsh-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "netsh.exe" and (process.args : "disable" and
-process.args : "firewall" and process.args : "set") or (process.args
-: "advfirewall" and process.args : "off" and process.args : "state")
-----------------------------------
-
-Version 14 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 11 (8.2.0 release)::
-* Formatting only
-
-Version 10 (7.16.0 release)::
-* Formatting only
-
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:netsh.exe and process.args:(disable and firewall and set)
-or process.args:(advfirewall and off and state)
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:netsh.exe and process.args:(disable and firewall and set)
-or process.args:(advfirewall and off and state)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:"netsh.exe" and process.args:("firewall" and "set" and
-"disable") or process.args:("advfirewall" and "state" and "off")
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify System Firewall
+** ID: T1562.004
+** Reference URL: https://attack.mitre.org/techniques/T1562/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/disabling-user-account-control-via-registry-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/disabling-user-account-control-via-registry-modification.asciidoc
index 154f30f42f..d9073a9d1a 100644
--- a/docs/detections/prebuilt-rules/rule-details/disabling-user-account-control-via-registry-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/disabling-user-account-control-via-registry-modification.asciidoc
@@ -5,74 +5,74 @@ User Account Control (UAC) can help mitigate the impact of malware on Windows ho
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.greyhathacker.net/?p=796
 * https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/user-account-control-group-policy-and-registry-key-settings
 * https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/user-account-control-overview
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Investigation Guide
-
-*Version*: 102 (<<disabling-user-account-control-via-registry-modification-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Disabling User Account Control via Registry Modification
+*Triage and analysis*
+
+
+
+*Investigating Disabling User Account Control via Registry Modification*
+
+
+Windows User Account Control (UAC) allows a program to elevate its privileges (tracked as low to high integrity levels) to perform a task under administrator-level permissions, possibly by prompting the user for confirmation. UAC can deny an operation under high-integrity enforcement, or allow the user to perform the action if they are in the local administrators group and enter an administrator password when prompted.
+
+For more information about the UAC and how it works, check the https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/how-user-account-control-works[official Microsoft docs page].
 
-Windows User Account Control (UAC) allows a program to elevate its privileges (tracked as low to high integrity levels)
-to perform a task under administrator-level permissions, possibly by prompting the user for confirmation.
-UAC can deny an operation under high-integrity enforcement, or allow the user to perform the action if they are in the
-local administrators group and enter an administrator password when prompted.
+Attackers may disable UAC to execute code directly in high integrity. This rule identifies registry value changes to bypass the UAC protection.
 
-For more information about the UAC and how it works, check the [official Microsoft docs page](https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/how-user-account-control-works).
 
-Attackers may disable UAC to execute code directly in high integrity. This rule identifies registry value changes to
-bypass the UAC protection.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Inspect the host for suspicious or abnormal behaviors in the alert timeframe.
-- Investigate abnormal behaviors observed by the subject process such as network connections, registry or file
-modifications, and any spawned child processes.
+- Investigate abnormal behaviors observed by the subject process such as network connections, registry or file modifications, and any spawned child processes.
 - Analyze non-system processes executed with high integrity after UAC was disabled for unknown or suspicious processes.
 - Retrieve the suspicious processes' executables and determine if they are malicious:
   - Use a private sandboxed malware analysis system to perform analysis.
@@ -84,11 +84,15 @@ modifications, and any spawned child processes.
   - Use the PowerShell `Get-FileHash` cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -96,35 +100,47 @@ modifications, and any spawned child processes.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
 - Restore UAC settings to the desired state.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type == "change" and registry.path : (
-"HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\
-\EnableLUA", "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion
-\\Policies\\System\\ConsentPromptBehaviorAdmin", "HKLM\\SOFTWARE
-\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\PromptOnSecure
-Desktop" ) and registry.data.strings : ("0", "0x00000000")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type == "change" and
+  registry.path :
+    (
+      "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\EnableLUA",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\ConsentPromptBehaviorAdmin",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\PromptOnSecureDesktop",
+      "\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\EnableLUA",
+      "\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\ConsentPromptBehaviorAdmin",
+      "\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\PromptOnSecureDesktop"
+    ) and
+  registry.data.strings : ("0", "0x00000000")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -136,8 +152,10 @@ Desktop" ) and registry.data.strings : ("0", "0x00000000")
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -146,35 +164,19 @@ Desktop" ) and registry.data.strings : ("0", "0x00000000")
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[disabling-user-account-control-via-registry-modification-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type == "change" and registry.path : (
-"HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\
-\EnableLUA", "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion
-\\Policies\\System\\ConsentPromptBehaviorAdmin", "HKLM\\SOFTWARE
-\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\PromptOnSecure
-Desktop" ) and registry.data.strings : "0"
-----------------------------------
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/disabling-windows-defender-security-settings-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/disabling-windows-defender-security-settings-via-powershell.asciidoc
index d35c038211..3b74ced071 100644
--- a/docs/detections/prebuilt-rules/rule-details/disabling-windows-defender-security-settings-via-powershell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/disabling-windows-defender-security-settings-via-powershell.asciidoc
@@ -5,118 +5,128 @@ Identifies use of the Set-MpPreference PowerShell command to disable or weaken c
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/defender/set-mppreference?view=windowsserver2019-ps
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<disabling-windows-defender-security-settings-via-powershell-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Planned Windows Defender configuration changes.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Disabling Windows Defender Security Settings via PowerShell
+*Triage and analysis*
+
 
-Microsoft Windows Defender is an antivirus product built into Microsoft Windows, which makes it popular across multiple
-environments. Disabling it is a common step in threat actor playbooks.
+
+*Investigating Disabling Windows Defender Security Settings via PowerShell*
+
+
+Microsoft Windows Defender is an antivirus product built into Microsoft Windows, which makes it popular across multiple environments. Disabling it is a common step in threat actor playbooks.
 
 This rule monitors the execution of commands that can tamper the Windows Defender antivirus features.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate
-software installations.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Examine the command line to determine which action was executed. Based on that, examine exceptions, antivirus state,
-sample submission, etc.
+- Examine the command line to determine which action was executed. Based on that, examine exceptions, antivirus state, sample submission, etc.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity,
-the configuration is justified (for example, it is being used to deploy other security solutions or troubleshooting),
-and no other suspicious activity has been observed.
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity, the configuration is justified (for example, it is being used to deploy other security solutions or troubleshooting), and no other suspicious activity has been observed.
+
+
+*Related rules*
 
-### Related rules
 
 - Windows Defender Disabled via Registry Modification - 2ffa1f1e-b6db-47fa-994b-1512743847eb
 - Microsoft Windows Defender Tampering - fe794edd-487f-4a90-b285-3ee54f2af2d3
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Based on the command line, take actions to restore the appropriate Windows Defender antivirus configurations.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Review the privileges assigned to the user to ensure that the least privilege principle is being followed.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-("powershell.exe", "pwsh.exe", "powershell_ise.exe") or
-process.pe.original_file_name in ("powershell.exe", "pwsh.dll",
-"powershell_ise.exe")) and process.args : "Set-MpPreference" and
-process.args : ("-Disable*", "Disabled", "NeverSend", "-Exclusion*")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (
+    process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe") or
+    ?process.pe.original_file_name in ("powershell.exe", "pwsh.dll", "powershell_ise.exe")
+  ) and
+  process.args : "Set-MpPreference" and process.args : ("-Disable*", "Disabled", "NeverSend", "-Exclusion*")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -128,33 +138,19 @@ process.args : ("-Disable*", "Disabled", "NeverSend", "-Exclusion*")
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[disabling-windows-defender-security-settings-via-powershell-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and (process.name :
-("powershell.exe", "pwsh.exe") or process.pe.original_file_name ==
-"PowerShell.EXE") and process.args : "Set-MpPreference" and
-process.args : ("-Disable*", "Disabled", "NeverSend", "-Exclusion*")
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/discovery-of-domain-groups.asciidoc b/docs/detections/prebuilt-rules/rule-details/discovery-of-domain-groups.asciidoc
new file mode 100644
index 0000000000..255484890c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/discovery-of-domain-groups.asciidoc
@@ -0,0 +1,68 @@
+[[discovery-of-domain-groups]]
+=== Discovery of Domain Groups
+
+Identifies the execution of Linux built-in commands related to account or group enumeration. Adversaries may use account and group information to orient themselves before deciding how to act.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and (
+  process.name in ("ldapsearch", "dscacheutil") or (process.name == "dscl" and process.args : "*-list*")
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Permission Groups Discovery
+** ID: T1069
+** Reference URL: https://attack.mitre.org/techniques/T1069/
diff --git a/docs/detections/prebuilt-rules/rule-details/discovery-of-internet-capabilities-via-built-in-tools.asciidoc b/docs/detections/prebuilt-rules/rule-details/discovery-of-internet-capabilities-via-built-in-tools.asciidoc
new file mode 100644
index 0000000000..dd2e2cf749
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/discovery-of-internet-capabilities-via-built-in-tools.asciidoc
@@ -0,0 +1,66 @@
+[[discovery-of-internet-capabilities-via-built-in-tools]]
+=== Discovery of Internet Capabilities via Built-in Tools
+
+Identifies the use of built-in tools attackers can use to check for Internet connectivity on compromised systems. These results may be used to determine communication capabilities with C2 servers, or to identify routes, redirectors, and proxy servers.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 102
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:windows and event.category:process and event.type:start and 
+process.name.caseless:("ping.exe" or "tracert.exe" or "pathping.exe") and
+not process.args:("127.0.0.1" or "0.0.0.0" or "localhost" or "::1")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Network Configuration Discovery
+** ID: T1016
+** Reference URL: https://attack.mitre.org/techniques/T1016/
+* Sub-technique:
+** Name: Internet Connection Discovery
+** ID: T1016.001
+** Reference URL: https://attack.mitre.org/techniques/T1016/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/dns-over-https-enabled-via-registry.asciidoc b/docs/detections/prebuilt-rules/rule-details/dns-over-https-enabled-via-registry.asciidoc
index 3b56f9b384..6bce6db15d 100644
--- a/docs/detections/prebuilt-rules/rule-details/dns-over-https-enabled-via-registry.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/dns-over-https-enabled-via-registry.asciidoc
@@ -5,72 +5,75 @@ Identifies when a user enables DNS-over-HTTPS. This can be used to hide internet
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.tenforums.com/tutorials/151318-how-enable-disable-dns-over-https-doh-microsoft-edge.html
 * https://chromeenterprise.google/policies/?policy=DnsOverHttpsMode
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Version*: 101 (<<dns-over-https-enabled-via-registry-history, version history>>)
+*Version*: 109
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-(registry.path :
-"*\\SOFTWARE\\Policies\\Microsoft\\Edge\\BuiltInDnsClientEnabled" and
-registry.data.strings : "1") or (registry.path :
-"*\\SOFTWARE\\Google\\Chrome\\DnsOverHttpsMode" and
-registry.data.strings : "secure") or (registry.path :
-"*\\SOFTWARE\\Policies\\Mozilla\\Firefox\\DNSOverHTTPS" and
-registry.data.strings : "1")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type in ("creation", "change") and
+  (registry.path : "*\\SOFTWARE\\Policies\\Microsoft\\Edge\\BuiltInDnsClientEnabled" and
+  registry.data.strings : "1") or
+  (registry.path : "*\\SOFTWARE\\Google\\Chrome\\DnsOverHttpsMode" and
+  registry.data.strings : "secure") or
+  (registry.path : "*\\SOFTWARE\\Policies\\Mozilla\\Firefox\\DNSOverHTTPS" and
+  registry.data.strings : "1")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -82,22 +85,7 @@ registry.data.strings : "1")
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[dns-over-https-enabled-via-registry-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.0.0 release)::
-* Formatting only
-
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/dns-tunneling.asciidoc b/docs/detections/prebuilt-rules/rule-details/dns-tunneling.asciidoc
index 162fadce2e..0aee1969bf 100644
--- a/docs/detections/prebuilt-rules/rule-details/dns-tunneling.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/dns-tunneling.asciidoc
@@ -5,47 +5,37 @@ A machine learning job detected unusually large numbers of DNS queries for a sin
 
 *Rule type*: machine_learning
 
-*Machine learning job*: packetbeat_dns_tunneling
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Network
-* Threat Detection
-* ML
-* Command and Control
+*Tags*: 
 
-*Version*: 100 (<<dns-tunneling-history, version history>>)
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Command and Control
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-DNS domains that use large numbers of child domains, such as software or content distribution networks, can trigger this alert and such parent domains can be excluded.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -57,22 +47,3 @@ DNS domains that use large numbers of child domains, such as software or content
 ** Name: Protocol Tunneling
 ** ID: T1572
 ** Reference URL: https://attack.mitre.org/techniques/T1572/
-
-[[dns-tunneling-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/domain-added-to-google-workspace-trusted-domains.asciidoc b/docs/detections/prebuilt-rules/rule-details/domain-added-to-google-workspace-trusted-domains.asciidoc
index cb4c1fa359..8b92c2ec78 100644
--- a/docs/detections/prebuilt-rules/rule-details/domain-added-to-google-workspace-trusted-domains.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/domain-added-to-google-workspace-trusted-domains.asciidoc
@@ -5,7 +5,7 @@ Detects when a domain is added to the list of trusted Google Workspace domains.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,46 +14,91 @@ Detects when a domain is added to the list of trusted Google Workspace domains.
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/6160020?hl=en
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+
+*Version*: 205
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Defense Evasion
 
-*Version*: 101 (<<domain-added-to-google-workspace-trusted-domains-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Trusted domains may be added by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
-==== Investigation guide
 
+*Investigating Domain Added to Google Workspace Trusted Domains*
+
+
+Organizations use trusted domains in Google Workspace to give external users access to resources.
+
+A threat actor with administrative privileges may be able to add a malicious domain to the trusted domain list. Based on the configuration, potentially sensitive resources may be exposed or accessible by an unintended third-party.
+
+This rule detects when a third-party domain is added to the list of trusted domains in Google Workspace.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
+- After identifying the user, verify if the user should have administrative privileges to add external domains.
+- Check the `google_workspace.admin.domain.name` field to find the newly added domain.
+- Use reputational services, such as VirusTotal, for the trusted domain's third-party intelligence reputation.
+- Filter your data. Create a filter where `event.dataset` is `google_workspace.drive` and `google_workspace.drive.file.owner.email` is being compared to `user.email`.
+    - If mismatches are identified, this could indicate access from an external Google Workspace domain.
+
+
+*False positive analysis*
+
+
+- Verify that the user account should have administrative privileges that allow them to edit trusted domains in Google Workspace.
+- Talk to the user to evaluate why they added the third-party domain and if the domain has confidentiality risks.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -61,19 +106,20 @@ Trusted domains may be added by system administrators. Verify that the configura
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
 
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:google_workspace.admin and event.provider:admin and
-event.category:iam and event.action:ADD_TRUSTED_DOMAINS
+[source, js]
 ----------------------------------
+event.dataset:google_workspace.admin and event.provider:admin and event.category:iam and event.action:ADD_TRUSTED_DOMAINS
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -85,44 +131,7 @@ event.category:iam and event.action:ADD_TRUSTED_DOMAINS
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[domain-added-to-google-workspace-trusted-domains-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 14 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:ADD_TRUSTED_DOMAINS
-----------------------------------
-
-Version 5 (7.15.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/downloaded-shortcut-files.asciidoc b/docs/detections/prebuilt-rules/rule-details/downloaded-shortcut-files.asciidoc
new file mode 100644
index 0000000000..06cf332409
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/downloaded-shortcut-files.asciidoc
@@ -0,0 +1,79 @@
+[[downloaded-shortcut-files]]
+=== Downloaded Shortcut Files
+
+Identifies .lnk shortcut file downloaded from outside the local network. These shortcut files are commonly used in phishing campaigns.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and file.extension == "lnk" and file.Ext.windows.zone_identifier > 1
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: User Execution
+** ID: T1204
+** Reference URL: https://attack.mitre.org/techniques/T1204/
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/downloaded-url-files.asciidoc b/docs/detections/prebuilt-rules/rule-details/downloaded-url-files.asciidoc
new file mode 100644
index 0000000000..13111ebc7d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/downloaded-url-files.asciidoc
@@ -0,0 +1,77 @@
+[[downloaded-url-files]]
+=== Downloaded URL Files
+
+Identifies .url shortcut files downloaded from outside the local network. These shortcut files are commonly used in phishing campaigns.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and file.extension == "url"
+   and file.Ext.windows.zone_identifier > 1 and not process.name : "explorer.exe"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: User Execution
+** ID: T1204
+** Reference URL: https://attack.mitre.org/techniques/T1204/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/dumping-account-hashes-via-built-in-commands.asciidoc b/docs/detections/prebuilt-rules/rule-details/dumping-account-hashes-via-built-in-commands.asciidoc
index 7c0b3495a6..1403d56380 100644
--- a/docs/detections/prebuilt-rules/rule-details/dumping-account-hashes-via-built-in-commands.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/dumping-account-hashes-via-built-in-commands.asciidoc
@@ -5,55 +5,88 @@ Identifies the execution of macOS built-in commands used to dump user account ha
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://apple.stackexchange.com/questions/186893/os-x-10-9-where-are-password-hashes-stored
 * https://www.unix.com/man-page/osx/8/mkpassdb/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Credential Access
 
-*Version*: 100 (<<dumping-account-hashes-via-built-in-commands-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:start and
-process.name:(defaults or mkpassdb) and process.args:(ShadowHashData
-or "-dump")
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:start and
+ process.name:(defaults or mkpassdb) and process.args:(ShadowHashData or "-dump")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -65,13 +98,3 @@ or "-dump")
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[dumping-account-hashes-via-built-in-commands-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/dumping-of-keychain-content-via-security-command.asciidoc b/docs/detections/prebuilt-rules/rule-details/dumping-of-keychain-content-via-security-command.asciidoc
index 84cbfd9b01..4abed2ac65 100644
--- a/docs/detections/prebuilt-rules/rule-details/dumping-of-keychain-content-via-security-command.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/dumping-of-keychain-content-via-security-command.asciidoc
@@ -5,62 +5,86 @@ Adversaries may dump the content of the keychain storage data from a system to a
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://ss64.com/osx/security.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Credential Access
 
-*Version*: 100 (<<dumping-of-keychain-content-via-security-command-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This rule requires data coming in from Elastic Defend.
 
-----------------------------------
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.args : "dump-keychain" and process.args : "-d"
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and process.args : "dump-keychain" and process.args : "-d"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,16 +96,7 @@ process.args : "dump-keychain" and process.args : "-d"
 ** Name: Credentials from Password Stores
 ** ID: T1555
 ** Reference URL: https://attack.mitre.org/techniques/T1555/
-
-[[dumping-of-keychain-content-via-security-command-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Keychain
+** ID: T1555.001
+** Reference URL: https://attack.mitre.org/techniques/T1555/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/dynamic-linker-copy.asciidoc b/docs/detections/prebuilt-rules/rule-details/dynamic-linker-copy.asciidoc
index e9d86c5004..bd2446f141 100644
--- a/docs/detections/prebuilt-rules/rule-details/dynamic-linker-copy.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/dynamic-linker-copy.asciidoc
@@ -5,56 +5,176 @@ Detects the copying of the Linux dynamic loader binary and subsequent file creat
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-*
+* logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.intezer.com/blog/incident-response/orbit-new-undetected-linux-threat/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Threat: Orbit
+* Data Source: Elastic Defend
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Persistence
-* Orbit
 
-*Version*: 100 (<<dynamic-linker-copy-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.4.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Triage and analysis*
+
+
+
+*Investigating Dynamic Linker Copy*
+
+
+The Linux dynamic linker is responsible for loading shared libraries required by executables at runtime. It is a critical component of the Linux operating system and should not be tampered with. 
+
+Adversaries may attempt to copy the dynamic linker binary and create a backup copy before patching it to inject and preload malicious shared object files. This technique has been observed in recent Linux malware attacks and is considered highly suspicious or malicious.
+
+The detection rule 'Dynamic Linker Copy' is designed to identify such abuse by monitoring for processes with names "cp" or "rsync" that involve copying the dynamic linker binary ("/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2") and modifying the "/etc/ld.so.preload" file. Additionally, the rule checks for the creation of new files with the "so" extension on Linux systems. By detecting these activities within a short time span (1 minute), the rule aims to alert security analysts to potential malicious behavior.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Investigate the dynamic linker that was copied or altered.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE (\n  path = '/etc/ld.so.preload' OR\n  path = '/lib64/ld-linux-x86-64.so.2' OR\n  path = '/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' OR\n  path = '/usr/lib64/ld-linux-x86-64.so.2' OR\n  path = '/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2'\n)\n"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE (\n  path = '/etc/ld.so.preload' OR\n  path = '/lib64/ld-linux-x86-64.so.2' OR\n  path = '/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' OR\n  path = '/usr/lib64/ld-linux-x86-64.so.2' OR\n  path = '/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2'\n)\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+    - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+    - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+- Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+- The security team should address any potential benign true positive (B-TP), as this configuration can put the user and the domain at risk.
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Related Rules*
+
+
+- Modification of Dynamic Linker Preload Shared Object Inside A Container - 342f834b-21a6-41bf-878c-87d116eba3ee
+- Modification of Dynamic Linker Preload Shared Object - 717f82c2-7741-4f9b-85b8-d06aeb853f4f
+- Shared Object Created or Changed by Previously Unknown Process - aebaa51f-2a91-4f6a-850b-b601db2293f4
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id with maxspan=1m [process where
-event.type == "start" and process.name : ("cp", "rsync") and
-process.args : ("/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2",
-"/etc/ld.so.preload")] [file where event.action == "creation" and
-file.extension == "so"]
+[source, js]
 ----------------------------------
+sequence by process.entity_id with maxspan=1m
+[process where host.os.type == "linux" and event.type == "start" and process.name in ("cp", "rsync") and
+   process.args in (
+     "/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2", "/etc/ld.so.preload", "/lib64/ld-linux-x86-64.so.2",
+     "/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2", "/usr/lib64/ld-linux-x86-64.so.2"
+    )]
+[file where host.os.type == "linux" and event.action == "creation" and file.extension == "so"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,10 +186,7 @@ file.extension == "so"]
 ** Name: Hijack Execution Flow
 ** ID: T1574
 ** Reference URL: https://attack.mitre.org/techniques/T1574/
-
-[[dynamic-linker-copy-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Dynamic Linker Hijacking
+** ID: T1574.006
+** Reference URL: https://attack.mitre.org/techniques/T1574/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/ec2-ami-shared-with-another-account.asciidoc b/docs/detections/prebuilt-rules/rule-details/ec2-ami-shared-with-another-account.asciidoc
new file mode 100644
index 0000000000..865413477f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/ec2-ami-shared-with-another-account.asciidoc
@@ -0,0 +1,118 @@
+[[ec2-ami-shared-with-another-account]]
+=== EC2 AMI Shared with Another Account
+
+Identifies an AWS Amazon Machine Image (AMI) being shared with another AWS account. Adversaries with access may share an AMI with an external AWS account as a means of data exfiltration. AMIs can contain secrets, bash histories, code artifacts, and other sensitive data that adversaries may abuse if shared with unauthorized accounts. AMIs can be made publicly available accidentally as well.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-aws.cloudtrail-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html
+* https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-explicit.html
+* https://stratus-red-team.cloud/attack-techniques/AWS/aws.exfiltration.ec2-share-ami/
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: AWS EC2
+* Use Case: Threat Detection
+* Tactic: Exfiltration
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+*Triage and Analysis*
+
+
+
+*Investigating EC2 AMI Shared with Another Account*
+
+
+This rule identifies when an Amazon Machine Image (AMI) is shared with another AWS account. While sharing AMIs is a common practice, adversaries may exploit this feature to exfiltrate data by sharing AMIs with external accounts under their control.
+
+
+*Possible Investigation Steps*
+
+
+- **Review the Sharing Event**: Identify the AMI involved and review the event details in AWS CloudTrail. Look for `ModifyImageAttribute` actions where the AMI attributes were changed to include additional user accounts.
+    - **Request and Response Parameters**: Check the `aws.cloudtrail.request_parameters` and `aws.response.response_elements` fields in the CloudTrail event to identify the AMI ID and the user ID of the account with which the AMI was shared.
+- **Verify the Shared AMI**: Check the AMI that was shared and its contents to determine the sensitivity of the data stored within it.
+- **Contextualize with Recent Changes**: Compare this sharing event against recent changes in AMI configurations and deployments. Look for any other recent permissions changes or unusual administrative actions.
+- **Validate External Account**: Examine the AWS account to which the AMI was shared. Determine whether this account is known and previously authorized to access such resources.
+- **Interview Relevant Personnel**: If the share was initiated by a user, verify the intent and authorization for this action with the person or team responsible for managing AMI deployments.
+- **Audit Related Security Policies**: Check the security policies governing AMI sharing within your organization to ensure they are being followed and are adequate to prevent unauthorized sharing.
+
+
+*False Positive Analysis*
+
+
+- **Legitimate Sharing Practices**: AMI sharing is a common and legitimate practice for collaboration and resource management in AWS. Always verify that the sharing activity was unauthorized before escalating.
+- **Automation Tools**: Some organizations use automation tools for AMI management which might programmatically share AMIs. Verify if such tools are in operation and whether their actions are responsible for the observed behavior.
+
+
+*Response and Remediation*
+
+
+- **Review and Revoke Unauthorized Shares**: If the share is found to be unauthorized, immediately revoke the shared permissions from the AMI.
+- **Enhance Monitoring of Shared AMIs**: Implement monitoring to track changes to shared AMIs and alert on unauthorized access patterns.
+- **Incident Response**: If malicious intent is confirmed, consider it a data breach incident and initiate the incident response protocol. This includes further investigation, containment, and recovery.
+- **Policy Update**: Review and possibly update your organization’s policies on AMI sharing to tighten control and prevent unauthorized access.
+- **Educate Users**: Conduct training sessions for users involved in managing AMIs to reinforce best practices and organizational policies regarding AMI sharing.
+
+
+*Additional Information*
+
+
+For more information on managing and sharing AMIs, refer to the https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html[Amazon EC2 User Guide on AMIs] and https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-explicit.html[Sharing AMIs]. Additionally, explore adversarial techniques related to data exfiltration via AMI sharing as documented by Stratus Red Team https://stratus-red-team.cloud/attack-techniques/AWS/aws.exfiltration.ec2-share-ami/[here].
+
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset: "aws.cloudtrail" and event.provider: "ec2.amazonaws.com"
+    and event.action: ModifyImageAttribute and event.outcome: success
+    and aws.cloudtrail.request_parameters: (*imageId* and *add* and *userId*)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Transfer Data to Cloud Account
+** ID: T1537
+** Reference URL: https://attack.mitre.org/techniques/T1537/
diff --git a/docs/detections/prebuilt-rules/rule-details/eggshell-backdoor-execution.asciidoc b/docs/detections/prebuilt-rules/rule-details/eggshell-backdoor-execution.asciidoc
index 002d226c3e..eb8f1a15a7 100644
--- a/docs/detections/prebuilt-rules/rule-details/eggshell-backdoor-execution.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/eggshell-backdoor-execution.asciidoc
@@ -5,7 +5,7 @@ Identifies the execution of and EggShell Backdoor. EggShell is a known post expl
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,45 +14,42 @@ Identifies the execution of and EggShell Backdoor. EggShell is a known post expl
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/neoneggplant/EggShell
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* macOS
-* Threat Detection
-* Execution
-
-*Version*: 100 (<<eggshell-backdoor-execution-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:espl and process.args:eyJkZWJ1ZyI6*
+[source, js]
 ----------------------------------
+event.category:process and event.type:(process_started or start) and process.name:espl and process.args:eyJkZWJ1ZyI6*
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,13 +61,7 @@ process.name:espl and process.args:eyJkZWJ1ZyI6*
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[eggshell-backdoor-execution-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Python
+** ID: T1059.006
+** Reference URL: https://attack.mitre.org/techniques/T1059/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/elastic-agent-service-terminated.asciidoc b/docs/detections/prebuilt-rules/rule-details/elastic-agent-service-terminated.asciidoc
index 57e2b9e1ae..2b61bcd98d 100644
--- a/docs/detections/prebuilt-rules/rule-details/elastic-agent-service-terminated.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/elastic-agent-service-terminated.asciidoc
@@ -5,69 +5,82 @@ Identifies the Elastic endpoint agent has stopped and is no longer running on th
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-*
+* logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Windows
-* macOS
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<elastic-agent-service-terminated-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: Windows
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 8.3.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where /* net, sc or wmic stopping or deleting Elastic Agent on
-Windows */ (event.type == "start" and process.name : ("net.exe",
-"sc.exe", "wmic.exe","powershell.exe","taskkill.exe","PsKill.exe","Pro
-cessHacker.exe") and process.args : ("stopservice","uninstall",
-"stop", "disabled","Stop-Process","terminate","suspend") and
-process.args : ("elasticendpoint", "Elastic Agent","elastic-
-agent","elastic-endpoint")) or /* service or systemctl used to stop
-Elastic Agent on Linux */ (event.type == "end" and (process.name :
-("systemctl", "service") and process.args : "elastic-agent" and
-process.args : "stop") or /* Unload Elastic Agent extension on
-MacOS */ (process.name : "kextunload" and process.args :
-"com.apple.iokit.EndpointSecurity" and event.action : "end"))
+[source, js]
 ----------------------------------
+process where
+/* net, sc or wmic stopping or deleting Elastic Agent on Windows */
+(event.type == "start" and
+  process.name : ("net.exe", "sc.exe", "wmic.exe","powershell.exe","taskkill.exe","PsKill.exe","ProcessHacker.exe") and
+  process.args : ("stopservice","uninstall", "stop", "disabled","Stop-Process","terminate","suspend") and
+  process.args : ("elasticendpoint", "Elastic Agent","elastic-agent","elastic-endpoint"))
+or
+/* service or systemctl used to stop Elastic Agent on Linux */
+(event.type == "end" and
+  (process.name : ("systemctl", "service") and
+    process.args : "elastic-agent" and
+    process.args : "stop")
+  or
+  /* pkill , killall used to stop Elastic Agent on Linux */
+  ( event.type == "end" and process.name : ("pkill", "killall") and process.args: "elastic-agent")
+  or
+  /* Unload Elastic Agent extension on MacOS */
+  (process.name : "kextunload" and
+    process.args : "com.apple.iokit.EndpointSecurity" and
+    event.action : "end"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,45 +92,7 @@ MacOS */ (process.name : "kextunload" and process.args :
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[elastic-agent-service-terminated-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where /* net, sc or wmic stopping or deleting Elastic Agent on
-Windows */ (event.type == "start" and process.name : ("net.exe",
-"sc.exe", "wmic.exe","powershell.exe","taskkill.exe","PsKill.exe","Pro
-cessHacker.exe") and process.args : ("stopservice","uninstall",
-"stop", "disabled","Stop-Process","terminate","suspend") and
-process.args : ("elasticendpoint", "Elastic Agent","elastic-
-agent","elastic-endpoint")) or /* service or systemctl used to stop
-Elastic Agent on Linux */ (event.type == "end" and (process.name :
-("systemctl", "service") and process.args : "elastic-agent" and
-process.args : "stop") or /* Unload Elastic Agent extension on
-MacOS */ (process.name : "kextunload" and process.args :
-"com.apple.iokit.EndpointSecurity" and event.action : "end"))
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where /* net, sc or wmic stopping or deleting Elastic Agent on
-Windows */ (event.type == "start" and process.name : ("net.exe",
-"sc.exe", "wmic.exe","powershell.exe","taskkill.exe","PsKill.exe","Pro
-cessHacker.exe") and process.args : ("stopservice","uninstall",
-"stop", "disabled","Stop-Process","terminate","suspend") and
-process.args : ("elasticendpoint", "Elastic Agent","elastic-
-agent","elastic-endpoint")) or /* service or systemctl used to stop
-Elastic Agent on Linux */ (event.type == "end" and (process.name :
-("systemctl","service") and process.args : ("elastic-agent",
-"stop")) or /* Unload Elastic Agent extension on MacOS */
-(process.name : "kextunload" and process.args :
-"com.apple.iokit.EndpointSecurity" and event.action : "end"))
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/emond-rules-creation-or-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/emond-rules-creation-or-modification.asciidoc
index ca60317ebe..76c3c7dcf3 100644
--- a/docs/detections/prebuilt-rules/rule-details/emond-rules-creation-or-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/emond-rules-creation-or-modification.asciidoc
@@ -5,64 +5,88 @@ Identifies the creation or modification of the Event Monitor Daemon (emond) rule
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.xorrior.com/emond-persistence/
 * https://www.sentinelone.com/blog/how-malware-persists-on-macos/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<emond-rules-creation-or-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This rule requires data coming in from Elastic Defend.
 
-----------------------------------
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.path :
-("/private/etc/emond.d/rules/*.plist", "/etc/emon.d/rules/*.plist",
-"/private/var/db/emondClients/*")
+[source, js]
 ----------------------------------
+file where host.os.type == "macos" and event.type != "deletion" and
+ file.path : ("/private/etc/emond.d/rules/*.plist", "/etc/emon.d/rules/*.plist", "/private/var/db/emondClients/*")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,25 +98,7 @@ file where event.type != "deletion" and file.path :
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[emond-rules-creation-or-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.3.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type != "deletion" and file.path :
-("/private/etc/emond.d/rules/*.plist", "/etc/emon.d/rules/*.plist")
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Emond
+** ID: T1546.014
+** Reference URL: https://attack.mitre.org/techniques/T1546/014/
diff --git a/docs/detections/prebuilt-rules/rule-details/enable-host-network-discovery-via-netsh.asciidoc b/docs/detections/prebuilt-rules/rule-details/enable-host-network-discovery-via-netsh.asciidoc
index a3495d4534..e71fca5f02 100644
--- a/docs/detections/prebuilt-rules/rule-details/enable-host-network-discovery-via-netsh.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/enable-host-network-discovery-via-netsh.asciidoc
@@ -5,104 +5,114 @@ Identifies use of the netsh.exe program to enable host discovery via the network
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<enable-host-network-discovery-via-netsh-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Host Windows Firewall planned system administration changes.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Enable Host Network Discovery via Netsh
+*Triage and analysis*
+
+
+
+*Investigating Enable Host Network Discovery via Netsh*
+
 
-The Windows Defender Firewall is a native component that provides host-based, two-way network traffic filtering for a
-device and blocks unauthorized network traffic flowing into or out of the local device.
+The Windows Defender Firewall is a native component that provides host-based, two-way network traffic filtering for a device and blocks unauthorized network traffic flowing into or out of the local device.
 
-Attackers can enable Network Discovery on the Windows firewall to find other systems present in the same network. Systems
-with this setting enabled will communicate with other systems using broadcast messages, which can be used to identify
-targets for lateral movement. This rule looks for the setup of this setting using the netsh utility.
+Attackers can enable Network Discovery on the Windows firewall to find other systems present in the same network. Systems with this setting enabled will communicate with other systems using broadcast messages, which can be used to identify targets for lateral movement. This rule looks for the setup of this setting using the netsh utility.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Inspect the host for suspicious or abnormal behavior in the alert timeframe.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity
-and there are justifications for this configuration.
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the Administrator is aware of the activity and there are justifications for this configuration.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Disable Network Discovery:
     - Using netsh: `netsh advfirewall firewall set rule group="Network Discovery" new enable=No`
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "netsh.exe" and
-process.args : ("firewall", "advfirewall") and process.args :
-"group=Network Discovery" and process.args : "enable=Yes"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+process.name : "netsh.exe" and
+process.args : ("firewall", "advfirewall") and process.args : "group=Network Discovery" and process.args : "enable=Yes"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -114,25 +124,7 @@ process.args : ("firewall", "advfirewall") and process.args :
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[enable-host-network-discovery-via-netsh-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify System Firewall
+** ID: T1562.004
+** Reference URL: https://attack.mitre.org/techniques/T1562/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/encoded-executable-stored-in-the-registry.asciidoc b/docs/detections/prebuilt-rules/rule-details/encoded-executable-stored-in-the-registry.asciidoc
index 83d8c7b04c..1265231cb6 100644
--- a/docs/detections/prebuilt-rules/rule-details/encoded-executable-stored-in-the-registry.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/encoded-executable-stored-in-the-registry.asciidoc
@@ -5,50 +5,53 @@ Identifies registry write modifications to hide an encoded portable executable.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
 * endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 101 (<<encoded-executable-stored-in-the-registry-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where /* update here with encoding combinations */
-registry.data.strings : "TVqQAAMAAAAEAAAA*"
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and
+/* update here with encoding combinations */
+ registry.data.strings : "TVqQAAMAAAAEAAAA*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -57,31 +60,10 @@ registry.data.strings : "TVqQAAMAAAAEAAAA*"
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
 * Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
+* Technique:
 ** Name: Deobfuscate/Decode Files or Information
 ** ID: T1140
 ** Reference URL: https://attack.mitre.org/techniques/T1140/
-
-[[encoded-executable-stored-in-the-registry-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/encrypting-files-with-winrar-or-7z.asciidoc b/docs/detections/prebuilt-rules/rule-details/encrypting-files-with-winrar-or-7z.asciidoc
index 2c6c852aa3..954b5a1420 100644
--- a/docs/detections/prebuilt-rules/rule-details/encrypting-files-with-winrar-or-7z.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/encrypting-files-with-winrar-or-7z.asciidoc
@@ -5,9 +5,9 @@ Identifies use of WinRar or 7z to create an encrypted files. Adversaries will of
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
@@ -16,102 +16,122 @@ Identifies use of WinRar or 7z to create an encrypted files. Adversaries will of
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.welivesecurity.com/2020/12/02/turla-crutch-keeping-back-door-open/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Collection
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<encrypting-files-with-winrar-or-7z-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Encrypting Files with WinRar or 7z
+*Triage and analysis*
 
-Attackers may compress and/or encrypt data collected before exfiltration. Compressing the data can help obfuscate the
-collected data and minimize the amount of data sent over the network. Encryption can be used to hide information that is
-being exfiltrated from detection or make exfiltration less apparent upon inspection by a defender.
+
+
+*Investigating Encrypting Files with WinRar or 7z*
+
+
+Attackers may compress and/or encrypt data collected before exfiltration. Compressing the data can help obfuscate the collected data and minimize the amount of data sent over the network. Encryption can be used to hide information that is being exfiltrated from detection or make exfiltration less apparent upon inspection by a defender.
 
 These steps are usually done in preparation for exfiltration, meaning the attack may be in its final stages.
 
-#### Possible investigation steps
 
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Retrieve the encrypted file.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Check if the password used in the encryption was included in the command line.
 - Decrypt the `.rar`/`.zip` and check if the information is sensitive.
-- If the password is not available, and the format is `.zip` or the option used in WinRAR is not the `-hp`, list the
-file names included in the encrypted file.
+- If the password is not available, and the format is `.zip` or the option used in WinRAR is not the `-hp`, list the file names included in the encrypted file.
 - Investigate if the file was transferred to an attacker-controlled server.
 
-### False positive analysis
 
-- Backup software can use these utilities. Check the `process.parent.executable` and
-`process.parent.command_line` fields to determine what triggered the encryption.
+*False positive analysis*
+
+
+- Backup software can use these utilities. Check the `process.parent.executable` and `process.parent.command_line` fields to determine what triggered the encryption.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Prioritize cases that involve personally identifiable information (PII) or other classified data.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and ((process.name:"rar.exe" or
-process.code_signature.subject_name == "win.rar GmbH" or
-process.pe.original_file_name == "Command line RAR") and
-process.args == "a" and process.args : ("-hp*", "-p*", "-dw", "-tb",
-"-ta", "/hp*", "/p*", "/dw", "/tb", "/ta")) or
-(process.pe.original_file_name in ("7z.exe", "7za.exe") and
-process.args == "a" and process.args : ("-p*", "-sdel")) /*
-uncomment if noisy for backup software related FPs */ /* not
-process.parent.executable : ("C:\\Program Files\\*.exe", "C:\\Program
-Files (x86)\\*.exe") */
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+(
+  (
+    (
+      process.name:"rar.exe" or ?process.code_signature.subject_name == "win.rar GmbH" or
+      ?process.pe.original_file_name == "Command line RAR"
+    ) and
+    process.args == "a" and process.args : ("-hp*", "-p*", "/hp*", "/p*")
+  ) or
+  (
+    ?process.pe.original_file_name in ("7z.exe", "7za.exe") and
+    process.args == "a" and process.args : "-p*"
+  )
+) and
+  not process.parent.executable : (
+        "C:\\Program Files\\*.exe",
+        "C:\\Program Files (x86)\\*.exe",
+        "?:\\ManageEngine\\*\\jre\\bin\\java.exe",
+        "?:\\Nox\\bin\\Nox.exe"
+      )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -123,45 +143,11 @@ Files (x86)\\*.exe") */
 ** Name: Archive Collected Data
 ** ID: T1560
 ** Reference URL: https://attack.mitre.org/techniques/T1560/
-
-[[encrypting-files-with-winrar-or-7z-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-((process.name:"rar.exe" or process.code_signature.subject_name ==
-"win.rar GmbH" or process.pe.original_file_name == "Command line
-RAR") and process.args == "a" and process.args : ("-hp*", "-p*",
-"-dw", "-tb", "-ta", "/hp*", "/p*", "/dw", "/tb", "/ta")) or
-(process.pe.original_file_name in ("7z.exe", "7za.exe") and
-process.args == "a" and process.args : ("-p*", "-sdel")) /*
-uncomment if noisy for backup software related FPs */ /* not
-process.parent.executable : ("C:\\Program Files\\*.exe", "C:\\Program
-Files (x86)\\*.exe") */
-----------------------------------
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Archive via Utility
+** ID: T1560.001
+** Reference URL: https://attack.mitre.org/techniques/T1560/001/
+* Technique:
+** Name: Data from Local System
+** ID: T1005
+** Reference URL: https://attack.mitre.org/techniques/T1005/
diff --git a/docs/detections/prebuilt-rules/rule-details/endpoint-security.asciidoc b/docs/detections/prebuilt-rules/rule-details/endpoint-security.asciidoc
index 2738bb404a..f6db54fa70 100644
--- a/docs/detections/prebuilt-rules/rule-details/endpoint-security.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/endpoint-security.asciidoc
@@ -5,7 +5,7 @@ Generates a detection alert each time an Elastic Endpoint Security alert is rece
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.alerts-*
 
@@ -13,47 +13,47 @@ Generates a detection alert each time an Elastic Endpoint Security alert is rece
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-10m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Endpoint Security
+*Tags*: 
 
-*Version*: 100 (<<endpoint-security-history, version history>>)
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
 
+==== Setup
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:(endpoint and not endgame)
-----------------------------------
 
 
-[[endpoint-security-history]]
-==== Rule version history
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
 
-Version 100 (8.5.0 release)::
-* Formatting only
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
 
-Version 4 (8.4.0 release)::
-* Formatting only
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
 
-Version 3 (7.12.0 release)::
-* Formatting only
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
 
-Version 2 (7.10.0 release)::
-* Rule name changed from: Elastic Endpoint Security
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and event.module:(endpoint and not endgame)
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/enumerating-domain-trusts-via-dsquery-exe.asciidoc b/docs/detections/prebuilt-rules/rule-details/enumerating-domain-trusts-via-dsquery-exe.asciidoc
new file mode 100644
index 0000000000..91daf0bbda
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/enumerating-domain-trusts-via-dsquery-exe.asciidoc
@@ -0,0 +1,121 @@
+[[enumerating-domain-trusts-via-dsquery-exe]]
+=== Enumerating Domain Trusts via DSQUERY.EXE
+
+Identifies the use of dsquery.exe for domain trust discovery purposes. Adversaries may use this command-line utility to enumerate trust relationships that may be used for Lateral Movement opportunities in Windows multi-domain forest environments.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc732952(v=ws.11)
+* https://posts.specterops.io/a-guide-to-attacking-domain-trusts-971e52cb2944
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Enumerating Domain Trusts via DSQUERY.EXE*
+
+
+Active Directory (AD) domain trusts define relationships between domains within a Windows AD environment. In this setup, a "trusting" domain permits users from a "trusted" domain to access resources. These trust relationships can be configurable as one-way, two-way, transitive, or non-transitive, enabling controlled access and resource sharing across domains.
+
+This rule identifies the usage of the `dsquery.exe` utility to enumerate domain trusts. Attackers can use this information to enable the next actions in a target environment, such as lateral movement.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Discovery activities are not inherently malicious if they occur in isolation and are done within the user business context (e.g., an administrator in this context). As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
+
+
+*Related rules*
+
+
+- Enumerating Domain Trusts via NLTEST.EXE - 84da2554-e12a-11ec-b896-f661ea17fbcd
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+    (process.name : "dsquery.exe" or ?process.pe.original_file_name: "dsquery.exe") and 
+    process.args : "*objectClass=trustedDomain*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Domain Trust Discovery
+** ID: T1482
+** Reference URL: https://attack.mitre.org/techniques/T1482/
+* Technique:
+** Name: Remote System Discovery
+** ID: T1018
+** Reference URL: https://attack.mitre.org/techniques/T1018/
diff --git a/docs/detections/prebuilt-rules/rule-details/enumerating-domain-trusts-via-nltest-exe.asciidoc b/docs/detections/prebuilt-rules/rule-details/enumerating-domain-trusts-via-nltest-exe.asciidoc
new file mode 100644
index 0000000000..a4ef8f7e03
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/enumerating-domain-trusts-via-nltest-exe.asciidoc
@@ -0,0 +1,126 @@
+[[enumerating-domain-trusts-via-nltest-exe]]
+=== Enumerating Domain Trusts via NLTEST.EXE
+
+Identifies the use of nltest.exe for domain trust discovery purposes. Adversaries may use this command-line utility to enumerate domain trusts and gain insight into trust relationships, as well as the state of Domain Controller (DC) replication in a Microsoft Windows NT Domain.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc731935(v=ws.11)
+* https://redcanary.com/blog/how-one-hospital-thwarted-a-ryuk-ransomware-outbreak/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 110
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Enumerating Domain Trusts via NLTEST.EXE*
+
+
+Active Directory (AD) domain trusts define relationships between domains within a Windows AD environment. In this setup, a "trusting" domain permits users from a "trusted" domain to access resources. These trust relationships can be configurable as one-way, two-way, transitive, or non-transitive, enabling controlled access and resource sharing across domains.
+
+This rule identifies the usage of the `nltest.exe` utility to enumerate domain trusts. Attackers can use this information to enable the next actions in a target environment, such as lateral movement.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Discovery activities are not inherently malicious if they occur in isolation and are done within the user business context (e.g., an administrator in this context). As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
+
+
+*Related rules*
+
+
+- Enumerating Domain Trusts via DSQUERY.EXE - 06a7a03c-c735-47a6-a313-51c354aef6c3
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+    process.name : "nltest.exe" and process.args : (
+        "/DCLIST:*", "/DCNAME:*", "/DSGET*",
+        "/LSAQUERYFTI:*", "/PARENTDOMAIN",
+        "/DOMAIN_TRUSTS", "/BDC_QUERY:*"
+        ) and 
+not process.parent.name : "PDQInventoryScanner.exe" and 
+not user.id in ("S-1-5-18", "S-1-5-19", "S-1-5-20")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Domain Trust Discovery
+** ID: T1482
+** Reference URL: https://attack.mitre.org/techniques/T1482/
+* Technique:
+** Name: Remote System Discovery
+** ID: T1018
+** Reference URL: https://attack.mitre.org/techniques/T1018/
diff --git a/docs/detections/prebuilt-rules/rule-details/enumeration-command-spawned-via-wmiprvse.asciidoc b/docs/detections/prebuilt-rules/rule-details/enumeration-command-spawned-via-wmiprvse.asciidoc
index c4519342df..daa58230f0 100644
--- a/docs/detections/prebuilt-rules/rule-details/enumeration-command-spawned-via-wmiprvse.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/enumeration-command-spawned-via-wmiprvse.asciidoc
@@ -5,67 +5,97 @@ Identifies native Windows host and network enumeration commands spawned by the W
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<enumeration-command-spawned-via-wmiprvse-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name: (
-"arp.exe", "dsquery.exe", "dsget.exe", "gpresult.exe",
-"hostname.exe", "ipconfig.exe", "nbtstat.exe", "net.exe",
-"net1.exe", "netsh.exe", "netstat.exe", "nltest.exe",
-"ping.exe", "qprocess.exe", "quser.exe", "qwinsta.exe",
-"reg.exe", "sc.exe", "systeminfo.exe", "tasklist.exe",
-"tracert.exe", "whoami.exe" ) and
-process.parent.name:"wmiprvse.exe"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.command_line != null and 
+  process.name:
+  (
+    "arp.exe",
+    "dsquery.exe",
+    "dsget.exe",
+    "gpresult.exe",
+    "hostname.exe",
+    "ipconfig.exe",
+    "nbtstat.exe",
+    "net.exe",
+    "net1.exe",
+    "netsh.exe",
+    "netstat.exe",
+    "nltest.exe",
+    "ping.exe",
+    "qprocess.exe",
+    "quser.exe",
+    "qwinsta.exe",
+    "reg.exe",
+    "sc.exe",
+    "systeminfo.exe",
+    "tasklist.exe",
+    "tracert.exe",
+    "whoami.exe"
+  ) and
+  process.parent.name:"wmiprvse.exe" and 
+  not (
+    process.name : "sc.exe" and process.args : "RemoteRegistry" and process.args : "start=" and 
+    process.args : ("demand", "disabled")
+  ) and
+  not process.args : "tenable_mw_scan"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,8 +107,6 @@ process.parent.name:"wmiprvse.exe"
 ** Name: Windows Management Instrumentation
 ** ID: T1047
 ** Reference URL: https://attack.mitre.org/techniques/T1047/
-
-
 * Tactic:
 ** Name: Discovery
 ** ID: TA0007
@@ -87,34 +115,23 @@ process.parent.name:"wmiprvse.exe"
 ** Name: Remote System Discovery
 ** ID: T1018
 ** Reference URL: https://attack.mitre.org/techniques/T1018/
-
-[[enumeration-command-spawned-via-wmiprvse-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name: ( "arp.exe", "dsquery.exe", "dsget.exe",
-"gpresult.exe", "hostname.exe", "ipconfig.exe",
-"nbtstat.exe", "net.exe", "net1.exe", "netsh.exe",
-"netstat.exe", "nltest.exe", "ping.exe", "qprocess.exe",
-"quser.exe", "qwinsta.exe", "reg.exe", "sc.exe",
-"systeminfo.exe", "tasklist.exe", "tracert.exe",
-"whoami.exe" ) and process.parent.name:"wmiprvse.exe"
-----------------------------------
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Formatting only
-
+* Technique:
+** Name: Account Discovery
+** ID: T1087
+** Reference URL: https://attack.mitre.org/techniques/T1087/
+* Technique:
+** Name: Software Discovery
+** ID: T1518
+** Reference URL: https://attack.mitre.org/techniques/T1518/
+* Technique:
+** Name: System Network Configuration Discovery
+** ID: T1016
+** Reference URL: https://attack.mitre.org/techniques/T1016/
+* Sub-technique:
+** Name: Internet Connection Discovery
+** ID: T1016.001
+** Reference URL: https://attack.mitre.org/techniques/T1016/001/
+* Technique:
+** Name: Process Discovery
+** ID: T1057
+** Reference URL: https://attack.mitre.org/techniques/T1057/
diff --git a/docs/detections/prebuilt-rules/rule-details/enumeration-of-administrator-accounts.asciidoc b/docs/detections/prebuilt-rules/rule-details/enumeration-of-administrator-accounts.asciidoc
index 6c458e7723..62018e3b6b 100644
--- a/docs/detections/prebuilt-rules/rule-details/enumeration-of-administrator-accounts.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/enumeration-of-administrator-accounts.asciidoc
@@ -5,110 +5,130 @@ Identifies instances of lower privilege accounts enumerating Administrator accou
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<enumeration-of-administrator-accounts-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Enumeration of Administrator Accounts
+*Triage and analysis*
+
+
 
-After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps.
-This can happen by running commands to enumerate network resources, users, connections, files, and installed security
-software.
+*Investigating Enumeration of Administrator Accounts*
 
-This rule looks for the execution of the `net` and `wmic` utilities to enumerate administrator-related users or groups
-in the domain and local machine scope. Attackers can use this information to plan their next steps of the attack, such
-as mapping targets for credential compromise and other post-exploitation activities.
 
-#### Possible investigation steps
+After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+This rule looks for the execution of the `net` and `wmic` utilities to enumerate administrator-related users or groups in the domain and local machine scope. Attackers can use this information to plan their next steps of the attack, such as mapping targets for credential compromise and other post-exploitation activities.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+
 
-### False positive analysis
+*False positive analysis*
 
-- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify
-suspicious activity related to the user or host, such alerts can be dismissed.
 
-### Related rules
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
+
+
+*Related rules*
+
 
 - AdFind Command Activity - eda499b8-a073-4e35-9733-22ec71f57f3a
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (((process.name : "net.exe"
-or process.pe.original_file_name == "net.exe") or ((process.name :
-"net1.exe" or process.pe.original_file_name == "net1.exe") and
-not process.parent.name : "net.exe")) and process.args : ("group",
-"user", "localgroup") and process.args : ("admin", "Domain Admins",
-"Remote Desktop Users", "Enterprise Admins", "Organization
-Management") and not process.args : "/add") or
-((process.name : "wmic.exe" or process.pe.original_file_name ==
-"wmic.exe") and process.args : ("group", "useraccount"))
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+(
+  (
+    (
+      (process.name : "net.exe" or ?process.pe.original_file_name == "net.exe") or
+      ((process.name : "net1.exe" or ?process.pe.original_file_name == "net1.exe") and not process.parent.name : "net.exe")
+    ) and
+    process.args : ("group", "user", "localgroup") and
+    process.args : ("*admin*", "Domain Admins", "Remote Desktop Users", "Enterprise Admins", "Organization Management")
+    and not process.args : ("/add", "/delete")
+  ) or
+  (
+    (process.name : "wmic.exe" or ?process.pe.original_file_name == "wmic.exe") and
+    process.args : ("group", "useraccount")
+  )
+) and not user.id : ("S-1-5-18", "S-1-5-19", "S-1-5-20")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -120,45 +140,23 @@ Management") and not process.args : "/add") or
 ** Name: Permission Groups Discovery
 ** ID: T1069
 ** Reference URL: https://attack.mitre.org/techniques/T1069/
-
-[[enumeration-of-administrator-accounts-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(((process.name : "net.exe" or process.pe.original_file_name ==
-"net.exe") or ((process.name : "net1.exe" or
-process.pe.original_file_name == "net1.exe") and not
-process.parent.name : "net.exe")) and process.args : ("group",
-"user", "localgroup") and process.args : ("admin", "Domain Admins",
-"Remote Desktop Users", "Enterprise Admins", "Organization
-Management") and not process.args : "/add") or
-((process.name : "wmic.exe" or process.pe.original_file_name ==
-"wmic.exe") and process.args : ("group", "useraccount"))
-----------------------------------
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Local Groups
+** ID: T1069.001
+** Reference URL: https://attack.mitre.org/techniques/T1069/001/
+* Sub-technique:
+** Name: Domain Groups
+** ID: T1069.002
+** Reference URL: https://attack.mitre.org/techniques/T1069/002/
+* Technique:
+** Name: Account Discovery
+** ID: T1087
+** Reference URL: https://attack.mitre.org/techniques/T1087/
+* Sub-technique:
+** Name: Local Account
+** ID: T1087.001
+** Reference URL: https://attack.mitre.org/techniques/T1087/001/
+* Sub-technique:
+** Name: Domain Account
+** ID: T1087.002
+** Reference URL: https://attack.mitre.org/techniques/T1087/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/enumeration-of-kernel-modules-via-proc.asciidoc b/docs/detections/prebuilt-rules/rule-details/enumeration-of-kernel-modules-via-proc.asciidoc
new file mode 100644
index 0000000000..65a8bd816e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/enumeration-of-kernel-modules-via-proc.asciidoc
@@ -0,0 +1,84 @@
+[[enumeration-of-kernel-modules-via-proc]]
+=== Enumeration of Kernel Modules via Proc
+
+Loadable Kernel Modules (or LKMs) are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. This identifies attempts to enumerate information about a kernel module using the /proc/modules filesystem. This filesystem is used by utilities such as lsmod and kmod to list the available kernel modules.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+
+*Version*: 106
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires the use of the `auditd_manager` integration. `Auditd_manager` is a tool designed to simplify and enhance the management of the audit subsystem in Linux systems. It provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system. The following steps should be executed in order to install and deploy `auditd_manager` on a Linux system.
+```
+Kibana -->
+Management -->
+Integrations -->
+Auditd Manager -->
+Add Auditd Manager
+```
+`Auditd_manager` subscribes to the kernel and receives events as they occur without any additional configuration. However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+For this detection rule to trigger, the following additional audit rules are required to be added to the integration:
+```
+-w /proc/ -p r -k audit_proc
+```
+Add the newly installed `auditd manager` to an agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.category:file and event.action:"opened-file" and file.path:"/proc/modules" and
+not process.name:(grep or python* or chef-client)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/enumeration-of-kernel-modules.asciidoc b/docs/detections/prebuilt-rules/rule-details/enumeration-of-kernel-modules.asciidoc
index 0c761e887e..a89fb609ec 100644
--- a/docs/detections/prebuilt-rules/rule-details/enumeration-of-kernel-modules.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/enumeration-of-kernel-modules.asciidoc
@@ -3,95 +3,102 @@
 
 Loadable Kernel Modules (or LKMs) are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. This identifies attempts to enumerate information about a kernel module.
 
-*Rule type*: query
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Discovery
+*Tags*: 
 
-*Version*: 100 (<<enumeration-of-kernel-modules-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
 
-*Added ({stack} release)*: 7.8.0
+*Version*: 209
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Security tools and device drivers may run these programs in order to enumerate kernel modules. Use of these programs by ordinary users is uncommon. These can be exempted by process name or username.
+==== Setup
 
-==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.args:(kmod and list and sudo or sudo and (depmod or lsmod or
-modinfo))
-----------------------------------
+*Setup*
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+This rule requires data coming in from Elastic Defend.
 
-* Tactic:
-** Name: Discovery
-** ID: TA0007
-** Reference URL: https://attack.mitre.org/tactics/TA0007/
-* Technique:
-** Name: System Information Discovery
-** ID: T1082
-** Reference URL: https://attack.mitre.org/techniques/T1082/
 
-[[enumeration-of-kernel-modules-history]]
-==== Rule version history
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 7 (8.4.0 release)::
-* Formatting only
+*Prerequisite Requirements:*
 
-Version 6 (7.12.0 release)::
-* Formatting only
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 5 (7.11.2 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
 
-Version 3 (7.9.1 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:executed and process.args:(kmod and list and sudo or sudo
-and (depmod or lsmod or modinfo))
+event.category:process and host.os.type:linux and event.type:start and event.action:(exec or exec_event) and (
+ (process.name:(lsmod or modinfo)) or 
+ (process.name:kmod and process.args:list) or 
+ (process.name:depmod and process.args:(--all or -a))
+) and not process.parent.name:(mkinitramfs or cryptroot or framebuffer or dracut or jem or thin-provisioning-tools
+or readykernel or lvm2 or vz-start or iscsi or mdadm or ovalprobes or bcache or plymouth or dkms or overlayroot or 
+weak-modules or zfs)
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/enumeration-of-privileged-local-groups-membership.asciidoc b/docs/detections/prebuilt-rules/rule-details/enumeration-of-privileged-local-groups-membership.asciidoc
index 989961f6b4..3a8a1803e0 100644
--- a/docs/detections/prebuilt-rules/rule-details/enumeration-of-privileged-local-groups-membership.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/enumeration-of-privileged-local-groups-membership.asciidoc
@@ -3,109 +3,112 @@
 
 Identifies instances of an unusual process enumerating built-in Windows privileged local groups membership like Administrators or Remote Desktop users.
 
-*Rule type*: eql
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<enumeration-of-privileged-local-groups-membership-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Resources: Investigation Guide
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 311
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Enumeration of Privileged Local Groups Membership
+*Triage and analysis*
+
 
-After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps.
-This can happen by running commands to enumerate network resources, users, connections, files, and installed security
-software.
 
-This rule looks for the enumeration of privileged local groups' membership by suspicious processes, and excludes known
-legitimate utilities and programs installed. Attackers can use this information to decide the next steps of the attack,
-such as mapping targets for credential compromise and other post-exploitation activities.
+*Investigating Enumeration of Privileged Local Groups Membership*
+
+
+After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
+
+This rule looks for the enumeration of privileged local groups' membership by suspicious processes, and excludes known legitimate utilities and programs installed. Attackers can use this information to decide the next steps of the attack, such as mapping targets for credential compromise and other post-exploitation activities.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the process, host and user involved on the event.
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
+
+
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and command line conditions.
 
-### False positive analysis
 
-- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify
-suspicious activity related to the user or host, such alerts can be dismissed.
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination
-of user and command line conditions.
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
 
 The 'Audit Security Group Management' audit policy must be configured (Success).
-Steps to implement the logging policy with with Advanced Audit Configuration:
+Steps to implement the logging policy with Advanced Audit Configuration:
 
 ```
 Computer Configuration >
@@ -118,60 +121,63 @@ Account Management >
 Audit Security Group Management (Success)
 ```
 
-Microsoft introduced the [event used](https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4799) in this detection rule on Windows 10 and Windows Server 2016 or later operating systems.
+Microsoft introduced the https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4799[event used] in this detection rule on Windows 10 and Windows Server 2016 or later operating systems.
 
-If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define `event.ingested` and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate `event.ingested` to @timestamp for this rule to work.
-----------------------------------
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-iam where event.action == "user-member-enumerated" and /* excluding
-machine account */ not winlog.event_data.SubjectUserName: ("*$",
-"LOCAL SERVICE", "NETWORK SERVICE") and /* noisy and usual legit
-processes excluded */ not winlog.event_data.CallerProcessName:
-("-", "?:\\Windows\\System32\\VSSVC.exe",
-"?:\\Windows\\System32\\SearchIndexer.exe",
-"?:\\Windows\\System32\\CompatTelRunner.exe",
-"?:\\Windows\\System32\\oobe\\msoobe.exe",
-"?:\\Windows\\System32\\net1.exe",
-"?:\\Windows\\System32\\svchost.exe",
-"?:\\Windows\\System32\\Netplwiz.exe",
-"?:\\Windows\\System32\\msiexec.exe",
-"?:\\Windows\\SysWOW64\\msiexec.exe",
-"?:\\Windows\\System32\\CloudExperienceHostBroker.exe",
-"?:\\Windows\\System32\\wbem\\WmiPrvSE.exe",
-"?:\\Windows\\System32\\SrTasks.exe",
-"?:\\Windows\\System32\\lsass.exe",
-"?:\\Windows\\System32\\diskshadow.exe",
-"?:\\Windows\\System32\\dfsrs.exe", "?:\\Program
-Files\\*.exe", "?:\\Program Files (x86)\\*.exe",
-"?:\\WindowsAzure\\*\\WaAppAgent.exe",
-"?:\\Windows\\System32\\vssadmin.exe",
-"?:\\Windows\\VeeamVssSupport\\VeeamGuestHelper.exe",
-"?:\\Windows\\System32\\dllhost.exe",
-"?:\\Windows\\System32\\mmc.exe",
-"?:\\Windows\\System32\\SettingSyncHost.exe",
-"?:\\Windows\\ImmersiveControlPanel\\SystemSettings.exe",
-"?:\\Windows\\System32\\SystemSettingsAdminFlows.exe",
-"?:\\Windows\\Temp\\rubrik_vmware???\\snaptool.exe",
-"?:\\Windows\\System32\\inetsrv\\w3wp.exe",
-"?:\\$WINDOWS.~BT\\Sources\\*.exe",
-"?:\\Windows\\System32\\wsmprovhost.exe",
-"?:\\Windows\\System32\\spool\\drivers\\x64\\3\\x3jobt3?.exe",
-"?:\\Windows\\System32\\mstsc.exe",
-"?:\\Windows\\System32\\esentutl.exe",
-"?:\\Windows\\System32\\RecoveryDrive.exe",
-"?:\\Windows\\System32\\SystemPropertiesComputerName.exe") and /*
-privileged local groups */
-(group.name:("admin*","RemoteDesktopUsers") or
-winlog.event_data.TargetSid:("S-1-5-32-544","S-1-5-32-555"))
+[source, js]
 ----------------------------------
+host.os.type:windows and event.category:iam and event.action:user-member-enumerated and 
+  (
+    group.name:(*Admin* or "RemoteDesktopUsers") or
+    winlog.event_data.TargetSid:("S-1-5-32-544" or "S-1-5-32-555")
+  ) and 
+  not (
+    winlog.event_data.SubjectUserName: *$ or
+    winlog.event_data.SubjectUserSid: ("S-1-5-19" or "S-1-5-20") or 
+    winlog.event_data.CallerProcessName:("-" or 
+                                       C\:\\Windows\\System32\\VSSVC.exe or 
+                                       C\:\\Windows\\System32\\SearchIndexer.exe or 
+                                       C\:\\Windows\\System32\\CompatTelRunner.exe or 
+                                       C\:\\Windows\\System32\\oobe\\msoobe.exe or
+                                       C\:\\Windows\\System32\\net1.exe or 
+                                       C\:\\Windows\\System32\\svchost.exe or 
+                                       C\:\\Windows\\System32\\Netplwiz.exe or 
+                                       C\:\\Windows\\System32\\msiexec.exe or
+                                       C\:\\Windows\\System32\\CloudExperienceHostBroker.exe or
+                                       C\:\\Windows\\System32\\RuntimeBroker.exe or
+                                       C\:\\Windows\\System32\\wbem\\WmiPrvSE.exe or
+                                       C\:\\Windows\\System32\\SrTasks.exe or
+                                       C\:\\Windows\\System32\\diskshadow.exe or
+                                       C\:\\Windows\\System32\\dfsrs.exe or
+                                       C\:\\Windows\\System32\\vssadmin.exe or
+                                       C\:\\Windows\\System32\\dllhost.exe or
+                                       C\:\\Windows\\System32\\mmc.exe or
+                                       C\:\\Windows\\System32\\SettingSyncHost.exe or
+                                       C\:\\Windows\\System32\\inetsrv\\w3wp.exe or
+                                       C\:\\Windows\\System32\\wsmprovhost.exe or
+                                       C\:\\Windows\\System32\\mstsc.exe or
+                                       C\:\\Windows\\System32\\esentutl.exe or
+                                       C\:\\Windows\\System32\\RecoveryDrive.exe or
+                                       C\:\\Windows\\System32\\SystemPropertiesComputerName.exe or
+                                       C\:\\Windows\\SysWOW64\\msiexec.exe or
+                                       C\:\\Windows\\ImmersiveControlPanel\\SystemSettings.exe or
+                                       C\:\\Windows\\Temp\\rubrik_vmware*\\snaptool.exe or
+                                       C\:\\Windows\\VeeamVssSupport\\VeeamGuestHelper.exe or
+                                       C\:\\WindowsAzure\\*WaAppAgent.exe or
+                                       C\:\\$WINDOWS.~BT\\Sources\\*.exe
+                                      )
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -183,50 +189,7 @@ winlog.event_data.TargetSid:("S-1-5-32-544","S-1-5-32-555"))
 ** Name: Permission Groups Discovery
 ** ID: T1069
 ** Reference URL: https://attack.mitre.org/techniques/T1069/
-
-[[enumeration-of-privileged-local-groups-membership-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-iam where event.action == "user-member-enumerated" and /* noisy and
-usual legit processes excluded */ not
-winlog.event_data.CallerProcessName:
-("?:\\Windows\\System32\\VSSVC.exe",
-"?:\\Windows\\System32\\SearchIndexer.exe",
-"?:\\Windows\\System32\\CompatTelRunner.exe",
-"?:\\Windows\\System32\\oobe\\msoobe.exe",
-"?:\\Windows\\System32\\net1.exe",
-"?:\\Windows\\System32\\svchost.exe",
-"?:\\Windows\\System32\\Netplwiz.exe",
-"?:\\Windows\\System32\\msiexec.exe",
-"?:\\Windows\\System32\\CloudExperienceHostBroker.exe",
-"?:\\Windows\\System32\\wbem\\WmiPrvSE.exe",
-"?:\\Windows\\System32\\SrTasks.exe",
-"?:\\Windows\\System32\\lsass.exe",
-"?:\\Windows\\System32\\diskshadow.exe",
-"?:\\Windows\\System32\\dfsrs.exe", "?:\\Program
-Files\\*.exe", "?:\\Program Files (x86)\\*.exe") and
-/* privileged local groups */
-(group.name:("admin*","RemoteDesktopUsers") or
-winlog.event_data.TargetSid:("S-1-5-32-544","S-1-5-32-555"))
-----------------------------------
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Local Groups
+** ID: T1069.001
+** Reference URL: https://attack.mitre.org/techniques/T1069/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/enumeration-of-users-or-groups-via-built-in-commands.asciidoc b/docs/detections/prebuilt-rules/rule-details/enumeration-of-users-or-groups-via-built-in-commands.asciidoc
index 41dcb37ca1..727d21117e 100644
--- a/docs/detections/prebuilt-rules/rule-details/enumeration-of-users-or-groups-via-built-in-commands.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/enumeration-of-users-or-groups-via-built-in-commands.asciidoc
@@ -5,74 +5,103 @@ Identifies the execution of macOS built-in commands related to account or group
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* macOS
-* Threat Detection
-* Discovery
+*Tags*: 
 
-*Version*: 100 (<<enumeration-of-users-or-groups-via-built-in-commands-history, version history>>)
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and (
-process.name : ("ldapsearch", "dsmemberutil") or (process.name :
-"dscl" and process.args : ("read", "-read", "list", "-list",
-"ls", "search", "-search") and process.args : ("/Active
-Directory/*", "/Users*", "/Groups*")) ) and not
-process.parent.executable :
-("/Applications/NoMAD.app/Contents/MacOS/NoMAD",
-"/Applications/ZoomPresence.app/Contents/MacOS/ZoomPresence",
-"/Applications/Sourcetree.app/Contents/MacOS/Sourcetree",
-"/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfDaemon.
-app/Contents/MacOS/JamfDaemon", "/Applications/Jamf
-Connect.app/Contents/MacOS/Jamf Connect",
-"/usr/local/jamf/bin/jamf", "/Library/Application
-Support/AirWatch/hubd", "/opt/jc/bin/jumpcloud-agent",
-"/Applications/ESET Endpoint
-Antivirus.app/Contents/MacOS/esets_daemon", "/Applications/ESET
-Endpoint Security.app/Contents/MacOS/esets_daemon", "/Library/Pri
-vilegedHelperTools/com.fortinet.forticlient.uninstall_helper" )
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and
+  (
+    process.name : ("ldapsearch", "dsmemberutil") or
+    (process.name : "dscl" and
+      process.args : ("read", "-read", "list", "-list", "ls", "search", "-search") and
+      process.args : ("/Active Directory/*", "/Users*", "/Groups*"))
+	) and
+  ((process.Ext.effective_parent.executable : ("/Volumes/*", "/Applications/*") or process.parent.executable : ("/Volumes/*", "/Applications/*")) or
+   (process.Ext.effective_parent.name : ".*" or process.parent.name : ".*")) and
+  not process.Ext.effective_parent.executable : ("/Applications/QualysCloudAgent.app/Contents/MacOS/qualys-cloud-agent",
+                                                 "/Applications/Kaspersky Anti-Virus For Mac.app/Contents/MacOS/kavd.app/Contents/MacOS/kavd",
+                                                 "/Applications/ESET Endpoint Security.app/Contents/MacOS/esets_ctl",
+                                                 "/Applications/NordVPN.app/Contents/MacOS/NordVPN",
+                                                 "/Applications/Xcode.app/Contents/MacOS/Xcode",
+                                                 "/Applications/ESET Endpoint Security.app/Contents/Helpers/Uninstaller.app/Contents/MacOS/Uninstaller",
+                                                 "/Applications/Parallels Desktop.app/Contents/MacOS/prl_client_app",
+                                                 "/Applications/Zscaler/Zscaler.app/Contents/MacOS/Zscaler",
+                                                 "/Applications/com.avast.av.uninstaller.app/Contents/MacOS/com.avast.av.uninstaller",
+                                                 "/Applications/NoMAD.app/Contents/MacOS/NoMAD",
+                                                 "/Applications/ESET Management Agent.app/Contents/MacOS/ERAAgent")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,62 +113,15 @@ vilegedHelperTools/com.fortinet.forticlient.uninstall_helper" )
 ** Name: Permission Groups Discovery
 ** ID: T1069
 ** Reference URL: https://attack.mitre.org/techniques/T1069/
-
-[[enumeration-of-users-or-groups-via-built-in-commands-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and not
-process.parent.executable :
-("/Applications/NoMAD.app/Contents/MacOS/NoMAD",
-"/Applications/ZoomPresence.app/Contents/MacOS/ZoomPresence",
-"/Applications/Sourcetree.app/Contents/MacOS/Sourcetree",
-"/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfDaemon.
-app/Contents/MacOS/JamfDaemon", "/Applications/Jamf
-Connect.app/Contents/MacOS/Jamf Connect",
-"/usr/local/jamf/bin/jamf" ) and process.name : ("ldapsearch",
-"dsmemberutil") or (process.name : "dscl" and process.args :
-("read", "-read", "list", "-list", "ls", "search", "-search") and
-process.args : ("/Active Directory/*", "/Users*", "/Groups*"))
-----------------------------------
-
-Version 3 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and not
-process.parent.executable :
-("/Applications/NoMAD.app/Contents/MacOS/NoMAD",
-"/Applications/ZoomPresence.app/Contents/MacOS/ZoomPresence",
-"/Applications/Sourcetree.app/Contents/MacOS/Sourcetree",
-"/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfDaemon.
-app/Contents/MacOS/JamfDaemon", "/usr/local/jamf/bin/jamf" )
-and process.name : ("ldapsearch", "dsmemberutil") or
-(process.name : "dscl" and process.args : ("read", "-read",
-"list", "-list", "ls", "search", "-search") and process.args :
-("/Active Directory/*", "/Users*", "/Groups*"))
-----------------------------------
-
-Version 2 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and not
-process.parent.executable :
-("/Applications/NoMAD.app/Contents/MacOS/NoMAD",
-"/Applications/ZoomPresence.app/Contents/MacOS/ZoomPresence") and
-process.name : ("ldapsearch", "dsmemberutil") or (process.name :
-"dscl" and process.args : ("read", "-read", "list", "-list",
-"ls", "search", "-search") and process.args : ("/Active
-Directory/*", "/Users*", "/Groups*"))
-----------------------------------
-
+* Sub-technique:
+** Name: Local Groups
+** ID: T1069.001
+** Reference URL: https://attack.mitre.org/techniques/T1069/001/
+* Technique:
+** Name: Account Discovery
+** ID: T1087
+** Reference URL: https://attack.mitre.org/techniques/T1087/
+* Sub-technique:
+** Name: Local Account
+** ID: T1087.001
+** Reference URL: https://attack.mitre.org/techniques/T1087/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/esxi-discovery-via-find.asciidoc b/docs/detections/prebuilt-rules/rule-details/esxi-discovery-via-find.asciidoc
new file mode 100644
index 0000000000..0f00097488
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/esxi-discovery-via-find.asciidoc
@@ -0,0 +1,104 @@
+[[esxi-discovery-via-find]]
+=== ESXI Discovery via Find
+
+Identifies instances where the 'find' command is started on a Linux system with arguments targeting specific VM-related paths, such as "/etc/vmware/", "/usr/lib/vmware/", or "/vmfs/*". These paths are associated with VMware virtualization software, and their presence in the find command arguments may indicate that a threat actor is attempting to search for, analyze, or manipulate VM-related files and configurations on the system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.bleepingcomputer.com/news/security/massive-esxiargs-ransomware-attack-targets-vmware-esxi-servers-worldwide/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "find" and process.args : ("/etc/vmware/*", "/usr/lib/vmware/*", "/vmfs/*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Software Discovery
+** ID: T1518
+** Reference URL: https://attack.mitre.org/techniques/T1518/
diff --git a/docs/detections/prebuilt-rules/rule-details/esxi-discovery-via-grep.asciidoc b/docs/detections/prebuilt-rules/rule-details/esxi-discovery-via-grep.asciidoc
new file mode 100644
index 0000000000..d70ae73344
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/esxi-discovery-via-grep.asciidoc
@@ -0,0 +1,106 @@
+[[esxi-discovery-via-grep]]
+=== ESXI Discovery via Grep
+
+Identifies instances where a process named 'grep', 'egrep', or 'pgrep' is started on a Linux system with arguments related to virtual machine (VM) files, such as "vmdk", "vmx", "vmxf", "vmsd", "vmsn", "vswp", "vmss", "nvram", or "vmem". These file extensions are associated with VM-related file formats, and their presence in grep command arguments may indicate that a threat actor is attempting to search for, analyze, or manipulate VM files on the system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.bleepingcomputer.com/news/security/massive-esxiargs-ransomware-attack-targets-vmware-esxi-servers-worldwide/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name in ("grep", "egrep", "pgrep") and process.args in (
+  "vmdk", "vmx", "vmxf", "vmsd", "vmsn", "vswp", "vmss", "nvram", "vmem"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Software Discovery
+** ID: T1518
+** Reference URL: https://attack.mitre.org/techniques/T1518/
diff --git a/docs/detections/prebuilt-rules/rule-details/esxi-timestomping-using-touch-command.asciidoc b/docs/detections/prebuilt-rules/rule-details/esxi-timestomping-using-touch-command.asciidoc
new file mode 100644
index 0000000000..3661d65648
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/esxi-timestomping-using-touch-command.asciidoc
@@ -0,0 +1,109 @@
+[[esxi-timestomping-using-touch-command]]
+=== ESXI Timestomping using Touch Command
+
+Identifies instances where the 'touch' command is executed on a Linux system with the "-r" flag, which is used to modify the timestamp of a file based on another file's timestamp. The rule targets specific VM-related paths, such as "/etc/vmware/", "/usr/lib/vmware/", or "/vmfs/*". These paths are associated with VMware virtualization software, and their presence in the touch command arguments may indicate that a threat actor is attempting to tamper with timestamps of VM-related files and configurations on the system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.bleepingcomputer.com/news/security/massive-esxiargs-ransomware-attack-targets-vmware-esxi-servers-worldwide/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "touch" and process.args == "-r" and
+process.args : ("/etc/vmware/*", "/usr/lib/vmware/*", "/vmfs/*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indicator Removal
+** ID: T1070
+** Reference URL: https://attack.mitre.org/techniques/T1070/
+* Sub-technique:
+** Name: Timestomp
+** ID: T1070.006
+** Reference URL: https://attack.mitre.org/techniques/T1070/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/exchange-mailbox-export-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/exchange-mailbox-export-via-powershell.asciidoc
new file mode 100644
index 0000000000..93584abb4d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/exchange-mailbox-export-via-powershell.asciidoc
@@ -0,0 +1,130 @@
+[[exchange-mailbox-export-via-powershell]]
+=== Exchange Mailbox Export via PowerShell
+
+Identifies the use of the Exchange PowerShell cmdlet, New-MailBoxExportRequest, to export the contents of a primary mailbox or archive to a .pst file. Adversaries may target user email to collect sensitive information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.volexity.com/blog/2020/12/14/dark-halo-leverages-solarwinds-compromise-to-breach-organizations/
+* https://docs.microsoft.com/en-us/powershell/module/exchange/new-mailboxexportrequest?view=exchange-ps
+* https://www.elastic.co/security-labs/siestagraph-new-implant-uncovered-in-asean-member-foreign-ministry
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
+
+*Version*: 108
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Exchange Mailbox Export via PowerShell*
+
+
+The `New-MailBoxExportRequest` cmdlet is used to begin the process of exporting contents of a primary mailbox or archive to a .pst file. Note that this is done on a per-mailbox basis and this cmdlet is available only in on-premises Exchange.
+Attackers can abuse this functionality in preparation for exfiltrating contents, which is likely to contain sensitive and strategic data.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate the export operation:
+  - Identify the user account that performed the action and whether it should perform this kind of action.
+  - Contact the account owner and confirm whether they are aware of this activity.
+  - Check if this operation was approved and performed according to the organization's change management policy.
+  - Retrieve the operation status and use the `Get-MailboxExportRequest` cmdlet to review previous requests.
+  - By default, no group in Exchange has the privilege to import or export mailboxes. Investigate administrators that assigned the "Mailbox Import Export" privilege for abnormal activity.
+- Investigate if there is a significant quantity of export requests in the alert timeframe. This operation is done on a per-mailbox basis and can be part of a mass export.
+- If the operation was completed successfully:
+  - Check if the file is on the path specified in the command.
+  - Investigate if the file was compressed, archived, or retrieved by the attacker for exfiltration.
+
+
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity and it is done with proper approval.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- If the involved host is not the Exchange server, isolate the host to prevent further post-compromise behavior.
+- Use the `Remove-MailboxExportRequest` cmdlet to remove fully or partially completed export requests.
+- Prioritize cases that involve personally identifiable information (PII) or other classified data.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Review the privileges of users with the "Mailbox Import Export" privilege to ensure that the least privilege principle is being followed.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : "New-MailboxExportRequest"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Data from Local System
+** ID: T1005
+** Reference URL: https://attack.mitre.org/techniques/T1005/
+* Technique:
+** Name: Email Collection
+** ID: T1114
+** Reference URL: https://attack.mitre.org/techniques/T1114/
+* Sub-technique:
+** Name: Local Email Collection
+** ID: T1114.001
+** Reference URL: https://attack.mitre.org/techniques/T1114/001/
+* Sub-technique:
+** Name: Remote Email Collection
+** ID: T1114.002
+** Reference URL: https://attack.mitre.org/techniques/T1114/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/executable-file-creation-with-multiple-extensions.asciidoc b/docs/detections/prebuilt-rules/rule-details/executable-file-creation-with-multiple-extensions.asciidoc
index 2475ab343e..a85d66c8de 100644
--- a/docs/detections/prebuilt-rules/rule-details/executable-file-creation-with-multiple-extensions.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/executable-file-creation-with-multiple-extensions.asciidoc
@@ -5,67 +5,70 @@ Masquerading can allow an adversary to evade defenses and better blend in with t
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 101 (<<executable-file-creation-with-multiple-extensions-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type == "creation" and file.extension : "exe" and
-file.name regex~ """.*\.(vbs|vbe|bat|js|cmd|wsh|ps1|pdf|docx?|xlsx?|pp
-tx?|txt|rtf|gif|jpg|png|bmp|hta|txt|img|iso)\.exe""" and not
-(process.executable : ("?:\\Windows\\System32\\msiexec.exe",
-"C:\\Users\\*\\QGIS_SCCM\\Files\\QGIS-OSGeo4W-*-Setup-x86_64.exe") and
-file.path : "?:\\Program Files\\QGIS *\\apps\\grass\\*.exe") and not
-process.executable : ("/bin/sh", "/usr/sbin/MailScanner",
-"/usr/bin/perl")
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and file.extension : "exe" and
+  file.name regex~ """.*\.(vbs|vbe|bat|js|cmd|wsh|ps1|pdf|docx?|xlsx?|pptx?|txt|rtf|gif|jpg|png|bmp|hta|txt|img|iso)\.exe""" and
+  not (process.executable : ("?:\\Windows\\System32\\msiexec.exe", "C:\\Users\\*\\QGIS_SCCM\\Files\\QGIS-OSGeo4W-*-Setup-x86_64.exe") and
+       file.path : "?:\\Program Files\\QGIS *\\apps\\grass\\*.exe") and
+  not process.executable : ("/bin/sh", "/usr/sbin/MailScanner", "/usr/bin/perl")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,8 +80,10 @@ process.executable : ("/bin/sh", "/usr/sbin/MailScanner",
 ** Name: Masquerading
 ** ID: T1036
 ** Reference URL: https://attack.mitre.org/techniques/T1036/
-
-
+* Sub-technique:
+** Name: Double File Extension
+** ID: T1036.007
+** Reference URL: https://attack.mitre.org/techniques/T1036/007/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -87,44 +92,7 @@ process.executable : ("/bin/sh", "/usr/sbin/MailScanner",
 ** Name: User Execution
 ** ID: T1204
 ** Reference URL: https://attack.mitre.org/techniques/T1204/
-
-[[executable-file-creation-with-multiple-extensions-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type == "creation" and file.extension : "exe" and
-file.name regex~ """.*\.(vbs|vbe|bat|js|cmd|wsh|ps1|pdf|docx?|xlsx?|pp
-tx?|txt|rtf|gif|jpg|png|bmp|hta|txt|img|iso)\.exe"""
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.16.0 release)::
-* Formatting only
-
-Version 2 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type == "creation" and file.extension:"exe" and
-file.name: ( "*.vbs.exe", "*.vbe.exe", "*.bat.exe",
-"*.js.exe", "*.cmd.exe", "*.wsh.exe", "*.ps1.exe",
-"*.pdf.exe", "*.docx.exe", "*.doc.exe", "*.xlsx.exe",
-"*.xls.exe", "*.pptx.exe", "*.ppt.exe", "*.txt.exe",
-"*.rtf.exe", "*.gif.exe", "*.jpg.exe", "*.png.exe",
-"*.bmp.exe", "*.hta.exe", "*.txt.exe", "*.img.exe",
-"*.iso.exe" )
-----------------------------------
-
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/executable-file-with-unusual-extension.asciidoc b/docs/detections/prebuilt-rules/rule-details/executable-file-with-unusual-extension.asciidoc
new file mode 100644
index 0000000000..0671b6cb9c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/executable-file-with-unusual-extension.asciidoc
@@ -0,0 +1,80 @@
+[[executable-file-with-unusual-extension]]
+=== Executable File with Unusual Extension
+
+Identifies the creation or modification of an executable file with an unexpected file extension. Attackers may attempt to evade detection by masquerading files using the file extension values used by image, audio, or document file types.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.action != "deletion" and
+
+ /* MZ header or its common base64 equivalent TVqQ */
+ file.Ext.header_bytes : ("4d5a*", "54567151*") and
+
+ (
+   /* common image file extensions */
+   file.extension : ("jpg", "jpeg", "emf", "tiff", "gif", "png", "bmp", "fpx", "eps", "svg", "inf") or
+
+   /* common audio and video file extensions */
+   file.extension : ("mp3", "wav", "avi", "mpeg", "flv", "wma", "wmv", "mov", "mp4", "3gp") or
+
+   /* common document file extensions */
+   file.extension : ("txt", "pdf", "doc", "docx", "rtf", "ppt", "pptx", "xls", "xlsx", "hwp", "html")
+  ) and
+  not process.pid == 4 and
+  not process.executable : "?:\\Program Files (x86)\\Trend Micro\\Client Server Security Agent\\Ntrtscan.exe"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Masquerade File Type
+** ID: T1036.008
+** Reference URL: https://attack.mitre.org/techniques/T1036/008/
diff --git a/docs/detections/prebuilt-rules/rule-details/executable-masquerading-as-kernel-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/executable-masquerading-as-kernel-process.asciidoc
new file mode 100644
index 0000000000..bdb258f624
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/executable-masquerading-as-kernel-process.asciidoc
@@ -0,0 +1,110 @@
+[[executable-masquerading-as-kernel-process]]
+=== Executable Masquerading as Kernel Process
+
+Monitors for kernel processes with associated process executable fields that are not empty. Unix kernel processes such as kthreadd and kworker typically do not have process.executable fields associated to them. Attackers may attempt to hide their malicious programs by masquerading as legitimate kernel processes.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://sandflysecurity.com/blog/linux-stealth-rootkit-malware-with-edr-evasion-analyzed/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
+process.name : ("kworker*", "kthread*") and process.executable != null
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hide Artifacts
+** ID: T1564
+** Reference URL: https://attack.mitre.org/techniques/T1564/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Masquerade Task or Service
+** ID: T1036.004
+** Reference URL: https://attack.mitre.org/techniques/T1036/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-from-a-removable-media-with-network-connection.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-from-a-removable-media-with-network-connection.asciidoc
new file mode 100644
index 0000000000..227a644417
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/execution-from-a-removable-media-with-network-connection.asciidoc
@@ -0,0 +1,68 @@
+[[execution-from-a-removable-media-with-network-connection]]
+=== Execution from a Removable Media with Network Connection
+
+Identifies process execution from a removable media and by an unusual process. Adversaries may move onto systems, possibly those on disconnected or air-gapped networks, by copying malware to removable media and taking advantage of Autorun features when the media is inserted into a system and executes.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by process.entity_id with maxspan=5m
+ [process where host.os.type == "windows" and event.action == "start" and
+  
+  /* Direct Exec from USB */
+  (process.Ext.device.bus_type : "usb" or process.Ext.device.product_id : "USB *") and
+  (process.code_signature.trusted == false or process.code_signature.exists == false) and 
+  
+  not process.code_signature.status : ("errorExpired", "errorCode_endpoint*")]
+ [network where host.os.type == "windows" and event.action == "connection_attempted"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Replication Through Removable Media
+** ID: T1091
+** Reference URL: https://attack.mitre.org/techniques/T1091/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-from-unusual-directory-command-line.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-from-unusual-directory-command-line.asciidoc
index 19d36bc54a..d8f9cffa52 100644
--- a/docs/detections/prebuilt-rules/rule-details/execution-from-unusual-directory-command-line.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/execution-from-unusual-directory-command-line.asciidoc
@@ -5,88 +5,99 @@ Identifies process execution from suspicious default Windows directories. This m
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<execution-from-unusual-directory-command-line-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Execution from Unusual Directory - Command Line
+*Triage and analysis*
+
+
+
+*Investigating Execution from Unusual Directory - Command Line*
 
-This rule looks for the execution of scripts from unusual directories. Attackers can use system or application paths to
-hide malware and make the execution less suspicious.
+
+This rule looks for the execution of scripts from unusual directories. Attackers can use system or application paths to hide malware and make the execution less suspicious.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Examine the command line to determine which commands or scripts were executed.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the script using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of parent process executable and command line conditions.
 
-- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination
-of parent process executable and command line conditions.
 
-### Response and remediation
+*Related rules*
+
+
+- Process Execution from an Unusual Directory - ebfe1448-7fac-4d59-acea-181bd89b1f7f
+
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -94,105 +105,139 @@ of parent process executable and command line conditions.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
-This is related to the `Process Execution from an Unusual Directory rule`.
-----------------------------------
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name :
-("wscript.exe", "cscript.exe",
-"rundll32.exe", "regsvr32.exe",
-"cmstp.exe", "RegAsm.exe",
-"installutil.exe", "mshta.exe",
-"RegSvcs.exe", "powershell.exe",
-"pwsh.exe", "cmd.exe") and /* add suspicious
-execution paths here */ process.args : ("C:\\PerfLogs\\*",
-"C:\\Users\\Public\\*", "C:\\Windows\\Tasks\\*",
-"C:\\Intel\\*", "C:\\AMD\\Temp\\*",
-"C:\\Windows\\AppReadiness\\*",
-"C:\\Windows\\ServiceState\\*",
-"C:\\Windows\\security\\*",
-"C:\\Windows\\IdentityCRL\\*",
-"C:\\Windows\\Branding\\*", "C:\\Windows\\csc\\*",
-"C:\\Windows\\DigitalLocker\\*", "C:\\Windows\\en-
-US\\*", "C:\\Windows\\wlansvc\\*",
-"C:\\Windows\\Prefetch\\*", "C:\\Windows\\Fonts\\*",
-"C:\\Windows\\diagnostics\\*",
-"C:\\Windows\\TAPI\\*", "C:\\Windows\\INF\\*",
-"C:\\Windows\\System32\\Speech\\*",
-"C:\\windows\\tracing\\*", "c:\\windows\\IME\\*",
-"c:\\Windows\\Performance\\*",
-"c:\\windows\\intel\\*", "c:\\windows\\ms\\*",
-"C:\\Windows\\dot3svc\\*",
-"C:\\Windows\\panther\\*",
-"C:\\Windows\\RemotePackages\\*",
-"C:\\Windows\\OCR\\*", "C:\\Windows\\appcompat\\*",
-"C:\\Windows\\apppatch\\*",
-"C:\\Windows\\addins\\*", "C:\\Windows\\Setup\\*",
-"C:\\Windows\\Help\\*", "C:\\Windows\\SKB\\*",
-"C:\\Windows\\Vss\\*", "C:\\Windows\\servicing\\*",
-"C:\\Windows\\CbsTemp\\*", "C:\\Windows\\Logs\\*",
-"C:\\Windows\\WaaS\\*", "C:\\Windows\\twain_32\\*",
-"C:\\Windows\\ShellExperiences\\*",
-"C:\\Windows\\ShellComponents\\*",
-"C:\\Windows\\PLA\\*", "C:\\Windows\\Migration\\*",
-"C:\\Windows\\debug\\*", "C:\\Windows\\Cursors\\*",
-"C:\\Windows\\Containers\\*",
-"C:\\Windows\\Boot\\*", "C:\\Windows\\bcastdvr\\*",
-"C:\\Windows\\TextInput\\*",
-"C:\\Windows\\security\\*",
-"C:\\Windows\\schemas\\*",
-"C:\\Windows\\SchCache\\*",
-"C:\\Windows\\Resources\\*",
-"C:\\Windows\\rescache\\*",
-"C:\\Windows\\Provisioning\\*",
-"C:\\Windows\\PrintDialog\\*",
-"C:\\Windows\\PolicyDefinitions\\*",
-"C:\\Windows\\media\\*",
-"C:\\Windows\\Globalization\\*",
-"C:\\Windows\\L2Schemas\\*",
-"C:\\Windows\\LiveKernelReports\\*",
-"C:\\Windows\\ModemLogs\\*",
-"C:\\Windows\\ImmersiveControlPanel\\*",
-"C:\\$Recycle.Bin\\*") and /* noisy FP patterns */ not
-process.parent.executable : ("C:\\WINDOWS\\System32\\DriverStore\\File
-Repository\\*\\igfxCUIService*.exe",
-"C:\\Windows\\System32\\spacedeskService.exe",
-"C:\\Program Files\\Dell\\SupportAssistAgent\\SRE\\SRE.exe") and not
-(process.name : "rundll32.exe" and process.args :
-("uxtheme.dll,#64", "PRINTUI.DLL,PrintUIEntry",
-"?:\\Windows\\System32\\FirewallControlPanel.dll,ShowNotificationDialo
-g",
-"?:\\WINDOWS\\system32\\Speech\\SpeechUX\\sapi.cpl",
-"?:\\Windows\\system32\\shell32.dll,OpenAs_RunDLL")) and not
-(process.name : "cscript.exe" and process.args :
-"?:\\WINDOWS\\system32\\calluxxprovider.vbs") and not (process.name
-: "cmd.exe" and process.args : "?:\\WINDOWS\\system32\\powercfg.exe"
-and process.args : "?:\\WINDOWS\\inf\\PowerPlan.log") and not
-(process.name : "regsvr32.exe" and process.args :
-"?:\\Windows\\Help\\OEM\\scripts\\checkmui.dll") and not
-(process.name : "cmd.exe" and process.parent.executable :
-("?:\\Windows\\System32\\oobe\\windeploy.exe",
-"?:\\Program Files (x86)\\ossec-agent\\wazuh-agent.exe",
-"?:\\Windows\\System32\\igfxCUIService.exe",
-"?:\\Windows\\Temp\\IE*.tmp\\IE*-support\\ienrcore.exe"))
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : ("wscript.exe",
+                  "cscript.exe",
+                  "rundll32.exe",
+                  "regsvr32.exe",
+                  "cmstp.exe",
+                  "RegAsm.exe",
+                  "installutil.exe",
+                  "mshta.exe",
+                  "RegSvcs.exe",
+                  "powershell.exe",
+                  "pwsh.exe",
+                  "cmd.exe") and
+
+  /* add suspicious execution paths here */
+  process.args : ("C:\\PerfLogs\\*",
+                  "C:\\Users\\Public\\*",
+                  "C:\\Windows\\Tasks\\*",
+                  "C:\\Intel\\*",
+                  "C:\\AMD\\Temp\\*",
+                  "C:\\Windows\\AppReadiness\\*",
+                  "C:\\Windows\\ServiceState\\*",
+                  "C:\\Windows\\security\\*",
+                  "C:\\Windows\\IdentityCRL\\*",
+                  "C:\\Windows\\Branding\\*",
+                  "C:\\Windows\\csc\\*",
+                  "C:\\Windows\\DigitalLocker\\*",
+                  "C:\\Windows\\en-US\\*",
+                  "C:\\Windows\\wlansvc\\*",
+                  "C:\\Windows\\Prefetch\\*",
+                  "C:\\Windows\\Fonts\\*",
+                  "C:\\Windows\\diagnostics\\*",
+                  "C:\\Windows\\TAPI\\*",
+                  "C:\\Windows\\INF\\*",
+                  "C:\\Windows\\System32\\Speech\\*",
+                  "C:\\windows\\tracing\\*",
+                  "c:\\windows\\IME\\*",
+                  "c:\\Windows\\Performance\\*",
+                  "c:\\windows\\intel\\*",
+                  "c:\\windows\\ms\\*",
+                  "C:\\Windows\\dot3svc\\*",
+                  "C:\\Windows\\panther\\*",
+                  "C:\\Windows\\RemotePackages\\*",
+                  "C:\\Windows\\OCR\\*",
+                  "C:\\Windows\\appcompat\\*",
+                  "C:\\Windows\\apppatch\\*",
+                  "C:\\Windows\\addins\\*",
+                  "C:\\Windows\\Setup\\*",
+                  "C:\\Windows\\Help\\*",
+                  "C:\\Windows\\SKB\\*",
+                  "C:\\Windows\\Vss\\*",
+                  "C:\\Windows\\servicing\\*",
+                  "C:\\Windows\\CbsTemp\\*",
+                  "C:\\Windows\\Logs\\*",
+                  "C:\\Windows\\WaaS\\*",
+                  "C:\\Windows\\twain_32\\*",
+                  "C:\\Windows\\ShellExperiences\\*",
+                  "C:\\Windows\\ShellComponents\\*",
+                  "C:\\Windows\\PLA\\*",
+                  "C:\\Windows\\Migration\\*",
+                  "C:\\Windows\\debug\\*",
+                  "C:\\Windows\\Cursors\\*",
+                  "C:\\Windows\\Containers\\*",
+                  "C:\\Windows\\Boot\\*",
+                  "C:\\Windows\\bcastdvr\\*",
+                  "C:\\Windows\\TextInput\\*",
+                  "C:\\Windows\\security\\*",
+                  "C:\\Windows\\schemas\\*",
+                  "C:\\Windows\\SchCache\\*",
+                  "C:\\Windows\\Resources\\*",
+                  "C:\\Windows\\rescache\\*",
+                  "C:\\Windows\\Provisioning\\*",
+                  "C:\\Windows\\PrintDialog\\*",
+                  "C:\\Windows\\PolicyDefinitions\\*",
+                  "C:\\Windows\\media\\*",
+                  "C:\\Windows\\Globalization\\*",
+                  "C:\\Windows\\L2Schemas\\*",
+                  "C:\\Windows\\LiveKernelReports\\*",
+                  "C:\\Windows\\ModemLogs\\*",
+                  "C:\\Windows\\ImmersiveControlPanel\\*",
+                  "C:\\$Recycle.Bin\\*") and
+
+  /* noisy FP patterns */
+
+  not process.parent.executable : ("C:\\WINDOWS\\System32\\DriverStore\\FileRepository\\*\\igfxCUIService*.exe",
+                                   "C:\\Windows\\System32\\spacedeskService.exe",
+                                   "C:\\Program Files\\Dell\\SupportAssistAgent\\SRE\\SRE.exe") and
+  not (process.name : "rundll32.exe" and
+       process.args : ("uxtheme.dll,#64",
+                       "PRINTUI.DLL,PrintUIEntry",
+                       "?:\\Windows\\System32\\FirewallControlPanel.dll,ShowNotificationDialog",
+                       "?:\\WINDOWS\\system32\\Speech\\SpeechUX\\sapi.cpl",
+                       "?:\\Windows\\system32\\shell32.dll,OpenAs_RunDLL")) and
+
+  not (process.name : "cscript.exe" and process.args : "?:\\WINDOWS\\system32\\calluxxprovider.vbs") and
+
+  not (process.name : "cmd.exe" and process.args : "?:\\WINDOWS\\system32\\powercfg.exe" and process.args : "?:\\WINDOWS\\inf\\PowerPlan.log") and
+
+  not (process.name : "regsvr32.exe" and process.args : "?:\\Windows\\Help\\OEM\\scripts\\checkmui.dll") and
+
+  not (process.name : "cmd.exe" and
+       process.parent.executable : ("?:\\Windows\\System32\\oobe\\windeploy.exe",
+                                    "?:\\Program Files (x86)\\ossec-agent\\wazuh-agent.exe",
+                                    "?:\\Windows\\System32\\igfxCUIService.exe",
+                                    "?:\\Windows\\Temp\\IE*.tmp\\IE*-support\\ienrcore.exe"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -204,8 +249,10 @@ and process.args : "?:\\WINDOWS\\inf\\PowerPlan.log") and not
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -214,250 +261,7 @@ and process.args : "?:\\WINDOWS\\inf\\PowerPlan.log") and not
 ** Name: Masquerading
 ** ID: T1036
 ** Reference URL: https://attack.mitre.org/techniques/T1036/
-
-[[execution-from-unusual-directory-command-line-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.name : ("wscript.exe", "cscript.exe",
-"rundll32.exe", "regsvr32.exe",
-"cmstp.exe", "RegAsm.exe",
-"installutil.exe", "mshta.exe",
-"RegSvcs.exe", "powershell.exe",
-"pwsh.exe", "cmd.exe") and /* add suspicious
-execution paths here */ process.args : ("C:\\PerfLogs\\*",
-"C:\\Users\\Public\\*", "C:\\Windows\\Tasks\\*",
-"C:\\Intel\\*", "C:\\AMD\\Temp\\*",
-"C:\\Windows\\AppReadiness\\*",
-"C:\\Windows\\ServiceState\\*",
-"C:\\Windows\\security\\*",
-"C:\\Windows\\IdentityCRL\\*",
-"C:\\Windows\\Branding\\*", "C:\\Windows\\csc\\*",
-"C:\\Windows\\DigitalLocker\\*", "C:\\Windows\\en-
-US\\*", "C:\\Windows\\wlansvc\\*",
-"C:\\Windows\\Prefetch\\*", "C:\\Windows\\Fonts\\*",
-"C:\\Windows\\diagnostics\\*",
-"C:\\Windows\\TAPI\\*", "C:\\Windows\\INF\\*",
-"C:\\Windows\\System32\\Speech\\*",
-"C:\\windows\\tracing\\*", "c:\\windows\\IME\\*",
-"c:\\Windows\\Performance\\*",
-"c:\\windows\\intel\\*", "c:\\windows\\ms\\*",
-"C:\\Windows\\dot3svc\\*",
-"C:\\Windows\\panther\\*",
-"C:\\Windows\\RemotePackages\\*",
-"C:\\Windows\\OCR\\*", "C:\\Windows\\appcompat\\*",
-"C:\\Windows\\apppatch\\*",
-"C:\\Windows\\addins\\*", "C:\\Windows\\Setup\\*",
-"C:\\Windows\\Help\\*", "C:\\Windows\\SKB\\*",
-"C:\\Windows\\Vss\\*", "C:\\Windows\\servicing\\*",
-"C:\\Windows\\CbsTemp\\*", "C:\\Windows\\Logs\\*",
-"C:\\Windows\\WaaS\\*", "C:\\Windows\\twain_32\\*",
-"C:\\Windows\\ShellExperiences\\*",
-"C:\\Windows\\ShellComponents\\*",
-"C:\\Windows\\PLA\\*", "C:\\Windows\\Migration\\*",
-"C:\\Windows\\debug\\*", "C:\\Windows\\Cursors\\*",
-"C:\\Windows\\Containers\\*",
-"C:\\Windows\\Boot\\*", "C:\\Windows\\bcastdvr\\*",
-"C:\\Windows\\TextInput\\*",
-"C:\\Windows\\security\\*",
-"C:\\Windows\\schemas\\*",
-"C:\\Windows\\SchCache\\*",
-"C:\\Windows\\Resources\\*",
-"C:\\Windows\\rescache\\*",
-"C:\\Windows\\Provisioning\\*",
-"C:\\Windows\\PrintDialog\\*",
-"C:\\Windows\\PolicyDefinitions\\*",
-"C:\\Windows\\media\\*",
-"C:\\Windows\\Globalization\\*",
-"C:\\Windows\\L2Schemas\\*",
-"C:\\Windows\\LiveKernelReports\\*",
-"C:\\Windows\\ModemLogs\\*",
-"C:\\Windows\\ImmersiveControlPanel\\*",
-"C:\\$Recycle.Bin\\*") and /* noisy FP patterns */ not
-process.parent.executable : ("C:\\WINDOWS\\System32\\DriverStore\\File
-Repository\\*\\igfxCUIService*.exe",
-"C:\\Windows\\System32\\spacedeskService.exe",
-"C:\\Program Files\\Dell\\SupportAssistAgent\\SRE\\SRE.exe") and not
-(process.name : "rundll32.exe" and process.args :
-("uxtheme.dll,#64", "PRINTUI.DLL,PrintUIEntry",
-"?:\\Windows\\System32\\FirewallControlPanel.dll,ShowNotificationDialo
-g",
-"?:\\WINDOWS\\system32\\Speech\\SpeechUX\\sapi.cpl",
-"?:\\Windows\\system32\\shell32.dll,OpenAs_RunDLL")) and not
-(process.name : "cscript.exe" and process.args :
-"?:\\WINDOWS\\system32\\calluxxprovider.vbs") and not (process.name
-: "cmd.exe" and process.args : "?:\\WINDOWS\\system32\\powercfg.exe"
-and process.args : "?:\\WINDOWS\\inf\\PowerPlan.log") and not
-(process.name : "regsvr32.exe" and process.args :
-"?:\\Windows\\Help\\OEM\\scripts\\checkmui.dll") and not
-(process.name : "cmd.exe" and process.parent.executable :
-("?:\\Windows\\System32\\oobe\\windeploy.exe",
-"?:\\Program Files (x86)\\ossec-agent\\wazuh-agent.exe",
-"?:\\Windows\\System32\\igfxCUIService.exe",
-"?:\\Windows\\Temp\\IE*.tmp\\IE*-support\\ienrcore.exe"))
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.name : ("wscript.exe", "cscript.exe",
-"rundll32.exe", "regsvr32.exe",
-"cmstp.exe", "RegAsm.exe",
-"installutil.exe", "mshta.exe",
-"RegSvcs.exe", "powershell.exe",
-"pwsh.exe", "cmd.exe") and /*
-add suspicious execution paths here */ process.args :
-("C:\\PerfLogs\\*", "C:\\Users\\Public\\*",
-"C:\\Users\\Default\\*", "C:\\Windows\\Tasks\\*",
-"C:\\Intel\\*", "C:\\AMD\\Temp\\*",
-"C:\\Windows\\AppReadiness\\*",
-"C:\\Windows\\ServiceState\\*",
-"C:\\Windows\\security\\*",
-"C:\\Windows\\IdentityCRL\\*",
-"C:\\Windows\\Branding\\*", "C:\\Windows\\csc\\*",
-"C:\\Windows\\DigitalLocker\\*", "C:\\Windows\\en-
-US\\*", "C:\\Windows\\wlansvc\\*",
-"C:\\Windows\\Prefetch\\*", "C:\\Windows\\Fonts\\*",
-"C:\\Windows\\diagnostics\\*",
-"C:\\Windows\\TAPI\\*", "C:\\Windows\\INF\\*",
-"C:\\Windows\\System32\\Speech\\*",
-"C:\\windows\\tracing\\*", "c:\\windows\\IME\\*",
-"c:\\Windows\\Performance\\*",
-"c:\\windows\\intel\\*", "c:\\windows\\ms\\*",
-"C:\\Windows\\dot3svc\\*",
-"C:\\Windows\\ServiceProfiles\\*",
-"C:\\Windows\\panther\\*",
-"C:\\Windows\\RemotePackages\\*",
-"C:\\Windows\\OCR\\*", "C:\\Windows\\appcompat\\*",
-"C:\\Windows\\apppatch\\*",
-"C:\\Windows\\addins\\*", "C:\\Windows\\Setup\\*",
-"C:\\Windows\\Help\\*", "C:\\Windows\\SKB\\*",
-"C:\\Windows\\Vss\\*", "C:\\Windows\\Web\\*",
-"C:\\Windows\\servicing\\*",
-"C:\\Windows\\CbsTemp\\*", "C:\\Windows\\Logs\\*",
-"C:\\Windows\\WaaS\\*", "C:\\Windows\\twain_32\\*",
-"C:\\Windows\\ShellExperiences\\*",
-"C:\\Windows\\ShellComponents\\*",
-"C:\\Windows\\PLA\\*", "C:\\Windows\\Migration\\*",
-"C:\\Windows\\debug\\*", "C:\\Windows\\Cursors\\*",
-"C:\\Windows\\Containers\\*",
-"C:\\Windows\\Boot\\*", "C:\\Windows\\bcastdvr\\*",
-"C:\\Windows\\assembly\\*",
-"C:\\Windows\\TextInput\\*",
-"C:\\Windows\\security\\*",
-"C:\\Windows\\schemas\\*",
-"C:\\Windows\\SchCache\\*",
-"C:\\Windows\\Resources\\*",
-"C:\\Windows\\rescache\\*",
-"C:\\Windows\\Provisioning\\*",
-"C:\\Windows\\PrintDialog\\*",
-"C:\\Windows\\PolicyDefinitions\\*",
-"C:\\Windows\\media\\*",
-"C:\\Windows\\Globalization\\*",
-"C:\\Windows\\L2Schemas\\*",
-"C:\\Windows\\LiveKernelReports\\*",
-"C:\\Windows\\ModemLogs\\*",
-"C:\\Windows\\ImmersiveControlPanel\\*",
-"C:\\$Recycle.Bin\\*") and not process.parent.executable : ("C:\\WIN
-DOWS\\System32\\DriverStore\\FileRepository\\*\\igfxCUIService*.exe",
-"C:\\Windows\\System32\\spacedeskService.exe",
-"C:\\Program Files\\Dell\\SupportAssistAgent\\SRE\\SRE.exe") and not
-(process.name : "rundll32.exe" and process.args : ("uxtheme.dll,#64",
-"PRINTUI.DLL,PrintUIEntry"))
-----------------------------------
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.name : ("wscript.exe","cscript.exe","rundll32.exe","regsvr32.e
-xe","cmstp.exe","RegAsm.exe","installutil.exe","mshta.exe","RegSvcs.ex
-e", "powershell.exe", "pwsh.exe", "cmd.exe") and /* add suspicious
-execution paths here */ process.args : ("C:\\PerfLogs\\*","C:\\Users\\
-Public\\*","C:\\Users\\Default\\*","C:\\Windows\\Tasks\\*","C:\\Intel\
-\*", "C:\\AMD\\Temp\\*", "C:\\Windows\\AppReadiness\\*", "C:\\Window
-s\\ServiceState\\*","C:\\Windows\\security\\*","C:\\Windows\\IdentityC
-RL\\*","C:\\Windows\\Branding\\*","C:\\Windows\\csc\\*",
-"C:\\Windows\\DigitalLocker\\*","C:\\Windows\\en-US\\*","C:\\Windows\\
-wlansvc\\*","C:\\Windows\\Prefetch\\*","C:\\Windows\\Fonts\\*", "C:\\
-Windows\\diagnostics\\*","C:\\Windows\\TAPI\\*","C:\\Windows\\INF\\*",
-"C:\\Windows\\System32\\Speech\\*","C:\\windows\\tracing\\*", "c:\\wi
-ndows\\IME\\*","c:\\Windows\\Performance\\*","c:\\windows\\intel\\*","
-c:\\windows\\ms\\*","C:\\Windows\\dot3svc\\*","C:\\Windows\\ServicePro
-files\\*", "C:\\Windows\\panther\\*","C:\\Windows\\RemotePackages\\*"
-,"C:\\Windows\\OCR\\*","C:\\Windows\\appcompat\\*","C:\\Windows\\apppa
-tch\\*","C:\\Windows\\addins\\*", "C:\\Windows\\Setup\\*","C:\\Window
-s\\Help\\*","C:\\Windows\\SKB\\*","C:\\Windows\\Vss\\*","C:\\Windows\\
-Web\\*","C:\\Windows\\servicing\\*","C:\\Windows\\CbsTemp\\*", "C:\\W
-indows\\Logs\\*","C:\\Windows\\WaaS\\*","C:\\Windows\\twain_32\\*","C:
-\\Windows\\ShellExperiences\\*","C:\\Windows\\ShellComponents\\*","C:\
-\Windows\\PLA\\*", "C:\\Windows\\Migration\\*","C:\\Windows\\debug\\*
-","C:\\Windows\\Cursors\\*","C:\\Windows\\Containers\\*","C:\\Windows\
-\Boot\\*","C:\\Windows\\bcastdvr\\*", "C:\\Windows\\assembly\\*","C:\
-\Windows\\TextInput\\*","C:\\Windows\\security\\*","C:\\Windows\\schem
-as\\*","C:\\Windows\\SchCache\\*","C:\\Windows\\Resources\\*", "C:\\W
-indows\\rescache\\*","C:\\Windows\\Provisioning\\*","C:\\Windows\\Prin
-tDialog\\*","C:\\Windows\\PolicyDefinitions\\*","C:\\Windows\\media\\*
-", "C:\\Windows\\Globalization\\*","C:\\Windows\\L2Schemas\\*","C:\\W
-indows\\LiveKernelReports\\*","C:\\Windows\\ModemLogs\\*","C:\\Windows
-\\ImmersiveControlPanel\\*", "C:\\$Recycle.Bin\\*")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.name : ("wscript.exe","cscript.exe","rundll32.exe","regsvr32.e
-xe","cmstp.exe","RegAsm.exe","installutil.exe","mshta.exe","RegSvcs.ex
-e") and /* add suspicious execution paths here */ process.args : ("C:
-\\PerfLogs\\*","C:\\Users\\Public\\*","C:\\Users\\Default\\*","C:\\Win
-dows\\Tasks\\*","C:\\Intel\\*", "C:\\AMD\\Temp\\*",
-"C:\\Windows\\AppReadiness\\*", "C:\\Windows\\ServiceState\\*","C:\\Wi
-ndows\\security\\*","C:\\Windows\\IdentityCRL\\*","C:\\Windows\\Brandi
-ng\\*","C:\\Windows\\csc\\*",
-"C:\\Windows\\DigitalLocker\\*","C:\\Windows\\en-US\\*","C:\\Windows\\
-wlansvc\\*","C:\\Windows\\Prefetch\\*","C:\\Windows\\Fonts\\*", "C:\\
-Windows\\diagnostics\\*","C:\\Windows\\TAPI\\*","C:\\Windows\\INF\\*",
-"C:\\Windows\\System32\\Speech\\*","C:\\windows\\tracing\\*", "c:\\wi
-ndows\\IME\\*","c:\\Windows\\Performance\\*","c:\\windows\\intel\\*","
-c:\\windows\\ms\\*","C:\\Windows\\dot3svc\\*","C:\\Windows\\ServicePro
-files\\*", "C:\\Windows\\panther\\*","C:\\Windows\\RemotePackages\\*"
-,"C:\\Windows\\OCR\\*","C:\\Windows\\appcompat\\*","C:\\Windows\\apppa
-tch\\*","C:\\Windows\\addins\\*", "C:\\Windows\\Setup\\*","C:\\Window
-s\\Help\\*","C:\\Windows\\SKB\\*","C:\\Windows\\Vss\\*","C:\\Windows\\
-Web\\*","C:\\Windows\\servicing\\*","C:\\Windows\\CbsTemp\\*", "C:\\W
-indows\\Logs\\*","C:\\Windows\\WaaS\\*","C:\\Windows\\twain_32\\*","C:
-\\Windows\\ShellExperiences\\*","C:\\Windows\\ShellComponents\\*","C:\
-\Windows\\PLA\\*", "C:\\Windows\\Migration\\*","C:\\Windows\\debug\\*
-","C:\\Windows\\Cursors\\*","C:\\Windows\\Containers\\*","C:\\Windows\
-\Boot\\*","C:\\Windows\\bcastdvr\\*", "C:\\Windows\\assembly\\*","C:\
-\Windows\\TextInput\\*","C:\\Windows\\security\\*","C:\\Windows\\schem
-as\\*","C:\\Windows\\SchCache\\*","C:\\Windows\\Resources\\*", "C:\\W
-indows\\rescache\\*","C:\\Windows\\Provisioning\\*","C:\\Windows\\Prin
-tDialog\\*","C:\\Windows\\PolicyDefinitions\\*","C:\\Windows\\media\\*
-", "C:\\Windows\\Globalization\\*","C:\\Windows\\L2Schemas\\*","C:\\W
-indows\\LiveKernelReports\\*","C:\\Windows\\ModemLogs\\*","C:\\Windows
-\\ImmersiveControlPanel\\*")
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-of-an-unsigned-service.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-of-an-unsigned-service.asciidoc
new file mode 100644
index 0000000000..eb507052ac
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/execution-of-an-unsigned-service.asciidoc
@@ -0,0 +1,80 @@
+[[execution-of-an-unsigned-service]]
+=== Execution of an Unsigned Service
+
+This rule identifies the execution of unsigned executables via service control manager (SCM). Adversaries may abuse SCM to execute malware or escalate privileges.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 105
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:windows and event.category:process and event.type:start and 
+process.parent.executable:"C:\\Windows\\System32\\services.exe" and 
+(process.code_signature.exists:false or process.code_signature.trusted:false) and
+not process.code_signature.status : (errorCode_endpoint* or "errorChaining")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: System Services
+** ID: T1569
+** Reference URL: https://attack.mitre.org/techniques/T1569/
+* Sub-technique:
+** Name: Service Execution
+** ID: T1569.002
+** Reference URL: https://attack.mitre.org/techniques/T1569/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-of-com-object-via-xwizard.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-of-com-object-via-xwizard.asciidoc
index 20a93ae17b..9e34ce9922 100644
--- a/docs/detections/prebuilt-rules/rule-details/execution-of-com-object-via-xwizard.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/execution-of-com-object-via-xwizard.asciidoc
@@ -5,69 +5,76 @@ Windows Component Object Model (COM) is an inter-process communication (IPC) com
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://lolbas-project.github.io/lolbas/Binaries/Xwizard/
 * http://www.hexacorn.com/blog/2017/07/31/the-wizard-of-x-oppa-plugx-style/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Elastic Endgame
-
-*Version*: 102 (<<execution-of-com-object-via-xwizard-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.pe.original_file_name
-: "xwizard.exe" and ( (process.args : "RunWizard" and process.args
-: "{*}") or (process.executable != null and not
-process.executable : ("C:\\Windows\\SysWOW64\\xwizard.exe",
-"C:\\Windows\\System32\\xwizard.exe") ) )
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ (process.name : "xwizard.exe" or ?process.pe.original_file_name : "xwizard.exe") and
+ (
+   (process.args : "RunWizard" and process.args : "{*}") or
+   (process.executable != null and
+     not process.executable : ("C:\\Windows\\SysWOW64\\xwizard.exe", "C:\\Windows\\System32\\xwizard.exe")
+   )
+ )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,29 +86,7 @@ process.executable : ("C:\\Windows\\SysWOW64\\xwizard.exe",
 ** Name: Inter-Process Communication
 ** ID: T1559
 ** Reference URL: https://attack.mitre.org/techniques/T1559/
-
-[[execution-of-com-object-via-xwizard-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.pe.original_file_name : "xwizard.exe" and ( (process.args
-: "RunWizard" and process.args : "{*}") or (process.executable !=
-null and not process.executable :
-("C:\\Windows\\SysWOW64\\xwizard.exe",
-"C:\\Windows\\System32\\xwizard.exe") ) )
-----------------------------------
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Component Object Model
+** ID: T1559.001
+** Reference URL: https://attack.mitre.org/techniques/T1559/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-of-file-written-or-modified-by-microsoft-office.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-of-file-written-or-modified-by-microsoft-office.asciidoc
index 0e5056dcff..5d348c666a 100644
--- a/docs/detections/prebuilt-rules/rule-details/execution-of-file-written-or-modified-by-microsoft-office.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/execution-of-file-written-or-modified-by-microsoft-office.asciidoc
@@ -5,68 +5,65 @@ Identifies an executable created by a Microsoft Office application and subsequen
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
-* winlogbeat-*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.file-*
 * endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 60 minutes
+*Runs every*: 60m
 
 *Searches indices from*: now-120m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<execution-of-file-written-or-modified-by-microsoft-office-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Execution of File Written or Modified by Microsoft Office
+*Triage and analysis*
+
+
+
+*Investigating Execution of File Written or Modified by Microsoft Office*
+
+
+Microsoft Office, a widely used suite of productivity applications, is frequently targeted by attackers due to its popularity in corporate environments. Attackers exploit its extensive capabilities, like macro scripts in Word and Excel, to gain initial access to systems. They often use Office documents as delivery mechanisms for malware or phishing attempts, taking advantage of their trusted status in professional settings.
 
-Microsoft Office is a suite of applications designed to help with productivity and completing common tasks on a computer.
-You can create and edit documents containing text and images, work with data in spreadsheets and databases, and create
-presentations and posters. As it is some of the most-used software across companies, MS Office is frequently
-targeted for initial access. It also has a wide variety of capabilities that attackers can take advantage of.
+This rule searches for executable files written by MS Office applications executed in sequence. This is most likely the result of the execution of malicious documents or exploitation for initial access or privilege escalation. This rule can also detect suspicious processes masquerading as the MS Office applications.
 
-This rule searches for executable files written by MS Office applications executed in sequence. This is most likely the result
-of the execution of malicious documents or exploitation for initial access or privilege escalation. This rule can also detect
-suspicious processes masquerading as the MS Office applications.
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Retrieve MS Office documents received and opened by the user that could cause this behavior. Common locations include,
-but are not limited to, the Downloads and Document folders and the folder configured at the email client.
+- Retrieve MS Office documents received and opened by the user that could cause this behavior. Common locations include, but are not limited to, the Downloads and Document folders and the folder configured at the email client.
 - Determine if the collected files are malicious:
   - Use a private sandboxed malware analysis system to perform analysis.
     - Observe and collect information about the following activities:
@@ -77,54 +74,56 @@ but are not limited to, the Downloads and Document folders and the folder config
   - Use the PowerShell `Get-FileHash` cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - If the triage identified malware, search the environment for additional compromised hosts.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system,
-persistence mechanisms, and malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
   - If the malicious file was delivered via phishing:
     - Block the email sender from sending future emails.
     - Block the malicious web pages.
     - Remove emails from the sender from mailboxes.
     - Consider improvements to the security awareness program.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence with maxspan=2h [file where event.type != "deletion" and
-file.extension : "exe" and (process.name : "WINWORD.EXE" or
-process.name : "EXCEL.EXE" or process.name : "OUTLOOK.EXE" or
-process.name : "POWERPNT.EXE" or process.name : "eqnedt32.exe"
-or process.name : "fltldr.exe" or process.name :
-"MSPUB.EXE" or process.name : "MSACCESS.EXE") ] by host.id,
-file.path [process where event.type == "start"] by host.id,
-process.executable
+[source, js]
 ----------------------------------
+sequence with maxspan=2h
+  [file where host.os.type == "windows" and event.type != "deletion" and file.extension : "exe" and
+     (process.name : "WINWORD.EXE" or
+      process.name : "EXCEL.EXE" or
+      process.name : "OUTLOOK.EXE" or
+      process.name : "POWERPNT.EXE" or
+      process.name : "eqnedt32.exe" or
+      process.name : "fltldr.exe" or
+      process.name : "MSPUB.EXE" or
+      process.name : "MSACCESS.EXE")
+  ] by host.id, file.path
+  [process where host.os.type == "windows" and event.type == "start" and 
+   not (process.name : "NewOutlookInstaller.exe" and process.code_signature.subject_name : "Microsoft Corporation" and process.code_signature.trusted == true)
+  ] by host.id, process.executable
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -132,8 +131,6 @@ process.executable
 ** Name: Execution
 ** ID: TA0002
 ** Reference URL: https://attack.mitre.org/tactics/TA0002/
-
-
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -142,43 +139,11 @@ process.executable
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[execution-of-file-written-or-modified-by-microsoft-office-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=2h [file where event.type != "deletion" and
-file.extension : "exe" and (process.name : "WINWORD.EXE" or
-process.name : "EXCEL.EXE" or process.name : "OUTLOOK.EXE" or
-process.name : "POWERPNT.EXE" or process.name : "eqnedt32.exe"
-or process.name : "fltldr.exe" or process.name :
-"MSPUB.EXE" or process.name : "MSACCESS.EXE") ] by host.id,
-file.path [process where event.type in ("start", "process_started")]
-by host.id, process.executable
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (7.15.0 release)::
-* Formatting only
-
-Version 4 (7.14.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-of-file-written-or-modified-by-pdf-reader.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-of-file-written-or-modified-by-pdf-reader.asciidoc
index 89643cf1c0..8c5c122b6f 100644
--- a/docs/detections/prebuilt-rules/rule-details/execution-of-file-written-or-modified-by-pdf-reader.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/execution-of-file-written-or-modified-by-pdf-reader.asciidoc
@@ -5,67 +5,68 @@ Identifies a suspicious file that was written by a PDF reader application and su
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.file-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 60 minutes
+*Runs every*: 60m
 
 *Searches indices from*: now-120m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<execution-of-file-written-or-modified-by-pdf-reader-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Execution of File Written or Modified by PDF Reader
+*Triage and analysis*
+
+
+
+*Investigating Execution of File Written or Modified by PDF Reader*
+
+
+PDF is a common file type used in corporate environments and most machines have software to handle these files. This creates a vector where attackers can exploit the engines and technology behind this class of software for initial access or privilege escalation.
 
-PDF is a common file type used in corporate environments and most machines have software to
-handle these files. This creates a vector where attackers can exploit the engines and technology behind this class of
-software for initial access or privilege escalation.
+This rule searches for executable files written by PDF reader software and executed in sequence. This is most likely the result of exploitation for privilege escalation or initial access. This rule can also detect suspicious processes masquerading as PDF readers.
 
-This rule searches for executable files written by PDF reader software and executed in sequence. This is most likely the
-result of exploitation for privilege escalation or initial access. This rule can also detect suspicious processes masquerading as
-PDF readers.
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Retrieve the PDF documents received and opened by the user that could cause this behavior. Common locations include,
-but are not limited to, the Downloads and Document folders and the folder configured at the email client.
+- Retrieve the PDF documents received and opened by the user that could cause this behavior. Common locations include, but are not limited to, the Downloads and Document folders and the folder configured at the email client.
 - Determine if the collected files are malicious:
   - Use a private sandboxed malware analysis system to perform analysis.
     - Observe and collect information about the following activities:
@@ -76,56 +77,56 @@ but are not limited to, the Downloads and Document folders and the folder config
   - Use the PowerShell `Get-FileHash` cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - If the triage identified malware, search the environment for additional compromised hosts.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system,
-persistence mechanisms, and malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
   - If the malicious file was delivered via phishing:
     - Block the email sender from sending future emails.
     - Block the malicious web pages.
     - Remove emails from the sender from mailboxes.
     - Consider improvements to the security awareness program.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence with maxspan=2h [file where event.type != "deletion" and
-file.extension : "exe" and (process.name : "AcroRd32.exe" or
-process.name : "rdrcef.exe" or process.name :
-"FoxitPhantomPDF.exe" or process.name : "FoxitReader.exe") and
-not (file.name : "FoxitPhantomPDF.exe" or file.name :
-"FoxitPhantomPDFUpdater.exe" or file.name :
-"FoxitReader.exe" or file.name : "FoxitReaderUpdater.exe" or
-file.name : "AcroRd32.exe" or file.name : "rdrcef.exe") ]
-by host.id, file.path [process where event.type == "start"] by
-host.id, process.executable
+[source, js]
 ----------------------------------
+sequence with maxspan=2h
+  [file where host.os.type == "windows" and event.type != "deletion" and file.extension : "exe" and
+     (process.name : "AcroRd32.exe" or
+      process.name : "rdrcef.exe" or
+      process.name : "FoxitPhantomPDF.exe" or
+      process.name : "FoxitReader.exe") and
+     not (file.name : "FoxitPhantomPDF.exe" or
+          file.name : "FoxitPhantomPDFUpdater.exe" or
+          file.name : "FoxitReader.exe" or
+          file.name : "FoxitReaderUpdater.exe" or
+          file.name : "AcroRd32.exe" or
+          file.name : "rdrcef.exe")
+  ] by host.id, file.path
+  [process where host.os.type == "windows" and event.type == "start"] by host.id, process.executable
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -133,8 +134,6 @@ host.id, process.executable
 ** Name: Execution
 ** ID: TA0002
 ** Reference URL: https://attack.mitre.org/tactics/TA0002/
-
-
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -143,42 +142,11 @@ host.id, process.executable
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[execution-of-file-written-or-modified-by-pdf-reader-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=2h [file where event.type != "deletion" and
-file.extension : "exe" and (process.name : "AcroRd32.exe" or
-process.name : "rdrcef.exe" or process.name :
-"FoxitPhantomPDF.exe" or process.name : "FoxitReader.exe") and
-not (file.name : "FoxitPhantomPDF.exe" or file.name :
-"FoxitPhantomPDFUpdater.exe" or file.name :
-"FoxitReader.exe" or file.name : "FoxitReaderUpdater.exe" or
-file.name : "AcroRd32.exe" or file.name : "rdrcef.exe") ]
-by host.id, file.path [process where event.type in ("start",
-"process_started")] by host.id, process.executable
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (7.14.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-of-persistent-suspicious-program.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-of-persistent-suspicious-program.asciidoc
index 683bdd8e26..89dbcecf8b 100644
--- a/docs/detections/prebuilt-rules/rule-details/execution-of-persistent-suspicious-program.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/execution-of-persistent-suspicious-program.asciidoc
@@ -5,63 +5,69 @@ Identifies execution of suspicious persistent programs (scripts, rundll32, etc.)
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 101 (<<execution-of-persistent-suspicious-program-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-/* userinit followed by explorer followed by early child process of
-explorer (unlikely to be launched interactively) within 1m */ sequence
-by host.id, user.name with maxspan=1m [process where event.type ==
-"start" and process.name : "userinit.exe" and process.parent.name :
-"winlogon.exe"] [process where event.type == "start" and
-process.name : "explorer.exe"] [process where event.type == "start"
-and process.parent.name : "explorer.exe" and /* add suspicious
-programs here */ process.pe.original_file_name in ("cscript.exe",
-"wscript.exe", "PowerShell.EXE",
-"MSHTA.EXE", "RUNDLL32.EXE",
-"REGSVR32.EXE", "RegAsm.exe",
-"MSBuild.exe", "InstallUtil.exe")
-and /* add potential suspicious paths here */ process.args :
-("C:\\Users\\*", "C:\\ProgramData\\*", "C:\\Windows\\Temp\\*",
-"C:\\Windows\\Tasks\\*", "C:\\PerfLogs\\*", "C:\\Intel\\*") ]
+[source, js]
 ----------------------------------
+/* userinit followed by explorer followed by early child process of explorer (unlikely to be launched interactively) within 1m */
+sequence by host.id, user.name with maxspan=1m
+  [process where host.os.type == "windows" and event.type == "start" and process.name : "userinit.exe" and process.parent.name : "winlogon.exe"]
+  [process where host.os.type == "windows" and event.type == "start" and process.name : "explorer.exe"]
+  [process where host.os.type == "windows" and event.type == "start" and process.parent.name : "explorer.exe" and
+   /* add suspicious programs here */
+   process.pe.original_file_name in ("cscript.exe",
+                                     "wscript.exe",
+                                     "PowerShell.EXE",
+                                     "MSHTA.EXE",
+                                     "RUNDLL32.EXE",
+                                     "REGSVR32.EXE",
+                                     "RegAsm.exe",
+                                     "MSBuild.exe",
+                                     "InstallUtil.exe") and
+    /* add potential suspicious paths here */
+    process.args : ("C:\\Users\\*", "C:\\ProgramData\\*", "C:\\Windows\\Temp\\*", "C:\\Windows\\Tasks\\*", "C:\\PerfLogs\\*", "C:\\Intel\\*")
+   ]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,36 +79,7 @@ and /* add potential suspicious paths here */ process.args :
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[execution-of-persistent-suspicious-program-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* userinit followed by explorer followed by early child process of
-explorer (unlikely to be launched interactively) within 1m */ sequence
-by host.id, user.name with maxspan=1m [process where event.type in
-("start", "process_started") and process.name : "userinit.exe" and
-process.parent.name : "winlogon.exe"] [process where event.type in
-("start", "process_started") and process.name : "explorer.exe"]
-[process where event.type in ("start", "process_started") and
-process.parent.name : "explorer.exe" and /* add suspicious programs
-here */ process.pe.original_file_name in ("cscript.exe",
-"wscript.exe", "PowerShell.EXE",
-"MSHTA.EXE", "RUNDLL32.EXE",
-"REGSVR32.EXE", "RegAsm.exe",
-"MSBuild.exe", "InstallUtil.exe")
-and /* add potential suspicious paths here */ process.args :
-("C:\\Users\\*", "C:\\ProgramData\\*", "C:\\Windows\\Temp\\*",
-"C:\\Windows\\Tasks\\*", "C:\\PerfLogs\\*", "C:\\Intel\\*") ]
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Registry Run Keys / Startup Folder
+** ID: T1547.001
+** Reference URL: https://attack.mitre.org/techniques/T1547/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-via-electron-child-process-node-js-module.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-via-electron-child-process-node-js-module.asciidoc
new file mode 100644
index 0000000000..067fa58707
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/execution-via-electron-child-process-node-js-module.asciidoc
@@ -0,0 +1,109 @@
+[[execution-via-electron-child-process-node-js-module]]
+=== Execution via Electron Child Process Node.js Module
+
+Identifies attempts to execute a child process from within the context of an Electron application using the child_process Node.js module. Adversaries may abuse this technique to inherit permissions from parent processes.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.matthewslipper.com/2019/09/22/everything-you-wanted-electron-child-process.html
+* https://www.trustedsec.com/blog/macos-injection-via-third-party-frameworks/
+* https://nodejs.org/api/child_process.html
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and process.args:("-e" and const*require*child_process*)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-via-local-sxs-shared-module.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-via-local-sxs-shared-module.asciidoc
index 94140e651c..4b38a06c8d 100644
--- a/docs/detections/prebuilt-rules/rule-details/execution-via-local-sxs-shared-module.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/execution-via-local-sxs-shared-module.asciidoc
@@ -5,67 +5,78 @@ Identifies the creation, change, or deletion of a DLL module within a Windows Sx
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-redirection
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Elastic Endgame
-
-*Version*: 101 (<<execution-via-local-sxs-shared-module-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+
+*Triage and analysis*
+
 
 The SxS DotLocal folder is a legitimate feature that can be abused to hijack standard modules loading order by forcing an executable on the same application.exe.local folder to load a malicious DLL module from the same directory.
-----------------------------------
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where file.extension : "dll" and file.path :
-"C:\\*\\*.exe.local\\*.dll"
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and file.extension : "dll" and file.path : "C:\\*\\*.exe.local\\*.dll"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,28 +88,3 @@ file where file.extension : "dll" and file.path :
 ** Name: Shared Modules
 ** ID: T1129
 ** Reference URL: https://attack.mitre.org/techniques/T1129/
-
-[[execution-via-local-sxs-shared-module-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-via-microsoft-dotnet-clickonce-host.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-via-microsoft-dotnet-clickonce-host.asciidoc
new file mode 100644
index 0000000000..e2f5906838
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/execution-via-microsoft-dotnet-clickonce-host.asciidoc
@@ -0,0 +1,71 @@
+[[execution-via-microsoft-dotnet-clickonce-host]]
+=== Execution via Microsoft DotNet ClickOnce Host
+
+Identifies the execution of DotNet ClickOnce installer via Dfsvc.exe trampoline. Adversaries may take advantage of ClickOnce to proxy execution of malicious payloads via trusted Microsoft processes.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by user.id with maxspan=5s
+ [process where host.os.type == "windows" and event.action == "start" and
+  process.name : "rundll32.exe" and process.command_line : ("*dfshim*ShOpenVerbApplication*", "*dfshim*#*")]
+ [network where host.os.type == "windows" and process.name : "dfsvc.exe"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Trusted Developer Utilities Proxy Execution
+** ID: T1127
+** Reference URL: https://attack.mitre.org/techniques/T1127/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: Rundll32
+** ID: T1218.011
+** Reference URL: https://attack.mitre.org/techniques/T1218/011/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-via-ms-visualstudio-pre-post-build-events.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-via-ms-visualstudio-pre-post-build-events.asciidoc
new file mode 100644
index 0000000000..5d3d8228f0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/execution-via-ms-visualstudio-pre-post-build-events.asciidoc
@@ -0,0 +1,108 @@
+[[execution-via-ms-visualstudio-pre-post-build-events]]
+=== Execution via MS VisualStudio Pre/Post Build Events
+
+Identifies the execution of a command via Microsoft Visual Studio Pre or Post build events. Adversaries may backdoor a trusted visual studio project to execute a malicious command during the project build process.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.microsoft.com/en-us/visualstudio/ide/reference/pre-build-event-post-build-event-command-line-dialog-box?view=vs-2022
+* https://www.pwc.com/gx/en/issues/cybersecurity/cyber-threat-intelligence/threat-actor-of-in-tur-est.html
+* https://blog.google/threat-analysis-group/new-campaign-targeting-security-researchers/
+* https://github.com/sbousseaden/EVTX-ATTACK-SAMPLES/blob/master/Execution/execution_evasion_visual_studio_prebuild_event.evtx
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence with maxspan=1m
+  [process where host.os.type == "windows" and event.action == "start" and
+   process.name : "cmd.exe" and process.parent.name : "MSBuild.exe" and
+   process.args : "?:\\Users\\*\\AppData\\Local\\Temp\\tmp*.exec.cmd"] by process.entity_id
+  [process where host.os.type == "windows" and event.action == "start" and
+    process.name : (
+      "cmd.exe", "powershell.exe",
+      "MSHTA.EXE", "CertUtil.exe",
+      "CertReq.exe", "rundll32.exe",
+      "regsvr32.exe", "MSbuild.exe",
+      "cscript.exe", "wscript.exe",
+      "installutil.exe"
+    ) and
+    not 
+    (
+      process.name : ("cmd.exe", "powershell.exe") and
+      process.args : (
+        "*\\vcpkg\\scripts\\buildsystems\\msbuild\\applocal.ps1",
+        "HKLM\\SOFTWARE\\Microsoft\\VisualStudio\\SxS\\VS?",
+        "process.versions.node*",
+        "?:\\Program Files\\nodejs\\node.exe",
+        "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MSBuild\\ToolsVersions\\*",
+        "*Get-ChildItem*Tipasplus.css*",
+        "Build\\GenerateResourceScripts.ps1",
+        "Shared\\Common\\..\\..\\BuildTools\\ConfigBuilder.ps1\"",
+        "?:\\Projets\\*\\PostBuild\\MediaCache.ps1"
+      )
+    ) and
+    not process.executable : "?:\\Program Files*\\Microsoft Visual Studio\\*\\MSBuild.exe" and
+    not (process.name : "cmd.exe" and
+         process.command_line :
+                  ("*vswhere.exe -property catalog_productSemanticVersion*",
+                   "*git log --pretty=format*", "*\\.nuget\\packages\\vswhere\\*",
+                   "*Common\\..\\..\\BuildTools\\*"))
+  ] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Trusted Developer Utilities Proxy Execution
+** ID: T1127
+** Reference URL: https://attack.mitre.org/techniques/T1127/
+* Sub-technique:
+** Name: MSBuild
+** ID: T1127.001
+** Reference URL: https://attack.mitre.org/techniques/T1127/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-via-mssql-xp-cmdshell-stored-procedure.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-via-mssql-xp-cmdshell-stored-procedure.asciidoc
new file mode 100644
index 0000000000..ac743c94d2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/execution-via-mssql-xp-cmdshell-stored-procedure.asciidoc
@@ -0,0 +1,155 @@
+[[execution-via-mssql-xp-cmdshell-stored-procedure]]
+=== Execution via MSSQL xp_cmdshell Stored Procedure
+
+Identifies execution via MSSQL xp_cmdshell stored procedure. Malicious users may attempt to elevate their privileges by using xp_cmdshell, which is disabled by default, thus, it's important to review the context of it's use.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://thedfirreport.com/2022/07/11/select-xmrig-from-sqlserver/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 111
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Execution via MSSQL xp_cmdshell Stored Procedure*
+
+
+Microsoft SQL Server (MSSQL) has procedures meant to extend its functionality, the Extended Stored Procedures. These procedures are external functions written in C/C++; some provide interfaces for external programs. This is the case for xp_cmdshell, which spawns a Windows command shell and passes in a string for execution. Attackers can use this to execute commands on the system running the SQL server, commonly to escalate their privileges and establish persistence.
+
+The xp_cmdshell procedure is disabled by default, but when used, it has the same security context as the MSSQL Server service account, which is often privileged.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the command line to determine if the command executed is potentially harmful or malicious.
+- Inspect the host for suspicious or abnormal behavior in the alert timeframe.
+
+
+*False positive analysis*
+
+
+- This mechanism can be used legitimately, but it brings inherent risk. The security team must monitor any activity of it. If recurrent tasks are being executed using this mechanism, consider adding exceptions — preferably with a full command line.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Ensure that SQL servers are not directly exposed to the internet. If there is a business justification for such, use an allowlist to allow only connections from known legitimate sources.
+- Disable the xp_cmdshell stored procedure.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.parent.name : "sqlservr.exe" and 
+  (
+   (process.name : "cmd.exe" and 
+    not process.args : ("\\\\*", "diskfree", "rmdir", "mkdir", "dir", "del", "rename", "bcp", "*XMLNAMESPACES*", 
+                        "?:\\MSSQL\\Backup\\Jobs\\sql_agent_backup_job.ps1", "K:\\MSSQL\\Backup\\msdb", "K:\\MSSQL\\Backup\\Logins")) or 
+                        
+   (process.name : "vpnbridge.exe" or ?process.pe.original_file_name : "vpnbridge.exe") or 
+
+   (process.name : "certutil.exe" or ?process.pe.original_file_name == "CertUtil.exe") or 
+
+   (process.name : "bitsadmin.exe" or ?process.pe.original_file_name == "bitsadmin.exe")
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Server Software Component
+** ID: T1505
+** Reference URL: https://attack.mitre.org/techniques/T1505/
+* Sub-technique:
+** Name: SQL Stored Procedures
+** ID: T1505.001
+** Reference URL: https://attack.mitre.org/techniques/T1505/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-via-tsclient-mountpoint.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-via-tsclient-mountpoint.asciidoc
index 419a7ae144..d84a5830c7 100644
--- a/docs/detections/prebuilt-rules/rule-details/execution-via-tsclient-mountpoint.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/execution-via-tsclient-mountpoint.asciidoc
@@ -5,63 +5,68 @@ Identifies execution from the Remote Desktop Protocol (RDP) shared mountpoint ts
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://posts.specterops.io/revisiting-remote-desktop-lateral-movement-8fb905cb46c3
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-
-*Version*: 101 (<<execution-via-tsclient-mountpoint-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.executable :
-"\\Device\\Mup\\tsclient\\*.exe"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.executable : "\\Device\\Mup\\tsclient\\*.exe"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,28 +78,7 @@ process where event.type == "start" and process.executable :
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[execution-via-tsclient-mountpoint-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.executable : "\\Device\\Mup\\tsclient\\*.exe"
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Remote Desktop Protocol
+** ID: T1021.001
+** Reference URL: https://attack.mitre.org/techniques/T1021/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-via-windows-subsystem-for-linux.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-via-windows-subsystem-for-linux.asciidoc
new file mode 100644
index 0000000000..3e1af2337f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/execution-via-windows-subsystem-for-linux.asciidoc
@@ -0,0 +1,76 @@
+[[execution-via-windows-subsystem-for-linux]]
+=== Execution via Windows Subsystem for Linux
+
+Detects attempts to execute a program on the host from the Windows Subsystem for Linux. Adversaries may enable and use WSL for Linux to avoid detection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://learn.microsoft.com/en-us/windows/wsl/wsl-config
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type : "start" and
+  process.parent.name : ("wsl.exe", "wslhost.exe") and
+  not process.executable : (
+        "?:\\Program Files (x86)\\*",
+        "?:\\Program Files\\*",
+        "?:\\Program Files*\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_*\\wsl*.exe",
+        "?:\\Windows\\System32\\conhost.exe",
+        "?:\\Windows\\System32\\lxss\\wslhost.exe",
+        "?:\\Windows\\System32\\WerFault.exe",
+        "?:\\Windows\\Sys*\\wslconfig.exe"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indirect Command Execution
+** ID: T1202
+** Reference URL: https://attack.mitre.org/techniques/T1202/
diff --git a/docs/detections/prebuilt-rules/rule-details/execution-with-explicit-credentials-via-scripting.asciidoc b/docs/detections/prebuilt-rules/rule-details/execution-with-explicit-credentials-via-scripting.asciidoc
index 870815289a..a1175f5ebf 100644
--- a/docs/detections/prebuilt-rules/rule-details/execution-with-explicit-credentials-via-scripting.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/execution-with-explicit-credentials-via-scripting.asciidoc
@@ -5,58 +5,90 @@ Identifies execution of the security_authtrampoline process via a scripting inte
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://objectivebythesea.com/v2/talks/OBTS_v2_Thomas.pdf
 * https://www.manpagez.com/man/8/security_authtrampoline/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Execution
-* Privilege Escalation
 
-*Version*: 100 (<<execution-with-explicit-credentials-via-scripting-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:"security_authtrampoline" and
-process.parent.name:(osascript or com.apple.automator.runner or sh or
-bash or dash or zsh or python* or Python or perl* or php* or ruby or
-pwsh)
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+ process.name:"security_authtrampoline" and
+ process.parent.name:(osascript or com.apple.automator.runner or sh or bash or dash or zsh or python* or Python or perl* or php* or ruby or pwsh)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -68,8 +100,14 @@ pwsh)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Elevated Execution with Prompt
+** ID: T1548.004
+** Reference URL: https://attack.mitre.org/techniques/T1548/004/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -78,35 +116,3 @@ pwsh)
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[execution-with-explicit-credentials-via-scripting-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:"security_authtrampoline" and
-process.parent.name:(osascript or com.apple.automator.runner or sh or
-bash or dash or zsh or python* or perl* or php* or ruby or pwsh)
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Rule name changed from: Execution with Explicit Credentials via Apple Scripting
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [process where event.type in
-("start", "process_started", "info") and process.name == "osascript"]
-by process.pid [process where event.type in ("start",
-"process_started") and process.name == "security_authtrampoline"] by
-process.ppid
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/expired-or-revoked-driver-loaded.asciidoc b/docs/detections/prebuilt-rules/rule-details/expired-or-revoked-driver-loaded.asciidoc
new file mode 100644
index 0000000000..09bd35eacf
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/expired-or-revoked-driver-loaded.asciidoc
@@ -0,0 +1,75 @@
+[[expired-or-revoked-driver-loaded]]
+=== Expired or Revoked Driver Loaded
+
+Identifies an attempt to load a revoked or expired driver. Adversaries may bring outdated drivers with vulnerabilities to gain code execution in kernel mode or abuse revoked certificates to sign their drivers.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.microsoft.com/en-us/previous-versions/windows/hardware/design/dn653559(v=vs.85)?redirectedfrom=MSDN
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+driver where host.os.type == "windows" and process.pid == 4 and
+  dll.code_signature.status : ("errorExpired", "errorRevoked")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/exploit-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/exploit-detected-elastic-endgame.asciidoc
index ef33486297..38e5409e61 100644
--- a/docs/detections/prebuilt-rules/rule-details/exploit-detected-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/exploit-detected-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame detected an Exploit. Click the Elastic Endgame icon in the event
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,41 +13,53 @@ Elastic Endgame detected an Exploit. Click the Elastic Endgame icon in the event
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
-* Threat Detection
-* Execution
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<exploit-detected-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:detection and (event.action:exploit_event or
-endgame.event_subtype_full:exploit_event)
+[source, js]
 ----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:exploit_event or endgame.event_subtype_full:exploit_event)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -55,8 +67,6 @@ endgame.event_subtype_full:exploit_event)
 ** Name: Execution
 ** ID: TA0002
 ** Reference URL: https://attack.mitre.org/tactics/TA0002/
-
-
 * Tactic:
 ** Name: Privilege Escalation
 ** ID: TA0004
@@ -65,34 +75,3 @@ endgame.event_subtype_full:exploit_event)
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-[[exploit-detected-elastic-endgame-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Formatting only
-
-Version 6 (7.12.1 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Rule name changed from: Exploit - Detected - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Exploit - Detected - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Exploit - Detected - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:exploit_event and endgame.metadata.type:detection
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/exploit-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/exploit-prevented-elastic-endgame.asciidoc
index 6c392bf2dd..fa8aefd7b0 100644
--- a/docs/detections/prebuilt-rules/rule-details/exploit-prevented-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/exploit-prevented-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame prevented an Exploit. Click the Elastic Endgame icon in the even
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,41 +13,53 @@ Elastic Endgame prevented an Exploit. Click the Elastic Endgame icon in the even
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
-* Threat Detection
-* Execution
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<exploit-prevented-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:prevention and (event.action:exploit_event or
-endgame.event_subtype_full:exploit_event)
+[source, js]
 ----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:exploit_event or endgame.event_subtype_full:exploit_event)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -55,8 +67,6 @@ endgame.event_subtype_full:exploit_event)
 ** Name: Execution
 ** ID: TA0002
 ** Reference URL: https://attack.mitre.org/tactics/TA0002/
-
-
 * Tactic:
 ** Name: Privilege Escalation
 ** ID: TA0004
@@ -65,34 +75,3 @@ endgame.event_subtype_full:exploit_event)
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-[[exploit-prevented-elastic-endgame-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Formatting only
-
-Version 6 (7.12.1 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Rule name changed from: Exploit - Prevented - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Exploit - Prevented - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Exploit - Prevented - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:exploit_event and endgame.metadata.type:prevention
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/exporting-exchange-mailbox-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/exporting-exchange-mailbox-via-powershell.asciidoc
index e52e458d68..c164891164 100644
--- a/docs/detections/prebuilt-rules/rule-details/exporting-exchange-mailbox-via-powershell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/exporting-exchange-mailbox-via-powershell.asciidoc
@@ -5,120 +5,128 @@ Identifies the use of the Exchange PowerShell cmdlet, New-MailBoxExportRequest,
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.volexity.com/blog/2020/12/14/dark-halo-leverages-solarwinds-compromise-to-breach-organizations/
 * https://docs.microsoft.com/en-us/powershell/module/exchange/new-mailboxexportrequest?view=exchange-ps
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 111
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Collection
-* Investigation Guide
-* Elastic Endgame
 
-*Version*: 102 (<<exporting-exchange-mailbox-via-powershell-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Legitimate exchange system administration activity.
 
-==== Investigation guide
 
+*Investigating Exporting Exchange Mailbox via PowerShell*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Exporting Exchange Mailbox via PowerShell
+Email mailboxes and their information can be valuable assets for attackers. Company mailboxes often contain sensitive information such as login credentials, intellectual property, financial data, and personal information, making them high-value targets for malicious actors.
+
+The `New-MailBoxExportRequest` cmdlet is used to begin the process of exporting contents of a primary mailbox or archive to a .pst file. Note that this is done on a per-mailbox basis and this cmdlet is available only in on-premises Exchange.
 
-The `New-MailBoxExportRequest` cmdlet is used to begin the process of exporting contents of a primary mailbox or archive
-to a .pst file. Note that this is done on a per-mailbox basis and this cmdlet is available only in on-premises Exchange.
+Attackers can abuse this functionality in preparation for exfiltrating contents, which is likely to contain sensitive and strategic data.
 
-Attackers can abuse this functionality in preparation for exfiltrating contents, which is likely to contain sensitive
-and strategic data.
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Investigate the export operation:
   - Identify the user account that performed the action and whether it should perform this kind of action.
   - Contact the account owner and confirm whether they are aware of this activity.
   - Check if this operation was approved and performed according to the organization's change management policy.
   - Retrieve the operation status and use the `Get-MailboxExportRequest` cmdlet to review previous requests.
-  - By default, no group in Exchange has the privilege to import or export mailboxes. Investigate administrators that
-  assigned the "Mailbox Import Export" privilege for abnormal activity.
-- Investigate if there is a significant quantity of export requests in the alert timeframe. This operation is done on
-a per-mailbox basis and can be part of a mass export.
+  - By default, no group in Exchange has the privilege to import or export mailboxes. Investigate administrators that assigned the "Mailbox Import Export" privilege for abnormal activity.
+- Investigate if there is a significant quantity of export requests in the alert timeframe. This operation is done on a per-mailbox basis and can be part of a mass export.
 - If the operation was completed successfully:
   - Check if the file is on the path specified in the command.
   - Investigate if the file was compressed, archived, or retrieved by the attacker for exfiltration.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity
-and it is done with proper approval.
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity and it is done with proper approval.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - If the involved host is not the Exchange server, isolate the host to prevent further post-compromise behavior.
 - Use the `Remove-MailboxExportRequest` cmdlet to remove fully or partially completed export requests.
 - Prioritize cases that involve personally identifiable information (PII) or other classified data.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Review the privileges of users with the "Mailbox Import Export" privilege to ensure that the least privilege principle
-is being followed.
-- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system,
-persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Review the privileges of users with the "Mailbox Import Export" privilege to ensure that the least privilege principle is being followed.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name:
-("powershell.exe", "pwsh.exe", "powershell_ise.exe") and process.args
-: "New-MailboxExportRequest*"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name: ("powershell.exe", "pwsh.exe", "powershell_ise.exe") and 
+  process.command_line : ("*MailboxExportRequest*", "*-Mailbox*-ContentFilter*")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -130,48 +138,23 @@ process where event.type == "start" and process.name:
 ** Name: Data from Local System
 ** ID: T1005
 ** Reference URL: https://attack.mitre.org/techniques/T1005/
-
-[[exporting-exchange-mailbox-via-powershell-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name: ("powershell.exe", "pwsh.exe", "powershell_ise.exe") and
-process.args : "New-MailboxExportRequest*"
-----------------------------------
-
-Version 10 (8.4.0 release)::
-* Formatting only
-
-Version 8 (8.3.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name: ("powershell.exe", "pwsh.exe") and process.args : "New-
-MailboxExportRequest*"
-----------------------------------
-
-Version 4 (7.15.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Technique:
+** Name: Email Collection
+** ID: T1114
+** Reference URL: https://attack.mitre.org/techniques/T1114/
+* Sub-technique:
+** Name: Remote Email Collection
+** ID: T1114.002
+** Reference URL: https://attack.mitre.org/techniques/T1114/002/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/external-alerts.asciidoc b/docs/detections/prebuilt-rules/rule-details/external-alerts.asciidoc
index bb695c7dfe..3471cdff27 100644
--- a/docs/detections/prebuilt-rules/rule-details/external-alerts.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/external-alerts.asciidoc
@@ -5,7 +5,7 @@ Generates a detection alert for each external alert written to the configured in
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * apm-*-transaction*
 * traces-apm*
@@ -19,60 +19,50 @@ Generates a detection alert for each external alert written to the configured in
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Network
-* Windows
-* APM
-* macOS
-* Linux
+*Tags*: 
 
-*Version*: 100 (<<external-alerts-history, version history>>)
+* OS: Windows
+* Data Source: APM
+* OS: macOS
+* OS: Linux
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
 
+==== Setup
 
-[source,js]
-----------------------------------
-event.kind:alert and not event.module:(endgame or endpoint)
-----------------------------------
 
 
-[[external-alerts-history]]
-==== Rule version history
+*Setup*
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 5 (8.4.0 release)::
-* Formatting only
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
 
-Version 4 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and not event.module:(endgame or endpoint)
-----------------------------------
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
 
-Version 3 (7.12.0 release)::
-* Formatting only
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
 
-Version 2 (7.10.0 release)::
-* Formatting only
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
 
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:alert and not event.module:(endgame or endpoint or cloud_defend)
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/external-ip-lookup-from-non-browser-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/external-ip-lookup-from-non-browser-process.asciidoc
index c00d908929..c51600dfce 100644
--- a/docs/detections/prebuilt-rules/rule-details/external-ip-lookup-from-non-browser-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/external-ip-lookup-from-non-browser-process.asciidoc
@@ -5,131 +5,149 @@ Identifies domains commonly used by adversaries for post-exploitation IP lookups
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.network-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://community.jisc.ac.uk/blogs/csirt/article/trickbot-analysis-and-mitigation
 * https://www.cybereason.com/blog/dropping-anchor-from-a-trickbot-infection-to-the-discovery-of-the-anchor-malware
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
 
-*Version*: 102 (<<external-ip-lookup-from-non-browser-process-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.10.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-If the domains listed in this rule are used as part of an authorized workflow, this rule will be triggered by those events. Validate that this is expected activity and tune the rule to fit your environment variables.
 
-==== Investigation guide
 
+*Investigating External IP Lookup from Non-Browser Process*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating External IP Lookup from Non-Browser Process
+After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
+
+This rule looks for connections to known IP lookup services through non-browser processes or non-installed programs. Using only the IP address of the compromised system, attackers can obtain valuable information such as the system's geographic location, the company that owns the IP, whether the system is cloud-hosted, and more.
 
-After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps.
-This can happen by running commands to enumerate network resources, users, connections, files, and installed security
-software.
 
-This rule looks for connections to known IP lookup services through non-browser processes or non-installed programs.
-Using only the IP address of the compromised system, attackers can obtain valuable information such as the system's
-geographic location, the company that owns the IP, whether the system is cloud-hosted, and more.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file
-modifications, and any spawned child processes.
+- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
 
-### False positive analysis
 
-- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify
-suspicious activity related to the user or host, such alerts can be dismissed.
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination
-of user and command line conditions.
+*False positive analysis*
+
+
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Use the data collected through the analysis to investigate other machines affected in the environment.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-network where network.protocol == "dns" and process.name != null
-and user.id not in ("S-1-5-19", "S-1-5-20") and event.action ==
-"lookup_requested" and /* Add new external IP lookup services here
-*/ dns.question.name : ( "*api.ipify.org",
-"*freegeoip.app", "*checkip.amazonaws.com",
-"*checkip.dyndns.org", "*freegeoip.app",
-"*icanhazip.com", "*ifconfig.*", "*ipecho.net",
-"*ipgeoapi.com", "*ipinfo.io", "*ip.anysrc.net",
-"*myexternalip.com", "*myipaddress.com",
-"*showipaddress.com", "*whatismyipaddress.com",
-"*wtfismyip.com", "*ipapi.co", "*ip-lookup.net",
-"*ipstack.com" ) and /* Insert noisy false positives here */
-not process.executable : ( "?:\\Program Files\\*.exe",
-"?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\WWAHost.exe",
-"?:\\Windows\\System32\\smartscreen.exe",
-"?:\\Windows\\System32\\MicrosoftEdgeCP.exe",
-"?:\\ProgramData\\Microsoft\\Windows
-Defender\\Platform\\*\\MsMpEng.exe", "?:\\Users\\*\\AppData\\Loc
-al\\Google\\Chrome\\Application\\chrome.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Fiddler\\Fiddler.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe",
-"?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\OneDrive.exe"
-)
+[source, js]
 ----------------------------------
+network where host.os.type == "windows" and network.protocol == "dns" and
+    process.name != null and user.id not in ("S-1-5-19", "S-1-5-20") and
+    event.action == "lookup_requested" and
+    /* Add new external IP lookup services here */
+    dns.question.name :
+    (
+        "*api.ipify.org",
+        "*freegeoip.app",
+        "*checkip.amazonaws.com",
+        "*checkip.dyndns.org",
+        "*freegeoip.app",
+        "*icanhazip.com",
+        "*ifconfig.*",
+        "*ipecho.net",
+        "*ipgeoapi.com",
+        "*ipinfo.io",
+        "*ip.anysrc.net",
+        "*myexternalip.com",
+        "*myipaddress.com",
+        "*showipaddress.com",
+        "*whatismyipaddress.com",
+        "*wtfismyip.com",
+        "*ipapi.co",
+        "*ip-lookup.net",
+        "*ipstack.com"
+    ) and
+    /* Insert noisy false positives here */
+    not
+    (
+      (
+        process.executable : (
+            "?:\\Program Files\\*.exe",
+            "?:\\Program Files (x86)\\*.exe",
+            "?:\\Windows\\Prey\\versions\\*\\bin\\node.exe",
+            "?:\\Windows\\System32\\WWAHost.exe",
+            "?:\\Windows\\System32\\smartscreen.exe",
+            "?:\\Windows\\System32\\MicrosoftEdgeCP.exe",
+            "?:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\*\\MsMpEng.exe",
+            "?:\\Users\\*\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe",
+            "?:\\Users\\*\\AppData\\Local\\Programs\\Fiddler\\Fiddler.exe",
+            "?:\\Users\\*\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe",
+            "?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\OneDrive.exe"
+        ) and process.code_signature.trusted == true
+      ) or
+      (
+        (process.name : "Evernote.exe" and process.code_signature.subject_name : "Evernote Corporation" and process.code_signature.trusted == true) or
+        (process.name : "firefox.exe" and process.code_signature.subject_name : "Mozilla Corporation" and process.code_signature.trusted == true) or
+        (process.name : "Loom.exe" and process.code_signature.subject_name : "Loom, Inc." and process.code_signature.trusted == true) or
+        (process.name : "opera.exe" and process.code_signature.subject_name : "Opera Norway AS" and process.code_signature.trusted == true) or
+        (process.name : "brave.exe" and process.code_signature.subject_name : "Brave Software, Inc." and process.code_signature.trusted == true) or
+        (process.name : "vivaldi.exe" and process.code_signature.subject_name : "Vivaldi Technologies AS" and process.code_signature.trusted == true)
+      )
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -138,78 +156,14 @@ al\\Google\\Chrome\\Application\\chrome.exe",
 ** ID: TA0007
 ** Reference URL: https://attack.mitre.org/tactics/TA0007/
 * Technique:
+** Name: System Network Configuration Discovery
+** ID: T1016
+** Reference URL: https://attack.mitre.org/techniques/T1016/
+* Sub-technique:
+** Name: Internet Connection Discovery
+** ID: T1016.001
+** Reference URL: https://attack.mitre.org/techniques/T1016/001/
+* Technique:
 ** Name: System Location Discovery
 ** ID: T1614
 ** Reference URL: https://attack.mitre.org/techniques/T1614/
-
-[[external-ip-lookup-from-non-browser-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 10 (8.4.0 release)::
-* Formatting only
-
-Version 8 (8.3.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (7.15.0 release)::
-* Rule name changed from: External IP Lookup fron Non-Browser Process
-Version 5 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network where network.protocol == "dns" and process.name != null
-and user.id not in ("S-1-5-19", "S-1-5-20") and event.action ==
-"lookup_requested" and /* Add new external IP lookup services here
-*/ dns.question.name : ( "*api.ipify.org",
-"*freegeoip.app", "*checkip.amazonaws.com",
-"*checkip.dyndns.org", "*freegeoip.app",
-"*icanhazip.com", "*ifconfig.*", "*ipecho.net",
-"*ipgeoapi.com", "*ipinfo.io", "*ip.anysrc.net",
-"*myexternalip.com", "*myipaddress.com",
-"*showipaddress.com", "*whatismyipaddress.com",
-"*wtfismyip.com" ) and /* Insert noisy false positives here */
-not process.executable : ( "?:\\Program Files\\*.exe",
-"?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\WWAHost.exe",
-"?:\\Windows\\System32\\smartscreen.exe",
-"?:\\Windows\\System32\\MicrosoftEdgeCP.exe",
-"?:\\ProgramData\\Microsoft\\Windows
-Defender\\Platform\\*\\MsMpEng.exe", "?:\\Users\\*\\AppData\\Loc
-al\\Google\\Chrome\\Application\\chrome.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Fiddler\\Fiddler.exe",
-"?:\\Users\\*\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe",
-"?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\OneDrive.exe"
-)
-----------------------------------
-
-Version 4 (7.13.0 release)::
-* Rule name changed from: Public IP Reconnaissance Activity
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network AND event.type:connection AND
-server.domain:(ipecho.net OR ipinfo.io OR ifconfig.co OR ifconfig.me
-OR icanhazip.com OR myexternalip.com OR api.ipify.org OR
-bot.whatismyipaddress.com OR ip.anysrc.net OR wtfismyip.com) AND NOT
-http.response.status_code:302 AND status:OK AND NOT
-_exists_:http.request.referrer
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/external-user-added-to-google-workspace-group.asciidoc b/docs/detections/prebuilt-rules/rule-details/external-user-added-to-google-workspace-group.asciidoc
new file mode 100644
index 0000000000..c1f92def32
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/external-user-added-to-google-workspace-group.asciidoc
@@ -0,0 +1,141 @@
+[[external-user-added-to-google-workspace-group]]
+=== External User Added to Google Workspace Group
+
+Detects an external Google Workspace user account being added to an existing group. Adversaries may add external user accounts as a means to intercept shared files or emails with that specific group.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-google_workspace*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://support.google.com/a/answer/33329
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Identity and Access Audit
+* Tactic: Initial Access
+* Resources: Investigation Guide
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating External User Added to Google Workspace Group*
+
+
+Google Workspace groups allow organizations to assign specific users to a group that can share resources. Application specific roles can be manually set for each group, but if not inherit permissions from the top-level organizational unit.
+
+Threat actors may use phishing techniques and container-bound scripts to add external Google accounts to an organization's groups with editorial privileges. As a result, the user account is unable to manually access the organization's resources, settings and files, but will receive anything shared to the group. As a result, confidential information could be leaked or perhaps documents shared with editorial privileges be weaponized for further intrusion.
+
+This rule identifies when an external user account is added to an organization's groups where the domain name of the target does not match the Google Workspace domain.
+
+
+*Possible investigation steps*
+
+- Identify user account(s) associated by reviewing `user.name` or `user.email` in the alert
+  - The `user.target.email` field contains the user added to the groups
+  - The `group.name` field contains the group the target user was added to
+- Identify specific application settings given to the group which may indicate motive for the external user joining a particular group
+- With the user identified, verify administrative privileges are scoped properly to add external users to the group
+  - Unauthorized actions may indicate the `user.email` account has been compromised or leveraged to add an external user
+- To identify other users in this group, search for `event.action: "ADD_GROUP_MEMBER"`
+  - It is important to understand if external users with `@gmail.com` are expected to be added to this group based on historical references
+- Review Gmail logs where emails were sent to and from the `group.name` value
+  - This may indicate potential internal spearphishing
+
+
+*False positive analysis*
+
+- With the user account whom added the new user, verify this action was intentional
+- Verify that the target whom was added to the group is expected to have access to the organization's resources and data
+- If other members have been added to groups that are external, this may indicate historically that this action is expected
+
+
+*Response and remediation*
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Reactivate multi-factor authentication for the user.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security defaults https://cloud.google.com/security-command-center/docs/how-to-investigate-threats[provided by Google].
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
+
+- As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
+- This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
+- To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
+- By default, `var.interval` is set to 2 hours (2h). Consider changing this interval to a lower value, such as 10 minutes (10m).
+- See the following references for further information:
+  - https://support.google.com/a/answer/7061566
+  - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
+
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+iam where event.dataset == "google_workspace.admin" and event.action == "ADD_GROUP_MEMBER" and
+  not endsWith(user.target.email, user.target.group.domain)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Cloud Accounts
+** ID: T1078.004
+** Reference URL: https://attack.mitre.org/techniques/T1078/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-and-directory-permissions-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-and-directory-permissions-modification.asciidoc
new file mode 100644
index 0000000000..185eb4a851
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/file-and-directory-permissions-modification.asciidoc
@@ -0,0 +1,73 @@
+[[file-and-directory-permissions-modification]]
+=== File and Directory Permissions Modification
+
+Identifies the change of permissions/ownership of files/folders through built-in Windows utilities. Threat actors may require permission modification of files/folders to change, modify or delete them.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and host.os.type == "windows" and
+(
+  ((process.name: "icacls.exe" or process.pe.original_file_name == "iCACLS.EXE") and process.args: ("*:F", "/reset", "/setowner", "*grant*")) or
+  ((process.name: "cacls.exe" or process.pe.original_file_name == "CACLS.EXE") and process.args: ("/g", "*:f")) or
+  ((process.name: "takeown.exe" or process.pe.original_file_name == "takeown.exe") and process.args: ("/F")) or
+  ((process.name: "attrib.exe" or process.pe.original_file_name== "ATTRIB.EXE") and process.args: "-r")
+) and not user.id : "S-1-5-18" and
+not (
+  process.args : ("C:\\ProgramData\\Lenovo\\*", "C:\\ProgramData\\Adobe\\*", "C:\\ProgramData\\ASUS\\ASUS*")
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: File and Directory Permissions Modification
+** ID: T1222
+** Reference URL: https://attack.mitre.org/techniques/T1222/
+* Sub-technique:
+** Name: Windows File and Directory Permissions Modification
+** ID: T1222.001
+** Reference URL: https://attack.mitre.org/techniques/T1222/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-compressed-or-archived-into-common-format.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-compressed-or-archived-into-common-format.asciidoc
new file mode 100644
index 0000000000..8c5ed1501e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/file-compressed-or-archived-into-common-format.asciidoc
@@ -0,0 +1,168 @@
+[[file-compressed-or-archived-into-common-format]]
+=== File Compressed or Archived into Common Format
+
+Detects files being compressed or archived into common formats. This is a common technique used to obfuscate files to evade detection or to staging data for exfiltration.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 1000
+
+*References*: 
+
+* https://en.wikipedia.org/wiki/List_of_file_signatures
+
+*Tags*: 
+
+* Data Source: Elastic Defend
+* Domain: Endpoint
+* OS: macOS
+* OS: Windows
+* Tactic: Collection
+* Rule Type: BBR
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.type in ("creation", "change") and process.executable != null and not user.id : ("S-1-5-18", "S-1-5-17") and
+ file.Ext.header_bytes : (
+                          /* compression formats */
+                          "1F9D*",             /* tar zip, tar.z (Lempel-Ziv-Welch algorithm) */
+                          "1FA0*",             /* tar zip, tar.z (LZH algorithm) */
+                          "425A68*",           /* Bzip2 */
+                          "524E4301*",         /* Rob Northen Compression */
+                          "524E4302*",         /* Rob Northen Compression */
+                          "4C5A4950*",         /* LZIP */
+                          "504B0*",            /* ZIP */
+                          "526172211A07*",     /* RAR compressed */
+                          "44434D0150413330*", /* Windows Update Binary Delta Compression file */
+                          "50413330*",         /* Windows Update Binary Delta Compression file */
+                          "377ABCAF271C*",     /* 7-Zip */
+                          "1F8B*",             /* GZIP */
+                          "FD377A585A00*",     /* XZ, tar.xz */
+                          "7801*",	           /* zlib: No Compression (no preset dictionary) */
+                          "785E*",	           /* zlib: Best speed (no preset dictionary) */
+                          "789C*",	           /* zlib: Default Compression (no preset dictionary) */
+                          "78DA*", 	           /* zlib: Best Compression (no preset dictionary) */
+                          "7820*",	           /* zlib: No Compression (with preset dictionary) */
+                          "787D*",	           /* zlib: Best speed (with preset dictionary) */
+                          "78BB*",	           /* zlib: Default Compression (with preset dictionary) */
+                          "78F9*",	           /* zlib: Best Compression (with preset dictionary) */
+                          "62767832*",         /* LZFSE */
+                          "28B52FFD*",         /* Zstandard, zst */
+                          "5253564B44415441*", /* QuickZip rs compressed archive */
+                          "2A2A4143452A2A*",   /* ACE */
+
+                          /* archive formats */
+                          "2D686C302D*",       /* lzh */
+                          "2D686C352D*",       /* lzh */
+                          "303730373037*",     /* cpio */
+                          "78617221*",         /* xar */
+                          "4F4152*",           /* oar */
+                          "49536328*"          /* cab archive */
+ ) and
+ not (
+   (
+     process.name : "firefox.exe" and
+     process.code_signature.subject_name : "Mozilla Corporation" and process.code_signature.trusted == true
+   ) or
+   (
+     process.name : "wazuh-agent.exe" and
+     process.code_signature.subject_name : "Wazuh, Inc" and process.code_signature.trusted == true and
+     file.name : ("ossec-*.log.gz", "tmp-entry.gz", "tmp-entry", "last-entry.gz")
+   ) or
+   (
+     process.name : ("excel.exe", "winword.exe", "powerpnt.exe") and
+     process.code_signature.subject_name : "Microsoft Corporation" and process.code_signature.trusted == true
+   ) or
+   (
+     process.name : "OneDrive.exe" and
+     process.code_signature.subject_name : "Microsoft Corporation" and process.code_signature.trusted == true and
+     (
+      file.extension : ("xlsx", "docx", "pptx", "xlsm") or
+      file.path : "?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\logs\\*"
+     )
+   ) or
+   (
+     process.name : "Dropbox.exe" and
+     process.code_signature.subject_name : "Dropbox, Inc" and process.code_signature.trusted == true and
+     file.name : "store.bin"
+   ) or
+   (
+     process.name : "DellSupportAssistRemedationService.exe" and
+     process.code_signature.subject_name : "Dell Inc" and process.code_signature.trusted == true and
+     file.extension : "manifest"
+   ) or
+   (
+     process.name : "w3wp.exe" and
+     process.code_signature.subject_name : "Microsoft Windows" and process.code_signature.trusted == true and
+     file.path : "?:\\inetpub\\temp\\IIS Temporary Compressed Files\\*"
+   )
+ )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Archive Collected Data
+** ID: T1560
+** Reference URL: https://attack.mitre.org/techniques/T1560/
+* Sub-technique:
+** Name: Archive via Utility
+** ID: T1560.001
+** Reference URL: https://attack.mitre.org/techniques/T1560/001/
+* Technique:
+** Name: Data Staged
+** ID: T1074
+** Reference URL: https://attack.mitre.org/techniques/T1074/
+* Sub-technique:
+** Name: Local Data Staging
+** ID: T1074.001
+** Reference URL: https://attack.mitre.org/techniques/T1074/001/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Data Encoding
+** ID: T1132
+** Reference URL: https://attack.mitre.org/techniques/T1132/
+* Sub-technique:
+** Name: Standard Encoding
+** ID: T1132.001
+** Reference URL: https://attack.mitre.org/techniques/T1132/001/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Obfuscated Files or Information
+** ID: T1027
+** Reference URL: https://attack.mitre.org/techniques/T1027/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-creation-execution-and-self-deletion-in-suspicious-directory.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-creation-execution-and-self-deletion-in-suspicious-directory.asciidoc
new file mode 100644
index 0000000000..e5d9e4a768
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/file-creation-execution-and-self-deletion-in-suspicious-directory.asciidoc
@@ -0,0 +1,109 @@
+[[file-creation-execution-and-self-deletion-in-suspicious-directory]]
+=== File Creation, Execution and Self-Deletion in Suspicious Directory
+
+This rule monitors for the creation of a file, followed by its execution and self-deletion in a short timespan within a directory often used for malicious purposes by threat actors. This behavior is often used by malware to execute malicious code and delete itself to hide its tracks.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, user.id with maxspan=1m
+  [file where host.os.type == "linux" and event.action == "creation" and 
+   process.name in ("curl", "wget", "fetch", "ftp", "sftp", "scp", "rsync", "ld") and 
+   file.path : ("/dev/shm/*", "/run/shm/*", "/tmp/*", "/var/tmp/*",
+     "/run/*", "/var/run/*", "/var/www/*", "/proc/*/fd/*")] by file.name
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+   process.parent.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")] by process.name
+  [file where host.os.type == "linux" and event.action == "deletion" and not process.name in ("rm", "ld") and 
+   file.path : ("/dev/shm/*", "/run/shm/*", "/tmp/*", "/var/tmp/*",
+     "/run/*", "/var/run/*", "/var/www/*", "/proc/*/fd/*")] by file.name
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-creation-time-changed.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-creation-time-changed.asciidoc
new file mode 100644
index 0000000000..3611c2af54
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/file-creation-time-changed.asciidoc
@@ -0,0 +1,84 @@
+[[file-creation-time-changed]]
+=== File Creation Time Changed
+
+Identifies modification of a file creation time. Adversaries may modify file time attributes to blend malicious content with existing files. Timestomping is a technique that modifies the timestamps of a file often to mimic files that are in trusted directories.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.sysmon_operational-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Sysmon
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.code : "2" and
+
+ /* Requires Sysmon EventID 2 - File creation time change */
+ event.action : "File creation time changed*" and 
+ 
+ not process.executable : 
+          ("?:\\Program Files\\*", 
+           "?:\\Program Files (x86)\\*", 
+           "?:\\Windows\\system32\\cleanmgr.exe",
+           "?:\\Windows\\system32\\msiexec.exe", 
+           "?:\\Windows\\syswow64\\msiexec.exe", 
+           "?:\\Windows\\system32\\svchost.exe", 
+           "?:\\WINDOWS\\system32\\backgroundTaskHost.exe",
+           "?:\\Users\\*\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe", 
+           "?:\\Users\\*\\AppData\\Local\\Mozilla Firefox\\firefox.exe",
+           "?:\\Users\\*\\AppData\\Local\\slack\\app-*\\slack.exe", 
+           "?:\\Users\\*\\AppData\\Local\\GitHubDesktop\\app-*\\GitHubDesktop.exe",
+           "?:\\Users\\*\\AppData\\Local\\Microsoft\\Teams\\current\\Teams.exe", 
+           "?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\OneDrive.exe") and 
+ not file.extension : ("temp", "tmp", "~tmp", "xml", "newcfg") and not user.name : ("SYSTEM", "Local Service", "Network Service") and
+ not file.name : ("LOG", "temp-index", "license.rtf", "iconcache_*.db")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indicator Removal
+** ID: T1070
+** Reference URL: https://attack.mitre.org/techniques/T1070/
+* Sub-technique:
+** Name: Timestomp
+** ID: T1070.006
+** Reference URL: https://attack.mitre.org/techniques/T1070/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-deletion-via-shred.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-deletion-via-shred.asciidoc
index acee2e3117..36b9e7553d 100644
--- a/docs/detections/prebuilt-rules/rule-details/file-deletion-via-shred.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/file-deletion-via-shred.asciidoc
@@ -3,94 +3,102 @@
 
 Malware or other files dropped or created on a system by an adversary may leave traces behind as to what was done within a network and how. Adversaries may remove these files over the course of an intrusion to keep their footprint low or remove them at the end as part of the post-intrusion cleanup process.
 
-*Rule type*: query
+*Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<file-deletion-via-shred-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
 
-*Added ({stack} release)*: 7.8.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
 
+==== Setup
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:shred and process.args:("-u" or "--remove" or "-z" or "
---zero")
-----------------------------------
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Indicator Removal on Host
-** ID: T1070
-** Reference URL: https://attack.mitre.org/techniques/T1070/
 
-[[file-deletion-via-shred-history]]
-==== Rule version history
+*Elastic Defend Integration Setup*
 
-Version 100 (8.5.0 release)::
-* Formatting only
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-Version 8 (8.4.0 release)::
-* Formatting only
 
-Version 7 (7.12.0 release)::
-* Formatting only
+*Prerequisite Requirements:*
 
-Version 6 (7.11.2 release)::
-* Formatting only
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 5 (7.11.0 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
 
-Version 3 (7.9.1 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:(executed or process_started) and process.name:shred and
-process.args:("-u" or "--remove" or "-z" or "--zero")
+process where host.os.type == "linux" and event.type == "start" and process.name == "shred" and process.args in (
+  "-u", "--remove", "-z", "--zero"
+) and not process.parent.name == "logrotate"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indicator Removal
+** ID: T1070
+** Reference URL: https://attack.mitre.org/techniques/T1070/
+* Sub-technique:
+** Name: File Deletion
+** ID: T1070.004
+** Reference URL: https://attack.mitre.org/techniques/T1070/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-made-executable-via-chmod-inside-a-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-made-executable-via-chmod-inside-a-container.asciidoc
new file mode 100644
index 0000000000..68d7a323db
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/file-made-executable-via-chmod-inside-a-container.asciidoc
@@ -0,0 +1,76 @@
+[[file-made-executable-via-chmod-inside-a-container]]
+=== File Made Executable via Chmod Inside A Container
+
+This rule detects when chmod is used to add the execute permission to a file inside a container. Modifying file permissions to make a file executable could indicate malicious activity, as an attacker may attempt to run unauthorized or malicious code inside the container.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Defense Evasion
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where container.id: "*" and event.type in ("change", "creation") and
+
+/*account for tools that execute utilities as a subprocess, in this case the target utility name will appear as a process arg*/
+(process.name : "chmod" or process.args : "chmod") and 
+process.args : ("*x*", "777", "755", "754", "700") and not process.args: "-x"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: File and Directory Permissions Modification
+** ID: T1222
+** Reference URL: https://attack.mitre.org/techniques/T1222/
+* Sub-technique:
+** Name: Linux and Mac File and Directory Permissions Modification
+** ID: T1222.002
+** Reference URL: https://attack.mitre.org/techniques/T1222/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-made-immutable-by-chattr.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-made-immutable-by-chattr.asciidoc
index 42621f0486..b4c47f7d03 100644
--- a/docs/detections/prebuilt-rules/rule-details/file-made-immutable-by-chattr.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/file-made-immutable-by-chattr.asciidoc
@@ -5,59 +5,111 @@ Detects a file being made immutable using the chattr binary. Making a file immut
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 33
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<file-made-immutable-by-chattr-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Custom Ingest Pipeline*
+
+For versions <8.2, you need to add a custom ingest pipeline to populate `event.ingested` with @timestamp for non-elastic-agent indexes, like auditbeats/filebeat/winlogbeat etc. For more details to add a custom ingest pipeline refer to the https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html[guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and user.name == "root" and
-process.executable : "/usr/bin/chattr" and process.args : ("-*i*",
-"+*i*") and not process.parent.executable: "/lib/systemd/systemd"
+[source, js]
 ----------------------------------
+process where host.os.type == "linux" and event.type == "start" and user.id == "0" and
+  process.executable : "/usr/bin/chattr" and process.args : ("-*i*", "+*i*") and
+  not process.parent.executable: ("/lib/systemd/systemd", "/usr/local/uems_agent/bin/*", "/usr/lib/systemd/systemd") and
+  not process.parent.name in ("systemd", "cf-agent", "ntpdate", "xargs", "px", "preinst", "auth")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -69,10 +121,7 @@ process.executable : "/usr/bin/chattr" and process.args : ("-*i*",
 ** Name: File and Directory Permissions Modification
 ** ID: T1222
 ** Reference URL: https://attack.mitre.org/techniques/T1222/
-
-[[file-made-immutable-by-chattr-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Linux and Mac File and Directory Permissions Modification
+** ID: T1222.002
+** Reference URL: https://attack.mitre.org/techniques/T1222/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-or-directory-deletion-command.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-or-directory-deletion-command.asciidoc
new file mode 100644
index 0000000000..a5b58133de
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/file-or-directory-deletion-command.asciidoc
@@ -0,0 +1,78 @@
+[[file-or-directory-deletion-command]]
+=== File or Directory Deletion Command
+
+This rule identifies the execution of commands that can be used to delete files and directories. Adversaries may delete files and directories on a host system, such as logs, browser history, or malware.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and 
+(
+  (process.name: "rundll32.exe" and process.args: "*InetCpl.cpl,Clear*") or 
+  (process.name: "reg.exe" and process.args:"delete") or 
+  (
+    process.name: "cmd.exe" and process.args: ("*rmdir*", "*rm *", "rm") and
+    not process.args : (
+          "*\\AppData\\Local\\Microsoft\\OneDrive\\*",
+          "*\\AppData\\Local\\Temp\\DockerDesktop\\*",
+          "*\\AppData\\Local\\Temp\\Report.*",
+          "*\\AppData\\Local\\Temp\\*.PackageExtraction"
+    )
+  ) or
+  (process.name: "powershell.exe" and process.args: ("*rmdir", "rm", "rd", "*Remove-Item*", "del", "*]::Delete(*"))
+) and not user.id : "S-1-5-18"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indicator Removal
+** ID: T1070
+** Reference URL: https://attack.mitre.org/techniques/T1070/
+* Sub-technique:
+** Name: File Deletion
+** ID: T1070.004
+** Reference URL: https://attack.mitre.org/techniques/T1070/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-permission-modification-in-writable-directory.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-permission-modification-in-writable-directory.asciidoc
index d2d6f2b3b6..1b84fa945a 100644
--- a/docs/detections/prebuilt-rules/rule-details/file-permission-modification-in-writable-directory.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/file-permission-modification-in-writable-directory.asciidoc
@@ -3,97 +3,112 @@
 
 Identifies file permission modifications in common writable directories by a non-root user. Adversaries often drop files or payloads into a writable directory and change permissions prior to execution.
 
-*Rule type*: query
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<file-permission-modification-in-writable-directory-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.8.0
+*Version*: 210
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Certain programs or applications may modify files or change ownership in writable directories. These can be exempted by username.
+==== Setup
 
-==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:(chmod or chown or chattr or chgrp) and
-process.working_directory:(/tmp or /var/tmp or /dev/shm) and not
-user.name:root
-----------------------------------
+*Setup*
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: File and Directory Permissions Modification
-** ID: T1222
-** Reference URL: https://attack.mitre.org/techniques/T1222/
 
-[[file-permission-modification-in-writable-directory-history]]
-==== Rule version history
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 7 (8.4.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
 
-Version 6 (7.12.0 release)::
-* Formatting only
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Version 5 (7.11.2 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Formatting only
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
 
-Version 3 (7.9.1 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:executed and process.name:(chmod or chown or chattr or
-chgrp) and process.working_directory:(/tmp or /var/tmp or /dev/shm)
-and not user.name:root
+host.os.type:linux and event.category:process and event.type:start and
+process.name:(chattr or chgrp or chmod or chown) and process.working_directory:(/dev/shm or /tmp or /var/tmp) and
+not process.parent.name:(apt-key or update-motd-updates-available)
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: File and Directory Permissions Modification
+** ID: T1222
+** Reference URL: https://attack.mitre.org/techniques/T1222/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-staged-in-root-folder-of-recycle-bin.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-staged-in-root-folder-of-recycle-bin.asciidoc
new file mode 100644
index 0000000000..9ae417878a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/file-staged-in-root-folder-of-recycle-bin.asciidoc
@@ -0,0 +1,67 @@
+[[file-staged-in-root-folder-of-recycle-bin]]
+=== File Staged in Root Folder of Recycle Bin
+
+Identifies files written to the root of the Recycle Bin folder instead of subdirectories. Adversaries may place files in the root of the Recycle Bin in preparation for exfiltration or to evade defenses.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and
+  file.path : "?:\\$RECYCLE.BIN\\*" and
+  not file.path : "?:\\$RECYCLE.BIN\\*\\*" and
+  not file.name : "desktop.ini"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Data Staged
+** ID: T1074
+** Reference URL: https://attack.mitre.org/techniques/T1074/
+* Sub-technique:
+** Name: Local Data Staging
+** ID: T1074.001
+** Reference URL: https://attack.mitre.org/techniques/T1074/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-system-debugger-launched-inside-a-privileged-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-system-debugger-launched-inside-a-privileged-container.asciidoc
new file mode 100644
index 0000000000..41bc4db24d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/file-system-debugger-launched-inside-a-privileged-container.asciidoc
@@ -0,0 +1,65 @@
+[[file-system-debugger-launched-inside-a-privileged-container]]
+=== File System Debugger Launched Inside a Privileged Container
+
+This rule detects the use of the built-in Linux DebugFS utility from inside a privileged container. DebugFS is a special file system debugging utility which supports reading and writing directly from a hard drive device. When launched inside a privileged container, a container deployed with all the capabilities of the host machine, an attacker can access sensitive host level files which could be used for further privilege escalation and container escapes to the host machine.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://cyberark.wistia.com/medias/ygbzkzx93q?wvideo=ygbzkzx93q
+* https://book.hacktricks.xyz/linux-hardening/privilege-escalation/docker-security/docker-breakout-privilege-escalation#privileged
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.module == "cloud_defend" and     
+  event.type == "start" and process.name == "debugfs" and 
+  process.args : "/dev/sd*" and not process.args == "-R" and
+  container.security_context.privileged == true
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Escape to Host
+** ID: T1611
+** Reference URL: https://attack.mitre.org/techniques/T1611/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-transfer-or-listener-established-via-netcat.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-transfer-or-listener-established-via-netcat.asciidoc
index f8782631f1..2db3ddbbf8 100644
--- a/docs/detections/prebuilt-rules/rule-details/file-transfer-or-listener-established-via-netcat.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/file-transfer-or-listener-established-via-netcat.asciidoc
@@ -5,7 +5,7 @@ A netcat process is engaging in network activity on a Linux host. Netcat is ofte
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,13 +14,13 @@ A netcat process is engaging in network activity on a Linux host. Netcat is ofte
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * http://pentestmonkey.net/cheat-sheet/shells/reverse-shell-cheat-sheet
 * https://www.sans.org/security-resources/sec560/netcat_cheat_sheet_v1.pdf
@@ -29,182 +29,164 @@ A netcat process is engaging in network activity on a Linux host. Netcat is ofte
 * https://null-byte.wonderhowto.com/how-to/hack-like-pro-use-netcat-swiss-army-knife-hacking-tools-0148657/
 * https://levelup.gitconnected.com/ethical-hacking-part-15-netcat-nc-and-netcat-f6a8f7df43fd
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 110
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Execution
-* Investigation Guide
 
-*Version*: 102 (<<file-transfer-or-listener-established-via-netcat-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.6.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Netcat is a dual-use tool that can be used for benign or malicious activity. Netcat is included in some Linux distributions so its presence is not necessarily suspicious. Some normal use of this program, while uncommon, may originate from scripts, automation tools, and frameworks.
 
-==== Investigation guide
 
+*Investigating Netcat Network Activity*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Netcat Network Activity
+Netcat is a dual-use command line tool that can be used for various purposes, such as port scanning, file transfers, and connection tests. Attackers can abuse its functionality for malicious purposes such creating bind shells or reverse shells to gain access to the target system.
+
+A reverse shell is a mechanism that's abused to connect back to an attacker-controlled system. It effectively redirects the system's input and output and delivers a fully functional remote shell to the attacker. Even private systems are vulnerable since the connection is outgoing.
 
-Netcat is a dual-use command line tool that can be used for various purposes, such as port scanning, file transfers, and
-connection tests. Attackers can abuse its functionality for malicious purposes such creating bind shells or reverse
-shells to gain access to the target system.
+A bind shell is a type of backdoor that attackers set up on the target host and binds to a specific port to listen for an incoming connection from the attacker.
 
-A reverse shell is a mechanism that's abused to connect back to an attacker-controlled system. It effectively redirects
-the system's input and output and delivers a fully functional remote shell to the attacker. Even private systems are
-vulnerable since the connection is outgoing.
+This rule identifies potential reverse shell or bind shell activity using Netcat by checking for the execution of Netcat followed by a network connection.
 
-A bind shell is a type of backdoor that attackers set up on the target host and binds to a specific port to listen for
-an incoming connection from the attacker.
 
-This rule identifies potential reverse shell or bind shell activity using Netcat by checking for the execution of Netcat
-followed by a network connection.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Examine the command line to identify if the command is suspicious.
 - Extract and examine the target domain or IP address.
   - Check if the domain is newly registered or unexpected.
   - Check the reputation of the domain or IP address.
-  - Scope other potentially compromised hosts in your environment by mapping hosts that also communicated with the
-  domain or IP address.
+  - Scope other potentially compromised hosts in your environment by mapping hosts that also communicated with the domain or IP address.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
-- Investigate any abnormal behavior by the subject process such as network connections, file modifications, and any
-spawned child processes.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+- Investigate any abnormal behavior by the subject process such as network connections, file modifications, and any spawned child processes.
+
+
+*False positive analysis*
 
-### False positive analysis
 
-- Netcat is a dual-use tool that can be used for benign or malicious activity. It is included in some Linux
-distributions, so its presence is not necessarily suspicious. Some normal use of this program, while uncommon, may
-originate from scripts, automation tools, and frameworks.
+- Netcat is a dual-use tool that can be used for benign or malicious activity. It is included in some Linux distributions, so its presence is not necessarily suspicious. Some normal use of this program, while uncommon, may originate from scripts, automation tools, and frameworks.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Block the identified indicators of compromise (IoCs).
 - Take actions to terminate processes and connections used by the attacker.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-----------------------------------
 
+==== Setup
 
-==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where process.name:("nc","nca
-t","netcat","netcat.openbsd","netcat.traditional") and ( /*
-bind shell to echo for command execution */
-(process.args:("-l","-p") and process.args:("-c","echo","$*"))
-/* bind shell to specific port */ or
-process.args:("-l","-p","-lp") /* reverse shell to command-
-line interpreter used for command execution */ or
-(process.args:("-e") and process.args:("/bin/bash","/bin/sh"))
-/* file transfer via stdout */ or process.args:(">","<")
-/* file transfer via pipe */ or (process.args:("|") and
-process.args:("nc","ncat")) )] [network where (process.name ==
-"nc" or process.name == "ncat" or process.name == "netcat" or
-process.name == "netcat.openbsd" or process.name ==
-"netcat.traditional")]
-----------------------------------
+*Setup*
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
 
-* Tactic:
-** Name: Execution
-** ID: TA0002
-** Reference URL: https://attack.mitre.org/tactics/TA0002/
-* Technique:
-** Name: Command and Scripting Interpreter
-** ID: T1059
-** Reference URL: https://attack.mitre.org/techniques/T1059/
 
-[[file-transfer-or-listener-established-via-netcat-history]]
-==== Rule version history
+*Elastic Defend Integration Setup*
 
-Version 102 (8.6.0 release)::
-* Rule name changed from: Netcat Network Activity
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where (process.name == "nc"
-or process.name == "ncat" or process.name == "netcat" or
-process.name == "netcat.openbsd" or process.name ==
-"netcat.traditional") and event.type == "start"] [network where
-(process.name == "nc" or process.name == "ncat" or process.name ==
-"netcat" or process.name == "netcat.openbsd" or
-process.name == "netcat.traditional")]
-----------------------------------
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-Version 101 (8.5.0 release)::
-* Formatting only
 
-Version 8 (8.4.0 release)::
-* Formatting only
+*Prerequisite Requirements:*
 
-Version 6 (7.12.0 release)::
-* Formatting only
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 5 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:(access or connection or start)
-and process.name:(nc or ncat or netcat or netcat.openbsd or
-netcat.traditional)
-----------------------------------
 
-Version 4 (7.9.1 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
 
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:(nc or ncat or netcat or netcat.openbsd or
-netcat.traditional) and event.action:(bound-socket or connected-to or
-socket_opened)
-----------------------------------
 
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-process.name: (nc or ncat or netcat or netcat.openbsd or
-netcat.traditional) and event.action: (connected-to or bound-socket or
-socket_opened)
+sequence by process.entity_id
+  [process where host.os.type == "linux" and event.type == "start" and
+      process.name:("nc","ncat","netcat","netcat.openbsd","netcat.traditional") and (
+          /* bind shell to echo for command execution */
+          (process.args:("-l","-p") and process.args:("-c","echo","$*"))
+          /* bind shell to specific port */
+          or process.args:("-l","-p","-lp")
+          /* reverse shell to command-line interpreter used for command execution */
+          or (process.args:("-e") and process.args:("/bin/bash","/bin/sh"))
+          /* file transfer via stdout */
+          or process.args:(">","<")
+          /* file transfer via pipe */
+          or (process.args:("|") and process.args:("nc","ncat"))
+      )]
+  [network where host.os.type == "linux" and (process.name == "nc" or process.name == "ncat" or process.name == "netcat" or
+                  process.name == "netcat.openbsd" or process.name == "netcat.traditional")]
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/file-with-suspicious-extension-downloaded.asciidoc b/docs/detections/prebuilt-rules/rule-details/file-with-suspicious-extension-downloaded.asciidoc
new file mode 100644
index 0000000000..d59ba14eb4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/file-with-suspicious-extension-downloaded.asciidoc
@@ -0,0 +1,98 @@
+[[file-with-suspicious-extension-downloaded]]
+=== File with Suspicious Extension Downloaded
+
+Identifies unusual files downloaded from outside the local network that have the potential to be abused for code execution.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://x.com/Laughing_Mantis/status/1518766501385318406
+* https://wikileaks.org/ciav7p1/cms/page_13763375.html
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and
+  file.extension : (
+    "appinstaller", "application", "appx", "appxbundle", "cpl", "diagcab", "diagpkg", "diagcfg", "manifest",
+    "msix", "pif", "search-ms", "searchConnector-ms", "settingcontent-ms", "symlink", "theme", "themepack" 
+  ) and file.Ext.windows.zone_identifier > 1 and
+  not
+  (
+    (
+      file.extension : "msix" and 
+      file.path : (
+        "?:\\Users\\*\\AppData\\Local\\Temp\\WinGet\\Microsoft.Winget.Source*",
+        "?:\\Windows\\system32\\config\\systemprofile\\AppData\\Local\\Microsoft\\WinGet\\State\\defaultState\\Microsoft.PreIndexed.Package\\Microsoft.Winget.Source*"
+      )
+    ) or
+    (
+      process.name : "Teams.exe" and process.code_signature.trusted == true and
+      file.extension : "msix" and 
+      file.path : "?:\\Users\\*\\AppData\\Roaming\\Microsoft\\Teams\\tmp\\*"
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/finder-sync-plugin-registered-and-enabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/finder-sync-plugin-registered-and-enabled.asciidoc
index 3296f441ec..cfbf627db6 100644
--- a/docs/detections/prebuilt-rules/rule-details/finder-sync-plugin-registered-and-enabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/finder-sync-plugin-registered-and-enabled.asciidoc
@@ -5,66 +5,104 @@ Finder Sync plugins enable users to extend Finder’s functionality by modifying
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/specterops/presentations/raw/master/Leo%20Pitt/Hey_Im_Still_in_Here_Modern_macOS_Persistence_SO-CON2020.pdf
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<finder-sync-plugin-registered-and-enabled-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Trusted Finder Sync Plugins
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "pluginkit" and process.args : "-e" and process.args
-: "use" and process.args : "-i" and not process.args : (
-"com.google.GoogleDrive.FinderSyncAPIExtension",
-"com.google.drivefs.findersync", "com.boxcryptor.osx.Rednif",
-"com.adobe.accmac.ACCFinderSync",
-"com.microsoft.OneDrive.FinderSync", "com.insynchq.Insync.Insync-
-Finder-Integration", "com.box.desktop.findersyncext" ) and not
-process.parent.executable : ( "/Library/Application Support/IDrive
-forMac/IDriveHelperTools/FinderPluginApp.app/Contents/MacOS/FinderPlug
-inApp" )
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and process.name : "pluginkit" and
+  process.args : "-e" and process.args : "use" and process.args : "-i" and
+  not process.args :
+  (
+    "com.google.GoogleDrive.FinderSyncAPIExtension",
+    "com.google.drivefs.findersync",
+    "com.boxcryptor.osx.Rednif",
+    "com.adobe.accmac.ACCFinderSync",
+    "com.microsoft.OneDrive.FinderSync",
+    "com.insynchq.Insync.Insync-Finder-Integration",
+    "com.box.desktop.findersyncext"
+  ) and
+  not process.parent.executable : ("/Library/Application Support/IDriveforMac/IDriveHelperTools/FinderPluginApp.app/Contents/MacOS/FinderPluginApp",
+                                   "/Applications/Google Drive.app/Contents/MacOS/Google Drive") and
+  not process.Ext.effective_parent.executable : ("/Applications/Google Drive.app/Contents/MacOS/Google Drive",
+                                                 "/usr/local/jamf/bin/jamf",
+                                                 "/Applications/Nextcloud.app/Contents/MacOS/Nextcloud",
+                                                 "/Library/Application Support/Checkpoint/Endpoint Security/AMFinderExtensions.app/Contents/MacOS/AMFinderExtensions",
+                                                 "/Applications/pCloud Drive.app/Contents/MacOS/pCloud Drive")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,32 +114,3 @@ inApp" )
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[finder-sync-plugin-registered-and-enabled-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, user.id with maxspan = 5s [process where
-event.type in ("start", "process_started") and process.name :
-"pluginkit" and process.args : "-a"] [process where event.type in
-("start", "process_started") and process.name : "pluginkit" and
-process.args : "-e" and process.args : "use" and process.args : "-i"
-and not process.args : (
-"com.google.GoogleDrive.FinderSyncAPIExtension",
-"com.google.drivefs.findersync", "com.boxcryptor.osx.Rednif",
-"com.adobe.accmac.ACCFinderSync",
-"com.microsoft.OneDrive.FinderSync",
-"com.insynchq.Insync.Insync-Finder-Integration",
-"com.box.desktop.findersyncext" ) ]
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/first-occurrence-github-event-for-a-personal-access-token-pat.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-occurrence-github-event-for-a-personal-access-token-pat.asciidoc
new file mode 100644
index 0000000000..b047947239
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-occurrence-github-event-for-a-personal-access-token-pat.asciidoc
@@ -0,0 +1,62 @@
+[[first-occurrence-github-event-for-a-personal-access-token-pat]]
+=== First Occurrence GitHub Event for a Personal Access Token (PAT)
+
+Detects a first occurrence event for a personal access token (PAT) not seen in the last 14 days.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Execution
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"github.audit" and event.category:"configuration" and
+event.action:* and github.hashed_token:* and 
+github.programmatic_access_type:("OAuth access token" or "Fine-grained personal access token")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Serverless Execution
+** ID: T1648
+** Reference URL: https://attack.mitre.org/techniques/T1648/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-github-repo-interaction-from-a-new-ip.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-github-repo-interaction-from-a-new-ip.asciidoc
new file mode 100644
index 0000000000..00365da148
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-github-repo-interaction-from-a-new-ip.asciidoc
@@ -0,0 +1,62 @@
+[[first-occurrence-of-github-repo-interaction-from-a-new-ip]]
+=== First Occurrence of GitHub Repo Interaction From a New IP
+
+Detects an interaction with a private GitHub repository from a new IP address not seen in the last 14 days.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Execution
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"github.audit" and event.category:"configuration" and
+github.actor_ip:* and github.repo:* and 
+github.repository_public:false
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Serverless Execution
+** ID: T1648
+** Reference URL: https://attack.mitre.org/techniques/T1648/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-github-user-interaction-with-private-repo.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-github-user-interaction-with-private-repo.asciidoc
new file mode 100644
index 0000000000..56136146c0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-github-user-interaction-with-private-repo.asciidoc
@@ -0,0 +1,62 @@
+[[first-occurrence-of-github-user-interaction-with-private-repo]]
+=== First Occurrence of GitHub User Interaction with Private Repo
+
+Detects a new private repo interaction for a GitHub user not seen in the last 14 days.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Execution
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"github.audit" and event.category:"configuration" and
+github.repo:* and user.name:* and 
+github.repository_public:false
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Serverless Execution
+** ID: T1648
+** Reference URL: https://attack.mitre.org/techniques/T1648/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-ip-address-for-github-personal-access-token-pat.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-ip-address-for-github-personal-access-token-pat.asciidoc
new file mode 100644
index 0000000000..d123a3fdfd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-ip-address-for-github-personal-access-token-pat.asciidoc
@@ -0,0 +1,66 @@
+[[first-occurrence-of-ip-address-for-github-personal-access-token-pat]]
+=== First Occurrence of IP Address For GitHub Personal Access Token (PAT)
+
+Detects a new IP address used for a GitHub PAT not previously seen in the last 14 days.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Initial Access
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"github.audit" and event.category:"configuration" and
+github.actor_ip:* and github.hashed_token:* and
+github.programmatic_access_type:("OAuth access token" or "Fine-grained personal access token")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Cloud Accounts
+** ID: T1078.004
+** Reference URL: https://attack.mitre.org/techniques/T1078/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-ip-address-for-github-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-ip-address-for-github-user.asciidoc
new file mode 100644
index 0000000000..265f74a5ff
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-ip-address-for-github-user.asciidoc
@@ -0,0 +1,65 @@
+[[first-occurrence-of-ip-address-for-github-user]]
+=== First Occurrence of IP Address For GitHub User
+
+Detects a new IP address used for a GitHub user not previously seen in the last 14 days.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Initial Access
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"github.audit" and event.category:"configuration" and
+github.actor_ip:* and user.name:*
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Cloud Accounts
+** ID: T1078.004
+** Reference URL: https://attack.mitre.org/techniques/T1078/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-okta-user-session-started-via-proxy.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-okta-user-session-started-via-proxy.asciidoc
new file mode 100644
index 0000000000..21dac0d0e4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-okta-user-session-started-via-proxy.asciidoc
@@ -0,0 +1,111 @@
+[[first-occurrence-of-okta-user-session-started-via-proxy]]
+=== First Occurrence of Okta User Session Started via Proxy
+
+Identifies the first occurrence of an Okta user session started via a proxy.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://developer.okta.com/docs/reference/api/system-log/
+* https://developer.okta.com/docs/reference/api/event-types/
+* https://developer.okta.com/docs/reference/api/system-log/#issuer-object
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+
+*Tags*: 
+
+* Tactic: Initial Access
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating First Occurrence of Okta User Session Started via Proxy*
+
+
+This rule detects the first occurrence of an Okta user session started via a proxy. This rule is designed to help identify suspicious authentication behavior that may be indicative of an attacker attempting to gain access to an Okta account while remaining anonymous. This rule leverages the New Terms rule type feature where the `okta.actor.id` value is checked against the previous 7 days of data to determine if the value has been seen before for this activity.
+
+
+*Possible investigation steps:*
+
+- Identify the user involved in this action by examining the `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, and `okta.actor.display_name` fields.
+- Determine the client used by the actor. Review the `okta.client.ip`, `okta.client.user_agent.raw_user_agent`, `okta.client.zone`, `okta.client.device`, and `okta.client.id` fields.
+- Examine the `okta.debug_context.debug_data.flattened` field for more information about the proxy used.
+- Review the `okta.request.ip_chain` field for more information about the geographic location of the proxy.
+- Review the past activities of the actor involved in this action by checking their previous actions.
+- Evaluate the actions that happened just before and after this event in the `okta.event_type` field to help understand the full context of the activity.
+
+
+*False positive analysis:*
+
+- A user may have legitimately started a session via a proxy for security or privacy reasons.
+
+
+*Response and remediation:*
+
+- Review the profile of the user involved in this action to determine if proxy usage may be expected.
+- If the user is legitimate and the authentication behavior is not suspicious, no action is required.
+- If the user is legitimate but the authentication behavior is suspicious, consider resetting the user's password and enabling multi-factor authentication (MFA).
+    - If MFA is already enabled, consider resetting MFA for the user.
+- If the user is not legitimate, consider deactivating the user's account.
+- Conduct a review of Okta policies and ensure they are in accordance with security best practices.
+
+
+*Setup*
+
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:okta.system and okta.event_type: (user.session.start or user.authentication.verify) and okta.security_context.is_proxy:true and not okta.actor.id: okta*
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: External Remote Services
+** ID: T1133
+** Reference URL: https://attack.mitre.org/techniques/T1133/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-personal-access-token-pat-use-for-a-github-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-personal-access-token-pat-use-for-a-github-user.asciidoc
new file mode 100644
index 0000000000..b128b93fce
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-personal-access-token-pat-use-for-a-github-user.asciidoc
@@ -0,0 +1,66 @@
+[[first-occurrence-of-personal-access-token-pat-use-for-a-github-user]]
+=== First Occurrence of Personal Access Token (PAT) Use For a GitHub User
+
+A new PAT was used for a GitHub user not previously seen in the last 14 days.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Persistence
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"github.audit" and event.category:"configuration" and
+github.hashed_token:* and user.name:* and
+github.programmatic_access_type:("OAuth access token" or "Fine-grained personal access token")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Account Manipulation
+** ID: T1098
+** Reference URL: https://attack.mitre.org/techniques/T1098/
+* Sub-technique:
+** Name: Additional Cloud Credentials
+** ID: T1098.001
+** Reference URL: https://attack.mitre.org/techniques/T1098/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-private-repo-event-from-specific-github-personal-access-token-pat.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-private-repo-event-from-specific-github-personal-access-token-pat.asciidoc
new file mode 100644
index 0000000000..bf21f40cb8
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-private-repo-event-from-specific-github-personal-access-token-pat.asciidoc
@@ -0,0 +1,63 @@
+[[first-occurrence-of-private-repo-event-from-specific-github-personal-access-token-pat]]
+=== First Occurrence of Private Repo Event from Specific GitHub Personal Access Token (PAT)
+
+Detects a new private repo interaction for a GitHub PAT not seen in the last 14 days.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Execution
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"github.audit" and event.category:"configuration" and
+github.repo:* and github.hashed_token:* and
+github.programmatic_access_type:("OAuth access token" or "Fine-grained personal access token") and 
+github.repository_public:false
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Serverless Execution
+** ID: T1648
+** Reference URL: https://attack.mitre.org/techniques/T1648/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-user-agent-for-a-github-personal-access-token-pat.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-user-agent-for-a-github-personal-access-token-pat.asciidoc
new file mode 100644
index 0000000000..ef790f06f0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-user-agent-for-a-github-personal-access-token-pat.asciidoc
@@ -0,0 +1,66 @@
+[[first-occurrence-of-user-agent-for-a-github-personal-access-token-pat]]
+=== First Occurrence of User Agent For a GitHub Personal Access Token (PAT)
+
+Detects a new user agent used for a GitHub PAT not previously seen in the last 14 days.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Initial Access
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"github.audit" and event.category:"configuration" and
+github.user_agent:* and github.hashed_token:* and
+github.programmatic_access_type:("OAuth access token" or "Fine-grained personal access token")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Cloud Accounts
+** ID: T1078.004
+** Reference URL: https://attack.mitre.org/techniques/T1078/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-user-agent-for-a-github-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-user-agent-for-a-github-user.asciidoc
new file mode 100644
index 0000000000..40bcad7fd9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-occurrence-of-user-agent-for-a-github-user.asciidoc
@@ -0,0 +1,65 @@
+[[first-occurrence-of-user-agent-for-a-github-user]]
+=== First Occurrence of User-Agent For a GitHub User
+
+Detects a new user agent used for a GitHub user not previously seen in the last 14 days.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Initial Access
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"github.audit" and event.category:"configuration" and
+github.user_agent:* and user.name:*
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Cloud Accounts
+** ID: T1078.004
+** Reference URL: https://attack.mitre.org/techniques/T1078/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-time-seen-aws-secret-value-accessed-in-secrets-manager.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-time-seen-aws-secret-value-accessed-in-secrets-manager.asciidoc
new file mode 100644
index 0000000000..4d8bfd92ab
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-time-seen-aws-secret-value-accessed-in-secrets-manager.asciidoc
@@ -0,0 +1,132 @@
+[[first-time-seen-aws-secret-value-accessed-in-secrets-manager]]
+=== First Time Seen AWS Secret Value Accessed in Secrets Manager
+
+An adversary with access to a compromised AWS service such as an EC2 instance, Lambda function, or other service may attempt to leverage the compromised service to access secrets in AWS Secrets Manager. This rule looks for the first time a specific user identity has programmatically retrieved a specific secret value from Secrets Manager using the `GetSecretValue` action.  This rule assumes that AWS services such as Lambda functions and EC2 instances are setup with IAM role's assigned that have the necessary permissions to access the secrets in Secrets Manager. An adversary with access to a compromised AWS service such as an EC2 instance, Lambda function, or other service would rely on the compromised service's IAM role to access the secrets in Secrets Manager.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-aws.cloudtrail-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_GetSecretValue.html
+* https://detectioninthe.cloud/ttps/credential_access/access_secret_in_secrets_manager/
+* https://cloud.hacktricks.xyz/pentesting-cloud/aws-security/aws-services/aws-secrets-manager-enum
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Tactic: Credential Access
+* Resources: Investigation Guide
+
+*Version*: 310
+
+*Rule authors*: 
+
+* Nick Jones
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating First Time Seen AWS Secret Value Accessed in Secrets Manager*
+
+
+AWS Secrets Manager is a service that enables the replacement of hardcoded credentials in code, including passwords, with an API call to Secrets Manager to retrieve the secret programmatically.
+
+This rule looks for the retrieval of credentials using `GetSecretValue` action in Secrets Manager programmatically. This is a https://www.elastic.co/guide/en/security/master/rules-ui-create.html#create-new-terms-rule[New Terms] rule indicating this is the first time a specific user identity has successfuly retrieved a specific secret value from Secrets Manager within the last 15 days.
+
+
+*Possible investigation steps*
+
+
+- Identify the account and its role in the environment, and inspect the related policy.
+- Identify the applications that should use this account.
+- Investigate other alerts associated with the user account during the past 48 hours.
+- Investigate abnormal values in the `user_agent.original` field by comparing them with the intended and authorized usage and historical data. Suspicious user agent values include non-SDK, AWS CLI, custom user agents, etc.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences involving other users.
+- Contact the account owner and confirm whether they are aware of this activity.
+- Considering the source IP address and geolocation of the user who issued the command:
+    - Do they look normal for the calling user?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
+- Review IAM permission policies for the user identity and specific secrets accessed.
+- Examine the request parameters. These might indicate the source of the program or the nature of its tasks.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
+
+- False positives may occur due to the intended usage of the service. Tuning is needed in order to have higher confidence. Consider adding exceptions — preferably with a combination of user agent and IP address conditions.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Rotate secrets or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
+- Consider enabling multi-factor authentication for users.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
+- Take the actions needed to return affected systems, data, or services to their normal operational levels.
+- Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
+
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:aws.cloudtrail and event.provider:secretsmanager.amazonaws.com and
+    event.action:GetSecretValue and event.outcome:success and aws.cloudtrail.user_identity.session_context.session_issuer.type: Role and
+    not user_agent.name: ("Chrome" or "Firefox" or "Safari" or "Edge" or "Brave" or "Opera")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Steal Application Access Token
+** ID: T1528
+** Reference URL: https://attack.mitre.org/techniques/T1528/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-time-seen-commonly-abused-remote-access-tool-execution.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-time-seen-commonly-abused-remote-access-tool-execution.asciidoc
new file mode 100644
index 0000000000..f3728efb50
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-time-seen-commonly-abused-remote-access-tool-execution.asciidoc
@@ -0,0 +1,310 @@
+[[first-time-seen-commonly-abused-remote-access-tool-execution]]
+=== First Time Seen Commonly Abused Remote Access Tool Execution
+
+Adversaries may install legitimate remote access tools (RAT) to compromised endpoints for further command-and-control (C2). Adversaries can rely on installed RATs for persistence, execution of native commands and more. This rule detects when a process is started whose name or code signature resembles commonly abused RATs. This is a New Terms rule type indicating the host has not seen this RAT process started before within the last 30 days.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* endgame-*
+* winlogbeat-*
+* logs-windows.*
+* logs-system.security*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://thedfirreport.com/2023/04/03/malicious-iso-file-leads-to-domain-wide-ransomware/
+* https://attack.mitre.org/techniques/T1219/
+* https://github.com/redcanaryco/surveyor/blob/master/definitions/remote-admin.json
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating First Time Seen Commonly Abused Remote Access Tool Execution*
+
+
+Remote access software is a class of tools commonly used by IT departments to provide support by connecting securely to users' computers. Remote access is an ever-growing market where new companies constantly offer new ways of quickly accessing remote systems.
+
+At the same pace as IT departments adopt these tools, the attackers also adopt them as part of their workflow to connect into an interactive session, maintain access with legitimate software as a persistence mechanism, drop malicious software, etc.
+
+This rule detects when a remote access tool is seen in the environment for the first time in the last 15 days, enabling analysts to investigate and enforce the correct usage of such tools.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Check if the execution of the remote access tool is approved by the organization's IT department.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Contact the account owner and confirm whether they are aware of this activity.
+  - If the tool is not approved for use in the organization, the employee could have been tricked into installing it and providing access to a malicious third party. Investigate whether this third party could be attempting to scam the end-user or gain access to the environment through social engineering.
+- Investigate any abnormal behavior by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
+
+
+*False positive analysis*
+
+
+- If an authorized support person or administrator used the tool to conduct legitimate support or remote access, consider reinforcing that only tooling approved by the IT policy should be used. The analyst can dismiss the alert if no other suspicious behavior is observed involving the host or users.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If an unauthorized third party did the access via social engineering, consider improvements to the security awareness program.
+- Enforce that only tooling approved by the IT policy should be used for remote access purposes and only by authorized staff.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type: "windows" and
+
+   event.category: "process" and event.type : "start" and
+
+    (
+        process.code_signature.subject_name : (
+            "Action1 Corporation" or
+            "AeroAdmin LLC" or
+            "Ammyy LLC" or
+            "Atera Networks Ltd" or
+            "AWERAY PTE. LTD." or
+            "BeamYourScreen GmbH" or
+            "Bomgar Corporation" or
+            "DUC FABULOUS CO.,LTD" or
+            "DOMOTZ INC." or
+            "DWSNET OÜ" or
+            "FleetDeck Inc" or
+            "GlavSoft LLC" or
+            "GlavSoft LLC." or
+            "Hefei Pingbo Network Technology Co. Ltd" or
+            "IDrive, Inc." or
+            "IMPERO SOLUTIONS LIMITED" or
+            "Instant Housecall" or
+            "ISL Online Ltd." or
+            "LogMeIn, Inc." or
+            "Monitoring Client" or
+            "MMSOFT Design Ltd." or
+            "Nanosystems S.r.l." or
+            "NetSupport Ltd" or
+            "NinjaRMM, LLC" or
+            "Parallels International GmbH" or
+            "philandro Software GmbH" or
+            "Pro Softnet Corporation" or
+            "RealVNC" or
+            "RealVNC Limited" or
+            "BreakingSecurity.net" or
+            "Remote Utilities LLC" or
+            "Rocket Software, Inc." or
+            "SAFIB" or
+            "Servably, Inc." or
+            "ShowMyPC INC" or
+            "Splashtop Inc." or
+            "Superops Inc." or
+            "TeamViewer" or
+            "TeamViewer GmbH" or
+            "TeamViewer Germany GmbH" or
+            "Techinline Limited" or
+            "uvnc bvba" or
+            "Yakhnovets Denis Aleksandrovich IP" or
+            "Zhou Huabing"
+        ) or
+
+        process.name.caseless : (
+            AA_v*.exe or
+            "AeroAdmin.exe" or
+            "AnyDesk.exe" or
+            "apc_Admin.exe" or
+            "apc_host.exe" or
+            "AteraAgent.exe" or
+            aweray_remote*.exe or
+            "AweSun.exe" or
+            "B4-Service.exe" or
+            "BASupSrvc.exe" or
+            "bomgar-scc.exe" or
+            "domotzagent.exe" or
+            "domotz-windows-x64-10.exe" or
+            "dwagsvc.exe" or
+            "DWRCC.exe" or
+            "ImperoClientSVC.exe" or
+            "ImperoServerSVC.exe" or
+            "ISLLight.exe" or
+            "ISLLightClient.exe" or
+            fleetdeck_commander*.exe or
+            "getscreen.exe" or
+            "LMIIgnition.exe" or
+            "LogMeIn.exe" or
+            "ManageEngine_Remote_Access_Plus.exe" or
+            "Mikogo-Service.exe" or
+            "NinjaRMMAgent.exe" or
+            "NinjaRMMAgenPatcher.exe" or
+            "ninjarmm-cli.exe" or
+            "r_server.exe" or
+            "radmin.exe" or
+            "radmin3.exe" or
+            "RCClient.exe" or
+            "RCService.exe" or
+            "RemoteDesktopManager.exe" or
+            "RemotePC.exe" or
+            "RemotePCDesktop.exe" or
+            "RemotePCService.exe" or
+            "rfusclient.exe" or
+            "ROMServer.exe" or
+            "ROMViewer.exe" or
+            "RPCSuite.exe" or
+            "rserver3.exe" or
+            "rustdesk.exe" or
+            "rutserv.exe" or
+            "rutview.exe" or
+            "saazapsc.exe" or
+            ScreenConnect*.exe or
+            "smpcview.exe" or
+            "spclink.exe" or
+            "Splashtop-streamer.exe" or
+            "SRService.exe" or
+            "strwinclt.exe" or
+            "Supremo.exe" or
+            "SupremoService.exe" or
+            "teamviewer.exe" or
+            "TiClientCore.exe" or
+            "TSClient.exe" or
+            "tvn.exe" or
+            "tvnserver.exe" or
+            "tvnviewer.exe" or
+            UltraVNC*.exe or
+            UltraViewer*.exe or
+            "vncserver.exe" or
+            "vncviewer.exe" or
+            "winvnc.exe" or
+            "winwvc.exe" or
+            "Zaservice.exe" or
+            "ZohoURS.exe"
+        ) or
+        process.name : (
+            AA_v*.exe or
+            "AeroAdmin.exe" or
+            "AnyDesk.exe" or
+            "apc_Admin.exe" or
+            "apc_host.exe" or
+            "AteraAgent.exe" or
+            aweray_remote*.exe or
+            "AweSun.exe" or
+            "B4-Service.exe" or
+            "BASupSrvc.exe" or
+            "bomgar-scc.exe" or
+            "domotzagent.exe" or
+            "domotz-windows-x64-10.exe" or
+            "dwagsvc.exe" or
+            "DWRCC.exe" or
+            "ImperoClientSVC.exe" or
+            "ImperoServerSVC.exe" or
+            "ISLLight.exe" or
+            "ISLLightClient.exe" or
+            fleetdeck_commander*.exe or
+            "getscreen.exe" or
+            "LMIIgnition.exe" or
+            "LogMeIn.exe" or
+            "ManageEngine_Remote_Access_Plus.exe" or
+            "Mikogo-Service.exe" or
+            "NinjaRMMAgent.exe" or
+            "NinjaRMMAgenPatcher.exe" or
+            "ninjarmm-cli.exe" or
+            "r_server.exe" or
+            "radmin.exe" or
+            "radmin3.exe" or
+            "RCClient.exe" or
+            "RCService.exe" or
+            "RemoteDesktopManager.exe" or
+            "RemotePC.exe" or
+            "RemotePCDesktop.exe" or
+            "RemotePCService.exe" or
+            "rfusclient.exe" or
+            "ROMServer.exe" or
+            "ROMViewer.exe" or
+            "RPCSuite.exe" or
+            "rserver3.exe" or
+            "rustdesk.exe" or
+            "rutserv.exe" or
+            "rutview.exe" or
+            "saazapsc.exe" or
+            ScreenConnect*.exe or
+            "smpcview.exe" or
+            "spclink.exe" or
+            "Splashtop-streamer.exe" or
+            "SRService.exe" or
+            "strwinclt.exe" or
+            "Supremo.exe" or
+            "SupremoService.exe" or
+            "teamviewer.exe" or
+            "TiClientCore.exe" or
+            "TSClient.exe" or
+            "tvn.exe" or
+            "tvnserver.exe" or
+            "tvnviewer.exe" or
+            UltraVNC*.exe or
+            UltraViewer*.exe or
+            "vncserver.exe" or
+            "vncviewer.exe" or
+            "winvnc.exe" or
+            "winwvc.exe" or
+            "Zaservice.exe" or
+            "ZohoURS.exe"
+        )
+	) and
+
+	not (process.pe.original_file_name : ("G2M.exe" or "Updater.exe" or "powershell.exe") and process.code_signature.subject_name : "LogMeIn, Inc.")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Remote Access Software
+** ID: T1219
+** Reference URL: https://attack.mitre.org/techniques/T1219/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-time-seen-driver-loaded.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-time-seen-driver-loaded.asciidoc
new file mode 100644
index 0000000000..a181841fbd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-time-seen-driver-loaded.asciidoc
@@ -0,0 +1,153 @@
+[[first-time-seen-driver-loaded]]
+=== First Time Seen Driver Loaded
+
+Identifies the load of a driver with an original file name and signature values that were observed for the first time during the last 30 days. This rule type can help baseline drivers installation within your environment.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/kr/security-labs/stopping-vulnerable-driver-attacks
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Persistence
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating First Time Seen Driver Loaded*
+
+
+A driver is a software component that allows the operating system to communicate with hardware devices. It works at a high privilege level, the kernel level, having high control over the system's security and stability.
+
+Attackers may exploit known good but vulnerable drivers to execute code in their context because once an attacker can execute code in the kernel, security tools can no longer effectively protect the host. They can leverage these drivers to tamper, bypass and terminate security software, elevate privileges, create persistence mechanisms, and disable operating system protections and monitoring features. Attackers were seen in the wild conducting these actions before acting on their objectives, such as ransomware.
+
+Read the complete research on "Stopping Vulnerable Driver Attacks" done by Elastic Security Labs https://www.elastic.co/kr/security-labs/stopping-vulnerable-driver-attacks[here].
+
+This rule identifies the load of a driver with an original file name and signature values observed for the first time during the last 30 days. This rule type can help baseline drivers installation within your environment.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Examine the driver loaded to identify potentially suspicious characteristics. The following actions can help you gain context:
+  - Identify the path that the driver was loaded from. If using Elastic Defend, this information can be found in the `dll.path` field.
+  - Examine the digital signature of the driver, and check if it's valid.
+  - Examine the creation and modification timestamps of the file:
+    - On Elastic Defend, those can be found in the `dll.Ext.relative_file_creation_time` and `"dll.Ext.relative_file_name_modify_time"` fields, with the values being seconds.
+    - Search for file creation events sharing the same file name as the `dll.name` field and identify the process responsible for the operation.
+      - Investigate any other abnormal behavior by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
+  - Use the driver SHA-256 (`dll.hash.sha256` field) hash value to search for the existence and reputation in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Use Osquery to investigate the drivers loaded into the system.
+  - !{osquery{"label":"Osquery - Retrieve All Non-Microsoft Drivers with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, class, description, directory, image, issuer_name, manufacturer, service, signed, subject_name FROM drivers JOIN authenticode ON drivers.image = authenticode.path JOIN hash ON drivers.image = hash.path WHERE NOT (provider == \"Microsoft\" AND signed == \"1\")\n"}}
+  - !{osquery{"label":"Osquery - Retrieve All Unsigned Drivers with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, class, description, directory, image, issuer_name, manufacturer, service, signed, subject_name FROM drivers JOIN authenticode ON drivers.image = authenticode.path JOIN hash ON drivers.image = hash.path WHERE signed == \"0\"\n"}}
+- Identify the driver's `Device Name` and `Service Name`.
+- Check for alerts from the rules specified in the `Related Rules` section.
+
+
+*False positive analysis*
+
+
+- Matches derived from these rules are not inherently malicious. The security team should investigate them to ensure they are legitimate and needed, then include them in an allowlist only if required. The security team should address any vulnerable driver installation as it can put the user and the domain at risk.
+
+
+*Related Rules*
+
+
+- Untrusted Driver Loaded - d8ab1ec1-feeb-48b9-89e7-c12e189448aa
+- Code Signing Policy Modification Through Registry - da7733b1-fe08-487e-b536-0a04c6d8b0cd
+- Code Signing Policy Modification Through Built-in tools - b43570de-a908-4f7f-8bdb-b2df6ffd8c80
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Disable and uninstall all suspicious drivers found in the system. This can be done via Device Manager. (Note that this step may require you to boot the system into Safe Mode)
+- Remove the related services and registry keys found in the system. Note that the service will probably not stop if the driver is still installed.
+  - This can be done via PowerShell `Remove-Service` cmdlet.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Ensure that the Driver Signature Enforcement is enabled on the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:"driver" and host.os.type:windows and event.action:"load"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-time-seen-google-workspace-oauth-login-from-third-party-application.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-time-seen-google-workspace-oauth-login-from-third-party-application.asciidoc
new file mode 100644
index 0000000000..ad54698d6a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-time-seen-google-workspace-oauth-login-from-third-party-application.asciidoc
@@ -0,0 +1,103 @@
+[[first-time-seen-google-workspace-oauth-login-from-third-party-application]]
+=== First Time Seen Google Workspace OAuth Login from Third-Party Application
+
+Detects the first time a third-party application logs in and authenticated with OAuth. OAuth is used to grant permissions to specific resources and services in Google Workspace. Compromised credentials or service accounts could allow an adversary to authenticate to Google Workspace as a valid user and inherit their privileges.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-google_workspace*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/security-labs/google-workspace-attack-surface-part-one
+* https://developers.google.com/apps-script/guides/bound
+* https://developers.google.com/identity/protocols/oauth2
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Tactic: Defense Evasion
+* Tactic: Initial Access
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Setup*
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
+
+- As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
+- This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
+- To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
+- By default, `var.interval` is set to 2 hours (2h). Consider changing this interval to a lower value, such as 10 minutes (10m).
+- See the following references for further information:
+  - https://support.google.com/a/answer/7061566
+  - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
+
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset: "google_workspace.token" and event.action: "authorize" and
+google_workspace.token.scope.data.scope_name: *Login and google_workspace.token.client.id: *apps.googleusercontent.com
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Use Alternate Authentication Material
+** ID: T1550
+** Reference URL: https://attack.mitre.org/techniques/T1550/
+* Sub-technique:
+** Name: Application Access Token
+** ID: T1550.001
+** Reference URL: https://attack.mitre.org/techniques/T1550/001/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Cloud Accounts
+** ID: T1078.004
+** Reference URL: https://attack.mitre.org/techniques/T1078/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-time-seen-newcredentials-logon-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-time-seen-newcredentials-logon-process.asciidoc
new file mode 100644
index 0000000000..573d47359a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-time-seen-newcredentials-logon-process.asciidoc
@@ -0,0 +1,66 @@
+[[first-time-seen-newcredentials-logon-process]]
+=== First Time Seen NewCredentials Logon Process
+
+Identifies a new credentials logon type performed by an unusual process. This may indicate the existence of an access token forging capability that are often abused to bypass access control restrictions.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-system.*
+* logs-windows.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/pt/blog/how-attackers-abuse-access-token-manipulation
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:"authentication" and host.os.type:"windows" and winlog.logon.type:"NewCredentials" and winlog.event_data.LogonProcessName:(Advapi* or "Advapi  ") and not winlog.event_data.SubjectUserName:*$ and not process.executable :???\\Program?Files*
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Access Token Manipulation
+** ID: T1134
+** Reference URL: https://attack.mitre.org/techniques/T1134/
+* Sub-technique:
+** Name: Token Impersonation/Theft
+** ID: T1134.001
+** Reference URL: https://attack.mitre.org/techniques/T1134/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/first-time-seen-removable-device.asciidoc b/docs/detections/prebuilt-rules/rule-details/first-time-seen-removable-device.asciidoc
new file mode 100644
index 0000000000..a15e6ac707
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/first-time-seen-removable-device.asciidoc
@@ -0,0 +1,80 @@
+[[first-time-seen-removable-device]]
+=== First Time Seen Removable Device
+
+Identifies newly seen removable devices by device friendly name using registry modification events. While this activity is not inherently malicious, analysts can use those events to aid monitoring for data exfiltration over those devices.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.registry-*
+* winlogbeat-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://winreg-kb.readthedocs.io/en/latest/sources/system-keys/USB-storage.html
+* https://learn.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-device-specific-registry-settings
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Exfiltration
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:"registry" and host.os.type:"windows" and registry.value:"FriendlyName" and registry.path:*USBSTOR*
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Replication Through Removable Media
+** ID: T1091
+** Reference URL: https://attack.mitre.org/techniques/T1091/
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over Physical Medium
+** ID: T1052
+** Reference URL: https://attack.mitre.org/techniques/T1052/
+* Sub-technique:
+** Name: Exfiltration over USB
+** ID: T1052.001
+** Reference URL: https://attack.mitre.org/techniques/T1052/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/firsttime-seen-account-performing-dcsync.asciidoc b/docs/detections/prebuilt-rules/rule-details/firsttime-seen-account-performing-dcsync.asciidoc
new file mode 100644
index 0000000000..7d8127b3b0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/firsttime-seen-account-performing-dcsync.asciidoc
@@ -0,0 +1,164 @@
+[[firsttime-seen-account-performing-dcsync]]
+=== FirstTime Seen Account Performing DCSync
+
+This rule identifies when a User Account starts the Active Directory Replication Process for the first time. Attackers can use the DCSync technique to get credential information of individual accounts or the entire domain, thus compromising the entire domain.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-system.*
+* logs-windows.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://threathunterplaybook.com/notebooks/windows/06_credential_access/WIN-180815210510.html
+* https://threathunterplaybook.com/library/windows/active_directory_replication.html?highlight=dcsync#directory-replication-services-auditing
+* https://github.com/SigmaHQ/sigma/blob/master/rules/windows/builtin/security/win_ad_replication_non_machine_account.yml
+* https://github.com/atc-project/atomic-threat-coverage/blob/master/Atomic_Threat_Coverage/Logging_Policies/LP_0027_windows_audit_directory_service_access.md
+* https://attack.stealthbits.com/privilege-escalation-using-mimikatz-dcsync
+* https://www.thehacker.recipes/ad/movement/credentials/dumping/dcsync
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Privilege Escalation
+* Use Case: Active Directory Monitoring
+* Data Source: Active Directory
+* Resources: Investigation Guide
+
+*Version*: 10
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating FirstTime Seen Account Performing DCSync*
+
+
+Active Directory replication is the process by which the changes that originate on one domain controller are automatically transferred to other domain controllers that store the same data.
+
+Active Directory data consists of objects that have properties, or attributes. Each object is an instance of an object class, and object classes and their respective attributes are defined in the Active Directory schema. Objects are defined by the values of their attributes, and changes to attribute values must be transferred from the domain controller on which they occur to every other domain controller that stores a replica of an affected object.
+
+Adversaries can use the DCSync technique that uses Windows Domain Controller's API to simulate the replication process from a remote domain controller, compromising major credential material such as the Kerberos krbtgt keys that are used legitimately for creating tickets, but also for forging tickets by attackers. This attack requires some extended privileges to succeed (DS-Replication-Get-Changes and DS-Replication-Get-Changes-All), which are granted by default to members of the Administrators, Domain Admins, Enterprise Admins, and Domain Controllers groups. Privileged accounts can be abused to grant controlled objects the right to DCsync/Replicate.
+
+More details can be found on https://threathunterplaybook.com/library/windows/active_directory_replication.html?highlight=dcsync#directory-replication-services-auditing[Threat Hunter Playbook] and https://www.thehacker.recipes/ad/movement/credentials/dumping/dcsync[The Hacker Recipes].
+
+This rule monitors for when a Windows Event ID 4662 (Operation was performed on an Active Directory object) with the access mask 0x100 (Control Access) and properties that contain at least one of the following or their equivalent Schema-Id-GUID (DS-Replication-Get-Changes, DS-Replication-Get-Changes-All, DS-Replication-Get-Changes-In-Filtered-Set) is seen in the environment for the first time in the last 15 days.
+
+
+*Possible investigation steps*
+
+
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account and system owners and confirm whether they are aware of this activity.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Correlate security events 4662 and 4624 (Logon Type 3) by their Logon ID (`winlog.logon.id`) on the Domain Controller (DC) that received the replication request. This will tell you where the AD replication request came from, and if it came from another DC or not.
+- Scope which credentials were compromised (for example, whether all accounts were replicated or specific ones).
+
+
+*False positive analysis*
+
+
+- Administrators may use custom accounts on Azure AD Connect; investigate if this is part of a new Azure AD account setup, and ensure it is properly secured. If the activity was expected and there is no other suspicious activity involving the host or user, the analyst can dismiss the alert.
+- Although replicating Active Directory (AD) data to non-Domain Controllers is not a common practice and is generally not recommended from a security perspective, some software vendors may require it for their products to function correctly. Investigate if this is part of a new product setup, and ensure it is properly secured. If the activity was expected and there is no other suspicious activity involving the host or user, the analyst can dismiss the alert.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If the entire domain or the `krbtgt` user was compromised:
+  - Activate your incident response plan for total Active Directory compromise which should include, but not be limited to, a password reset (twice) of the `krbtgt` user.
+- Investigate how the attacker escalated privileges and identify systems they used to conduct lateral movement. Use this information to determine ways the attacker could regain access to the environment.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Directory Service Access' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Access (Success,Failure)
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.action:("Directory Service Access" or "object-operation-performed") and event.code:"4662" and
+ winlog.event_data.Properties:(*DS-Replication-Get-Changes* or *DS-Replication-Get-Changes-All* or
+                               *DS-Replication-Get-Changes-In-Filtered-Set* or *1131f6ad-9c07-11d1-f79f-00c04fc2dcd2* or
+                               *1131f6aa-9c07-11d1-f79f-00c04fc2dcd2* or *89e95b76-444d-4c62-991a-0facbeda640c*) and
+ not winlog.event_data.SubjectUserName:(*$ or MSOL_*)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: DCSync
+** ID: T1003.006
+** Reference URL: https://attack.mitre.org/techniques/T1003/006/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Domain Accounts
+** ID: T1078.002
+** Reference URL: https://attack.mitre.org/techniques/T1078/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/forwarded-google-workspace-security-alert.asciidoc b/docs/detections/prebuilt-rules/rule-details/forwarded-google-workspace-security-alert.asciidoc
new file mode 100644
index 0000000000..ec6d61fdb6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/forwarded-google-workspace-security-alert.asciidoc
@@ -0,0 +1,65 @@
+[[forwarded-google-workspace-security-alert]]
+=== Forwarded Google Workspace Security Alert
+
+Identifies the occurrence of a security alert from the Google Workspace alerts center. Google Workspace's security alert center provides an overview of actionable alerts that may be affecting an organization's domain. An alert is a warning of a potential security issue that Google has detected.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-google_workspace*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 10m
+
+*Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://workspace.google.com/products/admin/alert-center/
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Log Auditing
+* Use Case: Threat Detection
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+This is a promotion rule for Google Workspace security events, which are alertable events per the vendor.
+Consult vendor documentation on interpreting specific events.
+
+==== Setup
+
+
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset: google_workspace.alert
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/full-user-mode-dumps-enabled-system-wide.asciidoc b/docs/detections/prebuilt-rules/rule-details/full-user-mode-dumps-enabled-system-wide.asciidoc
index da6aae9d1d..5b78e68795 100644
--- a/docs/detections/prebuilt-rules/rule-details/full-user-mode-dumps-enabled-system-wide.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/full-user-mode-dumps-enabled-system-wide.asciidoc
@@ -5,58 +5,62 @@ Identifies the enable of the full user-mode dumps feature system-wide. This feat
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps
 * https://github.com/deepinstinct/Lsass-Shtinkering
 * https://media.defcon.org/DEF%20CON%2030/DEF%20CON%2030%20presentations/Asaf%20Gilboa%20-%20LSASS%20Shtinkering%20Abusing%20Windows%20Error%20Reporting%20to%20Dump%20LSASS.pdf
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Sysmon
 
-*Version*: 1
+*Version*: 7
 
-*Added ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.path :
-"HKLM\\SOFTWARE\\Microsoft\\Windows\\Windows Error
-Reporting\\LocalDumps\\DumpType" and registry.data.strings : ("2",
-"0x00000002") and not (process.executable :
-"?:\\Windows\\system32\\svchost.exe" and user.id : ("S-1-5-18",
-"S-1-5-19", "S-1-5-20"))
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and
+    registry.path : (
+        "HKLM\\SOFTWARE\\Microsoft\\Windows\\Windows Error Reporting\\LocalDumps\\DumpType",
+        "\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows\\Windows Error Reporting\\LocalDumps\\DumpType"
+    ) and
+    registry.data.strings : ("2", "0x00000002") and
+    not (process.executable : "?:\\Windows\\system32\\svchost.exe" and user.id : ("S-1-5-18", "S-1-5-19", "S-1-5-20"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -68,8 +72,10 @@ Reporting\\LocalDumps\\DumpType" and registry.data.strings : ("2",
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-creation.asciidoc
index 9185ef0ace..d4698d11ad 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-creation.asciidoc
@@ -5,7 +5,7 @@ Identifies when a firewall rule is created in Google Cloud Platform (GCP) for Vi
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,52 @@ Identifies when a firewall rule is created in Google Cloud Platform (GCP) for Vi
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/vpc/docs/firewalls
 * https://cloud.google.com/appengine/docs/standard/python/understanding-firewalls
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 102 (<<gcp-firewall-rule-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Firewall rules may be created by system administrators. Verify that the firewall configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and event.action:(*.compute.firewalls.insert
-or google.appengine.*.Firewall.Create*Rule)
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:(*.compute.firewalls.insert or google.appengine.*.Firewall.Create*Rule)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,40 +71,3 @@ or google.appengine.*.Firewall.Create*Rule)
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[gcp-firewall-rule-creation-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:v*.compute.firewalls.insert
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:v*.compute.firewalls.insert
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-deletion.asciidoc
index 3cc537f272..2f4d3283ef 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies when a firewall rule is deleted in Google Cloud Platform (GCP) for Vi
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,52 @@ Identifies when a firewall rule is deleted in Google Cloud Platform (GCP) for Vi
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/vpc/docs/firewalls
 * https://cloud.google.com/appengine/docs/standard/python/understanding-firewalls
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 102 (<<gcp-firewall-rule-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Firewall rules may be deleted by system administrators. Verify that the firewall configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and event.action:(*.compute.firewalls.delete
-or google.appengine.*.Firewall.Delete*Rule)
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:(*.compute.firewalls.delete or google.appengine.*.Firewall.Delete*Rule)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,40 +71,3 @@ or google.appengine.*.Firewall.Delete*Rule)
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[gcp-firewall-rule-deletion-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:v*.compute.firewalls.delete
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:v*.compute.firewalls.delete
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-modification.asciidoc
index 7c62fdadff..888affbb54 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-firewall-rule-modification.asciidoc
@@ -5,7 +5,7 @@ Identifies when a firewall rule is modified in Google Cloud Platform (GCP) for V
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,52 @@ Identifies when a firewall rule is modified in Google Cloud Platform (GCP) for V
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/vpc/docs/firewalls
 * https://cloud.google.com/appengine/docs/standard/python/understanding-firewalls
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 102 (<<gcp-firewall-rule-modification-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Firewall rules may be modified by system administrators. Verify that the firewall configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and event.action:(*.compute.firewalls.patch or
-google.appengine.*.Firewall.Update*Rule)
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:(*.compute.firewalls.patch or google.appengine.*.Firewall.Update*Rule)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,40 +71,3 @@ google.appengine.*.Firewall.Update*Rule)
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[gcp-firewall-rule-modification-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:v*.compute.firewalls.patch
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:v*.compute.firewalls.patch
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-iam-custom-role-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-iam-custom-role-creation.asciidoc
index 166927a370..2d53439fb0 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-iam-custom-role-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-iam-custom-role-creation.asciidoc
@@ -5,7 +5,7 @@ Identifies an Identity and Access Management (IAM) custom role creation in Googl
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,58 +14,51 @@ Identifies an Identity and Access Management (IAM) custom role creation in Googl
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/iam/docs/understanding-custom-roles
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<gcp-iam-custom-role-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Identity and Access Audit
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Custom role creations may be done by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Role creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.iam.admin.v*.CreateRole and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.iam.admin.v*.CreateRole and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,8 +70,6 @@ event.action:google.iam.admin.v*.CreateRole and event.outcome:success
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -87,43 +78,3 @@ event.action:google.iam.admin.v*.CreateRole and event.outcome:success
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[gcp-iam-custom-role-creation-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.iam.admin.v*.CreateRole and event.outcome:success
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.iam.admin.v*.CreateRole and event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-iam-role-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-iam-role-deletion.asciidoc
index 0fdb11b39a..e78ee5c7b4 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-iam-role-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-iam-role-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies an Identity and Access Management (IAM) role deletion in Google Cloud
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,58 +14,51 @@ Identifies an Identity and Access Management (IAM) role deletion in Google Cloud
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/iam/docs/understanding-roles
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<gcp-iam-role-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Identity and Access Audit
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Role deletions may be done by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Role deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.iam.admin.v*.DeleteRole and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.iam.admin.v*.DeleteRole and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,43 +70,3 @@ event.action:google.iam.admin.v*.DeleteRole and event.outcome:success
 ** Name: Account Access Removal
 ** ID: T1531
 ** Reference URL: https://attack.mitre.org/techniques/T1531/
-
-[[gcp-iam-role-deletion-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.iam.admin.v*.DeleteRole and event.outcome:success
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.iam.admin.v*.DeleteRole and event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-iam-service-account-key-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-iam-service-account-key-deletion.asciidoc
index 76bf1a5713..e15e969355 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-iam-service-account-key-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-iam-service-account-key-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies the deletion of an Identity and Access Management (IAM) service accou
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,60 +14,52 @@ Identifies the deletion of an Identity and Access Management (IAM) service accou
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/iam/docs/service-accounts
 * https://cloud.google.com/iam/docs/creating-managing-service-account-keys
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<gcp-iam-service-account-key-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Service account key deletions may be done by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Key deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.iam.admin.v*.DeleteServiceAccountKey and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.iam.admin.v*.DeleteServiceAccountKey and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,45 +71,3 @@ event.outcome:success
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[gcp-iam-service-account-key-deletion-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.iam.admin.v*.DeleteServiceAccountKey and
-event.outcome:success
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.iam.admin.v*.DeleteServiceAccountKey and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-logging-bucket-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-logging-bucket-deletion.asciidoc
index 5709451843..66ec80cd6e 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-logging-bucket-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-logging-bucket-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies a Logging bucket deletion in Google Cloud Platform (GCP). Log buckets
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,60 +14,52 @@ Identifies a Logging bucket deletion in Google Cloud Platform (GCP). Log buckets
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/logging/docs/buckets
 * https://cloud.google.com/logging/docs/storage
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 102 (<<gcp-logging-bucket-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Log Auditing
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Logging bucket deletions may be done by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Logging bucket deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.logging.v*.ConfigServiceV*.DeleteBucket and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.logging.v*.ConfigServiceV*.DeleteBucket and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,48 +71,3 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[gcp-logging-bucket-deletion-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.logging.v*.ConfigServiceV*.DeleteBucket and
-event.outcome:success
-----------------------------------
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.logging.v*.ConfigServiceV*.DeleteBucket and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-logging-sink-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-logging-sink-deletion.asciidoc
index 7591c314e5..449a0cede1 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-logging-sink-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-logging-sink-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies a Logging sink deletion in Google Cloud Platform (GCP). Every time a
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,51 @@ Identifies a Logging sink deletion in Google Cloud Platform (GCP). Every time a
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/logging/docs/export
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 102 (<<gcp-logging-sink-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Log Auditing
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Logging sink deletions may be done by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Logging sink deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.logging.v*.ConfigServiceV*.DeleteSink and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.logging.v*.ConfigServiceV*.DeleteSink and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,45 +70,3 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[gcp-logging-sink-deletion-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.logging.v*.ConfigServiceV*.DeleteSink and
-event.outcome:success
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.logging.v*.ConfigServiceV*.DeleteSink and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-logging-sink-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-logging-sink-modification.asciidoc
index 309b38b88e..8eaebfe034 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-logging-sink-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-logging-sink-modification.asciidoc
@@ -5,7 +5,7 @@ Identifies a modification to a Logging sink in Google Cloud Platform (GCP). Logg
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,51 @@ Identifies a modification to a Logging sink in Google Cloud Platform (GCP). Logg
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/logging/docs/export#how_sinks_work
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 102 (<<gcp-logging-sink-modification-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Log Auditing
+* Tactic: Exfiltration
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Logging sink modifications may be done by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Sink modifications from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.logging.v*.ConfigServiceV*.UpdateSink and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.logging.v*.ConfigServiceV*.UpdateSink and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,42 +70,3 @@ event.outcome:success
 ** Name: Transfer Data to Cloud Account
 ** ID: T1537
 ** Reference URL: https://attack.mitre.org/techniques/T1537/
-
-[[gcp-logging-sink-modification-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.logging.v*.ConfigServiceV*.UpdateSink and
-event.outcome:success
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.logging.v*.ConfigServiceV*.UpdateSink and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-subscription-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-subscription-creation.asciidoc
index 8ab6c48ed9..bab25d82e6 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-subscription-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-subscription-creation.asciidoc
@@ -5,7 +5,7 @@ Identifies the creation of a subscription in Google Cloud Platform (GCP). In GCP
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,51 @@ Identifies the creation of a subscription in Google Cloud Platform (GCP). In GCP
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/pubsub/docs/overview
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 102 (<<gcp-pub-sub-subscription-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Log Auditing
+* Tactic: Collection
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Subscription creations may be done by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Subscription creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.pubsub.v*.Subscriber.CreateSubscription and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.pubsub.v*.Subscriber.CreateSubscription and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,48 +67,6 @@ event.outcome:success
 ** ID: TA0009
 ** Reference URL: https://attack.mitre.org/tactics/TA0009/
 * Technique:
-** Name: Data from Cloud Storage Object
+** Name: Data from Cloud Storage
 ** ID: T1530
 ** Reference URL: https://attack.mitre.org/techniques/T1530/
-
-[[gcp-pub-sub-subscription-creation-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.pubsub.v*.Subscriber.CreateSubscription and
-event.outcome:success
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.pubsub.v*.Subscriber.CreateSubscription and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-subscription-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-subscription-deletion.asciidoc
index 8984943040..a8f3714eba 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-subscription-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-subscription-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies the deletion of a subscription in Google Cloud Platform (GCP). In GCP
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,51 @@ Identifies the deletion of a subscription in Google Cloud Platform (GCP). In GCP
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/pubsub/docs/overview
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 102 (<<gcp-pub-sub-subscription-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Log Auditing
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Subscription deletions may be done by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Subscription deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.pubsub.v*.Subscriber.DeleteSubscription and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.pubsub.v*.Subscriber.DeleteSubscription and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,45 +70,3 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[gcp-pub-sub-subscription-deletion-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.pubsub.v*.Subscriber.DeleteSubscription and
-event.outcome:success
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.pubsub.v*.Subscriber.DeleteSubscription and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-topic-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-topic-creation.asciidoc
index 394686a706..0ef956fb06 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-topic-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-topic-creation.asciidoc
@@ -5,7 +5,7 @@ Identifies the creation of a topic in Google Cloud Platform (GCP). In GCP, the p
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,51 @@ Identifies the creation of a topic in Google Cloud Platform (GCP). In GCP, the p
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/pubsub/docs/admin
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 102 (<<gcp-pub-sub-topic-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Log Auditing
+* Tactic: Collection
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Topic creations may be done by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Topic creations by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.pubsub.v*.Publisher.CreateTopic and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.pubsub.v*.Publisher.CreateTopic and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,48 +67,6 @@ event.outcome:success
 ** ID: TA0009
 ** Reference URL: https://attack.mitre.org/tactics/TA0009/
 * Technique:
-** Name: Data from Cloud Storage Object
+** Name: Data from Cloud Storage
 ** ID: T1530
 ** Reference URL: https://attack.mitre.org/techniques/T1530/
-
-[[gcp-pub-sub-topic-creation-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.pubsub.v*.Publisher.CreateTopic and
-event.outcome:success
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.pubsub.v*.Publisher.CreateTopic and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-topic-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-topic-deletion.asciidoc
index 5d080130f1..5a0126ae43 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-topic-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-pub-sub-topic-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies the deletion of a topic in Google Cloud Platform (GCP). In GCP, the p
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,51 @@ Identifies the deletion of a topic in Google Cloud Platform (GCP). In GCP, the p
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/pubsub/docs/overview
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Log Auditing
-
-*Version*: 102 (<<gcp-pub-sub-topic-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Log Auditing
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Topic deletions may be done by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Topic deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.pubsub.v*.Publisher.DeleteTopic and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.pubsub.v*.Publisher.DeleteTopic and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,45 +70,3 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[gcp-pub-sub-topic-deletion-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.pubsub.v*.Publisher.DeleteTopic and
-event.outcome:success
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.pubsub.v*.Publisher.DeleteTopic and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-service-account-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-service-account-creation.asciidoc
index cb399f7be7..742f8a9397 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-service-account-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-service-account-creation.asciidoc
@@ -5,7 +5,7 @@ Identifies when a new service account is created in Google Cloud Platform (GCP).
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,51 @@ Identifies when a new service account is created in Google Cloud Platform (GCP).
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/iam/docs/service-accounts
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<gcp-service-account-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Service accounts can be created by system administrators. Verify that the behavior was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.iam.admin.v*.CreateServiceAccount and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.iam.admin.v*.CreateServiceAccount and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,42 +70,3 @@ event.outcome:success
 ** Name: Create Account
 ** ID: T1136
 ** Reference URL: https://attack.mitre.org/techniques/T1136/
-
-[[gcp-service-account-creation-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.iam.admin.v*.CreateServiceAccount and
-event.outcome:success
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.iam.admin.v*.CreateServiceAccount and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-service-account-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-service-account-deletion.asciidoc
index 0539cdd690..42f55398b0 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-service-account-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-service-account-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies when a service account is deleted in Google Cloud Platform (GCP). A s
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,51 @@ Identifies when a service account is deleted in Google Cloud Platform (GCP). A s
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/iam/docs/service-accounts
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<gcp-service-account-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Identity and Access Audit
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Service accounts may be deleted by system administrators. Verify that the behavior was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.iam.admin.v*.DeleteServiceAccount and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.iam.admin.v*.DeleteServiceAccount and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,42 +70,3 @@ event.outcome:success
 ** Name: Account Access Removal
 ** ID: T1531
 ** Reference URL: https://attack.mitre.org/techniques/T1531/
-
-[[gcp-service-account-deletion-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.iam.admin.v*.DeleteServiceAccount and
-event.outcome:success
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.iam.admin.v*.DeleteServiceAccount and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-service-account-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-service-account-disabled.asciidoc
index 23c4270966..23cb8e212b 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-service-account-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-service-account-disabled.asciidoc
@@ -5,7 +5,7 @@ Identifies when a service account is disabled in Google Cloud Platform (GCP). A
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,51 @@ Identifies when a service account is disabled in Google Cloud Platform (GCP). A
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/iam/docs/service-accounts
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<gcp-service-account-disabled-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Identity and Access Audit
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Service accounts may be disabled by system administrators. Verify that the behavior was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.iam.admin.v*.DisableServiceAccount and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.iam.admin.v*.DisableServiceAccount and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,42 +70,3 @@ event.outcome:success
 ** Name: Account Access Removal
 ** ID: T1531
 ** Reference URL: https://attack.mitre.org/techniques/T1531/
-
-[[gcp-service-account-disabled-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.iam.admin.v*.DisableServiceAccount and
-event.outcome:success
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.iam.admin.v*.DisableServiceAccount and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-service-account-key-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-service-account-key-creation.asciidoc
index 6f5da3a70c..854977a31b 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-service-account-key-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-service-account-key-creation.asciidoc
@@ -5,7 +5,7 @@ Identifies when a new key is created for a service account in Google Cloud Platf
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,60 +14,52 @@ Identifies when a new key is created for a service account in Google Cloud Platf
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/iam/docs/service-accounts
 * https://cloud.google.com/iam/docs/creating-managing-service-account-keys
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<gcp-service-account-key-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Service account keys may be created by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and
-event.action:google.iam.admin.v*.CreateServiceAccountKey and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:google.iam.admin.v*.CreateServiceAccountKey and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,42 +71,3 @@ event.outcome:success
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[gcp-service-account-key-creation-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:google.iam.admin.v*.CreateServiceAccountKey and
-event.outcome:success
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:google.iam.admin.v*.CreateServiceAccountKey and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-configuration-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-configuration-modification.asciidoc
index 897f3d5250..99dd060d49 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-configuration-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-configuration-modification.asciidoc
@@ -5,7 +5,7 @@ Identifies when the configuration is modified for a storage bucket in Google Clo
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,51 @@ Identifies when the configuration is modified for a storage bucket in Google Clo
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/storage/docs/key-terms#buckets
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Defense Evasion
-
-*Version*: 102 (<<gcp-storage-bucket-configuration-modification-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Identity and Access Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Storage bucket configuration may be modified by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and event.action:"storage.buckets.update" and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:"storage.buckets.update" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,46 +70,3 @@ event.outcome:success
 ** Name: Modify Cloud Compute Infrastructure
 ** ID: T1578
 ** Reference URL: https://attack.mitre.org/techniques/T1578/
-
-[[gcp-storage-bucket-configuration-modification-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:"storage.buckets.update" and event.outcome:success
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:storage.buckets.update and event.outcome:success
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:storage.buckets.update and event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-deletion.asciidoc
index 4c8164557e..03c7e0b298 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies when a Google Cloud Platform (GCP) storage bucket is deleted. An adve
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,57 +14,50 @@ Identifies when a Google Cloud Platform (GCP) storage bucket is deleted. An adve
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/storage/docs/key-terms#buckets
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 102 (<<gcp-storage-bucket-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Storage buckets may be deleted by a system or network administrator. Verify whether the user email, resource name, and/or hostname should be making changes in your environment. Bucket deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:gcp.audit and event.action:"storage.buckets.delete"
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,49 +69,3 @@ event.dataset:gcp.audit and event.action:"storage.buckets.delete"
 ** Name: Data Destruction
 ** ID: T1485
 ** Reference URL: https://attack.mitre.org/techniques/T1485/
-
-[[gcp-storage-bucket-deletion-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:"storage.buckets.delete"
-----------------------------------
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:storage.buckets.delete
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:storage.buckets.delete
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-permissions-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-permissions-modification.asciidoc
index 24dc149d42..99e956306a 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-permissions-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-storage-bucket-permissions-modification.asciidoc
@@ -5,7 +5,7 @@ Identifies when the Identity and Access Management (IAM) permissions are modifie
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,58 +14,51 @@ Identifies when the Identity and Access Management (IAM) permissions are modifie
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/storage/docs/access-control/iam-permissions
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<gcp-storage-bucket-permissions-modification-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Identity and Access Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Storage bucket permissions may be modified by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and event.action:"storage.setIamPermissions"
-and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:"storage.setIamPermissions" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,46 +70,3 @@ and event.outcome:success
 ** Name: File and Directory Permissions Modification
 ** ID: T1222
 ** Reference URL: https://attack.mitre.org/techniques/T1222/
-
-[[gcp-storage-bucket-permissions-modification-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:"storage.setIamPermissions" and event.outcome:success
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:storage.setIamPermissions and event.outcome:success
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:storage.setIamPermissions and event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-network-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-network-deletion.asciidoc
index 3fa38f3a8b..1a24d40d55 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-network-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-network-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies when a Virtual Private Cloud (VPC) network is deleted in Google Cloud
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,59 +14,51 @@ Identifies when a Virtual Private Cloud (VPC) network is deleted in Google Cloud
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/vpc/docs/vpc
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Defense Evasion
-
-*Version*: 102 (<<gcp-virtual-private-cloud-network-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Virtual Private Cloud networks may be deleted by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and event.action:v*.compute.networks.delete
-and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:v*.compute.networks.delete and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,40 +70,7 @@ and event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[gcp-virtual-private-cloud-network-deletion-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:v*.compute.networks.delete and event.outcome:success
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:v*.compute.networks.delete and event.outcome:success
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-route-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-route-creation.asciidoc
index 59152f721b..bf2fe436c3 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-route-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-route-creation.asciidoc
@@ -5,7 +5,7 @@ Identifies when a virtual private cloud (VPC) route is created in Google Cloud P
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,60 +14,52 @@ Identifies when a virtual private cloud (VPC) route is created in Google Cloud P
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/vpc/docs/routes
 * https://cloud.google.com/vpc/docs/using-routes
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Defense Evasion
-
-*Version*: 102 (<<gcp-virtual-private-cloud-route-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Virtual Private Cloud routes may be created by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and event.action:(v*.compute.routes.insert or
-"beta.compute.routes.insert")
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:(v*.compute.routes.insert or "beta.compute.routes.insert")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,53 +71,7 @@ event.dataset:gcp.audit and event.action:(v*.compute.routes.insert or
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[gcp-virtual-private-cloud-route-creation-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:(v*.compute.routes.insert or
-"beta.compute.routes.insert")
-----------------------------------
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (8.0.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:(v*.compute.routes.insert or beta.compute.routes.insert)
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:(v*.compute.routes.insert or beta.compute.routes.insert)
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-route-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-route-deletion.asciidoc
index 73a091a287..93a1a531b5 100644
--- a/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-route-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/gcp-virtual-private-cloud-route-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies when a Virtual Private Cloud (VPC) route is deleted in Google Cloud P
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-gcp*
@@ -14,60 +14,52 @@ Identifies when a Virtual Private Cloud (VPC) route is deleted in Google Cloud P
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cloud.google.com/vpc/docs/routes
 * https://cloud.google.com/vpc/docs/using-routes
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* GCP
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Defense Evasion
-
-*Version*: 102 (<<gcp-virtual-private-cloud-route-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: GCP
+* Data Source: Google Cloud Platform
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Virtual Private Cloud routes may be deleted by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The GCP Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:gcp.audit and event.action:v*.compute.routes.delete and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:gcp.audit and event.action:v*.compute.routes.delete and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,40 +71,7 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[gcp-virtual-private-cloud-route-deletion-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(googlecloud.audit or gcp.audit) and
-event.action:v*.compute.routes.delete and event.outcome:success
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:googlecloud.audit and
-event.action:v*.compute.routes.delete and event.outcome:success
-----------------------------------
-
+* Sub-technique:
+** Name: Disable or Modify Cloud Firewall
+** ID: T1562.007
+** Reference URL: https://attack.mitre.org/techniques/T1562/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/github-app-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/github-app-deleted.asciidoc
new file mode 100644
index 0000000000..9375856af4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/github-app-deleted.asciidoc
@@ -0,0 +1,58 @@
+[[github-app-deleted]]
+=== GitHub App Deleted
+
+Detects the deletion of a GitHub app either from a repo or an organization.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+configuration where event.dataset == "github.audit" and github.category == "integration_installation" and event.type == "deletion"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Serverless Execution
+** ID: T1648
+** Reference URL: https://attack.mitre.org/techniques/T1648/
diff --git a/docs/detections/prebuilt-rules/rule-details/github-owner-role-granted-to-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/github-owner-role-granted-to-user.asciidoc
new file mode 100644
index 0000000000..b8252401d6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/github-owner-role-granted-to-user.asciidoc
@@ -0,0 +1,63 @@
+[[github-owner-role-granted-to-user]]
+=== GitHub Owner Role Granted To User
+
+This rule detects when a member is granted the organization owner role of a GitHub organization. This role provides admin level privileges. Any new owner role should be investigated to determine its validity. Unauthorized owner roles could indicate compromise within your organization and provide unlimited access to data and settings.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Persistence
+* Data Source: Github
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+iam where event.dataset == "github.audit" and event.action == "org.update_member" and github.permission == "admin"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Account Manipulation
+** ID: T1098
+** Reference URL: https://attack.mitre.org/techniques/T1098/
+* Sub-technique:
+** Name: Additional Cloud Roles
+** ID: T1098.003
+** Reference URL: https://attack.mitre.org/techniques/T1098/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/github-pat-access-revoked.asciidoc b/docs/detections/prebuilt-rules/rule-details/github-pat-access-revoked.asciidoc
new file mode 100644
index 0000000000..36423b1d55
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/github-pat-access-revoked.asciidoc
@@ -0,0 +1,60 @@
+[[github-pat-access-revoked]]
+=== GitHub PAT Access Revoked
+
+Access to private GitHub organization resources was revoked for a PAT.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Impact
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+configuration where event.dataset == "github.audit" and event.action == "personal_access_token.access_revoked"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Account Access Removal
+** ID: T1531
+** Reference URL: https://attack.mitre.org/techniques/T1531/
diff --git a/docs/detections/prebuilt-rules/rule-details/github-protected-branch-settings-changed.asciidoc b/docs/detections/prebuilt-rules/rule-details/github-protected-branch-settings-changed.asciidoc
new file mode 100644
index 0000000000..62934e6b62
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/github-protected-branch-settings-changed.asciidoc
@@ -0,0 +1,63 @@
+[[github-protected-branch-settings-changed]]
+=== GitHub Protected Branch Settings Changed
+
+This rule detects setting modifications for protected branches of a GitHub repository. Branch protection rules can be used to enforce certain workflows or requirements before a contributor can push changes to a branch in your repository. Changes to these protected branch settings should be investigated and verified as legitimate activity. Unauthorized changes could be used to lower your organization's security posture and leave you exposed for future attacks.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Github
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+configuration where event.dataset == "github.audit" 
+  and github.category == "protected_branch" and event.type == "change" 
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/github-repo-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/github-repo-created.asciidoc
new file mode 100644
index 0000000000..55d0d30b50
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/github-repo-created.asciidoc
@@ -0,0 +1,60 @@
+[[github-repo-created]]
+=== GitHub Repo Created
+
+A new GitHub repository was created.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Execution
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+configuration where event.dataset == "github.audit" and event.action == "repo.create"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Serverless Execution
+** ID: T1648
+** Reference URL: https://attack.mitre.org/techniques/T1648/
diff --git a/docs/detections/prebuilt-rules/rule-details/github-repository-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/github-repository-deleted.asciidoc
new file mode 100644
index 0000000000..b9d8a211f0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/github-repository-deleted.asciidoc
@@ -0,0 +1,59 @@
+[[github-repository-deleted]]
+=== GitHub Repository Deleted
+
+This rule detects when a GitHub repository is deleted within your organization. Repositories are a critical component used within an organization to manage work, collaborate with others and release products to the public. Any delete action against a repository should be investigated to determine it's validity. Unauthorized deletion of organization repositories could cause irreversible loss of intellectual property and indicate compromise within your organization.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Impact
+* Data Source: Github
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+configuration where event.module == "github" and event.action == "repo.destroy"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Data Destruction
+** ID: T1485
+** Reference URL: https://attack.mitre.org/techniques/T1485/
diff --git a/docs/detections/prebuilt-rules/rule-details/github-ueba-multiple-alerts-from-a-github-account.asciidoc b/docs/detections/prebuilt-rules/rule-details/github-ueba-multiple-alerts-from-a-github-account.asciidoc
new file mode 100644
index 0000000000..96696ab80c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/github-ueba-multiple-alerts-from-a-github-account.asciidoc
@@ -0,0 +1,56 @@
+[[github-ueba-multiple-alerts-from-a-github-account]]
+=== GitHub UEBA - Multiple Alerts from a GitHub Account
+
+This rule is part of the "GitHub UEBA - Unusual Activity from Account Pack", and leverages alert data to determine when multiple alerts are executed by the same user in a timespan of one hour. Analysts can use this to prioritize triage and response, as these alerts are a higher indicator of compromised user accounts or PATs.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* .alerts-security.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Execution
+* Rule Type: Higher-Order Rule
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+signal.rule.tags:("Use Case: UEBA" and "Data Source: Github") and kibana.alert.workflow_status:"open"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
diff --git a/docs/detections/prebuilt-rules/rule-details/github-user-blocked-from-organization.asciidoc b/docs/detections/prebuilt-rules/rule-details/github-user-blocked-from-organization.asciidoc
new file mode 100644
index 0000000000..ac3f763ddb
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/github-user-blocked-from-organization.asciidoc
@@ -0,0 +1,60 @@
+[[github-user-blocked-from-organization]]
+=== GitHub User Blocked From Organization
+
+A GitHub user was blocked from access to an organization.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Impact
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+configuration where event.dataset == "github.audit" and event.action == "org.block_user"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Account Access Removal
+** ID: T1531
+** Reference URL: https://attack.mitre.org/techniques/T1531/
diff --git a/docs/detections/prebuilt-rules/rule-details/google-drive-ownership-transferred-via-google-workspace.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-drive-ownership-transferred-via-google-workspace.asciidoc
index 6282e41ef8..b2fda9be13 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-drive-ownership-transferred-via-google-workspace.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-drive-ownership-transferred-via-google-workspace.asciidoc
@@ -5,7 +5,7 @@ Drive and Docs is a Google Workspace service that allows users to leverage Googl
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,45 +14,90 @@ Drive and Docs is a Google Workspace service that allows users to leverage Googl
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/1247799?hl=en
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Tactic: Collection
+* Resources: Investigation Guide
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Collection
 
-*Version*: 2 (<<google-drive-ownership-transferred-via-google-workspace-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.5.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Administrators may transfer file ownership during employee leave or absence to ensure continued operations by a new or existing employee.
 
-==== Investigation guide
 
+*Investigating Google Drive Ownership Transferred via Google Workspace*
+
+
+Google Drive is a cloud storage service that allows users to store and access files. It is available to users with a Google Workspace account.
+
+Google Workspace administrators consider users' roles and organizational units when assigning permissions to files or shared drives. Owners of sensitive files and folders can grant permissions to users who make internal or external access requests. Adversaries abuse this trust system by accessing Google Drive resources with improperly scoped permissions and shared settings. Distributing phishing emails is another common approach to sharing malicious Google Drive documents. With this approach, adversaries aim to inherit the recipient's Google Workspace privileges when an external entity grants ownership.
+
+This rule identifies when the ownership of a shared drive within a Google Workspace organization is transferred to another internal user.
+
+
+*Possible investigation steps*
+
+
+- From the admin console, review admin logs for involved user accounts. To find admin logs, go to `Security > Reporting > Audit and investigation > Admin log events`.
+- Determine if involved user accounts are active. To view user activity, go to `Directory > Users`.
+- Check if the involved user accounts were recently disabled, then re-enabled.
+- Review involved user accounts for potentially misconfigured permissions or roles.
+- Review the involved shared drive or files and related policies to determine if this action was expected and appropriate.
+- If a shared drive, access requirements based on Organizational Units in `Apps > Google Workspace > Drive and Docs > Manage shared drives`.
+- Triage potentially related alerts based on the users involved. To find alerts, go to `Security > Alerts`.
+
+
+*False positive analysis*
+
+
+- Transferring drives requires Google Workspace administration permissions related to Google Drive. Check if this action was planned/expected from the requester and is appropriately targeting the correct receiver.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -60,20 +105,21 @@ Administrators may transfer file ownership during employee leave or absence to e
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
+
+==== Setup
 
 
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:"google_workspace.admin" and
-event.action:"CREATE_DATA_TRANSFER_REQUEST" and event.category:"iam"
-and google_workspace.admin.application.name:Drive*
+[source, js]
 ----------------------------------
+event.dataset:"google_workspace.admin" and event.action:"CREATE_DATA_TRANSFER_REQUEST"
+  and event.category:"iam" and google_workspace.admin.application.name:Drive*
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -85,10 +131,7 @@ and google_workspace.admin.application.name:Drive*
 ** Name: Data Staged
 ** ID: T1074
 ** Reference URL: https://attack.mitre.org/techniques/T1074/
-
-[[google-drive-ownership-transferred-via-google-workspace-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Remote Data Staging
+** ID: T1074.002
+** Reference URL: https://attack.mitre.org/techniques/T1074/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-2sv-policy-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-2sv-policy-disabled.asciidoc
index 6bbf226144..e103530d51 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-2sv-policy-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-2sv-policy-disabled.asciidoc
@@ -5,7 +5,7 @@ Google Workspace admins may setup 2-step verification (2SV) to add an extra laye
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,46 +14,92 @@ Google Workspace admins may setup 2-step verification (2SV) to add an extra laye
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/9176657?hl=en
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Configuration Audit
+* Tactic: Persistence
+* Resources: Investigation Guide
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Persistence
 
-*Version*: 2 (<<google-workspace-2sv-policy-disabled-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.5.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Administrators may remove 2-step verification (2SV) temporarily for testing or during maintenance. If 2SV was previously enabled, it is not common to disable this policy for extended periods of time.
 
-==== Investigation guide
 
+*Investigating Google Workspace 2SV Policy Disabled*
+
+
+Google Workspace administrators manage password policies to enforce password requirements for an organization's compliance needs. Administrators have the capability to set restrictions on password length, reset frequencies, reuse capability, expiration, and much more. Google Workspace also allows multi-factor authentication (MFA) and 2-step verification (2SV) for authentication. 2SV allows users to verify their identity using security keys, Google prompt, authentication codes, text messages, and more.
+
+2SV adds an extra authentication layer for Google Workspace users to verify their identity. If 2SV or MFA aren't implemented, users only authenticate with their user name and password credentials. This authentication method has often been compromised and can be susceptible to credential access techniques when weak password policies are used.
+
+This rule detects when a 2SV policy is disabled in Google Workspace.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user account(s) by reviewing `user.name` or `source.user.email` in the alert.
+- Identify what password setting was created or adjusted by reviewing `google_workspace.admin.setting.name`.
+- Review if a password setting was enabled or disabled by reviewing `google_workspace.admin.new_value` and `google_workspace.admin.old_value`.
+- After identifying the involved user account, verify administrative privileges are scoped properly.
+- Filter `event.dataset` for `google_workspace.login` and aggregate by `user.name`, `event.action`.
+  - The `google_workspace.login.challenge_method` field can be used to identify the challenge method that was used for failed and successful logins.
+
+
+*False positive analysis*
+
+
+- After finding the user account that updated the password policy, verify whether the action was intentional.
+- Verify whether the user should have Google Workspace administrative privileges that allow them to modify password policies.
+- Review organizational units or groups the role may have been added to and ensure its privileges are properly aligned.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -61,18 +107,20 @@ Administrators may remove 2-step verification (2SV) temporarily for testing or d
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
+
+==== Setup
 
 
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:"google_workspace.admin" and event.action:"2sv_disable"
+[source, js]
 ----------------------------------
+event.dataset:"google_workspace.login" and event.action:"2sv_disable"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,10 +132,3 @@ event.dataset:"google_workspace.admin" and event.action:"2sv_disable"
 ** Name: Modify Authentication Process
 ** ID: T1556
 ** Reference URL: https://attack.mitre.org/techniques/T1556/
-
-[[google-workspace-2sv-policy-disabled-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-admin-role-assigned-to-a-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-admin-role-assigned-to-a-user.asciidoc
index bda458f073..f146e3ce6e 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-admin-role-assigned-to-a-user.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-admin-role-assigned-to-a-user.asciidoc
@@ -5,7 +5,7 @@ Assigning the administrative role to a user will grant them access to the Google
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,46 +14,96 @@ Assigning the administrative role to a user will grant them access to the Google
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/172176?hl=en
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
+* Resources: Investigation Guide
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Persistence
 
-*Version*: 102 (<<google-workspace-admin-role-assigned-to-a-user-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Google Workspace admin role assignments may be modified by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
-==== Investigation guide
 
+*Investigating Google Workspace Admin Role Assigned to a User*
+
+
+Google Workspace roles allow administrators to assign specific permissions to users or groups. These assignments should follow the principle of least privilege (PoLP). Admin roles in Google Workspace grant users access to the Google Admin console, where more domain-wide settings are accessible. Google Workspace contains prebuilt administrator roles for performing business functions related to users, groups, and services. Custom administrator roles can be created when prebuilt roles are not sufficient.
+
+Administrator roles assigned to users will grant them additional permissions and privileges within the Google Workspace domain. Administrative roles also give users access to the admin console, where domain-wide settings can be adjusted. Threat actors might rely on these new privileges to advance their intrusion efforts and laterally move throughout the organization. Users with unexpected administrative privileges may also cause operational dysfunction if unfamiliar settings are adjusted without warning.
+
+This rule identifies when a Google Workspace administrative role is assigned to a user.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
+  - The `user.target.email` field contains the user who received the admin role.
+- Identify the role given to the user by reviewing the `google_workspace.admin.role.name` field in the alert.
+- After identifying the involved user, verify their administrative privileges are scoped properly.
+- To identify other users with this role, search the alert for `event.action: ASSIGN_ROLE`.
+  - Add `google_workspace.admin.role.name` with the role added as an additional filter.
+  - Adjust the relative time accordingly to identify all users that were assigned this admin role.
+- Identify if the user account was recently created by searching for `event.action: CREATE_USER`.
+  - Add `user.email` with the target user account that recently received this new admin role.
+- After identifying the involved user, create a filter with their `user.name` or `user.target.email`. Review the last 48 hours of their activity for anything that may indicate a compromise.
+
+
+*False positive analysis*
+
+
+- After identifying user account that added the admin role, verify the action was intentional.
+- Verify that the target user who was assigned the admin role should have administrative privileges in Google Workspace.
+- Review organizational units or groups the target user might have been added to and ensure the admin role permissions align.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -61,21 +111,21 @@ Google Workspace admin role assignments may be modified by system administrators
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
+
+==== Setup
 
 
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:"google_workspace.admin" and event.category:"iam" and
-event.action:"ASSIGN_ROLE" and
-google_workspace.event.type:"DELEGATED_ADMIN_SETTINGS" and
-google_workspace.admin.role.name : *_ADMIN_ROLE
+[source, js]
 ----------------------------------
+event.dataset:"google_workspace.admin" and event.category:"iam" and event.action:"ASSIGN_ROLE"
+  and google_workspace.event.type:"DELEGATED_ADMIN_SETTINGS" and google_workspace.admin.role.name : *_ADMIN_ROLE
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -87,50 +137,7 @@ google_workspace.admin.role.name : *_ADMIN_ROLE
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[google-workspace-admin-role-assigned-to-a-user-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:google_workspace.admin and event.provider:admin and
-event.category:iam and event.action:ASSIGN_ROLE
-----------------------------------
-
-Version 14 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:ASSIGN_ROLE
-----------------------------------
-
-Version 5 (7.15.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Additional Cloud Roles
+** ID: T1098.003
+** Reference URL: https://attack.mitre.org/techniques/T1098/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-admin-role-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-admin-role-deletion.asciidoc
index e6a4a7763a..5c9c951b94 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-admin-role-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-admin-role-deletion.asciidoc
@@ -5,7 +5,7 @@ Detects when a custom admin role is deleted. An adversary may delete a custom ad
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,46 +14,91 @@ Detects when a custom admin role is deleted. An adversary may delete a custom ad
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/2406043?hl=en
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Identity and Access Audit
+* Tactic: Impact
+* Resources: Investigation Guide
+
+*Version*: 205
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Impact
 
-*Version*: 101 (<<google-workspace-admin-role-deletion-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Google Workspace admin roles may be deleted by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
-==== Investigation guide
 
+*Investigating Google Workspace Admin Role Deletion*
+
+
+Google Workspace roles allow administrators to assign specific permissions to users or groups where the principle of least privilege (PoLP) is recommended. Admin roles in Google Workspace grant users access to the Google Admin console, where further domain-wide settings are accessible. Google Workspace contains prebuilt administrator roles for performing business functions related to users, groups, and services. Custom administrator roles can be created where prebuilt roles are not preferred.
+
+Deleted administrator roles may render some user accounts inaccessible or cause operational failure where these roles are relied upon to perform daily administrative tasks. The deletion of roles may also hinder the response and remediation actions of administrators responding to security-related alerts and events. Without specific roles assigned, users will inherit the permissions and privileges of the root organizational unit.
+
+This rule identifies when a Google Workspace administrative role is deleted within the Google Admin console.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
+- Identify the role deleted by reviewing `google_workspace.admin.role.name` in the alert.
+- With the user identified, verify if he has administrative privileges to disable or delete administrative roles.
+- To identify other users affected by this role removed, search for `event.action: ASSIGN_ROLE`.
+    - Add `google_workspace.admin.role.name` with the role deleted as an additional filter.
+    - Adjust the relative time accordingly to identify all users that were assigned this admin role.
+
+
+*False positive analysis*
+
+
+- After identifying the user account that disabled the admin role, verify the action was intentional.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Discuss with the user the affected users as a result of this action to mitigate operational discrepencies.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -61,19 +106,20 @@ Google Workspace admin roles may be deleted by system administrators. Verify tha
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
 
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:google_workspace.admin and event.provider:admin and
-event.category:iam and event.action:DELETE_ROLE
+[source, js]
 ----------------------------------
+event.dataset:google_workspace.admin and event.provider:admin and event.category:iam and event.action:DELETE_ROLE
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -85,44 +131,3 @@ event.category:iam and event.action:DELETE_ROLE
 ** Name: Account Access Removal
 ** ID: T1531
 ** Reference URL: https://attack.mitre.org/techniques/T1531/
-
-[[google-workspace-admin-role-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 14 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:DELETE_ROLE
-----------------------------------
-
-Version 5 (7.15.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-api-access-granted-via-domain-wide-delegation-of-authority.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-api-access-granted-via-domain-wide-delegation-of-authority.asciidoc
index c4feeffcb2..cdb603f300 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-api-access-granted-via-domain-wide-delegation-of-authority.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-api-access-granted-via-domain-wide-delegation-of-authority.asciidoc
@@ -5,7 +5,7 @@ Detects when a domain-wide delegation of authority is granted to a service accou
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,45 +14,93 @@ Detects when a domain-wide delegation of authority is granted to a service accou
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developers.google.com/admin-sdk/directory/v1/guides/delegation
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Persistence
+
+*Version*: 205
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Identity and Access
 
-*Version*: 101 (<<google-workspace-api-access-granted-via-domain-wide-delegation-of-authority-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Domain-wide delegation of authority may be granted to service accounts by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
-==== Investigation guide
 
+*Investigating API Access Granted via Domain-Wide Delegation of Authority*
+
+
+Domain-wide delegation is a feature that allows apps to access users' data across an organization's Google Workspace environment. Only super admins can manage domain-wide delegation, and they must specify each API scope that the application can access. Google Workspace services all have APIs that can be interacted with after domain-wide delegation is established with an OAuth2 client ID of the application. Typically, GCP service accounts and applications are created where the Google Workspace APIs are enabled, thus allowing the application to access resources and services in Google Workspace.
+
+Applications authorized to interact with Google Workspace resources and services through APIs have a wide range of capabilities depending on the scopes applied. If the principle of least privilege (PoLP) is not practiced when setting API scopes, threat actors could abuse additional privileges if the application is compromised. New applications created and given API access could indicate an attempt by a threat actor to register their malicious application with the Google Workspace domain in an attempt to establish a command and control foothold.
+
+This rule identifies when an application is authorized API client access.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
+  - Only users with super admin privileges can authorize API client access.
+- Identify the API client name by reviewing the `google_workspace.admin.api.client.name` field in the alert.
+  - If GCP audit logs are ingested, pivot to reviewing the last 48 hours of activity related to the service account ID.
+  - Search for the `google_workspace.admin.api.client.name` value with wildcards in the `gcp.audit.resource_name` field.
+  - Search for API client name and aggregated results on `event.action` to determine what the service account is being used for in GWS.
+- After identifying the involved user, verify super administrative privileges to access domain-wide delegation settings.
+
+
+*False positive analysis*
+
+
+- Changes to domain-wide delegation require super admin privileges. Check with the user to ensure these changes were expected.
+- Review scheduled maintenance notes related to expected API access changes.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Review the scope of the authorized API client access in Google Workspace.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -60,19 +108,20 @@ Domain-wide delegation of authority may be granted to service accounts by system
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
 
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:google_workspace.admin and event.provider:admin and
-event.category:iam and event.action:AUTHORIZE_API_CLIENT_ACCESS
+[source, js]
 ----------------------------------
+event.dataset:google_workspace.admin and event.provider:admin and event.category:iam and event.action:AUTHORIZE_API_CLIENT_ACCESS
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,44 +133,3 @@ event.category:iam and event.action:AUTHORIZE_API_CLIENT_ACCESS
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[google-workspace-api-access-granted-via-domain-wide-delegation-of-authority-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 14 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:AUTHORIZE_API_CLIENT_ACCESS
-----------------------------------
-
-Version 5 (7.15.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-bitlocker-setting-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-bitlocker-setting-disabled.asciidoc
index f748cde8ae..870b235f3a 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-bitlocker-setting-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-bitlocker-setting-disabled.asciidoc
@@ -5,7 +5,7 @@ Google Workspace administrators whom manage Windows devices and have Windows dev
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,46 +14,89 @@ Google Workspace administrators whom manage Windows devices and have Windows dev
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/9176657?hl=en
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Defense Evasion
 
-*Version*: 2 (<<google-workspace-bitlocker-setting-disabled-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.5.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Administrators may temporarily disabled Bitlocker on managed devices for maintenance, testing or to resolve potential endpoint conflicts.
 
-==== Investigation guide
 
+*Investigating Google Workspace Bitlocker Setting Disabled*
+
+
+BitLocker Drive Encryption is a data protection feature that integrates with the Windows operating system to address the data theft or exposure threats from lost, stolen, or inappropriately decommissioned computers. BitLocker helps mitigate unauthorized data access by enhancing file and system protections, such as data encryption and rendering data inaccessible. Google Workspace can sync with Windows endpoints that are registered in inventory, where BitLocker can be enabled and disabled.
+
+Disabling Bitlocker on an endpoint decrypts data at rest and makes it accessible, which raises the risk of exposing sensitive endpoint data.
+
+This rule identifies a user with administrative privileges and access to the admin console, disabling BitLocker for Windows endpoints.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
+- After identifying the user, verify if the user should have administrative privileges to disable BitLocker on Windows endpoints.
+- From the Google Workspace admin console, review `Reporting > Audit` and `Investigation > Device` logs, filtering on the user email identified from the alert.
+    - If a Google Workspace user logged into their account using a potentially compromised account, this will create an `Device sync event` event.
+
+
+*False positive analysis*
+
+
+- An administrator may have intentionally disabled BitLocker for routine maintenance or endpoint updates.
+   - Verify with the user that they intended to disable BitLocker on Windows endpoints.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -61,21 +104,21 @@ Administrators may temporarily disabled Bitlocker on managed devices for mainten
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
+
+==== Setup
 
 
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:"google_workspace.admin" and
-event.action:"CHANGE_APPLICATION_SETTING" and event.category:(iam or
-configuration) and google_workspace.admin.new_value:"Disabled" and
-google_workspace.admin.setting.name:BitLocker*
+[source, js]
 ----------------------------------
+event.dataset:"google_workspace.admin" and event.action:"CHANGE_APPLICATION_SETTING" and event.category:(iam or configuration)
+    and google_workspace.admin.new_value:"Disabled" and google_workspace.admin.setting.name:BitLocker*
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -87,10 +130,7 @@ google_workspace.admin.setting.name:BitLocker*
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[google-workspace-bitlocker-setting-disabled-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-custom-admin-role-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-custom-admin-role-created.asciidoc
index 30d1807191..d3d5505c00 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-custom-admin-role-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-custom-admin-role-created.asciidoc
@@ -5,7 +5,7 @@ Detects when a custom admin role is created in Google Workspace. An adversary ma
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,45 +14,96 @@ Detects when a custom admin role is created in Google Workspace. An adversary ma
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/2406043?hl=en
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Persistence
+
+*Version*: 205
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Identity and Access
 
-*Version*: 101 (<<google-workspace-custom-admin-role-created-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Custom Google Workspace admin roles may be created by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
-==== Investigation guide
 
+*Investigating Google Workspace Custom Admin Role Created*
+
+
+Google Workspace roles allow administrators to assign specific permissions to users or groups where the principle of least privilege (PoLP) is recommended. Admin roles in Google Workspace grant users access to the Google Admin console, where more domain-wide settings are accessible. Google Workspace contains prebuilt administrator roles for performing business functions related to users, groups, and services. Custom administrator roles can be created where prebuilt roles are not preferred.
+
+Roles assigned to users will grant them additional permissions and privileges within the Google Workspace domain. Threat actors might create new admin roles with privileges to advance their intrusion efforts and laterally move throughout the organization if existing roles or users do not have privileges aligned with their modus operandi. Users with unexpected privileges from new admin roles may also cause operational dysfunction if unfamiliar settings are adjusted without warning. Instead of modifying existing roles, administrators might create new roles to accomplish short-term goals and unintentionally introduce additional risk exposure.
+
+This rule identifies when a Google Workspace administrative role is added within the Google Workspace admin console.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
+- Identify the role added by reviewing the `google_workspace.admin.role.name` field in the alert.
+- After identifying the involved user, verify if they should have administrative privileges to add administrative roles.
+- To identify if users have been assigned this role, search for `event.action: ASSIGN_ROLE`.
+    - Add `google_workspace.admin.role.name` with the role added as an additional filter.
+    - Adjust the relative time accordingly to identify all users that were possibly assigned this admin role.
+- Monitor users assigned the admin role for the next 24 hours and look for attempts to use related privileges.
+  - The `event.provider` field will help filter for specific services in Google Workspace such as Drive or Admin.
+  - The `event.action` field will help trace what actions are being taken by users.
+
+
+*False positive analysis*
+
+
+- After identifying the user account that created the role, verify whether the action was intentional.
+- Verify that the user who created the role should have administrative privileges in Google Workspace to create custom roles.
+- Review organizational units or groups the role may have been added to and ensure the new privileges align properly.
+- Create a filter with the user's `user.name` and filter for `event.action`. In the results, check if there are multiple `CREATE_ROLE` actions and note whether they are new or historical.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -60,19 +111,20 @@ Custom Google Workspace admin roles may be created by system administrators. Ver
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
 
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:google_workspace.admin and event.provider:admin and
-event.category:iam and event.action:CREATE_ROLE
+[source, js]
 ----------------------------------
+event.dataset:google_workspace.admin and event.provider:admin and event.category:iam and event.action:CREATE_ROLE
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,44 +136,3 @@ event.category:iam and event.action:CREATE_ROLE
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[google-workspace-custom-admin-role-created-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 14 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:CREATE_ROLE
-----------------------------------
-
-Version 5 (7.15.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-custom-gmail-route-created-or-modified.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-custom-gmail-route-created-or-modified.asciidoc
index 08e667dea5..c4ddf6d878 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-custom-gmail-route-created-or-modified.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-custom-gmail-route-created-or-modified.asciidoc
@@ -5,7 +5,7 @@ Detects when a custom Gmail route is added or modified in Google Workspace. Adve
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,45 +14,89 @@ Detects when a custom Gmail route is added or modified in Google Workspace. Adve
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/2685650?hl=en
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Tactic: Collection
+* Resources: Investigation Guide
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Collection
 
-*Version*: 2 (<<google-workspace-custom-gmail-route-created-or-modified-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.5.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Administrators may create custom email routes in Google Workspace based on organizational policies, administrative preference or for security purposes regarding spam.
 
-==== Investigation guide
 
+*Investigating Google Workspace Custom Gmail Route Created or Modified*
+
+
+Gmail is a popular cloud-based email service developed and managed by Google. Gmail is one of many services available for users with Google Workspace accounts.
+
+Threat actors often send phishing emails containing malicious URL links or attachments to corporate Gmail accounts. Google Workspace identity relies on the corporate user Gmail account and if stolen, allows threat actors to further their intrusion efforts from valid user accounts.
+
+This rule identifies the creation of a custom global Gmail route by an administrator from the Google Workspace admin console. Custom email routes could indicate an attempt to secretly forward sensitive emails to unintentional recipients.
+
+
+*Possible investigation steps*
+
+
+- Identify the user account that created the custom email route and verify that they should have administrative privileges.
+- Review the added recipients from the custom email route and confidentiality of potential email contents.
+- Identify the user account, then review `event.action` values for related activity within the last 48 hours.
+- If the Google Workspace license is Enterprise Plus or Education Plus, search for emails matching the route filters. To find the Gmail event logs, go to `Reporting > Audit and investigation > Gmail log events`.
+- If existing emails have been sent and match the custom route criteria, review the sender and contents for malicious URL links and attachments.
+- Identified URLs or attachments can be submitted to VirusTotal for reputational services.
+
+
+*False positive analysis*
+
+
+- This rule searches for domain-wide custom email routes created in the admin console of Google Workspace. Administrators might create custom email routes to fulfill organizational requirements.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -60,22 +104,21 @@ Administrators may create custom email routes in Google Workspace based on organ
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
+
+==== Setup
 
 
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:"google_workspace.admin" and
-event.action:("CREATE_GMAIL_SETTING" or "CHANGE_GMAIL_SETTING") and
-google_workspace.event.type:"EMAIL_SETTINGS" and
-google_workspace.admin.setting.name:("EMAIL_ROUTE" or
-"MESSAGE_SECURITY_RULE")
+[source, js]
 ----------------------------------
+event.dataset:"google_workspace.admin" and event.action:("CREATE_GMAIL_SETTING" or "CHANGE_GMAIL_SETTING")
+  and google_workspace.event.type:"EMAIL_SETTINGS" and google_workspace.admin.setting.name:("EMAIL_ROUTE" or "MESSAGE_SECURITY_RULE")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -87,10 +130,7 @@ google_workspace.admin.setting.name:("EMAIL_ROUTE" or
 ** Name: Email Collection
 ** ID: T1114
 ** Reference URL: https://attack.mitre.org/techniques/T1114/
-
-[[google-workspace-custom-gmail-route-created-or-modified-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Email Forwarding Rule
+** ID: T1114.003
+** Reference URL: https://attack.mitre.org/techniques/T1114/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-drive-encryption-key-s-accessed-from-anonymous-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-drive-encryption-key-s-accessed-from-anonymous-user.asciidoc
new file mode 100644
index 0000000000..579824d95f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-drive-encryption-key-s-accessed-from-anonymous-user.asciidoc
@@ -0,0 +1,89 @@
+[[google-workspace-drive-encryption-key-s-accessed-from-anonymous-user]]
+=== Google Workspace Drive Encryption Key(s) Accessed from Anonymous User
+
+Detects when an external (anonymous) user has viewed, copied or downloaded an encryption key file from a Google Workspace drive. Adversaries may gain access to encryption keys stored in private drives from rogue access links that do not have an expiration. Access to encryption keys may allow adversaries to access sensitive data or authenticate on behalf of users.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-google_workspace*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 10m
+
+*Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://support.google.com/drive/answer/2494822
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Configuration Audit
+* Tactic: Credential Access
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
+
+- As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
+- This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
+- To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
+- By default, `var.interval` is set to 2 hours (2h). Consider changing this interval to a lower value, such as 10 minutes (10m).
+- See the following references for further information:
+  - https://support.google.com/a/answer/7061566
+  - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
+
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where event.dataset == "google_workspace.drive" and event.action : ("copy", "view", "download") and
+    google_workspace.drive.visibility: "people_with_link" and source.user.email == "" and
+    file.extension: (
+        "token","assig", "pssc", "keystore", "pub", "pgp.asc", "ps1xml", "pem", "gpg.sig", "der", "key",
+        "p7r", "p12", "asc", "jks", "p7b", "signature", "gpg", "pgp.sig", "sst", "pgp", "gpgz", "pfx", "crt",
+        "p8", "sig", "pkcs7", "jceks", "pkcs8", "psc1", "p7c", "csr", "cer", "spc", "ps2xml")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Unsecured Credentials
+** ID: T1552
+** Reference URL: https://attack.mitre.org/techniques/T1552/
+* Sub-technique:
+** Name: Private Keys
+** ID: T1552.004
+** Reference URL: https://attack.mitre.org/techniques/T1552/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-mfa-enforcement-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-mfa-enforcement-disabled.asciidoc
index f5a7493f49..5f95525b14 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-mfa-enforcement-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-mfa-enforcement-disabled.asciidoc
@@ -5,7 +5,7 @@ Detects when multi-factor authentication (MFA) enforcement is disabled for Googl
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,77 +14,71 @@ Detects when multi-factor authentication (MFA) enforcement is disabled for Googl
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/9176657?hl=en#
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Configuration Audit
+* Tactic: Impact
+* Resources: Investigation Guide
+
+*Version*: 207
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Impact
-* Investigation Guide
 
-*Version*: 103 (<<google-workspace-mfa-enforcement-disabled-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-MFA policies may be modified by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
-==== Investigation guide
 
+*Investigating Google Workspace MFA Enforcement Disabled*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Google Workspace MFA Enforcement Disabled
+Multi-factor authentication is a process in which users are prompted during the sign-in process for an additional form of identification, such as a code on their cellphone or a fingerprint scan.
+
+If you only use a password to authenticate a user, it leaves an insecure vector for attack. If the password is weak or has been exposed elsewhere, an attacker could be using it to gain access. When you require a second form of authentication, security is increased because this additional factor isn't something that's easy for an attacker to obtain or duplicate.
 
-Multi-factor authentication is a process in which users are prompted during the sign-in process for an additional form
-of identification, such as a code on their cellphone or a fingerprint scan.
+For more information about using MFA in Google Workspace, access the https://support.google.com/a/answer/175197[official documentation].
 
-If you only use a password to authenticate a user, it leaves an insecure vector for attack. If the password is weak or
-has been exposed elsewhere, an attacker could be using it to gain access. When you require a second form of authentication,
-security is increased because this additional factor isn't something that's easy for an attacker to obtain or duplicate.
+This rule identifies the disabling of MFA enforcement in Google Workspace. This modification weakens the security of the accounts and can lead to the compromise of accounts and other assets.
 
-For more information about using MFA in Google Workspace, access the [official documentation](https://support.google.com/a/answer/175197).
 
-This rule identifies the disabling of MFA enforcement in Google Workspace. This modification weakens the security of
-the accounts and can lead to the compromise of accounts and other assets.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Contact the account and resource owners and confirm whether they are aware of this activity.
 - Check if this operation was approved and performed according to the organization's change management policy.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
 
-### False positive analysis
 
-- While this activity can be done by administrators, all users must use MFA. The security team should address any
-potential benign true positive (B-TP), as this configuration can risk the user and domain.
+- While this activity can be done by administrators, all users must use MFA. The security team should address any potential benign true positive (B-TP), as this configuration can risk the user and domain.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -94,19 +88,19 @@ potential benign true positive (B-TP), as this configuration can risk the user a
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Reactivate the multi-factor authentication enforcement.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://support.google.com/a/answer/7587183) by Google.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
 
 
 
-### Important Information Regarding Google Workspace Event Lag Times
+*Important Information Regarding Google Workspace Event Lag Times*
+
+
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -114,20 +108,22 @@ mean time to respond (MTTR).
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
 
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:google_workspace.admin and event.provider:admin and
-event.category:iam and event.action:ENFORCE_STRONG_AUTHENTICATION
-and google_workspace.admin.new_value:false
+[source, js]
 ----------------------------------
+event.dataset:google_workspace.admin and event.provider:admin
+  and event.category:iam and event.action:ENFORCE_STRONG_AUTHENTICATION
+  and google_workspace.admin.new_value:false
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -139,64 +135,3 @@ and google_workspace.admin.new_value:false
 ** Name: Account Access Removal
 ** ID: T1531
 ** Reference URL: https://attack.mitre.org/techniques/T1531/
-
-[[google-workspace-mfa-enforcement-disabled-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 15 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:google_workspace.admin and event.provider:admin and
-event.category:iam and event.action:ENFORCE_STRONG_AUTHENTICATION and
-google_workspace.admin.new_value:false
-----------------------------------
-
-Version 13 (8.3.0 release)::
-* Formatting only
-
-Version 11 (8.2.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:ENFORCE_STRONG_AUTHENTICATION and
-(gsuite.admin.new_value:false or
-google_workspace.admin.new_value:false)
-----------------------------------
-
-Version 6 (7.15.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:ENFORCE_STRONG_AUTHENTICATION and
-gsuite.admin.new_value:false
-----------------------------------
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-object-copied-from-external-drive-and-access-granted-to-custom-application.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-object-copied-from-external-drive-and-access-granted-to-custom-application.asciidoc
new file mode 100644
index 0000000000..fc53b6c035
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-object-copied-from-external-drive-and-access-granted-to-custom-application.asciidoc
@@ -0,0 +1,154 @@
+[[google-workspace-object-copied-from-external-drive-and-access-granted-to-custom-application]]
+=== Google Workspace Object Copied from External Drive and Access Granted to Custom Application
+
+Detects when a user copies a Google spreadsheet, form, document or script from an external drive. Sequence logic has been added to also detect when a user grants a custom Google application permission via OAuth shortly after. An adversary may send a phishing email to the victim with a Drive object link where "copy" is included in the URI, thus copying the object to the victim's drive. If a container-bound script exists within the object, execution will require permission access via OAuth in which the user has to accept.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-google_workspace*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/security-labs/google-workspace-attack-surface-part-one
+* https://developers.google.com/apps-script/guides/bound
+* https://support.google.com/a/users/answer/13004165#share_make_a_copy_links
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Tactic: Initial Access
+* Resources: Investigation Guide
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Google Workspace Resource Copied from External Drive and Access Granted to Custom Application*
+
+
+Google Workspace users can share access to Drive objects such as documents, sheets, and forms via email delivery or a shared link. Shared link URIs have parameters like `view` or `edit` to indicate the recipient's permissions. The `copy` parameter allows the recipient to copy the object to their own Drive, which grants the object with the same privileges as the recipient. Specific objects in Google Drive allow container-bound scripts that run on Google's Apps Script platform. Container-bound scripts can contain malicious code that executes with the recipient's privileges if in their Drive.
+
+This rule aims to detect when a user copies an external Drive object to their Drive storage and then grants permissions to a custom application via OAuth prompt.
+
+
+*Possible investigation steps*
+
+- Identify user account(s) associated by reviewing `user.name` or `source.user.email` in the alert.
+- Identify the name of the file copied by reviewing `file.name` as well as the `file.id` for triaging.
+- Identify the file type by reviewing `google_workspace.drive.file.type`.
+- With the information gathered so far, query across data for the file metadata to determine if this activity is isolated or widespread.
+- Within the OAuth token event, identify the application name by reviewing `google_workspace.token.app_name`.
+    - Review the application ID as well from `google_workspace.token.client.id`.
+    - This metadata can be used to report the malicious application to Google for permanent blacklisting.
+- Identify the permissions granted to the application by the user by reviewing `google_workspace.token.scope.data.scope_name`.
+    - This information will help pivot and triage into what services may have been affected.
+- If a container-bound script was attached to the copied object, it will also exist in the user's drive.
+    - This object should be removed from all users affected and investigated for a better understanding of the malicious code.
+
+
+*False positive analysis*
+
+- Communicate with the affected user to identify if these actions were intentional
+- If a container-bound script exists, review code to identify if it is benign or malicious
+
+
+*Response and remediation*
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+    - Resetting passwords will revoke OAuth tokens which could have been stolen.
+- Reactivate multi-factor authentication for the user.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security defaults https://cloud.google.com/security-command-center/docs/how-to-investigate-threats[provided by Google].
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+*Setup*
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
+
+- As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
+- This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
+- To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
+- By default, `var.interval` is set to 2 hours (2h). Consider changing this interval to a lower value, such as 10 minutes (10m).
+- See the following references for further information:
+  - https://support.google.com/a/answer/7061566
+  - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
+
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by source.user.email with maxspan=3m
+[file where event.dataset == "google_workspace.drive" and event.action == "copy" and
+
+    /* Should only match if the object lives in a Drive that is external to the user's GWS organization */
+    google_workspace.drive.owner_is_team_drive == "false" and google_workspace.drive.copy_type == "external" and
+
+    /* Google Script, Forms, Sheets and Document can have container-bound scripts */
+    google_workspace.drive.file.type: ("script", "form", "spreadsheet", "document")]
+
+[any where event.dataset == "google_workspace.token" and event.action == "authorize" and
+
+    /* Ensures application ID references custom app in Google Workspace and not GCP */
+    google_workspace.token.client.id : "*apps.googleusercontent.com"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-password-policy-modified.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-password-policy-modified.asciidoc
index 75afafceb8..147bea78e4 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-password-policy-modified.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-password-policy-modified.asciidoc
@@ -5,7 +5,7 @@ Detects when a Google Workspace password policy is modified. An adversary may at
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,69 +14,122 @@ Detects when a Google Workspace password policy is modified. An adversary may at
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Persistence
+*Tags*: 
 
-*Version*: 101 (<<google-workspace-password-policy-modified-history, version history>>)
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
+* Resources: Investigation Guide
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 205
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Password policies may be modified by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
-- As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
+
+*Triage and analysis*
+
+
+
+*Investigating Google Workspace Password Policy Modified*
+
+
+Google Workspace administrators manage password policies to enforce password requirements for an organization's compliance needs. Administrators have the capability to set restrictions on password length, reset frequency, reuse capability, expiration, and much more. Google Workspace also allows multi-factor authentication (MFA) and 2-step verification (2SV) for authentication.
+
+Threat actors might rely on weak password policies or restrictions to attempt credential access by using password stuffing or spraying techniques for cloud-based user accounts. Administrators might introduce increased risk to credential access from a third-party by weakening the password restrictions for an organization.
+
+This rule detects when a Google Workspace password policy is modified to decrease password complexity or to adjust the reuse and reset frequency.
+
+
+*Possible investigation steps*
+
+
+- Identify associated user account(s) by reviewing the `user.name` or `source.user.email` fields in the alert.
+- Identify the password setting that was created or adjusted by reviewing `google_workspace.admin.setting.name` field.
+- Check if a password setting was enabled or disabled by reviewing the `google_workspace.admin.new_value` and `google_workspace.admin.old_value` fields.
+- After identifying the involved user, verify administrative privileges are scoped properly to change.
+- Filter `event.dataset` for `google_workspace.login` and aggregate by `user.name`, `event.action`.
+  - The `google_workspace.login.challenge_method` field can be used to identify the challenge method used for failed and successful logins.
+
+
+*False positive analysis*
+
+
+- After identifying the user account that updated the password policy, verify whether the action was intentional.
+- Verify whether the user should have administrative privileges in Google Workspace to modify password policies.
+- Review organizational units or groups the role may have been added to and ensure the new privileges align properly.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Consider resetting passwords for potentially affected users.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Reactivate multi-factor authentication for the user.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
+
+- As per Google's documentation, Google Workspace administrators might observe lag times ranging from several minutes to 3 days between the event occurrence time and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
 - By default, `var.interval` is set to 2 hours (2h). Consider changing this interval to a lower value, such as 10 minutes (10m).
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
+
+==== Setup
 
 
+The Google Workspace Fleet integration, the Filebeat module, or data that's similarly structured is required for this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:google_workspace.admin and event.provider:admin and
-event.category:iam and event.action:(CHANGE_APPLICATION_SETTING or
-CREATE_APPLICATION_SETTING) and
-google_workspace.admin.setting.name:( "Password Management -
-Enforce strong password" or "Password Management - Password reset
-frequency" or "Password Management - Enable password reuse" or
-"Password Management - Enforce password policy at next login" or
-"Password Management - Minimum password length" or "Password
-Management - Maximum password length" )
+[source, js]
 ----------------------------------
+event.dataset:google_workspace.admin and event.provider:admin and event.category:iam and
+  event.action:(CHANGE_APPLICATION_SETTING or CREATE_APPLICATION_SETTING) and
+  google_workspace.admin.setting.name:(
+    "Password Management - Enforce strong password" or
+    "Password Management - Password reset frequency" or
+    "Password Management - Enable password reuse" or
+    "Password Management - Enforce password policy at next login" or
+    "Password Management - Minimum password length" or
+    "Password Management - Maximum password length"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -88,72 +141,3 @@ Management - Maximum password length" )
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[google-workspace-password-policy-modified-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 15 (8.4.0 release)::
-* Formatting only
-
-Version 13 (8.3.0 release)::
-* Formatting only
-
-Version 11 (8.2.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:(CHANGE_APPLICATION_SETTING or
-CREATE_APPLICATION_SETTING) and gsuite.admin.setting.name:(
-"Password Management - Enforce strong password" or "Password
-Management - Password reset frequency" or "Password Management -
-Enable password reuse" or "Password Management - Enforce password
-policy at next login" or "Password Management - Minimum password
-length" or "Password Management - Maximum password length" ) or
-google_workspace.admin.setting.name:( "Password Management -
-Enforce strong password" or "Password Management - Password reset
-frequency" or "Password Management - Enable password reuse" or
-"Password Management - Enforce password policy at next login" or
-"Password Management - Minimum password length" or "Password
-Management - Maximum password length" )
-----------------------------------
-
-Version 6 (7.15.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:(CHANGE_APPLICATION_SETTING or
-CREATE_APPLICATION_SETTING) and gsuite.admin.setting.name:( "Password
-Management - Enforce strong password" or "Password Management -
-Password reset frequency" or "Password Management - Enable password
-reuse" or "Password Management - Enforce password policy at next
-login" or "Password Management - Minimum password length" or "Password
-Management - Maximum password length" )
-----------------------------------
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-restrictions-for-google-marketplace-modified-to-allow-any-app.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-restrictions-for-google-marketplace-modified-to-allow-any-app.asciidoc
index 658014bf18..d030e3f40a 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-restrictions-for-google-marketplace-modified-to-allow-any-app.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-restrictions-for-google-marketplace-modified-to-allow-any-app.asciidoc
@@ -5,7 +5,7 @@ Detects when the Google Marketplace restrictions are changed to allow any applic
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,46 +14,96 @@ Detects when the Google Marketplace restrictions are changed to allow any applic
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/6089179?hl=en
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Defense Evasion
 
-*Version*: 2 (<<google-workspace-restrictions-for-google-marketplace-modified-to-allow-any-app-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Last modified ({stack} release)*: 8.6.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Triage and analysis*
 
-==== Potential false positives
 
-Applications can be added and removed from blocklists by Google Workspace administrators, but they can all be explicitly allowed for users. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
-==== Investigation guide
+*Investigating Google Workspace Restrictions for Google Marketplace Modified to Allow Any App*
 
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
+Google Workspace Marketplace is an online store for free and paid web applications that work with Google Workspace services and third-party software. Listed applications are based on Google APIs or Google Apps Script and created by both Google and third-party developers.
+
+Marketplace applications require access to specific Google Workspace resources. Applications can be installed by individual users, if they have permission, or can be installed for an entire Google Workspace domain by administrators. Consent screens typically display what permissions and privileges the application requires during installation. As a result, malicious Marketplace applications may require more permissions than necessary or have malicious intent.
+
+Google clearly states that they are not responsible for any product on the Marketplace that originates from a source other than Google.
+
+This rule identifies when the global allow-all setting is enabled for Google Workspace Marketplace applications.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
+- This rule relies on data from `google_workspace.admin`, thus indicating the associated user has administrative privileges to the Marketplace.
+- Search for `event.action` is `ADD_APPLICATION` to identify applications installed after these changes were made.
+    - The `google_workspace.admin.application.name` field will help identify what applications were added.
+- With the user account, review other potentially related events within the last 48 hours.
+- Re-assess the permissions and reviews of the Marketplace applications to determine if they violate organizational policies or introduce unexpected risks.
+- With access to the Google Workspace admin console, determine if the application was installed domain-wide or individually by visiting `Apps > Google Workspace Marketplace Apps`.
+
+
+*False positive analysis*
+
+
+- Identify the user account associated with this action and assess their administrative privileges with Google Workspace Marketplace.
+- Google Workspace administrators may intentionally add an application from the marketplace based on organizational needs.
+    - Follow up with the user who added the application to ensure this was intended.
+- Verify the application identified has been assessed thoroughly by an administrator.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
+
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -61,24 +111,22 @@ Applications can be added and removed from blocklists by Google Workspace admini
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
+
+==== Setup
 
 
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:"google_workspace.admin" and
-event.action:"CHANGE_APPLICATION_SETTING" and event.category:(iam or
-configuration) and
-google_workspace.event.type:"APPLICATION_SETTINGS" and
-google_workspace.admin.application.name:"Google Workspace Marketplace"
-and google_workspace.admin.setting.name:"Apps Access Setting Allowlist
-access" and google_workspace.admin.new_value:"ALLOW_ALL"
+[source, js]
 ----------------------------------
+event.dataset:"google_workspace.admin" and event.action:"CHANGE_APPLICATION_SETTING" and event.category:(iam or configuration)
+    and google_workspace.event.type:"APPLICATION_SETTINGS" and google_workspace.admin.application.name:"Google Workspace Marketplace"
+        and google_workspace.admin.setting.name:"Apps Access Setting Allowlist access"  and google_workspace.admin.new_value:"ALLOW_ALL"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -90,10 +138,7 @@ access" and google_workspace.admin.new_value:"ALLOW_ALL"
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[google-workspace-restrictions-for-google-marketplace-modified-to-allow-any-app-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-role-modified.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-role-modified.asciidoc
index f01705e7f6..d482742f00 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-role-modified.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-role-modified.asciidoc
@@ -5,7 +5,7 @@ Detects when a custom admin role or its permissions are modified. An adversary m
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,45 +14,98 @@ Detects when a custom admin role or its permissions are modified. An adversary m
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/2406043?hl=en
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Persistence
+
+*Version*: 205
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Identity and Access
 
-*Version*: 101 (<<google-workspace-role-modified-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Google Workspace admin roles may be modified by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
-==== Investigation guide
 
+*Investigating Google Workspace Role Modified*
+
+
+Google Workspace roles allow administrators to assign specific permissions to users or groups where the principle of least privilege (PoLP) is recommended. Admin roles in Google Workspace grant users access to the Google Admin console, where more domain-wide settings are accessible. Google Workspace contains prebuilt admin roles for performing business functions related to users, groups, and services. Custom administrator roles can be created where prebuilt roles are not preferred. Each Google Workspace service has a set of custodial privileges that can be added to custom roles.
+
+Roles assigned to users will grant them additional permissions and privileges within the Google Workspace domain. Threat actors might modify existing roles with new privileges to advance their intrusion efforts and laterally move throughout the organization. Users with unexpected privileges might also cause operational dysfunction if unfamiliar settings are adjusted without warning.
+
+This rule identifies when a Google Workspace role is modified.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
+- Identify the role modified by reviewing the `google_workspace.admin.role.name` field in the alert.
+- Identify the privilege that was added or removed by reviewing the `google_workspace.admin.privilege.name` field in the alert.
+- After identifying the involved user, verify administrative privileges are scoped properly.
+- To identify other users with this role, search for `event.action: ASSIGN_ROLE`
+  - Add `google_workspace.admin.role.name` with the role added as an additional filter.
+  - Adjust the relative time accordingly to identify all users that were assigned this role.
+- Identify if the user account was recently created by searching for `event.action: CREATE_USER`.
+- If a privilege was added, monitor users assigned this role for the next 24 hours and look for attempts to use the new privilege.
+  - The `event.provider` field will help filter for specific services in Google Workspace such as Drive or Admin.
+  - The `event.action` field will help trace actions that are being taken by users.
+
+
+*False positive analysis*
+
+
+- After identifying the user account that modified the role, verify the action was intentional.
+- Verify that the user is expected to have administrative privileges in Google Workspace to modify roles.
+- Review organizational units or groups the role might have been added to and ensure the new privileges align properly.
+- Use the `user.name` to filter for `event.action` where `ADD_PRIVILEGE` or `UPDATE_ROLE` has been seen before to check if these actions are new or historical.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -60,19 +113,20 @@ Google Workspace admin roles may be modified by system administrators. Verify th
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
 
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:google_workspace.admin and event.provider:admin and
-event.category:iam and event.action:(ADD_PRIVILEGE or UPDATE_ROLE)
+[source, js]
 ----------------------------------
+event.dataset:google_workspace.admin and event.provider:admin and event.category:iam and event.action:(ADD_PRIVILEGE or UPDATE_ROLE)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,44 +138,3 @@ event.category:iam and event.action:(ADD_PRIVILEGE or UPDATE_ROLE)
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[google-workspace-role-modified-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 14 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:(ADD_PRIVILEGE or UPDATE_ROLE)
-----------------------------------
-
-Version 5 (7.15.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-suspended-user-account-renewed.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-suspended-user-account-renewed.asciidoc
new file mode 100644
index 0000000000..d78de43263
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-suspended-user-account-renewed.asciidoc
@@ -0,0 +1,84 @@
+[[google-workspace-suspended-user-account-renewed]]
+=== Google Workspace Suspended User Account Renewed
+
+Detects when a previously suspended user's account is renewed in Google Workspace. An adversary may renew a suspended user account to maintain access to the Google Workspace organization with a valid account.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-google_workspace*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 10m
+
+*Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://support.google.com/a/answer/1110339
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Identity and Access Audit
+* Tactic: Initial Access
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
+
+- As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
+- This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
+- To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
+- By default, `var.interval` is set to 2 hours (2h). Consider changing this interval to a lower value, such as 10 minutes (10m).
+- See the following references for further information:
+  - https://support.google.com/a/answer/7061566
+  - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
+
+==== Setup
+
+
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:google_workspace.admin and event.category:iam and event.action:UNSUSPEND_USER
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Cloud Accounts
+** ID: T1078.004
+** Reference URL: https://attack.mitre.org/techniques/T1078/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/google-workspace-user-organizational-unit-changed.asciidoc b/docs/detections/prebuilt-rules/rule-details/google-workspace-user-organizational-unit-changed.asciidoc
index b26e319a68..87d675c7e2 100644
--- a/docs/detections/prebuilt-rules/rule-details/google-workspace-user-organizational-unit-changed.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/google-workspace-user-organizational-unit-changed.asciidoc
@@ -5,7 +5,7 @@ Users in Google Workspace are typically assigned a specific organizational unit
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,46 +14,95 @@ Users in Google Workspace are typically assigned a specific organizational unit
 
 *Risk score*: 21
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.google.com/a/answer/6328701?hl=en#
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Configuration Audit
+* Tactic: Persistence
+* Resources: Investigation Guide
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Persistence
 
-*Version*: 2 (<<google-workspace-user-organizational-unit-changed-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.5.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Google Workspace administrators may adjust change which organizational unit a user belongs to as a result of internal role adjustments.
 
-==== Investigation guide
 
+*Investigating Google Workspace User Organizational Unit Changed*
+
+
+An organizational unit is a group that an administrator can create in the Google Admin console to apply settings to a specific set of users for Google Workspace. By default, all users are placed in the top-level (parent) organizational unit. Child organizational units inherit the settings from the parent but can be changed to fit the needs of the child organizational unit.
+
+Permissions and privileges for users are often inherited from the organizational unit they are placed in. Therefore, if a user is changed to a separate organizational unit, they will inherit all privileges and permissions. User accounts may have unexpected privileges when switching organizational units that would allow a threat actor to gain a stronger foothold within the organization. The principle of least privileged (PoLP) should be followed when users are switched to different groups in Google Workspace.
+
+This rule identifies when a user has been moved to a different organizational unit.
+
+
+*Possible investigation steps*
+
+
+- Identify the associated user accounts by reviewing `user.name` or `user.email` fields in the alert.
+  - The `user.target.email` field contains the user that had their assigned organizational unit switched.
+- Identify the user's previously assigned unit and new organizational unit by checking the `google_workspace.admin.org_unit.name` and `google_workspace.admin.new_value` fields.
+- Identify Google Workspace applications whose settings were explicitly set for this organizational unit.
+    - Search for `event.action` is `CREATE_APPLICATION_SETTING` where `google_workspace.admin.org_unit.name` is the new organizational unit.
+- After identifying the involved user, verify administrative privileges are scoped properly to allow changing user organizational units.
+- Identify if the user account was recently created by searching for `event.action: CREATE_USER`.
+  - Add `user.email` with the target user account that recently had their organizational unit changed.
+- Filter on `user.name` or `user.target.email` of the user who took this action and review the last 48 hours of activity for anything that may indicate a compromise.
+
+
+*False positive analysis*
+
+
+- After identifying the user account that changed another user's organizational unit, verify the action was intentional.
+- Verify whether the target user who received this update is expected to inherit privileges from the new organizational unit.
+- Review potential maintenance notes or organizational changes. They might explain why a user's organization was changed.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -61,20 +110,21 @@ Google Workspace administrators may adjust change which organizational unit a us
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
+
+==== Setup
 
 
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:"google_workspace.admin" and event.type:change and
-event.category:iam and google_workspace.event.type:"USER_SETTINGS"
-and event.action:"MOVE_USER_TO_ORG_UNIT"
+[source, js]
 ----------------------------------
+event.dataset:"google_workspace.admin" and event.type:change and event.category:iam
+    and google_workspace.event.type:"USER_SETTINGS" and event.action:"MOVE_USER_TO_ORG_UNIT"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -86,10 +136,7 @@ and event.action:"MOVE_USER_TO_ORG_UNIT"
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[google-workspace-user-organizational-unit-changed-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Additional Cloud Roles
+** ID: T1098.003
+** Reference URL: https://attack.mitre.org/techniques/T1098/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/group-policy-abuse-for-privilege-addition.asciidoc b/docs/detections/prebuilt-rules/rule-details/group-policy-abuse-for-privilege-addition.asciidoc
index 068857c561..20e53d8574 100644
--- a/docs/detections/prebuilt-rules/rule-details/group-policy-abuse-for-privilege-addition.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/group-policy-abuse-for-privilege-addition.asciidoc
@@ -5,99 +5,122 @@ Detects the first occurrence of a modification to Group Policy Object Attributes
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0025_windows_audit_directory_service_changes.md
 * https://labs.f-secure.com/tools/sharpgpoabuse
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Active Directory
-* Investigation Guide
-
-*Version*: 102 (<<group-policy-abuse-for-privilege-addition-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Active Directory
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Group Policy Abuse for Privilege Addition
+*Triage and analysis*
+
+
+
+*Investigating Group Policy Abuse for Privilege Addition*
+
+
+Group Policy Objects (GPOs) can be used to add rights and/or modify Group Membership on GPOs by changing the contents of an INF file named GptTmpl.inf, which is responsible for storing every setting under the Security Settings container in the GPO. This file is unique for each GPO, and only exists if the GPO contains security settings. Example Path: "\\DC.com\SysVol\DC.com\Policies\{PolicyGUID}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf"
+
 
-Group Policy Objects (GPOs) can be used to add rights and/or modify Group Membership on GPOs by changing the contents of an INF
-file named GptTmpl.inf, which is responsible for storing every setting under the Security Settings container in the GPO.
-This file is unique for each GPO, and only exists if the GPO contains security settings.
-Example Path: "\\DC.com\SysVol\DC.com\Policies\{PolicyGUID}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf"
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- This attack abuses a legitimate mechanism of Active Directory, so it is important to determine whether the activity
-is legitimate and the administrator is authorized to perform this operation.
-- Retrieve the contents of the `GptTmpl.inf` file, and under the `Privilege Rights` section, look for potentially
-dangerous high privileges, for example: SeTakeOwnershipPrivilege, SeEnableDelegationPrivilege, etc.
+- This attack abuses a legitimate mechanism of Active Directory, so it is important to determine whether the activity is legitimate and the administrator is authorized to perform this operation.
+- Retrieve the contents of the `GptTmpl.inf` file, and under the `Privilege Rights` section, look for potentially dangerous high privileges, for example: SeTakeOwnershipPrivilege, SeEnableDelegationPrivilege, etc.
 - Inspect the user security identifiers (SIDs) associated with these privileges, and if they should have these privileges.
 
-### False positive analysis
 
-- Inspect whether the user that has done the modifications should be allowed to. The user name can be found in the
-`winlog.event_data.SubjectUserName` field.
+*False positive analysis*
+
+
+- Inspect whether the user that has done the modifications should be allowed to. The user name can be found in the `winlog.event_data.SubjectUserName` field.
+
+
+*Related rules*
 
-### Related rules
 
 - Scheduled Task Execution at Scale via GPO - 15a8ba77-1c13-4274-88fe-6bd14133861e
 - Startup/Logon Script added to Group Policy Object - 16fac1a1-21ee-4ca6-b720-458e3855d046
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - The investigation and containment must be performed in every computer controlled by the GPO, where necessary.
 - Remove the script from the GPO.
 - Check if other GPOs have suspicious scripts attached.
-----------------------------------
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Directory Service Changes' audit policy must be configured (Success Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Changes (Success,Failure)
+```
 
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.code: "5136" and
-winlog.event_data.AttributeLDAPDisplayName:"gPCMachineExtensionNames"
-and winlog.event_data.AttributeValue:(*827D319E-6EAC-11D2-A4EA-00C04F7
-9F83A* and *803E14A0-B4FB-11D0-A0D0-00A0C90F574B*)
-----------------------------------
+  winlog.event_data.AttributeLDAPDisplayName:"gPCMachineExtensionNames" and
+  winlog.event_data.AttributeValue:(*827D319E-6EAC-11D2-A4EA-00C04F79F83A* and *803E14A0-B4FB-11D0-A0D0-00A0C90F574B*)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -109,33 +132,7 @@ and winlog.event_data.AttributeValue:(*827D319E-6EAC-11D2-A4EA-00C04F7
 ** Name: Domain Policy Modification
 ** ID: T1484
 ** Reference URL: https://attack.mitre.org/techniques/T1484/
-
-[[group-policy-abuse-for-privilege-addition-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.code: "5136" and
-winlog.event_data.AttributeLDAPDisplayName:"gPCMachineExtensionNames"
-and winlog.event_data.AttributeValue:(*827D319E-6EAC-11D2-A4EA-00C04F
-79F83A* and *803E14A0-B4FB-11D0-A0D0-00A0C90F574B*)
-----------------------------------
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Group Policy Modification
+** ID: T1484.001
+** Reference URL: https://attack.mitre.org/techniques/T1484/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/group-policy-discovery-via-microsoft-gpresult-utility.asciidoc b/docs/detections/prebuilt-rules/rule-details/group-policy-discovery-via-microsoft-gpresult-utility.asciidoc
new file mode 100644
index 0000000000..9d8514656c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/group-policy-discovery-via-microsoft-gpresult-utility.asciidoc
@@ -0,0 +1,112 @@
+[[group-policy-discovery-via-microsoft-gpresult-utility]]
+=== Group Policy Discovery via Microsoft GPResult Utility
+
+Detects the usage of gpresult.exe to query group policy objects. Attackers may query group policy objects during the reconnaissance phase after compromising a system to gain a better understanding of the active directory environment and possible methods to escalate privileges or move laterally.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Group Policy Discovery via Microsoft GPResult Utility*
+
+
+Group Policy is a Windows feature that allows administrators to manage and configure settings for users and computers in an Active Directory environment. The Microsoft GPResult utility (gpresult.exe) is a command-line tool used to query and display Group Policy Objects (GPOs) applied to a system. Attackers may abuse this utility to gain insights into the active directory environment and identify potential privilege escalation or lateral movement opportunities.
+
+The detection rule 'Group Policy Discovery via Microsoft GPResult Utility' is designed to identify the usage of gpresult.exe with specific arguments ("/z", "/v", "/r", "/x") that are commonly used by adversaries during the reconnaissance phase to perform group policy discovery.
+
+
+*Possible investigation steps*
+
+
+- Review the alert details to understand the context of the gpresult.exe usage, such as the user account, system, and time of execution.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+- Inspect the host for suspicious or abnormal behavior in the alert timeframe.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate any abnormal behavior by the parent process, such as network connections, registry or file modifications, and any other spawned child processes.
+
+
+*False positive analysis*
+
+
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Reimage the host operating system or restore the compromised files to clean versions.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+(process.name: "gpresult.exe" or ?process.pe.original_file_name == "gprslt.exe") and process.args: ("/z", "/v", "/r", "/x")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Group Policy Discovery
+** ID: T1615
+** Reference URL: https://attack.mitre.org/techniques/T1615/
diff --git a/docs/detections/prebuilt-rules/rule-details/halfbaked-command-and-control-beacon.asciidoc b/docs/detections/prebuilt-rules/rule-details/halfbaked-command-and-control-beacon.asciidoc
index 34fa6de3e5..c22cd8d2fb 100644
--- a/docs/detections/prebuilt-rules/rule-details/halfbaked-command-and-control-beacon.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/halfbaked-command-and-control-beacon.asciidoc
@@ -5,73 +5,63 @@ Halfbaked is a malware family used to establish persistence in a contested netwo
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.fireeye.com/blog/threat-research/2017/04/fin7-phishing-lnk.html
 * https://attack.mitre.org/software/S0151/
 
-*Tags*:
-
-* Elastic
-* Network
-* Threat Detection
-* Command and Control
-* Host
+*Tags*: 
 
-*Version*: 100 (<<halfbaked-command-and-control-beacon-history, version history>>)
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Domain: Endpoint
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-This rule should be tailored to exclude systems, either as sources or destinations, in which this behavior is expected.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Threat intel
 
-This activity has been observed in FIN7 campaigns.
-----------------------------------
+*Threat intel*
+
 
+This activity has been observed in FIN7 campaigns.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network OR network_traffic) AND network.protocol:http
-AND network.transport:tcp AND
-url.full:/http:\/\/[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}\/cd/
-AND destination.port:(53 OR 80 OR 8080 OR 443)
+[source, js]
 ----------------------------------
+(event.dataset: (network_traffic.tls OR network_traffic.http) OR
+  (event.category: (network OR network_traffic) AND network.protocol: http)) AND
+  network.transport:tcp AND url.full:/http:\/\/[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}\/cd/ AND
+  destination.port:(53 OR 80 OR 8080 OR 443)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -83,33 +73,11 @@ AND destination.port:(53 OR 80 OR 8080 OR 443)
 ** Name: Application Layer Protocol
 ** ID: T1071
 ** Reference URL: https://attack.mitre.org/techniques/T1071/
-
-[[halfbaked-command-and-control-beacon-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network OR network_traffic) AND network.protocol:http
-AND network.transport:tcp AND
-url.full:/http:\/\/[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}\/cd/
-AND destination.port:(53 OR 80 OR 8080 OR 443)
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Technique:
+** Name: Dynamic Resolution
+** ID: T1568
+** Reference URL: https://attack.mitre.org/techniques/T1568/
+* Sub-technique:
+** Name: Domain Generation Algorithms
+** ID: T1568.002
+** Reference URL: https://attack.mitre.org/techniques/T1568/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/hidden-files-and-directories-via-hidden-flag.asciidoc b/docs/detections/prebuilt-rules/rule-details/hidden-files-and-directories-via-hidden-flag.asciidoc
new file mode 100644
index 0000000000..32e57f3f62
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/hidden-files-and-directories-via-hidden-flag.asciidoc
@@ -0,0 +1,70 @@
+[[hidden-files-and-directories-via-hidden-flag]]
+=== Hidden Files and Directories via Hidden Flag
+
+Identify activity related where adversaries can add the 'hidden' flag to files to hide them from the user in an attempt to evade detection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where event.type == "creation" and process.name == "chflags"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hide Artifacts
+** ID: T1564
+** Reference URL: https://attack.mitre.org/techniques/T1564/
+* Sub-technique:
+** Name: Hidden Files and Directories
+** ID: T1564.001
+** Reference URL: https://attack.mitre.org/techniques/T1564/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/high-mean-of-process-arguments-in-an-rdp-session.asciidoc b/docs/detections/prebuilt-rules/rule-details/high-mean-of-process-arguments-in-an-rdp-session.asciidoc
new file mode 100644
index 0000000000..fc91a1e8fe
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/high-mean-of-process-arguments-in-an-rdp-session.asciidoc
@@ -0,0 +1,92 @@
+[[high-mean-of-process-arguments-in-an-rdp-session]]
+=== High Mean of Process Arguments in an RDP Session
+
+A machine learning job has detected unusually high number of process arguments in an RDP session. Executing sophisticated attacks such as lateral movement can involve the use of complex commands, obfuscation mechanisms, redirection and piping, which in turn increases the number of arguments in a command.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-12h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/lmd
+* https://www.elastic.co/blog/detecting-lateral-movement-activity-a-new-kibana-integration
+* https://www.elastic.co/blog/remote-desktop-protocol-connections-elastic-security
+
+*Tags*: 
+
+* Use Case: Lateral Movement Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Lateral Movement Detection integration assets to be installed, as well as file and Windows RDP process events collected by the Elastic Defend integration.  
+
+
+*Lateral Movement Detection Setup*
+
+The Lateral Movement Detection integration detects lateral movement activity by identifying abnormalities in file and Windows RDP events. Anomalies are detected using Elastic's Anomaly Detection feature.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Lateral Movement Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows RDP process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Lateral Movement Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Lateral Movement Detection and select the integration to see more details about it.
+- Under Settings, click Install Lateral Movement Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Lateral Movement Detection, you'll need to enable the corresponding Anomaly Detection jobs.
+- Before enabling the Anomaly Detection jobs, confirm that the Pivot Transform asset is installed and actively gathering data in the destination index `ml-rdp-lmd`.
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your transformed RDP process data i.e.`ml-rdp-lmd`.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/lmd/kibana/ml_module/lmd-ml.json[this] configuration file, you will see a card for Lateral Movement Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/high-mean-of-rdp-session-duration.asciidoc b/docs/detections/prebuilt-rules/rule-details/high-mean-of-rdp-session-duration.asciidoc
new file mode 100644
index 0000000000..465bb2ecaf
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/high-mean-of-rdp-session-duration.asciidoc
@@ -0,0 +1,92 @@
+[[high-mean-of-rdp-session-duration]]
+=== High Mean of RDP Session Duration
+
+A machine learning job has detected unusually high mean of RDP session duration. Long RDP sessions can be used to evade detection mechanisms via session persistence, and might be used to perform tasks such as lateral movement, that might require uninterrupted access to a compromised machine.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-12h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/lmd
+* https://www.elastic.co/blog/detecting-lateral-movement-activity-a-new-kibana-integration
+* https://www.elastic.co/blog/remote-desktop-protocol-connections-elastic-security
+
+*Tags*: 
+
+* Use Case: Lateral Movement Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Lateral Movement Detection integration assets to be installed, as well as file and Windows RDP process events collected by the Elastic Defend integration.  
+
+
+*Lateral Movement Detection Setup*
+
+The Lateral Movement Detection integration detects lateral movement activity by identifying abnormalities in file and Windows RDP events. Anomalies are detected using Elastic's Anomaly Detection feature.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Lateral Movement Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows RDP process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Lateral Movement Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Lateral Movement Detection and select the integration to see more details about it.
+- Under Settings, click Install Lateral Movement Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Lateral Movement Detection, you'll need to enable the corresponding Anomaly Detection jobs.
+- Before enabling the Anomaly Detection jobs, confirm that the Pivot Transform asset is installed and actively gathering data in the destination index `ml-rdp-lmd`.
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your transformed RDP process data i.e.`ml-rdp-lmd`.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/lmd/kibana/ml_module/lmd-ml.json[this] configuration file, you will see a card for Lateral Movement Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/high-number-of-cloned-github-repos-from-pat.asciidoc b/docs/detections/prebuilt-rules/rule-details/high-number-of-cloned-github-repos-from-pat.asciidoc
new file mode 100644
index 0000000000..d71c2ab309
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/high-number-of-cloned-github-repos-from-pat.asciidoc
@@ -0,0 +1,61 @@
+[[high-number-of-cloned-github-repos-from-pat]]
+=== High Number of Cloned GitHub Repos From PAT
+
+Detects a high number of unique private repo clone events originating from a single personal access token within a short time period.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Execution
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:"github.audit" and event.category:"configuration" and event.action:"git.clone" and 
+github.programmatic_access_type:("OAuth access token" or "Fine-grained personal access token") and 
+github.repository_public:false
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Serverless Execution
+** ID: T1648
+** Reference URL: https://attack.mitre.org/techniques/T1648/
diff --git a/docs/detections/prebuilt-rules/rule-details/high-number-of-okta-user-password-reset-or-unlock-attempts.asciidoc b/docs/detections/prebuilt-rules/rule-details/high-number-of-okta-user-password-reset-or-unlock-attempts.asciidoc
index 2a1f514c14..8b72e016ff 100644
--- a/docs/detections/prebuilt-rules/rule-details/high-number-of-okta-user-password-reset-or-unlock-attempts.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/high-number-of-okta-user-password-reset-or-unlock-attempts.asciidoc
@@ -5,7 +5,7 @@ Identifies a high number of Okta user password reset or account unlock attempts.
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,66 +14,90 @@ Identifies a high number of Okta user password reset or account unlock attempts.
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Defense Evasion
+
+*Version*: 208
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Identity and Access
+* @BenB196
+* Austin Songer
+
+*Rule license*: Elastic License v2
 
-*Version*: 102 (<<high-number-of-okta-user-password-reset-or-unlock-attempts-history, version history>>)
 
-*Added ({stack} release)*: 7.10.0
+==== Investigation guide
 
-*Last modified ({stack} release)*: 8.6.0
 
-*Rule authors*: Elastic, @BenB196, Austin Songer
 
-*Rule license*: Elastic License v2
+*Triage and analysis*
 
-==== Potential false positives
 
-The number of Okta user password reset or account unlock attempts will likely vary between organizations. To fit this rule to their organization, users can duplicate this rule and edit the schedule and threshold values in the new rule.
 
-==== Investigation guide
+*Investigating High Number of Okta User Password Reset or Unlock Attempts*
 
 
-[source,markdown]
-----------------------------------
+This rule is designed to detect a suspiciously high number of password reset or account unlock attempts in Okta. Excessive password resets or account unlocks can be indicative of an attacker's attempt to gain unauthorized access to an account.
+
+
+*Possible investigation steps:*
+
+- Identify the actor associated with the excessive attempts. The `okta.actor.alternate_id` field can be used for this purpose.
+- Determine the client used by the actor. You can look at `okta.client.device`, `okta.client.ip`, `okta.client.user_agent.raw_user_agent`, `okta.client.ip_chain.ip`, and `okta.client.geographical_context`.
+- Review the `okta.outcome.result` and `okta.outcome.reason` fields to understand the outcome of the password reset or unlock attempts.
+- Review the event actions associated with these attempts. Look at the `event.action` field and filter for actions related to password reset and account unlock attempts.
+- Check for other similar patterns of behavior from the same actor or IP address. If there is a high number of failed login attempts before the password reset or unlock attempts, this may suggest a brute force attack.
+- Also, look at the times when these attempts were made. If these were made during off-hours, it could further suggest an adversary's activity.
+
+
+*False positive analysis:*
+
+- This alert might be a false positive if there are legitimate reasons for a high number of password reset or unlock attempts. This could be due to the user forgetting their password or account lockouts due to too many incorrect attempts.
+- Check the actor's past behavior. If this is their usual behavior and they have a valid reason for it, then it might be a false positive.
+
+
+*Response and remediation:*
+
+- If unauthorized attempts are confirmed, initiate the incident response process.
+- Reset the user's password and enforce MFA re-enrollment, if applicable.
+- Block the IP address or device used in the attempts, if they appear suspicious.
+- If the attack was facilitated by a particular technique, ensure your systems are patched or configured to prevent such techniques.
+- Consider a security review of your Okta policies and rules to ensure they follow security best practices.
+
+==== Setup
 
-----------------------------------
 
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:okta.system and
-event.action:(system.email.account_unlock.sent_message or
-system.email.password_reset.sent_message or
-system.sms.send_account_unlock_message or
-system.sms.send_password_reset_message or
-system.voice.send_account_unlock_call or
-system.voice.send_password_reset_call or
-user.account.unlock_token)
-----------------------------------
+  event.action:(system.email.account_unlock.sent_message or system.email.password_reset.sent_message or
+                system.sms.send_account_unlock_message or system.sms.send_password_reset_message or
+                system.voice.send_account_unlock_call or system.voice.send_password_reset_call or
+                user.account.unlock_token)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -85,8 +109,6 @@ user.account.unlock_token)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -95,8 +117,6 @@ user.account.unlock_token)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -105,39 +125,3 @@ user.account.unlock_token)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[high-number-of-okta-user-password-reset-or-unlock-attempts-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:okta.system and
-event.action:(system.email.account_unlock.sent_message or
-system.email.password_reset.sent_message or
-system.sms.send_account_unlock_message or
-system.sms.send_password_reset_message or
-system.voice.send_account_unlock_call or
-system.voice.send_password_reset_call or user.account.unlock_token)
-----------------------------------
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/high-number-of-process-and-or-service-terminations.asciidoc b/docs/detections/prebuilt-rules/rule-details/high-number-of-process-and-or-service-terminations.asciidoc
index 8a806e9522..ad7ecf7a81 100644
--- a/docs/detections/prebuilt-rules/rule-details/high-number-of-process-and-or-service-terminations.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/high-number-of-process-and-or-service-terminations.asciidoc
@@ -5,104 +5,102 @@ This rule identifies a high number (10) of process terminations (stop, delete, o
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/security-labs/luna-ransomware-attack-pattern
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Impact
-* Investigation Guide
-
-*Version*: 102 (<<high-number-of-process-and-or-service-terminations-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating High Number of Process and/or Service Terminations
+*Triage and analysis*
+
+
 
-Attackers can stop services and kill processes for a variety of purposes. For example, they can stop services associated
-with business applications and databases to release the lock on files used by these applications so they may be encrypted,
-or stop security and backup solutions, etc.
+*Investigating High Number of Process and/or Service Terminations*
 
-This rule identifies a high number (10) of service and/or process terminations (stop, delete, or suspend) from the same
-host within a short time period.
 
-#### Possible investigation steps
+Attackers can stop services and kill processes for a variety of purposes. For example, they can stop services associated with business applications and databases to release the lock on files used by these applications so they may be encrypted, or stop security and backup solutions, etc.
 
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+This rule identifies a high number (10) of service and/or process terminations (stop, delete, or suspend) from the same host within a short time period.
+
+
+*Possible investigation steps*
+
+
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Check if any files on the host machine have been encrypted.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further destructive behavior, which is commonly associated with this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Reimage the host operating system or restore it to the operational state.
-- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look
-for ransomware preparation and execution activities.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look for ransomware preparation and execution activities.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:start and process.name:(net.exe
-or sc.exe or taskkill.exe) and process.args:(stop or pause or delete
-or "/PID" or "/IM" or "/T" or "/F" or "/t" or "/f" or "/im" or "/pid")
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and event.type:start and process.name:(net.exe or sc.exe or taskkill.exe) and
+ process.args:(stop or pause or delete or "/PID" or "/IM" or "/T" or "/F" or "/t" or "/f" or "/im" or "/pid") and
+ not process.parent.name:osquerybeat.exe
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -114,28 +112,3 @@ or "/PID" or "/IM" or "/T" or "/F" or "/t" or "/f" or "/im" or "/pid")
 ** Name: Service Stop
 ** ID: T1489
 ** Reference URL: https://attack.mitre.org/techniques/T1489/
-
-[[high-number-of-process-and-or-service-terminations-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.16.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/high-number-of-process-terminations.asciidoc b/docs/detections/prebuilt-rules/rule-details/high-number-of-process-terminations.asciidoc
index d6b75b2349..6e78d16008 100644
--- a/docs/detections/prebuilt-rules/rule-details/high-number-of-process-terminations.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/high-number-of-process-terminations.asciidoc
@@ -5,100 +5,137 @@ This rule identifies a high number (10) of process terminations via pkill from t
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Impact
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<high-number-of-process-terminations-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating High Number of Process Terminations
+*Triage and analysis*
+
 
-Attackers can kill processes for a variety of purposes. For example, they can kill process associated
-with business applications and databases to release the lock on files used by these applications so they may be
-encrypted,or stop security and backup solutions, etc.
 
-This rule identifies a high number (10) of process terminations via pkill from the same
-host within a short time period.
+*Investigating High Number of Process Terminations*
+
+
+Attackers can kill processes for a variety of purposes. For example, they can kill process associated with business applications and databases to release the lock on files used by these applications so they may be encrypted,or stop security and backup solutions, etc.
+
+This rule identifies a high number (10) of process terminations via pkill from the same host within a short time period.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-Detection alerts from this rule indicate High Number of Process Terminations from the same host
-Here are some possible avenues of investigation:
 - Examine the entry point to the host and user in action via the Analyse View.
-  - Identify the session entry leader and session user
+  - Identify the session entry leader and session user.
 - Examine the contents of session leading to the process termination(s) via the Session View.
-  - Examine the command execution pattern in the session, which may lead to suspricous activities
+  - Examine the command execution pattern in the session, which may lead to suspricous activities.
 - Examine the process killed during the malicious execution
-  - Identify imment threat to the system from the process killed
-  - Take necessary incident response actions to respawn necessary process
+  - Identify imment threat to the system from the process killed.
+  - Take necessary incident response actions to respawn necessary process.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further destructive behavior, which is commonly associated with this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Reimage the host operating system or restore it to the operational state.
-- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look
-for ransomware preparation and execution activities.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look for ransomware preparation and execution activities.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
 
-----------------------------------
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:start and process.name:"pkill"
-and process.args:"-f"
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:linux and event.type:start and process.name:"pkill" and process.args:"-f"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -110,13 +147,3 @@ and process.args:"-f"
 ** Name: Service Stop
 ** ID: T1489
 ** Reference URL: https://attack.mitre.org/techniques/T1489/
-
-[[high-number-of-process-terminations-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/high-variance-in-rdp-session-duration.asciidoc b/docs/detections/prebuilt-rules/rule-details/high-variance-in-rdp-session-duration.asciidoc
new file mode 100644
index 0000000000..94d1ce4ded
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/high-variance-in-rdp-session-duration.asciidoc
@@ -0,0 +1,92 @@
+[[high-variance-in-rdp-session-duration]]
+=== High Variance in RDP Session Duration
+
+A machine learning job has detected unusually high variance of RDP session duration. Long RDP sessions can be used to evade detection mechanisms via session persistence, and might be used to perform tasks such as lateral movement, that might require uninterrupted access to a compromised machine.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-12h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/lmd
+* https://www.elastic.co/blog/detecting-lateral-movement-activity-a-new-kibana-integration
+* https://www.elastic.co/blog/remote-desktop-protocol-connections-elastic-security
+
+*Tags*: 
+
+* Use Case: Lateral Movement Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Lateral Movement Detection integration assets to be installed, as well as file and Windows RDP process events collected by the Elastic Defend integration.  
+
+
+*Lateral Movement Detection Setup*
+
+The Lateral Movement Detection integration detects lateral movement activity by identifying abnormalities in file and Windows RDP events. Anomalies are detected using Elastic's Anomaly Detection feature.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Lateral Movement Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows RDP process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Lateral Movement Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Lateral Movement Detection and select the integration to see more details about it.
+- Under Settings, click Install Lateral Movement Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Lateral Movement Detection, you'll need to enable the corresponding Anomaly Detection jobs.
+- Before enabling the Anomaly Detection jobs, confirm that the Pivot Transform asset is installed and actively gathering data in the destination index `ml-rdp-lmd`.
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your transformed RDP process data i.e.`ml-rdp-lmd`.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/lmd/kibana/ml_module/lmd-ml.json[this] configuration file, you will see a card for Lateral Movement Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/host-files-system-changes-via-windows-subsystem-for-linux.asciidoc b/docs/detections/prebuilt-rules/rule-details/host-files-system-changes-via-windows-subsystem-for-linux.asciidoc
new file mode 100644
index 0000000000..3abab785c9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/host-files-system-changes-via-windows-subsystem-for-linux.asciidoc
@@ -0,0 +1,71 @@
+[[host-files-system-changes-via-windows-subsystem-for-linux]]
+=== Host Files System Changes via Windows Subsystem for Linux
+
+Detects files creation and modification on the host system from the the Windows Subsystem for Linux. Adversaries may enable and use WSL for Linux to avoid detection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/microsoft/WSL
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by process.entity_id with maxspan=5m
+ [process where host.os.type == "windows" and event.type == "start" and
+  process.name : "dllhost.exe" and 
+   /* Plan9FileSystem CLSID - WSL Host File System Worker */
+  process.command_line : "*{DFB65C4C-B34F-435D-AFE9-A86218684AA8}*"]
+ [file where host.os.type == "windows" and process.name : "dllhost.exe" and not file.path : "?:\\Users\\*\\Downloads\\*"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indirect Command Execution
+** ID: T1202
+** Reference URL: https://attack.mitre.org/techniques/T1202/
diff --git a/docs/detections/prebuilt-rules/rule-details/hosts-file-modified.asciidoc b/docs/detections/prebuilt-rules/rule-details/hosts-file-modified.asciidoc
index f75ff6d02b..5034791038 100644
--- a/docs/detections/prebuilt-rules/rule-details/hosts-file-modified.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/hosts-file-modified.asciidoc
@@ -5,7 +5,7 @@ The hosts file on endpoints is used to control manual IP address to hostname res
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * winlogbeat-*
@@ -16,163 +16,134 @@ The hosts file on endpoints is used to control manual IP address to hostname res
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/beats/auditbeat/current/auditbeat-reference-yml.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* Windows
-* macOS
-* Threat Detection
-* Impact
-* Investigation Guide
-
-*Version*: 102 (<<hosts-file-modified-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: Windows
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Hosts File Modified
+*Triage and analysis*
+
 
-Operating systems use the hosts file to map a connection between an IP address and domain names before going to domain
-name servers. Attackers can abuse this mechanism to route traffic to malicious infrastructure or disrupt security that
-depends on server communications. For example, Russian threat actors modified this file on a domain controller to
-redirect Duo MFA calls to localhost instead of the Duo server, which prevented the MFA service from contacting its
-server to validate MFA login. This effectively disabled MFA for active domain accounts because the default policy of Duo
-for Windows is to "Fail open" if the MFA server is unreachable. This can happen in any MFA implementation and is not
-exclusive to Duo. Find more details in this [CISA Alert](https://www.cisa.gov/uscert/ncas/alerts/aa22-074a).
 
-This rule identifies modifications in the hosts file across multiple operating systems using process creation events for
-Linux and file events in Windows and macOS.
+*Investigating Hosts File Modified*
+
+
+Operating systems use the hosts file to map a connection between an IP address and domain names before going to domain name servers. Attackers can abuse this mechanism to route traffic to malicious infrastructure or disrupt security that depends on server communications. For example, Russian threat actors modified this file on a domain controller to redirect Duo MFA calls to localhost instead of the Duo server, which prevented the MFA service from contacting its server to validate MFA login. This effectively disabled MFA for active domain accounts because the default policy of Duo for Windows is to "Fail open" if the MFA server is unreachable. This can happen in any MFA implementation and is not exclusive to Duo. Find more details in this https://www.cisa.gov/uscert/ncas/alerts/aa22-074a[CISA Alert].
+
+This rule identifies modifications in the hosts file across multiple operating systems using process creation events for Linux and file events in Windows and macOS.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the specifics of the involved assets, such as role, criticality, and associated users.
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Examine the changes to the hosts file by comparing it against file backups, volume shadow copies, and other restoration
-mechanisms.
+- Examine the changes to the hosts file by comparing it against file backups, volume shadow copies, and other restoration mechanisms.
+
 
-### False positive analysis
+*False positive analysis*
 
-- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity
-and the configuration was justified.
 
-### Response and remediation
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity and the configuration was justified.
+
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Consider isolating the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Review the privileges of the administrator account that performed the action.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
-==== Rule query
+==== Setup
 
 
-[source,js]
-----------------------------------
-any where /* file events for creation; file change events are not
-captured by some of the included sources for linux and so may
-miss this, which is the purpose of the process + command line args
-logic below */ ( event.category == "file" and event.type in
-("change", "creation") and file.path : ("/private/etc/hosts",
-"/etc/hosts", "?:\\Windows\\System32\\drivers\\etc\\hosts") ) or
-/* process events for change targeting linux only */ (
-event.category == "process" and event.type in ("start") and
-process.name in ("nano", "vim", "vi", "emacs", "echo", "sed") and
-process.args : ("/etc/hosts") )
-----------------------------------
 
-==== Threat mapping
+*Setup*
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Impact
-** ID: TA0040
-** Reference URL: https://attack.mitre.org/tactics/TA0040/
-* Technique:
-** Name: Data Manipulation
-** ID: T1565
-** Reference URL: https://attack.mitre.org/techniques/T1565/
-
-[[hosts-file-modified-history]]
-==== Rule version history
+For Windows systems using Auditbeat, this rule requires adding `C:/Windows/System32/drivers/etc` as an additional path in the 'file_integrity' module of auditbeat.yml.
 
-Version 102 (8.6.0 release)::
-* Formatting only
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
-Version 101 (8.5.0 release)::
-* Formatting only
 
-Version 11 (8.4.0 release)::
-* Formatting only
-
-Version 9 (8.3.0 release)::
-* Formatting only
+==== Rule query
 
-Version 8 (8.2.0 release)::
-* Formatting only
 
-Version 6 (7.16.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-file where event.type in ("change", "creation") and file.path :
-("/private/etc/hosts", "/etc/hosts",
-"?:\\Windows\\System32\\drivers\\etc\\hosts")
-----------------------------------
+any where
+
+  /* file events for creation; file change events are not captured by some of the included sources for linux and so may
+     miss this, which is the purpose of the process + command line args logic below */
+  (
+   event.category == "file" and event.type in ("change", "creation") and
+     file.path : ("/private/etc/hosts", "/etc/hosts", "?:\\Windows\\System32\\drivers\\etc\\hosts") and 
+     not process.name in ("dockerd", "rootlesskit", "podman", "crio")
+  )
+  or
+
+  /* process events for change targeting linux only */
+  (
+   event.category == "process" and event.type in ("start") and
+     process.name in ("nano", "vim", "vi", "emacs", "echo", "sed") and
+     process.args : ("/etc/hosts") and 
+     not process.parent.name in ("dhclient-script", "google_set_hostname")
+  )
 
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and event.type:(change or creation) and
-file.path:("/private/etc/hosts" or "/etc/hosts" or
-"C:\Windows\System32\drivers\etc\hosts")
 ----------------------------------
 
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
+*Framework*: MITRE ATT&CK^TM^
 
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Data Manipulation
+** ID: T1565
+** Reference URL: https://attack.mitre.org/techniques/T1565/
+* Sub-technique:
+** Name: Stored Data Manipulation
+** ID: T1565.001
+** Reference URL: https://attack.mitre.org/techniques/T1565/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/hping-process-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/hping-process-activity.asciidoc
index 4eb7448043..e0e9269c4b 100644
--- a/docs/detections/prebuilt-rules/rule-details/hping-process-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/hping-process-activity.asciidoc
@@ -3,108 +3,118 @@
 
 Hping ran on a Linux host. Hping is a FOSS command-line packet analyzer and has the ability to construct network packets for a wide variety of network security testing applications, including scanning and firewall auditing.
 
-*Rule type*: query
+*Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
 
-*Severity*: high
+*Severity*: medium
 
-*Risk score*: 73
+*Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://en.wikipedia.org/wiki/Hping
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Discovery
 
-*Version*: 100 (<<hping-process-activity-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.6.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
 
-Normal use of hping is uncommon apart from security testing and research. Use by non-security engineers is very uncommon.
 
-==== Rule query
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:(hping or hping2 or hping3)
-----------------------------------
+*Elastic Defend Integration Setup*
 
-==== Threat mapping
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Discovery
-** ID: TA0007
-** Reference URL: https://attack.mitre.org/tactics/TA0007/
-* Technique:
-** Name: System Information Discovery
-** ID: T1082
-** Reference URL: https://attack.mitre.org/techniques/T1082/
+*Prerequisite Requirements:*
 
-[[hping-process-activity-history]]
-==== Rule version history
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 9 (8.4.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
 
-Version 8 (8.3.0 release)::
-* Formatting only
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Version 7 (7.12.0 release)::
-* Formatting only
 
-Version 6 (7.11.2 release)::
-* Formatting only
+*Auditbeat Setup*
 
-Version 5 (7.10.0 release)::
-* Formatting only
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
 
-Version 4 (7.9.1 release)::
-* Formatting only
 
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:(hping or hping2 or hping3) and event.action:executed
-----------------------------------
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
+
 
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-process.name: (hping3 or hping2 or hping) and event.action:executed
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name in ("hping", "hping2", "hping3")
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/iis-http-logging-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/iis-http-logging-disabled.asciidoc
index 575372fb7e..02488bf66c 100644
--- a/docs/detections/prebuilt-rules/rule-details/iis-http-logging-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/iis-http-logging-disabled.asciidoc
@@ -5,126 +5,130 @@ Identifies when Internet Information Services (IIS) HTTP Logging is disabled on
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 33
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<iis-http-logging-disabled-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating IIS HTTP Logging Disabled*
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name : "appcmd.exe"
-or process.pe.original_file_name == "appcmd.exe") and process.args :
-"/dontLog*:*True" and not process.parent.name : "iissetup.exe"
-----------------------------------
 
-==== Threat mapping
+IIS (Internet Information Services) is a Microsoft web server software used to host websites and web applications on Windows. It provides features for serving dynamic and static content, and can be managed through a graphical interface or command-line tools.
 
-*Framework*: MITRE ATT&CK^TM^
+IIS logging is a data source that can be used for security monitoring, forensics, and incident response. It contains mainly information related to requests done to the web server, and can be used to spot malicious activities like webshells. Adversaries can tamper, clear, and delete this data to evade detection, cover their tracks, and slow down incident response.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Impair Defenses
-** ID: T1562
-** Reference URL: https://attack.mitre.org/techniques/T1562/
+This rule monitors commands that disable IIS logging.
 
-[[iis-http-logging-disabled-history]]
-==== Rule version history
 
-Version 102 (8.6.0 release)::
-* Formatting only
+*Possible investigation steps*
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "appcmd.exe" or process.pe.original_file_name ==
-"appcmd.exe") and process.args : "/dontLog*:*True" and not
-process.parent.name : "iissetup.exe"
-----------------------------------
 
-Version 9 (8.4.0 release)::
-* Formatting only
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - Verify if any other anti-forensics behaviors were observed.
+- Verify whether the logs stored in the `C:\inetpub\logs\logfiles\w3svc1` directory were deleted after this action.
+- Check if this operation is done under change management and approved according to the organization's policy.
 
-Version 7 (8.2.0 release)::
-* Formatting only
 
-Version 6 (7.16.0 release)::
-* Formatting only
+*False positive analysis*
 
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-(process.name:appcmd.exe or process.pe.original_file_name:appcmd.exe)
-and process.args:/dontLog\:\"True\" and not
-process.parent.name:iissetup.exe
-----------------------------------
 
-Version 4 (7.12.0 release)::
-* Formatting only
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Re-enable affected logging components, services, and security monitoring.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
 
-Version 3 (7.11.2 release)::
-* Formatting only
 
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.category:process and event.type:(start or process_started) and
-(process.name:appcmd.exe or process.pe.original_file_name:appcmd.exe
-or winlog.event_data.OriginalFileName:appcmd.exe) and
-process.args:/dontLog\:\"True\" and not
-process.parent.name:iissetup.exe
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "appcmd.exe" or ?process.pe.original_file_name == "appcmd.exe") and
+  process.args : "/dontLog*:*True" and
+  not process.parent.name : "iissetup.exe"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable Windows Event Logging
+** ID: T1562.002
+** Reference URL: https://attack.mitre.org/techniques/T1562/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/image-file-execution-options-injection.asciidoc b/docs/detections/prebuilt-rules/rule-details/image-file-execution-options-injection.asciidoc
index 9061b6faa5..163a2cc976 100644
--- a/docs/detections/prebuilt-rules/rule-details/image-file-execution-options-injection.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/image-file-execution-options-injection.asciidoc
@@ -5,62 +5,66 @@ The Debugger and SilentProcessExit registry keys can allow an adversary to inter
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://oddvar.moe/2018/04/10/persistence-using-globalflags-in-image-file-execution-options-hidden-from-autoruns-exe/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 100 (<<image-file-execution-options-injection-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where length(registry.data.strings) > 0 and registry.path :
-("HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Image File
-Execution Options\\*.exe\\Debugger",
-"HKLM\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows
-NT\\CurrentVersion\\Image File Execution Options\\*\\Debugger",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\SilentProcessExit\\*\\MonitorProcess",
-"HKLM\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows
-NT\\CurrentVersion\\SilentProcessExit\\*\\MonitorProcess") and /*
-add FPs here */ not registry.data.strings regex~ ("""C:\\Program
-Files( \(x86\))?\\ThinKiosk\\thinkiosk\.exe""",
-""".*\\PSAppDeployToolkit\\.*""")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and length(registry.data.strings) > 0 and
+  registry.path : (
+    "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Image File Execution Options\\*.exe\\Debugger",
+    "HKLM\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows NT\\CurrentVersion\\Image File Execution Options\\*\\Debugger",
+    "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\SilentProcessExit\\*\\MonitorProcess",
+    "HKLM\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows NT\\CurrentVersion\\SilentProcessExit\\*\\MonitorProcess",
+    "\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Image File Execution Options\\*.exe\\Debugger",
+    "\\REGISTRY\\MACHINE\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows NT\\CurrentVersion\\Image File Execution Options\\*\\Debugger",
+    "\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\SilentProcessExit\\*\\MonitorProcess",
+    "\\REGISTRY\\MACHINE\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows NT\\CurrentVersion\\SilentProcessExit\\*\\MonitorProcess"
+  ) and
+    /* add FPs here */
+  not registry.data.strings regex~ ("""C:\\Program Files( \(x86\))?\\ThinKiosk\\thinkiosk\.exe""", """.*\\PSAppDeployToolkit\\.*""")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,56 +76,15 @@ Files( \(x86\))?\\ThinKiosk\\thinkiosk\.exe""",
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[image-file-execution-options-injection-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where length(registry.data.strings) > 0 and registry.path :
-("HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Image File
-Execution Options\\*.exe\\Debugger",
-"HKLM\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows
-NT\\CurrentVersion\\Image File Execution Options\\*\\Debugger",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\SilentProcessExit\\*\\MonitorProcess",
-"HKLM\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows
-NT\\CurrentVersion\\SilentProcessExit\\*\\MonitorProcess") and /*
-add FPs here */ not registry.data.strings regex~ ("""C:\\Program
-Files( \(x86\))?\\ThinKiosk\\thinkiosk\.exe""",
-""".*\\PSAppDeployToolkit\\.*""")
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where length(registry.data.strings) > 0 and registry.path :
-("HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Image File
-Execution Options\\*.exe\\Debugger",
-"HKLM\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows
-NT\\CurrentVersion\\Image File Execution Options\\*\\Debugger",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\SilentProcessExit\\*\\MonitorProcess",
-"HKLM\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows
-NT\\CurrentVersion\\SilentProcessExit\\*\\MonitorProcess") and /*
-add FPs here */ not registry.data.strings : ("C:\\Program
-Files*\\ThinKiosk\\thinkiosk.exe", "*\\PSAppDeployToolkit\\*")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Image File Execution Options Injection
+** ID: T1546.012
+** Reference URL: https://attack.mitre.org/techniques/T1546/012/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/image-loaded-with-invalid-signature.asciidoc b/docs/detections/prebuilt-rules/rule-details/image-loaded-with-invalid-signature.asciidoc
new file mode 100644
index 0000000000..57fe501b3e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/image-loaded-with-invalid-signature.asciidoc
@@ -0,0 +1,70 @@
+[[image-loaded-with-invalid-signature]]
+=== Image Loaded with Invalid Signature
+
+Identifies binaries that are loaded and with an invalid code signature. This may indicate an attempt to masquerade as a signed binary.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+library where host.os.type == "windows" and event.action == "load" and
+  dll.code_signature.status : ("errorUntrustedRoot", "errorBadDigest", "errorUntrustedRoot") and
+  (dll.Ext.relative_file_creation_time <= 500 or dll.Ext.relative_file_name_modify_time <= 500) and
+  not startswith~(dll.name, process.name) and
+  not dll.path : (
+    "?:\\Windows\\System32\\DriverStore\\FileRepository\\*"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/imageload-via-windows-update-auto-update-client.asciidoc b/docs/detections/prebuilt-rules/rule-details/imageload-via-windows-update-auto-update-client.asciidoc
index ed24aacbe8..241b1efef2 100644
--- a/docs/detections/prebuilt-rules/rule-details/imageload-via-windows-update-auto-update-client.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/imageload-via-windows-update-auto-update-client.asciidoc
@@ -5,71 +5,139 @@ Identifies abuse of the Windows Update Auto Update Client (wuauclt.exe) to load
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://dtm.uk/wuauclt/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
-
-*Version*: 102 (<<imageload-via-windows-update-auto-update-client-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating ImageLoad via Windows Update Auto Update Client*
+
+
+The Windows Update Auto Update Client (wuauclt.exe) is the component responsible for managing system updates. However, adversaries may abuse this process to load a malicious DLL and execute malicious code while blending into a legitimate system mechanism. 
+
+This rule identifies potential abuse for code execution by monitoring for specific process arguments ("/RunHandlerComServer" and "/UpdateDeploymentProvider") and common writable paths where the target DLL can be placed (e.g., "C:\Users\*.dll", "C:\ProgramData\*.dll", etc.).
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate any abnormal behavior by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the command line and identify the DLL location.
+- Examine whether the DLL is signed.
+- Retrieve the DLL and determine if it is malicious:
+  - Analyze the file using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate the behavior of child processes, such as network connections, registry or file modifications, and any spawned processes.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and
-(process.pe.original_file_name == "wuauclt.exe" or process.name :
-"wuauclt.exe") and /* necessary windows update client args to load
-a dll */ process.args : "/RunHandlerComServer" and process.args :
-"/UpdateDeploymentProvider" and /* common paths writeable by a
-standard user where the target DLL can be placed */ process.args :
-("C:\\Users\\*.dll", "C:\\ProgramData\\*.dll",
-"C:\\Windows\\Temp\\*.dll", "C:\\Windows\\Tasks\\*.dll")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (?process.pe.original_file_name == "wuauclt.exe" or process.name : "wuauclt.exe") and
+   /* necessary windows update client args to load a dll */
+   process.args : "/RunHandlerComServer" and process.args : "/UpdateDeploymentProvider" and
+   /* common paths writeable by a standard user where the target DLL can be placed */
+   process.args : ("C:\\Users\\*.dll", "C:\\ProgramData\\*.dll", "C:\\Windows\\Temp\\*.dll", "C:\\Windows\\Tasks\\*.dll")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,40 +149,3 @@ standard user where the target DLL can be placed */ process.args :
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[imageload-via-windows-update-auto-update-client-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.pe.original_file_name == "wuauclt.exe" or process.name :
-"wuauclt.exe") and /* necessary windows update client args to load
-a dll */ process.args : "/RunHandlerComServer" and process.args :
-"/UpdateDeploymentProvider" and /* common paths writeable by a
-standard user where the target DLL can be placed */ process.args :
-("C:\\Users\\*.dll", "C:\\ProgramData\\*.dll",
-"C:\\Windows\\Temp\\*.dll", "C:\\Windows\\Tasks\\*.dll")
-----------------------------------
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/inbound-connection-to-an-unsecure-elasticsearch-node.asciidoc b/docs/detections/prebuilt-rules/rule-details/inbound-connection-to-an-unsecure-elasticsearch-node.asciidoc
index b1ef58cc01..0a506630a5 100644
--- a/docs/detections/prebuilt-rules/rule-details/inbound-connection-to-an-unsecure-elasticsearch-node.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/inbound-connection-to-an-unsecure-elasticsearch-node.asciidoc
@@ -5,71 +5,61 @@ Identifies Elasticsearch nodes that do not have Transport Layer Security (TLS),
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
-* filebeat-*
 * packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-security.html
 * https://www.elastic.co/guide/en/beats/packetbeat/current/packetbeat-http-options.html#_send_all_headers
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Network
-* Threat Detection
-* Initial Access
-* Host
-
-*Version*: 100 (<<inbound-connection-to-an-unsecure-elasticsearch-node-history, version history>>)
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Domain: Endpoint
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-If you have front-facing proxies that provide authentication and TLS, this rule would need to be tuned to eliminate the source IP address of your reverse-proxy.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+This rule requires the addition of port `9200` and `send_all_headers` to the `HTTP` protocol configuration in `packetbeat.yml`. See the References section for additional configuration documentation.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:network_traffic AND network.protocol:http AND status:OK
-AND destination.port:9200 AND network.direction:inbound AND NOT
-http.response.headers.content-type:"image/x-icon" AND NOT
-_exists_:http.request.headers.authorization
+[source, js]
 ----------------------------------
+(event.dataset: network_traffic.http OR (event.category: network_traffic AND network.protocol: http)) AND
+    status:OK AND destination.port:9200 AND network.direction:inbound AND NOT http.response.headers.content-type:"image/x-icon" AND NOT
+    _exists_:http.request.headers.authorization
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,33 +71,3 @@ _exists_:http.request.headers.authorization
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[inbound-connection-to-an-unsecure-elasticsearch-node-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network_traffic AND network.protocol:http AND status:OK
-AND destination.port:9200 AND network.direction:inbound AND NOT
-http.response.headers.content-type:"image/x-icon" AND NOT
-_exists_:http.request.headers.authorization
-----------------------------------
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-via-mshta.asciidoc b/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-via-mshta.asciidoc
index 595ef6d6f2..787e629ad0 100644
--- a/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-via-mshta.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-via-mshta.asciidoc
@@ -5,59 +5,60 @@ Identifies the use of Distributed Component Object Model (DCOM) to execute comma
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://codewhitesec.blogspot.com/2018/07/lethalhta.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-
-*Version*: 101 (<<incoming-dcom-lateral-movement-via-mshta-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence with maxspan=1m [process where event.type == "start" and
-process.name : "mshta.exe" and process.args : "-Embedding" ] by
-host.id, process.entity_id [network where event.type == "start" and
-process.name : "mshta.exe" and network.direction : ("incoming",
-"ingress") and network.transport == "tcp" and source.port > 49151
-and destination.port > 49151 and source.ip != "127.0.0.1" and
-source.ip != "::1" ] by host.id, process.entity_id
+[source, js]
 ----------------------------------
+sequence with maxspan=1m
+  [process where host.os.type == "windows" and event.type == "start" and
+     process.name : "mshta.exe" and process.args : "-Embedding"
+  ] by host.id, process.entity_id
+  [network where host.os.type == "windows" and event.type == "start" and process.name : "mshta.exe" and
+     network.direction : ("incoming", "ingress") and network.transport == "tcp" and
+     source.port > 49151 and destination.port > 49151 and source.ip != "127.0.0.1" and source.ip != "::1"
+  ] by host.id, process.entity_id
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -69,8 +70,10 @@ source.ip != "::1" ] by host.id, process.entity_id
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-
+* Sub-technique:
+** Name: Distributed Component Object Model
+** ID: T1021.003
+** Reference URL: https://attack.mitre.org/techniques/T1021/003/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -79,73 +82,7 @@ source.ip != "::1" ] by host.id, process.entity_id
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[incoming-dcom-lateral-movement-via-mshta-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1m [process where event.type in ("start",
-"process_started") and process.name : "mshta.exe" and
-process.args : "-Embedding" ] by host.id, process.entity_id
-[network where event.type == "start" and process.name : "mshta.exe"
-and network.direction : ("incoming", "ingress") and
-network.transport == "tcp" and source.port > 49151 and
-destination.port > 49151 and source.ip != "127.0.0.1" and source.ip !=
-"::1" ] by host.id, process.entity_id
-----------------------------------
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1m [process where event.type in ("start",
-"process_started") and process.name : "mshta.exe" and
-process.args : "-Embedding" ] by host.id, process.entity_id
-[network where event.type == "start" and process.name : "mshta.exe"
-and network.direction : ("incoming", "ingress") and
-network.transport == "tcp" and source.port > 49151 and
-destination.port > 49151 and source.ip != "127.0.0.1" and source.ip !=
-"::1" ] by host.id, process.entity_id
-----------------------------------
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1m [process where event.type in ("start",
-"process_started") and process.name : "mshta.exe" and
-process.args : "-Embedding" ] by host.id, process.entity_id
-[network where event.type == "start" and process.name : "mshta.exe"
-and network.direction : ("incoming", "ingress") and
-network.transport == "tcp" and source.port > 49151 and
-destination.port > 49151 and not source.address in ("127.0.0.1",
-"::1") ] by host.id, process.entity_id
-----------------------------------
-
-Version 4 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1m [process where event.type in ("start",
-"process_started") and process.name : "mshta.exe" and
-process.args : "-Embedding" ] by host.id, process.entity_id
-[network where event.type == "start" and process.name : "mshta.exe"
-and network.direction == "incoming" and network.transport ==
-"tcp" and source.port > 49151 and destination.port > 49151 and
-not source.address in ("127.0.0.1", "::1") ] by host.id,
-process.entity_id
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Mshta
+** ID: T1218.005
+** Reference URL: https://attack.mitre.org/techniques/T1218/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-with-mmc.asciidoc b/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-with-mmc.asciidoc
index 2d4d615152..5dab99397b 100644
--- a/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-with-mmc.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-with-mmc.asciidoc
@@ -5,59 +5,60 @@ Identifies the use of Distributed Component Object Model (DCOM) to run commands
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://enigma0x3.net/2017/01/05/lateral-movement-using-the-mmc20-application-com-object/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-
-*Version*: 101 (<<incoming-dcom-lateral-movement-with-mmc-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=1m [network where event.type ==
-"start" and process.name : "mmc.exe" and source.port >= 49152 and
-destination.port >= 49152 and source.ip != "127.0.0.1" and source.ip
-!= "::1" and network.direction : ("incoming", "ingress") and
-network.transport == "tcp" ] by process.entity_id [process where
-event.type == "start" and process.parent.name : "mmc.exe" ] by
-process.parent.entity_id
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=1m
+ [network where host.os.type == "windows" and event.type == "start" and process.name : "mmc.exe" and source.port >= 49152 and
+ destination.port >= 49152 and source.ip != "127.0.0.1" and source.ip != "::1" and
+  network.direction : ("incoming", "ingress") and network.transport == "tcp"
+ ] by process.entity_id
+ [process where host.os.type == "windows" and event.type == "start" and process.parent.name : "mmc.exe"
+ ] by process.parent.entity_id
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -69,55 +70,19 @@ process.parent.entity_id
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[incoming-dcom-lateral-movement-with-mmc-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=1m [network where event.type ==
-"start" and process.name : "mmc.exe" and source.port >= 49152 and
-destination.port >= 49152 and source.ip != "127.0.0.1" and source.ip
-!= "::1" and network.direction : ("incoming", "ingress") and
-network.transport == "tcp" ] by process.entity_id [process where
-event.type in ("start", "process_started") and process.parent.name :
-"mmc.exe" ] by process.parent.entity_id
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=1m [network where event.type ==
-"start" and process.name : "mmc.exe" and source.port >= 49152 and
-destination.port >= 49152 and source.address not in ("127.0.0.1",
-"::1") and network.direction : ("incoming", "ingress") and
-network.transport == "tcp" ] by process.entity_id [process where
-event.type in ("start", "process_started") and process.parent.name :
-"mmc.exe" ] by process.parent.entity_id
-----------------------------------
-
-Version 4 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=1m [network where event.type ==
-"start" and process.name : "mmc.exe" and source.port >= 49152 and
-destination.port >= 49152 and source.address not in ("127.0.0.1",
-"::1") and network.direction == "incoming" and network.transport ==
-"tcp" ] by process.entity_id [process where event.type in ("start",
-"process_started") and process.parent.name : "mmc.exe" ] by
-process.parent.entity_id
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Distributed Component Object Model
+** ID: T1021.003
+** Reference URL: https://attack.mitre.org/techniques/T1021/003/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: MMC
+** ID: T1218.014
+** Reference URL: https://attack.mitre.org/techniques/T1218/014/
diff --git a/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-with-shellbrowserwindow-or-shellwindows.asciidoc b/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-with-shellbrowserwindow-or-shellwindows.asciidoc
index 69e9a4ddc6..1199d63339 100644
--- a/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-with-shellbrowserwindow-or-shellwindows.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/incoming-dcom-lateral-movement-with-shellbrowserwindow-or-shellwindows.asciidoc
@@ -5,59 +5,60 @@ Identifies use of Distributed Component Object Model (DCOM) to run commands from
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://enigma0x3.net/2017/01/23/lateral-movement-via-dcom-round-2/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-
-*Version*: 101 (<<incoming-dcom-lateral-movement-with-shellbrowserwindow-or-shellwindows-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=5s [network where event.type ==
-"start" and process.name : "explorer.exe" and network.direction :
-("incoming", "ingress") and network.transport == "tcp" and
-source.port > 49151 and destination.port > 49151 and source.ip !=
-"127.0.0.1" and source.ip != "::1" ] by process.entity_id [process
-where event.type == "start" and process.parent.name : "explorer.exe"
-] by process.parent.entity_id
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=5s
+ [network where host.os.type == "windows" and event.type == "start" and process.name : "explorer.exe" and
+  network.direction : ("incoming", "ingress") and network.transport == "tcp" and
+  source.port > 49151 and destination.port > 49151 and source.ip != "127.0.0.1" and source.ip != "::1"
+ ] by process.entity_id
+ [process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : "explorer.exe"
+ ] by process.parent.entity_id
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -69,55 +70,7 @@ where event.type == "start" and process.parent.name : "explorer.exe"
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[incoming-dcom-lateral-movement-with-shellbrowserwindow-or-shellwindows-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [network where event.type ==
-"start" and process.name : "explorer.exe" and network.direction :
-("incoming", "ingress") and network.transport == "tcp" and
-source.port > 49151 and destination.port > 49151 and source.ip !=
-"127.0.0.1" and source.ip != "::1" ] by process.entity_id [process
-where event.type in ("start", "process_started") and
-process.parent.name : "explorer.exe" ] by process.parent.entity_id
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [network where event.type ==
-"start" and process.name : "explorer.exe" and network.direction :
-("incoming", "ingress") and network.transport == "tcp" and
-source.port > 49151 and destination.port > 49151 and not
-source.address in ("127.0.0.1", "::1") ] by process.entity_id
-[process where event.type in ("start", "process_started") and
-process.parent.name : "explorer.exe" ] by process.parent.entity_id
-----------------------------------
-
-Version 4 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [network where event.type ==
-"start" and process.name : "explorer.exe" and network.direction ==
-"incoming" and network.transport == "tcp" and source.port > 49151
-and destination.port > 49151 and not source.address in ("127.0.0.1",
-"::1") ] by process.entity_id [process where event.type in ("start",
-"process_started") and process.parent.name : "explorer.exe" ] by
-process.parent.entity_id
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Distributed Component Object Model
+** ID: T1021.003
+** Reference URL: https://attack.mitre.org/techniques/T1021/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/incoming-execution-via-powershell-remoting.asciidoc b/docs/detections/prebuilt-rules/rule-details/incoming-execution-via-powershell-remoting.asciidoc
index 72c778f96c..d9e70cf37a 100644
--- a/docs/detections/prebuilt-rules/rule-details/incoming-execution-via-powershell-remoting.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/incoming-execution-via-powershell-remoting.asciidoc
@@ -5,62 +5,58 @@ Identifies remote execution via Windows PowerShell remoting. Windows PowerShell
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/scripting/learn/remoting/running-remote-commands?view=powershell-7.1
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-
-*Version*: 100 (<<incoming-execution-via-powershell-remoting-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-PowerShell remoting is a dual-use protocol that can be used for benign or malicious activity. It's important to baseline your environment to determine the amount of noise to expect from this tool.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan = 30s [network where
-network.direction : ("incoming", "ingress") and destination.port in
-(5985, 5986) and network.protocol == "http" and source.ip !=
-"127.0.0.1" and source.ip != "::1" ] [process where event.type
-== "start" and process.parent.name : "wsmprovhost.exe" and not
-process.name : "conhost.exe"]
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan = 30s
+   [network where host.os.type == "windows" and network.direction : ("incoming", "ingress") and destination.port in (5985, 5986) and
+    network.protocol == "http" and source.ip != "127.0.0.1" and source.ip != "::1"]
+   [process where host.os.type == "windows" and 
+    event.type == "start" and process.parent.name : "wsmprovhost.exe" and not process.executable : "?:\\Windows\\System32\\conhost.exe"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,45 +68,19 @@ process.name : "conhost.exe"]
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[incoming-execution-via-powershell-remoting-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan = 30s [network where
-network.direction : ("incoming", "ingress") and destination.port in
-(5985, 5986) and network.protocol == "http" and source.address !=
-"127.0.0.1" and source.address != "::1" ] [process where
-event.type == "start" and process.parent.name : "wsmprovhost.exe" and
-not process.name : "conhost.exe"]
-----------------------------------
-
-Version 3 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan = 30s [network where
-network.direction == "incoming" and destination.port in (5985, 5986)
-and network.protocol == "http" and source.address != "127.0.0.1"
-and source.address != "::1" ] [process where event.type ==
-"start" and process.parent.name : "wsmprovhost.exe" and not
-process.name : "conhost.exe"]
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Windows Remote Management
+** ID: T1021.006
+** Reference URL: https://attack.mitre.org/techniques/T1021/006/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/incoming-execution-via-winrm-remote-shell.asciidoc b/docs/detections/prebuilt-rules/rule-details/incoming-execution-via-winrm-remote-shell.asciidoc
index 97c0e57315..f04e1c0c6d 100644
--- a/docs/detections/prebuilt-rules/rule-details/incoming-execution-via-winrm-remote-shell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/incoming-execution-via-winrm-remote-shell.asciidoc
@@ -5,58 +5,55 @@ Identifies remote execution via Windows Remote Management (WinRM) remote shell o
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
+*Tags*: 
 
-*Version*: 100 (<<incoming-execution-via-winrm-remote-shell-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-WinRM is a dual-use protocol that can be used for benign or malicious activity. It's important to baseline your environment to determine the amount of noise to expect from this tool.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=30s [network where process.pid ==
-4 and network.direction : ("incoming", "ingress") and
-destination.port in (5985, 5986) and network.protocol == "http" and
-source.ip != "127.0.0.1" and source.ip != "::1" ] [process where
-event.type == "start" and process.parent.name : "winrshost.exe" and
-not process.name : "conhost.exe"]
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=30s
+   [network where host.os.type == "windows" and process.pid == 4 and network.direction : ("incoming", "ingress") and
+    destination.port in (5985, 5986) and network.protocol == "http" and source.ip != "127.0.0.1" and source.ip != "::1"]
+   [process where host.os.type == "windows" and 
+    event.type == "start" and process.parent.name : "winrshost.exe" and not process.executable : "?:\\Windows\\System32\\conhost.exe"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -68,42 +65,7 @@ not process.name : "conhost.exe"]
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[incoming-execution-via-winrm-remote-shell-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=30s [network where process.pid ==
-4 and network.direction : ("incoming", "ingress") and
-destination.port in (5985, 5986) and network.protocol == "http" and
-not source.address in ("::1", "127.0.0.1") ] [process where
-event.type == "start" and process.parent.name : "winrshost.exe" and
-not process.name : "conhost.exe"]
-----------------------------------
-
-Version 3 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=30s [network where process.pid ==
-4 and network.direction == "incoming" and destination.port in
-(5985, 5986) and network.protocol == "http" and not source.address in
-("::1", "127.0.0.1") ] [process where event.type == "start" and
-process.parent.name : "winrshost.exe" and not process.name :
-"conhost.exe"]
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Windows Remote Management
+** ID: T1021.006
+** Reference URL: https://attack.mitre.org/techniques/T1021/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/indirect-command-execution-via-forfiles-pcalua.asciidoc b/docs/detections/prebuilt-rules/rule-details/indirect-command-execution-via-forfiles-pcalua.asciidoc
new file mode 100644
index 0000000000..99b4de7d66
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/indirect-command-execution-via-forfiles-pcalua.asciidoc
@@ -0,0 +1,66 @@
+[[indirect-command-execution-via-forfiles-pcalua]]
+=== Indirect Command Execution via Forfiles/Pcalua
+
+Identifies indirect command execution via Program Compatibility Assistant (pcalua.exe) or forfiles.exe.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* logs-system.security*
+* winlogbeat-*
+* logs-windows.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Rule Type: BBR
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : ("pcalua.exe", "forfiles.exe")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indirect Command Execution
+** ID: T1202
+** Reference URL: https://attack.mitre.org/techniques/T1202/
diff --git a/docs/detections/prebuilt-rules/rule-details/ingress-transfer-via-windows-bits.asciidoc b/docs/detections/prebuilt-rules/rule-details/ingress-transfer-via-windows-bits.asciidoc
new file mode 100644
index 0000000000..c7401a0ad1
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/ingress-transfer-via-windows-bits.asciidoc
@@ -0,0 +1,170 @@
+[[ingress-transfer-via-windows-bits]]
+=== Ingress Transfer via Windows BITS
+
+Identifies downloads of executable and archive files via the Windows Background Intelligent Transfer Service (BITS). Adversaries could leverage Windows BITS transfer jobs to download remote payloads.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://attack.mitre.org/techniques/T1197/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Ingress Transfer via Windows BITS*
+
+
+Windows Background Intelligent Transfer Service (BITS) is a technology that allows the transfer of files between a client and a server, which makes it a dual-use mechanism, being used by both legitimate apps and attackers. When malicious applications create BITS jobs, files are downloaded or uploaded in the context of the service host process, which can bypass security protections, and it helps to obscure which application requested the transfer.
+
+This rule identifies such abuse by monitoring for file renaming events involving "svchost.exe" and "BIT*.tmp" on Windows systems.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Gain context into the BITS transfer.
+  - Try to determine the process that initiated the BITS transfer.
+    - Search `bitsadmin.exe` processes and examine their command lines.
+    - Look for unusual processes loading `Bitsproxy.dll` and other BITS-related DLLs.
+  - Try to determine the origin of the file.
+    - Inspect network connections initiated by `svchost.exe`.
+    - Inspect `Microsoft-Windows-Bits-Client/Operational` Windows logs, specifically the event ID 59, for unusual events.
+      - Velociraptor can be used to extract these entries using the https://docs.velociraptor.app/exchange/artifacts/pages/bitsadmin/[bitsadmin artifact].
+    - Check the reputation of the remote server involved in the BITS transfer, such as its IP address or domain, using threat intelligence platforms or online reputation services.
+    - Check if the domain is newly registered or unexpected.
+    - Use the identified domain as an indicator of compromise (IoCs) to scope other compromised hosts in the environment.
+  - https://github.com/fireeye/BitsParser[BitsParser] can be used to parse BITS database files to extract BITS job information.
+- Examine the details of the dropped file, and whether it was executed.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the involved executables using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+
+*False positive analysis*
+
+
+- Known false positives for the rule include legitimate software and system updates that use BITS for downloading files.
+
+
+*Related Rules*
+
+
+- Persistence via BITS Job Notify Cmdline - c3b915e0-22f3-4bf7-991d-b643513c722f
+- Unsigned BITS Service Client Process - 9a3884d0-282d-45ea-86ce-b9c81100f026
+- Bitsadmin Activity - 8eec4df1-4b4b-4502-b6c3-c788714604c9
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+  - If malicious activity is confirmed, perform a broader investigation to identify the scope of the compromise and determine the appropriate remediation steps.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Restore the affected system to its operational state by applying any necessary patches, updates, or configuration changes.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.action == "rename" and
+  process.name : "svchost.exe" and file.Ext.original.name : "BIT*.tmp" and 
+  (file.extension : ("exe", "zip", "rar", "bat", "dll", "ps1", "vbs", "wsh", "js", "vbe", "pif", "scr", "cmd", "cpl") or
+   file.Ext.header_bytes : "4d5a*") and 
+ 
+  /* noisy paths, for hunting purposes you can use the same query without the following exclusions */
+  not file.path : ("?:\\Program Files\\*", "?:\\Program Files (x86)\\*", "?:\\Windows\\*", "?:\\ProgramData\\*\\*") and 
+ 
+  /* lot of third party SW use BITS to download executables with a long file name */
+  not length(file.name) > 30 and
+  not file.path : (
+        "?:\\Users\\*\\AppData\\Local\\Temp*\\wct*.tmp",
+        "?:\\Users\\*\\AppData\\Local\\Adobe\\ARM\\*\\RdrServicesUpdater*.exe",
+        "?:\\Users\\*\\AppData\\Local\\Adobe\\ARM\\*\\AcroServicesUpdater2_x64.exe",
+        "?:\\Users\\*\\AppData\\Local\\Docker Desktop Installer\\update-*.exe"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Ingress Tool Transfer
+** ID: T1105
+** Reference URL: https://attack.mitre.org/techniques/T1105/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: BITS Jobs
+** ID: T1197
+** Reference URL: https://attack.mitre.org/techniques/T1197/
diff --git a/docs/detections/prebuilt-rules/rule-details/installation-of-custom-shim-databases.asciidoc b/docs/detections/prebuilt-rules/rule-details/installation-of-custom-shim-databases.asciidoc
index 03979469f5..f1f1fb6810 100644
--- a/docs/detections/prebuilt-rules/rule-details/installation-of-custom-shim-databases.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/installation-of-custom-shim-databases.asciidoc
@@ -5,54 +5,57 @@ Identifies the installation of custom Application Compatibility Shim databases.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 101 (<<installation-of-custom-shim-databases-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id with maxspan = 5m [process where
-event.type == "start" and not (process.name : "sdbinst.exe" and
-process.parent.name : "msiexec.exe")] [registry where event.type in
-("creation", "change") and registry.path :
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\AppCompatFlags\\Custom\\*.sdb"]
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type in ("creation", "change") and
+    registry.path : "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\AppCompatFlags\\Custom\\*.sdb" and 
+    not process.executable : 
+                       ("?:\\Program Files (x86)\\DesktopCentral_Agent\\swrepository\\1\\swuploads\\SAP-SLC\\SAPSetupSLC02_14-80001954\\Setup\\NwSapSetup.exe", 
+                        "?:\\$WINDOWS.~BT\\Sources\\SetupPlatform.exe", 
+                         "?:\\Program Files (x86)\\SAP\\SAPsetup\\setup\\NwSapSetup.exe", 
+                         "?:\\Program Files (x86)\\SAP\\SapSetup\\OnRebootSvc\\NWSAPSetupOnRebootInstSvc.exe", 
+                         "?:\\Program Files (x86)\\Kaspersky Lab\\Kaspersky Security for Windows Server\\kavfs.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,39 +67,7 @@ NT\\CurrentVersion\\AppCompatFlags\\Custom\\*.sdb"]
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[installation-of-custom-shim-databases-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan = 5m [process where
-event.type in ("start", "process_started") and not (process.name :
-"sdbinst.exe" and process.parent.name : "msiexec.exe")] [registry
-where event.type in ("creation", "change") and registry.path :
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\AppCompatFlags\\Custom\\*.sdb"]
-----------------------------------
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan=5m [process where
-event.type in ("start", "process_started") and not (process.name
-: "sdbinst.exe" and process.parent.name : "msiexec.exe")] [registry
-where event.type in ("creation", "change") and
-wildcard(registry.path, "HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\AppCompatFlags\\Custom\\*.sdb")]
-----------------------------------
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Application Shimming
+** ID: T1546.011
+** Reference URL: https://attack.mitre.org/techniques/T1546/011/
diff --git a/docs/detections/prebuilt-rules/rule-details/installation-of-security-support-provider.asciidoc b/docs/detections/prebuilt-rules/rule-details/installation-of-security-support-provider.asciidoc
index 5699702e53..56de27f3e2 100644
--- a/docs/detections/prebuilt-rules/rule-details/installation-of-security-support-provider.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/installation-of-security-support-provider.asciidoc
@@ -5,63 +5,74 @@ Identifies registry modifications related to the Windows Security Support Provid
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 100 (<<installation-of-security-support-provider-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.path :
-("HKLM\\SYSTEM\\*ControlSet*\\Control\\Lsa\\Security Packages*",
-"HKLM\\SYSTEM\\*ControlSet*\\Control\\Lsa\\OSConfig\\Security
-Packages*") and not process.executable :
-("C:\\Windows\\System32\\msiexec.exe",
-"C:\\Windows\\SysWOW64\\msiexec.exe")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and
+   registry.path : (
+      "HKLM\\SYSTEM\\*ControlSet*\\Control\\Lsa\\Security Packages*",
+      "HKLM\\SYSTEM\\*ControlSet*\\Control\\Lsa\\OSConfig\\Security Packages*",
+      "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Control\\Lsa\\Security Packages*",
+      "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Control\\Lsa\\OSConfig\\Security Packages*"
+   ) and
+   not process.executable : ("C:\\Windows\\System32\\msiexec.exe", "C:\\Windows\\SysWOW64\\msiexec.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,45 +84,15 @@ Packages*") and not process.executable :
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[installation-of-security-support-provider-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path :
-("HKLM\\SYSTEM\\*ControlSet*\\Control\\Lsa\\Security Packages*",
-"HKLM\\SYSTEM\\*ControlSet*\\Control\\Lsa\\OSConfig\\Security
-Packages*") and not process.executable :
-("C:\\Windows\\System32\\msiexec.exe",
-"C:\\Windows\\SysWOW64\\msiexec.exe")
-----------------------------------
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path :
-("HKLM\\SYSTEM\\CurrentControlSet\\Control\\Lsa\\Security Packages*",
-"HKLM\\SYSTEM\\CurrentControlSet\\Control\\Lsa\\OSConfig\\Security
-Packages*") and not process.executable :
-("C:\\Windows\\System32\\msiexec.exe",
-"C:\\Windows\\SysWOW64\\msiexec.exe")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Security Support Provider
+** ID: T1547.005
+** Reference URL: https://attack.mitre.org/techniques/T1547/005/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/installutil-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/installutil-activity.asciidoc
new file mode 100644
index 0000000000..60c6d43a52
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/installutil-activity.asciidoc
@@ -0,0 +1,70 @@
+[[installutil-activity]]
+=== InstallUtil Activity
+
+InstallUtil is a command-line utility that allows for installation and uninstallation of resources by executing specific installer components specified in .NET binaries. Adversaries may use InstallUtil to proxy the execution of code through a trusted Windows utility.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* logs-system.security*
+* winlogbeat-*
+* logs-windows.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Rule Type: BBR
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "installutil.exe" and not user.id : "S-1-5-18"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: InstallUtil
+** ID: T1218.004
+** Reference URL: https://attack.mitre.org/techniques/T1218/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/installutil-process-making-network-connections.asciidoc b/docs/detections/prebuilt-rules/rule-details/installutil-process-making-network-connections.asciidoc
index 63cb7c3962..0008e3d80b 100644
--- a/docs/detections/prebuilt-rules/rule-details/installutil-process-making-network-connections.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/installutil-process-making-network-connections.asciidoc
@@ -5,53 +5,55 @@ Identifies InstallUtil.exe making outbound network connections. This may indicat
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 101 (<<installutil-process-making-network-connections-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-/* the benefit of doing this as an eql sequence vs kql is this will
-limit to alerting only on the first network connection */ sequence by
-process.entity_id [process where event.type == "start" and
-process.name : "installutil.exe"] [network where process.name :
-"installutil.exe" and network.direction : ("outgoing", "egress")]
+[source, js]
 ----------------------------------
+/* the benefit of doing this as an eql sequence vs kql is this will limit to alerting only on the first network connection */
 
-==== Threat mapping
+sequence by process.entity_id
+  [process where host.os.type == "windows" and event.type == "start" and process.name : "installutil.exe"]
+  [network where host.os.type == "windows" and process.name : "installutil.exe" and network.direction : ("outgoing", "egress")]
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -63,42 +65,7 @@ process.name : "installutil.exe"] [network where process.name :
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[installutil-process-making-network-connections-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* the benefit of doing this as an eql sequence vs kql is this will
-limit to alerting only on the first network connection */ sequence by
-process.entity_id [process where event.type in ("start",
-"process_started") and process.name : "installutil.exe"] [network
-where process.name : "installutil.exe" and network.direction :
-("outgoing", "egress")]
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* the benefit of doing this as an eql sequence vs kql is this will
-limit to alerting only on the first network connection */ sequence by
-process.entity_id [process where event.type in ("start",
-"process_started") and process.name : "installutil.exe"] [network
-where process.name : "installutil.exe" and network.direction ==
-"outgoing"]
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: InstallUtil
+** ID: T1218.004
+** Reference URL: https://attack.mitre.org/techniques/T1218/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/interactive-exec-command-launched-against-a-running-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/interactive-exec-command-launched-against-a-running-container.asciidoc
new file mode 100644
index 0000000000..b5eea02c89
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/interactive-exec-command-launched-against-a-running-container.asciidoc
@@ -0,0 +1,79 @@
+[[interactive-exec-command-launched-against-a-running-container]]
+=== Interactive Exec Command Launched Against A Running Container
+
+This rule detects interactive 'exec' events launched against a container using the 'exec' command. Using the 'exec' command in a pod allows a user to establish a temporary shell session and execute any process/command inside the container. This rule specifically targets higher-risk interactive commands that allow real-time interaction with a container's shell. A malicious actor could use this level of access to further compromise the container environment or attempt a container breakout.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://kubernetes.io/docs/tasks/debug/debug-application/debug-running-pod/
+* https://kubernetes.io/docs/tasks/debug/debug-application/get-shell-running-container/
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where container.id : "*" and event.type== "start" and 
+
+/* use of kubectl exec to enter a container */
+process.entry_leader.entry_meta.type : "container" and 
+
+/* process is the inital process run in a container */
+process.entry_leader.same_as_process== true and
+
+/* interactive process */
+process.interactive == true
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Technique:
+** Name: Container Administration Command
+** ID: T1609
+** Reference URL: https://attack.mitre.org/techniques/T1609/
diff --git a/docs/detections/prebuilt-rules/rule-details/interactive-logon-by-an-unusual-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/interactive-logon-by-an-unusual-process.asciidoc
new file mode 100644
index 0000000000..b9b52b18e6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/interactive-logon-by-an-unusual-process.asciidoc
@@ -0,0 +1,98 @@
+[[interactive-logon-by-an-unusual-process]]
+=== Interactive Logon by an Unusual Process
+
+Identifies interactive logon attempt with alternate credentials and by an unusual process. Adversaries may create a new token to escalate privileges and bypass access controls.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-system.*
+* logs-windows.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://attack.mitre.org/techniques/T1134/002/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+Audit event 4624 is needed to trigger this rule.
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+authentication where 
+ host.os.type : "windows" and winlog.event_data.LogonProcessName : "Advapi*" and 
+ winlog.logon.type == "Interactive" and winlog.event_data.SubjectUserSid : ("S-1-5-21*", "S-1-12-*") and 
+ winlog.event_data.TargetUserSid : ("S-1-5-21*", "S-1-12-*")  and process.executable : "C:\\*" and 
+ not startswith~(winlog.event_data.SubjectUserSid, winlog.event_data.TargetUserSid) and 
+ not process.executable : 
+            ("?:\\Windows\\System32\\winlogon.exe", 
+             "?:\\Windows\\System32\\wininit.exe", 
+             "?:\\Program Files\\*.exe", 
+             "?:\\Program Files (x86)\\*.exe", 
+             "?:\\Windows\\SysWOW64\\inetsrv\\w3wp.exe", 
+             "?:\\Windows\\System32\\inetsrv\\w3wp.exe", 
+             "?:\\Windows\\SysWOW64\\msiexec.exe")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Access Token Manipulation
+** ID: T1134
+** Reference URL: https://attack.mitre.org/techniques/T1134/
+* Sub-technique:
+** Name: Create Process with Token
+** ID: T1134.002
+** Reference URL: https://attack.mitre.org/techniques/T1134/002/
+* Sub-technique:
+** Name: Make and Impersonate Token
+** ID: T1134.003
+** Reference URL: https://attack.mitre.org/techniques/T1134/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/interactive-terminal-spawned-via-perl.asciidoc b/docs/detections/prebuilt-rules/rule-details/interactive-terminal-spawned-via-perl.asciidoc
index 6db17dc1d5..9ba96fcaa9 100644
--- a/docs/detections/prebuilt-rules/rule-details/interactive-terminal-spawned-via-perl.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/interactive-terminal-spawned-via-perl.asciidoc
@@ -5,89 +5,112 @@ Identifies when a terminal (tty) is spawned via Perl. Attackers may upgrade a si
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Execution
+*Tags*: 
 
-*Version*: 100 (<<interactive-terminal-spawned-via-perl-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.8.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
 
+==== Setup
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:perl and process.args:("exec \"/bin/sh\";" or "exec
-\"/bin/dash\";" or "exec \"/bin/bash\";")
-----------------------------------
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-* Tactic:
-** Name: Execution
-** ID: TA0002
-** Reference URL: https://attack.mitre.org/tactics/TA0002/
-* Technique:
-** Name: Command and Scripting Interpreter
-** ID: T1059
-** Reference URL: https://attack.mitre.org/techniques/T1059/
 
-[[interactive-terminal-spawned-via-perl-history]]
-==== Rule version history
+*Prerequisite Requirements:*
 
-Version 100 (8.5.0 release)::
-* Formatting only
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 7 (8.4.0 release)::
-* Formatting only
 
-Version 6 (7.12.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
 
-Version 5 (7.11.2 release)::
-* Formatting only
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Version 4 (7.10.0 release)::
-* Formatting only
 
-Version 3 (7.9.1 release)::
-* Formatting only
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
+
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:executed and process.name:perl and process.args:("exec
-\"/bin/sh\";" or "exec \"/bin/dash\";" or "exec \"/bin/bash\";")
+event.category:process and host.os.type:linux and event.type:(start or process_started) and process.name:perl and
+  process.args:("exec \"/bin/sh\";" or "exec \"/bin/dash\";" or "exec \"/bin/bash\";")
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
diff --git a/docs/detections/prebuilt-rules/rule-details/interactive-terminal-spawned-via-python.asciidoc b/docs/detections/prebuilt-rules/rule-details/interactive-terminal-spawned-via-python.asciidoc
index 9f279afdb4..0bbbf2d40f 100644
--- a/docs/detections/prebuilt-rules/rule-details/interactive-terminal-spawned-via-python.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/interactive-terminal-spawned-via-python.asciidoc
@@ -3,118 +3,106 @@
 
 Identifies when a terminal (tty) is spawned via Python. Attackers may upgrade a simple reverse shell to a fully interactive tty after obtaining initial access to a host.
 
-*Rule type*: query
+*Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Execution
+*Tags*: 
 
-*Version*: 100 (<<interactive-terminal-spawned-via-python-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.8.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
 
+==== Setup
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:python* and process.args:("import pty;
-pty.spawn(\"/bin/sh\")" or "import pty;
-pty.spawn(\"/bin/dash\")" or "import pty;
-pty.spawn(\"/bin/bash\")")
-----------------------------------
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+*Setup*
 
-* Tactic:
-** Name: Execution
-** ID: TA0002
-** Reference URL: https://attack.mitre.org/tactics/TA0002/
-* Technique:
-** Name: Command and Scripting Interpreter
-** ID: T1059
-** Reference URL: https://attack.mitre.org/techniques/T1059/
 
-[[interactive-terminal-spawned-via-python-history]]
-==== Rule version history
+This rule requires data coming in from Elastic Defend.
 
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:python* and process.args:("import pty;
-pty.spawn(\"/bin/sh\")" or "import pty;
-pty.spawn(\"/bin/dash\")" or "import pty;
-pty.spawn(\"/bin/bash\")")
-----------------------------------
 
-Version 10 (8.4.0 release)::
-* Formatting only
+*Elastic Defend Integration Setup*
 
-Version 9 (8.3.0 release)::
-* Formatting only
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-Version 7 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:python and process.args:("import pty;
-pty.spawn(\"/bin/sh\")" or "import pty;
-pty.spawn(\"/bin/dash\")" or "import pty;
-pty.spawn(\"/bin/bash\")")
-----------------------------------
 
-Version 6 (7.12.0 release)::
-* Formatting only
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 5 (7.11.2 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
 
-Version 3 (7.9.1 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:executed and process.name:python and
-process.args:("import pty; pty.spawn(\"/bin/sh\")" or "import pty;
-pty.spawn(\"/bin/dash\")" or "import pty; pty.spawn(\"/bin/bash\")")
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
+(
+  (process.parent.name : "python*" and process.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh",
+   "fish") and process.parent.args_count >= 3 and process.parent.args : "*pty.spawn*" and process.parent.args : "-c") or
+  (process.parent.name : "python*" and process.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh",
+   "fish") and process.args : "*sh" and process.args_count == 1 and process.parent.args_count == 1)
+)
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Python
+** ID: T1059.006
+** Reference URL: https://attack.mitre.org/techniques/T1059/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/ipsec-nat-traversal-port-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/ipsec-nat-traversal-port-activity.asciidoc
index aea60f0350..30a799c5bd 100644
--- a/docs/detections/prebuilt-rules/rule-details/ipsec-nat-traversal-port-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/ipsec-nat-traversal-port-activity.asciidoc
@@ -5,56 +5,48 @@ This rule detects events that could be describing IPSEC NAT Traversal traffic. I
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Network
-* Threat Detection
-* Command and Control
-* Host
+*Tags*: 
 
-*Version*: 100 (<<ipsec-nat-traversal-port-activity-history, version history>>)
+* Tactic: Command and Control
+* Domain: Endpoint
+* Use Case: Threat Detection
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Some networks may utilize these protocols but usage that is unfamiliar to local network administrators can be unexpected and suspicious. Because this port is in the ephemeral range, this rule may false under certain conditions, such as when an application server with a public IP address replies to a client which has used a UDP port in the range by coincidence. This is uncommon but such servers can be excluded.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:udp
-and destination.port:4500
+[source, js]
 ----------------------------------
+(event.dataset: network_traffic.flow or (event.category: (network or network_traffic))) and network.transport:udp and destination.port:4500
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -62,45 +54,3 @@ and destination.port:4500
 ** Name: Command and Control
 ** ID: TA0011
 ** Reference URL: https://attack.mitre.org/tactics/TA0011/
-
-[[ipsec-nat-traversal-port-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 8 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:udp
-and destination.port:4500
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport:udp and destination.port:4500
-----------------------------------
-
-Version 2 (7.6.1 release)::
-* Removed auditbeat-\*, packetbeat-*, and winlogbeat-* from the rule indices.
-
diff --git a/docs/detections/prebuilt-rules/rule-details/kerberos-cached-credentials-dumping.asciidoc b/docs/detections/prebuilt-rules/rule-details/kerberos-cached-credentials-dumping.asciidoc
index 680db815a9..2603316ffc 100644
--- a/docs/detections/prebuilt-rules/rule-details/kerberos-cached-credentials-dumping.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kerberos-cached-credentials-dumping.asciidoc
@@ -5,54 +5,89 @@ Identifies the use of the Kerberos credential cache (kcc) utility to dump locall
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/EmpireProject/EmPyre/blob/master/lib/modules/collection/osx/kerberosdump.py
 * https://opensource.apple.com/source/Heimdal/Heimdal-323.12/kuser/kcc-commands.in.auto.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Credential Access
 
-*Version*: 100 (<<kerberos-cached-credentials-dumping-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.10.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:kcc and process.args:copy_cred_cache
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+  process.name:kcc and
+  process.args:copy_cred_cache
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,22 +99,11 @@ process.name:kcc and process.args:copy_cred_cache
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[kerberos-cached-credentials-dumping-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Technique:
+** Name: Steal or Forge Kerberos Tickets
+** ID: T1558
+** Reference URL: https://attack.mitre.org/techniques/T1558/
+* Sub-technique:
+** Name: Kerberoasting
+** ID: T1558.003
+** Reference URL: https://attack.mitre.org/techniques/T1558/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/kerberos-pre-authentication-disabled-for-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/kerberos-pre-authentication-disabled-for-user.asciidoc
index 447b6e1eda..9ffd06a57f 100644
--- a/docs/detections/prebuilt-rules/rule-details/kerberos-pre-authentication-disabled-for-user.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kerberos-pre-authentication-disabled-for-user.asciidoc
@@ -5,101 +5,121 @@ Identifies the modification of an account's Kerberos pre-authentication options.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://harmj0y.medium.com/roasting-as-reps-e6179a65216b
 * https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4738
 * https://github.com/atc-project/atomic-threat-coverage/blob/master/Atomic_Threat_Coverage/Logging_Policies/LP_0026_windows_audit_user_account_management.md
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
-
-*Version*: 102 (<<kerberos-pre-authentication-disabled-for-user-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Defense Evasion
+* Tactic: Privilege Escalation
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
+* Data Source: Active Directory
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Kerberos Pre-authentication Disabled for User
+*Triage and analysis*
+
+
+
+*Investigating Kerberos Pre-authentication Disabled for User*
+
 
-Kerberos pre-authentication is an account protection against offline password cracking. When enabled, a user requesting
-access to a resource initiates communication with the Domain Controller (DC) by sending an Authentication Server Request
-(AS-REQ) message with a timestamp that is encrypted with the hash of their password. If and only if the DC is able to
-successfully decrypt the timestamp with the hash of the user’s password, it will then send an Authentication Server
-Response (AS-REP) message that contains the Ticket Granting Ticket (TGT) to the user. Part of the AS-REP message is
-signed with the user’s password. Microsoft's security monitoring [recommendations](https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4738) state that `'Don't Require Preauth' – Enabled` should not be enabled for user accounts because it weakens security for the account’s Kerberos authentication.
+Kerberos pre-authentication is an account protection against offline password cracking. When enabled, a user requesting access to a resource initiates communication with the Domain Controller (DC) by sending an Authentication Server Request (AS-REQ) message with a timestamp that is encrypted with the hash of their password. If and only if the DC is able to successfully decrypt the timestamp with the hash of the user’s password, it will then send an Authentication Server Response (AS-REP) message that contains the Ticket Granting Ticket (TGT) to the user. Part of the AS-REP message is signed with the user’s password. Microsoft's security monitoring https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4738[recommendations] state that `'Don't Require Preauth' – Enabled` should not be enabled for user accounts because it weakens security for the account’s Kerberos authentication.
 
-AS-REP roasting is an attack against Kerberos for user accounts that do not require pre-authentication, which means that
-if the target user has pre-authentication disabled, an attacker can request authentication data for it and get a TGT that
-can be brute-forced offline, similarly to Kerberoasting.
+AS-REP roasting is an attack against Kerberos for user accounts that do not require pre-authentication, which means that if the target user has pre-authentication disabled, an attacker can request authentication data for it and get a TGT that can be brute-forced offline, similarly to Kerberoasting.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Determine if the target account is sensitive or privileged.
 - Inspect the account activities for suspicious or abnormal behaviors in the alert timeframe.
 
-### False positive analysis
 
-- Disabling pre-authentication is a bad security practice and should not be allowed in the domain. The security team
-should map and monitor any potential benign true positives (B-TPs), especially if the target account is privileged.
+*False positive analysis*
+
+
+- Disabling pre-authentication is a bad security practice and should not be allowed in the domain. The security team should map and monitor any potential benign true positives (B-TPs), especially if the target account is privileged.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Reset the target account's password if there is any risk of TGTs having been retrieved.
 - Re-enable the preauthentication option or disable the target account.
 - Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit User Account Management' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+Account Management >
+Audit User Account Management (Success,Failure)
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.code:4738 and message:"'Don't Require Preauth' - Enabled"
+[source, js]
 ----------------------------------
+event.code:4738 and winlog.api:"wineventlog" and message:"'Don't Require Preauth' - Enabled"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -111,21 +131,27 @@ event.code:4738 and message:"'Don't Require Preauth' - Enabled"
 ** Name: Steal or Forge Kerberos Tickets
 ** ID: T1558
 ** Reference URL: https://attack.mitre.org/techniques/T1558/
-
-[[kerberos-pre-authentication-disabled-for-user-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Rule name changed from: Kerberos Preauthentication Disabled for User
+* Sub-technique:
+** Name: AS-REP Roasting
+** ID: T1558.004
+** Reference URL: https://attack.mitre.org/techniques/T1558/004/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Domain Accounts
+** ID: T1078.002
+** Reference URL: https://attack.mitre.org/techniques/T1078/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/kerberos-traffic-from-unusual-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/kerberos-traffic-from-unusual-process.asciidoc
index fca39329f8..c6cd8caa07 100644
--- a/docs/detections/prebuilt-rules/rule-details/kerberos-traffic-from-unusual-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kerberos-traffic-from-unusual-process.asciidoc
@@ -5,140 +5,176 @@ Identifies network connections to the standard Kerberos port from an unusual pro
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
-* winlogbeat-*
-* logs-windows.*
+* logs-endpoint.events.network-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<kerberos-traffic-from-unusual-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-HTTP traffic on a non standard port. Verify that the destination IP address is not related to a Domain Controller.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Kerberos Traffic from Unusual Process
+*Triage and analysis*
+
+
 
-Kerberos is the default authentication protocol in Active Directory, designed to provide strong authentication for
-client/server applications by using secret-key cryptography.
+*Investigating Kerberos Traffic from Unusual Process*
 
-Domain-joined hosts usually perform Kerberos traffic using the `lsass.exe` process. This rule detects the occurrence of
-traffic on the Kerberos port (88) by processes other than `lsass.exe` to detect the unusual request and usage of
-Kerberos tickets.
+
+Kerberos is the default authentication protocol in Active Directory, designed to provide strong authentication for client/server applications by using secret-key cryptography.
+
+Domain-joined hosts usually perform Kerberos traffic using the `lsass.exe` process. This rule detects the occurrence of traffic on the Kerberos port (88) by processes other than `lsass.exe` to detect the unusual request and usage of Kerberos tickets.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Check if the Destination IP is related to a Domain Controller.
 - Review event ID 4769 for suspicious ticket requests.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
-- This rule uses a Kerberos-related port but does not identify the protocol used on that port. HTTP traffic on a
-non-standard port or destination IP address unrelated to Domain controllers can create false positives.
+- This rule uses a Kerberos-related port but does not identify the protocol used on that port. HTTP traffic on a non-standard port or destination IP address unrelated to Domain controllers can create false positives.
 - Exceptions can be added for noisy/frequent connections.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
   - Ticket requests can be used to investigate potentially compromised accounts.
 - If the triage identified malware, search the environment for additional compromised hosts.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-network where event.type == "start" and network.direction :
-("outgoing", "egress") and destination.port == 88 and source.port >=
-49152 and not process.executable :
-("?:\\Windows\\System32\\lsass.exe", "System",
-"\\device\\harddiskvolume?\\windows\\system32\\lsass.exe",
-"?:\\Program Files\\rapid7\\nexpose\\nse\\.DLLCACHE\\nseserv.exe",
-"?:\\Program Files (x86)\\GFI\\LanGuard 12 Agent\\lnsscomm.exe",
-"?:\\Program Files (x86)\\SuperScan\\scanner.exe",
-"?:\\Program Files (x86)\\Nmap\\nmap.exe",
-"\\device\\harddiskvolume?\\program files (x86)\\nmap\\nmap.exe") and
-destination.address !="127.0.0.1" and destination.address !="::1" and
-/* insert false positives here */ not process.name in ("swi_fc.exe",
-"fsIPcam.exe", "IPCamera.exe", "MicrosoftEdgeCP.exe",
-"MicrosoftEdge.exe", "iexplore.exe", "chrome.exe", "msedge.exe",
-"opera.exe", "firefox.exe")
+[source, js]
 ----------------------------------
+network where host.os.type == "windows" and event.type == "start" and network.direction == "egress" and
+  destination.port == 88 and source.port >= 49152 and process.pid != 4 and destination.address : "*" and
+  not 
+  (
+    process.executable : (
+        "\\device\\harddiskvolume?\\program files (x86)\\nmap\\nmap.exe",
+        "\\device\\harddiskvolume?\\program files (x86)\\nmap oem\\nmap.exe",
+        "\\device\\harddiskvolume?\\windows\\system32\\lsass.exe",
+        "?:\\Program Files\\Amazon Corretto\\jdk1*\\bin\\java.exe",
+        "?:\\Program Files\\BlackBerry\\UEM\\Proxy Server\\bin\\prunsrv.exe",
+        "?:\\Program Files\\BlackBerry\\UEM\\Core\\tomcat-core\\bin\\tomcat9.exe",
+        "?:\\Program Files\\DBeaver\\dbeaver.exe",
+        "?:\\Program Files\\Docker\\Docker\\resources\\com.docker.backend.exe",
+        "?:\\Program Files\\Docker\\Docker\\resources\\com.docker.vpnkit.exe",
+        "?:\\Program Files\\Docker\\Docker\\resources\\vpnkit.exe",
+        "?:\\Program Files\\Google\\Chrome\\Application\\chrome.exe",
+        "?:\\Program Files\\Internet Explorer\\iexplore.exe",
+        "?:\\Program Files\\JetBrains\\PyCharm Community Edition*\\bin\\pycharm64.exe",
+        "?:\\Program Files\\Mozilla Firefox\\firefox.exe",
+        "?:\\Program Files\\Oracle\\VirtualBox\\VirtualBoxVM.exe",
+        "?:\\Program Files\\Puppet Labs\\Puppet\\puppet\\bin\\ruby.exe",
+        "?:\\Program Files\\rapid7\\nexpose\\nse\\.DLLCACHE\\nseserv.exe",
+        "?:\\Program Files\\Silverfort\\Silverfort AD Adapter\\SilverfortServer.exe",
+        "?:\\Program Files\\Tenable\\Nessus\\nessusd.exe",
+        "?:\\Program Files\\VMware\\VMware View\\Server\\bin\\ws_TomcatService.exe",
+        "?:\\Program Files (x86)\\Advanced Port Scanner\\advanced_port_scanner.exe",
+        "?:\\Program Files (x86)\\DesktopCentral_Agent\\bin\\dcpatchscan.exe",
+        "?:\\Program Files (x86)\\GFI\\LanGuard 12 Agent\\lnsscomm.exe",
+        "?:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe",
+        "?:\\Program Files (x86)\\Internet Explorer\\iexplore.exe",
+        "?:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe",
+        "?:\\Program Files (x86)\\Microsoft\\EdgeUpdate\\MicrosoftEdgeUpdate.exe",
+        "?:\\Program Files (x86)\\Microsoft Silverlight\\sllauncher.exe",
+        "?:\\Program Files (x86)\\Nmap\\nmap.exe",
+        "?:\\Program Files (x86)\\Nmap OEM\\nmap.exe",
+        "?:\\Program Files (x86)\\nwps\\NetScanTools Pro\\NSTPRO.exe",
+        "?:\\Program Files (x86)\\SAP BusinessObjects\\tomcat\\bin\\tomcat9.exe",
+        "?:\\Program Files (x86)\\SuperScan\\scanner.exe",
+        "?:\\Program Files (x86)\\Zscaler\\ZSATunnel\\ZSATunnel.exe",
+        "?:\\Windows\\System32\\lsass.exe",
+        "?:\\Windows\\System32\\MicrosoftEdgeCP.exe",
+        "?:\\Windows\\System32\\svchost.exe",
+        "?:\\Windows\\SysWOW64\\vmnat.exe",
+        "?:\\Windows\\SystemApps\\Microsoft.MicrosoftEdge_*\\MicrosoftEdge.exe",
+        "System"
+    ) and process.code_signature.trusted == true
+  ) and
+ destination.address != "127.0.0.1" and destination.address != "::1"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -150,70 +186,3 @@ destination.address !="127.0.0.1" and destination.address !="::1" and
 ** Name: Steal or Forge Kerberos Tickets
 ** ID: T1558
 ** Reference URL: https://attack.mitre.org/techniques/T1558/
-
-[[kerberos-traffic-from-unusual-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network where event.type == "start" and network.direction :
-("outgoing", "egress") and destination.port == 88 and source.port >=
-49152 and process.executable != "C:\\Windows\\System32\\lsass.exe"
-and destination.address !="127.0.0.1" and destination.address !="::1"
-and /* insert false positives here */ not process.name in
-("swi_fc.exe", "fsIPcam.exe", "IPCamera.exe", "MicrosoftEdgeCP.exe",
-"MicrosoftEdge.exe", "iexplore.exe", "chrome.exe", "msedge.exe",
-"opera.exe", "firefox.exe")
-----------------------------------
-
-Version 7 (8.3.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network where event.type == "start" and network.direction :
-("outgoing", "egress") and destination.port == 88 and source.port >=
-49152 and process.executable != "C:\\Windows\\System32\\lsass.exe"
-and destination.address !="127.0.0.1" and destination.address !="::1"
-and /* insert False Positives here */ not process.name in
-("swi_fc.exe", "fsIPcam.exe", "IPCamera.exe", "MicrosoftEdgeCP.exe",
-"MicrosoftEdge.exe", "iexplore.exe", "chrome.exe", "msedge.exe",
-"opera.exe", "firefox.exe")
-----------------------------------
-
-Version 4 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network where event.type == "start" and network.direction ==
-"outgoing" and destination.port == 88 and source.port >= 49152 and
-process.executable != "C:\\Windows\\System32\\lsass.exe" and
-destination.address !="127.0.0.1" and destination.address !="::1" and
-/* insert False Positives here */ not process.name in ("swi_fc.exe",
-"fsIPcam.exe", "IPCamera.exe", "MicrosoftEdgeCP.exe",
-"MicrosoftEdge.exe", "iexplore.exe", "chrome.exe", "msedge.exe",
-"opera.exe", "firefox.exe")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/kernel-driver-load-by-non-root-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/kernel-driver-load-by-non-root-user.asciidoc
new file mode 100644
index 0000000000..e19b65b394
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/kernel-driver-load-by-non-root-user.asciidoc
@@ -0,0 +1,111 @@
+[[kernel-driver-load-by-non-root-user]]
+=== Kernel Driver Load by non-root User
+
+Detects the loading of a Linux kernel module by a non-root user through system calls. Threat actors may leverage Linux kernel modules to load a rootkit on a system providing them with complete control and the ability to hide from security products. As other rules monitor for the addition of Linux kernel modules through system utilities or .ko files, this rule covers the gap that evasive rootkits leverage by monitoring for kernel module additions on the lowest level through auditd_manager.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Auditd Manager.
+
+
+*Auditd Manager Integration Setup*
+
+The Auditd Manager Integration receives audit events from the Linux Audit Framework which is a part of the Linux kernel.
+Auditd Manager provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system.
+
+
+*The following steps should be executed in order to add the Elastic Agent System integration "auditd_manager" on a Linux System:*
+
+- Go to the Kibana home page and click “Add integrations”.
+- In the query bar, search for “Auditd Manager” and select the integration to see more details about it.
+- Click “Add Auditd Manager”.
+- Configure the integration name and optionally add a description.
+- Review optional and advanced settings accordingly.
+- Add the newly installed “auditd manager” to an existing or a new agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+- Click “Save and Continue”.
+- For more details on the integration refer to the https://docs.elastic.co/integrations/auditd_manager[helper guide].
+
+
+*Rule Specific Setup Note*
+
+Auditd Manager subscribes to the kernel and receives events as they occur without any additional configuration.
+However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+- For this detection rule the following additional audit rules are required to be added to the integration:
+  -- "-a always,exit -F arch=b64 -S finit_module -S init_module -S delete_module -F auid!=-1 -k modules"
+  -- "-a always,exit -F arch=b32 -S finit_module -S init_module -S delete_module -F auid!=-1 -k modules"
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+driver where host.os.type == "linux" and event.action == "loaded-kernel-module" and
+auditd.data.syscall in ("init_module", "finit_module") and user.id != "0"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Sub-technique:
+** Name: Kernel Modules and Extensions
+** ID: T1547.006
+** Reference URL: https://attack.mitre.org/techniques/T1547/006/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Rootkit
+** ID: T1014
+** Reference URL: https://attack.mitre.org/techniques/T1014/
diff --git a/docs/detections/prebuilt-rules/rule-details/kernel-driver-load.asciidoc b/docs/detections/prebuilt-rules/rule-details/kernel-driver-load.asciidoc
new file mode 100644
index 0000000000..e104bc0d52
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/kernel-driver-load.asciidoc
@@ -0,0 +1,101 @@
+[[kernel-driver-load]]
+=== Kernel Driver Load
+
+Detects the loading of a Linux kernel module through system calls. Threat actors may leverage Linux kernel modules to load a rootkit on a system providing them with complete control and the ability to hide from security products. As other rules monitor for the addition of Linux kernel modules through system utilities or .ko files, this rule covers the gap that evasive rootkits leverage by monitoring for kernel module additions on the lowest level through auditd_manager.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+This rule requires the use of the `auditd_manager` integration. `Auditd_manager` is a tool designed to simplify and enhance the management of the audit subsystem in Linux systems. It provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system. The following steps should be executed in order to install and deploy `auditd_manager` on a Linux system. 
+
+```
+Kibana -->
+Management -->
+Integrations -->
+Auditd Manager -->
+Add Auditd Manager
+```
+
+`Auditd_manager` subscribes to the kernel and receives events as they occur without any additional configuration. However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from. 
+
+For this detection rule to trigger, the following additional audit rules are required to be added to the integration:
+```
+-a always,exit -F arch=b64 -S finit_module -S init_module -S delete_module -F auid!=-1 -k modules
+-a always,exit -F arch=b32 -S finit_module -S init_module -S delete_module -F auid!=-1 -k modules
+```
+
+Add the newly installed `auditd manager` to an agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+driver where host.os.type == "linux" and event.action == "loaded-kernel-module" and
+auditd.data.syscall in ("init_module", "finit_module")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Sub-technique:
+** Name: Kernel Modules and Extensions
+** ID: T1547.006
+** Reference URL: https://attack.mitre.org/techniques/T1547/006/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Rootkit
+** ID: T1014
+** Reference URL: https://attack.mitre.org/techniques/T1014/
diff --git a/docs/detections/prebuilt-rules/rule-details/kernel-load-or-unload-via-kexec-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/kernel-load-or-unload-via-kexec-detected.asciidoc
new file mode 100644
index 0000000000..b7c9d9dd71
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/kernel-load-or-unload-via-kexec-detected.asciidoc
@@ -0,0 +1,132 @@
+[[kernel-load-or-unload-via-kexec-detected]]
+=== Kernel Load or Unload via Kexec Detected
+
+This detection rule identifies the usage of kexec, helping to uncover unauthorized kernel replacements and potential compromise of the system's integrity. Kexec is a Linux feature that enables the loading and execution of a different kernel without going through the typical boot process. Malicious actors can abuse kexec to bypass security measures, escalate privileges, establish persistence or hide their activities by loading a malicious kernel, enabling them to tamper with the system's trusted state, allowing e.g. a VM Escape.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.crowdstrike.com/blog/venom-vulnerability-details/
+* https://www.makeuseof.com/what-is-venom-vulnerability/
+* https://madaidans-insecurities.github.io/guides/linux-hardening.html
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "kexec" and process.args in ("--exec", "-e", "--load", "-l", "--unload", "-u")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Escape to Host
+** ID: T1611
+** Reference URL: https://attack.mitre.org/techniques/T1611/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Sub-technique:
+** Name: Kernel Modules and Extensions
+** ID: T1547.006
+** Reference URL: https://attack.mitre.org/techniques/T1547/006/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify System Image
+** ID: T1601
+** Reference URL: https://attack.mitre.org/techniques/T1601/
+* Sub-technique:
+** Name: Patch System Image
+** ID: T1601.001
+** Reference URL: https://attack.mitre.org/techniques/T1601/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/kernel-module-load-via-insmod.asciidoc b/docs/detections/prebuilt-rules/rule-details/kernel-module-load-via-insmod.asciidoc
index b8ea822158..4e4e75e983 100644
--- a/docs/detections/prebuilt-rules/rule-details/kernel-module-load-via-insmod.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kernel-module-load-via-insmod.asciidoc
@@ -1,57 +1,184 @@
 [[kernel-module-load-via-insmod]]
-=== Kernel module load via insmod
+=== Kernel Module Load via insmod
 
 Detects the use of the insmod binary to load a Linux kernel object file. Threat actors can use this binary, given they have root privileges, to load a rootkit on a system providing them with complete control and the ability to hide from security products. Manually loading a kernel module in this manner should not be at all common and can indicate suspcious or malicious behavior.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-*
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://decoded.avast.io/davidalvarez/linux-threat-hunting-syslogk-a-kernel-rootkit-found-under-development-in-the-wild/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Threat: Rootkit
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
+
+*Version*: 109
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Persistence
-* Rootkit
 
-*Version*: 100 (<<kernel-module-load-via-insmod-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.4.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Triage and analysis*
+
+
+
+*Investigating Kernel module load via insmod*
+
+
+The insmod binary is a Linux utility that allows users with root privileges to load kernel modules, which are object files that extend the functionality of the kernel. 
+
+Threat actors can abuse this utility to load rootkits, granting them full control over the system and the ability to evade security products.
+
+The detection rule 'Kernel module load via insmod' is designed to identify instances where the insmod binary is used to load a kernel object file (with a .ko extension) on a Linux system. This activity is uncommon and may indicate suspicious or malicious behavior.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Investigate the kernel object file that was loaded via insmod.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+- Investigate the kernel ring buffer for any warnings or messages, such as tainted or out-of-tree kernel module loads through `dmesg`.
+- Investigate syslog for any unusual segfaults or other messages. Rootkits may be installed on targets with different architecture as expected, and could potentially cause segmentation faults. 
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+    - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+    - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+    - $osquery_6
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator who uses cron jobs for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Related Rules*
+
+
+- Kernel Driver Load - 3e12a439-d002-4944-bc42-171c0dcb9b96
+- Tainted Out-Of-Tree Kernel Module Load - 51a09737-80f7-4551-a3be-dac8ef5d181a
+- Tainted Kernel Module Load - 05cad2fb-200c-407f-b472-02ea8c9e5e4a
+- Attempt to Clear Kernel Ring Buffer - 2724808c-ba5d-48b2-86d2-0002103df753
+- Enumeration of Kernel Modules via Proc - 80084fa9-8677-4453-8680-b891d3c0c778
+- Suspicious Modprobe File Event - 40ddbcc8-6561-44d9-afc8-eefdbfe0cccd
+- Kernel Module Removal - cd66a5af-e34b-4bb0-8931-57d0a043f2ef
+- Enumeration of Kernel Modules - 2d8043ed-5bda-4caf-801c-c1feb7410504
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.executable :
-"/usr/sbin/insmod" and process.args : "*.ko"
+[source, js]
 ----------------------------------
+process where host.os.type == "linux" and event.type == "start" and process.name == "insmod" and process.args : "*.ko"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -63,10 +190,7 @@ process where event.type == "start" and process.executable :
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[kernel-module-load-via-insmod-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Kernel Modules and Extensions
+** ID: T1547.006
+** Reference URL: https://attack.mitre.org/techniques/T1547/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/kernel-module-removal.asciidoc b/docs/detections/prebuilt-rules/rule-details/kernel-module-removal.asciidoc
index 63277ea649..7daa946950 100644
--- a/docs/detections/prebuilt-rules/rule-details/kernel-module-removal.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kernel-module-removal.asciidoc
@@ -3,60 +3,92 @@
 
 Kernel modules are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. This rule identifies attempts to remove a kernel module.
 
-*Rule type*: query
+*Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
-*Severity*: high
+*Severity*: medium
 
-*Risk score*: 73
+*Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * http://man7.org/linux/man-pages/man8/modprobe.8.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 109
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Defense Evasion
 
-*Version*: 100 (<<kernel-module-removal-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.8.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-There is usually no reason to remove modules, but some buggy modules require it. These can be exempted by username. Note that some Linux distributions are not built to support the removal of modules at all.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.args:((rmmod and sudo) or (modprobe and sudo and ("--remove"
-or "-r")))
+[source, js]
 ----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
+process.name == "rmmod" or (process.name == "modprobe" and process.args in ("--remove", "-r")) and 
+process.parent.name in ("sudo", "bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -68,8 +100,10 @@ or "-r")))
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -78,37 +112,7 @@ or "-r")))
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[kernel-module-removal-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:executed and process.args:(rmmod and sudo or modprobe and
-sudo and ("--remove" or "-r"))
-----------------------------------
-
+* Sub-technique:
+** Name: Kernel Modules and Extensions
+** ID: T1547.006
+** Reference URL: https://attack.mitre.org/techniques/T1547/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/keychain-password-retrieval-via-command-line.asciidoc b/docs/detections/prebuilt-rules/rule-details/keychain-password-retrieval-via-command-line.asciidoc
index a0daef31f0..6bf8738595 100644
--- a/docs/detections/prebuilt-rules/rule-details/keychain-password-retrieval-via-command-line.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/keychain-password-retrieval-via-command-line.asciidoc
@@ -5,74 +5,93 @@ Adversaries may collect keychain storage data from a system to in order to acqui
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.netmeister.org/blog/keychain-passwords.html
 * https://github.com/priyankchheda/chrome_password_grabber/blob/master/chrome.py
 * https://ss64.com/osx/security.html
 * https://www.intezer.com/blog/research/operation-electrorat-attacker-creates-fake-companies-to-drain-your-crypto-wallets/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Credential Access
 
-*Version*: 100 (<<keychain-password-retrieval-via-command-line-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.12.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
 
-==== Potential false positives
 
-Applications for password management.
+This rule requires data coming in from Elastic Defend.
 
-==== Investigation guide
 
+*Elastic Defend Integration Setup*
 
-[source,markdown]
-----------------------------------
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-----------------------------------
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "security" and
-process.args : "-wa" and process.args : ("find-generic-password",
-"find-internet-password") and process.args : ("Chrome*", "Chromium",
-"Opera", "Safari*", "Brave", "Microsoft Edge", "Edge", "Firefox*") and
-not process.parent.executable : "/Applications/Keeper Password
-Manager.app/Contents/Frameworks/Keeper Password Manager
-Helper*/Contents/MacOS/Keeper Password Manager Helper*"
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.action == "exec" and
+ process.name : "security" and
+ process.args : ("-wa", "-ga") and process.args : ("find-generic-password", "find-internet-password") and
+ process.command_line : ("*Chrome*", "*Chromium*", "*Opera*", "*Safari*", "*Brave*", "*Microsoft Edge*", "*Firefox*") and
+ not process.parent.executable : "/Applications/Keeper Password Manager.app/Contents/Frameworks/Keeper Password Manager Helper*/Contents/MacOS/Keeper Password Manager Helper*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,26 +103,15 @@ Helper*/Contents/MacOS/Keeper Password Manager Helper*"
 ** Name: Credentials from Password Stores
 ** ID: T1555
 ** Reference URL: https://attack.mitre.org/techniques/T1555/
-
-[[keychain-password-retrieval-via-command-line-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:security and process.args:("find-generic-password" or
-"find-internet-password")
-----------------------------------
-
+* Sub-technique:
+** Name: Keychain
+** ID: T1555.001
+** Reference URL: https://attack.mitre.org/techniques/T1555/001/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Sub-technique:
+** Name: Credentials from Web Browsers
+** ID: T1555.003
+** Reference URL: https://attack.mitre.org/techniques/T1555/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/kirbi-file-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/kirbi-file-creation.asciidoc
new file mode 100644
index 0000000000..e60ee80ee9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/kirbi-file-creation.asciidoc
@@ -0,0 +1,65 @@
+[[kirbi-file-creation]]
+=== Kirbi File Creation
+
+Identifies the creation of .kirbi files. The creation of this kind of file is an indicator of an attacker running Kerberos ticket dump utilities, such as Mimikatz, and precedes attacks such as Pass-The-Ticket (PTT), which allows the attacker to impersonate users using Kerberos tickets.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 60m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and file.extension : "kirbi"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Technique:
+** Name: Steal or Forge Kerberos Tickets
+** ID: T1558
+** Reference URL: https://attack.mitre.org/techniques/T1558/
diff --git a/docs/detections/prebuilt-rules/rule-details/krbtgt-delegation-backdoor.asciidoc b/docs/detections/prebuilt-rules/rule-details/krbtgt-delegation-backdoor.asciidoc
index 059b187baf..46b1d0e3ab 100644
--- a/docs/detections/prebuilt-rules/rule-details/krbtgt-delegation-backdoor.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/krbtgt-delegation-backdoor.asciidoc
@@ -5,64 +5,76 @@ Identifies the modification of the msDS-AllowedToDelegateTo attribute to KRBTGT.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://skyblue.team/posts/delegate-krbtgt
 * https://github.com/atc-project/atomic-threat-coverage/blob/master/Atomic_Threat_Coverage/Logging_Policies/LP_0026_windows_audit_user_account_management.md
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Use Case: Active Directory Monitoring
+* Data Source: Active Directory
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Active Directory
 
-*Version*: 100 (<<krbtgt-delegation-backdoor-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.1.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+The 'Audit User Account Management' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
 
-----------------------------------
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+Account Management >
+Audit User Account Management (Success,Failure)
+```
 
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.action:modified-user-account and event.code:4738 and
-winlog.event_data.AllowedToDelegateTo:*krbtgt*
-----------------------------------
+  winlog.event_data.AllowedToDelegateTo:*krbtgt*
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,8 +86,6 @@ winlog.event_data.AllowedToDelegateTo:*krbtgt*
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-
 * Tactic:
 ** Name: Credential Access
 ** ID: TA0006
@@ -84,16 +94,3 @@ winlog.event_data.AllowedToDelegateTo:*krbtgt*
 ** Name: Steal or Forge Kerberos Tickets
 ** ID: T1558
 ** Reference URL: https://attack.mitre.org/techniques/T1558/
-
-[[krbtgt-delegation-backdoor-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-anonymous-request-authorized.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-anonymous-request-authorized.asciidoc
index 26dcfe971b..ca6c58a68c 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-anonymous-request-authorized.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-anonymous-request-authorized.asciidoc
@@ -5,7 +5,7 @@ This rule detects when an unauthenticated user request is authorized within the
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,62 +13,53 @@ This rule detects when an unauthenticated user request is authorized within the
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://media.defense.gov/2022/Aug/29/2003066362/-1/-1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Execution
-* Initial Access
-* Defense Evasion
-
-*Version*: 2 (<<kubernetes-anonymous-request-authorized-history, version history>>)
+* Data Source: Kubernetes
+* Tactic: Execution
+* Tactic: Initial Access
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 8.5.0
+*Version*: 6
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Anonymous access to the API server is a dangerous setting enabled by default. Common anonymous connections (e.g., health checks) have been excluded from this rule. All other instances of authorized anonymous requests should be investigated.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset : "kubernetes.audit_logs" and
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and (kubernetes.audit.user.username:("system:anonymous" or
-"system:unauthenticated") or not kubernetes.audit.user.username:*)
-and not kubernetes.audit.objectRef.resource:("healthz" or "livez" or
-"readyz")
+[source, js]
 ----------------------------------
+event.dataset:kubernetes.audit_logs
+  and kubernetes.audit.annotations.authorization_k8s_io/decision:allow
+  and kubernetes.audit.user.username:("system:anonymous" or "system:unauthenticated" or not *)
+  and not kubernetes.audit.requestURI:(/healthz* or /livez* or /readyz*)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,19 +71,7 @@ and not kubernetes.audit.objectRef.resource:("healthz" or "livez" or
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[kubernetes-anonymous-request-authorized-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and (kubernetes.audit.user.username:("system:anonymous" or
-"system:unauthenticated") or not kubernetes.audit.user.username:*)
-and not kubernetes.audit.objectRef.resource:("healthz" or "livez" or
-"readyz")
-----------------------------------
-
+* Sub-technique:
+** Name: Default Accounts
+** ID: T1078.001
+** Reference URL: https://attack.mitre.org/techniques/T1078/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-container-created-with-excessive-linux-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-container-created-with-excessive-linux-capabilities.asciidoc
index 17293f6099..1948751eb8 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-container-created-with-excessive-linux-capabilities.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-container-created-with-excessive-linux-capabilities.asciidoc
@@ -5,7 +5,7 @@ This rule detects a container deployed with one or more dangerously permissive L
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,85 +13,82 @@ This rule detects a container deployed with one or more dangerously permissive L
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-capabilities-for-a-container
 * https://0xn3va.gitbook.io/cheat-sheets/container/escaping/excessive-capabilities
 * https://man7.org/linux/man-pages/man7/capabilities.7.html
 * https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Execution
-* Privilege Escalation
+* Data Source: Kubernetes
+* Tactic: Execution
+* Tactic: Privilege Escalation
 
-*Version*: 1
+*Version*: 4
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Some container images require the addition of privileged capabilities. This rule leaves space for the exception of trusted container images. To add an exception, add the trusted container image name to the query field, kubernetes.audit.requestObject.spec.containers.image.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Kubernetes Container Created with Excessive Linux Capabilities
+*Triage and analysis*
+
+
+
+*Investigating Kubernetes Container Created with Excessive Linux Capabilities*
+
 
 Linux capabilities were designed to divide root privileges into smaller units. Each capability grants a thread just enough power to perform specific privileged tasks. In Kubernetes, containers are given a set of default capabilities that can be dropped or added to at the time of creation. Added capabilities entitle containers in a pod with additional privileges that can be used to change
 core processes, change network settings of a cluster, or directly access the underlying host. The following have been used in container escape techniques:
 
-BPF - Allow creating BPF maps, loading BPF Type Format (BTF) data, retrieve JITed code of BPF programs, and more. 
-DAC_READ_SEARCH - Bypass file read permission checks and directory read and execute permission checks. 
-NET_ADMIN - Perform various network-related operations. 
-SYS_ADMIN - Perform a range of system administration operations. 
-SYS_BOOT - Use reboot(2) and kexec_load(2), reboot and load a new kernel for later execution. 
-SYS_MODULE - Load and unload kernel modules. 
+BPF - Allow creating BPF maps, loading BPF Type Format (BTF) data, retrieve JITed code of BPF programs, and more.
+DAC_READ_SEARCH - Bypass file read permission checks and directory read and execute permission checks.
+NET_ADMIN - Perform various network-related operations.
+SYS_ADMIN - Perform a range of system administration operations.
+SYS_BOOT - Use reboot(2) and kexec_load(2), reboot and load a new kernel for later execution.
+SYS_MODULE - Load and unload kernel modules.
 SYS_PTRACE - Trace arbitrary processes using ptrace(2).
-SYS_RAWIO - Perform I/O port operations (iopl(2) and ioperm(2)). 
+SYS_RAWIO - Perform I/O port operations (iopl(2) and ioperm(2)).
 SYSLOG - Perform privileged syslog(2) operations.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - While these capabilities are not included by default in containers, some legitimate images may need to add them. This rule leaves space for the exception of trusted container images. To add an exception, add the trusted container image name to the query field, kubernetes.audit.requestObject.spec.containers.image.
-----------------------------------
 
+==== Setup
+
+
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset: kubernetes.audit_logs and
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and kubernetes.audit.verb: create and
-kubernetes.audit.objectRef.resource: pods and kubernetes.audit.requ
-estObject.spec.containers.securityContext.capabilities.add: ("BPF" or
-"DAC_READ_SEARCH" or "NET_ADMIN" or "SYS_ADMIN" or "SYS_BOOT" or
-"SYS_MODULE" or "SYS_PTRACE" or "SYS_RAWIO" or "SYSLOG") and not
-kubernetes.audit.requestObject.spec.containers.image :
-("docker.elastic.co/beats/elastic-agent:8.4.0" or "rancher/klipper-
-lb:v0.3.5" or "")
+[source, js]
 ----------------------------------
+event.dataset: kubernetes.audit_logs
+  and kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
+  and kubernetes.audit.verb: create
+  and kubernetes.audit.objectRef.resource: pods
+  and kubernetes.audit.requestObject.spec.containers.securityContext.capabilities.add: ("BPF" or "DAC_READ_SEARCH"  or "NET_ADMIN" or "SYS_ADMIN" or "SYS_BOOT" or "SYS_MODULE" or "SYS_PTRACE" or "SYS_RAWIO"  or "SYSLOG")
+  and not kubernetes.audit.requestObject.spec.containers.image : ("docker.elastic.co/beats/elastic-agent:8.4.0" or "rancher/klipper-lb:v0.3.5" or "")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -103,8 +100,6 @@ lb:v0.3.5" or "")
 ** Name: Escape to Host
 ** ID: T1611
 ** Reference URL: https://attack.mitre.org/techniques/T1611/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-denied-service-account-request.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-denied-service-account-request.asciidoc
index f6d0918e9a..3883222a73 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-denied-service-account-request.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-denied-service-account-request.asciidoc
@@ -5,7 +5,7 @@ This rule detects when a service account makes an unauthorized request for resou
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,58 +13,51 @@ This rule detects when a service account makes an unauthorized request for resou
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://research.nccgroup.com/2021/11/10/detection-engineering-for-kubernetes-clusters/#part3-kubernetes-detections
 * https://kubernetes.io/docs/reference/access-authn-authz/authentication/#service-account-tokens
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Discovery
-
-*Version*: 2 (<<kubernetes-denied-service-account-request-history, version history>>)
+* Data Source: Kubernetes
+* Tactic: Discovery
 
-*Added ({stack} release)*: 8.5.0
+*Version*: 5
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Unauthorized requests from service accounts are highly abnormal and more indicative of human behavior or a serious problem within the cluster. This behavior should be investigated further.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset: "kubernetes.audit_logs" and
-kubernetes.audit.user.username: system\:serviceaccount\:* and
-kubernetes.audit.annotations.authorization_k8s_io/decision: "forbid"
+[source, js]
 ----------------------------------
+event.dataset: "kubernetes.audit_logs"
+  and kubernetes.audit.user.username: system\:serviceaccount\:*
+  and kubernetes.audit.annotations.authorization_k8s_io/decision: "forbid"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,10 +69,3 @@ kubernetes.audit.annotations.authorization_k8s_io/decision: "forbid"
 ** Name: Container and Resource Discovery
 ** ID: T1613
 ** Reference URL: https://attack.mitre.org/techniques/T1613/
-
-[[kubernetes-denied-service-account-request-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-exposed-service-created-with-type-nodeport.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-exposed-service-created-with-type-nodeport.asciidoc
index 81b1c9d26f..361fa900d8 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-exposed-service-created-with-type-nodeport.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-exposed-service-created-with-type-nodeport.asciidoc
@@ -5,7 +5,7 @@ This rule detects an attempt to create or modify a service as type NodePort. The
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,62 +13,55 @@ This rule detects an attempt to create or modify a service as type NodePort. The
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types
 * https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
 * https://www.tigera.io/blog/new-vulnerability-exposes-kubernetes-to-man-in-the-middle-attacks-heres-how-to-mitigate/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Execution
-* Persistence
-
-*Version*: 200 (<<kubernetes-exposed-service-created-with-type-nodeport-history, version history>>)
+* Data Source: Kubernetes
+* Tactic: Execution
+* Tactic: Persistence
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 203
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Developers may have a legitimate use for NodePorts. For frontend parts of an application you may want to expose a Service onto an external IP address without using cloud specific Loadbalancers. NodePort can be used to expose the Service on each Node's IP at a static port (the NodePort). You'll be able to contact the NodePort Service from outside the cluster, by requesting <NodeIP>:<NodePort>. NodePort unlike Loadbalancers, allow the freedom to set up your own load balancing solution, configure environments that aren't fully supported by Kubernetes, or even to expose one or more node's IPs directly.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset : "kubernetes.audit_logs" and
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and kubernetes.audit.objectRef.resource:"services" and
-kubernetes.audit.verb:("create" or "update" or "patch") and
-kubernetes.audit.requestObject.spec.type:"NodePort"
+[source, js]
 ----------------------------------
+event.dataset : "kubernetes.audit_logs"
+  and kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
+  and kubernetes.audit.objectRef.resource:"services"
+  and kubernetes.audit.verb:("create" or "update" or "patch")
+  and kubernetes.audit.requestObject.spec.type:"NodePort"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,20 +73,3 @@ kubernetes.audit.requestObject.spec.type:"NodePort"
 ** Name: External Remote Services
 ** ID: T1133
 ** Reference URL: https://attack.mitre.org/techniques/T1133/
-
-[[kubernetes-exposed-service-created-with-type-nodeport-history]]
-==== Rule version history
-
-Version 200 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.objectRef.resource:"services" and
-kubernetes.audit.verb:("create" or "update" or "patch") and
-kubernetes.audit.requestObject.spec.type:"NodePort"
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-a-sensitive-hostpath-volume.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-a-sensitive-hostpath-volume.asciidoc
index f11384be9e..7a31bde0fa 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-a-sensitive-hostpath-volume.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-a-sensitive-hostpath-volume.asciidoc
@@ -5,7 +5,7 @@ This rule detects when a pod is created with a sensitive volume of type hostPath
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,69 +13,71 @@ This rule detects when a pod is created with a sensitive volume of type hostPath
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.appsecco.com/kubernetes-namespace-breakout-using-insecure-host-path-volume-part-1-b382f2a6e216
 * https://kubernetes.io/docs/concepts/storage/volumes/#hostpath
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Execution
-* Privilege Escalation
-
-*Version*: 200 (<<kubernetes-pod-created-with-a-sensitive-hostpath-volume-history, version history>>)
+* Data Source: Kubernetes
+* Tactic: Execution
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 203
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-An administrator may need to attach a hostPath volume for a legitimate reason. This alert should be investigated for legitimacy by determining if the kuberenetes.audit.requestObject.spec.volumes.hostPath.path triggered is one needed by its target container/pod. For example, when the fleet managed elastic agent is deployed as a daemonset it creates several hostPath volume mounts, some of which are sensitive host directories like /proc, /etc/kubernetes, and /var/log. Add exceptions for trusted container images using the query field "kubernetes.audit.requestObject.spec.container.image"
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset : "kubernetes.audit_logs" and
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.verb:("create" or "update" or "patch") and
-kubernetes.audit.requestObject.spec.volumes.hostPath.path: ("/" or
-"/proc" or "/root" or "/var" or "/var/run" or
-"/var/run/docker.sock" or "/var/run/crio/crio.sock" or
-"/var/run/cri-dockerd.sock" or "/var/lib/kubelet" or
-"/var/lib/kubelet/pki" or "/var/lib/docker/overlay2" or "/etc"
-or "/etc/kubernetes" or "/etc/kubernetes/manifests" or
-"/etc/kubernetes/pki" or "/home/admin") and not
-kubernetes.audit.requestObject.spec.containers.image:
-("docker.elastic.co/beats/elastic-agent:8.4.0")
+[source, js]
 ----------------------------------
+event.dataset : "kubernetes.audit_logs"
+  and kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
+  and kubernetes.audit.objectRef.resource:"pods"
+  and kubernetes.audit.verb:("create" or "update" or "patch")
+  and kubernetes.audit.requestObject.spec.volumes.hostPath.path:
+  ("/" or
+  "/proc" or
+  "/root" or
+  "/var" or
+  "/var/run" or
+  "/var/run/docker.sock" or
+  "/var/run/crio/crio.sock" or
+  "/var/run/cri-dockerd.sock" or
+  "/var/lib/kubelet" or
+  "/var/lib/kubelet/pki" or
+  "/var/lib/docker/overlay2" or
+  "/etc" or
+  "/etc/kubernetes" or
+  "/etc/kubernetes/manifests" or
+  "/etc/kubernetes/pki" or
+  "/home/admin")
+  and not kubernetes.audit.requestObject.spec.containers.image: ("docker.elastic.co/beats/elastic-agent:8.4.0")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -87,8 +89,6 @@ kubernetes.audit.requestObject.spec.containers.image:
 ** Name: Escape to Host
 ** ID: T1611
 ** Reference URL: https://attack.mitre.org/techniques/T1611/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -97,37 +97,3 @@ kubernetes.audit.requestObject.spec.containers.image:
 ** Name: Deploy Container
 ** ID: T1610
 ** Reference URL: https://attack.mitre.org/techniques/T1610/
-
-[[kubernetes-pod-created-with-a-sensitive-hostpath-volume-history]]
-==== Rule version history
-
-Version 200 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.verb:("create" or "update" or "patch") and
-kubernetes.audit.requestObject.spec.volumes.hostPath.path:("/" or
-"/proc" or "/root" or "/var" or "/var/run/docker.sock" or
-"/var/run/crio/crio.sock" or "/var/run/cri-dockerd.sock" or
-"/var/lib/kubelet" or "/var/lib/kubelet/pki" or
-"/var/lib/docker/overlay2" or "/etc" or "/etc/kubernetes" or
-"/etc/kubernetes/manifests" or "/home/admin")
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.verb:("create" or "update" or "patch") and
-kubernetes.audit.requestObject.spec.volumes.hostPath.path:("/" or
-"/proc" or "/root" or "/var" or "/var/run/docker.sock" or
-"/var/run/crio/crio.sock" or "/var/run/cri-dockerd.sock" or
-"/var/lib/kubelet" or "/var/lib/kubelet/pki" or
-"/var/lib/docker/overlay2" or "/etc" or "/etc/kubernetes" or
-"/etc/kubernetes/manifests" or "/home/admin")
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostipc.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostipc.asciidoc
index f5dbb98a35..563eee1bb4 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostipc.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostipc.asciidoc
@@ -5,7 +5,7 @@ This rule detects an attempt to create or modify a pod using the host IPC namesp
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,64 +13,56 @@ This rule detects an attempt to create or modify a pod using the host IPC namesp
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://research.nccgroup.com/2021/11/10/detection-engineering-for-kubernetes-clusters/#part3-kubernetes-detections
 * https://kubernetes.io/docs/concepts/security/pod-security-policy/#host-namespaces
 * https://bishopfox.com/blog/kubernetes-pod-privilege-escalation
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Execution
-* Privilege Escalation
-
-*Version*: 200 (<<kubernetes-pod-created-with-hostipc-history, version history>>)
+* Data Source: Kubernetes
+* Tactic: Execution
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 203
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-An administrator or developer may want to use a pod that runs as root and shares the host's IPC, Network, and PID namespaces for debugging purposes. If something is going wrong in the cluster and there is no easy way to SSH onto the host nodes directly, a privileged pod of this nature can be useful for viewing things like iptable rules and network namespaces from the host's perspective. Add exceptions for trusted container images using the query field "kubernetes.audit.requestObject.spec.container.image"
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset : "kubernetes.audit_logs" and
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.verb:("create" or "update" or "patch") and
-kubernetes.audit.requestObject.spec.hostIPC:true and not
-kubernetes.audit.requestObject.spec.containers.image:
-("docker.elastic.co/beats/elastic-agent:8.4.0")
+[source, js]
 ----------------------------------
+event.dataset : "kubernetes.audit_logs"
+  and kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
+  and kubernetes.audit.objectRef.resource:"pods"
+  and kubernetes.audit.verb:("create" or "update" or "patch")
+  and kubernetes.audit.requestObject.spec.hostIPC:true
+  and not kubernetes.audit.requestObject.spec.containers.image: ("docker.elastic.co/beats/elastic-agent:8.4.0")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -82,8 +74,6 @@ kubernetes.audit.requestObject.spec.containers.image:
 ** Name: Escape to Host
 ** ID: T1611
 ** Reference URL: https://attack.mitre.org/techniques/T1611/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -92,20 +82,3 @@ kubernetes.audit.requestObject.spec.containers.image:
 ** Name: Deploy Container
 ** ID: T1610
 ** Reference URL: https://attack.mitre.org/techniques/T1610/
-
-[[kubernetes-pod-created-with-hostipc-history]]
-==== Rule version history
-
-Version 200 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.verb:("create" or "update" or "patch") and
-kubernetes.audit.requestObject.spec.hostIPC:true
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostnetwork.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostnetwork.asciidoc
index b7c8842525..70177635a4 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostnetwork.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostnetwork.asciidoc
@@ -5,7 +5,7 @@ This rules detects an attempt to create or modify a pod attached to the host net
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,64 +13,56 @@ This rules detects an attempt to create or modify a pod attached to the host net
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://research.nccgroup.com/2021/11/10/detection-engineering-for-kubernetes-clusters/#part3-kubernetes-detections
 * https://kubernetes.io/docs/concepts/security/pod-security-policy/#host-namespaces
 * https://bishopfox.com/blog/kubernetes-pod-privilege-escalation
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Execution
-* Privilege Escalation
-
-*Version*: 200 (<<kubernetes-pod-created-with-hostnetwork-history, version history>>)
+* Data Source: Kubernetes
+* Tactic: Execution
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 203
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-An administrator or developer may want to use a pod that runs as root and shares the hosts IPC, Network, and PID namespaces for debugging purposes. If something is going wrong in the cluster and there is no easy way to SSH onto the host nodes directly, a privileged pod of this nature can be useful for viewing things like iptable rules and network namespaces from the host's perspective. Add exceptions for trusted container images using the query field "kubernetes.audit.requestObject.spec.container.image"
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset : "kubernetes.audit_logs" and
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.verb:("create" or "update" or "patch") and
-kubernetes.audit.requestObject.spec.hostNetwork:true and not
-kubernetes.audit.requestObject.spec.containers.image:
-("docker.elastic.co/beats/elastic-agent:8.4.0")
+[source, js]
 ----------------------------------
+event.dataset : "kubernetes.audit_logs"
+  and kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
+  and kubernetes.audit.objectRef.resource:"pods"
+  and kubernetes.audit.verb:("create" or "update" or "patch")
+  and kubernetes.audit.requestObject.spec.hostNetwork:true
+  and not kubernetes.audit.requestObject.spec.containers.image: ("docker.elastic.co/beats/elastic-agent:8.4.0")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -82,8 +74,6 @@ kubernetes.audit.requestObject.spec.containers.image:
 ** Name: Escape to Host
 ** ID: T1611
 ** Reference URL: https://attack.mitre.org/techniques/T1611/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -92,20 +82,3 @@ kubernetes.audit.requestObject.spec.containers.image:
 ** Name: Deploy Container
 ** ID: T1610
 ** Reference URL: https://attack.mitre.org/techniques/T1610/
-
-[[kubernetes-pod-created-with-hostnetwork-history]]
-==== Rule version history
-
-Version 200 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.verb:("create" or "update" or "patch") and
-kubernetes.audit.requestObject.spec.hostNetwork:true
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostpid.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostpid.asciidoc
index 7ed6ac6619..f939032c83 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostpid.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-pod-created-with-hostpid.asciidoc
@@ -5,7 +5,7 @@ This rule detects an attempt to create or modify a pod attached to the host PID
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,64 +13,56 @@ This rule detects an attempt to create or modify a pod attached to the host PID
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://research.nccgroup.com/2021/11/10/detection-engineering-for-kubernetes-clusters/#part3-kubernetes-detections
 * https://kubernetes.io/docs/concepts/security/pod-security-policy/#host-namespaces
 * https://bishopfox.com/blog/kubernetes-pod-privilege-escalation
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Execution
-* Privilege Escalation
-
-*Version*: 200 (<<kubernetes-pod-created-with-hostpid-history, version history>>)
+* Data Source: Kubernetes
+* Tactic: Execution
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 203
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-An administrator or developer may want to use a pod that runs as root and shares the hosts IPC, Network, and PID namespaces for debugging purposes. If something is going wrong in the cluster and there is no easy way to SSH onto the host nodes directly, a privileged pod of this nature can be useful for viewing things like iptable rules and network namespaces from the host's perspective. Add exceptions for trusted container images using the query field "kubernetes.audit.requestObject.spec.container.image"
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset : "kubernetes.audit_logs" and
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.verb:("create" or "update" or "patch") and
-kubernetes.audit.requestObject.spec.hostPID:true and not
-kubernetes.audit.requestObject.spec.containers.image:
-("docker.elastic.co/beats/elastic-agent:8.4.0")
+[source, js]
 ----------------------------------
+event.dataset : "kubernetes.audit_logs"
+  and kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
+  and kubernetes.audit.objectRef.resource:"pods"
+  and kubernetes.audit.verb:("create" or "update" or "patch")
+  and kubernetes.audit.requestObject.spec.hostPID:true
+  and not kubernetes.audit.requestObject.spec.containers.image: ("docker.elastic.co/beats/elastic-agent:8.4.0")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -82,8 +74,6 @@ kubernetes.audit.requestObject.spec.containers.image:
 ** Name: Escape to Host
 ** ID: T1611
 ** Reference URL: https://attack.mitre.org/techniques/T1611/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -92,20 +82,3 @@ kubernetes.audit.requestObject.spec.containers.image:
 ** Name: Deploy Container
 ** ID: T1610
 ** Reference URL: https://attack.mitre.org/techniques/T1610/
-
-[[kubernetes-pod-created-with-hostpid-history]]
-==== Rule version history
-
-Version 200 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.verb:("create" or "update" or "patch") and
-kubernetes.audit.requestObject.spec.hostPID:true
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-privileged-pod-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-privileged-pod-created.asciidoc
index e2652aec69..974feec576 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-privileged-pod-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-privileged-pod-created.asciidoc
@@ -5,7 +5,7 @@ This rule detects when a user creates a pod/container running in privileged mode
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,63 +13,55 @@ This rule detects when a user creates a pod/container running in privileged mode
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://media.defense.gov/2021/Aug/03/2002820425/-1/-1/1/CTR_KUBERNETES%20HARDENING%20GUIDANCE.PDF
 * https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Execution
-* Privilege Escalation
-
-*Version*: 200 (<<kubernetes-privileged-pod-created-history, version history>>)
+* Data Source: Kubernetes
+* Tactic: Execution
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 203
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-By default a container is not allowed to access any devices on the host, but a "privileged" container is given access to all devices on the host. This allows the container nearly all the same access as processes running on the host. An administrator may want to run a privileged container to use operating system administrative capabilities such as manipulating the network stack or accessing hardware devices from within the cluster. Add exceptions for trusted container images using the query field "kubernetes.audit.requestObject.spec.container.image"
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset : "kubernetes.audit_logs" and
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and kubernetes.audit.objectRef.resource:pods and
-kubernetes.audit.verb:create and kubernetes.audit.requestObject.spe
-c.containers.securityContext.privileged:true and not
-kubernetes.audit.requestObject.spec.containers.image:
-("docker.elastic.co/beats/elastic-agent:8.4.0")
+[source, js]
 ----------------------------------
+event.dataset : "kubernetes.audit_logs"
+  and kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
+  and kubernetes.audit.objectRef.resource:pods
+  and kubernetes.audit.verb:create
+  and kubernetes.audit.requestObject.spec.containers.securityContext.privileged:true
+  and not kubernetes.audit.requestObject.spec.containers.image: ("docker.elastic.co/beats/elastic-agent:8.4.0")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,8 +73,6 @@ kubernetes.audit.requestObject.spec.containers.image:
 ** Name: Escape to Host
 ** ID: T1611
 ** Reference URL: https://attack.mitre.org/techniques/T1611/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -91,20 +81,3 @@ kubernetes.audit.requestObject.spec.containers.image:
 ** Name: Deploy Container
 ** ID: T1610
 ** Reference URL: https://attack.mitre.org/techniques/T1610/
-
-[[kubernetes-privileged-pod-created-history]]
-==== Rule version history
-
-Version 200 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.objectRef.resource:pods and
-kubernetes.audit.verb:create and kubernetes.audit.requestObject.spec
-.containers.securityContext.privileged:true
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-suspicious-assignment-of-controller-service-account.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-suspicious-assignment-of-controller-service-account.asciidoc
index 0142bccf08..24b0993939 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-suspicious-assignment-of-controller-service-account.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-suspicious-assignment-of-controller-service-account.asciidoc
@@ -5,7 +5,7 @@ This rule detects a request to attach a controller service account to an existin
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,61 +13,54 @@ This rule detects a request to attach a controller service account to an existin
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.paloaltonetworks.com/apps/pan/public/downloadResource?pagePath=/content/pan/en_US/resources/whitepapers/kubernetes-privilege-escalation-excessive-permissions-in-popular-platforms
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Execution
-* Privilege Escalation
-
-*Version*: 3 (<<kubernetes-suspicious-assignment-of-controller-service-account-history, version history>>)
+* Data Source: Kubernetes
+* Tactic: Execution
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 8.5.0
+*Version*: 6
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Controller service accounts aren't normally assigned to running pods, this is abnormal behavior with very few legitimate use-cases and should result in very few false positives.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset : "kubernetes.audit_logs" and
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and kubernetes.audit.verb : "create" and
-kubernetes.audit.objectRef.resource : "pods" and
-kubernetes.audit.objectRef.namespace : "kube-system" and
-kubernetes.audit.requestObject.spec.serviceAccountName:*controller
+[source, js]
 ----------------------------------
+event.dataset : "kubernetes.audit_logs"
+  and kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
+  and kubernetes.audit.verb : "create"
+  and kubernetes.audit.objectRef.resource : "pods"
+  and kubernetes.audit.objectRef.namespace : "kube-system"
+  and kubernetes.audit.requestObject.spec.serviceAccountName:*controller
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,18 +72,7 @@ kubernetes.audit.requestObject.spec.serviceAccountName:*controller
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[kubernetes-suspicious-assignment-of-controller-service-account-history]]
-==== Rule version history
-
-Version 3 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset : "kubernetes.audit_logs" and kubernetes.audit.verb :
-"create" and kubernetes.audit.objectRef.resource : "pods" and
-kubernetes.audit.objectRef.namespace : "kube-system" and
-kubernetes.audit.requestObject.spec.serviceAccountName:*controller
-----------------------------------
-
+* Sub-technique:
+** Name: Default Accounts
+** ID: T1078.001
+** Reference URL: https://attack.mitre.org/techniques/T1078/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-suspicious-self-subject-review.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-suspicious-self-subject-review.asciidoc
index 0a5a0cbafe..1f77df6b44 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-suspicious-self-subject-review.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-suspicious-self-subject-review.asciidoc
@@ -5,7 +5,7 @@ This rule detects when a service account or node attempts to enumerate their own
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,65 +13,55 @@ This rule detects when a service account or node attempts to enumerate their own
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.paloaltonetworks.com/apps/pan/public/downloadResource?pagePath=/content/pan/en_US/resources/whitepapers/kubernetes-privilege-escalation-excessive-permissions-in-popular-platforms
 * https://kubernetes.io/docs/reference/access-authn-authz/authorization/#checking-api-access
 * https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/detecting-identity-attacks-in-kubernetes/ba-p/3232340
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Discovery
-
-*Version*: 200 (<<kubernetes-suspicious-self-subject-review-history, version history>>)
+* Data Source: Kubernetes
+* Tactic: Discovery
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 203
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-An administrator may submit this request as an "impersonatedUser" to determine what privileges a particular service account has been granted. However, an adversary may utilize the same technique as a means to determine the privileges of another token other than that of the compromised account.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset : "kubernetes.audit_logs" and
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and kubernetes.audit.verb:"create" and
-kubernetes.audit.objectRef.resource:("selfsubjectaccessreviews" or
-"selfsubjectrulesreviews") and
-(kubernetes.audit.user.username:(system\:serviceaccount\:* or
-system\:node\:*) or
-kubernetes.audit.impersonatedUser.username:(system\:serviceaccount\:*
-or system\:node\:*))
+[source, js]
 ----------------------------------
+event.dataset : "kubernetes.audit_logs"
+  and kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
+  and kubernetes.audit.verb:"create"
+  and kubernetes.audit.objectRef.resource:("selfsubjectaccessreviews" or "selfsubjectrulesreviews")
+  and (kubernetes.audit.user.username:(system\:serviceaccount\:* or system\:node\:*)
+  or kubernetes.audit.impersonatedUser.username:(system\:serviceaccount\:* or system\:node\:*))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -83,35 +73,3 @@ or system\:node\:*))
 ** Name: Container and Resource Discovery
 ** ID: T1613
 ** Reference URL: https://attack.mitre.org/techniques/T1613/
-
-[[kubernetes-suspicious-self-subject-review-history]]
-==== Rule version history
-
-Version 200 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.verb:"create" and
-kubernetes.audit.objectRef.resource:("selfsubjectaccessreviews" or
-"selfsubjectrulesreviews") and
-kubernetes.audit.user.username:(system\:serviceaccount\:* or
-system\:node\:*) or
-kubernetes.audit.impersonatedUser.username:(system\:serviceaccount\:*
-or system\:node\:*)
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.verb:"create" and
-kubernetes.audit.objectRef.resource:("selfsubjectaccessreviews" or
-"selfsubjectrulesreviews") and
-kubernetes.audit.user.username:(system\:serviceaccount\:* or
-system\:node\:*) or
-kubernetes.audit.impersonatedUser.username:(system\:serviceaccount\:*
-or system\:node\:*)
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/kubernetes-user-exec-into-pod.asciidoc b/docs/detections/prebuilt-rules/rule-details/kubernetes-user-exec-into-pod.asciidoc
index 7d3218f133..5bbc870f48 100644
--- a/docs/detections/prebuilt-rules/rule-details/kubernetes-user-exec-into-pod.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/kubernetes-user-exec-into-pod.asciidoc
@@ -5,7 +5,7 @@ This rule detects a user attempt to establish a shell session into a pod using t
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-kubernetes.*
 
@@ -13,60 +13,53 @@ This rule detects a user attempt to establish a shell session into a pod using t
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://kubernetes.io/docs/tasks/debug/debug-application/debug-running-pod/
 * https://kubernetes.io/docs/tasks/debug/debug-application/get-shell-running-container/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Kubernetes
-* Continuous Monitoring
-* Execution
-
-*Version*: 200 (<<kubernetes-user-exec-into-pod-history, version history>>)
+* Data Source: Kubernetes
+* Tactic: Execution
 
-*Added ({stack} release)*: 8.3.0
+*Version*: 203
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-An administrator may need to exec into a pod for a legitimate reason like debugging purposes. Containers built from Linux and Windows OS images, tend to include debugging utilities. In this case, an admin may choose to run commands inside a specific container with kubectl exec ${POD_NAME} -c ${CONTAINER_NAME} -- ${CMD} ${ARG1} ${ARG2} ... ${ARGN}. For example, the following command can be used to look at logs from a running Cassandra pod: kubectl exec cassandra --cat /var/log/cassandra/system.log . Additionally, the -i and -t arguments might be used to run a shell connected to the terminal: kubectl exec -i -t cassandra -- sh
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Kubernetes Fleet integration with Audit Logs enabled or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset : "kubernetes.audit_logs" and
-kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
-and kubernetes.audit.verb:"create" and
-kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.objectRef.subresource:"exec"
+[source, js]
 ----------------------------------
+event.dataset : "kubernetes.audit_logs"
+  and kubernetes.audit.annotations.authorization_k8s_io/decision:"allow"
+  and kubernetes.audit.verb:"create"
+  and kubernetes.audit.objectRef.resource:"pods"
+  and kubernetes.audit.objectRef.subresource:"exec"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,35 +71,3 @@ kubernetes.audit.objectRef.subresource:"exec"
 ** Name: Container Administration Command
 ** ID: T1609
 ** Reference URL: https://attack.mitre.org/techniques/T1609/
-
-[[kubernetes-user-exec-into-pod-history]]
-==== Rule version history
-
-Version 200 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.objectRef.subresource:"exec"
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.objectRef.subresource:"exec"
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:"kubernetes.audit_logs" and
-kubernetes.audit.objectRef.resource:"pods" and
-kubernetes.audit.objectRef.subresource:"exec"
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/lateral-movement-via-startup-folder.asciidoc b/docs/detections/prebuilt-rules/rule-details/lateral-movement-via-startup-folder.asciidoc
index b1ecaefead..56be641950 100644
--- a/docs/detections/prebuilt-rules/rule-details/lateral-movement-via-startup-folder.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/lateral-movement-via-startup-folder.asciidoc
@@ -5,68 +5,74 @@ Identifies suspicious file creations in the startup folder of a remote system. A
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.file-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.mdsec.co.uk/2017/06/rdpinception/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-
-*Version*: 100 (<<lateral-movement-via-startup-folder-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type in ("creation", "change") and /* via RDP
-TSClient mounted share or SMB */ (process.name : "mstsc.exe" or
-process.pid == 4) and file.path :
-("?:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start
-Menu\\Programs\\Startup\\*",
-"?:\\ProgramData\\Microsoft\\Windows\\Start
-Menu\\Programs\\Startup\\*")
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type in ("creation", "change") and
 
-==== Threat mapping
+ /* via RDP TSClient mounted share or SMB */
+  (process.name : "mstsc.exe" or process.pid == 4) and
+
+   file.path : ("?:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\Startup\\*",
+                "?:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\Startup\\*")
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,8 +84,10 @@ Menu\\Programs\\Startup\\*")
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-
+* Sub-technique:
+** Name: Remote Desktop Protocol
+** ID: T1021.001
+** Reference URL: https://attack.mitre.org/techniques/T1021/001/
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -88,30 +96,7 @@ Menu\\Programs\\Startup\\*")
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[lateral-movement-via-startup-folder-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type in ("creation", "change") and /* via RDP
-TSClient mounted share or SMB */ (process.name : "mstsc.exe" or
-process.pid == 4) and file.path : "C:\\*\\Microsoft\\Windows\\Start
-Menu\\Programs\\Startup\\*"
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Registry Run Keys / Startup Folder
+** ID: T1547.001
+** Reference URL: https://attack.mitre.org/techniques/T1547/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/launch-agent-creation-or-modification-and-immediate-loading.asciidoc b/docs/detections/prebuilt-rules/rule-details/launch-agent-creation-or-modification-and-immediate-loading.asciidoc
index 5e7841a938..f15de7b68a 100644
--- a/docs/detections/prebuilt-rules/rule-details/launch-agent-creation-or-modification-and-immediate-loading.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/launch-agent-creation-or-modification-and-immediate-loading.asciidoc
@@ -5,60 +5,90 @@ An adversary can establish persistence by installing a new launch agent that exe
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<launch-agent-creation-or-modification-and-immediate-loading-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Trusted applications persisting via LaunchAgent
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=1m [file where event.type !=
-"deletion" and file.path : ("/System/Library/LaunchAgents/*",
-"/Library/LaunchAgents/*", "/Users/*/Library/LaunchAgents/*") ]
-[process where event.type in ("start", "process_started") and
-process.name == "launchctl" and process.args == "load"]
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=1m
+ [file where host.os.type == "macos" and event.type != "deletion" and
+  file.path : ("/System/Library/LaunchAgents/*", "/Library/LaunchAgents/*", "/Users/*/Library/LaunchAgents/*")
+ ]
+ [process where host.os.type == "macos" and event.type in ("start", "process_started") and process.name == "launchctl" and process.args == "load"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,25 +100,7 @@ process.name == "launchctl" and process.args == "load"]
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[launch-agent-creation-or-modification-and-immediate-loading-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=1m [file where event.type !=
-"deletion" and file.path : ("/System/Library/LaunchAgents/*",
-"/Library/LaunchAgents/*", "/Users/*/Library/LaunchAgents/*") ]
-[process where event.type in ("start", "process_started") and
-process.name == "launchctl" and process.args == "load"]
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Launch Agent
+** ID: T1543.001
+** Reference URL: https://attack.mitre.org/techniques/T1543/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/launchdaemon-creation-or-modification-and-immediate-loading.asciidoc b/docs/detections/prebuilt-rules/rule-details/launchdaemon-creation-or-modification-and-immediate-loading.asciidoc
index 7d6d6bee2a..a735e6a7ed 100644
--- a/docs/detections/prebuilt-rules/rule-details/launchdaemon-creation-or-modification-and-immediate-loading.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/launchdaemon-creation-or-modification-and-immediate-loading.asciidoc
@@ -5,60 +5,88 @@ Indicates the creation or modification of a launch daemon, which adversaries may
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<launchdaemon-creation-or-modification-and-immediate-loading-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.11.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
 
-==== Potential false positives
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Trusted applications persisting via LaunchDaemons
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=1m [file where event.type !=
-"deletion" and file.path : ("/System/Library/LaunchDaemons/*",
-"/Library/LaunchDaemons/*")] [process where event.type in ("start",
-"process_started") and process.name == "launchctl" and process.args ==
-"load"]
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=1m
+ [file where host.os.type == "macos" and event.type != "deletion" and file.path : ("/System/Library/LaunchDaemons/*", "/Library/LaunchDaemons/*")]
+ [process where host.os.type == "macos" and event.type in ("start", "process_started") and process.name == "launchctl" and process.args == "load"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,40 +98,3 @@ sequence by host.id with maxspan=1m [file where event.type !=
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[launchdaemon-creation-or-modification-and-immediate-loading-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=1m [file where event.type !=
-"deletion" and file.path in ("/System/Library/LaunchDaemons/*",
-"/Library/LaunchDaemons/*")] [process where event.type in ("start",
-"process_started") and process.name == "launchctl" and process.args ==
-"load"]
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=1m [file where event.type !=
-"deletion" and file.path in ("/System/Library/LaunchDaemons/*", "
-/Library/LaunchDaemons/*")] [process where event.type in ("start",
-"process_started") and process.name == "launchctl" and process.args ==
-"load"]
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/linux-group-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/linux-group-creation.asciidoc
new file mode 100644
index 0000000000..e4b8c9e299
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/linux-group-creation.asciidoc
@@ -0,0 +1,158 @@
+[[linux-group-creation]]
+=== Linux Group Creation
+
+Identifies attempts to create a new group. Attackers may create new groups to establish persistence on a system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-system.auth-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Linux Group Creation*
+
+
+The `groupadd` and `addgroup` commands are used to create new user groups in Linux-based operating systems.
+
+Attackers may create new groups to maintain access to victim systems or escalate privileges by assigning a compromised account to a privileged group.
+
+This rule identifies the usages of `groupadd` and `addgroup` to create new groups.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Investigate whether the group was created succesfully.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific Group","query":"SELECT * FROM groups WHERE groupname = {{group.name}}"}}
+- Identify if a user account was added to this group after creation.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Group creation is a common administrative task, so there is a high chance of the activity being legitimate. Before investigating further, verify that this activity is not benign.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
+- Delete the created group and, in case an account was added to this group, delete the account.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Filebeat.
+
+
+*Filebeat Setup*
+
+Filebeat is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to Elasticsearch or Logstash for indexing.
+
+
+*The following steps should be executed in order to add the Filebeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html[helper guide].
+- To run Filebeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-docker.html[helper guide].
+- To run Filebeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html[helper guide].
+- For quick start information for Filebeat refer to the https://www.elastic.co/guide/en/beats/filebeat/8.11/filebeat-installation-configuration.html[helper guide].
+- For complete “Setup and Run Filebeat” information refer to the https://www.elastic.co/guide/en/beats/filebeat/current/setting-up-and-running.html[helper guide].
+
+
+*Rule Specific Setup Note*
+
+- This rule requires the “Filebeat System Module” to be enabled.
+- The system module collects and parses logs created by the system logging service of common Unix/Linux based distributions.
+- To run the system module of Filebeat on Linux follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-system.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+iam where host.os.type == "linux" and (event.type == "group" and event.type == "creation") and
+process.name in ("groupadd", "addgroup") and group.name != null
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create Account
+** ID: T1136
+** Reference URL: https://attack.mitre.org/techniques/T1136/
+* Sub-technique:
+** Name: Local Account
+** ID: T1136.001
+** Reference URL: https://attack.mitre.org/techniques/T1136/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/linux-init-pid-1-secret-dump-via-gdb.asciidoc b/docs/detections/prebuilt-rules/rule-details/linux-init-pid-1-secret-dump-via-gdb.asciidoc
new file mode 100644
index 0000000000..ff15c88c54
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/linux-init-pid-1-secret-dump-via-gdb.asciidoc
@@ -0,0 +1,106 @@
+[[linux-init-pid-1-secret-dump-via-gdb]]
+=== Linux init (PID 1) Secret Dump via GDB
+
+This rule monitors for the potential memory dump of the init process (PID 1) through gdb. Attackers may leverage memory dumping techniques to attempt secret extraction from privileged processes. Tools that display this behavior include "truffleproc" and "bash-memory-dump". This behavior should not happen by default, and should be investigated thoroughly.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/controlplaneio/truffleproc
+* https://github.com/hajzer/bash-memory-dump
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and 
+process.name == "gdb" and process.args in ("--pid", "-p") and process.args == "1"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: Proc Filesystem
+** ID: T1003.007
+** Reference URL: https://attack.mitre.org/techniques/T1003/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/linux-process-hooking-via-gdb.asciidoc b/docs/detections/prebuilt-rules/rule-details/linux-process-hooking-via-gdb.asciidoc
new file mode 100644
index 0000000000..518fa87e65
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/linux-process-hooking-via-gdb.asciidoc
@@ -0,0 +1,74 @@
+[[linux-process-hooking-via-gdb]]
+=== Linux Process Hooking via GDB
+
+This rule monitors for potential memory dumping through gdb. Attackers may leverage memory dumping techniques to attempt secret extraction from privileged processes. Tools that display this behavior include "truffleproc" and "bash-memory-dump". This behavior should not happen by default, and should be investigated thoroughly.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/controlplaneio/truffleproc
+* https://github.com/hajzer/bash-memory-dump
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "gdb" and process.args in ("--pid", "-p") and 
+/* Covered by d4ff2f53-c802-4d2e-9fb9-9ecc08356c3f */
+process.args != "1"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: Proc Filesystem
+** ID: T1003.007
+** Reference URL: https://attack.mitre.org/techniques/T1003/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/linux-restricted-shell-breakout-via-linux-binary-s.asciidoc b/docs/detections/prebuilt-rules/rule-details/linux-restricted-shell-breakout-via-linux-binary-s.asciidoc
new file mode 100644
index 0000000000..b62203f6de
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/linux-restricted-shell-breakout-via-linux-binary-s.asciidoc
@@ -0,0 +1,245 @@
+[[linux-restricted-shell-breakout-via-linux-binary-s]]
+=== Linux Restricted Shell Breakout via Linux Binary(s)
+
+Identifies the abuse of a Linux binary to break out of a restricted shell or environment by spawning an interactive system shell. The activity of spawning a shell from a binary is not common behavior for a user or system administrator, and may indicate an attempt to evade detection, increase capabilities or enhance the stability of an adversary.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://gtfobins.github.io/gtfobins/apt/
+* https://gtfobins.github.io/gtfobins/apt-get/
+* https://gtfobins.github.io/gtfobins/nawk/
+* https://gtfobins.github.io/gtfobins/mawk/
+* https://gtfobins.github.io/gtfobins/awk/
+* https://gtfobins.github.io/gtfobins/gawk/
+* https://gtfobins.github.io/gtfobins/busybox/
+* https://gtfobins.github.io/gtfobins/c89/
+* https://gtfobins.github.io/gtfobins/c99/
+* https://gtfobins.github.io/gtfobins/cpulimit/
+* https://gtfobins.github.io/gtfobins/crash/
+* https://gtfobins.github.io/gtfobins/env/
+* https://gtfobins.github.io/gtfobins/expect/
+* https://gtfobins.github.io/gtfobins/find/
+* https://gtfobins.github.io/gtfobins/flock/
+* https://gtfobins.github.io/gtfobins/gcc/
+* https://gtfobins.github.io/gtfobins/mysql/
+* https://gtfobins.github.io/gtfobins/nice/
+* https://gtfobins.github.io/gtfobins/ssh/
+* https://gtfobins.github.io/gtfobins/vi/
+* https://gtfobins.github.io/gtfobins/vim/
+* https://gtfobins.github.io/gtfobins/capsh/
+* https://gtfobins.github.io/gtfobins/byebug/
+* https://gtfobins.github.io/gtfobins/git/
+* https://gtfobins.github.io/gtfobins/ftp/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 112
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Shell Evasion via Linux Utilities*
+
+Detection alerts from this rule indicate that a Linux utility has been abused to breakout of restricted shells or
+environments by spawning an interactive system shell.
+Here are some possible avenues of investigation:
+- Examine the entry point to the host and user in action via the Analyse View.
+  - Identify the session entry leader and session user
+- Examine the contents of session leading to the abuse via the Session View.
+  - Examine the command execution pattern in the session, which may lead to suspricous activities
+- Examine the execution of commands in the spawned shell.
+  - Identify imment threat to the system from the executed commands
+  - Take necessary incident response actions to contain any malicious behviour caused via this execution.
+
+
+*Related rules*
+
+
+- A malicious spawned shell can execute any of the possible MITTRE ATT&CK vectors mainly to impair defences.
+- Hence its adviced to enable defence evasion and privilige escalation rules accordingly in your environment
+
+
+*Response and remediation*
+
+
+Initiate the incident response process based on the outcome of the triage.
+
+- If the triage releaved suspicious netwrok activity from the malicious spawned shell,
+  - Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware execution via the maliciously spawned shell,
+  - Search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- If the triage revelaed defence evasion for imparing defenses
+  - Isolate the involved host to prevent further post-compromise behavior.
+  - Identified the disabled security guard components on the host and take necessary steps in renebaling the same.
+  - If any tools have been disbaled / uninstalled or config tampered work towards reenabling the same.
+- If the triage revelaed addition of persistence mechanism exploit like auto start scripts
+  - Isolate further login to the systems that can initae auto start scripts.
+  - Identify the auto start scripts and disable and remove the same from the systems
+- If the triage revealed data crawling or data export via remote copy
+  - Investigate credential exposure on systems compromised / used / decoded by the attacker during the data crawling
+  - Intiate compromised credential deactivation and credential rotation process for all exposed crednetials.
+  - Investiagte if any IPR data was accessed during the data crawling and take appropriate actions.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+Session View uses process data collected by the Elastic Defend integration, but this data is not always collected by default. Session View is available on enterprise subscription for versions 8.3 and above.
+
+*To confirm that Session View data is enabled:*
+
+- Go to “Manage → Policies”, and edit one or more of your Elastic Defend integration policies.
+- Select the” Policy settings” tab, then scroll down to the “Linux event collection” section near the bottom.
+- Check the box for “Process events”, and turn on the “Include session data” toggle.
+- If you want to include file and network alerts in Session View, check the boxes for “Network and File events”.
+- If you want to enable terminal output capture, turn on the “Capture terminal output” toggle.
+For more information about the additional fields collected when this setting is enabled and the usage of Session View for Analysis refer to the https://www.elastic.co/guide/en/security/current/session-view.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and
+(
+  /* launching shell from capsh */
+  (process.name == "capsh" and process.args == "--") or
+  
+  /* launching shells from unusual parents or parent+arg combos */
+  (process.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") and (
+    (process.parent.name : "*awk" and process.parent.args : "BEGIN {system(*)}") or
+    (process.parent.name == "git" and process.parent.args : ("*PAGER*", "!*sh", "exec *sh") or 
+     process.args : ("*PAGER*", "!*sh", "exec *sh") and not process.name == "ssh" ) or
+    (process.parent.name : ("byebug", "ftp", "strace", "zip", "tar") and 
+    (
+      process.parent.args : "BEGIN {system(*)}" or
+      (process.parent.args : ("*PAGER*", "!*sh", "exec *sh") or process.args : ("*PAGER*", "!*sh", "exec *sh")) or
+      (
+        (process.parent.args : "exec=*sh" or (process.parent.args : "-I" and process.parent.args : "*sh")) or
+        (process.args : "exec=*sh" or (process.args : "-I" and process.args : "*sh"))
+        )
+      )
+    ) or
+    
+    /* shells specified in parent args */
+    /* nice rule is broken in 8.2 */
+    (process.parent.args : "*sh" and
+      (
+        (process.parent.name == "nice") or
+        (process.parent.name == "cpulimit" and process.parent.args == "-f") or
+        (process.parent.name == "find" and process.parent.args == "." and process.parent.args == "-exec" and 
+         process.parent.args == ";" and process.parent.args : "/bin/*sh") or
+        (process.parent.name == "flock" and process.parent.args == "-u" and process.parent.args == "/")
+      )
+    )
+  )) or
+
+  /* shells specified in args */
+  (process.args : "*sh" and (
+    (process.parent.name == "crash" and process.parent.args == "-h") or
+    (process.name == "sensible-pager" and process.parent.name in ("apt", "apt-get") and process.parent.args == "changelog")
+    /* scope to include more sensible-pager invoked shells with different parent process to reduce noise and remove false positives */
+    
+  )) or
+  (process.name == "busybox" and event.action == "exec" and process.args_count == 2 and process.args : "*sh" and not 
+   process.executable : "/var/lib/docker/overlay2/*/merged/bin/busybox" and not (process.parent.args == "init" and
+   process.parent.args == "runc") and not process.parent.args in ("ls-remote", "push", "fetch") and not process.parent.name == "mkinitramfs") or
+  (process.name == "env" and process.args_count == 2 and process.args : "*sh") or
+  (process.parent.name in ("vi", "vim") and process.parent.args == "-c" and process.parent.args : ":!*sh") or
+  (process.parent.name in ("c89", "c99", "gcc") and process.parent.args : "*sh,-s" and process.parent.args == "-wrapper") or
+  (process.parent.name == "expect" and process.parent.args == "-c" and process.parent.args : "spawn *sh;interact") or
+  (process.parent.name == "mysql" and process.parent.args == "-e" and process.parent.args : "\\!*sh") or
+  (process.parent.name == "ssh" and process.parent.args == "-o" and process.parent.args : "ProxyCommand=;*sh 0<&2 1>&2")
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/linux-system-information-discovery.asciidoc b/docs/detections/prebuilt-rules/rule-details/linux-system-information-discovery.asciidoc
new file mode 100644
index 0000000000..45263a0d7d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/linux-system-information-discovery.asciidoc
@@ -0,0 +1,69 @@
+[[linux-system-information-discovery]]
+=== Linux System Information Discovery
+
+Enrich process events with uname and other command lines that imply Linux system information discovery.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started") and (
+  process.name: "uname" or (
+  process.name: ("cat", "more", "less") and process.args: ("*issue*", "*version*", "*profile*", "*services*", "*cpuinfo*")
+  )
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/linux-user-account-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/linux-user-account-creation.asciidoc
new file mode 100644
index 0000000000..54fbd48318
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/linux-user-account-creation.asciidoc
@@ -0,0 +1,157 @@
+[[linux-user-account-creation]]
+=== Linux User Account Creation
+
+Identifies attempts to create new users. Attackers may add new users to establish persistence on a system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-system.auth-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Linux User Account Creation*
+
+
+The `useradd` and `adduser` commands are used to create new user accounts in Linux-based operating systems.
+
+Attackers may create new accounts (both local and domain) to maintain access to victim systems.
+
+This rule identifies the usage of `useradd` and `adduser` to create new accounts.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Investigate whether the user was created succesfully.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Identify if the account was added to privileged groups or assigned special privileges after creation.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific Group","query":"SELECT * FROM groups WHERE groupname = {{group.name}}"}}
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Account creation is a common administrative task, so there is a high chance of the activity being legitimate. Before investigating further, verify that this activity is not benign.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
+- Delete the created account.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Filebeat.
+
+
+*Filebeat Setup*
+
+Filebeat is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to Elasticsearch or Logstash for indexing.
+
+
+*The following steps should be executed in order to add the Filebeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html[helper guide].
+- To run Filebeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-docker.html[helper guide].
+- To run Filebeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html[helper guide].
+- For quick start information for Filebeat refer to the https://www.elastic.co/guide/en/beats/filebeat/8.11/filebeat-installation-configuration.html[helper guide].
+- For complete “Setup and Run Filebeat” information refer to the https://www.elastic.co/guide/en/beats/filebeat/current/setting-up-and-running.html[helper guide].
+
+
+*Rule Specific Setup Note*
+
+- This rule requires the “Filebeat System Module” to be enabled.
+- The system module collects and parses logs created by the system logging service of common Unix/Linux based distributions.
+- To run the system module of Filebeat on Linux follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-system.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+iam where host.os.type == "linux" and (event.type == "user" and event.type == "creation") and
+process.name in ("useradd", "adduser") and user.name != null
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create Account
+** ID: T1136
+** Reference URL: https://attack.mitre.org/techniques/T1136/
+* Sub-technique:
+** Name: Local Account
+** ID: T1136.001
+** Reference URL: https://attack.mitre.org/techniques/T1136/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/linux-user-added-to-privileged-group.asciidoc b/docs/detections/prebuilt-rules/rule-details/linux-user-added-to-privileged-group.asciidoc
new file mode 100644
index 0000000000..395357913a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/linux-user-added-to-privileged-group.asciidoc
@@ -0,0 +1,174 @@
+[[linux-user-added-to-privileged-group]]
+=== Linux User Added to Privileged Group
+
+Identifies attempts to add a user to a privileged group. Attackers may add users to a privileged group in order to establish persistence on a system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Linux User User Added to Privileged Group*
+
+
+The `usermod`, `adduser`, and `gpasswd` commands can be used to assign user accounts to new groups in Linux-based operating systems.
+
+Attackers may add users to a privileged group in order to escalate privileges or establish persistence on a system or domain.
+
+This rule identifies the usages of `usermod`, `adduser` and `gpasswd` to assign user accounts to a privileged group.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Investigate whether the user was succesfully added to the privileged group.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Retrieve information about the privileged group to which the user was added.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific Group","query":"SELECT * FROM groups WHERE groupname = {{group.name}}"}}
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Adding accounts to a group is a common administrative task, so there is a high chance of the activity being legitimate. Before investigating further, verify that this activity is not benign.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
+- Delete the account that seems to be involved in malicious activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.args in (
+  "root", "admin", "wheel", "staff", "sudo","disk", "video", "shadow", "lxc", "lxd"
+) and
+(
+  process.name in ("usermod", "adduser") or
+  process.name == "gpasswd" and 
+  process.args in ("-a", "--add", "-M", "--members") 
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create Account
+** ID: T1136
+** Reference URL: https://attack.mitre.org/techniques/T1136/
+* Sub-technique:
+** Name: Local Account
+** ID: T1136.001
+** Reference URL: https://attack.mitre.org/techniques/T1136/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/local-account-tokenfilter-policy-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/local-account-tokenfilter-policy-disabled.asciidoc
index 6d1918c626..e95c4a0f7c 100644
--- a/docs/detections/prebuilt-rules/rule-details/local-account-tokenfilter-policy-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/local-account-tokenfilter-policy-disabled.asciidoc
@@ -5,59 +5,60 @@ Identifies registry modification to the LocalAccountTokenFilterPolicy policy. If
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.stigviewer.com/stig/windows_server_2008_r2_member_server/2014-04-02/finding/V-36439
 * https://posts.specterops.io/pass-the-hash-is-dead-long-live-localaccounttokenfilterpolicy-506c25a7c167
 * https://www.welivesecurity.com/wp-content/uploads/2018/01/ESET_Turla_Mosquito.pdf
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Privilege Escalation
-* Elastic Endgame
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Lateral Movement
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Version*: 1
+*Version*: 8
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.path : (
-"HKLM\\*\\LocalAccountTokenFilterPolicy",
-"\\REGISTRY\\MACHINE\\*\\LocalAccountTokenFilterPolicy") and
-registry.data.strings : ("1", "0x00000001")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and registry.path : (
+  "HKLM\\*\\LocalAccountTokenFilterPolicy",
+  "\\REGISTRY\\MACHINE\\*\\LocalAccountTokenFilterPolicy") and
+  registry.data.strings : ("1", "0x00000001")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -69,13 +70,19 @@ registry.data.strings : ("1", "0x00000001")
 ** Name: Modify Registry
 ** ID: T1112
 ** Reference URL: https://attack.mitre.org/techniques/T1112/
-
-
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
 * Tactic:
-** Name: Privilege Escalation
-** ID: TA0004
-** Reference URL: https://attack.mitre.org/tactics/TA0004/
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
 * Technique:
-** Name: Valid Accounts
-** ID: T1078
-** Reference URL: https://attack.mitre.org/techniques/T1078/
+** Name: Use Alternate Authentication Material
+** ID: T1550
+** Reference URL: https://attack.mitre.org/techniques/T1550/
+* Sub-technique:
+** Name: Pass the Hash
+** ID: T1550.002
+** Reference URL: https://attack.mitre.org/techniques/T1550/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/local-scheduled-task-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/local-scheduled-task-creation.asciidoc
index cbf64342fc..4565fb7cc3 100644
--- a/docs/detections/prebuilt-rules/rule-details/local-scheduled-task-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/local-scheduled-task-creation.asciidoc
@@ -5,75 +5,66 @@ Indicates the creation of a scheduled task. Adversaries can use these to establi
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/security-labs/hunting-for-persistence-using-elastic-security-part-1
 * https://www.elastic.co/security-labs/hunting-for-persistence-using-elastic-security-part-2
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 101 (<<local-scheduled-task-creation-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Legitimate scheduled tasks may be created during installation of new software.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence with maxspan=1m [process where event.type != "end" and
-((process.name : ("cmd.exe", "wscript.exe", "rundll32.exe",
-"regsvr32.exe", "wmic.exe", "mshta.exe",
-"powershell.exe", "pwsh.exe", "powershell_ise.exe", "WmiPrvSe.exe",
-"wsmprovhost.exe", "winrshost.exe") or
-process.pe.original_file_name : ("cmd.exe", "wscript.exe",
-"rundll32.exe", "regsvr32.exe", "wmic.exe", "mshta.exe",
-"powershell.exe", "pwsh.dll", "powershell_ise.exe", "WmiPrvSe.exe",
-"wsmprovhost.exe",
-"winrshost.exe")) or process.code_signature.trusted == false)] by
-process.entity_id [process where event.type == "start" and
-(process.name : "schtasks.exe" or process.pe.original_file_name ==
-"schtasks.exe") and process.args : ("/create", "-create") and
-process.args : ("/RU", "/SC", "/TN", "/TR", "/F", "/XML") and /*
-exclude SYSTEM Integrity Level - look for task creations by non-SYSTEM
-user */ not (?process.Ext.token.integrity_level_name : "System" or
-?winlog.event_data.IntegrityLevel : "System") ] by
-process.parent.entity_id
+[source, js]
 ----------------------------------
+sequence with maxspan=1m
+  [process where host.os.type == "windows" and event.type != "end" and
+    ((process.name : ("cmd.exe", "wscript.exe", "rundll32.exe", "regsvr32.exe", "wmic.exe", "mshta.exe",
+                      "powershell.exe", "pwsh.exe", "powershell_ise.exe", "WmiPrvSe.exe", "wsmprovhost.exe", "winrshost.exe") or
+    process.pe.original_file_name : ("cmd.exe", "wscript.exe", "rundll32.exe", "regsvr32.exe", "wmic.exe", "mshta.exe",
+                                     "powershell.exe", "pwsh.dll", "powershell_ise.exe", "WmiPrvSe.exe", "wsmprovhost.exe",
+                                     "winrshost.exe")) or
+    ?process.code_signature.trusted == false)] by process.entity_id
+  [process where host.os.type == "windows" and event.type == "start" and
+    (process.name : "schtasks.exe" or process.pe.original_file_name == "schtasks.exe") and
+    process.args : ("/create", "-create") and process.args : ("/RU", "/SC", "/TN", "/TR", "/F", "/XML") and
+    /* exclude SYSTEM Integrity Level - look for task creations by non-SYSTEM user */
+    not (?process.Ext.token.integrity_level_name : "System" or ?winlog.event_data.IntegrityLevel : "System")
+  ] by process.parent.entity_id
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -85,132 +76,7 @@ process.parent.entity_id
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[local-scheduled-task-creation-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 13 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1m [process where event.type != "end" and
-((process.name : ("cmd.exe", "wscript.exe", "rundll32.exe",
-"regsvr32.exe", "wmic.exe", "mshta.exe",
-"powershell.exe", "pwsh.exe", "powershell_ise.exe", "WmiPrvSe.exe",
-"wsmprovhost.exe", "winrshost.exe") or
-process.pe.original_file_name : ("cmd.exe", "wscript.exe",
-"rundll32.exe", "regsvr32.exe", "wmic.exe", "mshta.exe",
-"powershell.exe", "pwsh.dll", "powershell_ise.exe", "WmiPrvSe.exe",
-"wsmprovhost.exe",
-"winrshost.exe")) or process.code_signature.trusted == false)] by
-process.entity_id [process where event.type == "start" and
-(process.name : "schtasks.exe" or process.pe.original_file_name ==
-"schtasks.exe") and process.args : ("/create", "-create") and
-process.args : ("/RU", "/SC", "/TN", "/TR", "/F", "/XML") and /*
-exclude SYSTEM Integrity Level - look for task creations by non-SYSTEM
-user */ not (process.Ext.token.integrity_level_name : "System" or
-winlog.event_data.IntegrityLevel : "System") ] by
-process.parent.entity_id
-----------------------------------
-
-Version 10 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1m [process where event.type != "end" and
-((process.name : ("cmd.exe", "wscript.exe", "rundll32.exe",
-"regsvr32.exe", "wmic.exe", "mshta.exe",
-"powershell.exe", "pwsh.exe", "powershell_ise.exe", "WmiPrvSe.exe",
-"wsmprovhost.exe", "winrshost.exe") or
-process.pe.original_file_name : ("cmd.exe", "wscript.exe",
-"rundll32.exe", "regsvr32.exe", "wmic.exe", "mshta.exe",
-"powershell.exe", "pwsh.dll", "powershell_ise.exe", "WmiPrvSe.exe",
-"wsmprovhost.exe",
-"winrshost.exe")) or process.code_signature.trusted == false)] by
-process.entity_id [process where event.type == "start" and
-(process.name : "schtasks.exe" or process.pe.original_file_name ==
-"schtasks.exe") and process.args : ("/create", "-create") and
-process.args : ("/RU", "/SC", "/TN", "/TR", "/F", "/XML") and /*
-exclude SYSTEM SIDs - look for task creations by non-SYSTEM user */
-not user.id : ("S-1-5-18", "S-1-5-19", "S-1-5-20")] by
-process.parent.entity_id
-----------------------------------
-
-Version 9 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1m [process where event.type != "end" and
-((process.name : ("cmd.exe", "wscript.exe", "rundll32.exe",
-"regsvr32.exe", "wmic.exe", "mshta.exe",
-"powershell.exe", "pwsh.exe", "WmiPrvSe.exe", "wsmprovhost.exe",
-"winrshost.exe") or process.pe.original_file_name : ("cmd.exe",
-"wscript.exe", "rundll32.exe", "regsvr32.exe", "wmic.exe",
-"mshta.exe", "powershell.exe",
-"pwsh.exe", "WmiPrvSe.exe", "wsmprovhost.exe",
-"winrshost.exe")) or process.code_signature.trusted == false)] by
-process.entity_id [process where event.type == "start" and
-(process.name : "schtasks.exe" or process.pe.original_file_name ==
-"schtasks.exe") and process.args : ("/create", "-create") and
-process.args : ("/RU", "/SC", "/TN", "/TR", "/F", "/XML") and /*
-exclude SYSTEM SIDs - look for task creations by non-SYSTEM user */
-not user.id : ("S-1-5-18", "S-1-5-19", "S-1-5-20")] by
-process.parent.entity_id
-----------------------------------
-
-Version 8 (7.13.0 release)::
-* Rule name changed from: Local Scheduled Task Commands
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:schtasks.exe and process.args:(-change or -create or -run
-or -s or /S or /change or /create or /run)
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:schtasks.exe and process.args:(-change or -create or -run
-or -s or /S or /change or /create or /run)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:schtasks.exe and process.args:("/create" or "-create" or
-"/S" or "-s" or "/run" or "-run" or "/change" or "-change")
-----------------------------------
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/lsass-memory-dump-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/lsass-memory-dump-creation.asciidoc
index 719f4f8438..8bcea6f2f3 100644
--- a/docs/detections/prebuilt-rules/rule-details/lsass-memory-dump-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/lsass-memory-dump-creation.asciidoc
@@ -5,125 +5,168 @@ Identifies the creation of a Local Security Authority Subsystem Service (lsass.e
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/outflanknl/Dumpert
 * https://github.com/hoangprod/AndrewSpecial
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Elastic Endgame
-
-*Version*: 101 (<<lsass-memory-dump-creation-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating LSASS Memory Dump Creation*
 
-[source,js]
-----------------------------------
-file where file.name : ("lsass*.dmp", "dumpert.dmp", "Andrew.dmp",
-"SQLDmpr*.mdmp", "Coredump.dmp") and not (process.executable :
-("?:\\Program Files\\Microsoft SQL Server\\*\\Shared\\SqlDumper.exe",
-"?:\\Windows\\System32\\dllhost.exe") and file.path :
-("?:\\Program Files\\Microsoft SQL
-Server\\*\\Shared\\ErrorDumps\\SQLDmpr*.mdmp",
-"?:\\*\\Reporting Services\\Logfiles\\SQLDmpr*.mdmp")) and not
-(process.executable : "?:\\WINDOWS\\system32\\WerFault.exe" and
-file.path : "?:\\Windows\\System32\\config\\systemprofile\\AppData\\Lo
-cal\\CrashDumps\\lsass.exe.*.dmp")
-----------------------------------
 
-==== Threat mapping
+Local Security Authority Server Service (LSASS) is a process in Microsoft Windows operating systems that is responsible for enforcing security policy on the system. It verifies users logging on to a Windows computer or server, handles password changes, and creates access tokens.
 
-*Framework*: MITRE ATT&CK^TM^
+This rule looks for the creation of memory dump files with file names compatible with credential dumping tools or that start with `lsass`.
 
-* Tactic:
-** Name: Credential Access
-** ID: TA0006
-** Reference URL: https://attack.mitre.org/tactics/TA0006/
-* Technique:
-** Name: OS Credential Dumping
-** ID: T1003
-** Reference URL: https://attack.mitre.org/techniques/T1003/
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-[[lsass-memory-dump-creation-history]]
-==== Rule version history
 
-Version 101 (8.6.0 release)::
-* Formatting only
+*Possible investigation steps*
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 11 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where file.name : ("lsass*.dmp", "dumpert.dmp", "Andrew.dmp",
-"SQLDmpr*.mdmp", "Coredump.dmp")
-----------------------------------
+- Identify the process responsible for creating the dump file.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
+
 
-Version 9 (8.3.0 release)::
-* Formatting only
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
 
-Version 7 (8.2.0 release)::
-* Formatting only
 
-Version 5 (7.16.0 release)::
-* Formatting only
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
 
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.category:file and file.name:(lsass.DMP or lsass*.dmp or
-dumpert.dmp or Andrew.dmp or SQLDmpr*.mdmp or Coredump.dmp)
-----------------------------------
+file where host.os.type == "windows" and event.action != "deletion" and
+  file.name : ("lsass*.dmp", "dumpert.dmp", "Andrew.dmp", "SQLDmpr*.mdmp", "Coredump.dmp") and
+
+  not (
+        process.executable : (
+          "?:\\Program Files\\Microsoft SQL Server\\*\\Shared\\SqlDumper.exe",
+          "?:\\Windows\\System32\\dllhost.exe"
+        ) and
+        file.path : (
+          "?:\\*\\Reporting Services\\Logfiles\\SQLDmpr*.mdmp",
+          "?:\\Program Files\\Microsoft SQL Server\\*\\Shared\\ErrorDumps\\SQLDmpr*.mdmp",
+          "?:\\Program Files\\Microsoft SQL Server\\*\\MSSQL\\LOG\\SQLDmpr*.mdmp"
+        )
+      ) and
+
+  not (
+        process.executable : "?:\\Windows\\system32\\WerFault.exe" and
+        file.path : (
+          "?:\\Windows\\System32\\config\\systemprofile\\AppData\\Local\\CrashDumps\\lsass.exe.*.dmp",
+          "?:\\Windows\\System32\\%LOCALAPPDATA%\\CrashDumps\\lsass.exe.*.dmp"
+        )
+  )
 
-Version 3 (7.12.0 release)::
-* Formatting only
+----------------------------------
 
-Version 2 (7.11.2 release)::
-* Formatting only
+*Framework*: MITRE ATT&CK^TM^
 
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/lsass-memory-dump-handle-access.asciidoc b/docs/detections/prebuilt-rules/rule-details/lsass-memory-dump-handle-access.asciidoc
index a2b84fe3bf..19fc7982c9 100644
--- a/docs/detections/prebuilt-rules/rule-details/lsass-memory-dump-handle-access.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/lsass-memory-dump-handle-access.asciidoc
@@ -5,22 +5,23 @@ Identifies handle requests for the Local Security Authority Subsystem Service (L
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4656
 * https://twitter.com/jsecurity101/status/1227987828534956033?s=20
@@ -29,78 +30,73 @@ Identifies handle requests for the Local Security Authority Subsystem Service (L
 * http://findingbad.blogspot.com/2017/
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
-
-*Version*: 102 (<<lsass-memory-dump-handle-access-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
 
-*Added ({stack} release)*: 8.2.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating LSASS Memory Dump Handle Access
+*Triage and analysis*
+
+
+
+*Investigating LSASS Memory Dump Handle Access*
+
 
-Local Security Authority Server Service (LSASS) is a process in Microsoft Windows operating systems that is responsible
-for enforcing security policy on the system. It verifies users logging on to a Windows computer or server, handles
-password changes, and creates access tokens.
+Local Security Authority Server Service (LSASS) is a process in Microsoft Windows operating systems that is responsible for enforcing security policy on the system. It verifies users logging on to a Windows computer or server, handles password changes, and creates access tokens.
 
-Adversaries may attempt to access credential material stored in LSASS process memory. After a user logs on,the system
-generates and stores a variety of credential materials in LSASS process memory. This is meant to facilitate single
-sign-on (SSO) ensuring a user isn’t prompted each time resource access is requested. These credential materials can be
-harvested by an adversary using administrative user or SYSTEM privileges to conduct lateral movement using
-[alternate authentication material](https://attack.mitre.org/techniques/T1550/).
+Adversaries may attempt to access credential material stored in LSASS process memory. After a user logs on, the system generates and stores a variety of credential materials in LSASS process memory. This is meant to facilitate single sign-on (SSO) ensuring a user isn’t prompted each time resource access is requested. These credential materials can be harvested by an adversary using administrative user or SYSTEM privileges to conduct lateral movement using https://attack.mitre.org/techniques/T1550/[alternate authentication material].
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+
+*False positive analysis*
 
 
-### False positive analysis
+- There should be very few or no false positives for this rule. If this activity is expected or noisy in your environment, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If the process is related to antivirus or endpoint detection and response solutions, validate that it is installed on the correct path and signed with the company's valid digital signature.
 
-- There should be very few or no false positives for this rule. If this activity is expected or noisy in your environment,
-consider adding exceptions — preferably with a combination of user and command line conditions.
-- If the process is related to antivirus or endpoint detection and response solutions, validate that it is installed on
-the correct path and signed with the company's valid digital signature.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -109,20 +105,23 @@ the correct path and signed with the company's valid digital signature.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
 
 Ensure advanced audit policies for Windows are enabled, specifically:
-Object Access policies [Event ID 4656](https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4656) (Handle to an Object was Requested)
+Object Access policies https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4656[Event ID 4656] (Handle to an Object was Requested)
 
 ```
 Computer Configuration >
@@ -136,38 +135,46 @@ Audit File System (Success,Failure)
 Audit Handle Manipulation (Success,Failure)
 ```
 
-Also, this event generates only if the object’s [SACL](https://docs.microsoft.com/en-us/windows/win32/secauthz/access-control-lists) has the required access control entry (ACE) to handle the use of specific access rights.
+Also, this event generates only if the object’s https://docs.microsoft.com/en-us/windows/win32/secauthz/access-control-lists[SACL] has the required access control entry (ACE) to handle the use of specific access rights.
 
-If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define `event.ingested` and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate `event.ingested` to @timestamp for this rule to work.
-----------------------------------
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 any where event.action == "File System" and event.code == "4656" and
-winlog.event_data.ObjectName : (
-"?:\\Windows\\System32\\lsass.exe",
-"\\Device\\HarddiskVolume?\\Windows\\System32\\lsass.exe",
-"\\Device\\HarddiskVolume??\\Windows\\System32\\lsass.exe") and
-/* The right to perform an operation controlled by an extended access
-right. */ (winlog.event_data.AccessMask : ("0x1fffff" , "0x1010",
-"0x120089", "0x1F3FFF") or
-winlog.event_data.AccessMaskDescription : ("READ_CONTROL", "Read from
-process memory")) /* Common Noisy False Positives */ and
-not winlog.event_data.ProcessName : ( "?:\\Program
-Files\\*.exe", "?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\system32\\wbem\\WmiPrvSE.exe",
-"?:\\Windows\\System32\\dllhost.exe",
-"?:\\Windows\\System32\\svchost.exe",
-"?:\\Windows\\System32\\msiexec.exe",
-"?:\\ProgramData\\Microsoft\\Windows Defender\\*.exe",
-"?:\\Windows\\explorer.exe")
-----------------------------------
 
-==== Threat mapping
+    winlog.event_data.ObjectName : (
+        "?:\\Windows\\System32\\lsass.exe",
+        "\\Device\\HarddiskVolume?\\Windows\\System32\\lsass.exe",
+        "\\Device\\HarddiskVolume??\\Windows\\System32\\lsass.exe") and
+
+    /* The right to perform an operation controlled by an extended access right. */
+
+    (winlog.event_data.AccessMask : ("0x1fffff" , "0x1010", "0x120089", "0x1F3FFF") or
+     winlog.event_data.AccessMaskDescription : ("READ_CONTROL", "Read from process memory"))
+
+     /* Common Noisy False Positives */
+
+    and not winlog.event_data.ProcessName : (
+        "?:\\Program Files\\*.exe",
+        "?:\\Program Files (x86)\\*.exe",
+        "?:\\Windows\\system32\\wbem\\WmiPrvSE.exe",
+        "?:\\Windows\\System32\\dllhost.exe",
+        "?:\\Windows\\System32\\svchost.exe",
+        "?:\\Windows\\System32\\msiexec.exe",
+        "?:\\ProgramData\\Microsoft\\Windows Defender\\*.exe",
+        "?:\\Windows\\explorer.exe",
+        "?:\\Windows\\System32\\poqexec.exe")
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -179,19 +186,7 @@ Files\\*.exe", "?:\\Program Files (x86)\\*.exe",
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[lsass-memory-dump-handle-access-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.3.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/lsass-process-access-via-windows-api.asciidoc b/docs/detections/prebuilt-rules/rule-details/lsass-process-access-via-windows-api.asciidoc
new file mode 100644
index 0000000000..9d773da84a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/lsass-process-access-via-windows-api.asciidoc
@@ -0,0 +1,195 @@
+[[lsass-process-access-via-windows-api]]
+=== LSASS Process Access via Windows API
+
+Identifies access attempts to the LSASS handle, which may indicate an attempt to dump credentials from LSASS memory.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.api-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1003.001/T1003.001.md
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating LSASS Process Access via Windows API*
+
+
+The Local Security Authority Subsystem Service (LSASS) is a critical Windows component responsible for managing user authentication and security policies. Adversaries may attempt to access the LSASS handle to dump credentials from its memory, which can be used for lateral movement and privilege escalation.
+
+This rule identifies attempts to access LSASS by monitoring for specific API calls (OpenProcess, OpenThread) targeting the "lsass.exe" process.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate the process execution chain (parent process tree) of the process that accessed the LSASS handle.
+  - Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - Determine the first time the process executable was seen in the environment and if this behavior happened in the past.
+  - Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+  - Investigate any abnormal behavior by the subject process, such as network connections, DLLs loaded, registry or file modifications, and any spawned child processes.
+- Assess the access rights (`process.Ext.api.parameters.desired_access`field) requested by the process. This https://learn.microsoft.com/en-us/windows/win32/procthread/process-security-and-access-rights[Microsoft documentation] may be useful to help the interpretation.
+- If there are traces of LSASS memory being successfully dumped, investigate potentially compromised accounts. Analysts can do this by searching for login events (e.g., 4624) to the target host.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the executables of the processes using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+
+*False positive analysis*
+
+
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of `process.executable`, `process.code_signature.subject_name` and `process.Ext.api.parameters.desired_access_numeric` conditions.
+
+
+*Related Rules*
+
+
+- Suspicious Lsass Process Access - 128468bf-cab1-4637-99ea-fdf3780a4609
+- Potential Credential Access via DuplicateHandle in LSASS - 02a4576a-7480-4284-9327-548a806b5e48
+- LSASS Memory Dump Handle Access - 208dbe77-01ed-4954-8d44-1e5751cb20de
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+  - If malicious activity is confirmed, perform a broader investigation to identify the scope of the compromise and determine the appropriate remediation steps.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Reimage the host operating system or restore the compromised files to clean versions.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+api where host.os.type == "windows" and 
+  process.Ext.api.name in ("OpenProcess", "OpenThread") and Target.process.name : "lsass.exe" and 
+  not 
+  (
+    process.executable : (
+        "?:\\ProgramData\\GetSupportService*\\Updates\\Update_*.exe",
+        "?:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\*\\MsMpEng.exe",
+        "?:\\Program Files (x86)\\Asiainfo Security\\OfficeScan Client\\NTRTScan.exe",
+        "?:\\Program Files (x86)\\Blackpoint\\SnapAgent\\SnapAgent.exe",
+        "?:\\Program Files (x86)\\eScan\\reload.exe",
+        "?:\\Program Files (x86)\\Google\\Update\\GoogleUpdate.exe",
+        "?:\\Program Files (x86)\\Kaspersky Lab\\*\\avp.exe",
+        "?:\\Program Files (x86)\\N-able Technologies\\Reactive\\bin\\NableReactiveManagement.exe",
+        "?:\\Program Files (x86)\\N-able Technologies\\Windows Agent\\bin\\agent.exe",
+        "?:\\Program Files (x86)\\Trend Micro\\*\\CCSF\\TmCCSF.exe",
+        "?:\\Program Files*\\Windows Defender\\MsMpEng.exe",
+        "?:\\Program Files\\Bitdefender\\Endpoint Security\\EPSecurityService.exe",
+        "?:\\Program Files\\Cisco\\AMP\\*\\sfc.exe",
+        "?:\\Program Files\\Common Files\\McAfee\\AVSolution\\mcshield.exe",
+        "?:\\Program Files\\EA\\AC\\EAAntiCheat.GameService.exe",
+        "?:\\Program Files\\Elastic\\Agent\\data\\elastic-agent-*\\components\\metricbeat.exe",
+        "?:\\Program Files\\Elastic\\Agent\\data\\elastic-agent-*\\components\\osqueryd.exe",
+        "?:\\Program Files\\Elastic\\Agent\\data\\elastic-agent-*\\components\\packetbeat.exe",
+        "?:\\Program Files\\ESET\\ESET Security\\ekrn.exe",
+        "?:\\Program Files\\Fortinet\\FortiClient\\FortiProxy.exe",
+        "?:\\Program Files\\Huntress\\HuntressAgent.exe",
+        "?:\\Program Files\\LogicMonitor\\Agent\\bin\\sbshutdown.exe",
+        "?:\\Program Files\\Microsoft Security Client\\MsMpEng.exe",
+        "?:\\Program Files\\Qualys\\QualysAgent\\QualysAgent.exe",
+        "?:\\Program Files\\TDAgent\\ossec-agent\\ossec-agent.exe",
+        "?:\\Program Files\\Topaz OFD\\Warsaw\\core.exe",
+        "?:\\Program Files\\VMware\\VMware Tools\\vmtoolsd.exe",
+        "?:\\Windows\\AdminArsenal\\PDQDeployRunner\\*\\exec\\Sysmon64.exe",
+        "?:\\Windows\\Sysmon.exe",
+        "?:\\Windows\\Sysmon64.exe",
+        "?:\\Windows\\System32\\csrss.exe",
+        "?:\\Windows\\System32\\MRT.exe",
+        "?:\\Windows\\System32\\msiexec.exe",
+        "?:\\Windows\\System32\\RtkAudUService64.exe",
+        "?:\\Windows\\System32\\wbem\\WmiPrvSE.exe",
+        "?:\\Windows\\SysWOW64\\wbem\\WmiPrvSE.exe"
+    ) and process.code_signature.trusted == true
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Native API
+** ID: T1106
+** Reference URL: https://attack.mitre.org/techniques/T1106/
diff --git a/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-dns-request-predicted-to-be-a-dga-domain.asciidoc b/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-dns-request-predicted-to-be-a-dga-domain.asciidoc
new file mode 100644
index 0000000000..e0c48c1aca
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-dns-request-predicted-to-be-a-dga-domain.asciidoc
@@ -0,0 +1,132 @@
+[[machine-learning-detected-a-dns-request-predicted-to-be-a-dga-domain]]
+=== Machine Learning Detected a DNS Request Predicted to be a DGA Domain
+
+A supervised machine learning model has identified a DNS question name that is predicted to be the result of a Domain Generation Algorithm (DGA), which could indicate command and control network activity.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* logs-network_traffic.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-10m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/dga
+* https://www.elastic.co/security-labs/detect-domain-generation-algorithm-activity-with-new-kibana-integration
+
+*Tags*: 
+
+* Domain: Network
+* Domain: Endpoint
+* Data Source: Elastic Defend
+* Use Case: Domain Generation Algorithm Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Command and Control
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Domain Generation Algorithm (DGA) Detection integration assets to be installed, as well as DNS events collected by integrations such as Elastic Defend, Network Packet Capture, or Packetbeat.  
+
+
+*DGA Detection Setup*
+
+The DGA Detection integration consists of an ML-based framework to detect DGA activity in DNS events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for DGA Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- DNS events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend], https://docs.elastic.co/integrations/network_traffic[Network Packet Capture] integration, or https://www.elastic.co/guide/en/beats/packetbeat/current/packetbeat-overview.html[Packetbeat].
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To add the Network Packet Capture integration to an Elastic Agent policy, refer to https://www.elastic.co/guide/en/fleet/current/add-integration-to-policy.html[this] guide.
+- To set up and run Packetbeat, follow https://www.elastic.co/guide/en/beats/packetbeat/current/setting-up-and-running.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the DGA Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Domain Generation Algorithm Detection and select the integration to see more details about it.
+- Under Settings, click Install Domain Generation Algorithm Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+Before you can enable this rule, you'll need to enrich DNS events with predictions from the Supervised DGA Detection model. This is done via the ingest pipeline named `<package_version>-ml_dga_ingest_pipeline` installed with the DGA Detection package.
+- If using an Elastic Beat such as Packetbeat, add the DGA ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `packetbeat.yml`.
+- If adding the DGA ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the DGA ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "ml_is_dga": {
+      "properties": {
+        "malicious_prediction": {
+          "type": "long"
+        },
+        "malicious_probability": {
+          "type": "float"
+        }
+      }
+    }
+  }
+}
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+ml_is_dga.malicious_prediction:1 and not dns.question.registered_domain:avsvmcloud.com
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Dynamic Resolution
+** ID: T1568
+** Reference URL: https://attack.mitre.org/techniques/T1568/
+* Sub-technique:
+** Name: Domain Generation Algorithms
+** ID: T1568.002
+** Reference URL: https://attack.mitre.org/techniques/T1568/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-dns-request-with-a-high-dga-probability-score.asciidoc b/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-dns-request-with-a-high-dga-probability-score.asciidoc
new file mode 100644
index 0000000000..e19070ebe9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-dns-request-with-a-high-dga-probability-score.asciidoc
@@ -0,0 +1,132 @@
+[[machine-learning-detected-a-dns-request-with-a-high-dga-probability-score]]
+=== Machine Learning Detected a DNS Request With a High DGA Probability Score
+
+A supervised machine learning model has identified a DNS question name with a high probability of sourcing from a Domain Generation Algorithm (DGA), which could indicate command and control network activity.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* logs-network_traffic.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-10m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/dga
+* https://www.elastic.co/security-labs/detect-domain-generation-algorithm-activity-with-new-kibana-integration
+
+*Tags*: 
+
+* Domain: Network
+* Domain: Endpoint
+* Data Source: Elastic Defend
+* Use Case: Domain Generation Algorithm Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Command and Control
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Domain Generation Algorithm (DGA) Detection integration assets to be installed, as well as DNS events collected by integrations such as Elastic Defend, Network Packet Capture, or Packetbeat.  
+
+
+*DGA Detection Setup*
+
+The DGA Detection integration consists of an ML-based framework to detect DGA activity in DNS events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for DGA Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- DNS events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend], https://docs.elastic.co/integrations/network_traffic[Network Packet Capture] integration, or https://www.elastic.co/guide/en/beats/packetbeat/current/packetbeat-overview.html[Packetbeat].
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To add the Network Packet Capture integration to an Elastic Agent policy, refer to https://www.elastic.co/guide/en/fleet/current/add-integration-to-policy.html[this] guide.
+- To set up and run Packetbeat, follow https://www.elastic.co/guide/en/beats/packetbeat/current/setting-up-and-running.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the DGA Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Domain Generation Algorithm Detection and select the integration to see more details about it.
+- Under Settings, click Install Domain Generation Algorithm Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+Before you can enable this rule, you'll need to enrich DNS events with predictions from the Supervised DGA Detection model. This is done via the ingest pipeline named `<package_version>-ml_dga_ingest_pipeline` installed with the DGA Detection package.
+- If using an Elastic Beat such as Packetbeat, add the DGA ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `packetbeat.yml`.
+- If adding the DGA ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the DGA ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "ml_is_dga": {
+      "properties": {
+        "malicious_prediction": {
+          "type": "long"
+        },
+        "malicious_probability": {
+          "type": "float"
+        }
+      }
+    }
+  }
+}
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+ml_is_dga.malicious_probability > 0.98
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Dynamic Resolution
+** ID: T1568
+** Reference URL: https://attack.mitre.org/techniques/T1568/
+* Sub-technique:
+** Name: Domain Generation Algorithms
+** ID: T1568.002
+** Reference URL: https://attack.mitre.org/techniques/T1568/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-suspicious-windows-event-predicted-to-be-malicious-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-suspicious-windows-event-predicted-to-be-malicious-activity.asciidoc
new file mode 100644
index 0000000000..e2be5d6857
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-suspicious-windows-event-predicted-to-be-malicious-activity.asciidoc
@@ -0,0 +1,134 @@
+[[machine-learning-detected-a-suspicious-windows-event-predicted-to-be-malicious-activity]]
+=== Machine Learning Detected a Suspicious Windows Event Predicted to be Malicious Activity
+
+A supervised machine learning model (ProblemChild) has identified a suspicious Windows process event with high probability of it being malicious activity. Alternatively, the model's blocklist identified the event as being malicious.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* endgame-*
+* logs-endpoint.events.process-*
+* winlogbeat-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-10m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/problemchild
+* https://www.elastic.co/security-labs/detecting-living-off-the-land-attacks-with-new-elastic-integration
+
+*Tags*: 
+
+* OS: Windows
+* Data Source: Elastic Endgame
+* Use Case: Living off the Land Attack Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Defense Evasion
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Living off the Land (LotL) Attack Detection integration assets to be installed, as well as Windows process events collected by integrations such as Elastic Defend or Winlogbeat.  
+
+
+*LotL Attack Detection Setup*
+
+The LotL Attack Detection integration detects living-off-the-land activity in Windows process events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for LotL Attack Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration or Winlogbeat(https://www.elastic.co/guide/en/beats/winlogbeat/current/_winlogbeat_overview.html).
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To set up and run Winlogbeat, follow https://www.elastic.co/guide/en/beats/winlogbeat/current/winlogbeat-installation-configuration.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the LotL Attack Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Living off the Land Attack Detection and select the integration to see more details about it.
+- Under Settings, click Install Living off the Land Attack Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+**Before you can enable this rule**, you'll need to enrich Windows process events with predictions from the Supervised LotL Attack Detection model. This is done via the ingest pipeline named `<package_version>-problem_child_ingest_pipeline` installed with the LotL Attack Detection package.
+- If using an Elastic Beat such as Winlogbeat, add the LotL ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `winlogbeat.yml`.
+- If adding the LotL ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor]. For example, you can check if your winlogbeat or Elastic Defend (the https://docs.elastic.co/en/integrations/endpoint#logs[default index pattern] being `logs-endpoint*`) already has an ingest pipeline by navigating to `Data > Index Management`, finding the index (sometimes you need to toggle "Include hidden indices"), and checking the index's settings for a default or final https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#set-default-pipeline[pipeline].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the LotL ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "problemchild": {
+      "properties": {
+        "prediction": {
+          "type": "long"
+        },
+        "prediction_probability": {
+          "type": "float"
+        }
+      }
+    },
+    "blocklist_label": {
+      "type": "long"
+    }
+  }
+}
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where (problemchild.prediction == 1 or blocklist_label == 1) and not process.args : ("*C:\\WINDOWS\\temp\\nessus_*.txt*", "*C:\\WINDOWS\\temp\\nessus_*.tmp*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Masquerade Task or Service
+** ID: T1036.004
+** Reference URL: https://attack.mitre.org/techniques/T1036/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-suspicious-windows-event-with-a-high-malicious-probability-score.asciidoc b/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-suspicious-windows-event-with-a-high-malicious-probability-score.asciidoc
new file mode 100644
index 0000000000..13b2bfe6d6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-a-suspicious-windows-event-with-a-high-malicious-probability-score.asciidoc
@@ -0,0 +1,135 @@
+[[machine-learning-detected-a-suspicious-windows-event-with-a-high-malicious-probability-score]]
+=== Machine Learning Detected a Suspicious Windows Event with a High Malicious Probability Score
+
+A supervised machine learning model (ProblemChild) has identified a suspicious Windows process event with high probability of it being malicious activity. Alternatively, the model's blocklist identified the event as being malicious.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* endgame-*
+* logs-endpoint.events.process-*
+* winlogbeat-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-10m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/problemchild
+* https://www.elastic.co/security-labs/detecting-living-off-the-land-attacks-with-new-elastic-integration
+
+*Tags*: 
+
+* OS: Windows
+* Data Source: Elastic Endgame
+* Use Case: Living off the Land Attack Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Defense Evasion
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Living off the Land (LotL) Attack Detection integration assets to be installed, as well as Windows process events collected by integrations such as Elastic Defend or Winlogbeat.  
+
+
+*LotL Attack Detection Setup*
+
+The LotL Attack Detection integration detects living-off-the-land activity in Windows process events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for LotL Attack Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration or Winlogbeat(https://www.elastic.co/guide/en/beats/winlogbeat/current/_winlogbeat_overview.html).
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To set up and run Winlogbeat, follow https://www.elastic.co/guide/en/beats/winlogbeat/current/winlogbeat-installation-configuration.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the LotL Attack Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Living off the Land Attack Detection and select the integration to see more details about it.
+- Under Settings, click Install Living off the Land Attack Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+**Before you can enable this rule**, you'll need to enrich Windows process events with predictions from the Supervised LotL Attack Detection model. This is done via the ingest pipeline named `<package_version>-problem_child_ingest_pipeline` installed with the LotL Attack Detection package.
+- If using an Elastic Beat such as Winlogbeat, add the LotL ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `winlogbeat.yml`.
+- If adding the LotL ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor]. For example, you can check if your winlogbeat or Elastic Defend (the https://docs.elastic.co/en/integrations/endpoint#logs[default index pattern] being `logs-endpoint*`) already has an ingest pipeline by navigating to `Data > Index Management`, finding the index (sometimes you need to toggle "Include hidden indices"), and checking the index's settings for a default or final https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#set-default-pipeline[pipeline].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the LotL ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "problemchild": {
+      "properties": {
+        "prediction": {
+          "type": "long"
+        },
+        "prediction_probability": {
+          "type": "float"
+        }
+      }
+    },
+    "blocklist_label": {
+      "type": "long"
+    }
+  }
+}
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where ((problemchild.prediction == 1 and problemchild.prediction_probability > 0.98) or
+blocklist_label == 1) and not process.args : ("*C:\\WINDOWS\\temp\\nessus_*.txt*", "*C:\\WINDOWS\\temp\\nessus_*.tmp*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Masquerade Task or Service
+** ID: T1036.004
+** Reference URL: https://attack.mitre.org/techniques/T1036/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-dga-activity-using-a-known-sunburst-dns-domain.asciidoc b/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-dga-activity-using-a-known-sunburst-dns-domain.asciidoc
new file mode 100644
index 0000000000..a03efbd550
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/machine-learning-detected-dga-activity-using-a-known-sunburst-dns-domain.asciidoc
@@ -0,0 +1,132 @@
+[[machine-learning-detected-dga-activity-using-a-known-sunburst-dns-domain]]
+=== Machine Learning Detected DGA activity using a known SUNBURST DNS domain
+
+A supervised machine learning model has identified a DNS question name that used by the SUNBURST malware and is predicted to be the result of a Domain Generation Algorithm.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* logs-network_traffic.*
+
+*Severity*: critical
+
+*Risk score*: 99
+
+*Runs every*: 5m
+
+*Searches indices from*: now-10m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/dga
+* https://www.elastic.co/security-labs/detect-domain-generation-algorithm-activity-with-new-kibana-integration
+
+*Tags*: 
+
+* Domain: Network
+* Domain: Endpoint
+* Data Source: Elastic Defend
+* Use Case: Domain Generation Algorithm Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Command and Control
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Domain Generation Algorithm (DGA) Detection integration assets to be installed, as well as DNS events collected by integrations such as Elastic Defend, Network Packet Capture, or Packetbeat.  
+
+
+*DGA Detection Setup*
+
+The DGA Detection integration consists of an ML-based framework to detect DGA activity in DNS events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for DGA Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- DNS events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend], https://docs.elastic.co/integrations/network_traffic[Network Packet Capture] integration, or https://www.elastic.co/guide/en/beats/packetbeat/current/packetbeat-overview.html[Packetbeat].
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To add the Network Packet Capture integration to an Elastic Agent policy, refer to https://www.elastic.co/guide/en/fleet/current/add-integration-to-policy.html[this] guide.
+- To set up and run Packetbeat, follow https://www.elastic.co/guide/en/beats/packetbeat/current/setting-up-and-running.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the DGA Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Domain Generation Algorithm Detection and select the integration to see more details about it.
+- Under Settings, click Install Domain Generation Algorithm Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+Before you can enable this rule, you'll need to enrich DNS events with predictions from the Supervised DGA Detection model. This is done via the ingest pipeline named `<package_version>-ml_dga_ingest_pipeline` installed with the DGA Detection package.
+- If using an Elastic Beat such as Packetbeat, add the DGA ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `packetbeat.yml`.
+- If adding the DGA ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the DGA ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "ml_is_dga": {
+      "properties": {
+        "malicious_prediction": {
+          "type": "long"
+        },
+        "malicious_probability": {
+          "type": "float"
+        }
+      }
+    }
+  }
+}
+``` 
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+ml_is_dga.malicious_prediction:1 and dns.question.registered_domain:avsvmcloud.com
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Dynamic Resolution
+** ID: T1568
+** Reference URL: https://attack.mitre.org/techniques/T1568/
+* Sub-technique:
+** Name: Domain Generation Algorithms
+** ID: T1568.002
+** Reference URL: https://attack.mitre.org/techniques/T1568/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/macos-installer-package-spawns-network-event.asciidoc b/docs/detections/prebuilt-rules/rule-details/macos-installer-package-spawns-network-event.asciidoc
index c32107bae5..817fa0223d 100644
--- a/docs/detections/prebuilt-rules/rule-details/macos-installer-package-spawns-network-event.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/macos-installer-package-spawns-network-event.asciidoc
@@ -5,7 +5,7 @@ Detects the execution of a MacOS installer package with an abnormal child proces
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
 
@@ -13,55 +13,83 @@ Detects the execution of a MacOS installer package with an abnormal child proces
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://redcanary.com/blog/clipping-silver-sparrows-wings
 * https://posts.specterops.io/introducing-mystikal-4fbd2f7ae520
 * https://github.com/D00MFist/Mystikal
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Execution
-* Command and Control
 
-*Version*: 100 (<<macos-installer-package-spawns-network-event-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Custom organization-specific macOS packages that use .pkg files to run cURL could trigger this rule. If known behavior is causing false positives, it can be excluded from the rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, user.id with maxspan=30s [process where
-event.type == "start" and event.action == "exec" and
-process.parent.name : ("installer", "package_script_service") and
-process.name : ("bash", "sh", "zsh", "python", "osascript", "tclsh*")]
-[network where event.type == "start" and process.name : ("curl",
-"osascript", "wget", "python")]
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=15s
+[process where host.os.type == "macos" and event.type == "start" and event.action == "exec" and process.parent.name : ("installer", "package_script_service") and process.name : ("bash", "sh", "zsh", "python", "osascript", "tclsh*")] by process.entity_id
+[network where host.os.type == "macos" and event.type == "start" and process.name : ("curl", "osascript", "wget", "python", "java", "ruby", "node")] by process.parent.entity_id
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,8 +101,10 @@ process.name : ("bash", "sh", "zsh", "python", "osascript", "tclsh*")]
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-
+* Sub-technique:
+** Name: JavaScript
+** ID: T1059.007
+** Reference URL: https://attack.mitre.org/techniques/T1059/007/
 * Tactic:
 ** Name: Command and Control
 ** ID: TA0011
@@ -83,62 +113,7 @@ process.name : ("bash", "sh", "zsh", "python", "osascript", "tclsh*")]
 ** Name: Application Layer Protocol
 ** ID: T1071
 ** Reference URL: https://attack.mitre.org/techniques/T1071/
-
-[[macos-installer-package-spawns-network-event-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, user.id with maxspan=30s [process where
-event.type == "start" and event.action == "exec" and
-process.parent.name : ("installer", "package_script_service") and
-process.name : ("bash", "sh", "zsh", "python", "osascript", "tclsh*")]
-[network where event.type == "start" and process.name : ("curl",
-"osascript", "wget", "python")]
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Rule name changed from: macOS Installer Spawns Network Event
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan=1m [process where
-event.type == "start" and host.os.family == "macos" and
-process.parent.executable in ("/usr/sbin/installer",
-"/System/Library/CoreServices/Installer.app/Contents/MacOS/Installer")
-] [network where not cidrmatch(destination.ip, "10.0.0.0/8",
-"127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
-"192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24", "192.31.196.0/24",
-"192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
-"100.64.0.0/10", "192.175.48.0/24", "198.18.0.0/15",
-"198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
-"FE80::/10", "FF00::/8")]
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.15.0 release)::
-* Formatting only
-
-Version 2 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan=1m [ process where
-event.type == "start" and host.os.family == "macos" and
-process.parent.executable in ("/usr/sbin/installer",
-"/System/Library/CoreServices/Installer.app/Contents/MacOS/Installer")
-] [ network where not cidrmatch(destination.ip,
-"192.168.0.0/16", "10.0.0.0/8", "172.16.0.0/12",
-"224.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16",
-"::1", "FE80::/10", "FF00::/8") ]
-----------------------------------
-
+* Sub-technique:
+** Name: Web Protocols
+** ID: T1071.001
+** Reference URL: https://attack.mitre.org/techniques/T1071/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/malware-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/malware-detected-elastic-endgame.asciidoc
index 251a1ae211..49d92fa6d8 100644
--- a/docs/detections/prebuilt-rules/rule-details/malware-detected-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/malware-detected-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame detected Malware. Click the Elastic Endgame icon in the event.mo
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,67 +13,47 @@ Elastic Endgame detected Malware. Click the Elastic Endgame icon in the event.mo
 
 *Risk score*: 99
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 100 (<<malware-detected-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
+
+==== Setup
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:detection and
-(event.action:file_classification_event or
-endgame.event_subtype_full:file_classification_event)
-----------------------------------
 
+*Setup*
 
-[[malware-detected-elastic-endgame-history]]
-==== Rule version history
 
-Version 100 (8.5.0 release)::
-* Formatting only
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
 
-Version 8 (8.4.0 release)::
-* Formatting only
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
 
-Version 7 (8.0.0 release)::
-* Formatting only
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
 
-Version 6 (7.12.1 release)::
-* Formatting only
 
-Version 5 (7.12.0 release)::
-* Rule name changed from: Malware - Detected - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Malware - Detected - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Malware - Detected - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:file_classification_event and
-endgame.metadata.type:detection
-----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:file_classification_event or endgame.event_subtype_full:file_classification_event)
 
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/malware-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/malware-prevented-elastic-endgame.asciidoc
index 0fbf8d6b8b..e310499173 100644
--- a/docs/detections/prebuilt-rules/rule-details/malware-prevented-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/malware-prevented-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame prevented Malware. Click the Elastic Endgame icon in the event.m
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,67 +13,47 @@ Elastic Endgame prevented Malware. Click the Elastic Endgame icon in the event.m
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 100 (<<malware-prevented-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
+
+==== Setup
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:prevention and
-(event.action:file_classification_event or
-endgame.event_subtype_full:file_classification_event)
-----------------------------------
 
+*Setup*
 
-[[malware-prevented-elastic-endgame-history]]
-==== Rule version history
 
-Version 100 (8.5.0 release)::
-* Formatting only
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
 
-Version 8 (8.4.0 release)::
-* Formatting only
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
 
-Version 7 (8.0.0 release)::
-* Formatting only
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
 
-Version 6 (7.12.1 release)::
-* Formatting only
 
-Version 5 (7.12.0 release)::
-* Rule name changed from: Malware - Prevented - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Malware - Prevented - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Malware - Prevented - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:file_classification_event and
-endgame.metadata.type:prevention
-----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:file_classification_event or endgame.event_subtype_full:file_classification_event)
 
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/masquerading-space-after-filename.asciidoc b/docs/detections/prebuilt-rules/rule-details/masquerading-space-after-filename.asciidoc
index 5e0b5c7c3a..474dc6398f 100644
--- a/docs/detections/prebuilt-rules/rule-details/masquerading-space-after-filename.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/masquerading-space-after-filename.asciidoc
@@ -5,7 +5,7 @@ This rules identifies a process created from an executable with a space appended
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,53 +14,59 @@ This rules identifies a process created from an executable with a space appended
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.picussecurity.com/resource/blog/picus-10-critical-mitre-attck-techniques-t1036-masquerading
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* macOS
-* Threat Detection
-* Defense Evasion
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
 
-*Version*: 1
+*Version*: 6
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where host.os.type:("linux","macos") and event.type ==
-"start" and (process.executable regex~ """/[a-z0-9\s_\-\\./]+\s""")
-and not process.name in ("ls", "find", "grep", "xkbcomp")
+[source, js]
 ----------------------------------
+process where host.os.type:("linux","macos") and
+  event.type == "start" and
+  (process.executable regex~ """/[a-z0-9\s_\-\\./]+\s""") and not
+  process.name in ("ls", "find", "grep", "xkbcomp")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,3 +78,7 @@ and not process.name in ("ls", "find", "grep", "xkbcomp")
 ** Name: Masquerading
 ** ID: T1036
 ** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Space after Filename
+** ID: T1036.006
+** Reference URL: https://attack.mitre.org/techniques/T1036/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/member-removed-from-github-organization.asciidoc b/docs/detections/prebuilt-rules/rule-details/member-removed-from-github-organization.asciidoc
new file mode 100644
index 0000000000..059876b9c1
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/member-removed-from-github-organization.asciidoc
@@ -0,0 +1,60 @@
+[[member-removed-from-github-organization]]
+=== Member Removed From GitHub Organization
+
+A member was removed or their invitation to join was removed from a GitHub Organization.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Impact
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+configuration where event.dataset == "github.audit" and event.action == "org.remove_member"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Account Access Removal
+** ID: T1531
+** Reference URL: https://attack.mitre.org/techniques/T1531/
diff --git a/docs/detections/prebuilt-rules/rule-details/memory-dump-file-with-unusual-extension.asciidoc b/docs/detections/prebuilt-rules/rule-details/memory-dump-file-with-unusual-extension.asciidoc
new file mode 100644
index 0000000000..089611c4c2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/memory-dump-file-with-unusual-extension.asciidoc
@@ -0,0 +1,90 @@
+[[memory-dump-file-with-unusual-extension]]
+=== Memory Dump File with Unusual Extension
+
+Identifies the creation of a memory dump file with an unusual extension, which can indicate an attempt to disguise a memory dump as another file type to bypass security defenses.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and
+
+  /* MDMP header */
+  file.Ext.header_bytes : "4d444d50*" and
+  not file.extension : ("dmp", "mdmp", "hdmp", "edmp", "full", "tdref", "cg", "tmp", "dat") and
+  not 
+  (
+    process.executable : "?:\\Program Files\\Endgame\\esensor.exe" and
+    process.code_signature.trusted == true and length(file.extension) == 0
+  ) and
+  not
+  (
+    process.name : "System" and file.extension : "tmpscan"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Masquerade File Type
+** ID: T1036.008
+** Reference URL: https://attack.mitre.org/techniques/T1036/008/
diff --git a/docs/detections/prebuilt-rules/rule-details/mfa-deactivation-with-no-re-activation-for-okta-user-account.asciidoc b/docs/detections/prebuilt-rules/rule-details/mfa-deactivation-with-no-re-activation-for-okta-user-account.asciidoc
new file mode 100644
index 0000000000..edcc87323c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/mfa-deactivation-with-no-re-activation-for-okta-user-account.asciidoc
@@ -0,0 +1,120 @@
+[[mfa-deactivation-with-no-re-activation-for-okta-user-account]]
+=== MFA Deactivation with no Re-Activation for Okta User Account
+
+Detects multi-factor authentication (MFA) deactivation with no subsequent re-activation for an Okta user account. An adversary may deactivate MFA for an Okta user account in order to weaken the authentication requirements for the account.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta.system*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 6h
+
+*Searches indices from*: now-12h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://developer.okta.com/docs/reference/api/system-log/
+* https://developer.okta.com/docs/reference/api/event-types/
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+
+*Tags*: 
+
+* Tactic: Persistence
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Domain: Cloud
+
+*Version*: 207
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating MFA Deactivation with no Re-Activation for Okta User Account*
+
+
+MFA is used to provide an additional layer of security for user accounts. An adversary may achieve MFA deactivation for an Okta user account to achieve persistence.
+
+This rule fires when an Okta user account has MFA deactivated and no subsequent MFA reactivation is observed within 12 hours.
+
+
+*Possible investigation steps:*
+
+
+- Identify the actor related to the alert by reviewing `okta.actor.alternate_id` field in the alert. This should give the username of the account being targeted.
+- Review `okta.target` or `user.target.full_name` fields to determine if deactivation was performed by a se parate user.
+- Using the `okta.actor.alternate_id` field, search  for MFA re-activation events where `okta.event_type` is `user.mfa.factor.activate`.
+- Review events where `okta.event_type` is `user.authenticate*` to determine if the user account had suspicious login activity.
+    - Geolocation details found in `client.geo*` related fields may be useful in determining if the login activity was suspicious for this user.
+
+
+*False positive steps:*
+
+
+- Determine with the target user if MFA deactivation was expected.
+- Determine if MFA is required for the target user account.
+
+
+*Response and remediation:*
+
+
+- If the MFA deactivation was not expected, consider deactivating the user
+    - This should be followed by resetting the user's password and re-enabling MFA.
+- If the MFA deactivation was expected, consider adding an exception to this rule to filter false positives.
+- Investigate the source of the attack. If a specific machine or network is compromised, additional steps may need to be taken to address the issue.
+- Encourage users to use complex, unique passwords and consider implementing multi-factor authentication.
+- Check if the compromised account was used to access or alter any sensitive data, applications or systems.
+
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by okta.actor.id with maxspan=12h
+    [any where event.dataset == "okta.system" and okta.event_type == "user.mfa.factor.deactivate"
+        and okta.outcome.result == "SUCCESS" and not okta.client.user_agent.raw_user_agent like "SFDC-Callout*"]
+    ![any where event.dataset == "okta.system" and okta.event_type == "user.mfa.factor.activate"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Modify Authentication Process
+** ID: T1556
+** Reference URL: https://attack.mitre.org/techniques/T1556/
+* Sub-technique:
+** Name: Multi-Factor Authentication
+** ID: T1556.006
+** Reference URL: https://attack.mitre.org/techniques/T1556/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/mfa-disabled-for-google-workspace-organization.asciidoc b/docs/detections/prebuilt-rules/rule-details/mfa-disabled-for-google-workspace-organization.asciidoc
index 69802426a9..6f31ded95c 100644
--- a/docs/detections/prebuilt-rules/rule-details/mfa-disabled-for-google-workspace-organization.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/mfa-disabled-for-google-workspace-organization.asciidoc
@@ -5,7 +5,7 @@ Detects when multi-factor authentication (MFA) is disabled for a Google Workspac
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-google_workspace*
@@ -14,42 +14,90 @@ Detects when multi-factor authentication (MFA) is disabled for a Google Workspac
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-130m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Cloud
-* Google Workspace
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Persistence
+*Tags*: 
 
-*Version*: 101 (<<mfa-disabled-for-google-workspace-organization-history, version history>>)
+* Domain: Cloud
+* Data Source: Google Workspace
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
+* Resources: Investigation Guide
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 205
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-MFA settings may be modified by system administrators. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-### Important Information Regarding Google Workspace Event Lag Times
+
+*Triage and analysis*
+
+
+
+*Investigating MFA Disabled for Google Workspace Organization*
+
+
+Multi-factor authentication (MFA) is a process in which users are prompted for an additional form of identification, such as a code on their cell phone or a fingerprint scan, during the sign-in process.
+
+If you only use a password to authenticate a user, it leaves an insecure vector for attack. If the users's password is weak or has been exposed elsewhere, an attacker could use it to gain access. Requiring a second form of authentication increases security because attackers cannot easily obtain or duplicate the additional authentication factor.
+
+For more information about using MFA in Google Workspace, access the https://support.google.com/a/answer/175197[official documentation].
+
+This rule identifies when MFA enforcement is turned off in Google Workspace. This modification weakens account security and can lead to accounts and other assets being compromised.
+
+
+*Possible investigation steps*
+
+
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate other alerts associated with the user account during the past 48 hours.
+- Contact the account and resource owners and confirm whether they are aware of this activity.
+- Check if this operation was approved and performed according to the organization's change management policy.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
+
+- While this activity can be done by administrators, all users must use MFA. The security team should address any potential benign true positive (B-TP), as this configuration can risk the user and domain.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Disable or limit the account during the investigation and response.
+- Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
+    - Identify the account role in the cloud environment.
+    - Assess the criticality of affected services and servers.
+    - Work with your IT team to identify and minimize the impact on users.
+    - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
+    - Identify any regulatory or legal ramifications related to this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Reactivate the multi-factor authentication enforcement.
+- Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
+- Implement security best practices https://support.google.com/a/answer/7587183[outlined] by Google.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+
+
+*Important Information Regarding Google Workspace Event Lag Times*
+
 - As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
 - This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
 - To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
@@ -57,21 +105,20 @@ MFA settings may be modified by system administrators. Verify that the configura
 - See the following references for further information:
   - https://support.google.com/a/answer/7061566
   - https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html
-----------------------------------
+
+==== Setup
 
 
+The Google Workspace Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:google_workspace.admin and event.provider:admin and
-event.category:iam and event.action:(ENFORCE_STRONG_AUTHENTICATION or
-ALLOW_STRONG_AUTHENTICATION) and
-google_workspace.admin.new_value:false
+[source, js]
 ----------------------------------
+event.dataset:google_workspace.admin and event.provider:admin and event.category:iam and event.action:(ENFORCE_STRONG_AUTHENTICATION or ALLOW_STRONG_AUTHENTICATION) and google_workspace.admin.new_value:false
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -83,57 +130,3 @@ google_workspace.admin.new_value:false
 ** Name: Modify Authentication Process
 ** ID: T1556
 ** Reference URL: https://attack.mitre.org/techniques/T1556/
-
-[[mfa-disabled-for-google-workspace-organization-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 15 (8.4.0 release)::
-* Formatting only
-
-Version 13 (8.3.0 release)::
-* Formatting only
-
-Version 11 (8.2.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:(ENFORCE_STRONG_AUTHENTICATION or
-ALLOW_STRONG_AUTHENTICATION) and (gsuite.admin.new_value:false or
-google_workspace.admin.new_value:false)
-----------------------------------
-
-Version 6 (7.15.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(gsuite.admin or google_workspace.admin) and
-event.provider:admin and event.category:iam and
-event.action:(ENFORCE_STRONG_AUTHENTICATION or
-ALLOW_STRONG_AUTHENTICATION) and gsuite.admin.new_value:false
-----------------------------------
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-anti-phish-policy-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-anti-phish-policy-deletion.asciidoc
index d8d37a3b7b..1fc71ad4db 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-anti-phish-policy-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-anti-phish-policy-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies the deletion of an anti-phishing policy in Microsoft 365. By default,
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,51 @@ Identifies the deletion of an anti-phishing policy in Microsoft 365. By default,
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/remove-antiphishpolicy?view=exchange-ps
 * https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/set-up-anti-phishing-policies?view=o365-worldwide
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<microsoft-365-exchange-anti-phish-policy-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-An anti-phishing policy may be deleted by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"Remove-AntiPhishPolicy" and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:"Remove-AntiPhishPolicy" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,28 +70,3 @@ event.outcome:success
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[microsoft-365-exchange-anti-phish-policy-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-anti-phish-rule-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-anti-phish-rule-modification.asciidoc
index e29aaf213e..fedc9bd4de 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-anti-phish-rule-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-anti-phish-rule-modification.asciidoc
@@ -5,7 +5,7 @@ Identifies the modification of an anti-phishing rule in Microsoft 365. By defaul
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,51 @@ Identifies the modification of an anti-phishing rule in Microsoft 365. By defaul
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/remove-antiphishrule?view=exchange-ps
 * https://docs.microsoft.com/en-us/powershell/module/exchange/disable-antiphishrule?view=exchange-ps
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<microsoft-365-exchange-anti-phish-rule-modification-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-An anti-phishing rule may be deleted by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:("Remove-AntiPhishRule" or
-"Disable-AntiPhishRule") and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:("Remove-AntiPhishRule" or "Disable-AntiPhishRule") and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,28 +70,3 @@ event.category:web and event.action:("Remove-AntiPhishRule" or
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[microsoft-365-exchange-anti-phish-rule-modification-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-dkim-signing-configuration-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-dkim-signing-configuration-disabled.asciidoc
index ee1941f9cc..d49d2eb2a2 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-dkim-signing-configuration-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-dkim-signing-configuration-disabled.asciidoc
@@ -5,7 +5,7 @@ Identifies when a DomainKeys Identified Mail (DKIM) signing configuration is dis
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,49 @@ Identifies when a DomainKeys Identified Mail (DKIM) signing configuration is dis
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/set-dkimsigningconfig?view=exchange-ps
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Data Protection
-* Persistence
-
-*Version*: 101 (<<microsoft-365-exchange-dkim-signing-configuration-disabled-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Disabling a DKIM configuration may be done by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"Set-DkimSigningConfig" and
-o365.audit.Parameters.Enabled:False and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:"Set-DkimSigningConfig" and o365.audit.Parameters.Enabled:False and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,31 +68,3 @@ o365.audit.Parameters.Enabled:False and event.outcome:success
 ** Name: Modify Authentication Process
 ** ID: T1556
 ** Reference URL: https://attack.mitre.org/techniques/T1556/
-
-[[microsoft-365-exchange-dkim-signing-configuration-disabled-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-dlp-policy-removed.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-dlp-policy-removed.asciidoc
index 9dee46c467..23e35ccf29 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-dlp-policy-removed.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-dlp-policy-removed.asciidoc
@@ -5,7 +5,7 @@ Identifies when a Data Loss Prevention (DLP) policy is removed in Microsoft 365.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,51 @@ Identifies when a Data Loss Prevention (DLP) policy is removed in Microsoft 365.
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/remove-dlppolicy?view=exchange-ps
 * https://docs.microsoft.com/en-us/microsoft-365/compliance/data-loss-prevention-policies?view=o365-worldwide
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<microsoft-365-exchange-dlp-policy-removed-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A DLP policy may be removed by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"Remove-DlpPolicy" and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:"Remove-DlpPolicy" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,28 +70,3 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[microsoft-365-exchange-dlp-policy-removed-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-malware-filter-policy-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-malware-filter-policy-deletion.asciidoc
index 4635cbb02e..63dfd57229 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-malware-filter-policy-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-malware-filter-policy-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies when a malware filter policy has been deleted in Microsoft 365. A mal
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,59 +14,50 @@ Identifies when a malware filter policy has been deleted in Microsoft 365. A mal
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/remove-malwarefilterpolicy?view=exchange-ps
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<microsoft-365-exchange-malware-filter-policy-deletion-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A malware filter policy may be deleted by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"Remove-MalwareFilterPolicy" and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:"Remove-MalwareFilterPolicy" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,28 +69,3 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[microsoft-365-exchange-malware-filter-policy-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-malware-filter-rule-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-malware-filter-rule-modification.asciidoc
index 3cad8baef0..b6127da4d4 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-malware-filter-rule-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-malware-filter-rule-modification.asciidoc
@@ -5,7 +5,7 @@ Identifies when a malware filter rule has been deleted or disabled in Microsoft
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,51 @@ Identifies when a malware filter rule has been deleted or disabled in Microsoft
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/remove-malwarefilterrule?view=exchange-ps
 * https://docs.microsoft.com/en-us/powershell/module/exchange/disable-malwarefilterrule?view=exchange-ps
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<microsoft-365-exchange-malware-filter-rule-modification-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A malware filter rule may be deleted by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:("Remove-MalwareFilterRule" or
-"Disable-MalwareFilterRule") and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:("Remove-MalwareFilterRule" or "Disable-MalwareFilterRule") and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,28 +70,3 @@ event.category:web and event.action:("Remove-MalwareFilterRule" or
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[microsoft-365-exchange-malware-filter-rule-modification-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-management-group-role-assignment.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-management-group-role-assignment.asciidoc
index e6577a99b2..4e403f0837 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-management-group-role-assignment.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-management-group-role-assignment.asciidoc
@@ -5,7 +5,7 @@ Identifies when a new role is assigned to a management group in Microsoft 365. A
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,51 @@ Identifies when a new role is assigned to a management group in Microsoft 365. A
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/new-managementroleassignment?view=exchange-ps
 * https://docs.microsoft.com/en-us/microsoft-365/admin/add-users/about-admin-roles?view=o365-worldwide
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<microsoft-365-exchange-management-group-role-assignment-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A new role may be assigned to a management group by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"New-ManagementRoleAssignment" and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:"New-ManagementRoleAssignment" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,28 +70,3 @@ event.outcome:success
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[microsoft-365-exchange-management-group-role-assignment-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-safe-attachment-rule-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-safe-attachment-rule-disabled.asciidoc
index f27d9fcbcd..222f8ed210 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-safe-attachment-rule-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-safe-attachment-rule-disabled.asciidoc
@@ -5,7 +5,7 @@ Identifies when a safe attachment rule is disabled in Microsoft 365. Safe attach
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,59 +14,50 @@ Identifies when a safe attachment rule is disabled in Microsoft 365. Safe attach
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/disable-safeattachmentrule?view=exchange-ps
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<microsoft-365-exchange-safe-attachment-rule-disabled-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A safe attachment rule may be disabled by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"Disable-SafeAttachmentRule" and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:"Disable-SafeAttachmentRule" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,28 +69,3 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[microsoft-365-exchange-safe-attachment-rule-disabled-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-safe-link-policy-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-safe-link-policy-disabled.asciidoc
index 8b5cb245f1..ba13564570 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-safe-link-policy-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-safe-link-policy-disabled.asciidoc
@@ -5,7 +5,7 @@ Identifies when a Safe Link policy is disabled in Microsoft 365. Safe Link polic
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,51 @@ Identifies when a Safe Link policy is disabled in Microsoft 365. Safe Link polic
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/disable-safelinksrule?view=exchange-ps
 * https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/atp-safe-links?view=o365-worldwide
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<microsoft-365-exchange-safe-link-policy-disabled-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Identity and Access Audit
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Disabling safe links may be done by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"Disable-SafeLinksRule" and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:"Disable-SafeLinksRule" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,28 +70,3 @@ event.outcome:success
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[microsoft-365-exchange-safe-link-policy-disabled-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-transport-rule-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-transport-rule-creation.asciidoc
index 21d773e2eb..321728f3ff 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-transport-rule-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-transport-rule-creation.asciidoc
@@ -5,7 +5,7 @@ Identifies a transport rule creation in Microsoft 365. As a best practice, Excha
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,51 @@ Identifies a transport rule creation in Microsoft 365. As a best practice, Excha
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/new-transportrule?view=exchange-ps
 * https://docs.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/mail-flow-rules
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<microsoft-365-exchange-transport-rule-creation-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Exfiltration
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A new transport rule may be created by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"New-TransportRule" and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:"New-TransportRule" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,31 +70,3 @@ event.outcome:success
 ** Name: Transfer Data to Cloud Account
 ** ID: T1537
 ** Reference URL: https://attack.mitre.org/techniques/T1537/
-
-[[microsoft-365-exchange-transport-rule-creation-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-transport-rule-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-transport-rule-modification.asciidoc
index 2b0bd352c1..ef1b4f21a5 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-transport-rule-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-exchange-transport-rule-modification.asciidoc
@@ -5,7 +5,7 @@ Identifies when a transport rule has been disabled or deleted in Microsoft 365.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,61 +14,52 @@ Identifies when a transport rule has been disabled or deleted in Microsoft 365.
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/remove-transportrule?view=exchange-ps
 * https://docs.microsoft.com/en-us/powershell/module/exchange/disable-transportrule?view=exchange-ps
 * https://docs.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/mail-flow-rules
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<microsoft-365-exchange-transport-rule-modification-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Exfiltration
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A transport rule may be modified by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:("Remove-TransportRule" or
-"Disable-TransportRule") and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:("Remove-TransportRule" or "Disable-TransportRule") and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,28 +71,3 @@ event.category:web and event.action:("Remove-TransportRule" or
 ** Name: Transfer Data to Cloud Account
 ** ID: T1537
 ** Reference URL: https://attack.mitre.org/techniques/T1537/
-
-[[microsoft-365-exchange-transport-rule-modification-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-global-administrator-role-assigned.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-global-administrator-role-assigned.asciidoc
index bf44ec9867..70666088e4 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-global-administrator-role-assigned.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-global-administrator-role-assigned.asciidoc
@@ -5,7 +5,7 @@ In Azure Active Directory (Azure AD), permissions to manage resources are assign
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,56 +14,51 @@ In Azure Active Directory (Azure AD), permissions to manage resources are assign
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/active-directory/roles/permissions-reference#global-administrator
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 101 (<<microsoft-365-global-administrator-role-assigned-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.code:"AzureActiveDirectory" and
-event.action:"Add member to role." and
-o365.audit.ModifiedProperties.Role_DisplayName.NewValue:"Global
-Administrator"
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.code:"AzureActiveDirectory" and event.action:"Add member to role." and
+o365.audit.ModifiedProperties.Role_DisplayName.NewValue:"Global Administrator"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,19 +70,7 @@ Administrator"
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[microsoft-365-global-administrator-role-assigned-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Additional Cloud Roles
+** ID: T1098.003
+** Reference URL: https://attack.mitre.org/techniques/T1098/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-impossible-travel-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-impossible-travel-activity.asciidoc
new file mode 100644
index 0000000000..72ac7bbc9c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-impossible-travel-activity.asciidoc
@@ -0,0 +1,72 @@
+[[microsoft-365-impossible-travel-activity]]
+=== Microsoft 365 Impossible travel activity
+
+Identifies when a Microsoft Cloud App Security reported a risky sign-in attempt due to a login associated with an impossible travel.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-o365*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.microsoft.com/en-us/cloud-app-security/anomaly-detection-policy
+* https://docs.microsoft.com/en-us/cloud-app-security/policy-template-reference
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Initial Access
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Austin Songer
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:o365.audit and event.provider:SecurityComplianceCenter and event.category:web and event.action:"Impossible travel activity" and event.outcome:success
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-inbox-forwarding-rule-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-inbox-forwarding-rule-created.asciidoc
index 65d5201dcb..af217503d2 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-inbox-forwarding-rule-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-inbox-forwarding-rule-created.asciidoc
@@ -5,7 +5,7 @@ Identifies when a new Inbox forwarding rule is created in Microsoft 365. Inbox r
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,64 +14,62 @@ Identifies when a new Inbox forwarding rule is created in Microsoft 365. Inbox r
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/responding-to-a-compromised-email-account?view=o365-worldwide
 * https://docs.microsoft.com/en-us/powershell/module/exchange/new-inboxrule?view=exchange-ps
 * https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/detect-and-remediate-outlook-rules-forms-attack?view=o365-worldwide
 * https://raw.githubusercontent.com/PwC-IR/Business-Email-Compromise-Guide/main/Extractor%20Cheat%20Sheet.pdf
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<microsoft-365-inbox-forwarding-rule-created-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Collection
 
-*Added ({stack} release)*: 7.13.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Gary Blackwell, Austin Songer
+* Elastic
+* Gary Blackwell
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Users and Administrators can create inbox rules for legitimate purposes. Verify if it complies with the company policy and done with the user's consent. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:("New-InboxRule" or "Set-
-InboxRule") and ( o365.audit.Parameters.ForwardTo:* or
-o365.audit.Parameters.ForwardAsAttachmentTo:* or
-o365.audit.Parameters.RedirectTo:* ) and event.outcome:success
-----------------------------------
+event.category:web and event.action:("New-InboxRule" or "Set-InboxRule") and
+    (
+        o365.audit.Parameters.ForwardTo:* or
+        o365.audit.Parameters.ForwardAsAttachmentTo:* or
+        o365.audit.Parameters.RedirectTo:*
+    )
+    and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -83,62 +81,7 @@ o365.audit.Parameters.RedirectTo:* ) and event.outcome:success
 ** Name: Email Collection
 ** ID: T1114
 ** Reference URL: https://attack.mitre.org/techniques/T1114/
-
-[[microsoft-365-inbox-forwarding-rule-created-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"New-InboxRule" and (
-o365.audit.Parameters.ForwardTo:* or
-o365.audit.Parameters.ForwardAsAttachmentTo:* or
-o365.audit.Parameters.RedirectTo:* ) and event.outcome:success
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"New-InboxRule" and (
-o365.audit.Parameters.ForwardTo:* or
-o365.audit.Parameters.ForwardAsAttachmentTo:* or
-o365.audit.Parameters.RedirectTo:* ) and
-event.outcome:success
-----------------------------------
-
-Version 4 (8.3.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"New-InboxRule" and (
-o365audit.Parameters.ForwardTo:* or
-o365audit.Parameters.ForwardAsAttachmentTo:* or
-o365audit.Parameters.RedirectTo:* ) and event.outcome:success
-----------------------------------
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Rule name changed from: Microsoft 365 New Inbox Rule Created
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:"New-InboxRule" and
-event.outcome:success
-----------------------------------
-
+* Sub-technique:
+** Name: Email Forwarding Rule
+** ID: T1114.003
+** Reference URL: https://attack.mitre.org/techniques/T1114/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-mass-download-by-a-single-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-mass-download-by-a-single-user.asciidoc
new file mode 100644
index 0000000000..8d013480b2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-mass-download-by-a-single-user.asciidoc
@@ -0,0 +1,68 @@
+[[microsoft-365-mass-download-by-a-single-user]]
+=== Microsoft 365 Mass download by a single user
+
+Identifies when Microsoft Cloud App Security reports that a single user performs more than 50 downloads within 1 minute.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-o365*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.microsoft.com/en-us/cloud-app-security/anomaly-detection-policy
+* https://docs.microsoft.com/en-us/cloud-app-security/policy-template-reference
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Exfiltration
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Austin Songer
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:o365.audit and event.provider:SecurityComplianceCenter and event.category:web and event.action:"Mass download by a single user" and event.outcome:success
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-potential-ransomware-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-potential-ransomware-activity.asciidoc
index 05b3582ddd..62cc9e6f9e 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-potential-ransomware-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-potential-ransomware-activity.asciidoc
@@ -5,7 +5,7 @@ Identifies when Microsoft Cloud App Security reports that a user has uploaded fi
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,51 @@ Identifies when Microsoft Cloud App Security reports that a user has uploaded fi
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/cloud-app-security/anomaly-detection-policy
 * https://docs.microsoft.com/en-us/cloud-app-security/policy-template-reference
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Impact
 
-*Version*: 101 (<<microsoft-365-potential-ransomware-activity-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-If Cloud App Security identifies, for example, a high rate of file uploads or file deletion activities it may represent an adverse encryption process.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:SecurityComplianceCenter
-and event.category:web and event.action:"Potential ransomware
-activity" and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:SecurityComplianceCenter and event.category:web and event.action:"Potential ransomware activity" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,22 +70,3 @@ activity" and event.outcome:success
 ** Name: Data Encrypted for Impact
 ** ID: T1486
 ** Reference URL: https://attack.mitre.org/techniques/T1486/
-
-[[microsoft-365-potential-ransomware-activity-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
-Version 2 (8.0.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-custom-application-interaction-allowed.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-custom-application-interaction-allowed.asciidoc
index c24304ab39..e6b4daead8 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-custom-application-interaction-allowed.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-custom-application-interaction-allowed.asciidoc
@@ -5,7 +5,7 @@ Identifies when custom applications are allowed in Microsoft Teams. If an organi
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,61 +14,53 @@ Identifies when custom applications are allowed in Microsoft Teams. If an organi
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/deploy-and-publish/apps-upload
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-* Persistence
-
-*Version*: 101 (<<microsoft-365-teams-custom-application-interaction-allowed-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Custom applications may be allowed by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.dataset:o365.audit and event.provider:MicrosoftTeams and
 event.category:web and event.action:TeamsTenantSettingChanged and
 o365.audit.Name:"Allow sideloading and interaction of custom apps" and
 o365.audit.NewValue:True and event.outcome:success
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,28 +68,3 @@ o365.audit.NewValue:True and event.outcome:success
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-[[microsoft-365-teams-custom-application-interaction-allowed-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-external-access-enabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-external-access-enabled.asciidoc
index d0ed2eb9c1..bc82a213bf 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-external-access-enabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-external-access-enabled.asciidoc
@@ -5,7 +5,7 @@ Identifies when external access is enabled in Microsoft Teams. External access l
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,61 +14,52 @@ Identifies when external access is enabled in Microsoft Teams. External access l
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/microsoftteams/manage-external-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<microsoft-365-teams-external-access-enabled-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Teams external access may be enabled by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:(SkypeForBusiness or
-MicrosoftTeams) and event.category:web and event.action:"Set-
-CsTenantFederationConfiguration" and
-o365.audit.Parameters.AllowFederatedUsers:True and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:(SkypeForBusiness or MicrosoftTeams) and
+event.category:web and event.action:"Set-CsTenantFederationConfiguration" and
+o365.audit.Parameters.AllowFederatedUsers:True and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,28 +71,3 @@ event.outcome:success
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[microsoft-365-teams-external-access-enabled-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-guest-access-enabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-guest-access-enabled.asciidoc
index 62391ca65f..075a7825df 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-guest-access-enabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-teams-guest-access-enabled.asciidoc
@@ -5,7 +5,7 @@ Identifies when guest access is enabled in Microsoft Teams. Guest access in Team
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,52 @@ Identifies when guest access is enabled in Microsoft Teams. Guest access in Team
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/skype/get-csteamsclientconfiguration?view=skype-ps
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<microsoft-365-teams-guest-access-enabled-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Teams guest access may be enabled by a system or network administrator. Verify that the configuration change was expected. Exceptions can be added to this rule to filter expected behavior.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
-event.dataset:o365.audit and event.provider:(SkypeForBusiness or
-MicrosoftTeams) and event.category:web and event.action:"Set-
-CsTeamsClientConfiguration" and
+event.dataset:o365.audit and event.provider:(SkypeForBusiness or MicrosoftTeams) and
+event.category:web and event.action:"Set-CsTeamsClientConfiguration" and
 o365.audit.Parameters.AllowGuestUser:True and event.outcome:success
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,28 +71,3 @@ o365.audit.Parameters.AllowGuestUser:True and event.outcome:success
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[microsoft-365-teams-guest-access-enabled-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-unusual-volume-of-file-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-unusual-volume-of-file-deletion.asciidoc
index 2f471fa52d..5d1a541924 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-unusual-volume-of-file-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-unusual-volume-of-file-deletion.asciidoc
@@ -5,7 +5,7 @@ Identifies that a user has deleted an unusually large volume of files as reporte
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,51 @@ Identifies that a user has deleted an unusually large volume of files as reporte
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/cloud-app-security/anomaly-detection-policy
 * https://docs.microsoft.com/en-us/cloud-app-security/policy-template-reference
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Impact
 
-*Version*: 101 (<<microsoft-365-unusual-volume-of-file-deletion-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Users or System Administrator cleaning out folders.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:SecurityComplianceCenter
-and event.category:web and event.action:"Unusual volume of file
-deletion" and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:SecurityComplianceCenter and event.category:web and event.action:"Unusual volume of file deletion" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,19 +70,3 @@ deletion" and event.outcome:success
 ** Name: Data Destruction
 ** ID: T1485
 ** Reference URL: https://attack.mitre.org/techniques/T1485/
-
-[[microsoft-365-unusual-volume-of-file-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-365-user-restricted-from-sending-email.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-365-user-restricted-from-sending-email.asciidoc
index 6bab47e5ab..c91074b5c2 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-365-user-restricted-from-sending-email.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-365-user-restricted-from-sending-email.asciidoc
@@ -5,7 +5,7 @@ Identifies when a user has been restricted from sending email due to exceeding s
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,60 +14,51 @@ Identifies when a user has been restricted from sending email due to exceeding s
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/cloud-app-security/anomaly-detection-policy
 * https://docs.microsoft.com/en-us/cloud-app-security/policy-template-reference
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Initial Access
 
-*Version*: 101 (<<microsoft-365-user-restricted-from-sending-email-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A user sending emails using personal distribution folders may trigger the event.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:SecurityComplianceCenter
-and event.category:web and event.action:"User restricted from sending
-email" and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:SecurityComplianceCenter and event.category:web and event.action:"User restricted from sending email" and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,19 +70,3 @@ email" and event.outcome:success
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[microsoft-365-user-restricted-from-sending-email-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-an-unusual-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-an-unusual-process.asciidoc
index 7982dd9823..71ba46d50c 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-an-unusual-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-an-unusual-process.asciidoc
@@ -3,72 +3,70 @@
 
 An instance of MSBuild, the Microsoft Build Engine, started a PowerShell script or the Visual C# Command Line Compiler. This technique is sometimes used to deploy a malicious payload using the Build Engine.
 
-*Rule type*: eql
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
-* endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.talosintelligence.com/2020/02/building-bypass-with-msbuild.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
-
-*Version*: 102 (<<microsoft-build-engine-started-an-unusual-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 211
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-The Build Engine is commonly used by Windows developers but use by non-engineers is unusual. If a build system triggers this rule it can be exempted by process, user or host name.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"MSBuild.exe" and process.name : ("csc.exe", "iexplore.exe",
-"powershell.exe")
+[source, js]
 ----------------------------------
+host.os.type:windows and event.category:process and event.type:start and process.parent.name:("MSBuild.exe" or "msbuild.exe") and
+process.name:("csc.exe" or "iexplore.exe" or "powershell.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,60 +78,15 @@ process where event.type == "start" and process.parent.name :
 ** Name: Obfuscated Files or Information
 ** ID: T1027
 ** Reference URL: https://attack.mitre.org/techniques/T1027/
-
-[[microsoft-build-engine-started-an-unusual-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "MSBuild.exe" and process.name : ("csc.exe",
-"iexplore.exe", "powershell.exe")
-----------------------------------
-
-Version 11 (8.4.0 release)::
-* Formatting only
-
-Version 9 (8.2.0 release)::
-* Formatting only
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:MSBuild.exe and process.name:(csc.exe or
-iexplore.exe or powershell.exe)
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.parent.name:MSBuild.exe and process.name:(csc.exe or
-iexplore.exe or powershell.exe)
-----------------------------------
-
+* Sub-technique:
+** Name: Compile After Delivery
+** ID: T1027.004
+** Reference URL: https://attack.mitre.org/techniques/T1027/004/
+* Technique:
+** Name: Trusted Developer Utilities Proxy Execution
+** ID: T1127
+** Reference URL: https://attack.mitre.org/techniques/T1127/
+* Sub-technique:
+** Name: MSBuild
+** ID: T1127.001
+** Reference URL: https://attack.mitre.org/techniques/T1127/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-a-script-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-a-script-process.asciidoc
index 3c7a4b4183..4b514f2bbb 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-a-script-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-a-script-process.asciidoc
@@ -3,69 +3,69 @@
 
 An instance of MSBuild, the Microsoft Build Engine, was started by a script or the Windows command interpreter. This behavior is unusual and is sometimes used by malicious payloads.
 
-*Rule type*: eql
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
-* endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 101 (<<microsoft-build-engine-started-by-a-script-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 209
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-The Build Engine is commonly used by Windows developers but use by non-engineers is unusual.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"MSBuild.exe" or process.pe.original_file_name == "MSBuild.exe") and
-process.parent.name : ("cmd.exe", "powershell.exe", "pwsh.exe",
-"powershell_ise.exe", "cscript.exe", "wscript.exe", "mshta.exe")
+[source, js]
 ----------------------------------
+host.os.type:windows and event.category:process and event.type:start and (
+  process.name.caseless:"msbuild.exe" or process.pe.original_file_name:"MSBuild.exe") and 
+  process.parent.name:("cmd.exe" or "powershell.exe" or "pwsh.exe" or "powershell_ise.exe" or "cscript.exe" or
+    "wscript.exe" or "mshta.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,71 +77,27 @@ process.parent.name : ("cmd.exe", "powershell.exe", "pwsh.exe",
 ** Name: Trusted Developer Utilities Proxy Execution
 ** ID: T1127
 ** Reference URL: https://attack.mitre.org/techniques/T1127/
-
-
+* Sub-technique:
+** Name: MSBuild
+** ID: T1127.001
+** Reference URL: https://attack.mitre.org/techniques/T1127/001/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
 ** Reference URL: https://attack.mitre.org/tactics/TA0002/
-
-[[microsoft-build-engine-started-by-a-script-process-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 13 (8.4.0 release)::
-* Formatting only
-
-Version 11 (8.2.0 release)::
-* Formatting only
-
-Version 10 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"MSBuild.exe" or process.pe.original_file_name == "MSBuild.exe") and
-process.parent.name : ("cmd.exe", "powershell.exe", "cscript.exe",
-"wscript.exe", "mshta.exe")
-----------------------------------
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type: start and
-process.name:MSBuild.exe and process.parent.name:(cmd.exe or
-powershell.exe or cscript.exe or wscript.exe)
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:MSBuild.exe and process.parent.name:(cmd.exe or
-powershell.exe or cscript.exe or wscript.exe) and
-event.action:"Process Create (rule: ProcessCreate)"
-----------------------------------
-
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
+* Sub-technique:
+** Name: Visual Basic
+** ID: T1059.005
+** Reference URL: https://attack.mitre.org/techniques/T1059/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-a-system-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-a-system-process.asciidoc
index 99bc69557f..1e6b4cb6bb 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-a-system-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-a-system-process.asciidoc
@@ -5,65 +5,69 @@ An instance of MSBuild, the Microsoft Build Engine, was started by Explorer or t
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<microsoft-build-engine-started-by-a-system-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-The Build Engine is commonly used by Windows developers but use by non-engineers is unusual.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "MSBuild.exe"
-and process.parent.name : ("explorer.exe", "wmiprvse.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "MSBuild.exe" and
+  process.parent.name : ("explorer.exe", "wmiprvse.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,69 +79,11 @@ and process.parent.name : ("explorer.exe", "wmiprvse.exe")
 ** Name: Trusted Developer Utilities Proxy Execution
 ** ID: T1127
 ** Reference URL: https://attack.mitre.org/techniques/T1127/
-
-
+* Sub-technique:
+** Name: MSBuild
+** ID: T1127.001
+** Reference URL: https://attack.mitre.org/techniques/T1127/001/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
 ** Reference URL: https://attack.mitre.org/tactics/TA0002/
-
-[[microsoft-build-engine-started-by-a-system-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "MSBuild.exe" and process.parent.name :
-("explorer.exe", "wmiprvse.exe")
-----------------------------------
-
-Version 12 (8.4.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 9 (7.16.0 release)::
-* Formatting only
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:MSBuild.exe and process.parent.name:(explorer.exe or
-wmiprvse.exe)
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:MSBuild.exe and process.parent.name:(explorer.exe or
-wmiprvse.exe) and event.action:"Process Create (rule: ProcessCreate)"
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-an-office-application.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-an-office-application.asciidoc
index 4d7a157821..92a312854d 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-an-office-application.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-started-by-an-office-application.asciidoc
@@ -5,81 +5,73 @@ An instance of MSBuild, the Microsoft Build Engine, was started by Excel or Word
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.talosintelligence.com/2020/02/building-bypass-with-msbuild.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 110
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
 
-*Version*: 102 (<<microsoft-build-engine-started-by-an-office-application-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.7.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-The Build Engine is commonly used by Windows developers but use by non-engineers is unusual. It is quite unusual for this program to be started by an Office application like Word or Excel.
 
-==== Investigation guide
 
+*Investigating Microsoft Build Engine Started by an Office Application*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Microsoft Build Engine Started by an Office Application
+Microsoft Office (MS Office) is a suite of applications designed to help with productivity and completing common tasks on a computer. You can create and edit documents containing text and images, work with data in spreadsheets and databases, and create presentations and posters. As it is some of the most-used software across companies, MS Office is frequently targeted for initial access. It also has a wide variety of capabilities that attackers can take advantage of.
+
+The Microsoft Build Engine is a platform for building applications. This engine, also known as MSBuild, provides an XML schema for a project file that controls how the build platform processes and builds software, and can be abused to proxy execution of code.
 
-Microsoft Office (MS Office) is a suite of applications designed to help with productivity and completing common tasks on a computer.
-You can create and edit documents containing text and images, work with data in spreadsheets and databases, and create
-presentations and posters. As it is some of the most-used software across companies, MS Office is frequently targeted
-for initial access. It also has a wide variety of capabilities that attackers can take advantage of.
+This rule looks for the `Msbuild.exe` utility spawned by MS Office programs. This is generally the result of the execution of malicious documents.
 
-The Microsoft Build Engine is a platform for building applications. This engine, also known as MSBuild, provides an XML
-schema for a project file that controls how the build platform processes and builds software, and can be abused to proxy
-execution of code.
 
-This rule looks for the `Msbuild.exe` utility spawned by MS Office programs. This is generally the result of the
-execution of malicious documents.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file
-modifications, and any spawned child processes.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Retrieve MS Office documents received and opened by the user that could cause this behavior. Common locations include,
-but are not limited to, the Downloads and Document folders and the folder configured at the email client.
+- Retrieve MS Office documents received and opened by the user that could cause this behavior. Common locations include, but are not limited to, the Downloads and Document folders and the folder configured at the email client.
 - Determine if the collected files are malicious:
   - Use a private sandboxed malware analysis system to perform analysis.
     - Observe and collect information about the following activities:
@@ -90,51 +82,66 @@ but are not limited to, the Downloads and Document folders and the folder config
   - Use the PowerShell Get-FileHash cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - If the triage identified malware, search the environment for additional compromised hosts.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system,
-persistence mechanisms, and malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
   - If the malicious file was delivered via phishing:
     - Block the email sender from sending future emails.
     - Block the malicious web pages.
     - Remove emails from the sender from mailboxes.
     - Consider improvements to the security awareness program.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "MSBuild.exe"
-and process.parent.name : ("eqnedt32.exe",
-"excel.exe", "fltldr.exe",
-"msaccess.exe", "mspub.exe",
-"outlook.exe", "powerpnt.exe",
-"winword.exe" )
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "MSBuild.exe" and
+  process.parent.name : ("eqnedt32.exe",
+                         "excel.exe",
+                         "fltldr.exe",
+                         "msaccess.exe",
+                         "mspub.exe",
+                         "outlook.exe",
+                         "powerpnt.exe",
+                         "winword.exe" )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -146,75 +153,11 @@ and process.parent.name : ("eqnedt32.exe",
 ** Name: Trusted Developer Utilities Proxy Execution
 ** ID: T1127
 ** Reference URL: https://attack.mitre.org/techniques/T1127/
-
-
+* Sub-technique:
+** Name: MSBuild
+** ID: T1127.001
+** Reference URL: https://attack.mitre.org/techniques/T1127/001/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
 ** Reference URL: https://attack.mitre.org/tactics/TA0002/
-
-[[microsoft-build-engine-started-by-an-office-application-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "MSBuild.exe" and process.parent.name :
-("eqnedt32.exe", "excel.exe",
-"fltldr.exe", "msaccess.exe",
-"mspub.exe", "outlook.exe",
-"powerpnt.exe", "winword.exe" )
-----------------------------------
-
-Version 12 (8.4.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 9 (7.16.0 release)::
-* Formatting only
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:MSBuild.exe and process.parent.name:(eqnedt32.exe or
-excel.exe or fltldr.exe or msaccess.exe or mspub.exe or outlook.exe or
-powerpnt.exe or winword.exe)
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:MSBuild.exe and process.parent.name:(eqnedt32.exe or
-excel.exe or fltldr.exe or msaccess.exe or mspub.exe or outlook.exe or
-powerpnt.exe or winword.exe) and event.action: "Process Create (rule:
-ProcessCreate)"
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-using-an-alternate-name.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-using-an-alternate-name.asciidoc
index 259125a243..8ce2eadee4 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-using-an-alternate-name.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-build-engine-using-an-alternate-name.asciidoc
@@ -5,151 +5,154 @@ An instance of MSBuild, the Microsoft Build Engine, was started after being rena
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<microsoft-build-engine-using-an-alternate-name-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-The Build Engine is commonly used by Windows developers but use by non-engineers is unusual.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Microsoft Build Engine Using an Alternate Name*
 
-[source,js]
-----------------------------------
-process where event.type == "start" and
-process.pe.original_file_name == "MSBuild.exe" and not process.name
-: "MSBuild.exe"
-----------------------------------
 
-==== Threat mapping
+The OriginalFileName attribute of a PE (Portable Executable) file is a metadata field that contains the original name of the executable file when compiled or linked. By using this attribute, analysts can identify renamed instances that attackers can use with the intent of evading detections, application allowlists, and other security protections.
 
-*Framework*: MITRE ATT&CK^TM^
+The Microsoft Build Engine is a platform for building applications. This engine, also known as MSBuild, provides an XML schema for a project file that controls how the build platform processes and builds software, and can be abused to proxy execution of code.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Masquerading
-** ID: T1036
-** Reference URL: https://attack.mitre.org/techniques/T1036/
+This rule checks for renamed instances of MSBuild, which can indicate an attempt of evading detections, application allowlists, and other security protections.
 
-[[microsoft-build-engine-using-an-alternate-name-history]]
-==== Rule version history
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.pe.original_file_name == "MSBuild.exe" and not process.name
-: "MSBuild.exe"
-----------------------------------
+*Possible investigation steps*
 
-Version 12 (8.4.0 release)::
-* Formatting only
 
-Version 10 (8.2.0 release)::
-* Formatting only
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-Version 9 (7.16.0 release)::
-* Formatting only
 
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.pe.original_file_name:MSBuild.exe and not process.name:
-MSBuild.exe
-----------------------------------
+*False positive analysis*
 
-Version 7 (7.12.0 release)::
-* Formatting only
 
-Version 6 (7.11.2 release)::
-* Formatting only
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-Version 5 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-(process.pe.original_file_name:MSBuild.exe or
-winlog.event_data.OriginalFileName:MSBuild.exe) and not process.name:
-MSBuild.exe
-----------------------------------
 
-Version 4 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-(pe.original_file_name:MSBuild.exe or
-winlog.event_data.OriginalFileName:MSBuild.exe) and not process.name:
-MSBuild.exe
-----------------------------------
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
 
-Version 3 (7.9.1 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-(pe.original_file_name:MSBuild.exe or
-winlog.event_data.OriginalFileName: MSBuild.exe) and not process.name:
-MSBuild.exe and event.action: "Process Create (rule: ProcessCreate)"
+process where host.os.type == "windows" and event.type == "start" and
+  process.pe.original_file_name == "MSBuild.exe" and
+  not process.name : "MSBuild.exe"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Rename System Utilities
+** ID: T1036.003
+** Reference URL: https://attack.mitre.org/techniques/T1036/003/
+* Technique:
+** Name: Trusted Developer Utilities Proxy Execution
+** ID: T1127
+** Reference URL: https://attack.mitre.org/techniques/T1127/
+* Sub-technique:
+** Name: MSBuild
+** ID: T1127.001
+** Reference URL: https://attack.mitre.org/techniques/T1127/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-server-um-spawning-suspicious-processes.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-server-um-spawning-suspicious-processes.asciidoc
index c4c9089cea..7bf57ed14a 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-server-um-spawning-suspicious-processes.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-server-um-spawning-suspicious-processes.asciidoc
@@ -5,74 +5,83 @@ Identifies suspicious processes being spawned by the Microsoft Exchange Server U
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.microsoft.com/security/blog/2021/03/02/hafnium-targeting-exchange-servers
 * https://www.volexity.com/blog/2021/03/02/active-exploitation-of-microsoft-exchange-zero-day-vulnerabilities
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Initial Access
-
-*Version*: 100 (<<microsoft-exchange-server-um-spawning-suspicious-processes-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Lateral Movement
+* Data Source: Elastic Endgame
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Legitimate processes may be spawned from the Microsoft Exchange Server Unified Messaging (UM) service. If known processes are causing false positives, they can be exempted from the rule.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-("UMService.exe", "UMWorkerProcess.exe") and not
-process.executable :
-("?:\\Windows\\System32\\werfault.exe",
-"?:\\Windows\\System32\\wermgr.exe", "?:\\Program
-Files\\Microsoft\\Exchange Server\\V??\\Bin\\UMWorkerProcess.exe",
-"D:\\Exchange 2016\\Bin\\UMWorkerProcess.exe",
-"E:\\ExchangeServer\\Bin\\UMWorkerProcess.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : ("UMService.exe", "UMWorkerProcess.exe") and
+    not process.executable :
+              ("?:\\Windows\\System32\\werfault.exe",
+               "?:\\Windows\\System32\\wermgr.exe",
+               "?:\\Program Files\\Microsoft\\Exchange Server\\V??\\Bin\\UMWorkerProcess.exe",
+               "?:\\Program Files\\Microsoft\\Exchange Server\\Bin\\UMWorkerProcess.exe",
+               "D:\\Exchange 2016\\Bin\\UMWorkerProcess.exe",
+               "E:\\ExchangeServer\\Bin\\UMWorkerProcess.exe",
+               "D:\\Exchange\\Bin\\UMWorkerProcess.exe",
+               "D:\\Exchange Server\\Bin\\UMWorkerProcess.exe",
+               "E:\\Exchange Server\\V15\\Bin\\UMWorkerProcess.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,23 +93,11 @@ Files\\Microsoft\\Exchange Server\\V??\\Bin\\UMWorkerProcess.exe",
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[microsoft-exchange-server-um-spawning-suspicious-processes-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-("UMService.exe", "UMWorkerProcess.exe") and not process.name :
-("werfault.exe", "wermgr.exe")
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-server-um-writing-suspicious-files.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-server-um-writing-suspicious-files.asciidoc
index 59988980f8..492f4ab6f0 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-server-um-writing-suspicious-files.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-server-um-writing-suspicious-files.asciidoc
@@ -5,87 +5,99 @@ Identifies suspicious files being written by the Microsoft Exchange Server Unifi
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.microsoft.com/security/blog/2021/03/02/hafnium-targeting-exchange-servers
 * https://www.volexity.com/blog/2021/03/02/active-exploitation-of-microsoft-exchange-zero-day-vulnerabilities
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Initial Access
-
-*Version*: 100 (<<microsoft-exchange-server-um-writing-suspicious-files-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Lateral Movement
+* Data Source: Elastic Endgame
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Files generated during installation will generate a lot of noise, so the rule should only be enabled after the fact.
-This rule was tuned using the following baseline: https://raw.githubusercontent.com/microsoft/CSS-Exchange/main/Security/Baselines/baseline_15.2.792.5.csv from Microsoft. Depending on version, consult https://github.com/microsoft/CSS-Exchange/tree/main/Security/Baselines to help determine normalcy.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-Positive hits can be checked against the established Microsoft [baselines](https://github.com/microsoft/CSS-Exchange/tree/main/Security/Baselines).
+*Triage and analysis*
+
+
+Positive hits can be checked against the established Microsoft https://github.com/microsoft/CSS-Exchange/tree/main/Security/Baselines[baselines].
 
 Microsoft highly recommends that the best course of action is patching, but this may not protect already compromised systems
 from existing intrusions. Other tools for detecting and mitigating can be found within their Exchange support
-[repository](https://github.com/microsoft/CSS-Exchange/tree/main/Security)
-----------------------------------
+https://github.com/microsoft/CSS-Exchange/tree/main/Security[repository]
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type == "creation" and process.name :
-("UMWorkerProcess.exe", "umservice.exe") and file.extension :
-("php", "jsp", "js", "aspx", "asmx", "asax", "cfm", "shtml") and (
-file.path : "?:\\inetpub\\wwwroot\\aspnet_client\\*" or
-(file.path : "?:\\*\\Microsoft\\Exchange
-Server*\\FrontEnd\\HttpProxy\\owa\\auth\\*" and not (file.path
-: "?:\\*\\Microsoft\\Exchange
-Server*\\FrontEnd\\HttpProxy\\owa\\auth\\version\\*" or
-file.name : ("errorFE.aspx", "expiredpassword.aspx", "frowny.aspx",
-"GetIdToken.htm", "logoff.aspx", "logon.aspx",
-"OutlookCN.aspx", "RedirSuiteServiceProxy.aspx", "signout.aspx"))) or
-(file.path : "?:\\*\\Microsoft\\Exchange
-Server*\\FrontEnd\\HttpProxy\\ecp\\auth\\*" and not file.name :
-"TimeoutLogoff.aspx") )
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and
+  process.name : ("UMWorkerProcess.exe", "umservice.exe") and
+  file.extension : ("php", "jsp", "js", "aspx", "asmx", "asax", "cfm", "shtml") and
+  (
+    file.path : "?:\\inetpub\\wwwroot\\aspnet_client\\*" or
+
+    (file.path : "?:\\*\\Microsoft\\Exchange Server*\\FrontEnd\\HttpProxy\\owa\\auth\\*" and
+       not (file.path : "?:\\*\\Microsoft\\Exchange Server*\\FrontEnd\\HttpProxy\\owa\\auth\\version\\*" or
+            file.name : ("errorFE.aspx", "expiredpassword.aspx", "frowny.aspx", "GetIdToken.htm", "logoff.aspx",
+                        "logon.aspx", "OutlookCN.aspx", "RedirSuiteServiceProxy.aspx", "signout.aspx"))) or
 
-==== Threat mapping
+    (file.path : "?:\\*\\Microsoft\\Exchange Server*\\FrontEnd\\HttpProxy\\ecp\\auth\\*" and
+       not file.name : "TimeoutLogoff.aspx")
+  )
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -97,30 +109,11 @@ Server*\\FrontEnd\\HttpProxy\\ecp\\auth\\*" and not file.name :
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[microsoft-exchange-server-um-writing-suspicious-files-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type == "creation" and process.parent.name :
-("UMWorkerProcess.exe", "umservice.exe") and file.extension :
-("php", "jsp", "js", "aspx", "asmx", "asax", "cfm", "shtml") and (
-file.path : ("C:\\inetpub\\wwwroot\\aspnet_client\\*",
-"C:\\*\\FrontEnd\\HttpProxy\\owa\\auth\\*") or (file.path :
-"C:\\*\\FrontEnd\\HttpProxy\\ecp\\auth\\*" and not file.name :
-"TimeoutLogoff.aspx") )
-----------------------------------
-
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-transport-agent-install-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-transport-agent-install-script.asciidoc
new file mode 100644
index 0000000000..a5d8ab5515
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-transport-agent-install-script.asciidoc
@@ -0,0 +1,110 @@
+[[microsoft-exchange-transport-agent-install-script]]
+=== Microsoft Exchange Transport Agent Install Script
+
+Identifies the use of Cmdlets and methods related to Microsoft Exchange Transport Agents install. Adversaries may leverage malicious Microsoft Exchange Transport Agents to execute tasks in response to adversary-defined criteria, establishing persistence.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: PowerShell Logs
+* Rule Type: BBR
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+Steps to implement the logging policy via registry:
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category: "process" and host.os.type:windows and
+  powershell.file.script_block_text : (
+    (
+    "Install-TransportAgent" or
+    "Enable-TransportAgent"
+    )
+  ) and
+  not user.id : "S-1-5-18" and
+  not powershell.file.script_block_text : (
+    "'Install-TransportAgent', 'Invoke-MonitoringProbe', 'Mount-Database', 'Move-ActiveMailboxDatabase'," or
+    "'Enable-TransportAgent', 'Enable-TransportRule', 'Export-ActiveSyncLog', 'Export-AutoDiscoverConfig'," or
+    ("scriptCmd.GetSteppablePipeline" and "ForwardHelpTargetName Install-TransportAgent")
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Server Software Component
+** ID: T1505
+** Reference URL: https://attack.mitre.org/techniques/T1505/
+* Sub-technique:
+** Name: Transport Agent
+** ID: T1505.002
+** Reference URL: https://attack.mitre.org/techniques/T1505/002/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-worker-spawning-suspicious-processes.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-worker-spawning-suspicious-processes.asciidoc
index 4e20123792..4bad1f231d 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-worker-spawning-suspicious-processes.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-exchange-worker-spawning-suspicious-processes.asciidoc
@@ -5,68 +5,74 @@ Identifies suspicious processes being spawned by the Microsoft Exchange Server w
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.microsoft.com/security/blog/2021/03/02/hafnium-targeting-exchange-servers
 * https://www.volexity.com/blog/2021/03/02/active-exploitation-of-microsoft-exchange-zero-day-vulnerabilities
 * https://discuss.elastic.co/t/detection-and-response-for-hafnium-activity/266289
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Initial Access
-
-*Version*: 100 (<<microsoft-exchange-worker-spawning-suspicious-processes-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"w3wp.exe" and process.parent.args : "MSExchange*AppPool" and
-(process.name : ("cmd.exe", "powershell.exe", "pwsh.exe",
-"powershell_ise.exe") or process.pe.original_file_name in
-("cmd.exe", "powershell.exe", "pwsh.dll", "powershell_ise.exe"))
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : "w3wp.exe" and process.parent.args : "MSExchange*AppPool" and
+  (process.name : ("cmd.exe", "powershell.exe", "pwsh.exe", "powershell_ise.exe") or
+  ?process.pe.original_file_name in ("cmd.exe", "powershell.exe", "pwsh.dll", "powershell_ise.exe"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,28 +84,19 @@ process where event.type == "start" and process.parent.name :
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[microsoft-exchange-worker-spawning-suspicious-processes-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"w3wp.exe" and process.parent.args : "MSExchange*AppPool" and
-(process.name : ("cmd.exe", "powershell.exe", "pwsh.exe") or
-process.pe.original_file_name : ("cmd.exe", "powershell.exe",
-"pwsh.exe"))
-----------------------------------
-
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-iis-connection-strings-decryption.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-iis-connection-strings-decryption.asciidoc
index 59ab538c0e..4cd54013d1 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-iis-connection-strings-decryption.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-iis-connection-strings-decryption.asciidoc
@@ -5,68 +5,71 @@ Identifies use of aspnet_regiis to decrypt Microsoft IIS connection strings. An
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 33
 
-*References*:
+*References*: 
 
 * https://blog.netspi.com/decrypting-iis-passwords-to-break-out-of-the-dmz-part-1/
 * https://symantec-enterprise-blogs.security.com/blogs/threat-intelligence/greenbug-espionage-telco-south-asia
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Elastic Endgame
-
-*Version*: 102 (<<microsoft-iis-connection-strings-decryption-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"aspnet_regiis.exe" or process.pe.original_file_name ==
-"aspnet_regiis.exe") and process.args : "connectionStrings" and
-process.args : "-pdf"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "aspnet_regiis.exe" or ?process.pe.original_file_name == "aspnet_regiis.exe") and
+  process.args : "connectionStrings" and process.args : "-pdf"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,45 +81,3 @@ process.args : "-pdf"
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[microsoft-iis-connection-strings-decryption-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "aspnet_regiis.exe" or process.pe.original_file_name
-== "aspnet_regiis.exe") and process.args : "connectionStrings" and
-process.args : "-pdf"
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-(process.name:aspnet_regiis.exe or
-process.pe.original_file_name:aspnet_regiis.exe or
-winlog.event_data.OriginalFileName:aspnet_regiis.exe) and
-process.args:(connectionStrings and "-pdf")
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-iis-service-account-password-dumped.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-iis-service-account-password-dumped.asciidoc
index b108f4bcaa..61c28c916b 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-iis-service-account-password-dumped.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-iis-service-account-password-dumped.asciidoc
@@ -5,66 +5,70 @@ Identifies the Internet Information Services (IIS) command-line tool, AppCmd, be
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 33
 
-*References*:
+*References*: 
 
 * https://blog.netspi.com/decrypting-iis-passwords-to-break-out-of-the-dmz-part-1/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Elastic Endgame
-
-*Version*: 102 (<<microsoft-iis-service-account-password-dumped-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"appcmd.exe" or process.pe.original_file_name == "appcmd.exe") and
-process.args : "/list" and process.args : "/text*password"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+   (process.name : "appcmd.exe" or ?process.pe.original_file_name == "appcmd.exe") and
+   process.args : "/list" and process.args : "/text*password"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,53 +80,3 @@ process.args : "/list" and process.args : "/text*password"
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[microsoft-iis-service-account-password-dumped-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "appcmd.exe" or process.pe.original_file_name ==
-"appcmd.exe") and process.args : "/list" and process.args :
-"/text*password"
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "appcmd.exe" or process.pe.original_file_name ==
-"appcmd.exe") and process.args : "/list" and process.args :
-"/text*password"
-----------------------------------
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process AND event.type:(start OR process_started) AND
-(process.name:appcmd.exe OR process.pe.original_file_name:appcmd.exe
-or winlog.event_data.OriginalFileName:appcmd.exe) AND
-process.args:(/[lL][iI][sS][tT]/ AND
-/\/[tT][eE][xX][tT]\:[pP][aA][sS][sS][wW][oO][rR][dD]/)
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/microsoft-windows-defender-tampering.asciidoc b/docs/detections/prebuilt-rules/rule-details/microsoft-windows-defender-tampering.asciidoc
index 7c29913f50..045e981903 100644
--- a/docs/detections/prebuilt-rules/rule-details/microsoft-windows-defender-tampering.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/microsoft-windows-defender-tampering.asciidoc
@@ -5,23 +5,23 @@ Identifies when one or more features on Microsoft Defender are disabled. Adversa
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://thedfirreport.com/2021/10/18/icedid-to-xinglocker-ransomware-in-24-hours/
 * https://www.tenforums.com/tutorials/32236-enable-disable-microsoft-defender-pua-protection-windows-10-a.html
@@ -32,135 +32,128 @@ Identifies when one or more features on Microsoft Defender are disabled. Adversa
 * https://www.tenforums.com/tutorials/3569-turn-off-real-time-protection-microsoft-defender-antivirus.html
 * https://www.tenforums.com/tutorials/99576-how-schedule-scan-microsoft-defender-antivirus-windows-10-a.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Version*: 102 (<<microsoft-windows-defender-tampering-history, version history>>)
+*Version*: 110
 
-*Added ({stack} release)*: 8.0.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Legitimate Windows Defender configuration changes
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Microsoft Windows Defender Tampering
+*Triage and analysis*
+
+
+
+*Investigating Microsoft Windows Defender Tampering*
 
-Microsoft Windows Defender is an antivirus product built into Microsoft Windows, which makes it popular across multiple
-environments. Disabling it is a common step in threat actor playbooks.
+
+Microsoft Windows Defender is an antivirus product built into Microsoft Windows, which makes it popular across multiple environments. Disabling it is a common step in threat actor playbooks.
 
 This rule monitors the registry for modifications that disable Windows Defender features.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate
-software installations.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Examine which features have been disabled, and check if this operation is done under change management and approved
-according to the organization's policy.
+- Examine which features have been disabled, and check if this operation is done under change management and approved according to the organization's policy.
+
+
+*False positive analysis*
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity,
-the configuration is justified (for example, it is being used to deploy other security solutions or troubleshooting),
-and no other suspicious activity has been observed.
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity, the configuration is justified (for example, it is being used to deploy other security solutions or troubleshooting), and no other suspicious activity has been observed.
+
+
+*Related rules*
 
-### Related rules
 
 - Windows Defender Disabled via Registry Modification - 2ffa1f1e-b6db-47fa-994b-1512743847eb
 - Disabling Windows Defender Security Settings via PowerShell - c8cccb06-faf2-4cd5-886e-2c9636cfcb87
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Take actions to restore the appropriate Windows Defender antivirus configurations.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Review the privileges assigned to the user to ensure that the least privilege principle is being followed.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-(registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\PUAProtection" and registry.data.strings : ("0",
-"0x00000000")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender Security
-Center\\App and Browser protection\\DisallowExploitProtectionOverride"
-and registry.data.strings : ("0", "0x00000000")) or (registry.path
-: "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\DisableAntiSpyware" and registry.data.strings : ("1",
-"0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\Features\\TamperProtection" and registry.data.strings :
-("0", "0x00000000")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableRealtimeMonitoring" and registry.data.strings :
-("1", "0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableIntrusionPreventionSystem" and
-registry.data.strings : ("1", "0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableScriptScanning" and registry.data.strings : ("1",
-"0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Windows
-Defender Exploit Guard\\Controlled Folder
-Access\\EnableControlledFolderAccess" and registry.data.strings :
-("0", "0x00000000")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableIOAVProtection" and registry.data.strings : ("1",
-"0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\Reporting\\DisableEnhancedNotifications" and
-registry.data.strings : ("1", "0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\SpyNet\\DisableBlockAtFirstSeen" and registry.data.strings
-: ("1", "0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\SpyNet\\SpynetReporting" and registry.data.strings : ("0",
-"0x00000000")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\SpyNet\\SubmitSamplesConsent" and registry.data.strings :
-("0", "0x00000000")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableBehaviorMonitoring" and registry.data.strings :
-("1", "0x00000001"))
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type in ("creation", "change") and
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\PUAProtection" and
+  registry.data.strings : ("0", "0x00000000")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender Security Center\\App and Browser protection\\DisallowExploitProtectionOverride" and
+  registry.data.strings : ("0", "0x00000000")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\DisableAntiSpyware" and
+  registry.data.strings : ("1", "0x00000001")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Features\\TamperProtection" and
+  registry.data.strings : ("0", "0x00000000")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time Protection\\DisableRealtimeMonitoring" and
+  registry.data.strings : ("1", "0x00000001")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time Protection\\DisableIntrusionPreventionSystem" and
+  registry.data.strings : ("1", "0x00000001")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time Protection\\DisableScriptScanning" and
+  registry.data.strings : ("1", "0x00000001")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Windows Defender Exploit Guard\\Controlled Folder Access\\EnableControlledFolderAccess" and
+  registry.data.strings : ("0", "0x00000000")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time Protection\\DisableIOAVProtection" and
+  registry.data.strings : ("1", "0x00000001")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Reporting\\DisableEnhancedNotifications" and
+  registry.data.strings : ("1", "0x00000001")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\SpyNet\\DisableBlockAtFirstSeen" and
+  registry.data.strings : ("1", "0x00000001")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\SpyNet\\SpynetReporting" and
+  registry.data.strings : ("0", "0x00000000")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\SpyNet\\SubmitSamplesConsent" and
+  registry.data.strings : ("0", "0x00000000")) or
+  (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time Protection\\DisableBehaviorMonitoring" and
+  registry.data.strings : ("1", "0x00000001"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -172,117 +165,7 @@ Protection\\DisableBehaviorMonitoring" and registry.data.strings :
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[microsoft-windows-defender-tampering-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-(registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\PUAProtection" and registry.data.strings : ("0",
-"0x00000000")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender Security
-Center\\App and Browser protection\\DisallowExploitProtectionOverride"
-and registry.data.strings : ("1", "0x00000001")) or (registry.path
-: "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\DisableAntiSpyware" and registry.data.strings : ("1",
-"0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\Features\\TamperProtection" and registry.data.strings :
-("0", "0x00000000")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableRealtimeMonitoring" and registry.data.strings :
-("1", "0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableIntrusionPreventionSystem" and
-registry.data.strings : ("1", "0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableScriptScanning" and registry.data.strings : ("1",
-"0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Windows
-Defender Exploit Guard\\Controlled Folder
-Access\\EnableControlledFolderAccess" and registry.data.strings :
-("0", "0x00000000")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableIOAVProtection" and registry.data.strings : ("1",
-"0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\Reporting\\DisableEnhancedNotifications" and
-registry.data.strings : ("1", "0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\SpyNet\\DisableBlockAtFirstSeen" and registry.data.strings
-: ("1", "0x00000001")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\SpyNet\\SpynetReporting" and registry.data.strings : ("0",
-"0x00000000")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\SpyNet\\SubmitSamplesConsent" and registry.data.strings :
-("0", "0x00000000")) or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableBehaviorMonitoring" and registry.data.strings :
-("1", "0x00000001"))
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-(registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\PUAProtection" and registry.data.strings : "0") or
-(registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender Security Center\\App and Browser
-protection\\DisallowExploitProtectionOverride" and
-registry.data.strings : "1") or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\DisableAntiSpyware" and registry.data.strings : "1") or
-(registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\Features\\TamperProtection" and registry.data.strings :
-"0") or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableRealtimeMonitoring" and registry.data.strings :
-"1") or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableIntrusionPreventionSystem" and
-registry.data.strings : "1") or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableScriptScanning" and registry.data.strings : "1")
-or (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\Windows Defender Exploit Guard\\Controlled Folder
-Access\\EnableControlledFolderAccess" and registry.data.strings :
-"0") or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableIOAVProtection" and registry.data.strings : "1")
-or (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\Reporting\\DisableEnhancedNotifications" and
-registry.data.strings : "1") or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\SpyNet\\DisableBlockAtFirstSeen" and registry.data.strings
-: "1") or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\SpyNet\\SpynetReporting" and registry.data.strings : "0")
-or (registry.path : "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\SpyNet\\SubmitSamplesConsent" and registry.data.strings :
-"0") or (registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Real-Time
-Protection\\DisableBehaviorMonitoring" and registry.data.strings :
-"1")
-----------------------------------
-
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/mimikatz-memssp-log-file-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/mimikatz-memssp-log-file-detected.asciidoc
index a8bdc4e8d1..1ee3343f02 100644
--- a/docs/detections/prebuilt-rules/rule-details/mimikatz-memssp-log-file-detected.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/mimikatz-memssp-log-file-detected.asciidoc
@@ -5,116 +5,126 @@ Identifies the password log file from the default Mimikatz memssp module.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<mimikatz-memssp-log-file-detected-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Mimikatz Memssp Log File Detected
+*Triage and analysis*
+
+
+
+*Investigating Mimikatz Memssp Log File Detected*
+
+
+https://github.com/gentilkiwi/mimikatz[Mimikatz] is an open-source tool used to collect, decrypt, and/or use cached credentials. This tool is commonly abused by adversaries during the post-compromise stage where adversaries have gained an initial foothold on an endpoint and are looking to elevate privileges and seek out additional authentication objects such as tokens/hashes/credentials that can then be used to laterally move and pivot across a network.
+
+This rule looks for the creation of a file named `mimilsa.log`, which is generated when using the Mimikatz misc::memssp module, which injects a malicious Windows SSP to collect locally authenticated credentials, which includes the computer account password, running service credentials, and any accounts that logon.
 
-[Mimikatz](https://github.com/gentilkiwi/mimikatz) is an open-source tool used to collect, decrypt, and/or use cached
-credentials. This tool is commonly abused by adversaries during the post-compromise stage where adversaries have gained
-an initial foothold on an endpoint and are looking to elevate privileges and seek out additional authentication objects
-such as tokens/hashes/credentials that can then be used to laterally move and pivot across a network.
 
-This rule looks for the creation of a file named `mimilsa.log`, which is generated when using the Mimikatz misc::memssp
-module, which injects a malicious Windows SSP to collect locally authenticated credentials, which includes the computer
-account password, running service credentials, and any accounts that logon.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate potentially compromised accounts. Analysts can do this by searching for login events (e.g., 4624) to the target
-host.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (e.g., 4624) to the target host.
 - Retrieve and inspect the log file contents.
 - Search for DLL files created in the same location as the log file, and retrieve unsigned DLLs.
   - Use the PowerShell Get-FileHash cmdlet to get the SHA-256 hash value of these files.
     - Search for the existence of these files in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
   - Identify the process that created the DLL using file creation events.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This file name `mimilsa.log` should not legitimately be created.
 
-### Related rules
+
+*Related rules*
+
 
 - Mimikatz Powershell Module Activity - ac96ceb8-4399-4191-af1d-4feeac1f1f46
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - If the host is a Domain Controller (DC):
   - Activate your incident response plan for total Active Directory compromise.
-  - Review the privileges assigned to users that can access the DCs to ensure that the least privilege principle is
-  being followed and reduce the attack surface.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+  - Review the privileges assigned to users that can access the DCs to ensure that the least privilege principle is being followed and reduce the attack surface.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Reboot the host to remove the injected SSP from memory.
 - Reimage the host operating system or restore compromised files to clean versions.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where file.name : "mimilsa.log" and process.name : "lsass.exe"
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and file.name : "mimilsa.log" and process.name : "lsass.exe"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -126,37 +136,3 @@ file where file.name : "mimilsa.log" and process.name : "lsass.exe"
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[mimikatz-memssp-log-file-detected-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and file.name:mimilsa.log and
-process.name:lsass.exe
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/modification-of-amsienable-registry-key.asciidoc b/docs/detections/prebuilt-rules/rule-details/modification-of-amsienable-registry-key.asciidoc
index 7e77f03ab6..abc0cbd0fd 100644
--- a/docs/detections/prebuilt-rules/rule-details/modification-of-amsienable-registry-key.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/modification-of-amsienable-registry-key.asciidoc
@@ -5,71 +5,71 @@ Identifies modifications of the AmsiEnable registry key to 0, which disables the
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://hackinparis.com/data/slides/2019/talks/HIP2019-Dominic_Chell-Cracking_The_Perimeter_With_Sharpshooter.pdf
 * https://docs.microsoft.com/en-us/windows/win32/amsi/antimalware-scan-interface-portal
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<modification-of-amsienable-registry-key-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Modification of AmsiEnable Registry Key
+*Triage and analysis*
+
 
-The Windows Antimalware Scan Interface (AMSI) is a versatile interface standard that allows your applications and
-services to integrate with any antimalware product that's present on a machine. AMSI provides integration with multiple
-Windows components, ranging from User Account Control (UAC) to VBA Macros.
 
-Since AMSI is widely used across security products for increased visibility, attackers can disable it to evade
-detections that rely on it.
+*Investigating Modification of AmsiEnable Registry Key*
+
+
+The Windows Antimalware Scan Interface (AMSI) is a versatile interface standard that allows your applications and services to integrate with any antimalware product on a machine. AMSI integrates with multiple Windows components, ranging from User Account Control (UAC) to VBA macros and PowerShell.
+
+Since AMSI is widely used across security products for increased visibility, attackers can disable it to evade detections that rely on it.
 
 This rule monitors the modifications to the Software\Microsoft\Windows Script\Settings\AmsiEnable registry key.
 
-#### Possible investigation steps
+
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Investigate the execution of scripts and macros after the registry modification.
 - Retrieve scripts or Microsoft Office files and determine if they are malicious:
@@ -83,16 +83,21 @@ for prevalence, whether they are located in expected locations, and if they are
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 - Use process name, command line, and file hash to search for occurrences on other hosts.
 
-### False positive analysis
 
-- This modification should not happen legitimately. Any potential benign true positive (B-TP) should be mapped and
-monitored by the security team, as these modifications expose the host to malware infections.
+*False positive analysis*
+
+
+- This modification should not happen legitimately. Any potential benign true positive (B-TP) should be mapped and monitored by the security team as these modifications expose the host to malware infections.
+
+
+*Related rules*
 
-### Related rules
 
 - Microsoft Windows Defender Tampering - fe794edd-487f-4a90-b285-3ee54f2af2d3
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
@@ -100,33 +105,42 @@ monitored by the security team, as these modifications expose the host to malwar
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Delete or set the key to its default value.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-registry.path : ( "HKEY_USERS\\*\\Software\\Microsoft\\Windows
-Script\\Settings\\AmsiEnable",
-"HKU\\*\\Software\\Microsoft\\Windows Script\\Settings\\AmsiEnable",
-"\\REGISTRY\\USER\\*\\Software\\Microsoft\\Windows
-Script\\Settings\\AmsiEnable" ) and registry.data.strings: ("0",
-"0x00000000")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type in ("creation", "change") and
+  registry.path : (
+    "HKEY_USERS\\*\\Software\\Microsoft\\Windows Script\\Settings\\AmsiEnable",
+    "HKU\\*\\Software\\Microsoft\\Windows Script\\Settings\\AmsiEnable",
+    "\\REGISTRY\\USER\\*\\Software\\Microsoft\\Windows Script\\Settings\\AmsiEnable"
+  ) and
+  registry.data.strings: ("0", "0x00000000")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -138,44 +152,11 @@ Script\\Settings\\AmsiEnable" ) and registry.data.strings: ("0",
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[modification-of-amsienable-registry-key-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-registry.path : ( "HKEY_USERS\\*\\Software\\Microsoft\\Windows
-Script\\Settings\\AmsiEnable",
-"HKU\\*\\Software\\Microsoft\\Windows Script\\Settings\\AmsiEnable"
-) and registry.data.strings: ("0", "0x00000000")
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-registry.path: "HKEY_USERS\\*\\Software\\Microsoft\\Windows
-Script\\Settings\\AmsiEnable" and registry.data.strings: "0"
-----------------------------------
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/modification-of-boot-configuration.asciidoc b/docs/detections/prebuilt-rules/rule-details/modification-of-boot-configuration.asciidoc
index 2174a2663a..cd39d00576 100644
--- a/docs/detections/prebuilt-rules/rule-details/modification-of-boot-configuration.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/modification-of-boot-configuration.asciidoc
@@ -5,53 +5,57 @@ Identifies use of bcdedit.exe to delete boot configuration data. This tactic is
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Impact
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<modification-of-boot-configuration-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Modification of Boot Configuration
+*Triage and analysis*
+
+
+
+*Investigating Modification of Boot Configuration*
 
-Boot entry parameters, or boot parameters, are optional, system-specific settings that represent configuration options.
-These are stored in a boot configuration data (BCD) store, and administrators can use utilities like `bcdedit.exe` to
-configure these.
+
+Boot entry parameters, or boot parameters, are optional, system-specific settings that represent configuration options. These are stored in a boot configuration data (BCD) store, and administrators can use utilities like `bcdedit.exe` to configure these.
 
 This rule identifies the usage of `bcdedit.exe` to:
 
@@ -60,53 +64,68 @@ This rule identifies the usage of `bcdedit.exe` to:
 
 These are common steps in destructive attacks by adversaries leveraging ransomware.
 
-#### Possible investigation steps
 
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
 - Check if any files on the host machine have been encrypted.
 
-### False positive analysis
 
-- The usage of these options is not inherently malicious. Administrators can modify these configurations to force a
-machine to boot for troubleshooting or data recovery purposes.
+*False positive analysis*
+
+
+- The usage of these options is not inherently malicious. Administrators can modify these configurations to force a machine to boot for troubleshooting or data recovery purposes.
+
+
+*Related rules*
 
-### Related rules
 
 - Deleting Backup Catalogs with Wbadmin - 581add16-df76-42bb-af8e-c979bfb39a59
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look
-for ransomware preparation and execution activities.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look for ransomware preparation and execution activities.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"bcdedit.exe" or process.pe.original_file_name == "bcdedit.exe") and
-( (process.args : "/set" and process.args : "bootstatuspolicy"
-and process.args : "ignoreallfailures") or (process.args : "no"
-and process.args : "recoveryenabled") )
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "bcdedit.exe" or ?process.pe.original_file_name == "bcdedit.exe") and
+    (
+      (process.args : "/set" and process.args : "bootstatuspolicy" and process.args : "ignoreallfailures") or
+      (process.args : "no" and process.args : "recoveryenabled")
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -118,78 +137,3 @@ and process.args : "recoveryenabled") )
 ** Name: Inhibit System Recovery
 ** ID: T1490
 ** Reference URL: https://attack.mitre.org/techniques/T1490/
-
-[[modification-of-boot-configuration-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "bcdedit.exe" or process.pe.original_file_name ==
-"bcdedit.exe") and ( (process.args : "/set" and process.args
-: "bootstatuspolicy" and process.args : "ignoreallfailures") or
-(process.args : "no" and process.args : "recoveryenabled") )
-----------------------------------
-
-Version 13 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "bcdedit.exe" or process.pe.original_file_name ==
-"bcdedit.exe") and (process.args : "/set" and process.args :
-"bootstatuspolicy" and process.args : "ignoreallfailures") or
-(process.args : "no" and process.args : "recoveryenabled")
-----------------------------------
-
-Version 11 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 9 (7.16.0 release)::
-* Formatting only
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:bcdedit.exe and process.args:(/set and (bootstatuspolicy
-and ignoreallfailures or no and recoveryenabled))
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:bcdedit.exe and process.args:(/set and (bootstatuspolicy
-and ignoreallfailures or no and recoveryenabled))
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/modification-of-dynamic-linker-preload-shared-object-inside-a-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/modification-of-dynamic-linker-preload-shared-object-inside-a-container.asciidoc
new file mode 100644
index 0000000000..e600c940a4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/modification-of-dynamic-linker-preload-shared-object-inside-a-container.asciidoc
@@ -0,0 +1,65 @@
+[[modification-of-dynamic-linker-preload-shared-object-inside-a-container]]
+=== Modification of Dynamic Linker Preload Shared Object Inside A Container
+
+This rule detects the creation or modification of the dynamic linker preload shared object (ld.so.preload) inside a container. The Linux dynamic linker is used to load libraries needed by a program at runtime. Adversaries may hijack the dynamic linker by modifying the /etc/ld.so.preload file to point to malicious libraries. This behavior can be used to grant unauthorized access to system resources and has been used to evade detection of malicious processes in container environments.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://unit42.paloaltonetworks.com/hildegard-malware-teamtnt/
+* https://www.anomali.com/blog/rocke-evolves-its-arsenal-with-a-new-malware-family-written-in-golang/
+* https://sysdig.com/blog/threat-detection-aws-cloud-containers/
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* Tactic: Defense Evasion
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where event.module== "cloud_defend" and event.type != "deletion" and file.path== "/etc/ld.so.preload"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: Dynamic Linker Hijacking
+** ID: T1574.006
+** Reference URL: https://attack.mitre.org/techniques/T1574/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/modification-of-dynamic-linker-preload-shared-object.asciidoc b/docs/detections/prebuilt-rules/rule-details/modification-of-dynamic-linker-preload-shared-object.asciidoc
index 10cc568e8f..6faa6852d6 100644
--- a/docs/detections/prebuilt-rules/rule-details/modification-of-dynamic-linker-preload-shared-object.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/modification-of-dynamic-linker-preload-shared-object.asciidoc
@@ -3,55 +3,108 @@
 
 Identifies modification of the dynamic linker preload shared object (ld.so.preload). Adversaries may execute malicious payloads by hijacking the dynamic linker used to load libraries.
 
-*Rule type*: query
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.anomali.com/blog/rocke-evolves-its-arsenal-with-a-new-malware-family-written-in-golang
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 209
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Privilege Escalation
 
-*Version*: 100 (<<modification-of-dynamic-linker-preload-shared-object-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.12.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:file and not event.type:deletion and
-file.path:/etc/ld.so.preload
+[source, js]
 ----------------------------------
+host.os.type:linux and event.category:file and event.action:(updated or renamed or rename or file_rename_event) and 
+not event.type:deletion and file.path:/etc/ld.so.preload and not process.name:(wine or oneagentinstallaction)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -63,16 +116,7 @@ file.path:/etc/ld.so.preload
 ** Name: Hijack Execution Flow
 ** ID: T1574
 ** Reference URL: https://attack.mitre.org/techniques/T1574/
-
-[[modification-of-dynamic-linker-preload-shared-object-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Dynamic Linker Hijacking
+** ID: T1574.006
+** Reference URL: https://attack.mitre.org/techniques/T1574/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/modification-of-environment-variable-via-unsigned-or-untrusted-parent.asciidoc b/docs/detections/prebuilt-rules/rule-details/modification-of-environment-variable-via-unsigned-or-untrusted-parent.asciidoc
new file mode 100644
index 0000000000..1b420ab8c9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/modification-of-environment-variable-via-unsigned-or-untrusted-parent.asciidoc
@@ -0,0 +1,116 @@
+[[modification-of-environment-variable-via-unsigned-or-untrusted-parent]]
+=== Modification of Environment Variable via Unsigned or Untrusted Parent
+
+Identifies modifications to an environment variable using the built-in launchctl command. Adversaries may execute their own malicious payloads by hijacking certain environment variables to load arbitrary libraries or bypass certain restrictions.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/rapid7/metasploit-framework/blob/master//modules/post/osx/escalate/tccbypass.rb
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:macos and event.type:start and 
+  process.name:launchctl and 
+  (process.parent.code_signature.exists : false or process.parent.code_signature.trusted : false) and
+  process.args:(setenv and not (ANT_HOME or 
+                                DBUS_LAUNCHD_SESSION_BUS_SOCKET or 
+                                EDEN_ENV or 
+                                LG_WEBOS_TV_SDK_HOME or 
+                                RUNTIME_JAVA_HOME or 
+                                WEBOS_CLI_TV or 
+                                JAVA*_HOME) and 
+                not *.vmoptions) and 
+  not process.parent.executable:("/Applications/IntelliJ IDEA CE.app/Contents/jbr/Contents/Home/lib/jspawnhelper" or 
+                                  /Applications/NoMachine.app/Contents/Frameworks/bin/nxserver.bin or 
+                                  /Applications/NoMachine.app/Contents/Frameworks/bin/nxserver.bin or 
+                                  /usr/local/bin/kr)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: Path Interception by PATH Environment Variable
+** ID: T1574.007
+** Reference URL: https://attack.mitre.org/techniques/T1574/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/modification-of-openssh-binaries.asciidoc b/docs/detections/prebuilt-rules/rule-details/modification-of-openssh-binaries.asciidoc
index ba5af86302..c08159b37c 100644
--- a/docs/detections/prebuilt-rules/rule-details/modification-of-openssh-binaries.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/modification-of-openssh-binaries.asciidoc
@@ -5,60 +5,187 @@ Adversaries may modify SSH related binaries for persistence or credential access
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.angelalonso.es/2016/09/anatomy-of-real-linux-intrusion-part-ii.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Persistence
+* Tactic: Lateral Movement
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 109
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Credential Access
-* Persistence
 
-*Version*: 100 (<<modification-of-openssh-binaries-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.12.0
+==== Investigation guide
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Triage and analysis*
+
+
+
+*Investigating Modification of OpenSSH Binaries*
+
+
+OpenSSH is a widely used suite of secure networking utilities based on the Secure Shell (SSH) protocol, which provides encrypted communication sessions over a computer network.
+
+Adversaries may exploit OpenSSH by modifying its binaries, such as `/usr/bin/scp`, `/usr/bin/sftp`, `/usr/bin/ssh`, `/usr/sbin/sshd`, or `libkeyutils.so`, to gain unauthorized access or exfiltrate SSH credentials.
+
+The detection rule 'Modification of OpenSSH Binaries' is designed to identify such abuse by monitoring file changes in the Linux environment. It triggers an alert when a process, modifies any of the specified OpenSSH binaries or libraries. This helps security analysts detect potential malicious activities and take appropriate action.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+    - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+    - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+
+
+*False positive analysis*
+
+
+- Regular users should not need to modify OpenSSH binaries, which makes false positives unlikely. In the case of authorized benign true positives (B-TPs), exceptions can be added.
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator that performed these actions for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
 
-==== Potential false positives
 
-Trusted OpenSSH executable updates. It's recommended to verify the integrity of OpenSSH binary changes.
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:file and event.type:change and process.name:* and
-(file.path:(/usr/sbin/sshd or /usr/bin/ssh or /usr/bin/sftp or
-/usr/bin/scp) or file.name:libkeyutils.so) and not
-process.name:("dpkg" or "yum" or "dnf" or "dnf-automatic")
+[source, js]
 ----------------------------------
+event.category:file and host.os.type:linux and event.type:change and 
+  process.name:(* and not (dnf or dnf-automatic or dpkg or yum or rpm or yum-cron or anacron or platform-python)) and 
+  (file.path:(/usr/bin/scp or 
+                /usr/bin/sftp or 
+                /usr/bin/ssh or 
+                /usr/sbin/sshd) or 
+  file.name:libkeyutils.so) and
+  not process.executable:/usr/share/elasticsearch/*
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,8 +197,6 @@ process.name:("dpkg" or "yum" or "dnf" or "dnf-automatic")
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-
 * Tactic:
 ** Name: Credential Access
 ** ID: TA0006
@@ -80,21 +205,23 @@ process.name:("dpkg" or "yum" or "dnf" or "dnf-automatic")
 ** Name: Modify Authentication Process
 ** ID: T1556
 ** Reference URL: https://attack.mitre.org/techniques/T1556/
-
-[[modification-of-openssh-binaries-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and event.type:change and process.name:* and
-(file.path:(/usr/sbin/sshd or /usr/bin/ssh or /usr/bin/sftp or
-/usr/bin/scp) or file.name:libkeyutils.so) and not
-process.executable:/usr/bin/dpkg
-----------------------------------
-
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SSH
+** ID: T1021.004
+** Reference URL: https://attack.mitre.org/techniques/T1021/004/
+* Technique:
+** Name: Remote Service Session Hijacking
+** ID: T1563
+** Reference URL: https://attack.mitre.org/techniques/T1563/
+* Sub-technique:
+** Name: SSH Hijacking
+** ID: T1563.001
+** Reference URL: https://attack.mitre.org/techniques/T1563/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/modification-of-safari-settings-via-defaults-command.asciidoc b/docs/detections/prebuilt-rules/rule-details/modification-of-safari-settings-via-defaults-command.asciidoc
index 9419262467..966a9f0f7a 100644
--- a/docs/detections/prebuilt-rules/rule-details/modification-of-safari-settings-via-defaults-command.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/modification-of-safari-settings-via-defaults-command.asciidoc
@@ -5,58 +5,96 @@ Identifies changes to the Safari configuration using the built-in defaults comma
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://objectivebythesea.com/v2/talks/OBTS_v2_Zohar.pdf
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Defense Evasion
 
-*Version*: 100 (<<modification-of-safari-settings-via-defaults-command-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:start and
-process.name:defaults and process.args: (com.apple.Safari and
-write and not ( UniversalSearchEnabled or
-SuppressSearchSuggestions or WebKitTabToLinksPreferenceKey or
-ShowFullURLInSmartSearchField or
-com.apple.Safari.ContentPageGroupIdentifier.WebKit2TabsToLinks )
-)
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:start and
+  process.name:defaults and process.args:
+    (com.apple.Safari and write and not
+      (
+      UniversalSearchEnabled or
+      SuppressSearchSuggestions or
+      WebKitTabToLinksPreferenceKey or
+      ShowFullURLInSmartSearchField or
+      com.apple.Safari.ContentPageGroupIdentifier.WebKit2TabsToLinks
+      )
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -68,13 +106,7 @@ com.apple.Safari.ContentPageGroupIdentifier.WebKit2TabsToLinks )
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[modification-of-safari-settings-via-defaults-command-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/modification-of-standard-authentication-module-or-configuration.asciidoc b/docs/detections/prebuilt-rules/rule-details/modification-of-standard-authentication-module-or-configuration.asciidoc
index 3ff17547e7..4cab1d0430 100644
--- a/docs/detections/prebuilt-rules/rule-details/modification-of-standard-authentication-module-or-configuration.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/modification-of-standard-authentication-module-or-configuration.asciidoc
@@ -3,9 +3,9 @@
 
 Adversaries may modify the standard authentication module for persistence via patching the normal authorization process or modifying the login configuration to allow unauthorized access or elevate privileges.
 
-*Rule type*: query
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,66 +14,72 @@ Adversaries may modify the standard authentication module for persistence via pa
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/zephrax/linux-pam-backdoor
 * https://github.com/eurialo/pambd
 * http://0x90909090.blogspot.com/2016/06/creating-backdoor-in-pam-in-5-line-of.html
 * https://www.trendmicro.com/en_us/research/19/i/skidmap-linux-malware-uses-rootkit-capabilities-to-hide-cryptocurrency-mining-payload.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* macOS
-* Linux
-* Threat Detection
-* Credential Access
-* Persistence
-
-*Version*: 100 (<<modification-of-standard-authentication-module-or-configuration-history, version history>>)
+* Domain: Endpoint
+* OS: macOS
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Persistence
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 204
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Trusted system module updates or allowed Pluggable Authentication Module (PAM) daemon configuration changes.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:file and event.type:change and (file.name:pam_*.so or
-file.path:(/etc/pam.d/* or /private/etc/pam.d/*)) and
-process.executable: (* and not ( /bin/yum or
-"/usr/sbin/pam-auth-update" or /usr/libexec/packagekitd or
-/usr/bin/dpkg or /usr/bin/vim or /usr/libexec/xpcproxy
-or /usr/bin/bsdtar or /usr/local/bin/brew or
-/usr/bin/rsync or /usr/bin/yum or
-/var/lib/docker/*/bin/yum or /var/lib/docker/*/bin/dpkg or
-./merged/var/lib/docker/*/bin/dpkg or "/System/Library/Private
-Frameworks/PackageKit.framework/Versions/A/XPCServices/package_script_
-service.xpc/Contents/MacOS/package_script_service" ) ) and
-not file.path: ( /tmp/snap.rootfs_*/pam_*.so or
-/tmp/newroot/lib/*/pam_*.so or /private/var/folders/*/T/com
-.apple.fileprovider.ArchiveService/TemporaryItems/*/lib/security/pam_*
-.so or /tmp/newroot/usr/lib64/security/pam_*.so )
+[source, js]
 ----------------------------------
+event.category:file and event.type:change and
+  (file.name:pam_*.so or file.path:(/etc/pam.d/* or /private/etc/pam.d/* or /usr/lib64/security/*)) and
+  process.executable:
+    (* and
+      not
+      (
+        /usr/libexec/packagekitd or
+        /usr/bin/vim or
+        /usr/libexec/xpcproxy or
+        /usr/bin/bsdtar or
+        /usr/local/bin/brew or
+        "/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/XPCServices/package_script_service.xpc/Contents/MacOS/package_script_service"
+      )
+    ) and
+  not file.path:
+         (
+           /tmp/snap.rootfs_*/pam_*.so or
+           /tmp/newroot/lib/*/pam_*.so or
+           /private/var/folders/*/T/com.apple.fileprovider.ArchiveService/TemporaryItems/*/lib/security/pam_*.so or
+           /tmp/newroot/usr/lib64/security/pam_*.so
+         ) and
+  not process.name:
+         (
+           yum or dnf or rsync or platform-python or authconfig or rpm or pdkg or apk or dnf-automatic or btrfs or
+           dpkg or pam-auth-update or steam or platform-python3.6 or pam-config or microdnf or yum_install or yum-cron or
+           systemd or containerd or pacman
+         )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -85,8 +91,6 @@ not file.path: ( /tmp/snap.rootfs_*/pam_*.so or
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-
 * Tactic:
 ** Name: Credential Access
 ** ID: TA0006
@@ -95,45 +99,3 @@ not file.path: ( /tmp/snap.rootfs_*/pam_*.so or
 ** Name: Modify Authentication Process
 ** ID: T1556
 ** Reference URL: https://attack.mitre.org/techniques/T1556/
-
-[[modification-of-standard-authentication-module-or-configuration-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and event.type:change and (file.name:pam_*.so
-or file.path:(/etc/pam.d/* or /private/etc/pam.d/*)) and
-process.executable: (* and not ( /bin/yum or
-"/usr/sbin/pam-auth-update" or /usr/libexec/packagekitd or
-/usr/bin/dpkg or /usr/bin/vim or
-/usr/libexec/xpcproxy or /usr/bin/bsdtar or
-/usr/local/bin/brew or /usr/bin/rsync or /usr/bin/yum
-or /var/lib/docker/*/bin/yum or
-/var/lib/docker/*/bin/dpkg or
-./merged/var/lib/docker/*/bin/dpkg or "/System/Library/Private
-Frameworks/PackageKit.framework/Versions/A/XPCServices/package_script_
-service.xpc/Contents/MacOS/package_script_service" ) ) and
-not file.path: ( /tmp/snap.rootfs_*/pam_*.so or
-/tmp/newroot/lib/*/pam_*.so or /private/var/folders/*/T/com
-.apple.fileprovider.ArchiveService/TemporaryItems/*/lib/security/pam_*
-.so or /tmp/newroot/usr/lib64/security/pam_*.so )
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and event.type:change and (file.name:pam_*.so or
-file.path:(/etc/pam.d/* or /private/etc/pam.d/*)) and
-process.executable: (* and not ( /bin/yum or "/usr/sbin/pam-auth-
-update" or /usr/libexec/packagekitd or /usr/bin/dpkg or /usr/bin/vim
-or /usr/libexec/xpcproxy or /usr/bin/bsdtar or /usr/local/bin/brew ) )
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/modification-of-the-mspkiaccountcredentials.asciidoc b/docs/detections/prebuilt-rules/rule-details/modification-of-the-mspkiaccountcredentials.asciidoc
index 411e4f4b14..ad64bceb5f 100644
--- a/docs/detections/prebuilt-rules/rule-details/modification-of-the-mspkiaccountcredentials.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/modification-of-the-mspkiaccountcredentials.asciidoc
@@ -5,65 +5,78 @@ Identify the modification of the msPKIAccountCredentials attribute in an Active
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.mandiant.com/resources/blog/apt29-windows-credential-roaming
 * https://social.technet.microsoft.com/wiki/contents/articles/11483.windows-credential-roaming.aspx
 * https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-5136
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Active Directory
-* Privilege Escalation
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Data Source: Active Directory
+* Tactic: Privilege Escalation
+* Use Case: Active Directory Monitoring
 
-*Version*: 1
+*Version*: 9
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+The 'Audit Directory Service Changes' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Changes (Success,Failure)
+```
 
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.action:"Directory Service Changes" and event.code:"5136" and
-winlog.event_data.AttributeLDAPDisplayName:"msPKIAccountCredentials"
-and winlog.event_data.OperationType:"%%14674" and not
-winlog.event_data.SubjectUserSid : "S-1-5-18"
-----------------------------------
+  winlog.event_data.AttributeLDAPDisplayName:"msPKIAccountCredentials" and winlog.event_data.OperationType:"%%14674" and
+  not winlog.event_data.SubjectUserSid : "S-1-5-18"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
diff --git a/docs/detections/prebuilt-rules/rule-details/modification-of-wdigest-security-provider.asciidoc b/docs/detections/prebuilt-rules/rule-details/modification-of-wdigest-security-provider.asciidoc
index 72643e565b..9a44251f34 100644
--- a/docs/detections/prebuilt-rules/rule-details/modification-of-wdigest-security-provider.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/modification-of-wdigest-security-provider.asciidoc
@@ -5,74 +5,71 @@ Identifies attempts to modify the WDigest security provider in the registry to f
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.csoonline.com/article/3438824/how-to-detect-and-halt-credential-theft-via-windows-wdigest.html
 * https://www.praetorian.com/blog/mitigating-mimikatz-wdigest-cleartext-credential-theft?edition=2019
 * https://frsecure.com/compromised-credentials-response-playbook
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<modification-of-wdigest-security-provider-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Modification of WDigest Security Provider
+*Triage and analysis*
+
 
-In Windows XP, Microsoft added support for a protocol known as WDigest. The WDigest protocol allows clients to send
-cleartext credentials to Hypertext Transfer Protocol (HTTP) and Simple Authentication Security Layer (SASL) applications
-based on RFC 2617 and 2831. Windows versions up to 8 and 2012 store logon credentials in memory in plaintext by default,
-which is no longer the case with newer Windows versions.
 
-Still, attackers can force WDigest to store the passwords insecurely on the memory by modifying the
-`HKLM\SYSTEM\*ControlSet*\Control\SecurityProviders\WDigest\UseLogonCredential` registry key. This activity is
-commonly related to the execution of credential dumping tools.
+*Investigating Modification of WDigest Security Provider*
 
-#### Possible investigation steps
 
-- It is unlikely that the monitored registry key was modified legitimately in newer versions of Windows. Analysts should
-treat any activity triggered from this rule with high priority as it typically represents an active adversary.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+In Windows XP, Microsoft added support for a protocol known as WDigest. The WDigest protocol allows clients to send cleartext credentials to Hypertext Transfer Protocol (HTTP) and Simple Authentication Security Layer (SASL) applications based on RFC 2617 and 2831. Windows versions up to 8 and 2012 store logon credentials in memory in plaintext by default, which is no longer the case with newer Windows versions.
+
+Still, attackers can force WDigest to store the passwords insecurely on the memory by modifying the `HKLM\SYSTEM\*ControlSet*\Control\SecurityProviders\WDigest\UseLogonCredential` registry key. This activity is commonly related to the execution of credential dumping tools.
+
+
+*Possible investigation steps*
+
+
+- It is unlikely that the monitored registry key was modified legitimately in newer versions of Windows. Analysts should treat any activity triggered from this rule with high priority as it typically represents an active adversary.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Determine if credential dumping tools were run on the host, and retrieve and analyze suspicious executables:
   - Use a private sandboxed malware analysis system to perform analysis.
@@ -84,50 +81,60 @@ prevalence, whether they are located in expected locations, and if they are sign
   - Use the PowerShell Get-FileHash cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 - Use process name, command line, and file hash to search for occurrences on other hosts.
-- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target
-host after the registry modification.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
 
-### False positive analysis
+*False positive analysis*
 
-- This modification should not happen legitimately. Any potential benign true positive (B-TP) should be mapped and
-monitored by the security team, as these modifications expose the entire domain to credential compromises and
-consequently unauthorized access.
 
-### Related rules
+- This modification should not happen legitimately. Any potential benign true positive (B-TP) should be mapped and monitored by the security team, as these modifications expose the entire domain to credential compromises and consequently unauthorized access.
+
+
+*Related rules*
+
 
 - Mimikatz Powershell Module Activity - ac96ceb8-4399-4191-af1d-4feeac1f1f46
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Reimage the host operating system and restore compromised files to clean versions.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type : ("creation", "change") and
-registry.path : ( "HKLM\\SYSTEM\\*ControlSet*\\Control\\Securi
-tyProviders\\WDigest\\UseLogonCredential", "\\REGISTRY\\MACHIN
-E\\SYSTEM\\*ControlSet*\\Control\\SecurityProviders\\WDigest\\UseLogon
-Credential" ) and registry.data.strings : ("1", "0x00000001") and
-not (process.executable : "?:\\Windows\\System32\\svchost.exe" and
-user.id : "S-1-5-18")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type : ("creation", "change") and
+    registry.path : (
+        "HKLM\\SYSTEM\\*ControlSet*\\Control\\SecurityProviders\\WDigest\\UseLogonCredential",
+        "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Control\\SecurityProviders\\WDigest\\UseLogonCredential"
+    ) and registry.data.strings : ("1", "0x00000001") and
+    not (process.executable : "?:\\Windows\\System32\\svchost.exe" and user.id : "S-1-5-18")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -139,49 +146,7 @@ user.id : "S-1-5-18")
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[modification-of-wdigest-security-provider-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type : ("creation", "change") and
-registry.path : "HKLM\\SYSTEM\\*ControlSet*\\Control\\Security
-Providers\\WDigest\\UseLogonCredential" and registry.data.strings
-: ("1", "0x00000001") and not (process.executable :
-"?:\\Windows\\System32\\svchost.exe" and user.id : "S-1-5-18")
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type : ("creation", "change") and
-registry.path : "HKLM\\SYSTEM\\*ControlSet*\\Control\\Securit
-yProviders\\WDigest\\UseLogonCredential" and registry.data.strings
-: ("1", "0x00000001")
-----------------------------------
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type in ("creation", "change") and registry.pat
-h:"HKLM\\SYSTEM\\*ControlSet*\\Control\\SecurityProviders\\WDigest\\Us
-eLogonCredential" and registry.data.strings:"1"
-----------------------------------
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/modification-or-removal-of-an-okta-application-sign-on-policy.asciidoc b/docs/detections/prebuilt-rules/rule-details/modification-or-removal-of-an-okta-application-sign-on-policy.asciidoc
index 6b9264999e..5f244dde4f 100644
--- a/docs/detections/prebuilt-rules/rule-details/modification-or-removal-of-an-okta-application-sign-on-policy.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/modification-or-removal-of-an-okta-application-sign-on-policy.asciidoc
@@ -5,7 +5,7 @@ Detects attempts to modify or delete a sign on policy for an Okta application. A
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,63 +14,52 @@ Detects attempts to modify or delete a sign on policy for an Okta application. A
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://help.okta.com/en/prod/Content/Topics/Security/App_Based_Signon.htm
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Persistence
-
-*Version*: 102 (<<modification-or-removal-of-an-okta-application-sign-on-policy-history, version history>>)
+* Tactic: Persistence
+* Use Case: Identity and Access Audit
+* Data Source: Okta
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Consider adding exceptions to this rule to filter false positives if sign on policies for Okta applications are regularly modified or deleted in your organization.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and
-event.action:(application.policy.sign_on.update or
-application.policy.sign_on.rule.delete)
+[source, js]
 ----------------------------------
+event.dataset:okta.system and event.action:(application.policy.sign_on.update or application.policy.sign_on.rule.delete)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -82,38 +71,3 @@ application.policy.sign_on.rule.delete)
 ** Name: Modify Authentication Process
 ** ID: T1556
 ** Reference URL: https://attack.mitre.org/techniques/T1556/
-
-[[modification-or-removal-of-an-okta-application-sign-on-policy-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:(application.policy.sign_on.update or
-application.policy.sign_on.rule.delete)
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/mofcomp-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/mofcomp-activity.asciidoc
new file mode 100644
index 0000000000..a13ef062a7
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/mofcomp-activity.asciidoc
@@ -0,0 +1,82 @@
+[[mofcomp-activity]]
+=== Mofcomp Activity
+
+Managed Object Format (MOF) files can be compiled locally or remotely through mofcomp.exe. Attackers may leverage MOF files to build their own namespaces and classes into the Windows Management Instrumentation (WMI) repository, or establish persistence using WMI Event Subscription.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "mofcomp.exe" and process.args : "*.mof" and
+  not user.id : "S-1-5-18" and
+  not
+  (
+    process.parent.name : "ScenarioEngine.exe" and
+    process.args : (
+      "*\\MSSQL\\Binn\\*.mof",
+      "*\\Microsoft SQL Server\\???\\Shared\\*.mof",
+      "*\\OLAP\\bin\\*.mof"
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Windows Management Instrumentation
+** ID: T1047
+** Reference URL: https://attack.mitre.org/techniques/T1047/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: Windows Management Instrumentation Event Subscription
+** ID: T1546.003
+** Reference URL: https://attack.mitre.org/techniques/T1546/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/mount-launched-inside-a-privileged-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/mount-launched-inside-a-privileged-container.asciidoc
new file mode 100644
index 0000000000..44ca9ceda9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/mount-launched-inside-a-privileged-container.asciidoc
@@ -0,0 +1,62 @@
+[[mount-launched-inside-a-privileged-container]]
+=== Mount Launched Inside a Privileged Container
+
+This rule detects the use of the mount utility from inside a privileged container. The mount command is used to make a device or file system accessible to the system, and then to connect its root directory to a specified mount point on the local file system. When launched inside a privileged container--a container deployed with all the capabilities of the host machine-- an attacker can access sensitive host level files which could be used for further privilege escalation and container escapes to the host machine. Any usage of mount inside a running privileged container should be further investigated.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://book.hacktricks.xyz/linux-hardening/privilege-escalation/docker-security/docker-breakout-privilege-escalation#privileged
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.module == "cloud_defend" and  event.type== "start" and 
+(process.name== "mount" or process.args== "mount") and container.security_context.privileged == true
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Escape to Host
+** ID: T1611
+** Reference URL: https://attack.mitre.org/techniques/T1611/
diff --git a/docs/detections/prebuilt-rules/rule-details/mounting-hidden-or-webdav-remote-shares.asciidoc b/docs/detections/prebuilt-rules/rule-details/mounting-hidden-or-webdav-remote-shares.asciidoc
index 9df585c80d..e665229ec6 100644
--- a/docs/detections/prebuilt-rules/rule-details/mounting-hidden-or-webdav-remote-shares.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/mounting-hidden-or-webdav-remote-shares.asciidoc
@@ -5,65 +5,74 @@ Identifies the use of net.exe to mount a WebDav or hidden remote share. This may
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Initial Access
-* Lateral Movement
+*Tags*: 
 
-*Version*: 102 (<<mounting-hidden-or-webdav-remote-shares-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Lateral Movement
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and ((process.name : "net.exe" or
-process.pe.original_file_name == "net.exe") or ((process.name :
-"net1.exe" or process.pe.original_file_name == "net1.exe") and not
-process.parent.name : "net.exe")) and process.args : "use" and /*
-including hidden and webdav based online shares such as onedrive */
-process.args : ("\\\\*\\*$*", "\\\\*@SSL\\*", "http*") and /*
-excluding shares deletion operation */ not process.args : "/d*"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ ((process.name : "net.exe" or ?process.pe.original_file_name == "net.exe") or ((process.name : "net1.exe" or ?process.pe.original_file_name == "net1.exe") and
+ not process.parent.name : "net.exe")) and
+ process.args : "use" and
+ /* including hidden and webdav based online shares such as onedrive  */
+ process.args : ("\\\\*\\*$*", "\\\\*@SSL\\*", "http*") and
+ /* excluding shares deletion operation */
+ not process.args : "/d*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,8 +84,10 @@ excluding shares deletion operation */ not process.args : "/d*"
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -85,37 +96,23 @@ excluding shares deletion operation */ not process.args : "/d*"
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[mounting-hidden-or-webdav-remote-shares-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-((process.name : "net.exe" or process.pe.original_file_name ==
-"net.exe") or ((process.name : "net1.exe" or
-process.pe.original_file_name == "net1.exe") and not
-process.parent.name : "net.exe")) and process.args : "use" and /*
-including hidden and webdav based online shares such as onedrive */
-process.args : ("\\\\*\\*$*", "\\\\*@SSL\\*", "http*") and /*
-excluding shares deletion operation */ not process.args : "/d*"
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Local Accounts
+** ID: T1078.003
+** Reference URL: https://attack.mitre.org/techniques/T1078/003/
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Account Discovery
+** ID: T1087
+** Reference URL: https://attack.mitre.org/techniques/T1087/
+* Sub-technique:
+** Name: Local Account
+** ID: T1087.001
+** Reference URL: https://attack.mitre.org/techniques/T1087/001/
+* Sub-technique:
+** Name: Domain Account
+** ID: T1087.002
+** Reference URL: https://attack.mitre.org/techniques/T1087/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/ms-office-macro-security-registry-modifications.asciidoc b/docs/detections/prebuilt-rules/rule-details/ms-office-macro-security-registry-modifications.asciidoc
index 7f418a7c08..5ee17df7ef 100644
--- a/docs/detections/prebuilt-rules/rule-details/ms-office-macro-security-registry-modifications.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/ms-office-macro-security-registry-modifications.asciidoc
@@ -5,75 +5,70 @@ Microsoft Office Products offer options for users and developers to control the
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<ms-office-macro-security-registry-modifications-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating MS Office Macro Security Registry Modifications
+*Triage and analysis*
+
 
-Macros are small programs that are used to automate repetitive tasks in Microsoft Office applications.
-Historically, macros have been used for a variety of reasons -- from automating part of a job, to
-building entire processes and data flows. Macros are written in Visual Basic for Applications (VBA) and are saved as
-part of Microsoft Office files.
 
-Macros are often created for legitimate reasons, but they can also be written by attackers to gain access, harm a
-system, or bypass other security controls such as application allow listing. In fact, exploitation from malicious macros
-is one of the top ways that organizations are compromised today. These attacks are often conducted through phishing or
-spear phishing campaigns.
+*Investigating MS Office Macro Security Registry Modifications*
 
-Attackers can convince victims to modify Microsoft Office security settings, so their macros are trusted by default and
-no warnings are displayed when they are executed. These settings include:
 
-* *Trust access to the VBA project object model* - When enabled, Microsoft Office will trust all macros and run any code
-without showing a security warning or requiring user permission.
-* *VbaWarnings* - When set to 1, Microsoft Office will trust all macros and run any code without showing a security
-warning or requiring user permission.
+Macros are small programs that are used to automate repetitive tasks in Microsoft Office applications. Historically, macros have been used for a variety of reasons -- from automating part of a job, to building entire processes and data flows. Macros are written in Visual Basic for Applications (VBA) and are saved as part of Microsoft Office files.
+
+Macros are often created for legitimate reasons, but they can also be written by attackers to gain access, harm a system, or bypass other security controls such as application allow listing. In fact, exploitation from malicious macros is one of the top ways that organizations are compromised today. These attacks are often conducted through phishing or spear phishing campaigns.
+
+Attackers can convince victims to modify Microsoft Office security settings, so their macros are trusted by default and no warnings are displayed when they are executed. These settings include:
+
+- *Trust access to the VBA project object model* - When enabled, Microsoft Office will trust all macros and run any code without showing a security warning or requiring user permission.
+- *VbaWarnings* - When set to 1, Microsoft Office will trust all macros and run any code without showing a security warning or requiring user permission.
 
 This rule looks for registry changes affecting the conditions above.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the user and check if the change was done manually.
 - Verify whether malicious macros were executed after the registry change.
@@ -88,50 +83,60 @@ for prevalence, whether they are located in expected locations, and if they are
   - Use the PowerShell Get-FileHash cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
 
-- This activity should not happen legitimately. The security team should address any potential benign true
-positives (B-TPs), as this configuration can put the user and the domain at risk.
+*False positive analysis*
+
+
+- This activity should not happen legitimately. The security team should address any potential benign true positive (B-TP), as this configuration can put the user and the domain at risk.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Reset the registry key value.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Explore using GPOs to manage security settings for Microsoft Office macros.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type == "change" and registry.path : (
-"HKU\\S-1-5-21-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\AccessVBOM
-", "HKU\\S-1-5-21-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\
-\VbaWarnings", "HKU\\S-1-12-1-*\\SOFTWARE\\Microsoft\\Office\\
-*\\Security\\AccessVBOM", "HKU\\S-1-12-1-*\\SOFTWARE\\Microsof
-t\\Office\\*\\Security\\VbaWarnings", "\\REGISTRY\\USER\\S-1-5
--21-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\AccessVBOM", 
-"\\REGISTRY\\USER\\S-1-5-21-*\\SOFTWARE\\Microsoft\\Office\\*\\Securit
-y\\VbaWarnings", "\\REGISTRY\\USER\\S-1-12-1-*\\SOFTWARE\\Micr
-osoft\\Office\\*\\Security\\AccessVBOM", "\\REGISTRY\\USER\\S-
-1-12-1-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\VbaWarnings"
-) and registry.data.strings : ("0x00000001", "1") and
-process.name : ("cscript.exe", "wscript.exe", "mshta.exe",
-"mshta.exe", "winword.exe", "excel.exe")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type == "change" and
+    registry.path : (
+        "HKU\\S-1-5-21-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\AccessVBOM",
+        "HKU\\S-1-5-21-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\VbaWarnings",
+        "HKU\\S-1-12-1-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\AccessVBOM",
+        "HKU\\S-1-12-1-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\VbaWarnings",
+        "\\REGISTRY\\USER\\S-1-5-21-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\AccessVBOM",
+        "\\REGISTRY\\USER\\S-1-5-21-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\VbaWarnings",
+        "\\REGISTRY\\USER\\S-1-12-1-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\AccessVBOM",
+        "\\REGISTRY\\USER\\S-1-12-1-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\VbaWarnings"
+        ) and
+    registry.data.strings : ("0x00000001", "1") and
+    process.name : ("cscript.exe", "wscript.exe", "mshta.exe", "mshta.exe", "winword.exe", "excel.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -143,8 +148,6 @@ process.name : ("cscript.exe", "wscript.exe", "mshta.exe",
 ** Name: Modify Registry
 ** ID: T1112
 ** Reference URL: https://attack.mitre.org/techniques/T1112/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -153,42 +156,7 @@ process.name : ("cscript.exe", "wscript.exe", "mshta.exe",
 ** Name: User Execution
 ** ID: T1204
 ** Reference URL: https://attack.mitre.org/techniques/T1204/
-
-[[ms-office-macro-security-registry-modifications-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type == "change" and registry.path : (
-"HKU\\S-1-5-21-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\AccessVBOM
-", "HKU\\S-1-5-21-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\
-\VbaWarnings" ) and registry.data.strings == "0x00000001"
-and process.name : ("cscript.exe", "wscript.exe", "mshta.exe",
-"mshta.exe", "winword.exe", "excel.exe")
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type == "change" and registry.path : (
-"HKU\\S-1-5-21-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\\AccessVBOM
-", "HKU\\S-1-5-21-*\\SOFTWARE\\Microsoft\\Office\\*\\Security\
-\VbaWarnings" ) and registry.data.strings == "0x00000001"
-and process.name : ("cscript.exe", "wscript.exe", "mshta.exe",
-"mshta.exe", "winword.exe", "excel.exe")
-----------------------------------
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/msbuild-making-network-connections.asciidoc b/docs/detections/prebuilt-rules/rule-details/msbuild-making-network-connections.asciidoc
index d829248b2f..7377f2640b 100644
--- a/docs/detections/prebuilt-rules/rule-details/msbuild-making-network-connections.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/msbuild-making-network-connections.asciidoc
@@ -5,109 +5,137 @@ Identifies MsBuild.exe making outbound network connections. This may indicate ad
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<msbuild-making-network-connections-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
 
+==== Investigation guide
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where process.name :
-"MSBuild.exe" and event.type == "start"] [network where process.name
-: "MSBuild.exe" and not cidrmatch(destination.ip, "127.0.0.1",
-"::1")]
-----------------------------------
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+*Triage and analysis*
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Trusted Developer Utilities Proxy Execution
-** ID: T1127
-** Reference URL: https://attack.mitre.org/techniques/T1127/
 
-[[msbuild-making-network-connections-history]]
-==== Rule version history
 
-Version 100 (8.5.0 release)::
-* Formatting only
+*Investigating MsBuild Making Network Connections*
 
-Version 9 (8.4.0 release)::
-* Formatting only
 
-Version 8 (7.16.0 release)::
-* Formatting only
+By examining the specific traits of Windows binaries (such as process trees, command lines, network connections, registry modifications, and so on) it's possible to establish a baseline of normal activity. Deviations from this baseline can indicate malicious activity, such as masquerading and deserve further investigation.
 
-Version 7 (7.12.0 release)::
-* Formatting only
+The Microsoft Build Engine, also known as MSBuild, is a platform for building applications. This engine provides an XML schema for a project file that controls how the build platform processes and builds software, and can be abused to proxy code execution.
 
-Version 6 (7.11.0 release)::
-* Formatting only
+This rule looks for the `Msbuild.exe` utility execution, followed by a network connection to an external address. Attackers can abuse MsBuild to execute malicious files or masquerade as those utilities in order to bypass detections and evade defenses.
 
-Version 5 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:connection and
-process.name:MSBuild.exe and not destination.ip:(127.0.0.1 or "::1")
-----------------------------------
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-Version 4 (7.9.1 release)::
-* Formatting only
 
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Network connection detected (rule: NetworkConnect)" and
-process.name:MSBuild.exe and not destination.ip:(127.0.0.1 or "::1")
-----------------------------------
+*Possible investigation steps*
+
+
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+  - Investigate the file digital signature and process original filename, if suspicious, treat it as potential malware.
+- Investigate the target host that the signed binary is communicating with.
+  - Check if the domain is newly registered or unexpected.
+  - Check the reputation of the domain or IP address.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of destination IP address and command line conditions.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
 
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:"Network connection detected (rule: NetworkConnect)" and
-process.name:MSBuild.exe and not destination.ip:("127.0.0.1" or "::1")
+sequence by process.entity_id
+  [process where host.os.type == "windows" and process.name : "MSBuild.exe" and event.type == "start"]
+  [network where host.os.type == "windows" and process.name : "MSBuild.exe" and
+     not cidrmatch(destination.ip, "127.0.0.1", "::1") and
+     not dns.question.name : "localhost"]
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Trusted Developer Utilities Proxy Execution
+** ID: T1127
+** Reference URL: https://attack.mitre.org/techniques/T1127/
+* Sub-technique:
+** Name: MSBuild
+** ID: T1127.001
+** Reference URL: https://attack.mitre.org/techniques/T1127/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/mshta-making-network-connections.asciidoc b/docs/detections/prebuilt-rules/rule-details/mshta-making-network-connections.asciidoc
index 4d0b33c43d..2113cf65f2 100644
--- a/docs/detections/prebuilt-rules/rule-details/mshta-making-network-connections.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/mshta-making-network-connections.asciidoc
@@ -5,56 +5,57 @@ Identifies Mshta.exe making outbound network connections. This may indicate adve
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-20m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 101 (<<mshta-making-network-connections-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id with maxspan=10m [process where
-event.type == "start" and process.name : "mshta.exe" and not
-process.parent.name : "Microsoft.ConfigurationManagement.exe" and
-not (process.parent.executable : "C:\\Amazon\\Amazon
-Assistant\\amazonAssistantService.exe" or
-process.parent.executable : "C:\\TeamViewer\\TeamViewer.exe") and
-not process.args : "ADSelfService_Enroll.hta"] [network where
-process.name : "mshta.exe"]
+[source, js]
 ----------------------------------
+sequence by process.entity_id with maxspan=10m
+  [process where host.os.type == "windows" and event.type == "start" and process.name : "mshta.exe" and
+     not process.parent.name : "Microsoft.ConfigurationManagement.exe" and
+     not (process.parent.executable : "C:\\Amazon\\Amazon Assistant\\amazonAssistantService.exe" or
+          process.parent.executable : "C:\\TeamViewer\\TeamViewer.exe") and
+     not process.args : "ADSelfService_Enroll.hta"]
+  [network where host.os.type == "windows" and process.name : "mshta.exe"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,51 +67,7 @@ process.name : "mshta.exe"]
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[mshta-making-network-connections-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan=10m [process where
-event.type in ("start", "process_started") and process.name :
-"mshta.exe" and not process.parent.name :
-"Microsoft.ConfigurationManagement.exe" and not
-(process.parent.executable : "C:\\Amazon\\Amazon
-Assistant\\amazonAssistantService.exe" or
-process.parent.executable : "C:\\TeamViewer\\TeamViewer.exe") and
-not process.args : "ADSelfService_Enroll.hta"] [network where
-process.name : "mshta.exe"]
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.15.0 release)::
-* Formatting only
-
-Version 4 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan=2h [process where
-event.type in ("start", "process_started") and process.name :
-"mshta.exe" and not process.parent.name :
-"Microsoft.ConfigurationManagement.exe" and not
-(process.parent.executable : "C:\\Amazon\\Amazon
-Assistant\\amazonAssistantService.exe" or
-process.parent.executable : "C:\\TeamViewer\\TeamViewer.exe") and
-not process.args : "ADSelfService_Enroll.hta"] [network where
-process.name : "mshta.exe"]
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Mshta
+** ID: T1218.005
+** Reference URL: https://attack.mitre.org/techniques/T1218/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/multi-factor-authentication-disabled-for-an-azure-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/multi-factor-authentication-disabled-for-an-azure-user.asciidoc
index 9ac88afe67..e3cd74964c 100644
--- a/docs/detections/prebuilt-rules/rule-details/multi-factor-authentication-disabled-for-an-azure-user.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/multi-factor-authentication-disabled-for-an-azure-user.asciidoc
@@ -5,7 +5,7 @@ Identifies when multi-factor authentication (MFA) is disabled for an Azure user
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,68 +14,69 @@ Identifies when multi-factor authentication (MFA) is disabled for an Azure user
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Investigation Guide
+*Tags*: 
 
-*Version*: 103 (<<multi-factor-authentication-disabled-for-an-azure-user-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Multi-Factor Authentication Disabled for an Azure User
+*Triage and analysis*
+
+
+
+*Investigating Multi-Factor Authentication Disabled for an Azure User*
+
 
-Multi-factor authentication is a process in which users are prompted during the sign-in process for an additional form
-of identification, such as a code on their cellphone or a fingerprint scan.
+Multi-factor authentication is a process in which users are prompted during the sign-in process for an additional form of identification, such as a code on their cellphone or a fingerprint scan.
 
-If you only use a password to authenticate a user, it leaves an insecure vector for attack. If the password is weak or
-has been exposed elsewhere, an attacker could be using it to gain access. When you require a second form of authentication,
-security is increased because this additional factor isn't something that's easy for an attacker to obtain or duplicate.
+If you only use a password to authenticate a user, it leaves an insecure vector for attack. If the password is weak or has been exposed elsewhere, an attacker could be using it to gain access. When you require a second form of authentication, security is increased because this additional factor isn't something that's easy for an attacker to obtain or duplicate.
 
-For more information about using MFA in Azure AD, access the [official documentation](https://docs.microsoft.com/en-us/azure/active-directory/authentication/concept-mfa-howitworks#how-to-enable-and-use-azure-ad-multi-factor-authentication).
+For more information about using MFA in Azure AD, access the https://docs.microsoft.com/en-us/azure/active-directory/authentication/concept-mfa-howitworks#how-to-enable-and-use-azure-ad-multi-factor-authentication[official documentation].
 
-This rule identifies the deactivation of MFA for an Azure user account. This modification weakens account security
-and can lead to the compromise of accounts and other assets.
+This rule identifies the deactivation of MFA for an Azure user account. This modification weakens account security and can lead to the compromise of accounts and other assets.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Contact the account and resource owners and confirm whether they are aware of this activity.
 - Check if this operation was approved and performed according to the organization's change management policy.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
 
-### False positive analysis
 
-- While this activity can be done by administrators, all users must use MFA. The security team should address any
-potential benign true positive (B-TP), as this configuration can risk the user and domain.
+- While this activity can be done by administrators, all users must use MFA. The security team should address any potential benign true positive (B-TP), as this configuration can risk the user and domain.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -85,29 +86,26 @@ potential benign true positive (B-TP), as this configuration can risk the user a
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Reactivate multi-factor authentication for the user.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security defaults [provided by Microsoft](https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/concept-fundamentals-security-defaults).
+- Implement security defaults https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/concept-fundamentals-security-defaults[provided by Microsoft].
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.auditlogs and
-azure.auditlogs.operation_name:"Disable Strong Authentication" and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Disable Strong Authentication" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -119,35 +117,3 @@ event.outcome:(Success or success)
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[multi-factor-authentication-disabled-for-an-azure-user-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.auditlogs and
-azure.auditlogs.operation_name:"Disable Strong Authentication" and
-event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/multiple-alerts-in-different-att-ck-tactics-on-a-single-host.asciidoc b/docs/detections/prebuilt-rules/rule-details/multiple-alerts-in-different-att-ck-tactics-on-a-single-host.asciidoc
index 4c6fc32ea7..f1d894420e 100644
--- a/docs/detections/prebuilt-rules/rule-details/multiple-alerts-in-different-att-ck-tactics-on-a-single-host.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/multiple-alerts-in-different-att-ck-tactics-on-a-single-host.asciidoc
@@ -5,43 +5,41 @@ This rule uses alert data to determine when multiple alerts in different phases
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
-* .alerts-*
+* .alerts-security.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 1 hour
+*Runs every*: 1h
 
 *Searches indices from*: now-24h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Threat Detection
-* Higher-Order Rules
+*Tags*: 
 
-*Version*: 1
+* Use Case: Threat Detection
+* Rule Type: Higher-Order Rule
 
-*Added ({stack} release)*: 8.6.0
+*Version*: 4
 
-*Rule authors*: Elastic
+*Rule authors*: 
 
-*Rule license*: Elastic License v2
+* Elastic
 
-==== Potential false positives
+*Rule license*: Elastic License v2
 
-False positives can occur because the rules may be mapped to a few MITRE ATT&CK tactics. Use the attached Timeline to determine which detections were triggered on the host.
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 signal.rule.name:* and kibana.alert.rule.threat.tactic.id:*
-----------------------------------
 
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/multiple-alerts-involving-a-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/multiple-alerts-involving-a-user.asciidoc
new file mode 100644
index 0000000000..3663fbcb11
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/multiple-alerts-involving-a-user.asciidoc
@@ -0,0 +1,45 @@
+[[multiple-alerts-involving-a-user]]
+=== Multiple Alerts Involving a User
+
+This rule uses alert data to determine when multiple different alerts involving the same user are triggered. Analysts can use this to prioritize triage and response, as these users are more likely to be compromised.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* .alerts-security.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 1h
+
+*Searches indices from*: now-24h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Use Case: Threat Detection
+* Rule Type: Higher-Order Rule
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+signal.rule.name:* and user.name:* and not user.id:("S-1-5-18" or "S-1-5-19" or "S-1-5-20")
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/multiple-logon-failure-followed-by-logon-success.asciidoc b/docs/detections/prebuilt-rules/rule-details/multiple-logon-failure-followed-by-logon-success.asciidoc
index 20b70e40d3..09ba222aab 100644
--- a/docs/detections/prebuilt-rules/rule-details/multiple-logon-failure-followed-by-logon-success.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/multiple-logon-failure-followed-by-logon-success.asciidoc
@@ -5,102 +5,148 @@ Identifies multiple logon failures followed by a successful one from the same so
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-system.*
+* logs-system.security*
+* logs-windows.forwarded*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4625
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
 
-*Version*: 1
+*Version*: 10
 
-*Added ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-#### Possible investigation steps
+*Triage and analysis*
+
+
+
+*Investigating Multiple Logon Failure Followed by Logon Success*
+
 
-- Investigate the logon failure reason code and the targeted user names.
+Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts. Without knowledge of the password for an account, an adversary may opt to guess the password using a repetitive or iterative mechanism systematically. More details can be found https://attack.mitre.org/techniques/T1110/001/[here].
+
+This rule identifies potential password guessing/brute force activity from a single address, followed by a successful logon, indicating that an attacker potentially successfully compromised the account.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the logon failure reason code and the targeted user name.
+  - Prioritize the investigation if the account is critical or has administrative privileges over the domain.
 - Investigate the source IP address of the failed Network Logon attempts.
-- Investigate other alerts associated with the user/host during the past 48 hours.
+  - Identify whether these attempts are coming from the internet or are internal.
+- Investigate other alerts associated with the involved users and source host during the past 48 hours.
 - Identify the source and the target computer and their roles in the IT environment.
+- Check whether the involved credentials are used in automation or scheduled tasks.
+- If this activity is suspicious, contact the account owner and confirm whether they are aware of it.
+- Examine the source host for derived artifacts that indicate compromise:
+  - Observe and collect information about the following activities in the alert source host:
+    - Attempts to contact external domains and addresses.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the host which is the source of this activity.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - Authentication misconfiguration or obsolete credentials.
 - Service account password expired.
-- Trust relationship between the primary domain and the trusted domain issue.
-- Infrastructure or availability issue.
+- Domain trust relationship issues.
+- Infrastructure or availability issues.
+
+
+*Related rules*
+
+
+- Multiple Logon Failure from the same Source Address - 48b6edfc-079d-4907-b43c-baffa243270d
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
-- If the host is a domain controller (DC):
-  - Activate your incident response plan for total Active Directory compromise.
-  - Review the privileges assigned to users that can access the DCs, to ensure that the least privilege principle is
-  being followed and to reduce the attack surface.
-- Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Isolate the source host to prevent further post-compromise behavior.
+- If the asset is exposed to the internet with RDP or other remote services available, take the necessary measures to restrict access to the asset. If not possible, limit the access via the firewall to only the needed IP addresses. Also, ensure the system uses robust authentication mechanisms and is patched regularly.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, source.ip with maxspan=5s [authentication where
-event.action == "logon-failed" and /* event 4625 need to be logged
-*/ winlog.logon.type : "Network" and source.ip != null and
-source.ip != "127.0.0.1" and source.ip != "::1" and not user.name
-: ("ANONYMOUS LOGON", "-", "*$") and not user.domain == "NT AUTHORITY"
-and /* noisy failure status codes often associated to
-authentication misconfiguration */ not winlog.event_data.Status :
-("0xC000015B", "0XC000005E", "0XC0000133", "0XC0000192")] with runs=5
-[authentication where event.action == "logged-in" and /* event
-4624 need to be logged */ winlog.logon.type : "Network" and
-source.ip != null and source.ip != "127.0.0.1" and source.ip != "::1"
-and not user.name : ("ANONYMOUS LOGON", "-", "*$") and not
-user.domain == "NT AUTHORITY"]
+[source, js]
 ----------------------------------
+sequence by winlog.computer_name, source.ip with maxspan=5s
+  [authentication where event.action == "logon-failed" and
+    /* event 4625 need to be logged */
+    winlog.logon.type : "Network" and user.id != null and 
+    source.ip != null and source.ip != "127.0.0.1" and source.ip != "::1" and 
+    not winlog.event_data.TargetUserSid : "S-1-0-0" and not user.id : "S-1-0-0" and 
+    not user.name : ("ANONYMOUS LOGON", "-", "*$") and not user.domain == "NT AUTHORITY" and
+
+    /* noisy failure status codes often associated to authentication misconfiguration */
+    not winlog.event_data.Status : ("0xC000015B", "0XC000005E", "0XC0000133", "0XC0000192")] with runs=5
+  [authentication where event.action == "logged-in" and
+    /* event 4624 need to be logged */
+    winlog.logon.type : "Network" and
+    source.ip != null and source.ip != "127.0.0.1" and source.ip != "::1" and
+    not user.name : ("ANONYMOUS LOGON", "-", "*$") and not user.domain == "NT AUTHORITY"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -112,3 +158,11 @@ user.domain == "NT AUTHORITY"]
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Sub-technique:
+** Name: Password Guessing
+** ID: T1110.001
+** Reference URL: https://attack.mitre.org/techniques/T1110/001/
+* Sub-technique:
+** Name: Password Spraying
+** ID: T1110.003
+** Reference URL: https://attack.mitre.org/techniques/T1110/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/multiple-logon-failure-from-the-same-source-address.asciidoc b/docs/detections/prebuilt-rules/rule-details/multiple-logon-failure-from-the-same-source-address.asciidoc
index 55e1518d53..5c75382780 100644
--- a/docs/detections/prebuilt-rules/rule-details/multiple-logon-failure-from-the-same-source-address.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/multiple-logon-failure-from-the-same-source-address.asciidoc
@@ -5,107 +5,148 @@ Identifies multiple consecutive logon failures from the same source address and
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-system.*
+* logs-system.security*
+* logs-windows.forwarded*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4625
+* https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=4624
+* https://social.technet.microsoft.com/Forums/ie/en-US/c82ac4f3-a235-472c-9fd3-53aa646cfcfd/network-information-missing-in-event-id-4624?forum=winserversecurity
+* https://serverfault.com/questions/379092/remote-desktop-failed-logon-event-4625-not-logging-ip-address-on-2008-terminal-s/403638#403638
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
 
-*Version*: 1
+*Version*: 9
 
-*Added ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-#### Possible investigation steps
+*Triage and analysis*
+
+
+
+*Investigating Multiple Logon Failure from the same Source Address*
+
+
+Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts. Without knowledge of the password for an account, an adversary may opt to guess the password using a repetitive or iterative mechanism systematically. More details can be found https://attack.mitre.org/techniques/T1110/001/[here].
+
+This rule identifies potential password guessing/brute force activity from a single address.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
 
 - Investigate the logon failure reason code and the targeted user names.
+  - Prioritize the investigation if the account is critical or has administrative privileges over the domain.
 - Investigate the source IP address of the failed Network Logon attempts.
-- Investigate other alerts associated with the user/host during the past 48 hours.
+  - Identify whether these attempts are coming from the internet or are internal.
+- Investigate other alerts associated with the involved users and source host during the past 48 hours.
 - Identify the source and the target computer and their roles in the IT environment.
+- Check whether the involved credentials are used in automation or scheduled tasks.
+- If this activity is suspicious, contact the account owner and confirm whether they are aware of it.
+- Examine the source host for derived artifacts that indicate compromise:
+  - Observe and collect information about the following activities in the alert source host:
+    - Attempts to contact external domains and addresses.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the host which is the source of this activity
+
 
-### False positive analysis
+*False positive analysis*
 
+
+- Understand the context of the authentications by contacting the asset owners. This activity can be related to a new or existing automation or business process that is in a failing state.
 - Authentication misconfiguration or obsolete credentials.
 - Service account password expired.
-- Trust relationship between the primary domain and the trusted domain issue.
-- Infrastructure or availability issue.
+- Domain trust relationship issues.
+- Infrastructure or availability issues.
+
+
+*Related rules*
 
-### Related rules
 
 - Multiple Logon Failure Followed by Logon Success - 4e85dc8a-3e41-40d8-bc28-91af7ac6cf60
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
-- If the host is a domain controller (DC):
-  - Activate your incident response plan for total Active Directory compromise.
-  - Review the privileges assigned to users that can access the DCs, to ensure that the least privilege principle is
-  being followed and to reduce the attack surface.
-- Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Isolate the source host to prevent further post-compromise behavior.
+- If the asset is exposed to the internet with RDP or other remote services available, take the necessary measures to restrict access to the asset. If not possible, limit the access via the firewall to only the needed IP addresses. Also, ensure the system uses robust authentication mechanisms and is patched regularly.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+- In some cases the source network address in Windows events 4625/4624 is not populated due to Microsoft logging limitations (examples in the references links). This edge case will break the rule condition and it won't trigger an alert.
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, source.ip with maxspan=10s [authentication
-where event.action == "logon-failed" and /* event 4625 need to be
-logged */ winlog.logon.type : "Network" and source.ip != null
-and source.ip != "127.0.0.1" and source.ip != "::1" and not
-user.name : ("ANONYMOUS LOGON", "-", "*$") and not user.domain == "NT
-AUTHORITY" and /* noisy failure status codes often
-associated to authentication misconfiguration : 0xC000015B - The
-user has not been granted the requested logon type (also called the
-logon right) at this machine. 0XC000005E - There are currently no
-logon servers available to service the logon request. 0XC0000133
-- Clocks between DC and other computer too far out of sync.
-0XC0000192 An attempt was made to logon, but the Netlogon service was
-not started. */ not winlog.event_data.Status : ("0xC000015B",
-"0XC000005E", "0XC0000133", "0XC0000192")] with runs=10
+[source, js]
 ----------------------------------
+sequence by winlog.computer_name, source.ip with maxspan=10s
+  [authentication where event.action == "logon-failed" and
+    /* event 4625 need to be logged */
+    winlog.logon.type : "Network" and
+    source.ip != null and source.ip != "127.0.0.1" and source.ip != "::1" and
+    not user.name : ("ANONYMOUS LOGON", "-", "*$") and not user.domain == "NT AUTHORITY" and
+
+    /*
+    noisy failure status codes often associated to authentication misconfiguration :
+     0xC000015B - The user has not been granted the requested logon type (also called the logon right) at this machine.
+     0XC000005E	- There are currently no logon servers available to service the logon request.
+     0XC0000133	- Clocks between DC and other computer too far out of sync.
+     0XC0000192	An attempt was made to logon, but the Netlogon service was not started.
+    */
+    not winlog.event_data.Status : ("0xC000015B", "0XC000005E", "0XC0000133", "0XC0000192")] with runs=10
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -117,3 +158,11 @@ not started. */ not winlog.event_data.Status : ("0xC000015B",
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Sub-technique:
+** Name: Password Guessing
+** ID: T1110.001
+** Reference URL: https://attack.mitre.org/techniques/T1110/001/
+* Sub-technique:
+** Name: Password Spraying
+** ID: T1110.003
+** Reference URL: https://attack.mitre.org/techniques/T1110/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/multiple-okta-client-addresses-for-a-single-user-session.asciidoc b/docs/detections/prebuilt-rules/rule-details/multiple-okta-client-addresses-for-a-single-user-session.asciidoc
new file mode 100644
index 0000000000..e3c03454a6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/multiple-okta-client-addresses-for-a-single-user-session.asciidoc
@@ -0,0 +1,79 @@
+[[multiple-okta-client-addresses-for-a-single-user-session]]
+=== Multiple Okta Client Addresses for a Single User Session
+
+Detects when a user has started multiple Okta sessions with the same user account and different session IDs. This may indicate an attacker has compromised a user's Okta account and is using it to access the organization's resources.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 60m
+
+*Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://developer.okta.com/docs/reference/api/system-log/
+* https://developer.okta.com/docs/reference/api/event-types/
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Initial Access
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:okta.system
+    and okta.authentication_context.external_session_id:* and okta.debug_context.debug_data.dt_hash:*
+    and not (okta.actor.id: okta* or okta.actor.display_name: okta*)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Cloud Accounts
+** ID: T1078.004
+** Reference URL: https://attack.mitre.org/techniques/T1078/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/multiple-okta-sessions-detected-for-a-single-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/multiple-okta-sessions-detected-for-a-single-user.asciidoc
new file mode 100644
index 0000000000..765de89213
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/multiple-okta-sessions-detected-for-a-single-user.asciidoc
@@ -0,0 +1,78 @@
+[[multiple-okta-sessions-detected-for-a-single-user]]
+=== Multiple Okta Sessions Detected for a Single User
+
+Detects when a user has started multiple Okta sessions with the same user account and different session IDs. This may indicate that an attacker has stolen the user's session cookie and is using it to access the user's account from a different location.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 60m
+
+*Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://developer.okta.com/docs/reference/api/system-log/
+* https://developer.okta.com/docs/reference/api/event-types/
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Lateral Movement
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:okta.system and okta.event_type:user.session.start and okta.authentication_context.external_session_id:*
+    and not (okta.actor.id: okta* or okta.actor.display_name: okta*) 
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Use Alternate Authentication Material
+** ID: T1550
+** Reference URL: https://attack.mitre.org/techniques/T1550/
+* Sub-technique:
+** Name: Web Session Cookie
+** ID: T1550.004
+** Reference URL: https://attack.mitre.org/techniques/T1550/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/multiple-okta-user-auth-events-with-same-device-token-hash-behind-a-proxy.asciidoc b/docs/detections/prebuilt-rules/rule-details/multiple-okta-user-auth-events-with-same-device-token-hash-behind-a-proxy.asciidoc
new file mode 100644
index 0000000000..b957965537
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/multiple-okta-user-auth-events-with-same-device-token-hash-behind-a-proxy.asciidoc
@@ -0,0 +1,138 @@
+[[multiple-okta-user-auth-events-with-same-device-token-hash-behind-a-proxy]]
+=== Multiple Okta User Auth Events with Same Device Token Hash Behind a Proxy
+
+Detects when Okta user authentication events are reported for multiple users with the same device token hash behind a proxy.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://developer.okta.com/docs/reference/api/system-log/
+* https://developer.okta.com/docs/reference/api/event-types/
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Credential Access
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Multiple Okta User Auth Events with Same Device Token Hash Behind a Proxy*
+
+
+This rule detects when Okta user authentication events are reported for multiple users with the same device token hash behind a proxy. This may indicate that a shared device between users, or that a user is using a proxy to access multiple accounts for password spraying.
+
+
+*Possible investigation steps:*
+
+- Identify the users involved in this action by examining the `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, and `okta.actor.display_name` fields.
+- Determine the device client used for these actions by analyzing `okta.client.ip`, `okta.client.user_agent.raw_user_agent`, `okta.client.zone`, `okta.client.device`, and `okta.client.id` fields.
+    - Since the device is behind a proxy, the `okta.client.ip` field will not be useful for determining the actual device IP address.
+- Review the `okta.request.ip_chain` field for more information about the geographic location of the proxy.
+- With Okta end users identified, review the `okta.debug_context.debug_data.dt_hash` field.
+    - Historical analysis should indicate if this device token hash is commonly associated with the user.
+- Review the `okta.event_type` field to determine the type of authentication event that occurred.
+    - If the event type is `user.authentication.sso`, the user may have legitimately started a session via a proxy for security or privacy reasons.
+    - If the event type is `user.authentication.password`, the user may be using a proxy to access multiple accounts for password spraying.
+- Examine the `okta.outcome.result` field to determine if the authentication was successful.
+- Review the past activities of the actor(s) involved in this action by checking their previous actions.
+- Evaluate the actions that happened just before and after this event in the `okta.event_type` field to help understand the full context of the activity.
+    - This may help determine the authentication and authorization actions that occurred between the user, Okta and application.
+
+
+*False positive analysis:*
+
+- A user may have legitimately started a session via a proxy for security or privacy reasons.
+- Users may share an endpoint related to work or personal use in which separate Okta accounts are used.
+    - Architecturally, this shared endpoint may leverage a proxy for security or privacy reasons.
+    - Shared systems such as Kiosks and conference room computers may be used by multiple users.
+    - Shared working spaces may have a single endpoint that is used by multiple users.
+
+
+*Response and remediation:*
+
+- Review the profile of the users involved in this action to determine if proxy usage may be expected.
+- If the user is legitimate and the authentication behavior is not suspicious based on device analysis, no action is required.
+- If the user is legitimate but the authentication behavior is suspicious, consider resetting passwords for the users involves and enabling multi-factor authentication (MFA).
+    - If MFA is already enabled, consider resetting MFA for the users.
+- If any of the users are not legitimate, consider deactivating the user's account.
+- Conduct a review of Okta policies and ensure they are in accordance with security best practices.
+- Check with internal IT teams to determine if the accounts involved recently had MFA reset at the request of the user.
+    - If so, confirm with the user this was a legitimate request.
+    - If so and this was not a legitimate request, consider deactivating the user's account temporarily.
+        - Reset passwords and reset MFA for the user.
+- If this is a false positive, consider adding the `okta.debug_context.debug_data.dt_hash` field to the `exceptions` list in the rule.
+    - This will prevent future occurrences of this event for this device from triggering the rule.
+
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:okta.system
+    and not okta.actor.id:okta* and okta.debug_context.debug_data.dt_hash:*
+    and okta.event_type:user.authentication* and okta.security_context.is_proxy:true
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Brute Force
+** ID: T1110
+** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Sub-technique:
+** Name: Password Spraying
+** ID: T1110.003
+** Reference URL: https://attack.mitre.org/techniques/T1110/003/
+* Technique:
+** Name: Brute Force
+** ID: T1110
+** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Sub-technique:
+** Name: Credential Stuffing
+** ID: T1110.004
+** Reference URL: https://attack.mitre.org/techniques/T1110/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/multiple-vault-web-credentials-read.asciidoc b/docs/detections/prebuilt-rules/rule-details/multiple-vault-web-credentials-read.asciidoc
index 6119cfa5e8..149360ecba 100644
--- a/docs/detections/prebuilt-rules/rule-details/multiple-vault-web-credentials-read.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/multiple-vault-web-credentials-read.asciidoc
@@ -5,69 +5,77 @@ Windows Credential Manager allows you to create, view, or delete saved credentia
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=5382
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-
-*Version*: 2 (<<multiple-vault-web-credentials-read-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 8.5.0
+*Version*: 10
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, winlog.process.pid with maxspan=1s /* 2
-consecutive vault reads from same pid for web creds */ [any where
-event.code : "5382" and (winlog.event_data.SchemaFriendlyName :
-"Windows Web Password Credential" or winlog.event_data.Resource :
-"http*") and not winlog.event_data.SubjectLogonId : "0x3e7"] [any
-where event.code : "5382" and (winlog.event_data.SchemaFriendlyName
-: "Windows Web Password Credential" or winlog.event_data.Resource :
-"http*") and not winlog.event_data.SubjectLogonId : "0x3e7"]
+[source, js]
 ----------------------------------
+sequence by winlog.computer_name, winlog.process.pid with maxspan=1s
 
-==== Threat mapping
+ /* 2 consecutive vault reads from same pid for web creds */
+
+ [any where event.code : "5382" and
+  (winlog.event_data.SchemaFriendlyName : "Windows Web Password Credential" and winlog.event_data.Resource : "http*") and
+  not winlog.event_data.SubjectLogonId : "0x3e7" and 
+  not winlog.event_data.Resource : "http://localhost/"]
+
+ [any where event.code : "5382" and
+  (winlog.event_data.SchemaFriendlyName : "Windows Web Password Credential" and winlog.event_data.Resource : "http*") and
+  not winlog.event_data.SubjectLogonId : "0x3e7" and 
+  not winlog.event_data.Resource : "http://localhost/"]
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,10 +87,11 @@ where event.code : "5382" and (winlog.event_data.SchemaFriendlyName
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[multiple-vault-web-credentials-read-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Formatting only
-
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Sub-technique:
+** Name: Windows Credential Manager
+** ID: T1555.004
+** Reference URL: https://attack.mitre.org/techniques/T1555/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/my-first-rule.asciidoc b/docs/detections/prebuilt-rules/rule-details/my-first-rule.asciidoc
new file mode 100644
index 0000000000..37f3bc07b9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/my-first-rule.asciidoc
@@ -0,0 +1,61 @@
+[[my-first-rule]]
+=== My First Rule
+
+This rule helps you test and practice using alerts with Elastic Security as you get set up. It’s not a sign of threat activity.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* auditbeat-*
+* filebeat-*
+* logs-*
+* winlogbeat-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 24h
+
+*Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 1
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-rules.html
+
+*Tags*: 
+
+* Use Case: Guided Onboarding
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+This is a test alert.
+
+This alert does not show threat activity. Elastic created this alert to help you understand how alerts work.
+
+For normal rules, the Investigation Guide will help analysts investigate alerts.
+
+This alert will show once every 24 hours for each host. It is safe to disable this rule.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind:event
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/namespace-manipulation-using-unshare.asciidoc b/docs/detections/prebuilt-rules/rule-details/namespace-manipulation-using-unshare.asciidoc
index a1335aafff..e527ba7243 100644
--- a/docs/detections/prebuilt-rules/rule-details/namespace-manipulation-using-unshare.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/namespace-manipulation-using-unshare.asciidoc
@@ -1,59 +1,113 @@
 [[namespace-manipulation-using-unshare]]
 === Namespace Manipulation Using Unshare
 
-Identifies  suspicious usage of unshare to manipulate system namespaces. Unshare can be utilized to escalate privileges or escape container security boundaries. Threat actors have utilized this binary to allow themselves to escape to the host and access other resources or escalate privileges.
+Identifies suspicious usage of unshare to manipulate system namespaces. Unshare can be utilized to escalate privileges or escape container security boundaries. Threat actors have utilized this binary to allow themselves to escape to the host and access other resources or escalate privileges.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://man7.org/linux/man-pages/man1/unshare.1.html
 * https://www.crowdstrike.com/blog/cve-2022-0185-kubernetes-container-escape-using-linux-kernel-exploit/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Privilege Escalation
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Version*: 1
+*Version*: 9
 
-*Added ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and event.action == "exec" and
-process.executable: "/usr/bin/unshare" and not
-process.parent.executable: ("/usr/bin/udevadm",
-"*/lib/systemd/systemd-udevd", "/usr/bin/unshare") and not
-process.args : "/usr/bin/snap"
+[source, js]
 ----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action : ("exec", "exec_event") and
+process.executable: "/usr/bin/unshare" and
+not process.parent.executable: ("/usr/bin/udevadm", "*/lib/systemd/systemd-udevd", "/usr/bin/unshare") and
+not process.args == "/usr/bin/snap" and not process.parent.name in ("zz-proxmox-boot", "java")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
diff --git a/docs/detections/prebuilt-rules/rule-details/netcat-listener-established-inside-a-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/netcat-listener-established-inside-a-container.asciidoc
new file mode 100644
index 0000000000..9a8e259e72
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/netcat-listener-established-inside-a-container.asciidoc
@@ -0,0 +1,74 @@
+[[netcat-listener-established-inside-a-container]]
+=== Netcat Listener Established Inside A Container
+
+This rule detects an established netcat listener running inside a container. Netcat is a utility used for reading and writing data across network connections, and it can be used for malicious purposes such as establishing a backdoor for persistence or exfiltrating data.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where container.id: "*" and event.type== "start" 
+and event.action in ("fork", "exec") and 
+(
+process.name:("nc","ncat","netcat","netcat.openbsd","netcat.traditional") or
+/*account for tools that execute utilities as a subprocess, in this case the target utility name will appear as a process arg*/
+process.args: ("nc","ncat","netcat","netcat.openbsd","netcat.traditional")
+) and (
+          /* bind shell to echo for command execution */
+          (process.args:("-*l*", "--listen", "-*p*", "--source-port") and process.args:("-c", "--sh-exec", "-e", "--exec", "echo","$*"))
+          /* bind shell to specific port */
+          or process.args:("-*l*", "--listen", "-*p*", "--source-port")
+          )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/netcat-listener-established-via-rlwrap.asciidoc b/docs/detections/prebuilt-rules/rule-details/netcat-listener-established-via-rlwrap.asciidoc
new file mode 100644
index 0000000000..1f2783cb6d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/netcat-listener-established-via-rlwrap.asciidoc
@@ -0,0 +1,105 @@
+[[netcat-listener-established-via-rlwrap]]
+=== Netcat Listener Established via rlwrap
+
+Monitors for the execution of a netcat listener via rlwrap. rlwrap is a 'readline wrapper', a small utility that uses the GNU Readline library to allow the editing of keyboard input for any command. This utility can be used in conjunction with netcat to gain a more stable reverse shell.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and 
+process.name == "rlwrap" and process.args in ("nc", "ncat", "netcat", "nc.openbsd", "socat") and
+process.args : "*l*" and process.args_count >= 4
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/netsh-helper-dll.asciidoc b/docs/detections/prebuilt-rules/rule-details/netsh-helper-dll.asciidoc
new file mode 100644
index 0000000000..6a3ce4b70c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/netsh-helper-dll.asciidoc
@@ -0,0 +1,77 @@
+[[netsh-helper-dll]]
+=== Netsh Helper DLL
+
+Identifies the addition of a Netsh Helper DLL, netsh.exe supports the addition of these DLLs to extend its functionality. Attackers may abuse this mechanism to execute malicious payloads every time the utility is executed, which can be done by administrators or a scheduled task.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.registry-*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+registry where host.os.type == "windows" and event.type == "change" and
+  registry.path : (
+    "HKLM\\Software\\Microsoft\\netsh\\*",
+    "\\REGISTRY\\MACHINE\\Software\\Microsoft\\netsh\\*"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: Netsh Helper DLL
+** ID: T1546.007
+** Reference URL: https://attack.mitre.org/techniques/T1546/007/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/network-activity-detected-via-cat.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-activity-detected-via-cat.asciidoc
new file mode 100644
index 0000000000..42df1dd1c3
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/network-activity-detected-via-cat.asciidoc
@@ -0,0 +1,185 @@
+[[network-activity-detected-via-cat]]
+=== Network Activity Detected via cat
+
+This rule monitors for the execution of the cat command, followed by a connection attempt by the same process. Cat is capable of transfering data via tcp/udp channels by redirecting its read output to a /dev/tcp or /dev/udp channel. This activity is highly suspicious, and should be investigated. Attackers may leverage this capability to transfer tools or files to another host in the network or exfiltrate data while attempting to evade detection in the process.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Network Activity Detected via cat*
+
+
+Attackers may leverage the `cat` utility in conjunction with a listener to read all bytes of a file, and output the content to a `/dev/tcp` or `/dev/udp` channel to transfer/exfiltrate file contents to a remote system. 
+
+This rule looks for a sequence of a `cat` execution event followed by a network connection attempt by the same `cat` process. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Identify any signs of suspicious network activity or anomalies that may indicate command and control activity or data exfiltration. This could include unexpected traffic patterns or unusual network behavior.
+  - Investigate listening ports and open sockets to look for potential protocol tunneling, reverse shells, or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+  - !{osquery{"label":"Osquery - Retrieve Process Info","query":"SELECT name, cmdline, parent, path, uid FROM processes"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+
+
+*Related rules*
+
+
+- Suspicious Network Activity to the Internet by Previously Unknown Executable - 53617418-17b4-4e9c-8a2c-8deb8086ca4b
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors, such as reverse shells, reverse proxies, or droppers, that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.entity_id with maxspan=1s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+   process.name == "cat" and process.parent.name in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")]
+  [network where host.os.type == "linux" and event.action in ("connection_attempted", "disconnect_received") and
+   process.name == "cat" and not (destination.ip == null or destination.ip == "0.0.0.0" or cidrmatch(
+     destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.0.0.0/29",
+     "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
+     "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
+     "192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
+     "FF00::/8"
+     )
+   )]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
diff --git a/docs/detections/prebuilt-rules/rule-details/network-activity-detected-via-kworker.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-activity-detected-via-kworker.asciidoc
new file mode 100644
index 0000000000..cf1b872f28
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/network-activity-detected-via-kworker.asciidoc
@@ -0,0 +1,124 @@
+[[network-activity-detected-via-kworker]]
+=== Network Activity Detected via Kworker
+
+This rule monitors for network connections from a kworker process. kworker, or kernel worker, processes are part of the kernel's workqueue mechanism. They are responsible for executing work that has been scheduled to be done in kernel space, which might include tasks like handling interrupts, background activities, and other kernel-related tasks. Attackers may attempt to evade detection by masquerading as a kernel worker process.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.category:network and event.action:(connection_attempted or connection_accepted) and 
+process.name:kworker* and not destination.ip:(
+  10.0.0.0/8 or
+  127.0.0.0/8 or
+  169.254.0.0/16 or
+  172.16.0.0/12 or
+  192.168.0.0/16 or
+  224.0.0.0/4 or
+  "::1" or
+  "FE80::/10" or
+  "FF00::/8"
+) and not destination.port:2049
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Technique:
+** Name: Rootkit
+** ID: T1014
+** Reference URL: https://attack.mitre.org/techniques/T1014/
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over C2 Channel
+** ID: T1041
+** Reference URL: https://attack.mitre.org/techniques/T1041/
diff --git a/docs/detections/prebuilt-rules/rule-details/network-connection-from-binary-with-rwx-memory-region.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-connection-from-binary-with-rwx-memory-region.asciidoc
new file mode 100644
index 0000000000..416009582a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/network-connection-from-binary-with-rwx-memory-region.asciidoc
@@ -0,0 +1,103 @@
+[[network-connection-from-binary-with-rwx-memory-region]]
+=== Network Connection from Binary with RWX Memory Region
+
+Monitors for the execution of a unix binary with read, write and execute memory region permissions, followed by a network connection. The mprotect() system call is used to change the access protections on a region of memory that has already been allocated. This syscall allows a process to modify the permissions of pages in its virtual address space, enabling or disabling permissions such as read, write, and execute for those pages. RWX permissions on memory is in many cases overly permissive, and should (especially in conjunction with an outbound network connection) be analyzed thoroughly.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://man7.org/linux/man-pages/man2/mprotect.2.html
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires the use of the `auditd_manager` integration. `Auditd_manager` is a tool designed to simplify and enhance the management of the audit subsystem in Linux systems. It provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system. The following steps should be executed in order to install and deploy `auditd_manager` on a Linux system.
+```
+Kibana -->
+Management -->
+Integrations -->
+Auditd Manager -->
+Add Auditd Manager
+```
+`Auditd_manager` subscribes to the kernel and receives events as they occur without any additional configuration. However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+For this detection rule to trigger, the following additional audit rules are required to be added to the integration:
+```
+-a always,exit -F arch=b64 -S mprotect
+```
+Add the newly installed `auditd manager` to an agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sample by host.id, process.pid, process.name
+  /* auditd.data.a2 == "7" translates to RWX memory region protection (PROT_READ | PROT_WRITE | PROT_EXEC) */
+  [process where host.os.type == "linux" and auditd.data.syscall == "mprotect" and auditd.data.a2 == "7"]
+  [network where host.os.type == "linux" and event.type == "start" and event.action == "connection_attempted" and
+   not cidrmatch(destination.ip, "127.0.0.0/8", "169.254.0.0/16", "224.0.0.0/4", "::1")]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/network-connection-via-certutil.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-connection-via-certutil.asciidoc
index 954d524713..eae02c3386 100644
--- a/docs/detections/prebuilt-rules/rule-details/network-connection-via-certutil.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/network-connection-via-certutil.asciidoc
@@ -5,96 +5,100 @@ Identifies certutil.exe making a network connection. Adversaries could abuse cer
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 * https://frsecure.com/malware-incident-response-playbook/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
-* Investigation Guide
-
-*Version*: 102 (<<network-connection-via-certutil-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Network Connection via Certutil
+*Triage and analysis*
+
 
-Attackers can abuse `certutil.exe` to download malware, offensive security tools, and certificates from external sources
-in order to take the next steps in a compromised environment.
 
-This rule looks for network events where `certutil.exe` contacts IP ranges other than the ones specified in
-[IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml)
+*Investigating Network Connection via Certutil*
+
+
+Attackers can abuse `certutil.exe` to download malware, offensive security tools, and certificates from external sources in order to take the next steps in a compromised environment.
+
+This rule looks for network events where `certutil.exe` contacts IP ranges other than the ones specified in https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml[IANA IPv4 Special-Purpose Address Registry]
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/interactive-investigation-guides.html[Investigate Markdown Plugin] introduced in Elastic Stack version 8.8.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
+  - !{investigate{"label":"Alerts associated with the user in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"user.id","queryType":"phrase","value":"{{user.id}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
+  - !{investigate{"label":"Alerts associated with the host in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"host.name","queryType":"phrase","value":"{{host.name}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
 - Investigate if the downloaded file was executed.
 - Determine the context in which `certutil.exe` and the file were run.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the downloaded file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+        - !{investigate{"label":"Investigate the Subject Process Network Events","providers":[[{"excluded":false,"field":"process.entity_id","queryType":"phrase","value":"{{process.entity_id}}","valueType":"string"},{"excluded":false,"field":"event.category","queryType":"phrase","value":"network","valueType":"string"}]]}}
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. If trusted software uses this command and the triage has not identified
-anything suspicious, this alert can be closed as a false positive.
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination
-of user and command line conditions.
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. If trusted software uses this command and the triage has not identified anything suspicious, this alert can be closed as a false positive.
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -102,37 +106,28 @@ of user and command line conditions.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where process.name :
-"certutil.exe" and event.type == "start"] [network where
-process.name : "certutil.exe" and not cidrmatch(destination.ip,
-"10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12",
-"192.0.0.0/24", "192.0.0.0/29",
-"192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32",
-"192.0.0.171/32", "192.0.2.0/24", "192.31.196.0/24",
-"192.52.193.0/24", "192.168.0.0/16",
-"192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10", "192.175.48.0/24",
-"198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4",
-"::1", "FE80::/10", "FF00::/8")]
+[source, js]
 ----------------------------------
+network where host.os.type == "windows" and process.name : "certutil.exe" and
+  not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
+                                "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32",
+                                "192.0.0.171/32", "192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24",
+                                "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10", "192.175.48.0/24",
+                                "198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
+                                "FE80::/10", "FF00::/8") and
+  not dns.question.name in ("localhost", "*.digicert.com", "ctldl.windowsupdate.com")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -144,59 +139,3 @@ process.name : "certutil.exe" and not cidrmatch(destination.ip,
 ** Name: Ingress Tool Transfer
 ** ID: T1105
 ** Reference URL: https://attack.mitre.org/techniques/T1105/
-
-[[network-connection-via-certutil-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 10 (8.4.0 release)::
-* Formatting only
-
-Version 8 (8.3.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where process.name :
-"certutil.exe" and event.type == "start"] [network where
-process.name : "certutil.exe" and not cidrmatch(destination.ip,
-"10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16")]
-----------------------------------
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:connection and
-process.name:certutil.exe and not destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:certutil.exe and event.action:"Network connection
-detected (rule: NetworkConnect)" and not destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/network-connection-via-compiled-html-file.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-connection-via-compiled-html-file.asciidoc
index a545bae483..3d8b4f9b06 100644
--- a/docs/detections/prebuilt-rules/rule-details/network-connection-via-compiled-html-file.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/network-connection-via-compiled-html-file.asciidoc
@@ -5,63 +5,137 @@ Compiled HTML files (.chm) are commonly distributed as part of the Microsoft HTM
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
 
-*Version*: 100 (<<network-connection-via-compiled-html-file-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.6.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Triage and analysis*
+
+
+
+*Investigating Network Connection via Compiled HTML File*
+
+
+CHM (Compiled HTML) files are a format for delivering online help files on Windows. CHM files are compressed compilations of various content, such as HTML documents, images, and scripting/web-related programming languages such as VBA, JScript, Java, and ActiveX.
+
+When users double-click CHM files, the HTML Help executable program (`hh.exe`) will execute them. `hh.exe` also can be used to execute code embedded in those files, PowerShell scripts, and executables. This makes it useful for attackers not only to proxy the execution of malicious payloads via a signed binary that could bypass security controls, but also to gain initial access to environments via social engineering methods.
+
+This rule identifies network connections done by `hh.exe`, which can potentially indicate abuse to download malicious files or tooling, or masquerading.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - Examine the command lines for suspicious activities.
+  - Retrieve `.chm`, `.ps1`, and other files that were involved for further examination.
+  - Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+  - Investigate the file digital signature and process original filename, if suspicious, treat it as potential malware.
+- Investigate the target host that the signed binary is communicating with.
+  - Check if the domain is newly registered or unexpected.
+  - Check the reputation of the domain or IP address.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executables, scripts and help files retrieved from the system using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of user and command line conditions.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- If the malicious file was delivered via phishing:
+  - Block the email sender from sending future emails.
+  - Block the malicious web pages.
+  - Remove emails from the sender from mailboxes.
+  - Consider improvements to the security awareness program.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where process.name : "hh.exe"
-and event.type == "start"] [network where process.name : "hh.exe"
-and not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8",
-"169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
-"192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
-"192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16",
-"192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
-"192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24",
-"203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
-"FF00::/8")]
+[source, js]
 ----------------------------------
+sequence by process.entity_id
+  [process where host.os.type == "windows" and process.name : "hh.exe" and event.type == "start"]
+  [network where host.os.type == "windows" and process.name : "hh.exe" and
+     not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
+       "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32",
+       "192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
+       "100.64.0.0/10", "192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
+       "FE80::/10", "FF00::/8") and
+     not dns.question.name : "localhost"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,8 +147,10 @@ and not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8",
 ** Name: User Execution
 ** ID: T1204
 ** Reference URL: https://attack.mitre.org/techniques/T1204/
-
-
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -83,66 +159,7 @@ and not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8",
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[network-connection-via-compiled-html-file-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 11 (8.4.0 release)::
-* Formatting only
-
-Version 9 (7.16.0 release)::
-* Formatting only
-
-Version 8 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where process.name : "hh.exe"
-and event.type == "start"] [network where process.name : "hh.exe"
-and not cidrmatch(destination.ip, "10.0.0.0/8", "172.16.0.0/12",
-"192.168.0.0/16")]
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:connection and
-process.name:hh.exe and not destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:hh.exe and event.action:"Network connection detected
-(rule: NetworkConnect)" and not destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:hh.exe and event.action:"Network connection detected
-(rule: NetworkConnect)" and not destination.ip:10.0.0.0/8 and not
-destination.ip:172.16.0.0/12 and not destination.ip:192.168.0.0/16
-----------------------------------
-
+* Sub-technique:
+** Name: Compiled HTML File
+** ID: T1218.001
+** Reference URL: https://attack.mitre.org/techniques/T1218/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/network-connection-via-msxsl.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-connection-via-msxsl.asciidoc
index 8effc9dc44..41f4a60238 100644
--- a/docs/detections/prebuilt-rules/rule-details/network-connection-via-msxsl.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/network-connection-via-msxsl.asciidoc
@@ -5,63 +5,60 @@ Identifies msxsl.exe making a network connection. This may indicate adversarial
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-
-*Version*: 100 (<<network-connection-via-msxsl-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where process.name :
-"msxsl.exe" and event.type == "start"] [network where process.name :
-"msxsl.exe" and not cidrmatch(destination.ip, "10.0.0.0/8",
-"127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
-"192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
-"192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16",
-"192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
-"192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24",
-"203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
-"FF00::/8")]
+[source, js]
 ----------------------------------
+sequence by process.entity_id
+  [process where host.os.type == "windows" and process.name : "msxsl.exe" and event.type == "start"]
+  [network where host.os.type == "windows" and process.name : "msxsl.exe" and
+     not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
+       "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32",
+       "192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
+       "100.64.0.0/10", "192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
+       "FE80::/10", "FF00::/8")]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,53 +70,3 @@ sequence by process.entity_id [process where process.name :
 ** Name: XSL Script Processing
 ** ID: T1220
 ** Reference URL: https://attack.mitre.org/techniques/T1220/
-
-[[network-connection-via-msxsl-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 7 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where process.name :
-"msxsl.exe" and event.type == "start"] [network where process.name :
-"msxsl.exe" and not cidrmatch(destination.ip, "10.0.0.0/8",
-"172.16.0.0/12", "192.168.0.0/16")]
-----------------------------------
-
-Version 6 (7.12.0 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:connection and
-process.name:msxsl.exe and not destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:msxsl.exe and event.action:"Network connection detected
-(rule: NetworkConnect)" and not destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/network-connection-via-recently-compiled-executable.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-connection-via-recently-compiled-executable.asciidoc
new file mode 100644
index 0000000000..5416c9d218
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/network-connection-via-recently-compiled-executable.asciidoc
@@ -0,0 +1,114 @@
+[[network-connection-via-recently-compiled-executable]]
+=== Network Connection via Recently Compiled Executable
+
+This rule monitors a sequence involving a program compilation event followed by its execution and a subsequent network connection event. This behavior can indicate the set up of a reverse tcp connection to a command-and-control server. Attackers may spawn reverse shells to establish persistence onto a target system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=1m
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+   process.name in ("gcc", "g++", "cc")] by process.args
+  [file where host.os.type == "linux" and event.action == "creation" and process.name == "ld"] by file.name
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec"] by process.name
+  [network where host.os.type == "linux" and event.action == "connection_attempted" and destination.ip != null and 
+   not cidrmatch(destination.ip, "127.0.0.0/8", "169.254.0.0/16", "224.0.0.0/4", "::1")] by process.name
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/network-connection-via-registration-utility.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-connection-via-registration-utility.asciidoc
index 386aa9d917..d838a0ed36 100644
--- a/docs/detections/prebuilt-rules/rule-details/network-connection-via-registration-utility.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/network-connection-via-registration-utility.asciidoc
@@ -5,217 +5,155 @@ Identifies the native Windows tools regsvr32.exe, regsvr64.exe, RegSvcs.exe, or
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
 
-*Version*: 100 (<<network-connection-via-registration-utility-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.6.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Security testing may produce events like this. Activity of this kind performed by non-engineers and ordinary users is unusual.
 
-==== Rule query
 
+*Investigating Network Connection via Registration Utility*
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where event.type == "start"
-and process.name : ("regsvr32.exe", "RegAsm.exe", "RegSvcs.exe")
-and not ( (?process.Ext.token.integrity_level_name :
-"System" or ?winlog.event_data.IntegrityLevel : "System") and
-(process.parent.name : "msiexec.exe" or process.parent.executable :
-("C:\\Program Files (x86)\\*.exe", "C:\\Program Files\\*.exe"))
-) ] [network where process.name : ("regsvr32.exe", "RegAsm.exe",
-"RegSvcs.exe") and not cidrmatch(destination.ip, "10.0.0.0/8",
-"127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
-"192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
-"192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16",
-"192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
-"192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24",
-"203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
-"FF00::/8") and network.protocol != "dns"]
-----------------------------------
 
-==== Threat mapping
+By examining the specific traits of Windows binaries -- such as process trees, command lines, network connections, registry modifications, and so on -- it's possible to establish a baseline of normal activity. Deviations from this baseline can indicate malicious activity such as masquerading, and deserve further investigation.
 
-*Framework*: MITRE ATT&CK^TM^
+This rule looks for the execution of `regsvr32.exe`, `RegAsm.exe`, or `RegSvcs.exe` utilities followed by a network connection to an external address. Attackers can abuse utilities to execute malicious files or masquerade as those utilities in order to bypass detections and evade defenses.
 
-* Tactic:
-** Name: Execution
-** ID: TA0002
-** Reference URL: https://attack.mitre.org/tactics/TA0002/
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: System Binary Proxy Execution
-** ID: T1218
-** Reference URL: https://attack.mitre.org/techniques/T1218/
+*Possible investigation steps*
 
-[[network-connection-via-registration-utility-history]]
-==== Rule version history
 
-Version 100 (8.5.0 release)::
-* Formatting only
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+  - Investigate the file digital signature and process original filename, if suspicious, treat it as potential malware.
+- Investigate the target host that the signed binary is communicating with.
+  - Check if the domain is newly registered or unexpected.
+  - Check the reputation of the domain or IP address.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-Version 13 (8.4.0 release)::
-* Formatting only
 
-Version 11 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where event.type == "start"
-and process.name : ("regsvr32.exe", "RegAsm.exe", "RegSvcs.exe")
-and not ( (process.Ext.token.integrity_level_name :
-"System" or winlog.event_data.IntegrityLevel : "System") and
-(process.parent.name : "msiexec.exe" or process.parent.executable :
-("C:\\Program Files (x86)\\*.exe", "C:\\Program Files\\*.exe"))
-) ] [network where process.name : ("regsvr32.exe", "RegAsm.exe",
-"RegSvcs.exe") and not cidrmatch(destination.ip, "10.0.0.0/8",
-"127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
-"192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
-"192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16",
-"192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
-"192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24",
-"203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
-"FF00::/8") and network.protocol != "dns"]
-----------------------------------
+*False positive analysis*
 
-Version 10 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where event.type == "start"
-and process.name : ("regsvr32.exe", "RegAsm.exe", "RegSvcs.exe")
-and not ( user.id == "S-1-5-18" and
-(process.parent.name : "msiexec.exe" or process.parent.executable :
-("C:\\Program Files (x86)\\*.exe", "C:\\Program Files\\*.exe"))
-) ] [network where process.name : ("regsvr32.exe", "RegAsm.exe",
-"RegSvcs.exe") and not cidrmatch(destination.ip, "10.0.0.0/8",
-"127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
-"192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
-"192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16",
-"192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
-"192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24",
-"203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
-"FF00::/8") and network.protocol != "dns"]
-----------------------------------
 
-Version 9 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where event.type == "start"
-and process.name : ("regsvr32.exe", "RegAsm.exe", "RegSvcs.exe")
-and not ( user.id == "S-1-5-18" and
-(process.parent.name : "msiexec.exe" or process.parent.executable :
-("C:\\Program Files (x86)\\*.exe", "C:\\Program Files\\*.exe"))
-) ] [network where process.name : ("regsvr32.exe", "RegAsm.exe",
-"RegSvcs.exe") and not cidrmatch(destination.ip, "10.0.0.0/8",
-"169.254.169.254", "172.16.0.0/12", "192.168.0.0/16") and
-network.protocol != "dns"]
-----------------------------------
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of destination IP address and command line conditions.
 
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where (process.name :
-"regsvr32.exe" or process.name : "regsvr64.exe" or
-process.name : "RegAsm.exe" or process.name : "RegSvcs.exe") and
-event.type == "start"] [network where (process.name : "regsvr32.exe"
-or process.name : "regsvr64.exe" or process.name :
-"RegAsm.exe" or process.name : "RegSvcs.exe") and not
-cidrmatch(destination.ip, "10.0.0.0/8", "169.254.169.254",
-"172.16.0.0/12", "192.168.0.0/16")]
-----------------------------------
 
-Version 7 (7.12.0 release)::
-* Formatting only
+*Response and remediation*
 
-Version 6 (7.11.0 release)::
-* Formatting only
 
-Version 5 (7.10.0 release)::
-* Rule name changed from: Network Connection via Regsvr
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:connection and
-process.name:(regsvr32.exe or regsvr64.exe) and not
-destination.ip:(10.0.0.0/8 or 169.254.169.254 or 172.16.0.0/12 or
-192.168.0.0/16)
-----------------------------------
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 4 (7.9.1 release)::
-* Formatting only
 
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:(regsvr32.exe or regsvr64.exe) and event.action:"Network
-connection detected (rule: NetworkConnect)" and not
-destination.ip:(10.0.0.0/8 or 169.254.169.254 or 172.16.0.0/12 or
-192.168.0.0/16)
-----------------------------------
+==== Rule query
+
 
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-(process.name:regsvr32.exe or process.name:regsvr64.exe) and
-event.action:"Network connection detected (rule: NetworkConnect)" and
-not destination.ip:169.254.169.254/32 and not
-destination.ip:10.0.0.0/8 and not destination.ip:172.16.0.0/12 and not
-destination.ip:192.168.0.0/16
+sequence by process.entity_id
+  [process where host.os.type == "windows" and event.type == "start" and
+   process.name : ("regsvr32.exe", "RegAsm.exe", "RegSvcs.exe") and
+   not (
+         (?process.Ext.token.integrity_level_name : "System" or ?winlog.event_data.IntegrityLevel : "System") and
+         (process.parent.name : "msiexec.exe" or process.parent.executable : ("C:\\Program Files (x86)\\*.exe", "C:\\Program Files\\*.exe"))
+       )
+   ]
+  [network where host.os.type == "windows" and process.name : ("regsvr32.exe", "RegAsm.exe", "RegSvcs.exe")  and
+   not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
+       "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32",
+       "192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
+       "100.64.0.0/10", "192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
+       "FE80::/10", "FF00::/8") and network.protocol != "dns"]
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: Regsvcs/Regasm
+** ID: T1218.009
+** Reference URL: https://attack.mitre.org/techniques/T1218/009/
+* Sub-technique:
+** Name: Regsvr32
+** ID: T1218.010
+** Reference URL: https://attack.mitre.org/techniques/T1218/010/
diff --git a/docs/detections/prebuilt-rules/rule-details/network-connection-via-signed-binary.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-connection-via-signed-binary.asciidoc
index 08f8b8e20a..3986c50422 100644
--- a/docs/detections/prebuilt-rules/rule-details/network-connection-via-signed-binary.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/network-connection-via-signed-binary.asciidoc
@@ -5,167 +5,139 @@ Binaries signed with trusted digital certificates can execute on Windows systems
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
 
-*Version*: 100 (<<network-connection-via-signed-binary-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.6.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Rule query
+*Triage and analysis*
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where (process.name :
-"expand.exe" or process.name : "extrac32.exe" or
-process.name : "ieexec.exe" or process.name : "makecab.exe") and
-event.type == "start"] [network where (process.name : "expand.exe"
-or process.name : "extrac32.exe" or process.name :
-"ieexec.exe" or process.name : "makecab.exe") and not
-cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8",
-"169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.0.0.0/29",
-"192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24", "192.31.196.0/24",
-"192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
-"100.64.0.0/10", "192.175.48.0/24", "198.18.0.0/15",
-"198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
-"FE80::/10", "FF00::/8")]
-----------------------------------
 
-==== Threat mapping
+*Investigating Network Connection via Signed Binary*
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: System Binary Proxy Execution
-** ID: T1218
-** Reference URL: https://attack.mitre.org/techniques/T1218/
+By examining the specific traits of Windows binaries (such as process trees, command lines, network connections, registry modifications, and so on) it's possible to establish a baseline of normal activity. Deviations from this baseline can indicate malicious activity, such as masquerading and deserve further investigation.
 
+This rule looks for the execution of `expand.exe`, `extrac32.exe`, `ieexec.exe`, or `makecab.exe` utilities, followed by a network connection to an external address. Attackers can abuse utilities to execute malicious files or masquerade as those utilities to bypass detections and evade defenses.
 
-* Tactic:
-** Name: Execution
-** ID: TA0002
-** Reference URL: https://attack.mitre.org/tactics/TA0002/
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-[[network-connection-via-signed-binary-history]]
-==== Rule version history
 
-Version 100 (8.5.0 release)::
-* Formatting only
+*Possible investigation steps*
 
-Version 11 (8.4.0 release)::
-* Formatting only
 
-Version 9 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where (process.name :
-"expand.exe" or process.name : "extrac.exe" or
-process.name : "ieexec.exe" or process.name : "makecab.exe") and
-event.type == "start"] [network where (process.name : "expand.exe"
-or process.name : "extrac.exe" or process.name :
-"ieexec.exe" or process.name : "makecab.exe") and not
-cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8",
-"169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.0.0.0/29",
-"192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24", "192.31.196.0/24",
-"192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
-"100.64.0.0/10", "192.175.48.0/24", "198.18.0.0/15",
-"198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
-"FE80::/10", "FF00::/8")]
-----------------------------------
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+  - Investigate the file digital signature and process original filename, if suspicious, treat it as potential malware.
+- Investigate the target host that the signed binary is communicating with.
+  - Check if the domain is newly registered or unexpected.
+  - Check the reputation of the domain or IP address.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-Version 8 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where (process.name :
-"expand.exe" or process.name : "extrac.exe" or
-process.name : "ieexec.exe" or process.name : "makecab.exe") and
-event.type == "start"] [network where (process.name : "expand.exe"
-or process.name : "extrac.exe" or process.name :
-"ieexec.exe" or process.name : "makecab.exe") and not
-cidrmatch(destination.ip, "10.0.0.0/8", "172.16.0.0/12",
-"192.168.0.0/16")]
-----------------------------------
 
-Version 7 (7.12.0 release)::
-* Formatting only
+*False positive analysis*
 
-Version 6 (7.11.0 release)::
-* Formatting only
 
-Version 5 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:connection and
-process.name:(expand.exe or extrac.exe or ieexec.exe or makecab.exe)
-and not destination.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of destination IP address and command line conditions.
 
-Version 4 (7.9.1 release)::
-* Formatting only
 
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:(expand.exe or extrac.exe or ieexec.exe or makecab.exe)
-and event.action:"Network connection detected (rule: NetworkConnect)"
-and not destination.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
 
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-(process.name:expand.exe or process.name:extrac.exe or
-process.name:ieexec.exe or process.name:makecab.exe) and
-event.action:"Network connection detected (rule: NetworkConnect)" and
-not destination.ip:10.0.0.0/8 and not destination.ip:172.16.0.0/12 and
-not destination.ip:192.168.0.0/16
+sequence by process.entity_id
+  [process where host.os.type == "windows" and (process.name : "expand.exe" or process.name : "extrac32.exe" or
+                 process.name : "ieexec.exe" or process.name : "makecab.exe") and
+                 event.type == "start"]
+  [network where host.os.type == "windows" and (process.name : "expand.exe" or process.name : "extrac32.exe" or
+                 process.name : "ieexec.exe" or process.name : "makecab.exe") and
+    not cidrmatch(destination.ip,
+      "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.0.0.0/29", "192.0.0.8/32",
+      "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24", "192.31.196.0/24",
+      "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10", "192.175.48.0/24",
+      "198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10", "FF00::/8")]
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
diff --git a/docs/detections/prebuilt-rules/rule-details/network-level-authentication-nla-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-level-authentication-nla-disabled.asciidoc
new file mode 100644
index 0000000000..57bc6915bd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/network-level-authentication-nla-disabled.asciidoc
@@ -0,0 +1,71 @@
+[[network-level-authentication-nla-disabled]]
+=== Network-Level Authentication (NLA) Disabled
+
+Identifies the attempt to disable Network-Level Authentication (NLA) via registry modification. Network Level Authentication (NLA) is a feature on Windows that provides an extra layer of security for Remote Desktop (RDP) connections, as it requires users to authenticate before allowing a full RDP session. Attackers can disable NLA to enable persistence methods that require access to the Windows sign-in screen without authenticating, such as Accessibility Features persistence methods, like Sticky Keys.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.registry-*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.microsoft.com/en-us/security/blog/2023/08/24/flax-typhoon-using-legitimate-software-to-quietly-access-taiwanese-organizations/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+registry where host.os.type == "windows" and event.action != "deletion" and
+  registry.path :
+       ("HKLM\\SYSTEM\\ControlSet*\\Control\\Terminal Server\\WinStations\\RDP-Tcp\\UserAuthentication", 
+        "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Control\\Terminal Server\\WinStations\\RDP-Tcp\\UserAuthentication" ) and
+  registry.data.strings : "0"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
diff --git a/docs/detections/prebuilt-rules/rule-details/network-logon-provider-registry-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-logon-provider-registry-modification.asciidoc
index 8ae3cd7895..49dfe62730 100644
--- a/docs/detections/prebuilt-rules/rule-details/network-logon-provider-registry-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/network-logon-provider-registry-modification.asciidoc
@@ -5,67 +5,141 @@ Identifies the modification of the network logon provider registry. Adversaries
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
 * endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/gtworek/PSBits/tree/master/PasswordStealing/NPPSpy
 * https://docs.microsoft.com/en-us/windows/win32/api/npapi/nf-npapi-nplogonnotify
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 109
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Credential Access
-* Elastic Endgame
 
-*Version*: 101 (<<network-logon-provider-registry-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.13.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
+
+
+
+*Investigating Network Logon Provider Registry Modification*
+
+
+Network logon providers are components in Windows responsible for handling the authentication process during a network logon.
+
+This rule identifies the modification of the network logon provider registry. Adversaries may register a rogue network logon provider module for persistence and/or credential access via intercepting the authentication credentials in plain text during user logon.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Examine the `registry.data.strings` field to identify the DLL registered.
+- Identify the process responsible for the registry operation and the file creation and investigate their process execution chains (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+  - Investigate any abnormal behavior by the subject process, such as network connections, DLLs loaded, registry or file modifications, and any spawned child processes.
+- Retrieve the file and examine if it is signed with valid digital signatures from vendors that are supposed to implement this kind of software and approved to use in the environment. Check for prevalence in the environment and whether they are located in expected locations.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the executables of the processes using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+
+*False positive analysis*
+
+
+- False Positives can include legitimate software installations or updates that modify the network logon provider registry. These modifications may be necessary for the proper functioning of the software and are not indicative of malicious activity.
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+  - If malicious activity is confirmed, perform a broader investigation to identify the scope of the compromise and determine the appropriate remediation steps.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Reimage the host operating system or restore the compromised files to clean versions.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Authorized third party network logon providers.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.data.strings != null and registry.path : (
-"HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\NetworkProvider\\ProviderPat
-h", "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\*\\Netwo
-rkProvider\\ProviderPath" ) and /* Excluding default
-NetworkProviders RDPNP, LanmanWorkstation and webclient. */ not (
-user.id : "S-1-5-18" and registry.data.strings in
-("%SystemRoot%\\System32\\ntlanman.dll",
-"%SystemRoot%\\System32\\drprov.dll",
-"%SystemRoot%\\System32\\davclnt.dll") )
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and registry.data.strings : "?*" and
+  registry.path : (
+    "HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\NetworkProvider\\ProviderPath",
+    "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\*\\NetworkProvider\\ProviderPath"
+  ) and
+  /* Excluding default NetworkProviders RDPNP, LanmanWorkstation and webclient. */
+  not (
+    user.id : "S-1-5-18" and
+    registry.data.strings : (
+        "%SystemRoot%\\System32\\ntlanman.dll",
+        "%SystemRoot%\\System32\\drprov.dll",
+        "%SystemRoot%\\System32\\davclnt.dll",
+        "%SystemRoot%\\System32\\vmhgfs.dll",
+        "?:\\Program Files (x86)\\Citrix\\ICA Client\\x64\\pnsson.dll",
+        "?:\\Program Files\\Dell\\SARemediation\\agent\\DellMgmtNP.dll",
+        "?:\\Program Files (x86)\\CheckPoint\\Endpoint Connect\\\\epcgina.dll"
+    )
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,8 +151,6 @@ user.id : "S-1-5-18" and registry.data.strings in
 ** Name: Modify Authentication Process
 ** ID: T1556
 ** Reference URL: https://attack.mitre.org/techniques/T1556/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -87,34 +159,3 @@ user.id : "S-1-5-18" and registry.data.strings in
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[network-logon-provider-registry-modification-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.data.strings != null and registry.path : "HKL
-M\\SYSTEM\\*ControlSet*\\Services\\*\\NetworkProvider\\ProviderPath"
-and /* Excluding default NetworkProviders RDPNP, LanmanWorkstation
-and webclient. */ not ( user.id : "S-1-5-18" and
-registry.data.strings in
-("%SystemRoot%\\System32\\ntlanman.dll",
-"%SystemRoot%\\System32\\drprov.dll",
-"%SystemRoot%\\System32\\davclnt.dll") )
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/network-traffic-capture-via-cap-net-raw.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-traffic-capture-via-cap-net-raw.asciidoc
new file mode 100644
index 0000000000..5bc3ca8590
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/network-traffic-capture-via-cap-net-raw.asciidoc
@@ -0,0 +1,99 @@
+[[network-traffic-capture-via-cap-net-raw]]
+=== Network Traffic Capture via CAP_NET_RAW
+
+Identifies the ability of a process to be able to create RAW and PACKET socket types for the available network namespaces by a non-root user. A malicious process with this capability may exploit routing between hosts, bypass network access controls, and otherwise tamper with host networking if a firewall is not in place to limit the packet types and contents. The CAP_NET_RAW capability allows the process to bind to any address within the available namespaces, which allows network traffic sniffing by a non root user. The rule identifies previously unknown processes executing with CAP_NET_RAW capabilities through the use of the new terms rule type.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:"process" and host.os.type:"linux" and event.type:"start" and event.action:"exec" and process.name:* and
+(process.thread.capabilities.effective:"CAP_NET_RAW" or process.thread.capabilities.permitted:"CAP_NET_RAW") and
+not user.id:"0"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Network Sniffing
+** ID: T1040
+** Reference URL: https://attack.mitre.org/techniques/T1040/
diff --git a/docs/detections/prebuilt-rules/rule-details/network-traffic-to-rare-destination-country.asciidoc b/docs/detections/prebuilt-rules/rule-details/network-traffic-to-rare-destination-country.asciidoc
index 091519e77a..6714e07213 100644
--- a/docs/detections/prebuilt-rules/rule-details/network-traffic-to-rare-destination-country.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/network-traffic-to-rare-destination-country.asciidoc
@@ -5,52 +5,33 @@ A machine learning job detected a rare destination country name in the network l
 
 *Rule type*: machine_learning
 
-*Machine learning job*: rare_destination_country
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Network
-* Threat Detection
-* ML
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
 
-*Version*: 100 (<<network-traffic-to-rare-destination-country-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.13.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Business workflows that occur very occasionally, and involve a business relationship with an organization in a country that does not routinely appear in network events, can trigger this alert. A new business workflow with an organization in a country with which no workflows previously existed may trigger this alert - although the model will learn that the new destination country is no longer anomalous as the activity becomes ongoing. Business travelers who roam to many countries for brief periods may trigger this alert.
-
-[[network-traffic-to-rare-destination-country-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (7.14.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/new-activesyncalloweddeviceid-added-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/new-activesyncalloweddeviceid-added-via-powershell.asciidoc
index 5761fb7c54..87ce6af264 100644
--- a/docs/detections/prebuilt-rules/rule-details/new-activesyncalloweddeviceid-added-via-powershell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/new-activesyncalloweddeviceid-added-via-powershell.asciidoc
@@ -5,69 +5,71 @@ Identifies the use of the Exchange PowerShell cmdlet, Set-CASMailbox, to add a n
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.volexity.com/blog/2020/12/14/dark-halo-leverages-solarwinds-compromise-to-breach-organizations/
 * https://docs.microsoft.com/en-us/powershell/module/exchange/set-casmailbox?view=exchange-ps
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 101 (<<new-activesyncalloweddeviceid-added-via-powershell-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Legitimate exchange system administration activity.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name:
-("powershell.exe", "pwsh.exe", "powershell_ise.exe") and process.args
-: "Set-CASMailbox*ActiveSyncAllowedDeviceIDs*"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name: ("powershell.exe", "pwsh.exe", "powershell_ise.exe") and process.args : "Set-CASMailbox*ActiveSyncAllowedDeviceIDs*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,42 +81,19 @@ process where event.type == "start" and process.name:
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[new-activesyncalloweddeviceid-added-via-powershell-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name: ("powershell.exe", "pwsh.exe", "powershell_ise.exe") and
-process.args : "Set-CASMailbox*ActiveSyncAllowedDeviceIDs*"
-----------------------------------
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name: ("powershell.exe", "pwsh.exe") and process.args : "Set-
-CASMailbox*ActiveSyncAllowedDeviceIDs*"
-----------------------------------
-
-Version 4 (7.15.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Additional Email Delegate Permissions
+** ID: T1098.002
+** Reference URL: https://attack.mitre.org/techniques/T1098/002/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/new-github-app-installed.asciidoc b/docs/detections/prebuilt-rules/rule-details/new-github-app-installed.asciidoc
new file mode 100644
index 0000000000..442a18c87e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/new-github-app-installed.asciidoc
@@ -0,0 +1,58 @@
+[[new-github-app-installed]]
+=== New GitHub App Installed
+
+This rule detects when a new GitHub App has been installed in your organization account. GitHub Apps extend GitHub's functionality both within and outside of GitHub. When an app is installed it is granted permissions to read or modify your repository and organization data. Only trusted apps should be installed and any newly installed apps should be investigated to verify their legitimacy. Unauthorized app installation could lower your organization's security posture and leave you exposed for future attacks.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+configuration where event.dataset == "github.audit" and event.action == "integration_installation.create"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Software Deployment Tools
+** ID: T1072
+** Reference URL: https://attack.mitre.org/techniques/T1072/
diff --git a/docs/detections/prebuilt-rules/rule-details/new-github-owner-added.asciidoc b/docs/detections/prebuilt-rules/rule-details/new-github-owner-added.asciidoc
new file mode 100644
index 0000000000..b7af907460
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/new-github-owner-added.asciidoc
@@ -0,0 +1,63 @@
+[[new-github-owner-added]]
+=== New GitHub Owner Added
+
+Detects when a new member is added to a GitHub organization as an owner. This role provides admin level privileges. Any new owner roles should be investigated to determine it's validity. Unauthorized owner roles could indicate compromise within your organization and provide unlimited access to data and settings.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Persistence
+* Data Source: Github
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+iam where event.dataset == "github.audit" and event.action == "org.add_member" and github.permission == "admin"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create Account
+** ID: T1136
+** Reference URL: https://attack.mitre.org/techniques/T1136/
+* Sub-technique:
+** Name: Cloud Account
+** ID: T1136.003
+** Reference URL: https://attack.mitre.org/techniques/T1136/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/new-okta-authentication-behavior-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/new-okta-authentication-behavior-detected.asciidoc
new file mode 100644
index 0000000000..bb08cd8dfb
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/new-okta-authentication-behavior-detected.asciidoc
@@ -0,0 +1,104 @@
+[[new-okta-authentication-behavior-detected]]
+=== New Okta Authentication Behavior Detected
+
+Detects events where Okta behavior detection has identified a new authentication behavior.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 15m
+
+*Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+* https://unit42.paloaltonetworks.com/muddled-libra/
+* https://help.okta.com/oie/en-us/content/topics/security/behavior-detection/about-behavior-detection.htm
+
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Tactic: Initial Access
+* Data Source: Okta
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating New Okta Authentication Behavior Detected*
+
+
+This rule detects events where Okta behavior detection has identified a new authentication behavior such as a new device or location.
+
+
+*Possible investigation steps:*
+
+- Identify the user involved in this action by examining the `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, and `okta.actor.display_name` fields.
+- Determine the authentication anomaly by examining the `okta.debug_context.debug_data.risk_behaviors` and `okta.debug_context.debug_data.flattened` fields.
+- Determine the client used by the actor. Review the `okta.client.ip`, `okta.client.user_agent.raw_user_agent`, `okta.client.zone`, `okta.client.device`, and `okta.client.id` fields.
+- If the client is a device, check the `okta.device.id`, `okta.device.name`, `okta.device.os_platform`, `okta.device.os_version`, and `okta.device.managed` fields.
+- Review the past activities of the actor involved in this action by checking their previous actions.
+- Examine the `okta.request.ip_chain` field to potentially determine if the actor used a proxy or VPN to perform this action.
+- Evaluate the actions that happened just before and after this event in the `okta.event_type` field to help understand the full context of the activity.
+
+
+*False positive analysis:*
+
+- A user may be using a new device or location to sign in.
+- The Okta behavior detection may be incorrectly identifying a new authentication behavior and need adjusted.
+
+
+*Response and remediation:*
+
+- If the user is legitimate and the authentication behavior is not suspicious, no action is required.
+- If the user is legitimate but the authentication behavior is suspicious, consider resetting the user's password and enabling multi-factor authentication (MFA).
+    - If MFA is already enabled, consider resetting MFA for the user.
+- If the user is not legitimate, consider deactivating the user's account.
+- If this is a false positive, consider adjusting the Okta behavior detection settings.
+- Block the IP address or device used in the attempts if they appear suspicious, using the data from the `okta.client.ip` and `okta.device.id` fields.
+- Conduct a review of Okta policies and ensure they are in accordance with security best practices.
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:okta.system and okta.debug_context.debug_data.risk_behaviors:*
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
diff --git a/docs/detections/prebuilt-rules/rule-details/new-okta-identity-provider-idp-added-by-admin.asciidoc b/docs/detections/prebuilt-rules/rule-details/new-okta-identity-provider-idp-added-by-admin.asciidoc
new file mode 100644
index 0000000000..c668422ea2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/new-okta-identity-provider-idp-added-by-admin.asciidoc
@@ -0,0 +1,114 @@
+[[new-okta-identity-provider-idp-added-by-admin]]
+=== New Okta Identity Provider (IdP) Added by Admin
+
+Detects the creation of a new Identity Provider (IdP) by a Super Administrator or Organization Administrator within Okta.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 15m
+
+*Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.cloudflare.com/cloudflare-investigation-of-the-january-2022-okta-compromise/
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+* https://unit42.paloaltonetworks.com/muddled-libra/
+
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Tactic: Persistence
+* Data Source: Okta
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating New Okta Identity Provider (IdP) Added by Admin*
+
+
+This rule detects the creation of a new Identity Provider (IdP) by a Super Administrator or Organization Administrator within Okta.
+
+
+*Possible investigation steps:*
+
+- Identify the actor associated with the IdP creation by examining the `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, and `okta.actor.display_name` fields.
+- Identify the IdP added by reviewing the `okta.target` field and determing if this IdP is authorized.
+- Determine the client used by the actor. Review the `okta.client.ip`, `okta.client.user_agent.raw_user_agent`, `okta.client.zone`, `okta.client.device`, and `okta.client.id` fields.
+- If the client is a device, check the `okta.device.id`, `okta.device.name`, `okta.device.os_platform`, `okta.device.os_version`, and `okta.device.managed` fields.
+- Review the past activities of the actor involved in this action by checking their previous actions logged in the `okta.target` field.
+- Examine the `okta.request.ip_chain` field to potentially determine if the actor used a proxy or VPN to perform this action.
+- Evaluate the actions that happened just before and after this event in the `okta.event_type` field to help understand the full context of the activity.
+
+
+*False positive analysis:*
+
+- It might be a false positive if the action was part of a planned activity or performed by an authorized person.
+- Several unsuccessful attempts prior to this success, may indicate an adversary attempting to add an unauthorized IdP multiple times.
+
+
+*Response and remediation:*
+
+- If the IdP is unauthorized, deactivate it immediately via the Okta console.
+- If the IdP is authorized, ensure that the actor who created it is authorized to do so.
+- If the actor is unauthorized, deactivate their account via the Okta console.
+- If the actor is authorized, ensure that the actor's account is not compromised.
+- Reset the user's password and enforce MFA re-enrollment, if applicable.
+- Block the IP address or device used in the attempts if they appear suspicious, using the data from the `okta.client.ip` and `okta.device.id` fields.
+- Conduct a review of Okta policies and ensure they are in accordance with security best practices.
+- If the deactivated IdP was crucial to the organization, consider adding a new IdP and removing the unauthorized IdP.
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset: "okta.system" and event.action: "system.idp.lifecycle.create" and okta.outcome.result: "SUCCESS"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Modify Authentication Process
+** ID: T1556
+** Reference URL: https://attack.mitre.org/techniques/T1556/
+* Sub-technique:
+** Name: Hybrid Identity
+** ID: T1556.007
+** Reference URL: https://attack.mitre.org/techniques/T1556/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/new-or-modified-federation-domain.asciidoc b/docs/detections/prebuilt-rules/rule-details/new-or-modified-federation-domain.asciidoc
index 8874ff8d55..94d820b51a 100644
--- a/docs/detections/prebuilt-rules/rule-details/new-or-modified-federation-domain.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/new-or-modified-federation-domain.asciidoc
@@ -5,7 +5,7 @@ Identifies a new or modified federation domain, which can be used to create a tr
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,13 +14,13 @@ Identifies a new or modified federation domain, which can be used to create a tr
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/exchange/remove-accepteddomain?view=exchange-ps
 * https://docs.microsoft.com/en-us/powershell/module/exchange/remove-federateddomain?view=exchange-ps
@@ -29,47 +29,42 @@ Identifies a new or modified federation domain, which can be used to create a tr
 * https://docs.microsoft.com/en-us/powershell/module/exchange/set-accepteddomain?view=exchange-ps
 * https://docs.microsoft.com/en-us/powershell/module/msonline/set-msoldomainfederationsettings?view=azureadps-1.0
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Identity and Access
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Identity and Access Audit
+* Tactic: Privilege Escalation
 
-*Version*: 101 (<<new-or-modified-federation-domain-history, version history>>)
+*Version*: 206
 
-*Added ({stack} release)*: 7.16.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:("Set-AcceptedDomain" or "Set-
-MsolDomainFederationSettings" or "Add-FederatedDomain" or "New-
-AcceptedDomain" or "Remove-AcceptedDomain" or "Remove-
-FederatedDomain") and event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:("Set-AcceptedDomain" or
+"Set-MsolDomainFederationSettings" or "Add-FederatedDomain" or "New-AcceptedDomain" or "Remove-AcceptedDomain" or "Remove-FederatedDomain") and
+event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,28 +76,7 @@ FederatedDomain") and event.outcome:success
 ** Name: Domain Policy Modification
 ** ID: T1484
 ** Reference URL: https://attack.mitre.org/techniques/T1484/
-
-[[new-or-modified-federation-domain-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.category:web and event.action:("Set-AcceptedDomain" or "Set-
-MsolDomainFederationSettings" or "Add-FederatedDomain" or "New-
-AcceptedDomain" or "Remove-AcceptedDomain" or "Remove-
-FederatedDomain") and event.outcome:success
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Domain Trust Modification
+** ID: T1484.002
+** Reference URL: https://attack.mitre.org/techniques/T1484/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/new-systemd-service-created-by-previously-unknown-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/new-systemd-service-created-by-previously-unknown-process.asciidoc
new file mode 100644
index 0000000000..56c9a3ff10
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/new-systemd-service-created-by-previously-unknown-process.asciidoc
@@ -0,0 +1,220 @@
+[[new-systemd-service-created-by-previously-unknown-process]]
+=== New Systemd Service Created by Previously Unknown Process
+
+Systemd service files are configuration files in Linux systems used to define and manage system services. Malicious actors can leverage systemd service files to achieve persistence by creating or modifying service files to execute malicious commands or payloads during system startup. This allows them to maintain unauthorized access, execute additional malicious activities, or evade detection.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://opensource.com/article/20/7/systemd-timers
+* https://pberba.github.io/security/2022/01/30/linux-threat-hunting-for-persistence-systemd-timers-cron/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 9
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating New Systemd Service Created by Previously Unknown Process*
+
+
+Systemd service files are configuration files in Linux systems used to define and manage system services.
+
+Malicious actors can leverage systemd service files to achieve persistence by creating or modifying service files to execute malicious commands or payloads during system startup. This allows them to maintain unauthorized access, execute additional malicious activities, or evade detection.
+
+This rule monitors the creation of new systemd service files, potentially indicating the creation of a persistence mechanism.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible Investigation Steps*
+
+
+- Investigate the systemd service file that was created or modified.
+  - !{osquery{"label":"Osquery - Retrieve File Information","query":"SELECT * FROM file WHERE path = {{file.path}}"}}
+- Investigate the currently enabled systemd services through the following command `sudo systemctl list-unit-files`.
+- Investigate whether any other files in any of the available systemd directories have been altered through OSQuery.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE (\npath LIKE '/etc/systemd/system/%' OR \npath LIKE '/usr/local/lib/systemd/system/%' OR \npath LIKE '/lib/systemd/system/%' OR\npath LIKE '/usr/lib/systemd/system/%' OR\npath LIKE '/home/user/.config/systemd/user/%'\n)\n"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE (\npath LIKE '/etc/systemd/system/%' OR \npath LIKE '/usr/local/lib/systemd/system/%' OR \npath LIKE '/lib/systemd/system/%' OR\npath LIKE '/usr/lib/systemd/system/%' OR\npath LIKE '/home/{{user.name}}/.config/systemd/user/%'\n)\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+    - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+    - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+
+
+*False Positive Analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator who uses systemd services for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Related Rules*
+
+
+- Potential Persistence Through Run Control Detected - 0f4d35e4-925e-4959-ab24-911be207ee6f
+- Potential Persistence Through init.d Detected - 474fd20e-14cc-49c5-8160-d9ab4ba16c8b
+- New Systemd Timer Created - 7fb500fa-8e24-4bd1-9480-2a819352602c
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Delete the service/timer or restore its original configuration.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.category:file and event.action:("creation" or "file_create_event") and file.path:(
+  /etc/systemd/system/* or 
+  /usr/local/lib/systemd/system/* or 
+  /lib/systemd/system/* or 
+  /usr/lib/systemd/system/* or 
+  /home/*/.config/systemd/user/*
+) and 
+not (
+  process.name:(
+    "dpkg" or "dockerd" or "rpm" or "snapd" or "yum" or "exe" or "dnf" or "dnf-automatic" or python* or "puppetd" or
+    "elastic-agent" or "cinc-client" or "chef-client" or "pacman" or "puppet" or "cloudflared" or "packagekitd" or
+    "podman"
+  ) or 
+  file.extension:("swp" or "swpx")
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Systemd Service
+** ID: T1543.002
+** Reference URL: https://attack.mitre.org/techniques/T1543/002/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Systemd Service
+** ID: T1543.002
+** Reference URL: https://attack.mitre.org/techniques/T1543/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/new-systemd-timer-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/new-systemd-timer-created.asciidoc
new file mode 100644
index 0000000000..b1dcab6ef3
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/new-systemd-timer-created.asciidoc
@@ -0,0 +1,187 @@
+[[new-systemd-timer-created]]
+=== New Systemd Timer Created
+
+Detects the creation of a systemd timer within any of the default systemd timer directories. Systemd timers can be used by an attacker to gain persistence, by scheduling the execution of a command or script. Similarly to cron/at, systemd timers can be set up to execute on boot time, or on a specific point in time, which allows attackers to regain access in case the connection to the infected asset was lost.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://opensource.com/article/20/7/systemd-timers
+* https://pberba.github.io/security/2022/01/30/linux-threat-hunting-for-persistence-systemd-timers-cron/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 9
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating New Systemd Timer Created*
+
+
+Systemd timers are used for scheduling and automating recurring tasks or services on Linux systems. 
+
+Attackers can leverage systemd timers to run scripts, commands, or malicious software at system boot or on a set time interval by creating a systemd timer and a corresponding systemd service file. 
+
+This rule monitors the creation of new systemd timer files, potentially indicating the creation of a persistence mechanism.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible Investigation Steps*
+
+
+- Investigate the timer file that was created or modified.
+  - !{osquery{"label":"Osquery - Retrieve File Information","query":"SELECT * FROM file WHERE path = {{file.path}}"}}
+- Investigate the currently enabled systemd timers through the following command `sudo systemctl list-timers`.
+- Search for the systemd service file named similarly to the timer that was created.
+- Investigate whether any other files in any of the available systemd directories have been altered through OSQuery.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE (\npath LIKE '/etc/systemd/system/%' OR \npath LIKE '/usr/local/lib/systemd/system/%' OR \npath LIKE '/lib/systemd/system/%' OR\npath LIKE '/usr/lib/systemd/system/%' OR\npath LIKE '/home/user/.config/systemd/user/%'\n)\n"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE (\npath LIKE '/etc/systemd/system/%' OR \npath LIKE '/usr/local/lib/systemd/system/%' OR \npath LIKE '/lib/systemd/system/%' OR\npath LIKE '/usr/lib/systemd/system/%' OR\npath LIKE '/home/{{user.name}}/.config/systemd/user/%'\n)\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+
+
+*False Positive Analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator who uses systemd timers for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Delete the service/timer or restore its original configuration.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type : "linux" and event.action : ("creation" or "file_create_event") and file.extension : "timer" and
+file.path : (/etc/systemd/system/* or /usr/local/lib/systemd/system/* or /lib/systemd/system/* or 
+/usr/lib/systemd/system/* or /home/*/.config/systemd/user/*) and not (
+  (process.name : (
+    "docker" or "dockerd" or "dnf" or "yum" or "rpm" or "dpkg" or "executor" or "cloudflared" or "pacman" or "podman" or 
+    "pamac-daemon"
+  ))
+  or (file.name:apt-*.timer)
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: Systemd Timers
+** ID: T1053.006
+** Reference URL: https://attack.mitre.org/techniques/T1053/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/new-user-added-to-github-organization.asciidoc b/docs/detections/prebuilt-rules/rule-details/new-user-added-to-github-organization.asciidoc
new file mode 100644
index 0000000000..93107fff00
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/new-user-added-to-github-organization.asciidoc
@@ -0,0 +1,64 @@
+[[new-user-added-to-github-organization]]
+=== New User Added To GitHub Organization
+
+A new user was added to a GitHub organization.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-github.audit-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Cloud
+* Use Case: Threat Detection
+* Use Case: UEBA
+* Tactic: Persistence
+* Rule Type: BBR
+* Data Source: Github
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+configuration where event.dataset == "github.audit" and event.action == "org.add_member"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Account Manipulation
+** ID: T1098
+** Reference URL: https://attack.mitre.org/techniques/T1098/
+* Sub-technique:
+** Name: Additional Cloud Credentials
+** ID: T1098.001
+** Reference URL: https://attack.mitre.org/techniques/T1098/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/nping-process-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/nping-process-activity.asciidoc
index 1fe1683ffd..f486800ec3 100644
--- a/docs/detections/prebuilt-rules/rule-details/nping-process-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/nping-process-activity.asciidoc
@@ -3,105 +3,118 @@
 
 Nping ran on a Linux host. Nping is part of the Nmap tool suite and has the ability to construct raw packets for a wide variety of security testing applications, including denial of service testing.
 
-*Rule type*: query
+*Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://en.wikipedia.org/wiki/Nmap
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Discovery
 
-*Version*: 100 (<<nping-process-activity-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.6.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
 
-Some normal use of this command may originate from security engineers and network or server administrators, but this is usually not routine or unannounced. Use of `Nping` by non-engineers or ordinary users is uncommon.
 
-==== Rule query
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:nping
-----------------------------------
+*Elastic Defend Integration Setup*
 
-==== Threat mapping
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Discovery
-** ID: TA0007
-** Reference URL: https://attack.mitre.org/tactics/TA0007/
-* Technique:
-** Name: Network Service Discovery
-** ID: T1046
-** Reference URL: https://attack.mitre.org/techniques/T1046/
+*Prerequisite Requirements:*
 
-[[nping-process-activity-history]]
-==== Rule version history
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 9 (8.4.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
 
-Version 7 (7.12.0 release)::
-* Formatting only
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Version 6 (7.11.2 release)::
-* Formatting only
 
-Version 5 (7.10.0 release)::
-* Formatting only
+*Auditbeat Setup*
 
-Version 4 (7.9.1 release)::
-* Formatting only
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
 
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:nping and event.action:executed
-----------------------------------
 
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-process.name: nping and event.action:executed
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "nping"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Network Service Discovery
+** ID: T1046
+** Reference URL: https://attack.mitre.org/techniques/T1046/
diff --git a/docs/detections/prebuilt-rules/rule-details/ntds-or-sam-database-file-copied.asciidoc b/docs/detections/prebuilt-rules/rule-details/ntds-or-sam-database-file-copied.asciidoc
index 97535857c7..46d7fd7bc0 100644
--- a/docs/detections/prebuilt-rules/rule-details/ntds-or-sam-database-file-copied.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/ntds-or-sam-database-file-copied.asciidoc
@@ -5,131 +5,164 @@ Identifies a copy operation of the Active Directory Domain Database (ntds.dit) o
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 33
 
-*References*:
+*References*: 
 
 * https://thedfirreport.com/2020/11/23/pysa-mespinoza-ransomware/
 * https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1003.002/T1003.002.md#atomic-test-3---esentutlexe-sam-copy
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Elastic Endgame
-
-*Version*: 102 (<<ntds-or-sam-database-file-copied-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating NTDS or SAM Database File Copied*
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (
-(process.pe.original_file_name in ("Cmd.Exe", "PowerShell.EXE",
-"XCOPY.EXE") and process.args : ("copy", "xcopy", "Copy-Item",
-"move", "cp", "mv") ) or (process.pe.original_file_name :
-"esentutl.exe" and process.args : ("*/y*", "*/vss*", "*/d*")) ) and
-process.args : ("*\\ntds.dit", "*\\config\\SAM",
-"\\*\\GLOBALROOT\\Device\\HarddiskVolumeShadowCopy*\\*",
-"*/system32/config/SAM*")
-----------------------------------
 
-==== Threat mapping
+The Active Directory Domain Database (ntds.dit) and Security Account Manager (SAM) files are critical components in Windows environments, containing sensitive information such as hashed domain and local credentials.
 
-*Framework*: MITRE ATT&CK^TM^
+This rule identifies copy operations of these files using specific command-line tools, such as Cmd.Exe, PowerShell.EXE, XCOPY.EXE, and esentutl.exe. By monitoring for the presence of these tools and their associated arguments, the rule aims to detect potential credential access activities.
 
-* Tactic:
-** Name: Credential Access
-** ID: TA0006
-** Reference URL: https://attack.mitre.org/tactics/TA0006/
-* Technique:
-** Name: OS Credential Dumping
-** ID: T1003
-** Reference URL: https://attack.mitre.org/techniques/T1003/
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-[[ntds-or-sam-database-file-copied-history]]
-==== Rule version history
 
-Version 102 (8.6.0 release)::
-* Formatting only
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, command lines, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Check for any recent changes in user account privileges or group memberships that may have allowed the unauthorized access.
+- Determine whether the file was potentially exfiltrated from the subject host.
+- Scope compromised credentials and disable the accounts.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Look for the presence of relevant artifacts on other systems. Identify commonalities and differences between potentially compromised systems.
+
+
+*False positive analysis*
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and (
-(process.pe.original_file_name in ("Cmd.Exe", "PowerShell.EXE",
-"XCOPY.EXE") and process.args : ("copy", "xcopy", "Copy-Item",
-"move", "cp", "mv") ) or (process.pe.original_file_name :
-"esentutl.exe" and process.args : ("*/y*", "*/vss*", "*/d*")) ) and
-process.args : ("*\\ntds.dit", "*\\config\\SAM",
-"\\*\\GLOBALROOT\\Device\\HarddiskVolumeShadowCopy*\\*",
-"*/system32/config/SAM*")
-----------------------------------
 
-Version 8 (8.4.0 release)::
-* Formatting only
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-Version 6 (8.2.0 release)::
-* Formatting only
 
-Version 5 (7.16.0 release)::
-* Formatting only
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+  - If malicious activity is confirmed, perform a broader investigation to identify the scope of the compromise and determine the appropriate remediation steps.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Restore the affected system to its operational state by applying any necessary patches, updates, or configuration changes.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
 
-Version 4 (7.15.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-process where event.type in ("start", "process_started") and
-process.pe.original_file_name in ("Cmd.Exe", "PowerShell.EXE",
-"XCOPY.EXE") and process.args : ("copy", "xcopy", "Copy-Item",
-"move", "cp", "mv") and process.args : ("*\\ntds.dit",
-"*\\config\\SAM",
-"\\*\\GLOBALROOT\\Device\\HarddiskVolumeShadowCopy*\\*")
-----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (
+    ((?process.pe.original_file_name in ("Cmd.Exe", "PowerShell.EXE", "XCOPY.EXE") or process.name : ("Cmd.Exe", "PowerShell.EXE", "XCOPY.EXE")) and
+       process.args : ("copy", "xcopy", "Copy-Item", "move", "cp", "mv")
+    ) or
+    ((?process.pe.original_file_name : "esentutl.exe" or process.name : "esentutl.exe") and process.args : ("*/y*", "*/vss*", "*/d*"))
+  ) and
+  process.command_line : ("*\\ntds.dit*", "*\\config\\SAM*", "*\\*\\GLOBALROOT\\Device\\HarddiskVolumeShadowCopy*\\*", "*/system32/config/SAM*", "*\\User Data\\*")
 
-Version 3 (7.12.0 release)::
-* Formatting only
+----------------------------------
 
-Version 2 (7.11.2 release)::
-* Formatting only
+*Framework*: MITRE ATT&CK^TM^
 
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: Security Account Manager
+** ID: T1003.002
+** Reference URL: https://attack.mitre.org/techniques/T1003/002/
+* Sub-technique:
+** Name: NTDS
+** ID: T1003.003
+** Reference URL: https://attack.mitre.org/techniques/T1003/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/nullsessionpipe-registry-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/nullsessionpipe-registry-modification.asciidoc
index 39c5322711..102b3dcbfd 100644
--- a/docs/detections/prebuilt-rules/rule-details/nullsessionpipe-registry-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/nullsessionpipe-registry-modification.asciidoc
@@ -5,54 +5,59 @@ Identifies NullSessionPipe registry modifications that specify which pipes can b
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.welivesecurity.com/2019/05/29/turla-powershell-usage/
 * https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-access-restrict-anonymous-access-to-named-pipes-and-shares
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-
-*Version*: 101 (<<nullsessionpipe-registry-modification-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.13.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type in ("creation", "change") and registry.path
-: "HKLM\\SYSTEM\\*ControlSet*\\services\\LanmanServer\\Parameters\\Nul
-lSessionPipes" and length(registry.data.strings) > 0
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type in ("creation", "change") and
+registry.path : (
+    "HKLM\\SYSTEM\\*ControlSet*\\services\\LanmanServer\\Parameters\\NullSessionPipes",
+    "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\services\\LanmanServer\\Parameters\\NullSessionPipes"
+) and length(registry.data.strings) > 0
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,26 +69,15 @@ lSessionPipes" and length(registry.data.strings) > 0
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[nullsessionpipe-registry-modification-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path : "HKLM\\SYSTEM\\*ControlSet*\\services\\
-LanmanServer\\Parameters\\NullSessionPipes" and registry.data.strings
-!= null
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/o365-email-reported-by-user-as-malware-or-phish.asciidoc b/docs/detections/prebuilt-rules/rule-details/o365-email-reported-by-user-as-malware-or-phish.asciidoc
index 9b141d1b34..7f603cf00f 100644
--- a/docs/detections/prebuilt-rules/rule-details/o365-email-reported-by-user-as-malware-or-phish.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/o365-email-reported-by-user-as-malware-or-phish.asciidoc
@@ -5,7 +5,7 @@ Detects the occurrence of emails reported as Phishing or Malware by Users. Secur
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,59 +14,49 @@ Detects the occurrence of emails reported as Phishing or Malware by Users. Secur
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.microsoft.com/en-us/office/use-the-report-message-add-in-b5caa9f1-cdf3-4443-af8c-ff724ea719d2?ui=en-us&rs=en-us&ad=us
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Initial Access
-
-*Version*: 101 (<<o365-email-reported-by-user-as-malware-or-phish-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Legitimate files reported by the users
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:SecurityComplianceCenter
-and event.action:AlertTriggered and rule.name:"Email reported by user
-as malware or phish"
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:SecurityComplianceCenter and event.action:AlertTriggered and rule.name:"Email reported by user as malware or phish"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,16 +68,11 @@ as malware or phish"
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[o365-email-reported-by-user-as-malware-or-phish-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/o365-excessive-single-sign-on-logon-errors.asciidoc b/docs/detections/prebuilt-rules/rule-details/o365-excessive-single-sign-on-logon-errors.asciidoc
index 6df1447d85..4d47248876 100644
--- a/docs/detections/prebuilt-rules/rule-details/o365-excessive-single-sign-on-logon-errors.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/o365-excessive-single-sign-on-logon-errors.asciidoc
@@ -5,7 +5,7 @@ Identifies accounts with a high number of single sign-on (SSO) logon errors. Exc
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,55 +14,49 @@ Identifies accounts with a high number of single sign-on (SSO) logon errors. Exc
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-20m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Identity and Access
+*Tags*: 
 
-*Version*: 101 (<<o365-excessive-single-sign-on-logon-errors-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Automated processes that attempt to authenticate using expired credentials and unbounded retries may lead to false positives.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:AzureActiveDirectory and
-event.category:authentication and
-o365.audit.LogonError:"SsoArtifactInvalidOrExpired"
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:AzureActiveDirectory and event.category:authentication and o365.audit.LogonError:"SsoArtifactInvalidOrExpired"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,32 +68,3 @@ o365.audit.LogonError:"SsoArtifactInvalidOrExpired"
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
-
-[[o365-excessive-single-sign-on-logon-errors-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.1.0 release)::
-* Formatting only
-
-Version 3 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:AzureActiveDirectory and
-event.category:web and
-o365.audit.LogonError:"SsoArtifactInvalidOrExpired"
-----------------------------------
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/o365-exchange-suspicious-mailbox-right-delegation.asciidoc b/docs/detections/prebuilt-rules/rule-details/o365-exchange-suspicious-mailbox-right-delegation.asciidoc
index 7227e1a302..097753d2e1 100644
--- a/docs/detections/prebuilt-rules/rule-details/o365-exchange-suspicious-mailbox-right-delegation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/o365-exchange-suspicious-mailbox-right-delegation.asciidoc
@@ -5,7 +5,7 @@ Identifies the assignment of rights to access content from another mailbox. An a
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,57 +14,51 @@ Identifies the assignment of rights to access content from another mailbox. An a
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
+*Tags*: 
 
-*Version*: 101 (<<o365-exchange-suspicious-mailbox-right-delegation-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Assignment of rights to a service account.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.action:Add-MailboxPermission and
-o365.audit.Parameters.AccessRights:(FullAccess or SendAs or
-SendOnBehalf) and event.outcome:success and not user.id : "NT
-AUTHORITY\SYSTEM (Microsoft.Exchange.Servicehost)"
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.action:Add-MailboxPermission and
+o365.audit.Parameters.AccessRights:(FullAccess or SendAs or SendOnBehalf) and event.outcome:success and
+not user.id : "NT AUTHORITY\SYSTEM (Microsoft.Exchange.Servicehost)"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,36 +70,7 @@ AUTHORITY\SYSTEM (Microsoft.Exchange.Servicehost)"
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[o365-exchange-suspicious-mailbox-right-delegation-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.action:Add-MailboxPermission and
-o365.audit.Parameters.AccessRights:(FullAccess or SendAs or
-SendOnBehalf) and event.outcome:success and not user.id : "NT
-AUTHORITY\SYSTEM (Microsoft.Exchange.Servicehost)"
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.action:Add-MailboxPermission and
-o365.audit.Parameters.AccessRights:(FullAccess or SendAs or
-SendOnBehalf) and event.outcome:success
-----------------------------------
-
+* Sub-technique:
+** Name: Additional Email Delegate Permissions
+** ID: T1098.002
+** Reference URL: https://attack.mitre.org/techniques/T1098/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/o365-mailbox-audit-logging-bypass.asciidoc b/docs/detections/prebuilt-rules/rule-details/o365-mailbox-audit-logging-bypass.asciidoc
index c6d206b69e..104a1cda96 100644
--- a/docs/detections/prebuilt-rules/rule-details/o365-mailbox-audit-logging-bypass.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/o365-mailbox-audit-logging-bypass.asciidoc
@@ -5,7 +5,7 @@ Detects the occurrence of mailbox audit bypass associations. The mailbox audit i
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,59 +14,50 @@ Detects the occurrence of mailbox audit bypass associations. The mailbox audit i
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://twitter.com/misconfig/status/1476144066807140355
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Initial Access
-
-*Version*: 101 (<<o365-mailbox-audit-logging-bypass-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Tactic: Initial Access
+* Tactic: Defense Evasion
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Legitimate allowlisting of noisy accounts
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:Exchange and
-event.action:Set-MailboxAuditBypassAssociation and
-event.outcome:success
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.action:Set-MailboxAuditBypassAssociation and event.outcome:success
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,19 +69,7 @@ event.outcome:success
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[o365-mailbox-audit-logging-bypass-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/office-test-registry-persistence.asciidoc b/docs/detections/prebuilt-rules/rule-details/office-test-registry-persistence.asciidoc
new file mode 100644
index 0000000000..62364b6e49
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/office-test-registry-persistence.asciidoc
@@ -0,0 +1,75 @@
+[[office-test-registry-persistence]]
+=== Office Test Registry Persistence
+
+Identifies the modification of the Microsoft Office "Office Test" Registry key, a registry location that can be used to specify a DLL which will be executed every time an MS Office application is started. Attackers can abuse this to gain persistence on a compromised host.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.registry-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://unit42.paloaltonetworks.com/unit42-technical-walkthrough-office-test-persistence-method-used-in-recent-sofacy-attacks/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+registry where host.os.type == "windows" and event.action != "deletion" and
+    registry.path : "*\\Software\\Microsoft\\Office Test\\Special\\Perf\\*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Office Application Startup
+** ID: T1137
+** Reference URL: https://attack.mitre.org/techniques/T1137/
+* Sub-technique:
+** Name: Office Test
+** ID: T1137.002
+** Reference URL: https://attack.mitre.org/techniques/T1137/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/okta-brute-force-or-password-spraying-attack.asciidoc b/docs/detections/prebuilt-rules/rule-details/okta-brute-force-or-password-spraying-attack.asciidoc
index cdb53df530..eb1ec3e6e3 100644
--- a/docs/detections/prebuilt-rules/rule-details/okta-brute-force-or-password-spraying-attack.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/okta-brute-force-or-password-spraying-attack.asciidoc
@@ -5,7 +5,7 @@ Identifies a high number of failed Okta user authentication attempts from a sing
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,99 +14,96 @@ Identifies a high number of failed Okta user authentication attempts from a sing
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
+* Data Source: Okta
+
+*Version*: 208
+
+*Rule authors*: 
 
 * Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Identity and Access
 
-*Version*: 102 (<<okta-brute-force-or-password-spraying-attack-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Automated processes that attempt to authenticate using expired credentials and unbounded retries may lead to false positives.
 
-==== Investigation guide
 
+*Investigating Okta Brute Force or Password Spraying Attack*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+This rule alerts when a high number of failed Okta user authentication attempts occur from a single IP address. This could be indicative of a brute force or password spraying attack, where an adversary may attempt to gain unauthorized access to user accounts by guessing the passwords.
 
 
-==== Rule query
+*Possible investigation steps:*
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and event.category:authentication and
-event.outcome:failure
-----------------------------------
+- Review the `source.ip` field to identify the IP address from which the high volume of failed login attempts originated.
+- Look into the `event.outcome` field to verify that these are indeed failed authentication attempts.
+- Determine the `user.name` or `user.email` related to these failed login attempts. If the attempts are spread across multiple accounts, it might indicate a password spraying attack.
+- Check the timeline of the events. Are the failed attempts spread out evenly, or are there burst periods, which might indicate an automated tool?
+- Determine the geographical location of the source IP. Is this location consistent with the user's typical login location?
+- Analyze any previous successful logins from this IP. Was this IP previously associated with successful logins?
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+*False positive analysis:*
 
-* Tactic:
-** Name: Credential Access
-** ID: TA0006
-** Reference URL: https://attack.mitre.org/tactics/TA0006/
-* Technique:
-** Name: Brute Force
-** ID: T1110
-** Reference URL: https://attack.mitre.org/techniques/T1110/
 
-[[okta-brute-force-or-password-spraying-attack-history]]
-==== Rule version history
+- A single user or automated process that attempts to authenticate using expired or wrong credentials multiple times may trigger a false positive.
+- Analyze the behavior of the source IP. If the IP is associated with legitimate users or services, it may be a false positive.
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 100 (8.5.0 release)::
-* Formatting only
+*Response and remediation:*
 
-Version 7 (8.4.0 release)::
-* Formatting only
 
-Version 5 (7.13.0 release)::
-* Formatting only
+- If you identify unauthorized access attempts, consider blocking the source IP at the firewall level.
+- Notify the users who are targeted by the attack. Ask them to change their passwords and ensure they use unique, complex passwords.
+- Enhance monitoring on the affected user accounts for any suspicious activity.
+- If the attack is persistent, consider implementing CAPTCHA or account lockouts after a certain number of failed login attempts.
+- If the attack is persistent, consider implementing multi-factor authentication (MFA) for the affected user accounts.
+- Review and update your security policies based on the findings from the incident.
 
-Version 4 (7.12.0 release)::
-* Formatting only
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
 
-Version 3 (7.11.0 release)::
-* Formatting only
 
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.category:authentication and event.outcome:failure
+event.dataset:okta.system and event.category:authentication and event.outcome:failure
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Brute Force
+** ID: T1110
+** Reference URL: https://attack.mitre.org/techniques/T1110/
diff --git a/docs/detections/prebuilt-rules/rule-details/okta-fastpass-phishing-detection.asciidoc b/docs/detections/prebuilt-rules/rule-details/okta-fastpass-phishing-detection.asciidoc
new file mode 100644
index 0000000000..cf86f556b8
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/okta-fastpass-phishing-detection.asciidoc
@@ -0,0 +1,78 @@
+[[okta-fastpass-phishing-detection]]
+=== Okta FastPass Phishing Detection
+
+Detects when Okta FastPass prevents a user from authenticating to a phishing website.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://developer.okta.com/docs/reference/api/system-log/
+* https://developer.okta.com/docs/reference/api/event-types/
+* https://sec.okta.com/fastpassphishingdetection
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+
+*Tags*: 
+
+* Tactic: Initial Access
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+
+*Version*: 103
+
+*Rule authors*: 
+
+* Austin Songer
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+This rule requires Okta to have the following turned on:
+
+Okta Identity Engine - select 'Phishing Resistance for FastPass' under Settings > Features in the Admin Console.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:okta.system and event.category:authentication and
+  okta.event_type:user.authentication.auth_via_mfa and event.outcome:failure and okta.outcome.reason:"FastPass declined phishing attempt"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
diff --git a/docs/detections/prebuilt-rules/rule-details/okta-sign-in-events-via-third-party-idp.asciidoc b/docs/detections/prebuilt-rules/rule-details/okta-sign-in-events-via-third-party-idp.asciidoc
new file mode 100644
index 0000000000..1737813a85
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/okta-sign-in-events-via-third-party-idp.asciidoc
@@ -0,0 +1,128 @@
+[[okta-sign-in-events-via-third-party-idp]]
+=== Okta Sign-In Events via Third-Party IdP
+
+Detects sign-in events where authentication is carried out via a third-party Identity Provider (IdP).
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 15m
+
+*Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.cloudflare.com/cloudflare-investigation-of-the-january-2022-okta-compromise/
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+* https://unit42.paloaltonetworks.com/muddled-libra/
+
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Tactic: Initial Access
+* Data Source: Okta
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Okta Sign-In Events via Third-Party IdP*
+
+
+This rule detects sign-in events where authentication is carried out via a third-party Identity Provider (IdP).
+
+Adversaries may attempt to add an unauthorized IdP to an Okta tenant to gain access to the tenant. Following this action, adversaries may attempt to sign in to the tenant using the unauthorized IdP. This rule detects both the addition of an unauthorized IdP and the subsequent sign-in attempt.
+
+
+*Possible investigation steps:*
+
+- Identify the third-party IdP by examining the `okta.authentication_context.issuer.id` field.
+- Once the third-party IdP is identified, determine if this IdP is authorized to be used by the tenant.
+- If the IdP is unauthorized, deactivate it immediately via the Okta console.
+- Identify the actor associated with the IdP creation by examining the `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, and `okta.actor.display_name` fields in historical data.
+    - The `New Okta Identity Provider (IdP) Added by Admin` rule may be helpful in identifying the actor and the IdP creation event.
+- Determine the client used by the actor. Review the `okta.client.ip`, `okta.client.user_agent.raw_user_agent`, `okta.client.zone`, `okta.client.device`, and `okta.client.id` fields.
+- If the client is a device, check the `okta.device.id`, `okta.device.name`, `okta.device.os_platform`, `okta.device.os_version`, and `okta.device.managed` fields.
+- Review the past activities of the actor involved in this action by checking their previous actions logged in the `okta.target` field.
+- Examine the `okta.request.ip_chain` field to potentially determine if the actor used a proxy or VPN to perform this action.
+- Evaluate the actions that happened just before and after this event in the `okta.event_type` field to help understand the full context of the activity.
+
+
+*False positive analysis:*
+
+- It might be a false positive if this IdP is authorized to be used by the tenant.
+- This may be a false positive if an authorized third-party IdP is used to sign in to the tenant but failures occurred due to an incorrect configuration.
+
+
+*Response and remediation:*
+
+- If the IdP is unauthorized, deactivate it immediately via the Okta console.
+- Reset the effected user's password and enforce MFA re-enrollment, if applicable.
+- Mobile device forensics may be required to determine if the user's device is compromised.
+- If the IdP is authorized, ensure that the actor who created it is authorized to do so.
+- If the actor is unauthorized, deactivate their account via the Okta console.
+- If the actor is authorized, ensure that the actor's account is not compromised.
+
+- Block the IP address or device used in the attempts if they appear suspicious, using the data from the `okta.client.ip` and `okta.device.id` fields.
+- Conduct a review of Okta policies and ensure they are in accordance with security best practices.
+- If the deactivated IdP was crucial to the organization, consider adding a new IdP and removing the unauthorized IdP.
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:okta.system and okta.debug_context.debug_data.request_uri:/oauth2/v1/authorize/callback and
+    (not okta.authentication_context.issuer.id:Okta and event.action:(user.authentication.auth_via_IDP
+        or user.authentication.auth_via_inbound_SAML
+        or user.authentication.auth_via_mfa
+        or user.authentication.auth_via_social)
+        or event.action:user.session.start) or
+    (event.action:user.authentication.auth_via_IDP and okta.outcome.result:FAILURE
+        and okta.outcome.reason:("A SAML assert with the same ID has already been processed by Okta for a previous request"
+            or "Unable to match transformed username"
+            or "Unable to resolve IdP endpoint"
+            or "Unable to validate SAML Response"
+            or "Unable to validate incoming SAML Assertion"))
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Trusted Relationship
+** ID: T1199
+** Reference URL: https://attack.mitre.org/techniques/T1199/
diff --git a/docs/detections/prebuilt-rules/rule-details/okta-threatinsight-threat-suspected-promotion.asciidoc b/docs/detections/prebuilt-rules/rule-details/okta-threatinsight-threat-suspected-promotion.asciidoc
new file mode 100644
index 0000000000..2016e26100
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/okta-threatinsight-threat-suspected-promotion.asciidoc
@@ -0,0 +1,66 @@
+[[okta-threatinsight-threat-suspected-promotion]]
+=== Okta ThreatInsight Threat Suspected Promotion
+
+Okta ThreatInsight is a feature that provides valuable debug data regarding authentication and authorization processes, which is logged in the system. Within this data, there is a specific field called threat_suspected, which represents Okta's internal evaluation of the authentication or authorization workflow. When this field is set to True, it suggests the presence of potential credential access techniques, such as password-spraying, brute-forcing, replay attacks, and other similar threats.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://developer.okta.com/docs/reference/api/system-log/
+* https://developer.okta.com/docs/reference/api/event-types/
+* https://help.okta.com/en-us/Content/Topics/Security/threat-insight/configure-threatinsight-system-log.html
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+
+*Version*: 205
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+This is a promotion rule for Okta ThreatInsight suspected threat events, which are alertable events per the vendor.
+Consult vendor documentation on interpreting specific events.
+
+==== Setup
+
+
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:okta.system and (event.action:security.threat.detected or okta.debug_context.debug_data.threat_suspected: true)
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/okta-user-session-impersonation.asciidoc b/docs/detections/prebuilt-rules/rule-details/okta-user-session-impersonation.asciidoc
index 28b724dbd1..7b59a51a78 100644
--- a/docs/detections/prebuilt-rules/rule-details/okta-user-session-impersonation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/okta-user-session-impersonation.asciidoc
@@ -5,7 +5,7 @@ A user has initiated a session impersonation granting them access to the environ
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,56 +14,86 @@ A user has initiated a session impersonation granting them access to the environ
 
 *Risk score*: 73
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.cloudflare.com/cloudflare-investigation-of-the-january-2022-okta-compromise/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Credential Access
-
-*Version*: 102 (<<okta-user-session-impersonation-history, version history>>)
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
+* Data Source: Okta
 
-*Added ({stack} release)*: 8.2.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating Okta User Session Impersonation*
+
+
+The detection of an Okta User Session Impersonation indicates that a user has initiated a session impersonation which grants them access with the permissions of the user they are impersonating. This type of activity typically indicates Okta administrative access and should only ever occur if requested and expected.
+
+
+*Possible investigation steps*
+
+
+- Identify the actor associated with the impersonation event by checking the `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields.
+- Review the `event.action` field to confirm the initiation of the impersonation event.
+- Check the `event.time` field to understand the timing of the event.
+- Check the `okta.target.id`, `okta.target.type`, `okta.target.alternate_id`, or `okta.target.display_name` to identify the user who was impersonated.
+- Review any activities that occurred during the impersonation session. Look for any activities related to the impersonated user's account during and after the impersonation event.
+
 
+*False positive analysis*
+
+
+- Verify if the session impersonation was part of an approved activity. Check if it was associated with any documented administrative tasks or troubleshooting efforts.
+- Ensure that the impersonation session was initiated by an authorized individual. You can check this by verifying the `okta.actor.id` or `okta.actor.display_name` against the list of approved administrators.
+
+
+*Response and remediation*
+
+
+- If the impersonation was not authorized, consider it as a breach. Suspend the user account of the impersonator immediately.
+- Reset the user session and invalidate any active sessions related to the impersonated user.
+- If a specific impersonation technique was used, ensure that systems are patched or configured to prevent such techniques.
+- Conduct a thorough investigation to understand the extent of the breach and the potential impact on the systems and data.
+- Review and update your security policies to prevent such incidents in the future.
+- Implement additional monitoring and logging of Okta events to improve visibility of user actions.
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and
-event.action:user.session.impersonation.initiate
+[source, js]
 ----------------------------------
+event.dataset:okta.system and event.action:user.session.impersonation.initiate
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -71,16 +101,3 @@ event.action:user.session.impersonation.initiate
 ** Name: Credential Access
 ** ID: TA0006
 ** Reference URL: https://attack.mitre.org/tactics/TA0006/
-
-[[okta-user-session-impersonation-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/okta-user-sessions-started-from-different-geolocations.asciidoc b/docs/detections/prebuilt-rules/rule-details/okta-user-sessions-started-from-different-geolocations.asciidoc
new file mode 100644
index 0000000000..17bfcd5beb
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/okta-user-sessions-started-from-different-geolocations.asciidoc
@@ -0,0 +1,79 @@
+[[okta-user-sessions-started-from-different-geolocations]]
+=== Okta User Sessions Started from Different Geolocations
+
+Detects when a specific Okta actor has multiple sessions started from different geolocations.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 15m
+
+*Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://developer.okta.com/docs/reference/api/system-log/
+* https://developer.okta.com/docs/reference/api/event-types/
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+* https://www.rezonate.io/blog/okta-logs-decoded-unveiling-identity-threats-through-threat-hunting/
+
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Initial Access
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:okta.system and okta.event_type:user.session.start and not okta.security_context.is_proxy:true
+    and okta.actor.id:* and client.geo.country_name:*
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Cloud Accounts
+** ID: T1078.004
+** Reference URL: https://attack.mitre.org/techniques/T1078/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/onedrive-malware-file-upload.asciidoc b/docs/detections/prebuilt-rules/rule-details/onedrive-malware-file-upload.asciidoc
index e2722498e1..042d168864 100644
--- a/docs/detections/prebuilt-rules/rule-details/onedrive-malware-file-upload.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/onedrive-malware-file-upload.asciidoc
@@ -5,7 +5,7 @@ Identifies the occurence of files uploaded to OneDrive being detected as Malware
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,59 +14,49 @@ Identifies the occurence of files uploaded to OneDrive being detected as Malware
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/virus-detection-in-spo?view=o365-worldwide
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Lateral Movement
-
-*Version*: 101 (<<onedrive-malware-file-upload-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Tactic: Lateral Movement
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Benign files can trigger signatures in the built-in virus protection
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:OneDrive and
-event.code:SharePointFileOperation and
-event.action:FileMalwareDetected
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:OneDrive and event.code:SharePointFileOperation and event.action:FileMalwareDetected
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,16 +68,3 @@ event.action:FileMalwareDetected
 ** Name: Taint Shared Content
 ** ID: T1080
 ** Reference URL: https://attack.mitre.org/techniques/T1080/
-
-[[onedrive-malware-file-upload-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/outbound-scheduled-task-activity-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/outbound-scheduled-task-activity-via-powershell.asciidoc
index 47c8a7f4f3..561fcd8982 100644
--- a/docs/detections/prebuilt-rules/rule-details/outbound-scheduled-task-activity-via-powershell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/outbound-scheduled-task-activity-via-powershell.asciidoc
@@ -5,64 +5,56 @@ Identifies the PowerShell process loading the Task Scheduler COM DLL followed by
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.library-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.volexity.com/blog/2020/12/14/dark-halo-leverages-solarwinds-compromise-to-breach-organizations/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-
-*Version*: 100 (<<outbound-scheduled-task-activity-via-powershell-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Legitimate scheduled tasks may be created during installation of new software.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan = 5s [any where
-(event.category == "library" or (event.category == "process" and
-event.action : "Image loaded*")) and (dll.name : "taskschd.dll" or
-file.name : "taskschd.dll") and process.name : ("powershell.exe",
-"pwsh.exe", "powershell_ise.exe")] [network where process.name :
-("powershell.exe", "pwsh.exe", "powershell_ise.exe") and
-destination.port == 135 and not destination.address in ("127.0.0.1",
-"::1")]
+[source, js]
 ----------------------------------
+sequence by host.id, process.entity_id with maxspan = 5s
+ [any where host.os.type == "windows" and (event.category == "library" or (event.category == "process" and event.action : "Image loaded*")) and
+  (?dll.name : "taskschd.dll" or file.name : "taskschd.dll") and process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe")]
+ [network where host.os.type == "windows" and process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe") and destination.port == 135 and not destination.address in ("127.0.0.1", "::1")]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,47 +66,15 @@ destination.port == 135 and not destination.address in ("127.0.0.1",
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[outbound-scheduled-task-activity-via-powershell-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan = 5s [library
-where dll.name : "taskschd.dll" and process.name : ("powershell.exe",
-"pwsh.exe", "powershell_ise.exe")] [network where process.name :
-("powershell.exe", "pwsh.exe", "powershell_ise.exe") and
-destination.port == 135 and not destination.address in ("127.0.0.1",
-"::1")]
-----------------------------------
-
-Version 4 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan = 5s [library
-where dll.name : "taskschd.dll" and process.name : ("powershell.exe",
-"pwsh.exe")] [network where process.name : ("powershell.exe",
-"pwsh.exe") and destination.port == 135 and not destination.address in
-("127.0.0.1", "::1")]
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan = 5s [library
-where file.name: "taskschd.dll" and process.name: ("powershell.exe",
-"pwsh.exe")] [network where process.name : ("powershell.exe",
-"pwsh.exe") and destination.port == 135 and not destination.address in
-("127.0.0.1", "::1")]
-----------------------------------
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/parent-process-pid-spoofing.asciidoc b/docs/detections/prebuilt-rules/rule-details/parent-process-pid-spoofing.asciidoc
index 33e01aa5e9..221158c10e 100644
--- a/docs/detections/prebuilt-rules/rule-details/parent-process-pid-spoofing.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/parent-process-pid-spoofing.asciidoc
@@ -5,69 +5,88 @@ Identifies parent process spoofing used to thwart detection. Adversaries may spo
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.didierstevens.com/2017/03/20/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-
-*Version*: 100 (<<parent-process-pid-spoofing-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-/* This rule is compatible with Elastic Endpoint only */ sequence by
-host.id, user.id with maxspan=5m [process where event.type == "start"
-and process.Ext.token.integrity_level_name != "system" and (
-process.pe.original_file_name : ("winword.exe", "excel.exe",
-"outlook.exe", "powerpnt.exe", "eqnedt32.exe",
-"fltldr.exe", "mspub.exe", "msaccess.exe", "powershell.exe",
-"pwsh.exe", "cscript.exe",
-"wscript.exe", "rundll32.exe", "regsvr32.exe", "msbuild.exe",
-"mshta.exe", "wmic.exe", "cmstp.exe", "msxsl.exe") or
-process.executable : ("?:\\Users\\*.exe",
-"?:\\ProgramData\\*.exe",
-"?:\\Windows\\Microsoft.NET\\*.exe",
-"?:\\Windows\\Temp\\*.exe",
-"?:\\Windows\\Tasks\\*") or process.code_signature.trusted != true
-) ] by process.pid [process where event.type == "start" and
-process.parent.Ext.real.pid > 0 and /* process.parent.Ext.real.pid
-is only populated if the parent process pid doesn't match */ not
-(process.name : "msedge.exe" and process.parent.name : "sihost.exe")
-] by process.parent.Ext.real.pid
+[source, js]
 ----------------------------------
+/* This rule is compatible with Elastic Endpoint only */
+
+sequence by host.id, user.id with maxspan=3m 
+
+ [process where host.os.type == "windows" and event.type == "start" and
+  process.Ext.token.integrity_level_name != "system" and 
+  (
+    process.pe.original_file_name : ("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe", "eqnedt32.exe",
+                                     "fltldr.exe", "mspub.exe", "msaccess.exe", "powershell.exe", "pwsh.exe",
+                                     "cscript.exe", "wscript.exe", "rundll32.exe", "regsvr32.exe", "msbuild.exe",
+                                     "mshta.exe", "wmic.exe", "cmstp.exe", "msxsl.exe") or 
+                                     
+    (process.executable : ("?:\\Users\\*.exe",
+                           "?:\\ProgramData\\*.exe",
+                           "?:\\Windows\\Temp\\*.exe",
+                           "?:\\Windows\\Tasks\\*") and 
+      (process.code_signature.exists == false or process.code_signature.status : "errorBadDigest")) or 
+                          
+    process.executable : "?:\\Windows\\Microsoft.NET\\*.exe"                      
+  ) and 
+  
+  not process.executable : 
+             ("?:\\Windows\\System32\\WerFaultSecure.exe", 
+              "?:\\WINDOWS\\SysWOW64\\WerFaultSecure.exe",
+              "?:\\Windows\\System32\\WerFault.exe",
+              "?:\\Windows\\SysWOW64\\WerFault.exe")
+  ] by process.pid
+ [process where host.os.type == "windows" and event.type == "start" and
+  process.parent.Ext.real.pid > 0 and 
+ 
+  /* process.parent.Ext.real.pid is only populated if the parent process pid doesn't match */
+  not (process.name : "msedge.exe" and process.parent.name : "sihost.exe") and 
+  
+   not process.executable : 
+             ("?:\\Windows\\System32\\WerFaultSecure.exe", 
+              "?:\\WINDOWS\\SysWOW64\\WerFaultSecure.exe",
+              "?:\\Windows\\System32\\WerFault.exe",
+              "?:\\Windows\\SysWOW64\\WerFault.exe")
+ ] by process.parent.Ext.real.pid
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,36 +98,19 @@ is only populated if the parent process pid doesn't match */ not
 ** Name: Access Token Manipulation
 ** ID: T1134
 ** Reference URL: https://attack.mitre.org/techniques/T1134/
-
-[[parent-process-pid-spoofing-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* This rule is compatible with Elastic Endpoint only */ sequence by
-host.id, user.id with maxspan=5m [process where event.type == "start"
-and process.Ext.token.integrity_level_name != "system" and (
-process.pe.original_file_name : ("winword.exe", "excel.exe",
-"outlook.exe", "powerpnt.exe", "eqnedt32.exe",
-"fltldr.exe", "mspub.exe", "msaccess.exe", "powershell.exe",
-"pwsh.exe", "cscript.exe",
-"wscript.exe", "rundll32.exe", "regsvr32.exe", "msbuild.exe",
-"mshta.exe", "wmic.exe", "cmstp.exe", "msxsl.exe") or
-process.executable : ("?:\\Users\\*.exe",
-"?:\\ProgramData\\*.exe",
-"?:\\Windows\\Microsoft.NET\\*.exe",
-"?:\\Windows\\Temp\\*.exe",
-"?:\\Windows\\Tasks\\*") or process.code_signature.trusted != true
-) ] by process.pid [process where event.type == "start" and
-process.parent.Ext.real.pid > 0 and /* process.parent.Ext.real.pid
-is only populated if the parent process pid doesn't match */ not
-(process.name : "msedge.exe" and process.parent.name : "sihost.exe")
-] by process.parent.Ext.real.pid
-----------------------------------
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Parent PID Spoofing
+** ID: T1134.004
+** Reference URL: https://attack.mitre.org/techniques/T1134/004/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Access Token Manipulation
+** ID: T1134
+** Reference URL: https://attack.mitre.org/techniques/T1134/
+* Sub-technique:
+** Name: Parent PID Spoofing
+** ID: T1134.004
+** Reference URL: https://attack.mitre.org/techniques/T1134/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/peripheral-device-discovery.asciidoc b/docs/detections/prebuilt-rules/rule-details/peripheral-device-discovery.asciidoc
index c3687dc4a0..ee0c3f07a9 100644
--- a/docs/detections/prebuilt-rules/rule-details/peripheral-device-discovery.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/peripheral-device-discovery.asciidoc
@@ -5,102 +5,112 @@ Identifies use of the Windows file system utility (fsutil.exe) to gather informa
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<peripheral-device-discovery-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Peripheral Device Discovery
+*Triage and analysis*
+
+
+
+*Investigating Peripheral Device Discovery*
+
+
+After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
+
+This rule looks for the execution of the `fsutil` utility with the `fsinfo` subcommand to enumerate drives attached to the computer, which can be used to identify secondary drives used for backups, mapped network drives, and removable media. These devices can contain valuable information for attackers.
 
-After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps.
-This can happen by running commands to enumerate network resources, users, connections, files, and installed security
-software.
 
-This rule looks for the execution of the `fsutil` utility with the `fsinfo` subcommand to enumerate drives attached to
-the computer, which can be used to identify secondary drives used for backups, mapped network drives, and removable
-media. These devices can contain valuable information for attackers.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
-- Determine whether this activity was followed by suspicious file access/copy operations or uploads to file storage
-services.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+- Determine whether this activity was followed by suspicious file access/copy operations or uploads to file storage services.
 
-### False positive analysis
 
-- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify
-suspicious activity related to the user or host, such alerts can be dismissed.
+*False positive analysis*
+
+
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name : "fsutil.exe"
-or process.pe.original_file_name == "fsutil.exe") and process.args :
-"fsinfo" and process.args : "drives"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "fsutil.exe" or ?process.pe.original_file_name == "fsutil.exe") and
+  process.args : "fsinfo" and process.args : "drives"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -112,44 +122,3 @@ or process.pe.original_file_name == "fsutil.exe") and process.args :
 ** Name: Peripheral Device Discovery
 ** ID: T1120
 ** Reference URL: https://attack.mitre.org/techniques/T1120/
-
-[[peripheral-device-discovery-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "fsutil.exe" or process.pe.original_file_name ==
-"fsutil.exe") and process.args : "fsinfo" and process.args :
-"drives"
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "fsutil.exe" or process.pe.original_file_name ==
-"fsutil.exe") and process.args : "fsinfo" and process.args :
-"drives"
-----------------------------------
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/permission-theft-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/permission-theft-detected-elastic-endgame.asciidoc
index eac825819e..b81c295527 100644
--- a/docs/detections/prebuilt-rules/rule-details/permission-theft-detected-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/permission-theft-detected-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame detected Permission Theft. Click the Elastic Endgame icon in the
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,41 +13,52 @@ Elastic Endgame detected Permission Theft. Click the Elastic Endgame icon in the
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<permission-theft-detected-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:detection and
-(event.action:token_protection_event or
-endgame.event_subtype_full:token_protection_event)
+[source, js]
 ----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:token_protection_event or endgame.event_subtype_full:token_protection_event)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -59,35 +70,3 @@ endgame.event_subtype_full:token_protection_event)
 ** Name: Access Token Manipulation
 ** ID: T1134
 ** Reference URL: https://attack.mitre.org/techniques/T1134/
-
-[[permission-theft-detected-elastic-endgame-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Formatting only
-
-Version 6 (7.12.1 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Rule name changed from: Permission Theft - Detected - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Permission Theft - Detected - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Permission Theft - Detected - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:token_protection_event and
-endgame.metadata.type:detection
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/permission-theft-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/permission-theft-prevented-elastic-endgame.asciidoc
index 53d68054c5..895256cf8a 100644
--- a/docs/detections/prebuilt-rules/rule-details/permission-theft-prevented-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/permission-theft-prevented-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame prevented Permission Theft. Click the Elastic Endgame icon in th
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,41 +13,52 @@ Elastic Endgame prevented Permission Theft. Click the Elastic Endgame icon in th
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<permission-theft-prevented-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:prevention and
-(event.action:token_protection_event or
-endgame.event_subtype_full:token_protection_event)
+[source, js]
 ----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:token_protection_event or endgame.event_subtype_full:token_protection_event)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -59,35 +70,3 @@ endgame.event_subtype_full:token_protection_event)
 ** Name: Access Token Manipulation
 ** ID: T1134
 ** Reference URL: https://attack.mitre.org/techniques/T1134/
-
-[[permission-theft-prevented-elastic-endgame-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Formatting only
-
-Version 6 (7.12.1 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Rule name changed from: Permission Theft - Prevented - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Permission Theft - Prevented - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Permission Theft - Prevented - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:token_protection_event and
-endgame.metadata.type:prevention
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-bits-job-notify-cmdline.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-bits-job-notify-cmdline.asciidoc
index f35560ea03..b87dbe6abb 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-bits-job-notify-cmdline.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-bits-job-notify-cmdline.asciidoc
@@ -5,71 +5,77 @@ An adversary can use the Background Intelligent Transfer Service (BITS) SetNotif
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://pentestlab.blog/2019/10/30/persistence-bits-jobs/
 * https://docs.microsoft.com/en-us/windows/win32/api/bits1_5/nf-bits1_5-ibackgroundcopyjob2-setnotifycmdline
 * https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/bitsadmin-setnotifycmdline
 * https://www.elastic.co/blog/hunting-for-persistence-using-elastic-security-part-2
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 100 (<<persistence-via-bits-job-notify-cmdline-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.13.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"svchost.exe" and process.parent.args : "BITS" and not
-process.executable :
-("?:\\Windows\\System32\\WerFaultSecure.exe",
-"?:\\Windows\\System32\\WerFault.exe",
-"?:\\Windows\\System32\\wermgr.exe",
-"?:\\WINDOWS\\system32\\directxdatabaseupdater.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : "svchost.exe" and process.parent.args : "BITS" and
+  not process.executable :
+              ("?:\\Windows\\System32\\WerFaultSecure.exe",
+               "?:\\Windows\\System32\\WerFault.exe",
+               "?:\\Windows\\System32\\wermgr.exe",
+               "?:\\WINDOWS\\system32\\directxdatabaseupdater.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,16 +87,3 @@ process.executable :
 ** Name: BITS Jobs
 ** ID: T1197
 ** Reference URL: https://attack.mitre.org/techniques/T1197/
-
-[[persistence-via-bits-job-notify-cmdline-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-directoryservice-plugin-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-directoryservice-plugin-modification.asciidoc
index d39226539a..bf0ad12547 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-directoryservice-plugin-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-directoryservice-plugin-modification.asciidoc
@@ -5,53 +5,87 @@ Identifies the creation or modification of a DirectoryService PlugIns (dsplug) f
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.chichou.me/2019/11/21/two-macos-persistence-tricks-abusing-plugins/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<persistence-via-directoryservice-plugin-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:file and not event.type:deletion and
-file.path:/Library/DirectoryServices/PlugIns/*.dsplug
+[source, js]
 ----------------------------------
+event.category:file and host.os.type:macos and not event.type:deletion and
+  file.path:/Library/DirectoryServices/PlugIns/*.dsplug
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -63,13 +97,3 @@ file.path:/Library/DirectoryServices/PlugIns/*.dsplug
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[persistence-via-directoryservice-plugin-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-docker-shortcut-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-docker-shortcut-modification.asciidoc
index f73ae68e91..e5274ae822 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-docker-shortcut-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-docker-shortcut-modification.asciidoc
@@ -5,55 +5,89 @@ An adversary can establish persistence by modifying an existing macOS dock prope
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/specterops/presentations/raw/master/Leo%20Pitt/Hey_Im_Still_in_Here_Modern_macOS_Persistence_SO-CON2020.pdf
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<persistence-via-docker-shortcut-modification-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.12.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category : file and event.action : modification and file.path :
-/Users/*/Library/Preferences/com.apple.dock.plist and not
-process.name : (xpcproxy or cfprefsd or plutil or jamf or PlistBuddy
-or InstallerRemotePluginService)
+[source, js]
 ----------------------------------
+event.category:file and host.os.type:macos and event.action:modification and
+ file.path:/Users/*/Library/Preferences/com.apple.dock.plist and
+ not process.name:(xpcproxy or cfprefsd or plutil or jamf or PlistBuddy or InstallerRemotePluginService) and
+ not process.executable:(/Library/Addigy/download-cache/* or "/Library/Kandji/Kandji Agent.app/Contents/MacOS/kandji-library-manager")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -65,24 +99,3 @@ or InstallerRemotePluginService)
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[persistence-via-docker-shortcut-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category : file and event.action : modification and file.path
-: /Users/*/Library/Preferences/com.apple.dock.plist and not
-process.name : (xpcproxy or cfprefsd or plutil or jamf or PlistBuddy
-or InstallerRemotePluginService)
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-folder-action-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-folder-action-script.asciidoc
index 772c60a87c..be4bbecff1 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-folder-action-script.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-folder-action-script.asciidoc
@@ -5,60 +5,88 @@ Detects modification of a Folder Action script. A Folder Action script is execut
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://posts.specterops.io/folder-actions-for-persistence-on-macos-8923f222343d
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Execution
-* Persistence
 
-*Version*: 100 (<<persistence-via-folder-action-script-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=5s [process where event.type in
-("start", "process_started", "info") and process.name ==
-"com.apple.foundation.UserScriptService"] by process.pid [process
-where event.type in ("start", "process_started") and process.name in
-("osascript", "python", "tcl", "node", "perl", "ruby", "php", "bash",
-"csh", "zsh", "sh") and not process.args :
-"/Users/*/Library/Application
-Support/iTerm2/Scripts/AutoLaunch/*.scpt" ] by process.parent.pid
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type : "start" and process.name in ("osascript", "python", "tcl", "node", "perl", "ruby", "php", "bash", "csh", "zsh", "sh") and
+  process.parent.name == "com.apple.foundation.UserScriptService" and not process.args : ("/Users/*/Library/Application Support/iTerm2/Scripts/AutoLaunch/*.scpt", "/Users/*/Library/Application Scripts/com.microsoft.*/FoxitUtils.applescript")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,8 +98,6 @@ Support/iTerm2/Scripts/AutoLaunch/*.scpt" ] by process.parent.pid
 ** Name: Boot or Logon Initialization Scripts
 ** ID: T1037
 ** Reference URL: https://attack.mitre.org/techniques/T1037/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -80,53 +106,3 @@ Support/iTerm2/Scripts/AutoLaunch/*.scpt" ] by process.parent.pid
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[persistence-via-folder-action-script-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [process where event.type in
-("start", "process_started", "info") and process.name ==
-"com.apple.foundation.UserScriptService"] by process.pid [process
-where event.type in ("start", "process_started") and process.name in
-("osascript", "python", "tcl", "node", "perl", "ruby", "php", "bash",
-"csh", "zsh", "sh")] by process.parent.pid
-----------------------------------
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [process where event.type in
-("start", "process_started", "info") and process.name ==
-"com.apple.foundation.UserScriptService"] by process.pid [process
-where event.type in ("start", "process_started") and process.name in
-("osascript", "sh")] by process.parent.pid
-----------------------------------
-
-Version 3 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [process where event.type in
-("start", "process_started", "info") and process.name ==
-"com.apple.foundation.UserScriptService"] by process.pid [process
-where event.type in ("start", "process_started") and process.name in
-("osascript", "sh")] by process.ppid
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-hidden-run-key-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-hidden-run-key-detected.asciidoc
index 457c24c29d..cde532b5f0 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-hidden-run-key-detected.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-hidden-run-key-detected.asciidoc
@@ -5,73 +5,84 @@ Identifies a persistence mechanism that utilizes the NtSetValueKey native API to
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/outflanknl/SharpHide
 * https://github.com/ewhitehats/InvisiblePersistence/blob/master/InvisibleRegValues_Whitepaper.pdf
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 100 (<<persistence-via-hidden-run-key-detected-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-/* Registry Path ends with backslash */ registry where /*
-length(registry.data.strings) > 0 and */ registry.path :
-("HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
-"HKU\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
-"HKLM\\Software\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Run\
-\", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\Cu
-rrentVersion\\Policies\\Explorer\\Run\\", "HKU\\*\\S
-oftware\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\
-", "HKLM\\Software\\Microsoft\\Windows\\CurrentVersi
-on\\Policies\\Explorer\\Run\\")
+[source, js]
 ----------------------------------
+/* Registry Path ends with backslash */
+registry where host.os.type == "windows" and /* length(registry.data.strings) > 0 and */
+ registry.path : ("HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
+                  "HKU\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
+                  "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
+                  "HKLM\\Software\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Run\\",
+                  "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\",
+                  "HKU\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\",
+                  "\\REGISTRY\\MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\",
+                  "\\REGISTRY\\USER\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
+                  "\\REGISTRY\\MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
+                  "\\REGISTRY\\MACHINE\\Software\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Run\\",
+                  "\\REGISTRY\\USER\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\",
+                  "\\REGISTRY\\MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -83,53 +94,23 @@ on\\Policies\\Explorer\\Run\\")
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[persistence-via-hidden-run-key-detected-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* Registry Path ends with backslash */ registry where /*
-length(registry.data.strings) > 0 and */ registry.path :
-("HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
-"HKU\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
-"HKLM\\Software\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Run\
-\", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\C
-urrentVersion\\Policies\\Explorer\\Run\\", "HKU\\*\\
-Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\
-\", "HKLM\\Software\\Microsoft\\Windows\\CurrentVers
-ion\\Policies\\Explorer\\Run\\")
-----------------------------------
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* Registry Path ends with backslash */ registry where /*
-length(registry.data.strings) > 0 and */ registry.path :
-("HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\",
-"HKLM\\Software\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Run\
-\", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\C
-urrentVersion\\Policies\\Explorer\\Run\\", "HKLM\\S
-oftware\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\
-")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Registry Run Keys / Startup Folder
+** ID: T1547.001
+** Reference URL: https://attack.mitre.org/techniques/T1547/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Native API
+** ID: T1106
+** Reference URL: https://attack.mitre.org/techniques/T1106/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-kde-autostart-script-or-desktop-file-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-kde-autostart-script-or-desktop-file-modification.asciidoc
index 5dbe1e7718..98c6941439 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-kde-autostart-script-or-desktop-file-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-kde-autostart-script-or-desktop-file-modification.asciidoc
@@ -5,74 +5,202 @@ Identifies the creation or modification of a K Desktop Environment (KDE) AutoSta
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://userbase.kde.org/System_Settings/Autostart
 * https://www.amnesty.org/en/latest/research/2020/09/german-made-finspy-spyware-found-in-egypt-and-mac-and-linux-versions-revealed/
 * https://www.intezer.com/blog/research/operation-electrorat-attacker-creates-fake-companies-to-drain-your-crypto-wallets/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Persistence
-
-*Version*: 100 (<<persistence-via-kde-autostart-script-or-desktop-file-modification-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating Persistence via KDE AutoStart Script or Desktop File Modification*
+
+
+K Desktop Environment (KDE) is a popular graphical desktop environment for Linux systems. It supports AutoStart scripts and desktop files that execute automatically upon user logon.
+
+Adversaries may exploit this feature to maintain persistence on a compromised system by creating or modifying these files.
+
+The detection rule 'Persistence via KDE AutoStart Script or Desktop File Modification' is designed to identify such activities by monitoring file events on Linux systems. It specifically targets the creation or modification of files with extensions ".sh" or ".desktop" in various AutoStart directories. By detecting these events, the rule helps security analysts identify potential abuse of KDE AutoStart functionality by malicious actors.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Investigate the file that was created or modified.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE (\n  path LIKE '/home/%/.config/autostart/%.sh' OR path LIKE '/home/%/.config/autostart/%.desktop' OR\n  path LIKE '/root/.config/autostart/%.sh' OR path LIKE '/root/.config/autostart/%.desktop' OR\n  path LIKE '/home/%/.kde/Autostart/%.sh' OR path LIKE '/home/%/.kde/Autostart/%.desktop' OR\n  path LIKE '/root/.kde/Autostart/%.sh' OR path LIKE '/root/.kde/Autostart/%.desktop' OR\n  path LIKE '/home/%/.kde4/Autostart/%.sh' OR path LIKE '/home/%/.kde4/Autostart/%.desktop' OR\n  path LIKE '/root/.kde4/Autostart/%.sh' OR path LIKE '/root/.kde4/Autostart/%.desktop' OR\n  path LIKE '/home/%/.kde/share/autostart/%.sh' OR path LIKE '/home/%/.kde/share/autostart/%.desktop' OR\n  path LIKE '/root/.kde/share/autostart/%.sh' OR path LIKE '/root/.kde/share/autostart/%.desktop' OR\n  path LIKE '/home/%/.kde4/share/autostart/%.sh' OR path LIKE '/home/%/.kde4/share/autostart/%.desktop' OR\n  path LIKE '/root/.kde4/share/autostart/%.sh' OR path LIKE '/root/.kde4/share/autostart/%.desktop' OR\n  path LIKE '/home/%/.local/share/autostart/%.sh' OR path LIKE '/home/%/.local/share/autostart/%.desktop' OR\n  path LIKE '/root/.local/share/autostart/%.sh' OR path LIKE '/root/.local/share/autostart/%.desktop' OR\n  path LIKE '/home/%/.config/autostart-scripts/%.sh' OR path LIKE '/home/%/.config/autostart-scripts/%.desktop' OR\n  path LIKE '/root/.config/autostart-scripts/%.sh' OR path LIKE '/root/.config/autostart-scripts/%.desktop' OR\n  path LIKE '/etc/xdg/autostart/%.sh' OR path LIKE '/etc/xdg/autostart/%.desktop' OR\n  path LIKE '/usr/share/autostart/%.sh' OR path LIKE '/usr/share/autostart/%.desktop'\n)\n"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE (\n  path LIKE '/home/%/.config/autostart/%.sh' OR path LIKE '/home/%/.config/autostart/%.desktop' OR\n  path LIKE '/root/.config/autostart/%.sh' OR path LIKE '/root/.config/autostart/%.desktop' OR\n  path LIKE '/home/%/.kde/Autostart/%.sh' OR path LIKE '/home/%/.kde/Autostart/%.desktop' OR\n  path LIKE '/root/.kde/Autostart/%.sh' OR path LIKE '/root/.kde/Autostart/%.desktop' OR\n  path LIKE '/home/%/.kde4/Autostart/%.sh' OR path LIKE '/home/%/.kde4/Autostart/%.desktop' OR\n  path LIKE '/root/.kde4/Autostart/%.sh' OR path LIKE '/root/.kde4/Autostart/%.desktop' OR\n  path LIKE '/home/%/.kde/share/autostart/%.sh' OR path LIKE '/home/%/.kde/share/autostart/%.desktop' OR\n  path LIKE '/root/.kde/share/autostart/%.sh' OR path LIKE '/root/.kde/share/autostart/%.desktop' OR\n  path LIKE '/home/%/.kde4/share/autostart/%.sh' OR path LIKE '/home/%/.kde4/share/autostart/%.desktop' OR\n  path LIKE '/root/.kde4/share/autostart/%.sh' OR path LIKE '/root/.kde4/share/autostart/%.desktop' OR\n  path LIKE '/home/%/.local/share/autostart/%.sh' OR path LIKE '/home/%/.local/share/autostart/%.desktop' OR\n  path LIKE '/root/.local/share/autostart/%.sh' OR path LIKE '/root/.local/share/autostart/%.desktop' OR\n  path LIKE '/home/%/.config/autostart-scripts/%.sh' OR path LIKE '/home/%/.config/autostart-scripts/%.desktop' OR\n  path LIKE '/root/.config/autostart-scripts/%.sh' OR path LIKE '/root/.config/autostart-scripts/%.desktop' OR\n  path LIKE '/etc/xdg/autostart/%.sh' OR path LIKE '/etc/xdg/autostart/%.desktop' OR\n  path LIKE '/usr/share/autostart/%.sh' OR path LIKE '/usr/share/autostart/%.desktop'\n)\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+    - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+    - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator who uses cron jobs for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Custom Ingest Pipeline*
+
+For versions <8.2, you need to add a custom ingest pipeline to populate `event.ingested` with @timestamp for non-elastic-agent indexes, like auditbeats/filebeat/winlogbeat etc. For more details to add a custom ingest pipeline refer to the https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html[guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.extension in ("sh",
-"desktop") and file.path : (
-"/home/*/.config/autostart/*", "/root/.config/autostart/*",
-"/home/*/.kde/Autostart/*", "/root/.kde/Autostart/*",
-"/home/*/.kde4/Autostart/*", "/root/.kde4/Autostart/*",
-"/home/*/.kde/share/autostart/*", "/root/.kde/share/autostart/*",
-"/home/*/.kde4/share/autostart/*", "/root/.kde4/share/autostart/*",
-"/home/*/.local/share/autostart/*", "/root/.local/share/autostart/*",
-"/home/*/.config/autostart-scripts/*", "/root/.config/autostart-
-scripts/*", "/etc/xdg/autostart/*", "/usr/share/autostart/*"
-) and not process.name in ("yum", "dpkg", "install", "dnf",
-"teams", "yum-cron", "dnf-automatic")
+[source, js]
 ----------------------------------
+file where host.os.type == "linux" and event.type != "deletion" and
+  file.extension in ("sh", "desktop") and
+  file.path :
+    (
+      "/home/*/.config/autostart/*", "/root/.config/autostart/*",
+      "/home/*/.kde/Autostart/*", "/root/.kde/Autostart/*",
+      "/home/*/.kde4/Autostart/*", "/root/.kde4/Autostart/*",
+      "/home/*/.kde/share/autostart/*", "/root/.kde/share/autostart/*",
+      "/home/*/.kde4/share/autostart/*", "/root/.kde4/share/autostart/*",
+      "/home/*/.local/share/autostart/*", "/root/.local/share/autostart/*",
+      "/home/*/.config/autostart-scripts/*", "/root/.config/autostart-scripts/*",
+      "/etc/xdg/autostart/*", "/usr/share/autostart/*"
+    ) and
+    not process.name in ("yum", "dpkg", "install", "dnf", "teams", "yum-cron", "dnf-automatic", "docker", "dockerd", 
+    "rpm", "pacman", "podman", "nautilus", "remmina", "cinnamon-settings.py")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,31 +212,3 @@ scripts/*", "/etc/xdg/autostart/*", "/usr/share/autostart/*"
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[persistence-via-kde-autostart-script-or-desktop-file-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type != "deletion" and file.extension in ("sh",
-"desktop") and file.path : (
-"/home/*/.config/autostart/*", "/root/.config/autostart/*",
-"/home/*/.kde/Autostart/*", "/root/.kde/Autostart/*",
-"/home/*/.kde4/Autostart/*", "/root/.kde4/Autostart/*",
-"/home/*/.kde/share/autostart/*", "/root/.kde/share/autostart/*",
-"/home/*/.kde4/share/autostart/*", "/root/.kde4/share/autostart/*",
-"/home/*/.local/share/autostart/*", "/root/.local/share/autostart/*",
-"/home/*/.config/autostart-scripts/*", "/root/.config/autostart-
-scripts/*", "/etc/xdg/autostart/*", "/usr/share/autostart/*"
-)
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-login-or-logout-hook.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-login-or-logout-hook.asciidoc
index 4add0902fd..4f8036c9ab 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-login-or-logout-hook.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-login-or-logout-hook.asciidoc
@@ -5,70 +5,95 @@ Identifies use of the Defaults command to install a login or logoff hook in MacO
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.virusbulletin.com/uploads/pdf/conference_slides/2014/Wardle-VB2014.pdf
 * https://www.manpagez.com/man/1/defaults/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<persistence-via-login-or-logout-hook-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.11.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
 
-==== Investigation guide
 
+This rule requires data coming in from Elastic Defend.
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name == "defaults"
-and process.args == "write" and process.args in ("LoginHook",
-"LogoutHook") and not process.args : (
-"Support/JAMF/ManagementFrameworkScripts/logouthook.sh",
-"Support/JAMF/ManagementFrameworkScripts/loginhook.sh",
-"/Library/Application
-Support/JAMF/ManagementFrameworkScripts/logouthook.sh",
-"/Library/Application
-Support/JAMF/ManagementFrameworkScripts/loginhook.sh" )
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type == "start" and
+ process.name == "defaults" and process.args == "write" and process.args : ("LoginHook", "LogoutHook") and
+ not process.args :
+       (
+         "Support/JAMF/ManagementFrameworkScripts/logouthook.sh",
+         "Support/JAMF/ManagementFrameworkScripts/loginhook.sh",
+         "/Library/Application Support/JAMF/ManagementFrameworkScripts/logouthook.sh",
+         "/Library/Application Support/JAMF/ManagementFrameworkScripts/loginhook.sh"
+       )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,32 +105,3 @@ Support/JAMF/ManagementFrameworkScripts/loginhook.sh" )
 ** Name: Boot or Logon Initialization Scripts
 ** ID: T1037
 ** Reference URL: https://attack.mitre.org/techniques/T1037/
-
-[[persistence-via-login-or-logout-hook-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name == "defaults" and process.args == "write" and
-process.args in ("LoginHook", "LogoutHook")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-microsoft-office-addins.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-microsoft-office-addins.asciidoc
index 859da722cb..26076979ad 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-microsoft-office-addins.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-microsoft-office-addins.asciidoc
@@ -5,66 +5,75 @@ Detects attempts to establish persistence on an endpoint by abusing Microsoft Of
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.file-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
-* https://labs.mwrinfosecurity.com/blog/add-in-opportunities-for-office-persistence/
+* https://labs.withsecure.com/publications/add-in-opportunities-for-office-persistence
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 100 (<<persistence-via-microsoft-office-addins-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.extension :
-("wll","xll","ppa","ppam","xla","xlam") and file.path : (
-"C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Word\\Startup\\*",
-"C:\\Users\\*\\AppData\\Roaming\\Microsoft\\AddIns\\*",
-"C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Excel\\XLSTART\\*" )
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and
+ file.extension : ("wll","xll","ppa","ppam","xla","xlam") and
+ file.path :
+    (
+    "C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Word\\Startup\\*",
+    "C:\\Users\\*\\AppData\\Roaming\\Microsoft\\AddIns\\*",
+    "C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Excel\\XLSTART\\*"
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,32 +85,7 @@ file where event.type != "deletion" and file.extension :
 ** Name: Office Application Startup
 ** ID: T1137
 ** Reference URL: https://attack.mitre.org/techniques/T1137/
-
-[[persistence-via-microsoft-office-addins-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type != "deletion" and
-wildcard(file.extension,"wll","xll","ppa","ppam","xla","xlam") and
-wildcard(file.path,
-"C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Word\\Startup\\*",
-"C:\\Users\\*\\AppData\\Roaming\\Microsoft\\AddIns\\*",
-"C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Excel\\XLSTART\\*")
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Add-ins
+** ID: T1137.006
+** Reference URL: https://attack.mitre.org/techniques/T1137/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-microsoft-outlook-vba.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-microsoft-outlook-vba.asciidoc
index 3aa3c2b542..b3c42fca85 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-microsoft-outlook-vba.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-microsoft-outlook-vba.asciidoc
@@ -5,68 +5,70 @@ Detects attempts to establish persistence on an endpoint by installing a rogue M
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.file-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.mdsec.co.uk/2020/11/a-fresh-outlook-on-mail-based-persistence/
 * https://www.linkedin.com/pulse/outlook-backdoor-using-vba-samir-b-/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 100 (<<persistence-via-microsoft-outlook-vba-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-A legitimate VBA for Outlook is usually configured interactively via OUTLOOK.EXE.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.path :
-"C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Outlook\\VbaProject.OTM"
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and
+ file.path : "C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Outlook\\VbaProject.OTM"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,28 +80,3 @@ file where event.type != "deletion" and file.path :
 ** Name: Office Application Startup
 ** ID: T1137
 ** Reference URL: https://attack.mitre.org/techniques/T1137/
-
-[[persistence-via-microsoft-outlook-vba-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type != "deletion" and wildcard(file.path,
-"C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Outlook\\VbaProject.OTM")
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-powershell-profile.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-powershell-profile.asciidoc
index 6e4ac7163f..580f6ec0b8 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-powershell-profile.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-powershell-profile.asciidoc
@@ -5,56 +5,127 @@ Identifies the creation or modification of a PowerShell profile. PowerShell prof
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_profiles
 * https://www.welivesecurity.com/2019/05/29/turla-powershell-usage/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Version*: 1
+*Version*: 9
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Persistence via PowerShell profile*
+
+
+PowerShell profiles are scripts executed when PowerShell starts, customizing the user environment. They are commonly used in Windows environments for legitimate purposes, such as setting variables or loading modules. However, adversaries can abuse PowerShell profiles to establish persistence by inserting malicious code that executes each time PowerShell is launched.
+
+This rule identifies the creation or modification of a PowerShell profile. It does this by monitoring file events on Windows systems, specifically targeting profile-related file paths and names, such as `profile.ps1` and `Microsoft.Powershell_profile.ps1`. By detecting these activities, security analysts can investigate potential abuse of PowerShell profiles for malicious persistence.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Retrive and inspect the PowerShell profile content; look for suspicious DLL imports, collection or persistence capabilities, suspicious functions, encoded or compressed data, suspicious commands, and other potentially malicious characteristics.
+- Identify the process responsible for the PowerShell profile creation/modification. Use the Elastic Defend events to examine all the activity of the subject process by filtering by the process's `process.entity_id`.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Evaluate whether the user needs to use PowerShell to complete tasks.
+- Check for additional PowerShell and command-line logs that indicate that any suspicious command or function were run.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Observe and collect information about the following activities in the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+
+
+*False positive analysis*
+
+
+- This is a dual-use mechanism, meaning its usage is not inherently malicious. Analysts can dismiss the alert if the script doesn't contain malicious functions or potential for abuse, no other suspicious activity was identified, and the user has business justifications to use PowerShell.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+  - If malicious activity is confirmed, perform a broader investigation to identify the scope of the compromise and determine the appropriate remediation steps.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Reimage the host operating system or restore the compromised files to clean versions.
+- Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+  - Consider enabling and collecting PowerShell logs such as transcription, module, and script block logging, to improve visibility into PowerShell activities.
+
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.path :
-("?:\\Users\\*\\Documents\\WindowsPowerShell\\*",
-"?:\\Users\\*\\Documents\\PowerShell\\*",
-"?:\\Windows\\System32\\WindowsPowerShell\\*") and file.name :
-("profile.ps1", "Microsoft.Powershell_profile.ps1")
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and
+  file.path : ("?:\\Users\\*\\Documents\\WindowsPowerShell\\*",
+               "?:\\Users\\*\\Documents\\PowerShell\\*",
+               "?:\\Windows\\System32\\WindowsPowerShell\\*") and
+  file.name : ("profile.ps1", "Microsoft.Powershell_profile.ps1")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,3 +137,19 @@ file where event.type != "deletion" and file.path :
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: PowerShell Profile
+** ID: T1546.013
+** Reference URL: https://attack.mitre.org/techniques/T1546/013/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: PowerShell Profile
+** ID: T1546.013
+** Reference URL: https://attack.mitre.org/techniques/T1546/013/
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-scheduled-job-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-scheduled-job-creation.asciidoc
index b03c750d44..979060630a 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-scheduled-job-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-scheduled-job-creation.asciidoc
@@ -5,63 +5,80 @@ A job can be used to schedule programs or scripts to be executed at a specified
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 100 (<<persistence-via-scheduled-job-creation-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.13.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Legitimate scheduled jobs may be created during installation of new software.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.path :
-"?:\\Windows\\Tasks\\*" and file.extension : "job"
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and
+  file.path : "?:\\Windows\\Tasks\\*" and file.extension : "job" and
+  not (
+    (
+      process.executable : "?:\\Program Files\\CCleaner\\CCleaner64.exe" and
+      file.path : "?:\\Windows\\Tasks\\CCleanerCrashReporting.job"
+    ) or
+    (
+      process.executable : (
+        "?:\\Program Files (x86)\\ManageEngine\\UEMS_Agent\\bin\\dcagentregister.exe",
+        "?:\\Program Files (x86)\\DesktopCentral_Agent\\bin\\dcagentregister.exe"
+      ) and
+      file.path : "?:\\Windows\\Tasks\\DCAgentUpdater.job"
+    )
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,19 +90,7 @@ file where event.type != "deletion" and file.path :
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[persistence-via-scheduled-job-creation-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-telemetrycontroller-scheduled-task-hijack.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-telemetrycontroller-scheduled-task-hijack.asciidoc
index 100752b7ff..7be3dfe7fd 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-telemetrycontroller-scheduled-task-hijack.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-telemetrycontroller-scheduled-task-hijack.asciidoc
@@ -5,66 +5,76 @@ Detects the successful hijack of Microsoft Compatibility Appraiser scheduled tas
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
-* https://www.trustedsec.com/blog/abusing-windows-telemetry-for-persistence/?utm_content=131234033&utm_medium=social&utm_source=twitter&hss_channel=tw-403811306
+* https://www.trustedsec.com/blog/abusing-windows-telemetry-for-persistence
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 101 (<<persistence-via-telemetrycontroller-scheduled-task-hijack-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"CompatTelRunner.exe" and process.args : "-cv*" and not process.name
-: ("conhost.exe", "DeviceCensus.exe",
-"CompatTelRunner.exe", "DismHost.exe",
-"rundll32.exe", "powershell.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : "CompatTelRunner.exe" and process.args : "-cv*" and
+  not process.name : ("conhost.exe",
+                      "DeviceCensus.exe",
+                      "CompatTelRunner.exe",
+                      "DismHost.exe",
+                      "rundll32.exe",
+                      "powershell.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,60 +86,27 @@ process where event.type == "start" and process.parent.name :
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[persistence-via-telemetrycontroller-scheduled-task-hijack-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "CompatTelRunner.exe" and process.args : "-cv*"
-and not process.name : ("conhost.exe",
-"DeviceCensus.exe", "CompatTelRunner.exe",
-"DismHost.exe", "rundll32.exe",
-"powershell.exe")
-----------------------------------
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (7.16.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:(CompatTelRunner.exe or compattelrunner.exe) and
-process.args:-cv* and not process.name:(conhost.exe or
-DeviceCensus.exe or devicecensus.exe or CompatTelRunner.exe or
-compattelrunner.exe or DismHost.exe or dismhost.exe or rundll32.exe or
-powershell.exe)
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:(CompatTelRunner.exe or compattelrunner.exe) and
-not process.name:(conhost.exe or DeviceCensus.exe or devicecensus.exe
-or CompatTelRunner.exe or compattelrunner.exe or DismHost.exe or
-dismhost.exe or rundll32.exe)
-----------------------------------
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-update-orchestrator-service-hijack.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-update-orchestrator-service-hijack.asciidoc
index d3322c6bce..fbc236327b 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-update-orchestrator-service-hijack.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-update-orchestrator-service-hijack.asciidoc
@@ -5,97 +5,99 @@ Identifies potential hijacking of the Microsoft Update Orchestrator Service to e
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/irsl/CVE-2020-1313
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* CVE-2020-1313
-* Investigation Guide
-
-*Version*: 102 (<<persistence-via-update-orchestrator-service-hijack-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Use Case: Vulnerability
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Persistence via Update Orchestrator Service Hijack
+*Triage and analysis*
+
 
-Windows Update Orchestrator Service is a DCOM service used by other components to install Windows updates that are
-already downloaded. Windows Update Orchestrator Service was vulnerable to elevation of privileges (any user to local
-system) due to an improper authorization of the callers. The vulnerability affected the Windows 10 and Windows Server
-Core products. Fixed by Microsoft on Patch Tuesday June 2020.
 
-This rule will detect uncommon processes spawned by `svchost.exe` with `UsoSvc` as the command line parameters.
-Attackers can leverage this technique to elevate privileges or maintain persistence.
+*Investigating Persistence via Update Orchestrator Service Hijack*
+
+
+Windows Update Orchestrator Service is a DCOM service used by other components to install Windows updates that are already downloaded. Windows Update Orchestrator Service was vulnerable to elevation of privileges (any user to local system) due to an improper authorization of the callers. The vulnerability affected the Windows 10 and Windows Server Core products. Fixed by Microsoft on Patch Tuesday June 2020.
+
+This rule will detect uncommon processes spawned by `svchost.exe` with `UsoSvc` as the command line parameters. Attackers can leverage this technique to elevate privileges or maintain persistence.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
 
 
-### False positive analysis
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -103,45 +105,52 @@ and any spawned child processes.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.executable :
-"C:\\Windows\\System32\\svchost.exe" and process.parent.args :
-"UsoSvc" and not process.executable : ("?:\\ProgramData\\M
-icrosoft\\Windows\\UUS\\Packages\\*\\amd64\\MoUsoCoreWorker.exe",
-"?:\\Windows\\System32\\UsoClient.exe",
-"?:\\Windows\\System32\\MusNotification.exe",
-"?:\\Windows\\System32\\MusNotificationUx.exe",
-"?:\\Windows\\System32\\MusNotifyIcon.exe",
-"?:\\Windows\\System32\\WerFault.exe",
-"?:\\Windows\\System32\\WerMgr.exe",
-"?:\\Windows\\UUS\\amd64\\MoUsoCoreWorker.exe",
-"?:\\Windows\\System32\\MoUsoCoreWorker.exe",
-"?:\\Windows\\UUS\\amd64\\UsoCoreWorker.exe",
-"?:\\Windows\\System32\\UsoCoreWorker.exe", "?:\\Program
-Files\\Common Files\\microsoft
-shared\\ClickToRun\\OfficeC2RClient.exe") and not process.name :
-("MoUsoCoreWorker.exe", "OfficeC2RClient.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.executable : "C:\\Windows\\System32\\svchost.exe" and
+  process.parent.args : "UsoSvc" and
+  not process.executable :
+          ("?:\\ProgramData\\Microsoft\\Windows\\UUS\\Packages\\*\\amd64\\MoUsoCoreWorker.exe",
+          "?:\\Windows\\System32\\UsoClient.exe",
+          "?:\\Windows\\System32\\MusNotification.exe",
+          "?:\\Windows\\System32\\MusNotificationUx.exe",
+          "?:\\Windows\\System32\\MusNotifyIcon.exe",
+          "?:\\Windows\\System32\\WerFault.exe",
+          "?:\\Windows\\System32\\WerMgr.exe",
+          "?:\\Windows\\UUS\\amd64\\MoUsoCoreWorker.exe",
+          "?:\\Windows\\System32\\MoUsoCoreWorker.exe",
+          "?:\\Windows\\UUS\\amd64\\UsoCoreWorker.exe",
+          "?:\\Windows\\System32\\UsoCoreWorker.exe",
+          "?:\\Program Files\\Common Files\\microsoft shared\\ClickToRun\\OfficeC2RClient.exe") and
+  not process.name : ("MoUsoCoreWorker.exe", "OfficeC2RClient.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -153,70 +162,19 @@ shared\\ClickToRun\\OfficeC2RClient.exe") and not process.name :
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[persistence-via-update-orchestrator-service-hijack-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.parent.executable :
-"C:\\Windows\\System32\\svchost.exe" and process.parent.args :
-"UsoSvc" and not process.executable : ("?:\\ProgramData\\M
-icrosoft\\Windows\\UUS\\Packages\\*\\amd64\\MoUsoCoreWorker.exe",
-"?:\\Windows\\System32\\UsoClient.exe",
-"?:\\Windows\\System32\\MusNotification.exe",
-"?:\\Windows\\System32\\MusNotificationUx.exe",
-"?:\\Windows\\System32\\MusNotifyIcon.exe",
-"?:\\Windows\\System32\\WerFault.exe",
-"?:\\Windows\\System32\\WerMgr.exe",
-"?:\\Windows\\UUS\\amd64\\MoUsoCoreWorker.exe",
-"?:\\Windows\\System32\\MoUsoCoreWorker.exe",
-"?:\\Windows\\UUS\\amd64\\UsoCoreWorker.exe",
-"?:\\Windows\\System32\\UsoCoreWorker.exe", "?:\\Program
-Files\\Common Files\\microsoft
-shared\\ClickToRun\\OfficeC2RClient.exe")
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.parent.executable :
-"C:\\Windows\\System32\\svchost.exe" and process.parent.args :
-"UsoSvc" and not process.executable : (
-"C:\\Windows\\System32\\UsoClient.exe",
-"C:\\Windows\\System32\\MusNotification.exe",
-"C:\\Windows\\System32\\MusNotificationUx.exe",
-"C:\\Windows\\System32\\MusNotifyIcon.exe",
-"C:\\Windows\\System32\\WerFault.exe",
-"C:\\Windows\\System32\\WerMgr.exe" )
-----------------------------------
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:svchost.exe and process.parent.args:(UsoSvc or
-usosvc) and not process.name:(UsoClient.exe or usoclient.exe or
-MusNotification.exe or musnotification.exe or MusNotificationUx.exe or
-musnotificationux.exe)
-----------------------------------
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-wmi-event-subscription.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-wmi-event-subscription.asciidoc
index e6bd47162e..b2700c47be 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-wmi-event-subscription.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-wmi-event-subscription.asciidoc
@@ -5,65 +5,72 @@ An adversary can use Windows Management Instrumentation (WMI) to install event f
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/security-labs/hunting-for-persistence-using-elastic-security-part-1
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 102 (<<persistence-via-wmi-event-subscription-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name : "wmic.exe"
-or process.pe.original_file_name == "wmic.exe") and process.args :
-"create" and process.args : ("ActiveScriptEventConsumer",
-"CommandLineEventConsumer")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "wmic.exe" or ?process.pe.original_file_name == "wmic.exe") and
+  process.args : "create" and
+  process.args : ("ActiveScriptEventConsumer", "CommandLineEventConsumer")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,44 +82,15 @@ or process.pe.original_file_name == "wmic.exe") and process.args :
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[persistence-via-wmi-event-subscription-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "wmic.exe" or process.pe.original_file_name ==
-"wmic.exe") and process.args : "create" and process.args :
-("ActiveScriptEventConsumer", "CommandLineEventConsumer")
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "wmic.exe" or process.pe.original_file_name ==
-"wmic.exe") and process.args : "create" and process.args :
-("ActiveScriptEventConsumer", "CommandLineEventConsumer")
-----------------------------------
-
+* Sub-technique:
+** Name: Windows Management Instrumentation Event Subscription
+** ID: T1546.003
+** Reference URL: https://attack.mitre.org/techniques/T1546/003/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Windows Management Instrumentation
+** ID: T1047
+** Reference URL: https://attack.mitre.org/techniques/T1047/
diff --git a/docs/detections/prebuilt-rules/rule-details/persistence-via-wmi-standard-registry-provider.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistence-via-wmi-standard-registry-provider.asciidoc
index 41661c5db7..e9932c8a9c 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistence-via-wmi-standard-registry-provider.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistence-via-wmi-standard-registry-provider.asciidoc
@@ -5,89 +5,169 @@ Identifies use of the Windows Management Instrumentation StdRegProv (registry pr
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/previous-versions/windows/desktop/regprov/stdregprov
 * https://www.elastic.co/security-labs/hunting-for-persistence-using-elastic-security-part-1
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
 
-*Version*: 101 (<<persistence-via-wmi-standard-registry-provider-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.13.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Triage and analysis*
+
+
+
+*Investigating Persistence via WMI Standard Registry Provider*
+
+
+The Windows Management Instrumentation (WMI) StdRegProv is a registry provider that allows users to manage registry keys and values on Windows systems. Adversaries may abuse this functionality to modify registry locations commonly used for persistence, enabling them to maintain unauthorized access to a system.
+
+This rule identifies instances where the WMI StdRegProv is used to modify specific registry paths associated with persistence mechanisms.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate if the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Identify which process triggered this behavior.
+- Verify whether the file specified in the run key is signed.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Examine the file specified in the run key using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.data.strings != null and process.name :
-"WmiPrvSe.exe" and registry.path : (
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKLM\\Software\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Run\
-\*", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\C
-urrentVersion\\Policies\\Explorer\\Run\\*", "HKLM\\S
-oftware\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\
-*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\*",
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\
-\*", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\C
-urrentVersion\\RunOnceEx\\*",
-"HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\ServiceDLL",
-"HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\ImagePath",
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell\\*",
-"HKEY_USERS\\*\\Environment\\UserInitMprLogonScript",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\Load",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell", "HKEY_USERS\\*
-\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Shel
-l", "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\W
-indows\\System\\Scripts\\Logoff\\Script", "HKEY_USER
-S\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logon\\
-Script", "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microso
-ft\\Windows\\System\\Scripts\\Shutdown\\Script", "HK
-EY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\
-Startup\\Script",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Ctf\\LangBarAddin\\*\\FilePath",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet
-Explorer\\Extensions\\*\\Exec",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet
-Explorer\\Extensions\\*\\Script",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Command Processor\\Autorun"
-)
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and
+ registry.data.strings != null and process.name : "WmiPrvSe.exe" and
+ registry.path : (
+                  "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Command Processor\\Autorun",
+                  "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
+                  "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
+                  "HKLM\\Software\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
+                  "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\*",
+                  "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\*",
+                  "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\\*",
+                  "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\*",
+                  "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\\*",
+                  "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\*",
+                  "HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\ServiceDLL",
+                  "HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\ImagePath",
+                  "HKEY_USERS\\*\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Shell\\*",
+                  "HKEY_USERS\\*\\Environment\\UserInitMprLogonScript",
+                  "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Windows\\Load",
+                  "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Shell",
+                  "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Shell",
+                  "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logoff\\Script",
+                  "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logon\\Script",
+                  "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Shutdown\\Script",
+                  "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Startup\\Script",
+                  "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Ctf\\LangBarAddin\\*\\FilePath",
+                  "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Exec",
+                  "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Script",
+                  "\\REGISTRY\\USER\\*\\SOFTWARE\\Microsoft\\Command Processor\\Autorun",
+                  "\\REGISTRY\\USER\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
+                  "\\REGISTRY\\MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
+                  "\\REGISTRY\\MACHINE\\Software\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
+                  "\\REGISTRY\\USER\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\*",
+                  "\\REGISTRY\\MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\*",
+                  "\\REGISTRY\\MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\\*",
+                  "\\REGISTRY\\MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\*",
+                  "\\REGISTRY\\USER\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\\*",
+                  "\\REGISTRY\\USER\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\*",
+                  "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\*\\ServiceDLL",
+                  "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\*\\ImagePath",
+                  "\\REGISTRY\\USER\\*\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Shell\\*",
+                  "\\REGISTRY\\USER\\*\\Environment\\UserInitMprLogonScript",
+                  "\\REGISTRY\\USER\\*\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Windows\\Load",
+                  "\\REGISTRY\\USER\\*\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Shell",
+                  "\\REGISTRY\\USER\\*\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Shell",
+                  "\\REGISTRY\\USER\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logoff\\Script",
+                  "\\REGISTRY\\USER\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logon\\Script",
+                  "\\REGISTRY\\USER\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Shutdown\\Script",
+                  "\\REGISTRY\\USER\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Startup\\Script",
+                  "\\REGISTRY\\USER\\*\\SOFTWARE\\Microsoft\\Ctf\\LangBarAddin\\*\\FilePath",
+                  "\\REGISTRY\\USER\\*\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Exec",
+                  "\\REGISTRY\\USER\\*\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Script"
+                  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -96,11 +176,21 @@ Explorer\\Extensions\\*\\Script",
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
 * Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
+* Technique:
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-
+* Sub-technique:
+** Name: Registry Run Keys / Startup Folder
+** ID: T1547.001
+** Reference URL: https://attack.mitre.org/techniques/T1547/001/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -109,61 +199,3 @@ Explorer\\Extensions\\*\\Script",
 ** Name: Windows Management Instrumentation
 ** ID: T1047
 ** Reference URL: https://attack.mitre.org/techniques/T1047/
-
-[[persistence-via-wmi-standard-registry-provider-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.data.strings != null and process.name :
-"WmiPrvSe.exe" and registry.path : (
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKLM\\Software\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Run\
-\*", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\C
-urrentVersion\\Policies\\Explorer\\Run\\*", "HKLM\\S
-oftware\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\
-*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\*",
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\
-\*", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\C
-urrentVersion\\RunOnceEx\\*",
-"HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\ServiceDLL",
-"HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\ImagePath",
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell\\*",
-"HKEY_USERS\\*\\Environment\\UserInitMprLogonScript",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\Load",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell", "HKEY_USERS\\
-*\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\She
-ll", "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\
-\Windows\\System\\Scripts\\Logoff\\Script", "HKEY_U
-SERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logo
-n\\Script", "HKEY_USERS\\*\\SOFTWARE\\Policies\\Mic
-rosoft\\Windows\\System\\Scripts\\Shutdown\\Script",
-"HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Script
-s\\Startup\\Script",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Ctf\\LangBarAddin\\*\\FilePath",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet
-Explorer\\Extensions\\*\\Exec",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet
-Explorer\\Extensions\\*\\Script",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Command Processor\\Autorun"
-)
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/persistent-scripts-in-the-startup-directory.asciidoc b/docs/detections/prebuilt-rules/rule-details/persistent-scripts-in-the-startup-directory.asciidoc
index 6c84e1de2b..2b08db1698 100644
--- a/docs/detections/prebuilt-rules/rule-details/persistent-scripts-in-the-startup-directory.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/persistent-scripts-in-the-startup-directory.asciidoc
@@ -5,93 +5,102 @@ Identifies script engines creating files in the Startup folder, or the creation
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<persistent-scripts-in-the-startup-directory-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Persistent Scripts in the Startup Directory
+*Triage and analysis*
+
+
 
-The Windows Startup folder is a special folder in Windows. Programs added to this folder are executed during account
-logon, without user interaction, providing an excellent way for attackers to maintain persistence.
+*Investigating Persistent Scripts in the Startup Directory*
+
+
+The Windows Startup folder is a special folder in Windows. Programs added to this folder are executed during account logon, without user interaction, providing an excellent way for attackers to maintain persistence.
 
 This rule looks for shortcuts created by wscript.exe or cscript.exe, or js/vbs scripts created by any process.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate
-software installations.
+- Validate if the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Related rules
+
+*Related rules*
+
 
 - Suspicious Startup Shell Folder Modification - c8b150f0-0164-475b-a75e-74b47800a9ff
 - Startup Folder Persistence via Unsigned Process - 2fba96c0-ade5-4bce-b92f-a5df2509da3f
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -99,85 +108,66 @@ software installations.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
-==== Rule query
+==== Setup
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and user.domain != "NT AUTHORITY"
-and /* detect shortcuts created by wscript.exe or cscript.exe */
-(file.path : "C:\\*\\Programs\\Startup\\*.lnk" and process.name :
-("wscript.exe", "cscript.exe")) or /* detect vbs or js files
-created by any process */ file.path :
-("C:\\*\\Programs\\Startup\\*.vbs",
-"C:\\*\\Programs\\Startup\\*.vbe",
-"C:\\*\\Programs\\Startup\\*.wsh",
-"C:\\*\\Programs\\Startup\\*.wsf",
-"C:\\*\\Programs\\Startup\\*.js")
-----------------------------------
 
-==== Threat mapping
+*Setup*
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Persistence
-** ID: TA0003
-** Reference URL: https://attack.mitre.org/tactics/TA0003/
-* Technique:
-** Name: Boot or Logon Autostart Execution
-** ID: T1547
-** Reference URL: https://attack.mitre.org/techniques/T1547/
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
-[[persistent-scripts-in-the-startup-directory-history]]
-==== Rule version history
 
-Version 102 (8.6.0 release)::
-* Formatting only
+==== Rule query
 
-Version 101 (8.5.0 release)::
-* Formatting only
 
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-file where event.type != "deletion" and user.domain != "NT AUTHORITY"
-and /* detect shortcuts created by wscript.exe or cscript.exe */
-(file.path : "C:\\*\\Programs\\Startup\\*.lnk" and process.name :
-("wscript.exe", "cscript.exe")) or /* detect vbs or js files
-created by any process */ file.path :
-("C:\\*\\Programs\\Startup\\*.vbs",
-"C:\\*\\Programs\\Startup\\*.vbe",
-"C:\\*\\Programs\\Startup\\*.wsh",
-"C:\\*\\Programs\\Startup\\*.wsf",
-"C:\\*\\Programs\\Startup\\*.js")
-----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and
 
-Version 5 (8.3.0 release)::
-* Formatting only
+  file.extension : ("lnk", "vbs", "vbe", "wsh", "wsf", "js") and
+  not (startsWith(user.domain, "NT") or endsWith(user.domain, "NT")) and
 
-Version 4 (8.2.0 release)::
-* Formatting only
+  /* detect shortcuts created by wscript.exe or cscript.exe */
+  (file.path : "C:\\*\\Programs\\Startup\\*.lnk" and
+     process.name : ("wscript.exe", "cscript.exe")) or
 
-Version 3 (7.12.0 release)::
-* Formatting only
+  /* detect vbs or js files created by any process */
+  file.path : ("C:\\*\\Programs\\Startup\\*.vbs",
+               "C:\\*\\Programs\\Startup\\*.vbe",
+               "C:\\*\\Programs\\Startup\\*.wsh",
+               "C:\\*\\Programs\\Startup\\*.wsf",
+               "C:\\*\\Programs\\Startup\\*.js")
 
-Version 2 (7.11.2 release)::
-* Formatting only
+----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Sub-technique:
+** Name: Registry Run Keys / Startup Folder
+** ID: T1547.001
+** Reference URL: https://attack.mitre.org/techniques/T1547/001/
+* Sub-technique:
+** Name: Shortcut Modification
+** ID: T1547.009
+** Reference URL: https://attack.mitre.org/techniques/T1547/009/
diff --git a/docs/detections/prebuilt-rules/rule-details/port-forwarding-rule-addition.asciidoc b/docs/detections/prebuilt-rules/rule-details/port-forwarding-rule-addition.asciidoc
index 0f9082eb50..162c846cbc 100644
--- a/docs/detections/prebuilt-rules/rule-details/port-forwarding-rule-addition.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/port-forwarding-rule-addition.asciidoc
@@ -5,84 +5,87 @@ Identifies the creation of a new port forwarding rule. An adversary may abuse th
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.fireeye.com/blog/threat-research/2019/01/bypassing-network-restrictions-through-rdp-tunneling.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<port-forwarding-rule-addition-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Port Forwarding Rule Addition
+*Triage and analysis*
+
 
-Network port forwarding is a mechanism to redirect incoming TCP connections (IPv4 or IPv6) from the local TCP port to
-any other port number, or even to a port on a remote computer.
 
-Attackers may configure port forwarding rules to bypass network segmentation restrictions, using the host as a jump box
-to access previously unreachable systems.
+*Investigating Port Forwarding Rule Addition*
+
+
+Network port forwarding is a mechanism to redirect incoming TCP connections (IPv4 or IPv6) from the local TCP port to any other port number, or even to a port on a remote computer.
+
+Attackers may configure port forwarding rules to bypass network segmentation restrictions, using the host as a jump box to access previously unreachable systems.
 
 This rule monitors the modifications to the `HKLM\SYSTEM\*ControlSet*\Services\PortProxy\v4tov4\` subkeys.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account and system owners and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Identify the target host IP address, check the connections originating from the host where the modification occurred,
-and inspect the credentials used.
+- Identify the target host IP address, check the connections originating from the host where the modification occurred, and inspect the credentials used.
   - Investigate suspicious login activity, such as unauthorized access and logins from outside working hours and unusual locations.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Analysts can dismiss the alert if the Administrator is aware of the activity
-and there are justifications for this configuration.
-- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination
-of user and command line conditions.
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the Administrator is aware of the activity and there are justifications for this configuration.
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Delete the port forwarding rule.
@@ -91,32 +94,39 @@ of user and command line conditions.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
-registry where registry.path : (
-"HKLM\\SYSTEM\\*ControlSet*\\Services\\PortProxy\\v4tov4\\*", "\\REG
-ISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\PortProxy\\v4tov4\\*"
+registry where host.os.type == "windows" and registry.path : (
+  "HKLM\\SYSTEM\\*ControlSet*\\Services\\PortProxy\\v4tov4\\*",
+  "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\PortProxy\\v4tov4\\*"
 )
-----------------------------------
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -128,46 +138,11 @@ ISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\PortProxy\\v4tov4\\*"
 ** Name: Protocol Tunneling
 ** ID: T1572
 ** Reference URL: https://attack.mitre.org/techniques/T1572/
-
-[[port-forwarding-rule-addition-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path :
-"HKLM\\SYSTEM\\*ControlSet*\\Services\\PortProxy\\v4tov4\\*"
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.3.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path :
-"HKLM\\SYSTEM\\ControlSet*\\Services\\PortProxy\\v4tov4\\*"
-----------------------------------
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/possible-consent-grant-attack-via-azure-registered-application.asciidoc b/docs/detections/prebuilt-rules/rule-details/possible-consent-grant-attack-via-azure-registered-application.asciidoc
index 445da42ba8..18ca9823e1 100644
--- a/docs/detections/prebuilt-rules/rule-details/possible-consent-grant-attack-via-azure-registered-application.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/possible-consent-grant-attack-via-azure-registered-application.asciidoc
@@ -5,67 +5,64 @@ Detects when a user grants permissions to an Azure-registered application or whe
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
+* logs-o365*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/detect-and-remediate-illicit-consent-grants?view=o365-worldwide
 * https://www.cloud-architekt.net/detection-and-mitigation-consent-grant-attacks-azuread/
 * https://docs.microsoft.com/en-us/defender-cloud-apps/investigate-risky-oauth#how-to-detect-risky-oauth-apps
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-* Investigation Guide
-
-*Version*: 103 (<<possible-consent-grant-attack-via-azure-registered-application-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Data Source: Microsoft 365
+* Use Case: Identity and Access Audit
+* Resources: Investigation Guide
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 212
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Possible Consent Grant Attack via Azure-Registered Application
+*Triage and analysis*
+
+
+
+*Investigating Possible Consent Grant Attack via Azure-Registered Application*
+
+
+In an illicit consent grant attack, the attacker creates an Azure-registered application that requests access to data such as contact information, email, or documents. The attacker then tricks an end user into granting that application consent to access their data either through a phishing attack, or by injecting illicit code into a trusted website. After the illicit application has been granted consent, it has account-level access to data without the need for an organizational account. Normal remediation steps like resetting passwords for breached accounts or requiring multi-factor authentication (MFA) on accounts are not effective against this type of attack, since these are third-party applications and are external to the organization.
 
-In an illicit consent grant attack, the attacker creates an Azure-registered application that requests access to data
-such as contact information, email, or documents. The attacker then tricks an end user into granting that application
-consent to access their data either through a phishing attack, or by injecting illicit code into a trusted website.
-After the illicit application has been granted consent, it has account-level access to data without the need for an
-organizational account. Normal remediation steps like resetting passwords for breached accounts or requiring multi-factor
-authentication (MFA) on accounts are not effective against this type of attack, since these are third-party applications
-and are external to the organization.
+Official Microsoft guidance for detecting and remediating this attack can be found https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/detect-and-remediate-illicit-consent-grants[here].
 
-Official Microsoft guidance for detecting and remediating this attack can be found [here](https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/detect-and-remediate-illicit-consent-grants).
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - From the Azure AD portal, Review the application that was granted permissions:
   - Click on the `Review permissions` button on the `Permissions` blade of the application.
@@ -76,14 +73,17 @@ Official Microsoft guidance for detecting and remediating this attack can be fou
   -  Low rating or score or bad comments.
   -  Apps with a suspicious publisher or website.
   -  Apps whose last update is not recent. This might indicate an app that is no longer supported.
-- Export and examine the [Oauth app auditing](https://docs.microsoft.com/en-us/defender-cloud-apps/manage-app-permissions#oauth-app-auditing) to identify users affected.
+- Export and examine the https://docs.microsoft.com/en-us/defender-cloud-apps/manage-app-permissions#oauth-app-auditing[Oauth app auditing] to identify users affected.
+
+
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Malicious applications abuse the same workflow used by legitimate apps. Thus, analysts must review each app consent to ensure that only desired apps are granted access.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Malicious applications abuse the same workflow used by legitimate apps.
-Thus, analysts must review each app consent to ensure that only desired apps are granted access.
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Identify the possible impact of the incident and prioritize accordingly; the following actions can help you gain context:
@@ -93,37 +93,35 @@ Thus, analysts must review each app consent to ensure that only desired apps are
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
 - Disable the malicious application to stop user access and the application access to your data.
-- Revoke the application Oauth consent grant. The `Remove-AzureADOAuth2PermissionGrant` cmdlet can be used to complete
-this task.
-- Remove the service principal application role assignment. The `Remove-AzureADServiceAppRoleAssignment` cmdlet can be
-used to complete this task.
-- Revoke the refresh token for all users assigned to the application. Azure provides a [playbook](https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks/Revoke-AADSignInSessions) for this task.
-- [Report](https://docs.microsoft.com/en-us/defender-cloud-apps/manage-app-permissions#send-feedback) the application as malicious to Microsoft.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
-- Investigate the potential for data compromise from the user's email and file sharing services. Activate your Data Loss
-incident response playbook.
+- Revoke the application Oauth consent grant. The `Remove-AzureADOAuth2PermissionGrant` cmdlet can be used to complete this task.
+- Remove the service principal application role assignment. The `Remove-AzureADServiceAppRoleAssignment` cmdlet can be used to complete this task.
+- Revoke the refresh token for all users assigned to the application. Azure provides a https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks/Revoke-AADSignInSessions[playbook] for this task.
+- https://docs.microsoft.com/en-us/defender-cloud-apps/manage-app-permissions#send-feedback[Report] the application as malicious to Microsoft.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
+- Investigate the potential for data compromise from the user's email and file sharing services. Activate your Data Loss incident response playbook.
 - Disable the permission for a user to set consent permission on their behalf.
-  - Enable the [Admin consent request](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-admin-consent-workflow) feature.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+  - Enable the https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-admin-consent-workflow[Admin consent request] feature.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:(azure.activitylogs or azure.auditlogs or o365.audit)
-and ( azure.activitylogs.operation_name:"Consent to application"
-or azure.auditlogs.operation_name:"Consent to application" or
-o365.audit.Operation:"Consent to application." ) and
-event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:(azure.activitylogs or azure.auditlogs or o365.audit) and
+  (
+    azure.activitylogs.operation_name:"Consent to application" or
+    azure.auditlogs.operation_name:"Consent to application" or
+    o365.audit.Operation:"Consent to application."
+  ) and
+  event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -135,8 +133,10 @@ event.outcome:(Success or success)
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
 * Tactic:
 ** Name: Credential Access
 ** ID: TA0006
@@ -145,45 +145,3 @@ event.outcome:(Success or success)
 ** Name: Steal Application Access Token
 ** ID: T1528
 ** Reference URL: https://attack.mitre.org/techniques/T1528/
-
-[[possible-consent-grant-attack-via-azure-registered-application-history]]
-==== Rule version history
-
-Version 103 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(azure.activitylogs or azure.auditlogs or o365.audit)
-and ( azure.activitylogs.operation_name:"Consent to
-application" or azure.auditlogs.operation_name:"Consent to
-application" or o365.audit.Operation:"Consent to application." )
-and event.outcome:(Success or success)
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:(azure.activitylogs or azure.auditlogs) and (
-azure.activitylogs.operation_name:"Consent to application" or
-azure.auditlogs.operation_name:"Consent to application" ) and
-event.outcome:success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/possible-fin7-dga-command-and-control-behavior.asciidoc b/docs/detections/prebuilt-rules/rule-details/possible-fin7-dga-command-and-control-behavior.asciidoc
index c3162ec5f3..e38c6b50c9 100644
--- a/docs/detections/prebuilt-rules/rule-details/possible-fin7-dga-command-and-control-behavior.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/possible-fin7-dga-command-and-control-behavior.asciidoc
@@ -5,72 +5,61 @@ This rule detects a known command and control pattern in network events. The FIN
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.fireeye.com/blog/threat-research/2018/08/fin7-pursuing-an-enigmatic-and-evasive-global-criminal-operation.html
 
-*Tags*:
-
-* Elastic
-* Network
-* Threat Detection
-* Command and Control
-* Host
+*Tags*: 
 
-*Version*: 100 (<<possible-fin7-dga-command-and-control-behavior-history, version history>>)
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Domain: Endpoint
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-This rule could identify benign domains that are formatted similarly to FIN7's command and control algorithm. Alerts should be investigated by an analyst to assess the validity of the individual observations.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-In the event this rule identifies benign domains in your environment, the `destination.domain` field in the rule can be modified to include those domains. Example: `...AND NOT destination.domain:(zoom.us OR benign.domain1 OR benign.domain2)`.
-----------------------------------
+*Triage and analysis*
+
 
+In the event this rule identifies benign domains in your environment, the `destination.domain` field in the rule can be modified to include those domains. Example: `...AND NOT destination.domain:(zoom.us OR benign.domain1 OR benign.domain2)`.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network OR network_traffic) AND type:(tls OR http) AND
-network.transport:tcp AND
-destination.domain:/[a-zA-Z]{4,5}\.(pw|us|club|info|site|top)/ AND NOT
-destination.domain:zoom.us
+[source, js]
 ----------------------------------
+(event.dataset: (network_traffic.tls OR network_traffic.http) OR
+    (event.category: (network OR network_traffic) AND type: (tls OR http) AND network.transport: tcp)) AND
+destination.domain:/[a-zA-Z]{4,5}\.(pw|us|club|info|site|top)/ AND NOT destination.domain:zoom.us
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -82,33 +71,11 @@ destination.domain:zoom.us
 ** Name: Application Layer Protocol
 ** ID: T1071
 ** Reference URL: https://attack.mitre.org/techniques/T1071/
-
-[[possible-fin7-dga-command-and-control-behavior-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network OR network_traffic) AND type:(tls OR http) AND
-network.transport:tcp AND
-destination.domain:/[a-zA-Z]{4,5}\.(pw|us|club|info|site|top)/ AND NOT
-destination.domain:zoom.us
-----------------------------------
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Technique:
+** Name: Dynamic Resolution
+** ID: T1568
+** Reference URL: https://attack.mitre.org/techniques/T1568/
+* Sub-technique:
+** Name: Domain Generation Algorithms
+** ID: T1568.002
+** Reference URL: https://attack.mitre.org/techniques/T1568/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/possible-okta-dos-attack.asciidoc b/docs/detections/prebuilt-rules/rule-details/possible-okta-dos-attack.asciidoc
index efd781a0b9..4cb0493b75 100644
--- a/docs/detections/prebuilt-rules/rule-details/possible-okta-dos-attack.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/possible-okta-dos-attack.asciidoc
@@ -5,7 +5,7 @@ Detects possible Denial of Service (DoS) attacks against an Okta organization. A
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,58 +14,51 @@ Detects possible Denial of Service (DoS) attacks against an Okta organization. A
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 102 (<<possible-okta-dos-attack-history, version history>>)
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Impact
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 205
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and
-event.action:(application.integration.rate_limit_exceeded or
-system.org.rate_limit.warning or system.org.rate_limit.violation or
-core.concurrency.org.limit.violation)
+[source, js]
 ----------------------------------
+event.dataset:okta.system and event.action:(application.integration.rate_limit_exceeded or system.org.rate_limit.warning or system.org.rate_limit.violation or core.concurrency.org.limit.violation)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,39 +70,7 @@ core.concurrency.org.limit.violation)
 ** Name: Network Denial of Service
 ** ID: T1498
 ** Reference URL: https://attack.mitre.org/techniques/T1498/
-
-[[possible-okta-dos-attack-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:(application.integration.rate_limit_exceeded or
-system.org.rate_limit.warning or system.org.rate_limit.violation or
-core.concurrency.org.limit.violation)
-----------------------------------
-
+* Technique:
+** Name: Endpoint Denial of Service
+** ID: T1499
+** Reference URL: https://attack.mitre.org/techniques/T1499/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-abuse-of-resources-by-high-token-count-and-large-response-sizes.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-abuse-of-resources-by-high-token-count-and-large-response-sizes.asciidoc
new file mode 100644
index 0000000000..83089d7c67
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-abuse-of-resources-by-high-token-count-and-large-response-sizes.asciidoc
@@ -0,0 +1,73 @@
+[[potential-abuse-of-resources-by-high-token-count-and-large-response-sizes]]
+=== Potential Abuse of Resources by High Token Count and Large Response Sizes
+
+Detects potential resource exhaustion or data breach attempts by monitoring for users who consistently generate high input token counts, submit numerous requests, and receive large responses. This behavior could indicate an attempt to overload the system or extract an unusually large amount of data, possibly revealing sensitive information or causing service disruptions.
+
+*Rule type*: esql
+
+*Rule indices*: None
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://atlas.mitre.org/techniques/AML.T0051
+* https://owasp.org/www-project-top-10-for-large-language-model-applications/
+* https://www.elastic.co/security-labs/elastic-advances-llm-security
+
+*Tags*: 
+
+* Domain: LLM
+* Data Source: AWS Bedrock
+* Data Source: Amazon Web Services
+* Data Source: AWS S3
+* Use Case: Potential Overload
+* Use Case: Resource Exhaustion
+* Mitre Atlas: LLM04
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires that guardrails are configured in AWS Bedrock. For more information, see the AWS Bedrock documentation:
+
+https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-create.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+from logs-aws_bedrock.invocation-*
+| stats max_tokens = max(gen_ai.usage.prompt_tokens),
+         total_requests = count(*),
+         avg_response_size = avg(gen_ai.usage.completion_tokens)
+  by user.id
+// tokens count depends on specific LLM, as is related to how embeddings are generated.
+| where max_tokens > 5000 and total_requests > 10 and avg_response_size > 500
+| eval risk_factor = (max_tokens / 1000) * total_requests * (avg_response_size / 500)
+| where risk_factor > 10
+| sort risk_factor desc
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-adidns-poisoning-via-wildcard-record-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-adidns-poisoning-via-wildcard-record-creation.asciidoc
new file mode 100644
index 0000000000..895e2a8e17
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-adidns-poisoning-via-wildcard-record-creation.asciidoc
@@ -0,0 +1,94 @@
+[[potential-adidns-poisoning-via-wildcard-record-creation]]
+=== Potential ADIDNS Poisoning via Wildcard Record Creation
+
+Active Directory Integrated DNS (ADIDNS) is one of the core components of AD DS, leveraging AD's access control and replication to maintain domain consistency. It stores DNS zones as AD objects, a feature that, while robust, introduces some security issues, such as wildcard records, mainly because of the default permission (Any authenticated users) to create DNS-named records. Attackers can create wildcard records to redirect traffic that doesn't explicitly match records contained in the zone, becoming the Man-in-the-Middle and being able to abuse DNS similarly to LLMNR/NBNS spoofing.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-system.*
+* logs-windows.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.netspi.com/blog/technical/network-penetration-testing/exploiting-adidns/
+* https://www.thehacker.recipes/a-d/movement/mitm-and-coerced-authentications/adidns-spoofing
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Active Directory
+* Use Case: Active Directory Monitoring
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Directory Service Changes' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Changes (Success,Failure)
+```
+
+The above policy does not cover the target object by default (we still need it to be configured to generate events), so we need to set up an AuditRule using https://github.com/OTRF/Set-AuditRule.
+
+```
+Set-AuditRule -AdObjectPath 'AD:\CN=MicrosoftDNS,DC=DomainDNSZones,DC=Domain,DC=com' -WellKnownSidType WorldSid -Rights CreateChild -InheritanceFlags Descendents -AttributeGUID e0fa1e8c-9b45-11d0-afdd-00c04fd930c9 -AuditFlags Success
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+any where host.os.type == "windows" and event.action == "Directory Service Changes" and
+    event.code == "5137" and startsWith(winlog.event_data.ObjectDN, "DC=*,")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Adversary-in-the-Middle
+** ID: T1557
+** Reference URL: https://attack.mitre.org/techniques/T1557/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-admin-group-account-addition.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-admin-group-account-addition.asciidoc
index bf489abc23..026fe16b7d 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-admin-group-account-addition.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-admin-group-account-addition.asciidoc
@@ -5,54 +5,91 @@ Identifies attempts to add an account to the admin group via the command line. T
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://managingosx.wordpress.com/2010/01/14/add-a-user-to-the-admin-group-via-command-line-3-0/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Privilege Escalation
 
-*Version*: 100 (<<potential-admin-group-account-addition-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:(dscl or dseditgroup) and process.args:(("/Groups/admin"
-or admin) and ("-a" or "-append"))
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+ process.name:(dscl or dseditgroup) and process.args:(("/Groups/admin" or admin) and ("-a" or "-append")) and
+ not process.Ext.effective_parent.executable : ("/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfDaemon.app/Contents/MacOS/JamfDaemon" or
+                                                "/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfManagementService.app/Contents/MacOS/JamfManagementService" or
+                                                "/opt/jc/bin/jumpcloud-agent" or
+                                                "/Library/Addigy/go-agent")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,13 +101,7 @@ or admin) and ("-a" or "-append"))
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[potential-admin-group-account-addition-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Local Accounts
+** ID: T1078.003
+** Reference URL: https://attack.mitre.org/techniques/T1078/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-antimalware-scan-interface-bypass-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-antimalware-scan-interface-bypass-via-powershell.asciidoc
new file mode 100644
index 0000000000..5b490ba1a8
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-antimalware-scan-interface-bypass-via-powershell.asciidoc
@@ -0,0 +1,167 @@
+[[potential-antimalware-scan-interface-bypass-via-powershell]]
+=== Potential Antimalware Scan Interface Bypass via PowerShell
+
+Identifies the execution of PowerShell script with keywords related to different Antimalware Scan Interface (AMSI) bypasses. An adversary may attempt first to disable AMSI before executing further malicious powershell scripts to evade detection.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/S3cur3Th1sSh1t/Amsi-Bypass-Powershell
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: PowerShell Logs
+* Resources: Investigation Guide
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Antimalware Scan Interface Bypass via PowerShell*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+The Windows Antimalware Scan Interface (AMSI) is a versatile interface standard that allows your applications and services to integrate with any antimalware product on a machine. AMSI integrates with multiple Windows components, ranging from User Account Control (UAC) to VBA macros and PowerShell.
+
+This rule identifies scripts that contain methods and classes that can be abused to bypass AMSI.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Determine whether the script was executed and capture relevant information, such as arguments that reveal intent or are indicators of compromise (IoCs).
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate commands and scripts executed after this activity was observed.
+- Inspect the host for suspicious or abnormal behavior in the alert timeframe:
+  - Observe and collect information about the following activities in the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:"process" and host.os.type:windows and
+  (
+    powershell.file.script_block_text : (
+      "System.Management.Automation.AmsiUtils" or
+			amsiInitFailed or 
+			"Invoke-AmsiBypass" or 
+			"Bypass.AMSI" or 
+			"amsi.dll" or 
+			AntimalwareProvider  or 
+			amsiSession or 
+			amsiContext or
+			AmsiInitialize or 
+			unloadobfuscated or 
+			unloadsilent or 
+			AmsiX64 or 
+			AmsiX32 or 
+			FindAmsiFun
+    ) or
+    powershell.file.script_block_text:("[System.Runtime.InteropServices.Marshal]::Copy" and "VirtualProtect") or
+    powershell.file.script_block_text:("[Ref].Assembly.GetType(('System.Management.Automation" and ".SetValue(")
+  ) and
+  not powershell.file.script_block_text : (
+    "sentinelbreakpoints" and "Set-PSBreakpoint"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-application-shimming-via-sdbinst.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-application-shimming-via-sdbinst.asciidoc
index da9eedb104..b56b22421f 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-application-shimming-via-sdbinst.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-application-shimming-via-sdbinst.asciidoc
@@ -5,60 +5,69 @@ The Application Shim was created to allow for backward compatibility of software
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 102 (<<potential-application-shimming-via-sdbinst-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "sdbinst.exe"
-and not (process.args : "-m" and process.args : "-bg") and not
-process.args : "-mm"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.name : "sdbinst.exe" and
+  process.args : "?*" and
+  not (process.args : "-m" and process.args : "-bg") and
+  not process.args : "-mm"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,8 +79,10 @@ process.args : "-mm"
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-
+* Sub-technique:
+** Name: Application Shimming
+** ID: T1546.011
+** Reference URL: https://attack.mitre.org/techniques/T1546/011/
 * Tactic:
 ** Name: Privilege Escalation
 ** ID: TA0004
@@ -80,62 +91,7 @@ process.args : "-mm"
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[potential-application-shimming-via-sdbinst-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.name : "sdbinst.exe"
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "sdbinst.exe"
-----------------------------------
-
-Version 11 (8.4.0 release)::
-* Formatting only
-
-Version 9 (8.2.0 release)::
-* Formatting only
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:sdbinst.exe
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.code:1 and process.name:sdbinst.exe
-----------------------------------
-
-Version 3 (7.9.0 release)::
-* Formatting only
-
-Version 2 (7.7.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Application Shimming
+** ID: T1546.011
+** Reference URL: https://attack.mitre.org/techniques/T1546/011/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-buffer-overflow-attack-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-buffer-overflow-attack-detected.asciidoc
new file mode 100644
index 0000000000..57af69941b
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-buffer-overflow-attack-detected.asciidoc
@@ -0,0 +1,86 @@
+[[potential-buffer-overflow-attack-detected]]
+=== Potential Buffer Overflow Attack Detected
+
+Detects potential buffer overflow attacks by querying the "Segfault Detected" pre-built rule signal index, through a threshold rule, with a minimum number of 100 segfault alerts in a short timespan. A large amount of segfaults in a short time interval could indicate application exploitation attempts.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* .alerts-security.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Initial Access
+* Use Case: Vulnerability
+* Rule Type: Higher-Order Rule
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule leverages alert data from other prebuilt detection rules to function correctly. 
+
+
+*Dependent Elastic Detection Rule Enablement*
+
+As a higher-order rule (based on other detections), this rule also requires the following prerequisite Elastic detection rule to be installed and enabled:
+- Segfault Detected (5c81fc9d-1eae-437f-ba07-268472967013)
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+kibana.alert.rule.rule_id:5c81fc9d-1eae-437f-ba07-268472967013 and event.kind:signal
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Exploit Public-Facing Application
+** ID: T1190
+** Reference URL: https://attack.mitre.org/techniques/T1190/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-chroot-container-escape-via-mount.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-chroot-container-escape-via-mount.asciidoc
new file mode 100644
index 0000000000..a87b06a1b3
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-chroot-container-escape-via-mount.asciidoc
@@ -0,0 +1,116 @@
+[[potential-chroot-container-escape-via-mount]]
+=== Potential Chroot Container Escape via Mount
+
+Monitors for the execution of a file system mount followed by a chroot execution. Given enough permissions, a user within a container is capable of mounting the root file system of the host, and leveraging chroot to escape its containarized environment. This behavior pattern is very uncommon and should be investigated.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://book.hacktricks.xyz/v/portugues-ht/linux-hardening/privilege-escalation/escaping-from-limited-bash
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Domain: Container
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+Session View uses process data collected by the Elastic Defend integration, but this data is not always collected by default. Session View is available on enterprise subscription for versions 8.3 and above.
+
+*To confirm that Session View data is enabled:*
+
+- Go to “Manage → Policies”, and edit one or more of your Elastic Defend integration policies.
+- Select the” Policy settings” tab, then scroll down to the “Linux event collection” section near the bottom.
+- Check the box for “Process events”, and turn on the “Include session data” toggle.
+- If you want to include file and network alerts in Session View, check the boxes for “Network and File events”.
+- If you want to enable terminal output capture, turn on the “Capture terminal output” toggle.
+For more information about the additional fields collected when this setting is enabled and the usage of Session View for Analysis refer to the https://www.elastic.co/guide/en/security/current/session-view.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.parent.entity_id with maxspan=5m
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+   process.name == "mount" and process.args : "/dev/sd*" and process.args_count >= 3 and
+   process.parent.name in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")]
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+   process.name == "chroot"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Escape to Host
+** ID: T1611
+** Reference URL: https://attack.mitre.org/techniques/T1611/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-code-execution-via-postgresql.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-code-execution-via-postgresql.asciidoc
new file mode 100644
index 0000000000..fa44cbb628
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-code-execution-via-postgresql.asciidoc
@@ -0,0 +1,106 @@
+[[potential-code-execution-via-postgresql]]
+=== Potential Code Execution via Postgresql
+
+This rule monitors for suspicious activities that may indicate an attacker attempting to execute arbitrary code within a PostgreSQL environment. Attackers can execute code via PostgreSQL as a result of gaining unauthorized access to a public facing PostgreSQL database or exploiting vulnerabilities, such as remote command execution and SQL injection attacks, which can result in unauthorized access and malicious actions, and facilitate post-exploitation activities for unauthorized access and malicious actions.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "fork", "fork_event") and 
+user.name == "postgres" and (
+  (process.parent.args : "*sh" and process.parent.args : "echo*") or 
+  (process.args : "*sh" and process.args : "echo*")
+) and not process.parent.name : "puppet"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-command-and-control-via-internet-explorer.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-command-and-control-via-internet-explorer.asciidoc
index bad4d1632f..6ca3880c66 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-command-and-control-via-internet-explorer.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-command-and-control-via-internet-explorer.asciidoc
@@ -5,64 +5,66 @@ Identifies instances of Internet Explorer (iexplore.exe) being started via the C
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.library-*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
+*Tags*: 
 
-*Version*: 100 (<<potential-command-and-control-via-internet-explorer-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Processes such as MS Office using IEproxy to render HTML content.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, user.name with maxspan = 5s [library where
-dll.name : "IEProxy.dll" and process.name : ("rundll32.exe",
-"regsvr32.exe")] [process where event.type == "start" and
-process.parent.name : "iexplore.exe" and process.parent.args :
-"-Embedding"] /* IE started via COM in normal conditions makes few
-connections, mainly to Microsoft and OCSP related domains, add FPs
-here */ [network where network.protocol == "dns" and process.name :
-"iexplore.exe" and not dns.question.name : (
-"*.microsoft.com", "*.digicert.com", "*.msocsp.com",
-"*.windowsupdate.com", "*.bing.com", "*.identrust.com",
-"*.sharepoint.com", "*.office365.com", "*.office.com" )
-] /* with runs=5 */
+[source, js]
 ----------------------------------
+sequence by host.id, user.name with maxspan = 5s
+  [library where host.os.type == "windows" and dll.name : "IEProxy.dll" and process.name : ("rundll32.exe", "regsvr32.exe")]
+  [process where host.os.type == "windows" and event.type == "start" and process.parent.name : "iexplore.exe" and process.parent.args : "-Embedding"]
+  /* IE started via COM in normal conditions makes few connections, mainly to Microsoft and OCSP related domains, add FPs here */
+  [network where host.os.type == "windows" and network.protocol == "dns" and process.name : "iexplore.exe" and
+   not dns.question.name :
+   (
+    "*.microsoft.com",
+    "*.digicert.com",
+    "*.msocsp.com",
+    "*.windowsupdate.com",
+    "*.bing.com",
+    "*.identrust.com",
+    "*.sharepoint.com",
+    "*.office365.com",
+    "*.office.com"
+    )
+  ] /* with runs=5 */
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,8 +76,6 @@ here */ [network where network.protocol == "dns" and process.name :
 ** Name: Application Layer Protocol
 ** ID: T1071
 ** Reference URL: https://attack.mitre.org/techniques/T1071/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -84,69 +84,7 @@ here */ [network where network.protocol == "dns" and process.name :
 ** Name: Inter-Process Communication
 ** ID: T1559
 ** Reference URL: https://attack.mitre.org/techniques/T1559/
-
-[[potential-command-and-control-via-internet-explorer-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, user.id with maxspan = 5s [library where
-dll.name : "IEProxy.dll" and process.name : ("rundll32.exe",
-"regsvr32.exe")] [process where event.type == "start" and
-process.parent.name : "iexplore.exe" and process.parent.args :
-"-Embedding"] /* IE started via COM in normal conditions makes few
-connections, mainly to Microsoft and OCSP related domains, add FPs
-here */ [network where network.protocol == "dns" and process.name :
-"iexplore.exe" and not dns.question.name : (
-"*.microsoft.com", "*.digicert.com", "*.msocsp.com",
-"*.windowsupdate.com", "*.bing.com", "*.identrust.com",
-"*.sharepoint.com", "*.office365.com", "*.office.com" )
-]
-----------------------------------
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan = 1s [process
-where event.type == "start" and process.parent.name : "iexplore.exe"
-and process.parent.args : "-Embedding"] /* IE started via COM in
-normal conditions makes few connections, mainly to Microsoft and OCSP
-related domains, add FPs here */ [network where network.protocol ==
-"dns" and process.name : "iexplore.exe" and not dns.question.name :
-( "*.microsoft.com", "*.digicert.com", "*.msocsp.com",
-"*.windowsupdate.com", "*.bing.com", "*.identrust.com" )
-]
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan = 1s [process
-where event.type:"start" and process.parent.name:"iexplore.exe" and
-process.parent.args:"-Embedding"] /* IE started via COM in normal
-conditions makes few connections, mainly to Microsoft and OCSP related
-domains, add FPs here */ [network where network.protocol : "dns" and
-process.name:"iexplore.exe" and not wildcard(dns.question.name,
-"*.microsoft.com",
-"*.digicert.com", "*.msocsp.com",
-"*.windowsupdate.com",
-"*.bing.com", "*.identrust.com")
-]
-----------------------------------
-
+* Sub-technique:
+** Name: Component Object Model
+** ID: T1559.001
+** Reference URL: https://attack.mitre.org/techniques/T1559/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-container-escape-via-modified-notify-on-release-file.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-container-escape-via-modified-notify-on-release-file.asciidoc
new file mode 100644
index 0000000000..1e9dc433ee
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-container-escape-via-modified-notify-on-release-file.asciidoc
@@ -0,0 +1,63 @@
+[[potential-container-escape-via-modified-notify-on-release-file]]
+=== Potential Container Escape via Modified notify_on_release File
+
+This rule detects modification of the cgroup notify_on_release file from inside a container. When the notify_on_release flag is enabled (1) in a cgroup, then whenever the last task in the cgroup exits or attaches to another cgroup, the command specified in the release_agent file is run and invoked from the host. A privileged container with SYS_ADMIN capabilities, enables a threat actor to mount a cgroup directory and modify the notify_on_release flag in order to take advantage of this feature, which could be used for further privilege escalation and container escapes to the host machine.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.trailofbits.com/2019/07/19/understanding-docker-container-escapes/
+* https://sysdig.com/blog/detecting-mitigating-cve-2022-0492-sysdig/
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where event.module == "cloud_defend" and event.action == "open" and 
+event.type == "change" and file.name : "notify_on_release"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Escape to Host
+** ID: T1611
+** Reference URL: https://attack.mitre.org/techniques/T1611/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-container-escape-via-modified-release-agent-file.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-container-escape-via-modified-release-agent-file.asciidoc
new file mode 100644
index 0000000000..ee401c00d0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-container-escape-via-modified-release-agent-file.asciidoc
@@ -0,0 +1,64 @@
+[[potential-container-escape-via-modified-release-agent-file]]
+=== Potential Container Escape via Modified release_agent File
+
+This rule detects modification of the CGroup release_agent file from inside a privileged container. The release_agent is a script that is executed at the termination of any process on that CGroup and is invoked from the host. A privileged container with SYS_ADMIN capabilities, enables a threat actor to mount a CGroup directory and modify the release_agent which could be used for further privilege escalation and container escapes to the host machine.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.aquasec.com/threat-alert-container-escape
+* https://sysdig.com/blog/detecting-mitigating-cve-2022-0492-sysdig/
+* https://book.hacktricks.xyz/linux-hardening/privilege-escalation/docker-security/docker-breakout-privilege-escalation#privileged-escape-abusing-existent-release_agent-cve-2022-0492-poc1
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where event.module == "cloud_defend" and event.action == "open" and 
+event.type == "change" and file.name : "release_agent"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Escape to Host
+** ID: T1611
+** Reference URL: https://attack.mitre.org/techniques/T1611/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-cookies-theft-via-browser-debugging.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-cookies-theft-via-browser-debugging.asciidoc
index e6ee377bf2..3d25f16eb5 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-cookies-theft-via-browser-debugging.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-cookies-theft-via-browser-debugging.asciidoc
@@ -5,7 +5,7 @@ Identifies the execution of a Chromium based browser with the debugging process
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * winlogbeat-*
@@ -16,69 +16,72 @@ Identifies the execution of a Chromium based browser with the debugging process
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 33
 
-*References*:
+*References*: 
 
 * https://github.com/defaultnamehere/cookie_crimes
 * https://embracethered.com/blog/posts/2020/cookie-crimes-on-mirosoft-edge/
 * https://github.com/rapid7/metasploit-framework/blob/master/documentation/modules/post/multi/gather/chrome_cookies.md
 * https://posts.specterops.io/hands-in-the-cookie-jar-dumping-cookies-with-chromiums-remote-debugger-port-34c4f468844e
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* Windows
-* macOS
-* Threat Detection
-* Credential Access
-
-*Version*: 100 (<<potential-cookies-theft-via-browser-debugging-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: Windows
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Developers performing browsers plugin or extension debugging.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 process where event.type in ("start", "process_started", "info") and
-process.name in ( "Microsoft Edge",
-"chrome.exe", "Google Chrome", "google-
-chrome-stable", "google-chrome-beta",
-"google-chrome", "msedge.exe") and process.args : ("--
-remote-debugging-port=*", "--remote-debugging-
-targets=*", "--remote-debugging-pipe=*") and
-process.args : "--user-data-dir=*" and not process.args:"--remote-
-debugging-port=0"
-----------------------------------
+  process.name in (
+             "Microsoft Edge",
+             "chrome.exe",
+             "Google Chrome",
+             "google-chrome-stable",
+             "google-chrome-beta",
+             "google-chrome",
+             "msedge.exe") and
+   process.args : ("--remote-debugging-port=*",
+                   "--remote-debugging-targets=*",
+                   "--remote-debugging-pipe=*") and
+   process.args : "--user-data-dir=*" and not process.args:"--remote-debugging-port=0"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -90,29 +93,3 @@ debugging-port=0"
 ** Name: Steal Web Session Cookie
 ** ID: T1539
 ** Reference URL: https://attack.mitre.org/techniques/T1539/
-
-[[potential-cookies-theft-via-browser-debugging-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.name in ( "Microsoft Edge",
-"chrome.exe", "Google Chrome", "google-
-chrome-stable", "google-chrome-beta",
-"google-chrome", "msedge.exe") and process.args : ("--
-remote-debugging-port=*", "--remote-debugging-
-targets=*", "--remote-debugging-pipe=*") and
-process.args : "--user-data-dir=*" and not process.args:"--remote-
-debugging-port=0"
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-dcsync.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-dcsync.asciidoc
index bdc3555d05..be7eca8a29 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-dcsync.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-dcsync.asciidoc
@@ -5,22 +5,23 @@ This rule identifies when a User Account starts the Active Directory Replication
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://threathunterplaybook.com/notebooks/windows/06_credential_access/WIN-180815210510.html
 * https://threathunterplaybook.com/library/windows/active_directory_replication.html?highlight=dcsync#directory-replication-services-auditing
@@ -29,111 +30,130 @@ This rule identifies when a User Account starts the Active Directory Replication
 * https://attack.stealthbits.com/privilege-escalation-using-mimikatz-dcsync
 * https://www.thehacker.recipes/ad/movement/credentials/dumping/dcsync
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Active Directory
-* Investigation Guide
-
-*Version*: 102 (<<potential-credential-access-via-dcsync-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Privilege Escalation
+* Data Source: Active Directory
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 113
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Potential Credential Access via DCSync
+*Triage and analysis*
+
 
-Active Directory replication is the process by which the changes that originate on one domain controller are
-automatically transferred to other domain controllers that store the same data.
 
-Active Directory data consists of objects that have properties, or attributes. Each object is an instance of an object
-class, and object classes and their respective attributes are defined in the Active Directory schema. Objects are
-defined by the values of their attributes, and changes to attribute values must be transferred from the domain
-controller on which they occur to every other domain controller that stores a replica of an affected object.
+*Investigating Potential Credential Access via DCSync*
 
-Adversaries can use the DCSync technique that uses Windows Domain Controller's API to simulate the replication process
-from a remote domain controller, compromising major credential material such as the Kerberos krbtgt keys used
-legitimately for tickets creation, but also tickets forging by attackers. This attack requires some extended privileges
-to succeed (DS-Replication-Get-Changes and DS-Replication-Get-Changes-All), which are granted by default to members of
-the Administrators, Domain Admins, Enterprise Admins, and Domain Controllers groups. Privileged accounts can be abused
-to grant controlled objects the right to DCsync/Replicate.
 
-More details can be found on [Threat Hunter Playbook](https://threathunterplaybook.com/library/windows/active_directory_replication.html?highlight=dcsync#directory-replication-services-auditing) and [The Hacker Recipes](https://www.thehacker.recipes/ad/movement/credentials/dumping/dcsync).
+Active Directory replication is the process by which the changes that originate on one domain controller are automatically transferred to other domain controllers that store the same data.
 
-This rule monitors for Event ID 4662 (Operation was performed on an Active Directory object) and identifies events that
-use the access mask 0x100 (Control Access) and properties that contain at least one of the following or their equivalent:
-Schema-Id-GUID (DS-Replication-Get-Changes, DS-Replication-Get-Changes-All, DS-Replication-Get-Changes-In-Filtered-Set).
-It also filters out events that use computer accounts and also Azure AD Connect MSOL accounts (more details [here](https://techcommunity.microsoft.com/t5/microsoft-defender-for-identity/ad-connect-msol-user-suspected-dcsync-attack/m-p/788028)).
+Active Directory data consists of objects that have properties, or attributes. Each object is an instance of an object class, and object classes and their respective attributes are defined in the Active Directory schema. Objects are defined by the values of their attributes, and changes to attribute values must be transferred from the domain controller on which they occur to every other domain controller that stores a replica of an affected object.
+
+Adversaries can use the DCSync technique that uses Windows Domain Controller's API to simulate the replication process from a remote domain controller, compromising major credential material such as the Kerberos krbtgt keys used legitimately for tickets creation, but also tickets forging by attackers. This attack requires some extended privileges to succeed (DS-Replication-Get-Changes and DS-Replication-Get-Changes-All), which are granted by default to members of the Administrators, Domain Admins, Enterprise Admins, and Domain Controllers groups. Privileged accounts can be abused to grant controlled objects the right to DCsync/Replicate.
+
+More details can be found on https://threathunterplaybook.com/library/windows/active_directory_replication.html?highlight=dcsync#directory-replication-services-auditing[Threat Hunter Playbook] and https://www.thehacker.recipes/ad/movement/credentials/dumping/dcsync[The Hacker Recipes].
+
+This rule monitors for Event ID 4662 (Operation was performed on an Active Directory object) and identifies events that use the access mask 0x100 (Control Access) and properties that contain at least one of the following or their equivalent Schema-Id-GUID (DS-Replication-Get-Changes, DS-Replication-Get-Changes-All, DS-Replication-Get-Changes-In-Filtered-Set). It also filters out events that use computer accounts and also Azure AD Connect MSOL accounts (more details https://techcommunity.microsoft.com/t5/microsoft-defender-for-identity/ad-connect-msol-user-suspected-dcsync-attack/m-p/788028[here]).
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account and system owners and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Correlate security events 4662 and 4624 (Logon Type 3) by their Logon ID (`winlog.logon.id`) on the Domain Controller
-(DC) that received the replication request. This will tell you where the AD replication request came from, and if it
-came from another DC or not.
+- Correlate security events 4662 and 4624 (Logon Type 3) by their Logon ID (`winlog.logon.id`) on the Domain Controller (DC) that received the replication request. This will tell you where the AD replication request came from, and if it came from another DC or not.
 - Scope which credentials were compromised (for example, whether all accounts were replicated or specific ones).
 
-### False positive analysis
 
-- This activity should not happen legitimately, since replication should be done by Domain Controllers only. Any
-potential benign true positive (B-TP) should be mapped and monitored by the security team. Any account that performs
-this activity can put the domain at risk for not having the same security standards as computer accounts (which have
-long, complex, random passwords that change frequently), exposing it to credential cracking attacks (Kerberoasting,
-brute force, etc.).
+*False positive analysis*
+
+
+- Administrators may use custom accounts on Azure AD Connect, investigate if it is the case, and if it is properly secured. If noisy in your environment due to expected activity, consider adding the corresponding account as a exception.
+- Although replicating Active Directory (AD) data to non-Domain Controllers is not a common practice and is generally not recommended from a security perspective, some software vendors may require it for their products to function correctly. If this rule is noisy in your environment due to expected activity, consider adding the corresponding account as a exception.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
-- If specific credentials were compromised:
-  - Reset the password for these accounts and other potentially compromised credentials, like email, business systems,
-  and web services.
-- If the entire domain or the `krbtgt` user were compromised:
-  - Activate your incident response plan for total Active Directory compromise which should include, but not be limited
-  to, a password reset (twice) of the `krbtgt` user.
-- Investigate how the attacker escalated privileges and identify systems they used to conduct lateral movement. Use this
-information to scope ways that the attacker could use to regain access to the environment.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If the entire domain or the `krbtgt` user was compromised:
+  - Activate your incident response plan for total Active Directory compromise which should include, but not be limited to, a password reset (twice) of the `krbtgt` user.
+- Investigate how the attacker escalated privileges and identify systems they used to conduct lateral movement. Use this information to determine ways the attacker could regain access to the environment.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Directory Service Access' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Access (Success,Failure)
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-any where event.action == "Directory Service Access" and event.code
-== "4662" and winlog.event_data.Properties : ( /* Control Access
-Rights/Permissions Symbol */ "*DS-Replication-Get-Changes*",
-"*DS-Replication-Get-Changes-All*", "*DS-Replication-Get-Changes-
-In-Filtered-Set*", /* Identifying GUID used in ACE */
-"*1131f6ad-9c07-11d1-f79f-00c04fc2dcd2*",
-"*1131f6aa-9c07-11d1-f79f-00c04fc2dcd2*",
-"*89e95b76-444d-4c62-991a-0facbeda640c*") /* The right to perform
-an operation controlled by an extended access right. */ and
-winlog.event_data.AccessMask : "0x100" and not
-winlog.event_data.SubjectUserName : ("*$", "MSOL_*")
+[source, js]
 ----------------------------------
+any where event.action : ("Directory Service Access", "object-operation-performed") and
+  event.code == "4662" and winlog.event_data.Properties : (
+
+    /* Control Access Rights/Permissions Symbol */
+
+    "*DS-Replication-Get-Changes*",
+    "*DS-Replication-Get-Changes-All*",
+    "*DS-Replication-Get-Changes-In-Filtered-Set*",
+
+    /* Identifying GUID used in ACE */
 
-==== Threat mapping
+    "*1131f6ad-9c07-11d1-f79f-00c04fc2dcd2*",
+    "*1131f6aa-9c07-11d1-f79f-00c04fc2dcd2*",
+    "*89e95b76-444d-4c62-991a-0facbeda640c*")
+
+    /* The right to perform an operation controlled by an extended access right. */
+
+    and winlog.event_data.AccessMask : "0x100" and
+    not winlog.event_data.SubjectUserName : (
+          "*$", "MSOL_*", "OpenDNS_Connector", "adconnect", "SyncADConnect",
+          "SyncADConnectCM", "aadsync", "svcAzureADSync", "-"
+        )
+
+    /* The Umbrella AD Connector uses the OpenDNS_Connector account to perform replication */
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -145,37 +165,19 @@ winlog.event_data.SubjectUserName : ("*$", "MSOL_*")
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[potential-credential-access-via-dcsync-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-any where event.action == "Directory Service Access" and event.code
-== "4662" and winlog.event_data.Properties : ( /* Control Access
-Rights/Permissions Symbol */ "*DS-Replication-Get-Changes*",
-"*DS-Replication-Get-Changes-All*", "*DS-Replication-Get-Changes-
-In-Filtered-Set*", /* Identifying GUID used in ACE */
-"*1131f6ad-9c07-11d1-f79f-00c04fc2dcd2*",
-"*1131f6aa-9c07-11d1-f79f-00c04fc2dcd2*",
-"*89e95b76-444d-4c62-991a-0facbeda640c*") /* The right to
-perform an operation controlled by an extended access right. */
-and winlog.event_data.AccessMask : "0x100" and not
-winlog.event_data.SubjectUserName : ("*$", "MSOL_*")
-----------------------------------
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: DCSync
+** ID: T1003.006
+** Reference URL: https://attack.mitre.org/techniques/T1003/006/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Domain Accounts
+** ID: T1078.002
+** Reference URL: https://attack.mitre.org/techniques/T1078/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-duplicatehandle-in-lsass.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-duplicatehandle-in-lsass.asciidoc
index 459f54a3f2..fa473d1124 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-duplicatehandle-in-lsass.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-duplicatehandle-in-lsass.asciidoc
@@ -5,66 +5,70 @@ Identifies suspicious access to an LSASS handle via DuplicateHandle from an unkn
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/CCob/MirrorDump
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Sysmon Only
-
-*Version*: 101 (<<potential-credential-access-via-duplicatehandle-in-lsass-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 208
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.code == "10" and /* LSASS requesting
-DuplicateHandle access right to another process */ process.name :
-"lsass.exe" and winlog.event_data.GrantedAccess == "0x40" and /*
-call is coming from an unknown executable region */
-winlog.event_data.CallTrace : "*UNKNOWN*"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.code == "10" and
+
+ /* LSASS requesting DuplicateHandle access right to another process */
+ process.name : "lsass.exe" and winlog.event_data.GrantedAccess == "0x40" and
 
-==== Threat mapping
+ /* call is coming from an unknown executable region */
+ winlog.event_data.CallTrace : "*UNKNOWN*"
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,31 +80,7 @@ winlog.event_data.CallTrace : "*UNKNOWN*"
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[potential-credential-access-via-duplicatehandle-in-lsass-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.code == "10" and /* LSASS requesting
-DuplicateHandle access right to another process */ process.name :
-"lsass.exe" and winlog.event_data.GrantedAccess == "0x40" and /*
-call is coming from an unknown executable region */
-winlog.event_data.CallTrace : "*UNKNOWN*"
-----------------------------------
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.0.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-lsass-memory-dump.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-lsass-memory-dump.asciidoc
index a3c5d9d76b..d5a44cdaa0 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-lsass-memory-dump.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-lsass-memory-dump.asciidoc
@@ -5,69 +5,77 @@ Identifies suspicious access to LSASS handle from a call trace pointing to DBGHe
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.ired.team/offensive-security/credential-access-and-credential-dumping/dump-credentials-from-lsass-process-without-mimikatz
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Sysmon Only
-
-*Version*: 101 (<<potential-credential-access-via-lsass-memory-dump-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic:Execution
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 209
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.code == "10" and winlog.event_data.TargetImage :
-"?:\\WINDOWS\\system32\\lsass.exe" and /* DLLs exporting
-MiniDumpWriteDump API to create an lsass mdmp*/
-winlog.event_data.CallTrace : ("*dbghelp*", "*dbgcore*") and /*
-case of lsass crashing */ not process.executable :
-("?:\\Windows\\System32\\WerFault.exe",
-"?:\\Windows\\System32\\WerFaultSecure.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.code == "10" and
+  winlog.event_data.TargetImage : "?:\\WINDOWS\\system32\\lsass.exe" and
+
+   /* DLLs exporting MiniDumpWriteDump API to create an lsass mdmp*/
+  winlog.event_data.CallTrace : ("*dbghelp*", "*dbgcore*") and
 
-==== Threat mapping
+   /* case of lsass crashing */
+  not process.executable : (
+        "?:\\Windows\\System32\\WerFault.exe",
+        "?:\\Windows\\SysWOW64\\WerFault.exe",
+        "?:\\Windows\\System32\\WerFaultSecure.exe"
+      )
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,44 +87,15 @@ case of lsass crashing */ not process.executable :
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[potential-credential-access-via-lsass-memory-dump-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.code == "10" and winlog.event_data.TargetImage :
-"?:\\WINDOWS\\system32\\lsass.exe" and /* DLLs exporting
-MiniDumpWriteDump API to create an lsass mdmp*/
-winlog.event_data.CallTrace : ("*dbghelp*", "*dbgcore*") and /*
-case of lsass crashing */ not process.executable :
-("?:\\Windows\\System32\\WerFault.exe",
-"?:\\Windows\\System32\\WerFaultSecure.exe")
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.code == "10" and winlog.event_data.TargetImage :
-"?:\\WINDOWS\\system32\\lsass.exe" and /* DLLs exporting
-MiniDumpWriteDump API to create an lsass mdmp*/
-winlog.event_data.CallTrace : ("*dbhelp*", "*dbgcore*") and /*
-case of lsass crashing */ not process.executable :
-("?:\\Windows\\System32\\WerFault.exe",
-"?:\\Windows\\System32\\WerFaultSecure.exe")
-----------------------------------
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Native API
+** ID: T1106
+** Reference URL: https://attack.mitre.org/techniques/T1106/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-memory-dump-file-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-memory-dump-file-creation.asciidoc
new file mode 100644
index 0000000000..269b9e447f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-memory-dump-file-creation.asciidoc
@@ -0,0 +1,106 @@
+[[potential-credential-access-via-memory-dump-file-creation]]
+=== Potential Credential Access via Memory Dump File Creation
+
+Identifies the creation or modification of a medium size memory dump file which can indicate an attempt to access credentials from a process memory.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and
+
+  /* MDMP header */
+  file.Ext.header_bytes : "4d444d50*" and file.size >= 30000 and
+  not
+
+  (
+    (
+      process.name : "System" or
+      process.executable : (
+        "?:\\Windows\\System32\\WerFault.exe",
+        "?:\\Windows\\SysWOW64\\WerFault.exe",
+        "?:\\Windows\\System32\\Wermgr.exe",
+        "?:\\Windows\\SysWOW64\\Wermgr.exe",
+        "?:\\Windows\\System32\\WerFaultSecure.exe",
+        "?:\\Windows\\SysWOW64\\WerFaultSecure.exe",
+        "?:\\Windows\\System32\\WUDFHost.exe",
+        "C:\\Windows\\System32\\rdrleakdiag.exe",
+        "?:\\Windows\\System32\\Taskmgr.exe",
+        "?:\\Windows\\SysWOW64\\Taskmgr.exe",
+        "?:\\Program Files\\*.exe",
+        "?:\\Program Files (x86)\\*.exe",
+        "?:\\Windows\\SystemApps\\*.exe",
+        "?:\\Users\\*\\AppData\\Roaming\\Zoom\\bin\\zCrashReport64.exe",
+        "?:\\Windows\\CCM\\ccmdump.exe"
+      ) and process.code_signature.trusted == true
+    ) or
+    (
+      file.path : (
+        "?:\\ProgramData\\Microsoft\\Windows\\WER\\*",
+        "?:\\ProgramData\\Microsoft\\WDF\\*",
+        "?:\\ProgramData\\Alteryx\\ErrorLogs\\*",
+        "?:\\ProgramData\\Goodix\\*",
+        "?:\\Windows\\system32\\config\\systemprofile\\AppData\\Local\\CrashDumps\\*",
+        "?:\\Users\\*\\AppData\\Roaming\\Zoom\\logs\\zoomcrash*",
+        "?:\\Users\\*\\AppData\\*\\Crashpad\\*",
+        "?:\\Users\\*\\AppData\\*\\crashpaddb\\*",
+        "?:\\Users\\*\\AppData\\*\\HungReports\\*",
+        "?:\\Users\\*\\AppData\\*\\CrashDumps\\*",
+        "?:\\Users\\*\\AppData\\*\\NativeCrashReporting\\*"
+      ) and (process.code_signature.trusted == true or process.executable == null)
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-renamed-com-services-dll.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-renamed-com-services-dll.asciidoc
index e248a037b7..ff275568ca 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-renamed-com-services-dll.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-renamed-com-services-dll.asciidoc
@@ -5,68 +5,146 @@ Identifies suspicious renamed COMSVCS.DLL Image Load, which exports the MiniDump
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://modexp.wordpress.com/2019/08/30/minidumpwritedump-via-com-services-dll/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Sysmon Only
-
-*Version*: 101 (<<potential-credential-access-via-renamed-com-services-dll-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Defense Evasion
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating Potential Credential Access via Renamed COM+ Services DLL*
+
+
+COMSVCS.DLL is a Windows library that exports the MiniDump function, which can be used to dump a process memory. Adversaries may attempt to dump LSASS memory using a renamed COMSVCS.DLL to bypass command-line based detection and gain unauthorized access to credentials.
+
+This rule identifies suspicious instances of rundll32.exe loading a renamed COMSVCS.DLL image, which can indicate potential abuse of the MiniDump function for credential theft.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate any abnormal behavior by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
+- Identify the process that created the DLL using file creation events.
+   - Inspect the file for useful metadata, such as file size and creation or modification time.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable and DLL using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Look for the presence of relevant artifacts on other systems. Identify commonalities and differences between potentially compromised systems.
+
+
+*False positive analysis*
+
+
+- False positives may include legitimate instances of rundll32.exe loading a renamed COMSVCS.DLL image for non-malicious purposes, such as during software development, testing, or troubleshooting.
+
+
+*Related Rules*
+
+
+- Potential Credential Access via LSASS Memory Dump - 9960432d-9b26-409f-972b-839a959e79e2
+- Suspicious Module Loaded by LSASS - 3a6001a0-0939-4bbe-86f4-47d8faeb7b97
+- Suspicious Lsass Process Access - 128468bf-cab1-4637-99ea-fdf3780a4609
+- LSASS Process Access via Windows API - ff4599cb-409f-4910-a239-52e4e6f532ff
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+  - If malicious activity is confirmed, perform a broader investigation to identify the scope of the compromise and determine the appropriate remediation steps.
+- Implement Elastic Endpoint Security to detect and prevent further post exploitation activities in the environment.
+   - Contain the affected system by isolating it from the network to prevent further spread of the attack.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Restore the affected system to its operational state by applying any necessary patches, updates, or configuration changes.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+You will need to enable logging of ImageLoads in your Sysmon configuration to include COMSVCS.DLL by Imphash or Original
+File Name.
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id with maxspan=1m [process where
-event.category == "process" and process.name : "rundll32.exe"]
-[process where event.category == "process" and event.dataset :
-"windows.sysmon_operational" and event.code == "7" and
-(file.pe.original_file_name : "COMSVCS.DLL" or file.pe.imphash :
-"EADBCCBB324829ACB5F2BBE87E5549A8") and /* renamed COMSVCS */
-not file.name : "COMSVCS.DLL"]
+[source, js]
 ----------------------------------
+sequence by process.entity_id with maxspan=1m
+ [process where host.os.type == "windows" and event.category == "process" and
+    process.name : "rundll32.exe"]
+ [process where host.os.type == "windows" and event.category == "process" and event.dataset : "windows.sysmon_operational" and event.code == "7" and
+   (file.pe.original_file_name : "COMSVCS.DLL" or file.pe.imphash : "EADBCCBB324829ACB5F2BBE87E5549A8") and
+    /* renamed COMSVCS */
+    not file.name : "COMSVCS.DLL"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,22 +156,19 @@ not file.name : "COMSVCS.DLL"]
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[potential-credential-access-via-renamed-com-services-dll-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: Rundll32
+** ID: T1218.011
+** Reference URL: https://attack.mitre.org/techniques/T1218/011/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-trusted-developer-utility.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-trusted-developer-utility.asciidoc
index 7a2ca30634..4b09f642d3 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-trusted-developer-utility.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-trusted-developer-utility.asciidoc
@@ -5,100 +5,97 @@ An instance of MSBuild, the Microsoft Build Engine, loaded DLLs (dynamically lin
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.library-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<potential-credential-access-via-trusted-developer-utility-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-The Build Engine is commonly used by Windows developers but use by non-engineers is unusual.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Potential Credential Access via Trusted Developer Utility
+*Triage and analysis*
+
+
 
-The Microsoft Build Engine is a platform for building applications. This engine, also known as MSBuild, provides an XML
-schema for a project file that controls how the build platform processes and builds software.
+*Investigating Potential Credential Access via Trusted Developer Utility*
 
-Adversaries can abuse MSBuild to proxy the execution of malicious code. The inline task capability of MSBuild that was
-introduced in .NET version 4 allows for C# or Visual Basic code to be inserted into an XML project file. MSBuild will
-compile and execute the inline task. `MSBuild.exe` is a signed Microsoft binary, and the execution of code using it can bypass
-application control defenses that are configured to allow `MSBuild.exe` execution.
 
-This rule looks for the MSBuild process loading `vaultcli.dll` or `SAMLib.DLL`, which indicates the execution of
-credential access activities.
+The Microsoft Build Engine is a platform for building applications. This engine, also known as MSBuild, provides an XML schema for a project file that controls how the build platform processes and builds software.
+
+Adversaries can abuse MSBuild to proxy the execution of malicious code. The inline task capability of MSBuild that was introduced in .NET version 4 allows for C# or Visual Basic code to be inserted into an XML project file. MSBuild will compile and execute the inline task. `MSBuild.exe` is a signed Microsoft binary, and the execution of code using it can bypass application control defenses that are configured to allow `MSBuild.exe` execution.
+
+This rule looks for the MSBuild process loading `vaultcli.dll` or `SAMLib.DLL`, which indicates the execution of credential access activities.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file
-modifications, and any spawned child processes.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Examine the command line to identify the `.csproj` file location.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
-- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target
-host after the registry modification.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
@@ -106,35 +103,25 @@ host after the registry modification.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where event.type == "start"
-and (process.name : "MSBuild.exe" or process.pe.original_file_name ==
-"MSBuild.exe")] [any where (event.category == "library" or
-(event.category == "process" and event.action : "Image loaded*")) and
-(dll.name : ("vaultcli.dll", "SAMLib.DLL") or file.name :
-("vaultcli.dll", "SAMLib.DLL"))]
+[source, js]
 ----------------------------------
+sequence by process.entity_id
+ [process where host.os.type == "windows" and event.type == "start" and (process.name : "MSBuild.exe" or process.pe.original_file_name == "MSBuild.exe")]
+ [any where host.os.type == "windows" and (event.category == "library" or (event.category == "process" and event.action : "Image loaded*")) and
+  (?dll.name : ("vaultcli.dll", "SAMLib.DLL") or file.name : ("vaultcli.dll", "SAMLib.DLL"))]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -146,71 +133,27 @@ and (process.name : "MSBuild.exe" or process.pe.original_file_name ==
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[potential-credential-access-via-trusted-developer-utility-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 11 (8.4.0 release)::
-* Rule name changed from: Microsoft Build Engine Loading Windows Credential Libraries
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where event.type == "start"
-and (process.name : "MSBuild.exe" or process.pe.original_file_name ==
-"MSBuild.exe")] [library where dll.name : ("vaultcli.dll",
-"SAMLib.DLL")]
-----------------------------------
-
-Version 9 (8.2.0 release)::
-* Formatting only
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:change and
-(process.pe.original_file_name:(vaultcli.dll or SAMLib.DLL) or
-dll.name:(vaultcli.dll or SAMLib.DLL)) and process.name: MSBuild.exe
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:change and
-(winlog.event_data.OriginalFileName:(vaultcli.dll or SAMLib.DLL) or
-dll.name:(vaultcli.dll or SAMLib.DLL)) and process.name: MSBuild.exe
-----------------------------------
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-(winlog.event_data.OriginalFileName: (vaultcli.dll or SAMLib.DLL) or
-dll.name: (vaultcli.dll or SAMLib.DLL)) and process.name: MSBuild.exe
-and event.action: "Image loaded (rule: ImageLoad)"
-----------------------------------
-
+* Sub-technique:
+** Name: Security Account Manager
+** ID: T1003.002
+** Reference URL: https://attack.mitre.org/techniques/T1003/002/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Sub-technique:
+** Name: Windows Credential Manager
+** ID: T1555.004
+** Reference URL: https://attack.mitre.org/techniques/T1555/004/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Trusted Developer Utilities Proxy Execution
+** ID: T1127
+** Reference URL: https://attack.mitre.org/techniques/T1127/
+* Sub-technique:
+** Name: MSBuild
+** ID: T1127.001
+** Reference URL: https://attack.mitre.org/techniques/T1127/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-windows-utilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-windows-utilities.asciidoc
index 424c673162..b7a6c35123 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-windows-utilities.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-credential-access-via-windows-utilities.asciidoc
@@ -5,125 +5,149 @@ Identifies the execution of known Windows utilities often abused to dump LSASS m
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://lolbas-project.github.io/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<potential-credential-access-via-windows-utilities-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Potential Credential Access via Windows Utilities
+*Triage and analysis*
+
+
+
+*Investigating Potential Credential Access via Windows Utilities*
+
+
+Local Security Authority Server Service (LSASS) is a process in Microsoft Windows operating systems that is responsible for enforcing security policy on the system. It verifies users logging on to a Windows computer or server, handles password changes, and creates access tokens.
+
+The `Ntds.dit` file is a database that stores Active Directory data, including information about user objects, groups, and group membership.
 
-Local Security Authority Server Service (LSASS) is a process in Microsoft Windows operating systems that is responsible
-for enforcing security policy on the system. It verifies users logging on to a Windows computer or server, handles
-password changes, and creates access tokens.
+This rule looks for the execution of utilities that can extract credential data from the LSASS memory and Active Directory `Ntds.dit` file.
 
-The `Ntds.dit` file is a database that stores Active Directory data, including information about user objects, groups, and
-group membership.
 
-This rule looks for the execution of utilities that can extract credential data from the LSASS memory and Active
-Directory `Ntds.dit` file.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file
-modifications, and any spawned child processes.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Examine the command line to identify what information was targeted.
 - Identify the target computer and its role in the IT environment.
 
-### False positive analysis
 
-- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious
-must be monitored by the security team.
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - If the host is a domain controller (DC):
   - Activate your incident response plan for total Active Directory compromise.
-  - Review the privileges assigned to users that can access the DCs, to ensure that the least privilege principle is
-  being followed and to reduce the attack surface.
+  - Review the privileges assigned to users that can access the DCs, to ensure that the least privilege principle is being followed and to reduce the attack surface.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and /* update here with any new
-lolbas with dump capability */ (process.pe.original_file_name ==
-"procdump" and process.args : "-ma") or (process.name :
-"ProcessDump.exe" and not process.parent.executable regex~
-"""C:\\Program Files( \(x86\))?\\Cisco Systems\\.*""") or
-(process.pe.original_file_name == "WriteMiniDump.exe" and not
-process.parent.executable regex~ """C:\\Program Files(
-\(x86\))?\\Steam\\.*""") or (process.pe.original_file_name ==
-"RUNDLL32.EXE" and (process.args : "MiniDump*" or process.command_line
-: "*comsvcs.dll*#24*")) or (process.pe.original_file_name ==
-"RdrLeakDiag.exe" and process.args : "/fullmemdmp") or
-(process.pe.original_file_name == "SqlDumper.exe" and process.args :
-"0x01100*") or (process.pe.original_file_name == "TTTracer.exe" and
-process.args : "-dumpFull" and process.args : "-attach") or
-(process.pe.original_file_name == "ntdsutil.exe" and process.args :
-"create*full*") or (process.pe.original_file_name == "diskshadow.exe"
-and process.args : "/s")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+(
+  (
+    (?process.pe.original_file_name : "procdump" or process.name : "procdump.exe") and process.args : "-ma"
+  ) or
+  (
+    process.name : "ProcessDump.exe" and not process.parent.executable regex~ """C:\\Program Files( \(x86\))?\\Cisco Systems\\.*"""
+  ) or
+  (
+    (?process.pe.original_file_name : "WriteMiniDump.exe" or process.name : "WriteMiniDump.exe") and
+      not process.parent.executable regex~ """C:\\Program Files( \(x86\))?\\Steam\\.*"""
+  ) or
+  (
+    (?process.pe.original_file_name : "RUNDLL32.EXE" or process.name : "RUNDLL32.exe") and
+      (process.args : "MiniDump*" or process.command_line : "*comsvcs.dll*#24*")
+  ) or
+  (
+    (?process.pe.original_file_name : "RdrLeakDiag.exe" or process.name : "RdrLeakDiag.exe") and
+      process.args : "/fullmemdmp"
+  ) or
+  (
+    (?process.pe.original_file_name : "SqlDumper.exe" or process.name : "SqlDumper.exe") and
+      process.args : "0x01100*") or
+  (
+    (?process.pe.original_file_name : "TTTracer.exe" or process.name : "TTTracer.exe") and
+      process.args : "-dumpFull" and process.args : "-attach") or
+  (
+    (?process.pe.original_file_name : "ntdsutil.exe" or process.name : "ntdsutil.exe") and
+      process.args : "create*full*") or
+  (
+    (?process.pe.original_file_name : "diskshadow.exe" or process.name : "diskshadow.exe") and process.args : "/s")
+)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -135,72 +159,23 @@ and process.args : "/s")
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[potential-credential-access-via-windows-utilities-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and /* update
-here with any new lolbas with dump capability */
-(process.pe.original_file_name == "procdump" and process.args : "-ma")
-or (process.name : "ProcessDump.exe" and not process.parent.executable
-regex~ """C:\\Program Files( \(x86\))?\\Cisco Systems\\.*""") or
-(process.pe.original_file_name == "WriteMiniDump.exe" and not
-process.parent.executable regex~ """C:\\Program Files(
-\(x86\))?\\Steam\\.*""") or (process.pe.original_file_name ==
-"RUNDLL32.EXE" and (process.args : "MiniDump*" or process.command_line
-: "*comsvcs.dll*#24*")) or (process.pe.original_file_name ==
-"RdrLeakDiag.exe" and process.args : "/fullmemdmp") or
-(process.pe.original_file_name == "SqlDumper.exe" and process.args :
-"0x01100*") or (process.pe.original_file_name == "TTTracer.exe" and
-process.args : "-dumpFull" and process.args : "-attach") or
-(process.pe.original_file_name == "ntdsutil.exe" and process.args :
-"create*full*") or (process.pe.original_file_name == "diskshadow.exe"
-and process.args : "/s")
-----------------------------------
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (7.16.0 release)::
-* Formatting only
-
-Version 4 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and /* update
-here with any new lolbas with dump capability */
-(process.pe.original_file_name == "procdump" and process.args : "-ma")
-or (process.name : "ProcessDump.exe" and not process.parent.executable
-: "C:\\Program Files*\\Cisco Systems\\*.exe") or
-(process.pe.original_file_name == "WriteMiniDump.exe" and not
-process.parent.executable : "C:\\Program Files*\\Steam\\*.exe") or
-(process.pe.original_file_name == "RUNDLL32.EXE" and (process.args :
-"MiniDump*" or process.command_line : "*comsvcs.dll*#24*")) or
-(process.pe.original_file_name == "RdrLeakDiag.exe" and process.args :
-"/fullmemdmp") or (process.pe.original_file_name == "SqlDumper.exe"
-and process.args : "0x01100*") or (process.pe.original_file_name ==
-"TTTracer.exe" and process.args : "-dumpFull" and process.args :
-"-attach") or (process.pe.original_file_name == "ntdsutil.exe" and
-process.args : "create*full*") or (process.pe.original_file_name ==
-"diskshadow.exe" and process.args : "/s")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
+* Sub-technique:
+** Name: NTDS
+** ID: T1003.003
+** Reference URL: https://attack.mitre.org/techniques/T1003/003/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: Rundll32
+** ID: T1218.011
+** Reference URL: https://attack.mitre.org/techniques/T1218/011/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-cross-site-scripting-xss.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-cross-site-scripting-xss.asciidoc
new file mode 100644
index 0000000000..5a7707beba
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-cross-site-scripting-xss.asciidoc
@@ -0,0 +1,62 @@
+[[potential-cross-site-scripting-xss]]
+=== Potential Cross Site Scripting (XSS)
+
+Cross-Site Scripting (XSS) is a type of attack in which malicious scripts are injected into trusted websites. In XSS attacks, an attacker uses a benign web application to send malicious code, generally in the form of a browser-side script. This detection rule identifies the potential malicious executions of such browser-side scripts.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* apm-*-transaction*
+* traces-apm*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/payloadbox/xss-payload-list
+
+*Tags*: 
+
+* Data Source: APM
+* Use Case: Threat Detection
+* Tactic: Initial Access
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+any where processor.name == "transaction" and
+url.fragment : ("<iframe*", "*prompt(*)*", "<script*>", "<svg*>", "*onerror=*", "*javascript*alert*", "*eval*(*)*", "*onclick=*",
+"*alert(document.cookie)*", "*alert(document.domain)*","*onresize=*","*onload=*","*onmouseover=*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Drive-by Compromise
+** ID: T1189
+** Reference URL: https://attack.mitre.org/techniques/T1189/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-curl-cve-2023-38545-exploitation.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-curl-cve-2023-38545-exploitation.asciidoc
new file mode 100644
index 0000000000..1e3308a4c3
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-curl-cve-2023-38545-exploitation.asciidoc
@@ -0,0 +1,120 @@
+[[potential-curl-cve-2023-38545-exploitation]]
+=== Potential curl CVE-2023-38545 Exploitation
+
+Detects potential exploitation of curl CVE-2023-38545 by monitoring for vulnerable command line arguments in conjunction with an unusual command line length. A flaw in curl version <= 8.3 makes curl vulnerable to a heap based buffer overflow during the SOCKS5 proxy handshake. Upgrade to curl version >= 8.4 to patch this vulnerability. This exploit can be executed with and without the use of environment variables. For increased visibility, enable the collection of http_proxy, HTTPS_PROXY and ALL_PROXY environment variables based on the instructions provided in the setup guide of this rule.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://curl.se/docs/CVE-2023-38545.html
+* https://daniel.haxx.se/blog/2023/10/11/curl-8-4-0/
+* https://twitter.com/_JohnHammond/status/1711986412554531015
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Use Case: Vulnerability
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+Elastic Defend integration does not collect environment variable logging by default.
+In order to capture this behavior, this rule requires a specific configuration option set within the advanced settings of the Elastic Defend integration.
+ #### To set up environment variable capture for an Elastic Agent policy:
+- Go to “Security → Manage → Policies”.
+- Select an “Elastic Agent policy”.
+- Click “Show advanced settings”.
+- Scroll down or search for “linux.advanced.capture_env_vars”.
+- Enter the names of environment variables you want to capture, separated by commas.
+- For this rule the linux.advanced.capture_env_vars variable should be set to "http_proxy,HTTPS_PROXY,ALL_PROXY".
+- Click “Save”.
+After saving the integration change, the Elastic Agents running this policy will be updated and the rule will function properly.
+For more information on capturing environment variables refer to the https://www.elastic.co/guide/en/security/current/environment-variable-capture.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and process.name == "curl" 
+and (
+  process.args : ("--socks5-hostname", "--proxy", "--preproxy", "socks5*") or 
+  process.env_vars: ("http_proxy=socks5h://*", "HTTPS_PROXY=socks5h://*", "ALL_PROXY=socks5h://*")
+) and length(process.command_line) > 255 and 
+not process.parent.name in ("cf-agent", "agent-run", "agent-check", "rudder", "agent-inventory", "cf-execd") and
+not process.args == "/opt/rudder/bin/curl"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Exploitation for Client Execution
+** ID: T1203
+** Reference URL: https://attack.mitre.org/techniques/T1203/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-destination-port.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-destination-port.asciidoc
new file mode 100644
index 0000000000..8b9714d938
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-destination-port.asciidoc
@@ -0,0 +1,91 @@
+[[potential-data-exfiltration-activity-to-an-unusual-destination-port]]
+=== Potential Data Exfiltration Activity to an Unusual Destination Port
+
+A machine learning job has detected data exfiltration to a particular destination port. Data transfer patterns that are outside the normal traffic patterns of an organization could indicate exfiltration over command and control channels.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-6h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/ded
+* https://www.elastic.co/blog/detect-data-exfiltration-activity-with-kibanas-new-integration
+
+*Tags*: 
+
+* Use Case: Data Exfiltration Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Exfiltration
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Data Exfiltration Detection integration assets to be installed, as well as network and file events collected by integrations such as Elastic Defend and Network Packet Capture (for network events only).  
+
+
+*Data Exfiltration Detection Setup*
+
+The Data Exfiltration Detection integration detects data exfiltration activity by identifying abnormalities in network and file events. Anomalies are detected using Elastic's Anomaly Detection feature. 
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Data Exfiltration Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Network events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] or https://docs.elastic.co/integrations/network_traffic[Network Packet Capture] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To add the Network Packet Capture integration to an Elastic Agent policy, refer to https://www.elastic.co/guide/en/fleet/current/add-integration-to-policy.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the Data Exfiltration Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Data Exfiltration Detection and select the integration to see more details about it.
+- Under Settings, click Install Data Exfiltration Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Data Exfiltration Detection, you'll need to enable the corresponding Anomaly Detection jobs. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your network data. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events, or `logs-network_traffic.*` if you used Network Packet Capture.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/ded/kibana/ml_module/ded-ml.json[this] configuration file, you will see a card for Data Exfiltration Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over C2 Channel
+** ID: T1041
+** Reference URL: https://attack.mitre.org/techniques/T1041/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-ip-address.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-ip-address.asciidoc
new file mode 100644
index 0000000000..5732f82689
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-ip-address.asciidoc
@@ -0,0 +1,91 @@
+[[potential-data-exfiltration-activity-to-an-unusual-ip-address]]
+=== Potential Data Exfiltration Activity to an Unusual IP Address
+
+A machine learning job has detected data exfiltration to a particular geo-location (by IP address). Data transfers to geo-locations that are outside the normal traffic patterns of an organization could indicate exfiltration over command and control channels.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-6h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/ded
+* https://www.elastic.co/blog/detect-data-exfiltration-activity-with-kibanas-new-integration
+
+*Tags*: 
+
+* Use Case: Data Exfiltration Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Exfiltration
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Data Exfiltration Detection integration assets to be installed, as well as network and file events collected by integrations such as Elastic Defend and Network Packet Capture (for network events only).  
+
+
+*Data Exfiltration Detection Setup*
+
+The Data Exfiltration Detection integration detects data exfiltration activity by identifying abnormalities in network and file events. Anomalies are detected using Elastic's Anomaly Detection feature. 
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Data Exfiltration Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Network events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] or https://docs.elastic.co/integrations/network_traffic[Network Packet Capture] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To add the Network Packet Capture integration to an Elastic Agent policy, refer to https://www.elastic.co/guide/en/fleet/current/add-integration-to-policy.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the Data Exfiltration Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Data Exfiltration Detection and select the integration to see more details about it.
+- Under Settings, click Install Data Exfiltration Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Data Exfiltration Detection, you'll need to enable the corresponding Anomaly Detection jobs. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your network data. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events, or `logs-network_traffic.*` if you used Network Packet Capture.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/ded/kibana/ml_module/ded-ml.json[this] configuration file, you will see a card for Data Exfiltration Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over C2 Channel
+** ID: T1041
+** Reference URL: https://attack.mitre.org/techniques/T1041/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-iso-code.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-iso-code.asciidoc
new file mode 100644
index 0000000000..e5508212fd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-iso-code.asciidoc
@@ -0,0 +1,91 @@
+[[potential-data-exfiltration-activity-to-an-unusual-iso-code]]
+=== Potential Data Exfiltration Activity to an Unusual ISO Code
+
+A machine learning job has detected data exfiltration to a particular geo-location (by region name). Data transfers to geo-locations that are outside the normal traffic patterns of an organization could indicate exfiltration over command and control channels.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-6h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/ded
+* https://www.elastic.co/blog/detect-data-exfiltration-activity-with-kibanas-new-integration
+
+*Tags*: 
+
+* Use Case: Data Exfiltration Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Exfiltration
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Data Exfiltration Detection integration assets to be installed, as well as network and file events collected by integrations such as Elastic Defend and Network Packet Capture (for network events only).  
+
+
+*Data Exfiltration Detection Setup*
+
+The Data Exfiltration Detection integration detects data exfiltration activity by identifying abnormalities in network and file events. Anomalies are detected using Elastic's Anomaly Detection feature. 
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Data Exfiltration Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Network events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] or https://docs.elastic.co/integrations/network_traffic[Network Packet Capture] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To add the Network Packet Capture integration to an Elastic Agent policy, refer to https://www.elastic.co/guide/en/fleet/current/add-integration-to-policy.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the Data Exfiltration Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Data Exfiltration Detection and select the integration to see more details about it.
+- Under Settings, click Install Data Exfiltration Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Data Exfiltration Detection, you'll need to enable the corresponding Anomaly Detection jobs. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your network data. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events, or `logs-network_traffic.*` if you used Network Packet Capture.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/ded/kibana/ml_module/ded-ml.json[this] configuration file, you will see a card for Data Exfiltration Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over C2 Channel
+** ID: T1041
+** Reference URL: https://attack.mitre.org/techniques/T1041/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-region.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-region.asciidoc
new file mode 100644
index 0000000000..850bec3f0f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-data-exfiltration-activity-to-an-unusual-region.asciidoc
@@ -0,0 +1,91 @@
+[[potential-data-exfiltration-activity-to-an-unusual-region]]
+=== Potential Data Exfiltration Activity to an Unusual Region
+
+A machine learning job has detected data exfiltration to a particular geo-location (by region name). Data transfers to geo-locations that are outside the normal traffic patterns of an organization could indicate exfiltration over command and control channels.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-6h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/ded
+* https://www.elastic.co/blog/detect-data-exfiltration-activity-with-kibanas-new-integration
+
+*Tags*: 
+
+* Use Case: Data Exfiltration Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Exfiltration
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Data Exfiltration Detection integration assets to be installed, as well as network and file events collected by integrations such as Elastic Defend and Network Packet Capture (for network events only).  
+
+
+*Data Exfiltration Detection Setup*
+
+The Data Exfiltration Detection integration detects data exfiltration activity by identifying abnormalities in network and file events. Anomalies are detected using Elastic's Anomaly Detection feature. 
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Data Exfiltration Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Network events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] or https://docs.elastic.co/integrations/network_traffic[Network Packet Capture] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To add the Network Packet Capture integration to an Elastic Agent policy, refer to https://www.elastic.co/guide/en/fleet/current/add-integration-to-policy.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the Data Exfiltration Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Data Exfiltration Detection and select the integration to see more details about it.
+- Under Settings, click Install Data Exfiltration Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Data Exfiltration Detection, you'll need to enable the corresponding Anomaly Detection jobs. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your network data. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events, or `logs-network_traffic.*` if you used Network Packet Capture.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/ded/kibana/ml_module/ded-ml.json[this] configuration file, you will see a card for Data Exfiltration Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over C2 Channel
+** ID: T1041
+** Reference URL: https://attack.mitre.org/techniques/T1041/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-defense-evasion-via-cmstp-exe.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-defense-evasion-via-cmstp-exe.asciidoc
new file mode 100644
index 0000000000..384df4e64d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-defense-evasion-via-cmstp-exe.asciidoc
@@ -0,0 +1,67 @@
+[[potential-defense-evasion-via-cmstp-exe]]
+=== Potential Defense Evasion via CMSTP.exe
+
+The Microsoft Connection Manager Profile Installer (CMSTP.exe) is a command-line program to install Connection Manager service profiles, which accept installation information file (INF) files. Adversaries may abuse CMSTP to proxy the execution of malicious code by supplying INF files that contain malicious commands.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://attack.mitre.org/techniques/T1218/003/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "cmstp.exe" and process.args == "/s"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: CMSTP
+** ID: T1218.003
+** Reference URL: https://attack.mitre.org/techniques/T1218/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-defense-evasion-via-proot.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-defense-evasion-via-proot.asciidoc
new file mode 100644
index 0000000000..261b8f8e6c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-defense-evasion-via-proot.asciidoc
@@ -0,0 +1,101 @@
+[[potential-defense-evasion-via-proot]]
+=== Potential Defense Evasion via PRoot
+
+Identifies the execution of the PRoot utility, an open-source tool for user-space implementation of chroot, mount --bind, and binfmt_misc. Adversaries can leverage an open-source tool PRoot to expand the scope of their operations to multiple Linux distributions and simplify their necessary efforts. In a normal threat scenario, the scope of an attack is limited by the varying configurations of each Linux distribution. With PRoot, it provides an attacker with a consistent operational environment across different Linux distributions, such as Ubuntu, Fedora, and Alpine. PRoot also provides emulation capabilities that allow for malware built on other architectures, such as ARM, to be run.The post-exploitation technique called bring your own filesystem (BYOF), can be used by the threat actors to execute malicious payload or elevate privileges or perform network scans or orchestrate another attack on the environment. Although PRoot was originally not developed with malicious intent it can be easily tuned to work for one.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://proot-me.github.io/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
+process.parent.name == "proot"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Exploitation for Defense Evasion
+** ID: T1211
+** Reference URL: https://attack.mitre.org/techniques/T1211/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-dga-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-dga-activity.asciidoc
new file mode 100644
index 0000000000..a82b558f4c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-dga-activity.asciidoc
@@ -0,0 +1,122 @@
+[[potential-dga-activity]]
+=== Potential DGA Activity
+
+A population analysis machine learning job detected potential DGA (domain generation algorithm) activity. Such activity is often used by malware command and control (C2) channels. This machine learning job looks for a source IP address making DNS requests that have an aggregate high probability of being DGA activity.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/dga
+* https://www.elastic.co/security-labs/detect-domain-generation-algorithm-activity-with-new-kibana-integration
+
+*Tags*: 
+
+* Use Case: Domain Generation Algorithm Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Command and Control
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Domain Generation Algorithm (DGA) Detection integration assets to be installed, as well as DNS events collected by integrations such as Elastic Defend, Network Packet Capture, or Packetbeat.  
+
+
+*DGA Detection Setup*
+
+The DGA Detection integration consists of an ML-based framework to detect DGA activity in DNS events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for DGA Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- DNS events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend], https://docs.elastic.co/integrations/network_traffic[Network Packet Capture] integration, or https://www.elastic.co/guide/en/beats/packetbeat/current/packetbeat-overview.html[Packetbeat].
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To add the Network Packet Capture integration to an Elastic Agent policy, refer to https://www.elastic.co/guide/en/fleet/current/add-integration-to-policy.html[this] guide.
+- To set up and run Packetbeat, follow https://www.elastic.co/guide/en/beats/packetbeat/current/setting-up-and-running.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the DGA Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Domain Generation Algorithm Detection and select the integration to see more details about it.
+- Under Settings, click Install Domain Generation Algorithm Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+Before you can enable this rule, you'll need to enrich DNS events with predictions from the Supervised DGA Detection model. This is done via the ingest pipeline named `<package_version>-ml_dga_ingest_pipeline` installed with the DGA Detection package.
+- If using an Elastic Beat such as Packetbeat, add the DGA ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `packetbeat.yml`.
+- If adding the DGA ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the DGA ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "ml_is_dga": {
+      "properties": {
+        "malicious_prediction": {
+          "type": "long"
+        },
+        "malicious_probability": {
+          "type": "float"
+        }
+      }
+    }
+  }
+}
+```
+
+
+*Anomaly Detection Setup*
+
+Before you can enable this rule, you'll need to enable the corresponding Anomaly Detection job. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your enriched DNS events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events, or `logs-network_traffic.*` if you used Network Packet Capture.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/dga/kibana/ml_module/dga-ml.json[this] configuration file, you will see a card for DGA under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection job and datafeed.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Dynamic Resolution
+** ID: T1568
+** Reference URL: https://attack.mitre.org/techniques/T1568/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-disabling-of-apparmor.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-disabling-of-apparmor.asciidoc
new file mode 100644
index 0000000000..4bf1f8219d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-disabling-of-apparmor.asciidoc
@@ -0,0 +1,109 @@
+[[potential-disabling-of-apparmor]]
+=== Potential Disabling of AppArmor
+
+This rule monitors for potential attempts to disable AppArmor. AppArmor is a Linux security module that enforces fine-grained access control policies to restrict the actions and resources that specific applications and processes can access. Adversaries may disable security tools to avoid possible detection of their tools and activities.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and (
+  (process.name == "systemctl" and process.args == "disable" and process.args == "apparmor") or
+  (process.name == "ln" and process.args : "/etc/apparmor.d/*" and process.args == "/etc/apparmor.d/disable/")
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-disabling-of-selinux.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-disabling-of-selinux.asciidoc
index cd38e354bd..201f7550b3 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-disabling-of-selinux.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-disabling-of-selinux.asciidoc
@@ -3,92 +3,120 @@
 
 Identifies potential attempts to disable Security-Enhanced Linux (SELinux), which is a Linux kernel security feature to support access control policies. Adversaries may disable security tools to avoid possible detection of their tools and activities.
 
-*Rule type*: query
+*Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<potential-disabling-of-selinux-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
 
-*Added ({stack} release)*: 7.8.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
 
+==== Setup
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:setenforce and process.args:0
-----------------------------------
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+*Setup*
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Impair Defenses
-** ID: T1562
-** Reference URL: https://attack.mitre.org/techniques/T1562/
 
-[[potential-disabling-of-selinux-history]]
-==== Rule version history
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
 
-Version 100 (8.5.0 release)::
-* Formatting only
+*Prerequisite Requirements:*
 
-Version 8 (8.4.0 release)::
-* Formatting only
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 7 (7.12.0 release)::
-* Formatting only
 
-Version 6 (7.11.2 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
 
-Version 5 (7.11.0 release)::
-* Formatting only
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Version 4 (7.10.0 release)::
-* Formatting only
 
-Version 3 (7.9.1 release)::
-* Formatting only
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
+
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:executed and process.name:setenforce and process.args:0
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "setenforce" and process.args == "0"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-dll-side-loading-via-microsoft-antimalware-service-executable.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-dll-side-loading-via-microsoft-antimalware-service-executable.asciidoc
index cabd350f77..820b6ab2a3 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-dll-side-loading-via-microsoft-antimalware-service-executable.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-dll-side-loading-via-microsoft-antimalware-service-executable.asciidoc
@@ -5,76 +5,79 @@ Identifies a Windows trusted program that is known to be vulnerable to DLL Searc
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://news.sophos.com/en-us/2021/07/04/independence-day-revil-uses-supply-chain-exploit-to-attack-hundreds-of-businesses/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
-
-*Version*: 101 (<<potential-dll-side-loading-via-microsoft-antimalware-service-executable-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Dennis Perto
+* Elastic
+* Dennis Perto
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Microsoft Antimalware Service Executable installed on non default installation path.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and
-(process.pe.original_file_name == "MsMpEng.exe" and not process.name :
-"MsMpEng.exe") or (process.name : "MsMpEng.exe" and not
-process.executable : ("?:\\ProgramData\\Microsoft\\Windows
-Defender\\*.exe", "?:\\Program
-Files\\Windows Defender\\*.exe",
-"?:\\Program Files (x86)\\Windows Defender\\*.exe",
-"?:\\Program Files\\Microsoft Security Client\\*.exe",
-"?:\\Program Files (x86)\\Microsoft Security Client\\*.exe"))
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+(
+  (process.pe.original_file_name == "MsMpEng.exe" and not process.name : "MsMpEng.exe") or
+  (process.name : "MsMpEng.exe" and not
+        process.executable : ("?:\\ProgramData\\Microsoft\\Windows Defender\\*.exe",
+                              "?:\\Program Files\\Windows Defender\\*.exe",
+                              "?:\\Program Files (x86)\\Windows Defender\\*.exe",
+                              "?:\\Program Files\\Microsoft Security Client\\*.exe",
+                              "?:\\Program Files (x86)\\Microsoft Security Client\\*.exe"))
+)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -86,33 +89,7 @@ Files\\Windows Defender\\*.exe",
 ** Name: Hijack Execution Flow
 ** ID: T1574
 ** Reference URL: https://attack.mitre.org/techniques/T1574/
-
-[[potential-dll-side-loading-via-microsoft-antimalware-service-executable-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and
-(process.pe.original_file_name == "MsMpEng.exe" and not process.name :
-"MsMpEng.exe") or (process.name : "MsMpEng.exe" and not
-process.executable : ("?:\\ProgramData\\Microsoft\\Windows
-Defender\\*.exe", "?:\\Program
-Files\\Windows Defender\\*.exe",
-"?:\\Program Files (x86)\\Windows Defender\\*.exe"))
-----------------------------------
-
+* Sub-technique:
+** Name: DLL Side-Loading
+** ID: T1574.002
+** Reference URL: https://attack.mitre.org/techniques/T1574/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-dll-side-loading-via-trusted-microsoft-programs.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-dll-side-loading-via-trusted-microsoft-programs.asciidoc
new file mode 100644
index 0000000000..cbaf790a10
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-dll-side-loading-via-trusted-microsoft-programs.asciidoc
@@ -0,0 +1,96 @@
+[[potential-dll-side-loading-via-trusted-microsoft-programs]]
+=== Potential DLL Side-Loading via Trusted Microsoft Programs
+
+Identifies an instance of a Windows trusted program that is known to be vulnerable to DLL Search Order Hijacking starting after being renamed or from a non-standard path. This is uncommon behavior and may indicate an attempt to evade defenses via side loading a malicious DLL within the memory space of one of those processes.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 110
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.pe.original_file_name in ("WinWord.exe", "EXPLORER.EXE", "w3wp.exe", "DISM.EXE") and
+  not (process.name : ("winword.exe", "explorer.exe", "w3wp.exe", "Dism.exe") or
+         process.executable : ("?:\\Windows\\explorer.exe",
+                               "?:\\Program Files\\Microsoft Office\\root\\Office*\\WINWORD.EXE",
+                               "?:\\Program Files?(x86)\\Microsoft Office\\root\\Office*\\WINWORD.EXE",
+                               "?:\\Windows\\System32\\Dism.exe",
+                               "?:\\Windows\\SysWOW64\\Dism.exe",
+                               "?:\\Windows\\System32\\inetsrv\\w3wp.exe")
+         )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: DLL Side-Loading
+** ID: T1574.002
+** Reference URL: https://attack.mitre.org/techniques/T1574/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-dns-tunneling-via-nslookup.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-dns-tunneling-via-nslookup.asciidoc
index 527ec8272a..cbcccad5e2 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-dns-tunneling-via-nslookup.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-dns-tunneling-via-nslookup.asciidoc
@@ -3,112 +3,107 @@
 
 This rule identifies a large number (15) of nslookup.exe executions with an explicit query type from the same host. This may indicate command and control activity utilizing the DNS protocol.
 
-*Rule type*: threshold
+*Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://unit42.paloaltonetworks.com/dns-tunneling-in-the-wild-overview-of-oilrigs-dns-tunneling/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<potential-dns-tunneling-via-nslookup-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Potential DNS Tunneling via NsLookup
+*Triage and analysis*
+
+
+
+*Investigating Potential DNS Tunneling via NsLookup*
 
-Attackers can abuse existing network rules that allow DNS communication with external resources to use the protocol as
-their command and control and/or exfiltration channel.
 
-DNS queries can be used to infiltrate data such as commands to be run, malicious files, etc., and also for exfiltration,
-since queries can be used to send data to the attacker-controlled DNS server. This process is commonly known as DNS tunneling.
+Attackers can abuse existing network rules that allow DNS communication with external resources to use the protocol as their command and control and/or exfiltration channel.
 
-More information on how tunneling works and how it can be abused can be found on
-[Palo Alto Unit42 Research](https://unit42.paloaltonetworks.com/dns-tunneling-how-dns-can-be-abused-by-malicious-actors).
+DNS queries can be used to infiltrate data such as commands to be run, malicious files, etc., and also for exfiltration, since queries can be used to send data to the attacker-controlled DNS server. This process is commonly known as DNS tunneling.
 
-#### Possible investigation steps
+More information on how tunneling works and how it can be abused can be found on https://unit42.paloaltonetworks.com/dns-tunneling-how-dns-can-be-abused-by-malicious-actors[Palo Alto Unit42 Research].
 
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+*Possible investigation steps*
+
+
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Inspect the DNS query and identify the information sent.
-- Extract this communication's indicators of compromise (IoCs) and use traffic logs to search for other potentially
-compromised hosts.
+- Extract this communication's indicators of compromise (IoCs) and use traffic logs to search for other potentially compromised hosts.
+
+
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. If the parent process is trusted and the data sent is not sensitive nor command and control related, this alert can be closed.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. If the parent process is trusted and the data sent is not sensitive nor
-command and control related, this alert can be closed.
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
 - Immediately block the identified indicators of compromise (IoCs).
 - Implement any temporary network rules, procedures, and segmentation required to contain the attack.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Update firewall rules to be more restrictive.
 - Reimage the host operating system or restore the compromised files to clean versions.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:start and
-process.name:nslookup.exe and process.args:(-querytype=* or -qt=* or
--q=* or -type=*)
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=5m
+[process where host.os.type == "windows" and event.type == "start" and
+  process.name : "nslookup.exe" and process.args:("-querytype=*", "-qt=*", "-q=*", "-type=*")] with runs = 10
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -120,28 +115,11 @@ process.name:nslookup.exe and process.args:(-querytype=* or -qt=* or
 ** Name: Application Layer Protocol
 ** ID: T1071
 ** Reference URL: https://attack.mitre.org/techniques/T1071/
-
-[[potential-dns-tunneling-via-nslookup-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.16.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: DNS
+** ID: T1071.004
+** Reference URL: https://attack.mitre.org/techniques/T1071/004/
+* Technique:
+** Name: Protocol Tunneling
+** ID: T1572
+** Reference URL: https://attack.mitre.org/techniques/T1572/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-enumeration-via-active-directory-web-service.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-enumeration-via-active-directory-web-service.asciidoc
new file mode 100644
index 0000000000..c8123621e0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-enumeration-via-active-directory-web-service.asciidoc
@@ -0,0 +1,74 @@
+[[potential-enumeration-via-active-directory-web-service]]
+=== Potential Enumeration via Active Directory Web Service
+
+Identifies processes loading Active Directory related modules followed by a network connection to the ADWS dedicated TCP port. Adversaries may abuse the ADWS Windows service that allows Active Directory to be queried via this web service.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+* logs-endpoint.events.network-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/FalconForceTeam/SOAPHound
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by process.entity_id with maxspan=3m
+ [library where host.os.type == "windows" and 
+  dll.name : ("System.DirectoryServices*.dll", "System.IdentityModel*.dll") and 
+  not user.id in ("S-1-5-18", "S-1-5-19", "S-1-5-20") and 
+  not process.executable : 
+                ("?:\\windows\\system32\\dsac.exe", 
+                 "?:\\program files\\powershell\\?\\pwsh.exe", 
+                 "?:\\windows\\system32\\windowspowershell\\*.exe", 
+                 "?:\\windows\\syswow64\\windowspowershell\\*.exe", 
+                 "?:\\program files\\microsoft monitoring agent\\*.exe", 
+                 "?:\\windows\\adws\\microsoft.activedirectory.webservices.exe")]
+ [network where host.os.type == "windows" and destination.port == 9389 and source.port >= 49152 and
+  network.direction == "egress" and network.transport == "tcp" and not cidrmatch(destination.ip, "127.0.0.0/8", "::1/128")]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Remote System Discovery
+** ID: T1018
+** Reference URL: https://attack.mitre.org/techniques/T1018/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-evasion-via-filter-manager.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-evasion-via-filter-manager.asciidoc
index 5b92c09045..b23f818c76 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-evasion-via-filter-manager.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-evasion-via-filter-manager.asciidoc
@@ -5,129 +5,144 @@ The Filter Manager Control Program (fltMC.exe) binary may be abused by adversari
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<potential-evasion-via-filter-manager-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Potential Evasion via Filter Manager*
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "fltMC.exe"
-and process.args : "unload"
-----------------------------------
 
-==== Threat mapping
+A file system filter driver, or minifilter, is a specialized type of filter driver designed to intercept and modify I/O requests sent to a file system or another filter driver. Minifilters are used by a wide range of security software, including EDR, antivirus, backup agents, encryption products, etc.
 
-*Framework*: MITRE ATT&CK^TM^
+Attackers may try to unload minifilters to avoid protections such as malware detection, file system monitoring, and behavior-based detections.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Impair Defenses
-** ID: T1562
-** Reference URL: https://attack.mitre.org/techniques/T1562/
+This rule identifies the attempt to unload a minifilter using the `fltmc.exe` command-line utility, a tool used to manage and query the filter drivers loaded on Windows systems.
 
-[[potential-evasion-via-filter-manager-history]]
-==== Rule version history
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "fltMC.exe" and process.args : "unload"
-----------------------------------
+*Possible investigation steps*
 
-Version 11 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "fltMC.exe" and process.args : "unload"
-----------------------------------
 
-Version 9 (8.2.0 release)::
-* Formatting only
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Examine the command line event to identify the target driver.
+  - Identify the minifilter's role in the environment and if it is security-related. Microsoft provides a https://learn.microsoft.com/en-us/windows-hardware/drivers/ifs/allocated-altitudes[list] of allocated altitudes that may provide more context, such as the manufacturer.
+- Contact the account owner and confirm whether they are aware of this activity.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Observe and collect information about the following activities in the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
 
-Version 8 (7.16.0 release)::
-* Formatting only
 
-Version 7 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:fltMC.exe
-----------------------------------
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity and there are justifications for the action.
+
 
-Version 6 (7.12.0 release)::
-* Formatting only
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
 
-Version 5 (7.11.2 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.code:1 and process.name:fltMC.exe
-----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "fltMC.exe" and process.args : "unload" and
+  not
+  (
+    (
+      process.executable : "?:\\Program Files (x86)\\ManageEngine\\UEMS_Agent\\bin\\DCFAService64.exe" and
+      process.args : ("DFMFilter", "DRMFilter")
+    ) or
+    (
+      process.executable : "?:\\Windows\\SysWOW64\\msiexec.exe" and
+      process.args : ("BrFilter_*", "BrCow_*") and
+      user.id : "S-1-5-18"
+    )
+  )
 
-Version 3 (7.9.0 release)::
-* Formatting only
+----------------------------------
 
-Version 2 (7.7.0 release)::
-* Formatting only
+*Framework*: MITRE ATT&CK^TM^
 
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-evasion-via-windows-filtering-platform.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-evasion-via-windows-filtering-platform.asciidoc
new file mode 100644
index 0000000000..b9d99df04a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-evasion-via-windows-filtering-platform.asciidoc
@@ -0,0 +1,134 @@
+[[potential-evasion-via-windows-filtering-platform]]
+=== Potential Evasion via Windows Filtering Platform
+
+Identifies multiple Windows Filtering Platform block events and where the process name is related to an endpoint security software. Adversaries may add malicious WFP rules to prevent Endpoint security from sending telemetry.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.network-*
+* logs-system.security-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/dsnezhkov/shutter/tree/main
+* https://github.com/netero1010/EDRSilencer/tree/main
+* https://www.mdsec.co.uk/2023/09/nighthawk-0-2-6-three-wise-monkeys/
+* https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-5157
+* https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-5152
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Filtering Platform Connection' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+Object Access >
+Filtering Platform Connection (Success,Failure)
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by winlog.computer_name with maxspan=1m
+ [network where host.os.type == "windows" and 
+  event.action : ("windows-firewall-packet-block", "windows-firewall-packet-drop") and 
+  process.name : (
+        "bdagent.exe", "bdreinit.exe", "pdscan.exe", "pdiface.exe", "BDSubWiz.exe", "ProductAgentService.exe",
+        "ProductAgentUI.exe", "WatchDog.exe", "CarbonBlackClientSetup.exe", "TrGUI.exe", "TracCAPI.exe", "cpmsi_tool.exe",
+        "trac.exe", "vna_install64.exe", "vna_utils.exe", "TracSrvWrapper.exe", "vsmon.exe", "p95tray.exe",
+        "CybereasonRansomFreeServiceHost.exe", "CrAmTray.exe", "minionhost.exe", "CybereasonSensor.exe", "CylanceUI.exe",
+        "CylanceProtectSetup.exe", "cylancesvc.exe", "cyupdate.exe", "elastic-agent.exe", "elastic-endpoint.exe",
+        "egui.exe", "minodlogin.exe", "emu-rep.exe", "emu_install.exe", "emu-cci.exe", "emu-gui.exe", "emu-uninstall.exe",
+        "ndep.exe", "spike.exe", "ecls.exe", "ecmd.exe", "ecomserver.exe", "eeclnt.exe", "eh64.exe", "EHttpSrv.exe",
+        "xagt.exe", "collectoragent.exe", "FSAEConfig.exe", "uninstalldcagent.exe", "rmon.exe", "fccomint.exe",
+        "fclanguageselector.exe", "fortifw.exe", "fcreg.exe", "fortitray.exe", "fcappdb.exe", "fcwizard.exe", "submitv.exe",
+        "av_task.exe", "fortiwf.exe", "fortiwadbd.exe", "fcauth.exe", "fcdblog.exe", "fcmgr.exe", "fortiwad.exe",
+        "fortiproxy.exe", "fortiscand.exe", "fortivpnst.exe", "ipsec.exe", "fcwscd7.exe", "fcasc.exe", "fchelper.exe",
+        "forticlient.exe","fcwsc.exe", "FortiClient.exe", "fmon.exe", "FSSOMA.exe", "FCVbltScan.exe", "FortiESNAC.exe",
+        "EPCUserAvatar.exe", "FortiAvatar.exe", "FortiClient_Diagnostic_Tool.exe", "FortiSSLVPNdaemon.exe", "avp.exe",
+        "FCConfig.exe", "avpsus.exe", "klnagent.exe", "klnsacwsrv.exe", "kl_platf.exe", "stpass.exe", "klnagwds.exe",
+        "mbae.exe", "mbae64.exe", "mbae-svc.exe", "mbae-uninstaller.exe", "mbaeLoader32.exe", "mbaeloader64.exe",
+        "mbam-dor.exe", "mbamgui.exe", "mbamservice.exe", "mbamtrayctrl.exe", "mbampt.exe", "mbamscheduler.exe",
+        "Coreinst.exe", "mbae-setup.exe", "mcupdate.exe", "ProtectedModuleHost.exe", "ESConfigTool.exe", "FWInstCheck.exe",
+        "FwWindowsFirewallHandler.exe", "mfeesp.exe", "mfefw.exe", "mfeProvisionModeUtility.exe", "mfetp.exe", "avpui.exe", 
+        "WscAVExe.exe", "mcshield.exe", "McChHost.exe", "mfewc.exe", "mfewch.exe", "mfewcui.exe", "fwinfo.exe",
+        "mfecanary.exe", "mfefire.exe", "mfehidin.exe", "mfemms.exe", "mfevtps.exe", "mmsinfo.exe", "vtpinfo.exe",
+        "MarSetup.exe", "mctray.exe", "masvc.exe", "macmnsvc.exe", "McAPExe.exe", "McPvTray.exe", "mcods.exe",
+        "mcuicnt.exe", "mcuihost.exe", "xtray.exe", "McpService.exe", "epefprtrainer.exe", "mfeffcoreservice.exe",
+        "MfeEpeSvc.exe", "qualysagent.exe", "QualysProxy.exe", "QualysAgentUI.exe", "SVRTgui.exe", "SVRTcli.exe",
+        "SVRTcli.exe", "SVRTgui.exe", "SCTCleanupService.exe", "SVRTservice.exe", "native.exe", "SCTBootTasks.exe",
+        "ALMon.exe", "SAA.exe", "SUMService.exe", "ssp.exe", "SCFService.exe", "SCFManager.exe", "spa.exe", "cabarc.exe",
+        "sargui.exe", "sntpservice.exe", "McsClient.exe", "McsAgent.exe", "McsHeartbeat.exe", "SAVAdminService.exe",
+        "sav32cli.exe", "ForceUpdateAlongSideSGN.exe", "SAVCleanupService.exe", "SavMain.exe", "SavProgress.exe", 
+        "SavProxy.exe", "SavService.exe", "swc_service.exe", "swi_di.exe", "swi_service.exe", "swi_filter.exe",
+        "ALUpdate.exe", "SophosUpdate.exe", "ALsvc.exe", "SophosAlert.exe", "osCheck.exe", "N360Downloader.exe",
+        "InstWrap.exe", "symbos.exe", "nss.exe", "symcorpui.exe", "isPwdSvc.exe", "ccsvchst.exe", "ntrmv.exe",
+        "pccntmon.exe", "AosUImanager.exe", "NTRTScan.exe", "TMAS_OL.exe", "TMAS_OLImp.exe", "TMAS_OLSentry.exe",
+        "ufnavi.exe", "Clnrbin.exe", "vizorhtmldialog.exe", "pwmConsole.exe", "PwmSvc.exe", "coreServiceShell.exe",
+        "ds_agent.exe", "SfCtlCom.exe", "MBAMHelper.exe", "cb.exe", "smc.exe", "tda.exe", "xagtnotif.exe", "ekrn.exe",
+        "dsa.exe", "Notifier.exe", "rphcp.exe", "lc_sensor.exe", "CSFalconService.exe", "CSFalconController.exe",
+        "SenseSampleUploader.exe", "windefend.exe", "MSASCui.exe", "MSASCuiL.exe", "msmpeng.exe", "msmpsvc.exe",
+        "MsSense.exe", "esensor.exe", "sentinelone.exe", "tmccsf.exe", "csfalconcontainer.exe", "sensecncproxy.exe",
+        "splunk.exe", "sysmon.exe", "sysmon64.exe", "taniumclient.exe"
+    )] with runs=5
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify System Firewall
+** ID: T1562.004
+** Reference URL: https://attack.mitre.org/techniques/T1562/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-execution-via-xzbackdoor.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-execution-via-xzbackdoor.asciidoc
new file mode 100644
index 0000000000..ccdaca43f7
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-execution-via-xzbackdoor.asciidoc
@@ -0,0 +1,98 @@
+[[potential-execution-via-xzbackdoor]]
+=== Potential Execution via XZBackdoor
+
+It identifies potential malicious shell executions through remote SSH and detects cases where the sshd service suddenly terminates soon after successful execution, suggesting suspicious behavior similar to the XZ backdoor.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/amlweems/xzbot
+* https://access.redhat.com/security/cve/CVE-2024-3094
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Persistence
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, user.id with maxspan=1s
+ [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and process.name == "sshd" and
+    process.args == "-D" and process.args == "-R"] by process.pid, process.entity_id
+ [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and process.parent.name == "sshd" and 
+  process.executable != "/usr/sbin/sshd"] by process.parent.pid, process.parent.entity_id
+ [process where host.os.type == "linux" and event.action == "end" and process.name == "sshd" and process.exit_code != 0] by process.pid, process.entity_id
+ [network where host.os.type == "linux" and event.type == "end" and event.action == "disconnect_received" and process.name == "sshd"] by process.pid, process.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Modify Authentication Process
+** ID: T1556
+** Reference URL: https://attack.mitre.org/techniques/T1556/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SSH
+** ID: T1021.004
+** Reference URL: https://attack.mitre.org/techniques/T1021/004/
+* Technique:
+** Name: Remote Service Session Hijacking
+** ID: T1563
+** Reference URL: https://attack.mitre.org/techniques/T1563/
+* Sub-technique:
+** Name: SSH Hijacking
+** ID: T1563.001
+** Reference URL: https://attack.mitre.org/techniques/T1563/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-exploitation-of-an-unquoted-service-path-vulnerability.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-exploitation-of-an-unquoted-service-path-vulnerability.asciidoc
new file mode 100644
index 0000000000..121c8dfd5f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-exploitation-of-an-unquoted-service-path-vulnerability.asciidoc
@@ -0,0 +1,67 @@
+[[potential-exploitation-of-an-unquoted-service-path-vulnerability]]
+=== Potential Exploitation of an Unquoted Service Path Vulnerability
+
+Adversaries may leverage unquoted service path vulnerabilities to escalate privileges. By placing an executable in a higher-level directory within the path of an unquoted service executable, Windows will natively launch this executable from its defined path variable instead of the benign one in a deeper directory, thus leading to code execution.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and 
+  (
+    process.executable : "?:\\Program.exe" or 
+    process.executable regex """(C:\\Program Files \(x86\)\\|C:\\Program Files\\)\w+.exe"""
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: Path Interception by Unquoted Path
+** ID: T1574.009
+** Reference URL: https://attack.mitre.org/techniques/T1574/009/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-external-linux-ssh-brute-force-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-external-linux-ssh-brute-force-detected.asciidoc
new file mode 100644
index 0000000000..95759e6540
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-external-linux-ssh-brute-force-detected.asciidoc
@@ -0,0 +1,159 @@
+[[potential-external-linux-ssh-brute-force-detected]]
+=== Potential External Linux SSH Brute Force Detected
+
+Identifies multiple external consecutive login failures targeting a user account from the same source address within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to these accounts.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-system.auth-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 5
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential External Linux SSH Brute Force Detected*
+
+
+The rule identifies consecutive SSH login failures targeting a user account from the same source IP address to the same target host indicating brute force login attempts.
+
+This rule will generate a lot of noise for systems with a front-facing SSH service, as adversaries scan the internet for remotely accessible SSH services and try to brute force them to gain unauthorized access. 
+
+In case this rule generates too much noise and external brute forcing is of not much interest, consider turning this rule off and enabling "Potential Internal Linux SSH Brute Force Detected" to detect internal brute force attempts.
+
+
+*Possible investigation steps*
+
+
+- Investigate the login failure user name(s).
+- Investigate the source IP address of the failed ssh login attempt(s).
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Identify the source and the target computer and their roles in the IT environment.
+
+
+*False positive analysis*
+
+
+- Authentication misconfiguration or obsolete credentials.
+- Service account password expired.
+- Infrastructure or availability issue.
+
+
+*Related Rules*
+
+
+- Potential Internal Linux SSH Brute Force Detected - 1c27fa22-7727-4dd3-81c0-de6da5555feb
+- Potential SSH Password Guessing - 8cb84371-d053-4f4f-bce0-c74990e28f28
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Filebeat.
+
+
+*Filebeat Setup*
+
+Filebeat is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to Elasticsearch or Logstash for indexing.
+
+
+*The following steps should be executed in order to add the Filebeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html[helper guide].
+- To run Filebeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-docker.html[helper guide].
+- To run Filebeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html[helper guide].
+- For quick start information for Filebeat refer to the https://www.elastic.co/guide/en/beats/filebeat/8.11/filebeat-installation-configuration.html[helper guide].
+- For complete “Setup and Run Filebeat” information refer to the https://www.elastic.co/guide/en/beats/filebeat/current/setting-up-and-running.html[helper guide].
+
+
+*Rule Specific Setup Note*
+
+- This rule requires the “Filebeat System Module” to be enabled.
+- The system module collects and parses logs created by the system logging service of common Unix/Linux based distributions.
+- To run the system module of Filebeat on Linux follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-system.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, source.ip, user.name with maxspan=15s
+  [ authentication where host.os.type == "linux" and 
+   event.action in ("ssh_login", "user_login") and event.outcome == "failure" and
+   not cidrmatch(source.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
+       "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32",
+       "192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
+       "100.64.0.0/10", "192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", 
+       "::1", "FE80::/10", "FF00::/8") ] with runs = 10
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Brute Force
+** ID: T1110
+** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Sub-technique:
+** Name: Password Guessing
+** ID: T1110.001
+** Reference URL: https://attack.mitre.org/techniques/T1110/001/
+* Sub-technique:
+** Name: Password Spraying
+** ID: T1110.003
+** Reference URL: https://attack.mitre.org/techniques/T1110/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-file-download-via-a-headless-browser.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-file-download-via-a-headless-browser.asciidoc
new file mode 100644
index 0000000000..0debd4c5de
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-file-download-via-a-headless-browser.asciidoc
@@ -0,0 +1,108 @@
+[[potential-file-download-via-a-headless-browser]]
+=== Potential File Download via a Headless Browser
+
+Identifies the use of a browser to download a file from a remote URL and from a suspicious parent process. Adversaries may use browsers to avoid ingress tool transfer restrictions.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://lolbas-project.github.io/lolbas/Binaries/Msedge/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Windows
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential File Download via a Headless Browser*
+
+
+- Investigate the process execution chain (parent process tree).
+- Investigate the process network and file events.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.name : ("chrome.exe", "msedge.exe", "brave.exe", "browser.exe", "dragon.exe", "vivaldi.exe") and
+  (process.args : "--headless*" or process.args : "data:text/html;base64,*") and
+  process.parent.name :
+     ("cmd.exe", "powershell.exe", "wscript.exe", "cscript.exe", "mshta.exe", "conhost.exe", "msiexec.exe",
+      "explorer.exe", "rundll32.exe", "winword.exe", "excel.exe", "onenote.exe", "hh.exe", "powerpnt.exe", "forfiles.exe",
+      "pcalua.exe", "wmiprvse.exe")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Ingress Tool Transfer
+** ID: T1105
+** Reference URL: https://attack.mitre.org/techniques/T1105/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-file-transfer-via-certreq.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-file-transfer-via-certreq.asciidoc
new file mode 100644
index 0000000000..197a4fe982
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-file-transfer-via-certreq.asciidoc
@@ -0,0 +1,152 @@
+[[potential-file-transfer-via-certreq]]
+=== Potential File Transfer via Certreq
+
+Identifies Certreq making an HTTP Post request. Adversaries could abuse Certreq to download files or upload data to a remote URL.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://lolbas-project.github.io/lolbas/Binaries/Certreq/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Command and Control
+* Tactic: Exfiltration
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential File Transfer via Certreq*
+
+
+Certreq is a command-line utility in Windows operating systems that allows users to request and manage certificates from certificate authorities. It is primarily used for generating certificate signing requests (CSRs) and installing certificates. However, adversaries may abuse Certreq's functionality to download files or upload data to a remote URL by making an HTTP POST request.
+
+This rule identifies the potential abuse of Certreq to download files or upload data to a remote URL.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Examine the details of the dropped file, and whether it was executed.
+- Check the reputation of the domain or IP address used to host the downloaded file or if the user downloaded the file from an internal system.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the file using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- This activity is unusual but can be done by administrators. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ (process.name : "CertReq.exe" or ?process.pe.original_file_name == "CertReq.exe") and process.args : "-Post"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Ingress Tool Transfer
+** ID: T1105
+** Reference URL: https://attack.mitre.org/techniques/T1105/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over Web Service
+** ID: T1567
+** Reference URL: https://attack.mitre.org/techniques/T1567/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-hidden-local-user-account-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-hidden-local-user-account-creation.asciidoc
index 45682a096f..d70a02e17a 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-hidden-local-user-account-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-hidden-local-user-account-creation.asciidoc
@@ -5,54 +5,87 @@ Identifies attempts to create a local account that will be hidden from the macOS
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.apple.com/en-us/HT203998
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<potential-hidden-local-user-account-creation-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:dscl and process.args:(IsHidden and create and (true or 1
-or yes))
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+ process.name:dscl and process.args:(IsHidden and create and (true or 1 or yes))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,13 +97,7 @@ or yes))
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[potential-hidden-local-user-account-creation-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Local Accounts
+** ID: T1078.003
+** Reference URL: https://attack.mitre.org/techniques/T1078/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-hidden-process-via-mount-hidepid.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-hidden-process-via-mount-hidepid.asciidoc
new file mode 100644
index 0000000000..7b0c90cefe
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-hidden-process-via-mount-hidepid.asciidoc
@@ -0,0 +1,105 @@
+[[potential-hidden-process-via-mount-hidepid]]
+=== Potential Hidden Process via Mount Hidepid
+
+Identifies the execution of mount process with hidepid parameter, which can make processes invisible to other users from the system. Adversaries using Linux kernel version 3.2+ (or RHEL/CentOS v6.5+ above) can hide the process from other users. When hidepid=2 option is executed to mount the /proc filesystem, only the root user can see all processes and the logged-in user can only see their own process. This provides a defense evasion mechanism for the adversaries to hide their process executions from all other commands such as ps, top, pgrep and more. With the Linux kernel hardening hidepid option all the user has to do is remount the /proc filesystem with the option, which can now be monitored and detected.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.cyberciti.biz/faq/linux-hide-processes-from-other-users/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "mount" and process.args == "/proc" and process.args == "-o" and
+process.args : "*hidepid=2*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hide Artifacts
+** ID: T1564
+** Reference URL: https://attack.mitre.org/techniques/T1564/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-internal-linux-ssh-brute-force-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-internal-linux-ssh-brute-force-detected.asciidoc
new file mode 100644
index 0000000000..a9cccd432e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-internal-linux-ssh-brute-force-detected.asciidoc
@@ -0,0 +1,155 @@
+[[potential-internal-linux-ssh-brute-force-detected]]
+=== Potential Internal Linux SSH Brute Force Detected
+
+Identifies multiple internal consecutive login failures targeting a user account from the same source address within a short time interval. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to these accounts.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-system.auth-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 5
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+
+*Version*: 11
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Internal Linux SSH Brute Force Detected*
+
+
+The rule identifies consecutive internal SSH login failures targeting a user account from the same source IP address to the same target host indicating brute force login attempts.
+
+
+*Possible investigation steps*
+
+
+- Investigate the login failure user name(s).
+- Investigate the source IP address of the failed ssh login attempt(s).
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Identify the source and the target computer and their roles in the IT environment.
+
+
+*False positive analysis*
+
+
+- Authentication misconfiguration or obsolete credentials.
+- Service account password expired.
+- Infrastructure or availability issue.
+
+
+*Related Rules*
+
+
+- Potential External Linux SSH Brute Force Detected - fa210b61-b627-4e5e-86f4-17e8270656ab
+- Potential SSH Password Guessing - 8cb84371-d053-4f4f-bce0-c74990e28f28
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Filebeat.
+
+
+*Filebeat Setup*
+
+Filebeat is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to Elasticsearch or Logstash for indexing.
+
+
+*The following steps should be executed in order to add the Filebeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html[helper guide].
+- To run Filebeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-docker.html[helper guide].
+- To run Filebeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html[helper guide].
+- For quick start information for Filebeat refer to the https://www.elastic.co/guide/en/beats/filebeat/8.11/filebeat-installation-configuration.html[helper guide].
+- For complete “Setup and Run Filebeat” information refer to the https://www.elastic.co/guide/en/beats/filebeat/current/setting-up-and-running.html[helper guide].
+
+
+*Rule Specific Setup Note*
+
+- This rule requires the “Filebeat System Module” to be enabled.
+- The system module collects and parses logs created by the system logging service of common Unix/Linux based distributions.
+- To run the system module of Filebeat on Linux follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-system.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, source.ip, user.name with maxspan=15s
+  [ authentication where host.os.type == "linux" and 
+   event.action in ("ssh_login", "user_login") and event.outcome == "failure" and
+   cidrmatch(source.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
+       "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32",
+       "192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
+       "100.64.0.0/10", "192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", 
+       "::1", "FE80::/10", "FF00::/8") ] with runs = 10
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Brute Force
+** ID: T1110
+** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Sub-technique:
+** Name: Password Guessing
+** ID: T1110.001
+** Reference URL: https://attack.mitre.org/techniques/T1110/001/
+* Sub-technique:
+** Name: Password Spraying
+** ID: T1110.003
+** Reference URL: https://attack.mitre.org/techniques/T1110/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-invoke-mimikatz-powershell-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-invoke-mimikatz-powershell-script.asciidoc
index e23d226c09..6199ec9bd6 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-invoke-mimikatz-powershell-script.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-invoke-mimikatz-powershell-script.asciidoc
@@ -5,86 +5,84 @@ Mimikatz is a credential dumper capable of obtaining plaintext Windows account l
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://attack.mitre.org/software/S0002/
 * https://raw.githubusercontent.com/EmpireProject/Empire/master/data/module_source/credentials/Invoke-Mimikatz.ps1
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
-
-*Version*: 102 (<<potential-invoke-mimikatz-powershell-script-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
 
-*Added ({stack} release)*: 8.3.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Mimikatz PowerShell Activity
+*Triage and analysis*
+
+
+
+*Investigating Mimikatz PowerShell Activity*
+
 
-[Mimikatz](https://github.com/gentilkiwi/mimikatz) is an open-source tool used to collect, decrypt, and/or use cached
-credentials. This tool is commonly abused by adversaries during the post-compromise stage where adversaries have gained
-an initial foothold on an endpoint and are looking to elevate privileges and seek out additional authentication objects
-such as tokens/hashes/credentials that can then be used to move laterally and pivot across a network.
+https://github.com/gentilkiwi/mimikatz[Mimikatz] is an open-source tool used to collect, decrypt, and/or use cached credentials. This tool is commonly abused by adversaries during the post-compromise stage where adversaries have gained an initial foothold on an endpoint and are looking to elevate privileges and seek out additional authentication objects such as tokens/hashes/credentials that can then be used to move laterally and pivot across a network.
 
-This rule looks for PowerShell scripts that load mimikatz in memory, like Invoke-Mimikataz, which are used to dump
-credentials from the Local Security Authority Subsystem Service (LSASS). Any activity triggered from this rule should be
-treated with high priority as it typically represents an active adversary.
+This rule looks for PowerShell scripts that load mimikatz in memory, like Invoke-Mimikataz, which are used to dump credentials from the Local Security Authority Subsystem Service (LSASS). Any activity triggered from this rule should be treated with high priority as it typically represents an active adversary.
 
-More information about Mimikatz components and how to detect/prevent them can be found on [ADSecurity](https://adsecurity.org/?page_id=1821).
+More information about Mimikatz components and how to detect/prevent them can be found on https://adsecurity.org/?page_id=1821[ADSecurity].
 
-#### Possible investigation steps
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Examine file or network events from the involved PowerShell process for suspicious behavior.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-  - Invoke-Mimitakz and alike scripts heavily use other capabilities covered by other detections described in the
-  "Related Rules" section.
+  - Invoke-Mimitakz and alike scripts heavily use other capabilities covered by other detections described in the "Related Rules" section.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
-- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the
-target host.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host.
   - Examine network and security events in the environment to identify potential lateral movement using compromised credentials.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Related rules
+
+*Related rules*
+
 
 - PowerShell PSReflect Script - 56f2e9b5-4803-4e44-a0a4-a52dc79d57fe
 - Suspicious .NET Reflection via PowerShell - e26f042e-c590-4e82-8e05-41e81bd822ad
@@ -93,36 +91,61 @@ target host.
 - Mimikatz Memssp Log File Detected - ebb200e8-adf0-43f8-a0bb-4ee5b5d852c6
 - Modification of WDigest Security Provider - d703a5af-d5b0-43bd-8ddb-7a5d500b7da5
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
 - Validate that cleartext passwords are disabled in memory for use with `WDigest`.
-- Look into preventing access to `LSASS` using capabilities such as LSA protection or antivirus/EDR tools that provide
-this capability.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Look into preventing access to `LSASS` using capabilities such as LSA protection or antivirus/EDR tools that provide this capability.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be configured (Enable).
+
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and powershell.file.script_block_text:(
-(DumpCreds and DumpCerts) or "sekurlsa::logonpasswords" or
-("crypto::certificates" and "CERT_SYSTEM_STORE_LOCAL_MACHINE") )
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and
+powershell.file.script_block_text:(
+  (DumpCreds and
+  DumpCerts) or
+  "sekurlsa::logonpasswords" or
+  ("crypto::certificates" and
+  "CERT_SYSTEM_STORE_LOCAL_MACHINE")
+)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -134,16 +157,7 @@ event.category:process and powershell.file.script_block_text:(
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[potential-invoke-mimikatz-powershell-script-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-java-jndi-exploitation-attempt.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-java-jndi-exploitation-attempt.asciidoc
index 449e262dbf..cd4233cffc 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-java-jndi-exploitation-attempt.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-java-jndi-exploitation-attempt.asciidoc
@@ -5,7 +5,7 @@ Identifies an outbound network connection by JAVA to LDAP, RMI or DNS standard p
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,13 +14,13 @@ Identifies an outbound network connection by JAVA to LDAP, RMI or DNS standard p
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.lunasec.io/docs/blog/log4j-zero-day/
 * https://github.com/christophetd/log4shell-vulnerable-app
@@ -28,44 +28,57 @@ Identifies an outbound network connection by JAVA to LDAP, RMI or DNS standard p
 * https://www.elastic.co/security-labs/detecting-log4j2-with-elastic-security
 * https://www.elastic.co/security-labs/analysis-of-log4shell-cve-2021-45046
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* macOS
-* Threat Detection
-* Execution
-
-*Version*: 101 (<<potential-java-jndi-exploitation-attempt-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=1m [network where event.action ==
-"connection_attempted" and process.name : "java" and /*
-outbound connection attempt to LDAP, RMI or DNS standard ports
-by JAVA process */ destination.port in (1389, 389, 1099, 53,
-5353)] by process.pid [process where event.type == "start" and /*
-Suspicious JAVA child process */ process.parent.name : "java" and
-process.name : ("sh", "bash",
-"dash", "ksh", "tcsh",
-"zsh", "curl", "perl*",
-"python*", "ruby*", "php*",
-"wget")] by process.parent.pid
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=1m
+ [network where event.action == "connection_attempted" and
+  process.name : "java" and
+  /*
+     outbound connection attempt to
+     LDAP, RMI or DNS standard ports
+     by JAVA process
+   */
+  destination.port in (1389, 389, 1099, 53, 5353)] by process.pid
+ [process where event.type == "start" and
+
+  /* Suspicious JAVA child process */
+  process.parent.name : "java" and
+   process.name : ("sh",
+                   "bash",
+                   "dash",
+                   "ksh",
+                   "tcsh",
+                   "zsh",
+                   "curl",
+                   "perl*",
+                   "python*",
+                   "ruby*",
+                   "php*",
+                   "wget")] by process.parent.pid
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,19 +90,11 @@ process.name : ("sh", "bash",
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[potential-java-jndi-exploitation-attempt-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: JavaScript
+** ID: T1059.007
+** Reference URL: https://attack.mitre.org/techniques/T1059/007/
+* Technique:
+** Name: Exploitation for Client Execution
+** ID: T1203
+** Reference URL: https://attack.mitre.org/techniques/T1203/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-kerberos-attack-via-bifrost.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-kerberos-attack-via-bifrost.asciidoc
index f257e59601..1a3043f387 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-kerberos-attack-via-bifrost.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-kerberos-attack-via-bifrost.asciidoc
@@ -5,56 +5,88 @@ Identifies use of Bifrost, a known macOS Kerberos pentesting tool, which can be
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/its-a-feature/bifrost
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Credential Access
-* Lateral Movement
 
-*Version*: 100 (<<potential-kerberos-attack-via-bifrost-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.12.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:start and
-process.args:("-action" and ("-kerberoast" or askhash or asktgs or
-asktgt or s4u or ("-ticket" and ptt) or (dump and (tickets or
-keytab))))
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:start and
+ process.args:("-action" and ("-kerberoast" or askhash or asktgs or asktgt or s4u or ("-ticket" and ptt) or (dump and (tickets or keytab))))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,8 +98,10 @@ keytab))))
 ** Name: Use Alternate Authentication Material
 ** ID: T1550
 ** Reference URL: https://attack.mitre.org/techniques/T1550/
-
-
+* Sub-technique:
+** Name: Pass the Ticket
+** ID: T1550.003
+** Reference URL: https://attack.mitre.org/techniques/T1550/003/
 * Tactic:
 ** Name: Credential Access
 ** ID: TA0006
@@ -76,24 +110,7 @@ keytab))))
 ** Name: Steal or Forge Kerberos Tickets
 ** ID: T1558
 ** Reference URL: https://attack.mitre.org/techniques/T1558/
-
-[[potential-kerberos-attack-via-bifrost-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:start and
-process.args:("-action" and ("-kerberoast" or askhash or asktgs or
-asktgt or s4u or ("-ticket" and ptt) or (dump and (tickets or
-keytab))))
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Kerberoasting
+** ID: T1558.003
+** Reference URL: https://attack.mitre.org/techniques/T1558/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-lateral-tool-transfer-via-smb-share.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-lateral-tool-transfer-via-smb-share.asciidoc
index d1388ce7d1..023417836c 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-lateral-tool-transfer-via-smb-share.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-lateral-tool-transfer-via-smb-share.asciidoc
@@ -5,58 +5,59 @@ Identifies the creation or change of a Windows executable file over network shar
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
-* winlogbeat-*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-endpoint.events.network-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<potential-lateral-tool-transfer-via-smb-share-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Potential Lateral Tool Transfer via SMB Share
+*Triage and analysis*
+
+
+
+*Investigating Potential Lateral Tool Transfer via SMB Share*
+
+
+Adversaries can use network shares to host tooling to support the compromise of other hosts in the environment. These tools can include discovery utilities, credential dumpers, malware, etc. Attackers can also leverage file shares that employees frequently access to host malicious files to gain a foothold in other machines.
 
-Adversaries can use network shares to host tooling to support the compromise of other hosts in the environment. These tools
-can include discovery utilities, credential dumpers, malware, etc. Attackers can also leverage file shares that employees
-frequently access to host malicious files to gain a foothold in other machines.
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
@@ -70,11 +71,15 @@ for prevalence, whether they are located in expected locations, and if they are
   - Use the PowerShell `Get-FileHash` cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity can happen legitimately. Consider adding exceptions if it is expected and noisy in your environment.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -82,35 +87,29 @@ for prevalence, whether they are located in expected locations, and if they are
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
 - Review the privileges needed to write to the network share and restrict write access as needed.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=30s [network where event.type ==
-"start" and process.pid == 4 and destination.port == 445 and
-network.direction : ("incoming", "ingress") and network.transport
-== "tcp" and source.ip != "127.0.0.1" and source.ip != "::1" ] by
-process.entity_id /* add more executable extensions here if they are
-not noisy in your environment */ [file where event.type in
-("creation", "change") and process.pid == 4 and file.extension :
-("exe", "dll", "bat", "cmd")] by process.entity_id
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=30s
+  [network where host.os.type == "windows" and event.type == "start" and process.pid == 4 and destination.port == 445 and
+   network.direction : ("incoming", "ingress") and
+   network.transport == "tcp" and source.ip != "127.0.0.1" and source.ip != "::1"
+  ] by process.entity_id
+  /* add more executable extensions here if they are not noisy in your environment */
+  [file where host.os.type == "windows" and event.type in ("creation", "change") and process.pid == 4 and 
+   (file.Ext.header_bytes : "4d5a*" or file.extension : ("exe", "scr", "pif", "com", "dll"))] by process.entity_id
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -119,54 +118,14 @@ not noisy in your environment */ [file where event.type in
 ** ID: TA0008
 ** Reference URL: https://attack.mitre.org/tactics/TA0008/
 * Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
+* Technique:
 ** Name: Lateral Tool Transfer
 ** ID: T1570
 ** Reference URL: https://attack.mitre.org/techniques/T1570/
-
-[[potential-lateral-tool-transfer-via-smb-share-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Rule name changed from: Lateral Tool Transfer
-Version 4 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=30s [network where event.type ==
-"start" and process.pid == 4 and destination.port == 445 and
-network.direction : ("incoming", "ingress") and network.transport ==
-"tcp" and source.address != "127.0.0.1" and source.address != "::1"
-] by process.entity_id /* add more executable extensions here if
-they are not noisy in your environment */ [file where event.type in
-("creation", "change") and process.pid == 4 and file.extension :
-("exe", "dll", "bat", "cmd")] by process.entity_id
-----------------------------------
-
-Version 3 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=30s [network where event.type ==
-"start" and process.pid == 4 and destination.port == 445 and
-network.direction == "incoming" and network.transport == "tcp" and
-source.address != "127.0.0.1" and source.address != "::1" ] by
-process.entity_id /* add more executable extensions here if they are
-not noisy in your environment */ [file where event.type in
-("creation", "change") and process.pid == 4 and file.extension :
-("exe", "dll", "bat", "cmd")] by process.entity_id
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-linux-backdoor-user-account-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-linux-backdoor-user-account-creation.asciidoc
new file mode 100644
index 0000000000..6f32d63d6e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-linux-backdoor-user-account-creation.asciidoc
@@ -0,0 +1,168 @@
+[[potential-linux-backdoor-user-account-creation]]
+=== Potential Linux Backdoor User Account Creation
+
+Identifies the attempt to create a new backdoor user by setting the user's UID to 0. Attackers may alter a user's UID to 0 to establish persistence on a system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Linux Backdoor User Account Creation*
+
+
+The `usermod` command is used to modify user account attributes and settings in Linux-based operating systems.
+
+Attackers may create new accounts with a UID of 0 to maintain root access to target systems without leveraging the root user account.
+
+This rule identifies the usage of the `usermod` command to set a user's UID to 0, indicating that the user becomes a root account. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+- Investigate the user account that got assigned a uid of 0, and analyze its corresponding attributes.
+  - !{osquery{"label":"Osquery - Retrieve User Accounts with a UID of 0","query":"SELECT description, gid, gid_signed, shell, uid, uid_signed, username FROM users WHERE username != 'root' AND uid LIKE '0'"}}
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Identify if the account was added to privileged groups or assigned special privileges after creation.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific Group","query":"SELECT * FROM groups WHERE groupname = {{group.name}}"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
+- Delete the created account.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "usermod" and process.args : "-u" and process.args : "0" and process.args : "-o"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create Account
+** ID: T1136
+** Reference URL: https://attack.mitre.org/techniques/T1136/
+* Sub-technique:
+** Name: Local Account
+** ID: T1136.001
+** Reference URL: https://attack.mitre.org/techniques/T1136/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-linux-credential-dumping-via-proc-filesystem.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-linux-credential-dumping-via-proc-filesystem.asciidoc
new file mode 100644
index 0000000000..1a32bf7114
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-linux-credential-dumping-via-proc-filesystem.asciidoc
@@ -0,0 +1,112 @@
+[[potential-linux-credential-dumping-via-proc-filesystem]]
+=== Potential Linux Credential Dumping via Proc Filesystem
+
+Identifies the execution of the mimipenguin exploit script which is linux adaptation of Windows tool mimikatz. Mimipenguin exploit script is used to dump clear text passwords from a currently logged-in user. The tool exploits a known vulnerability CVE-2018-20781. Malicious actors can exploit the cleartext credentials in memory by dumping the process and extracting lines that have a high probability of containing cleartext passwords.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/huntergregal/mimipenguin
+* https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20781
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.parent.name with maxspan=1m
+  [process where host.os.type == "linux" and process.name == "ps" and event.action == "exec"
+   and process.args in ("-eo", "pid", "command")]
+  [process where host.os.type == "linux" and process.name == "strings" and event.action == "exec"
+   and process.args : "/tmp/*"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: Proc Filesystem
+** ID: T1003.007
+** Reference URL: https://attack.mitre.org/techniques/T1003/007/
+* Technique:
+** Name: Exploitation for Credential Access
+** ID: T1212
+** Reference URL: https://attack.mitre.org/techniques/T1212/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-linux-credential-dumping-via-unshadow.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-linux-credential-dumping-via-unshadow.asciidoc
new file mode 100644
index 0000000000..6b40bf3987
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-linux-credential-dumping-via-unshadow.asciidoc
@@ -0,0 +1,105 @@
+[[potential-linux-credential-dumping-via-unshadow]]
+=== Potential Linux Credential Dumping via Unshadow
+
+Identifies the execution of the unshadow utility which is part of John the Ripper, a password-cracking tool on the host machine. Malicious actors can use the utility to retrieve the combined contents of the '/etc/shadow' and '/etc/password' files. Using the combined file generated from the utility, the malicious threat actors can use them as input for password-cracking utilities or prepare themselves for future operations by gathering credential information of the victim.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.cyberciti.biz/faq/unix-linux-password-cracking-john-the-ripper/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
+process.name == "unshadow" and process.args_count >= 3
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: /etc/passwd and /etc/shadow
+** ID: T1003.008
+** Reference URL: https://attack.mitre.org/techniques/T1003/008/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-linux-hack-tool-launched.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-linux-hack-tool-launched.asciidoc
new file mode 100644
index 0000000000..4ce00f7366
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-linux-hack-tool-launched.asciidoc
@@ -0,0 +1,114 @@
+[[potential-linux-hack-tool-launched]]
+=== Potential Linux Hack Tool Launched
+
+Monitors for the execution of different processes that might be used by attackers for malicious intent. An alert from this rule should be investigated further, as hack tools are commonly used by blue teamers and system administrators as well.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name in (
+  // exploitation frameworks
+  "crackmapexec", "msfconsole", "msfvenom", "sliver-client", "sliver-server", "havoc",
+  // network scanners (nmap left out to reduce noise)
+  "zenmap", "nuclei", "netdiscover", "legion",
+  // web enumeration
+  "gobuster", "dirbuster", "dirb", "wfuzz", "ffuf", "whatweb", "eyewitness",
+  // web vulnerability scanning
+  "wpscan", "joomscan", "droopescan", "nikto", 
+  // exploitation tools
+  "sqlmap", "commix", "yersinia",
+  // cracking and brute forcing
+  "john", "hashcat", "hydra", "ncrack", "cewl", "fcrackzip", "rainbowcrack",
+  // host and network
+  "linenum.sh", "linpeas.sh", "pspy32", "pspy32s", "pspy64", "pspy64s", "binwalk", "evil-winrm"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-linux-local-account-brute-force-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-linux-local-account-brute-force-detected.asciidoc
new file mode 100644
index 0000000000..40ef5e0325
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-linux-local-account-brute-force-detected.asciidoc
@@ -0,0 +1,106 @@
+[[potential-linux-local-account-brute-force-detected]]
+=== Potential Linux Local Account Brute Force Detected
+
+Identifies multiple consecutive login attempts executed by one process targeting a local linux user account within a short time interval. Adversaries might brute force login attempts across different users with a default wordlist or a set of customly crafted passwords in an attempt to gain access to these accounts.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.parent.executable, user.id with maxspan=1s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and process.name == "su" and 
+   not process.parent.name in (
+     "bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "clickhouse-server", "ma", "gitlab-runner",
+     "updatedb.findutils", "cron"
+   )
+  ] with runs=10
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Brute Force
+** ID: T1110
+** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Sub-technique:
+** Name: Password Guessing
+** ID: T1110.001
+** Reference URL: https://attack.mitre.org/techniques/T1110/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-linux-ransomware-note-creation-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-linux-ransomware-note-creation-detected.asciidoc
new file mode 100644
index 0000000000..f6d89f4886
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-linux-ransomware-note-creation-detected.asciidoc
@@ -0,0 +1,111 @@
+[[potential-linux-ransomware-note-creation-detected]]
+=== Potential Linux Ransomware Note Creation Detected
+
+This rule identifies a sequence of a mass file encryption event in conjunction with the creation of a .txt file with a file name containing ransomware keywords executed by the same process in a 1 second timespan. Ransomware is a type of malware that encrypts a victim's files or systems and demands payment (usually in cryptocurrency) in exchange for the decryption key. One important indicator of a ransomware attack is the mass encryption of the file system, after which a new file extension is added to the file.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Impact
+* Data Source: Elastic Defend
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by process.entity_id, host.id with maxspan=1s 
+  [file where host.os.type == "linux" and event.type == "change" and event.action == "rename" and file.extension : "?*" 
+   and process.executable : ("./*", "/tmp/*", "/var/tmp/*", "/dev/shm/*", "/var/run/*", "/boot/*", "/srv/*", "/run/*") and
+   file.path : (
+     "/home/*/Downloads/*", "/home/*/Documents/*", "/root/*", "/bin/*", "/usr/bin/*", "/var/log/*", "/var/lib/log/*",
+     "/var/backup/*", "/var/www/*") and
+   not process.name : (
+     "dpkg", "yum", "dnf", "rpm", "dockerd", "go", "java", "pip*", "python*", "node", "containerd", "php", "p4d",
+     "conda", "chrome", "imap", "cmake", "firefox", "semanage", "semodule", "ansible-galaxy", "fc-cache", "jammy", "git",
+     "systemsettings", "vmis-launcher", "bundle", "kudu-tserver", "suldownloader"
+    )
+  ] with runs=25
+  [file where host.os.type == "linux" and event.action == "creation" and file.name : (
+     "*crypt*", "*restore*", "*lock*", "*recovery*", "*data*", "*read*", "*instruction*", "*how_to*", "*ransom*"
+    )
+  ]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Data Encrypted for Impact
+** ID: T1486
+** Reference URL: https://attack.mitre.org/techniques/T1486/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-linux-ssh-x11-forwarding.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-linux-ssh-x11-forwarding.asciidoc
new file mode 100644
index 0000000000..5b94873e2f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-linux-ssh-x11-forwarding.asciidoc
@@ -0,0 +1,141 @@
+[[potential-linux-ssh-x11-forwarding]]
+=== Potential Linux SSH X11 Forwarding
+
+This rule monitors for X11 forwarding via SSH. X11 forwarding is a feature that allows users to run graphical applications on a remote server and display the application's graphical user interface on their local machine. Attackers can abuse X11 forwarding for tunneling their GUI-based tools, pivot through compromised systems, and create covert communication channels, enabling lateral movement and facilitating remote control of systems within a network.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://book.hacktricks.xyz/generic-methodologies-and-resources/tunneling-and-port-forwarding
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Linux SSH X11 Forwarding*
+
+
+Attackers can leverage SSH X11 forwarding to capture a user's graphical desktop session and potentially execute unauthorized GUI applications remotely.
+
+This rule looks for the execution of SSH in conjunction with command line arguments that are capable of setting up X11 forwarding. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Identify any signs of suspicious network activity or anomalies that may indicate network forwarding activity. This could include unexpected traffic patterns or unusual network behavior.
+  - Investigate listening ports and open sockets to look for potential protocol tunneling, reverse shells, or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+  - !{osquery{"label":"Osquery - Retrieve Process Info","query":"SELECT name, cmdline, parent, path, uid FROM processes"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+
+
+*Related rules*
+
+
+- Potential Linux Tunneling and/or Port Forwarding - 6ee947e9-de7e-4281-a55d-09289bdf947e
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator or developer who uses port tunneling/forwarding for benign purposes, consider adding exceptions for specific user accounts or hosts. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors, such as reverse shells, reverse proxies, or droppers, that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
+process.name in ("ssh", "sshd") and process.args in ("-X", "-Y") and process.args_count >= 3 and 
+process.parent.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Protocol Tunneling
+** ID: T1572
+** Reference URL: https://attack.mitre.org/techniques/T1572/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-linux-tunneling-and-or-port-forwarding.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-linux-tunneling-and-or-port-forwarding.asciidoc
new file mode 100644
index 0000000000..fe8f95594a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-linux-tunneling-and-or-port-forwarding.asciidoc
@@ -0,0 +1,196 @@
+[[potential-linux-tunneling-and-or-port-forwarding]]
+=== Potential Linux Tunneling and/or Port Forwarding
+
+This rule monitors for a set of Linux utilities that can be used for tunneling and port forwarding. Attackers can leverage tunneling and port forwarding techniques to bypass network defenses, establish hidden communication channels, and gain unauthorized access to internal resources, facilitating data exfiltration, lateral movement, and remote control.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.bitsadmin.com/living-off-the-foreign-land-windows-as-offensive-platform
+* https://book.hacktricks.xyz/generic-methodologies-and-resources/tunneling-and-port-forwarding
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Linux Tunneling and/or Port Forwarding*
+
+
+Attackers can leverage many utilities to clandestinely tunnel network communications and evade security measures, potentially gaining unauthorized access to sensitive systems.
+
+This rule looks for several utilities that are capable of setting up tunnel network communications by analyzing process names or command line arguments. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Identify any signs of suspicious network activity or anomalies that may indicate protocol tunneling. This could include unexpected traffic patterns or unusual network behavior.
+  - Investigate listening ports and open sockets to look for potential protocol tunneling, reverse shells, or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+  - !{osquery{"label":"Osquery - Retrieve Process Info","query":"SELECT name, cmdline, parent, path, uid FROM processes"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+
+
+*Related rules*
+
+
+- Potential Protocol Tunneling via Chisel Client - 3f12325a-4cc6-410b-8d4c-9fbbeb744cfd
+- Potential Protocol Tunneling via Chisel Server - ac8805f6-1e08-406c-962e-3937057fa86f
+- Potential Protocol Tunneling via EarthWorm - 9f1c4ca3-44b5-481d-ba42-32dc215a2769
+- Suspicious Utility Launched via ProxyChains - 6ace94ba-f02c-4d55-9f53-87d99b6f9af4
+- ProxyChains Activity - 4b868f1f-15ff-4ba3-8c11-d5a7a6356d37
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator or developer who uses port tunneling/forwarding for benign purposes, consider adding exceptions for specific user accounts or hosts. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors, such as reverse shells, reverse proxies, or droppers, that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and (
+  (
+    // gost & pivotnacci - spawned without process.parent.name
+    (process.name == "gost" and process.args : ("-L*", "-C*", "-R*")) or (process.name == "pivotnacci")) or (
+    // ssh
+    (process.name in ("ssh", "sshd") and (process.args in ("-R", "-L", "-D", "-w") and process.args_count >= 4 and 
+     not process.args : "chmod")) or
+    // sshuttle
+    (process.name == "sshuttle" and process.args in ("-r", "--remote", "-l", "--listen") and process.args_count >= 4) or
+    // socat
+    (process.name == "socat" and process.args : ("TCP4-LISTEN:*", "SOCKS*") and process.args_count >= 3) or
+    // chisel
+    (process.name : "chisel*" and process.args in ("client", "server")) or
+    // iodine(d), dnscat, hans, ptunnel-ng, ssf, 3proxy & ngrok 
+    (process.name in ("iodine", "iodined", "dnscat", "hans", "hans-ubuntu", "ptunnel-ng", "ssf", "3proxy", "ngrok"))
+  ) and process.parent.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Protocol Tunneling
+** ID: T1572
+** Reference URL: https://attack.mitre.org/techniques/T1572/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-local-ntlm-relay-via-http.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-local-ntlm-relay-via-http.asciidoc
index 223fbf0704..f735f97bf1 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-local-ntlm-relay-via-http.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-local-ntlm-relay-via-http.asciidoc
@@ -5,62 +5,64 @@ Identifies attempt to coerce a local NTLM authentication via HTTP using the Wind
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/med0x2e/NTLMRelay2Self
 * https://github.com/topotam/PetitPotam
 * https://github.com/dirkjanm/krbrelayx/blob/master/printerbug.py
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Elastic Endgame
-
-*Version*: 102 (<<potential-local-ntlm-relay-via-http-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 8.3.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name :
-"rundll32.exe" and /* Rundll32 WbeDav Client */ process.args :
-("?:\\Windows\\System32\\davclnt.dll,DavSetCookie",
-"?:\\Windows\\SysWOW64\\davclnt.dll,DavSetCookie") and /* Access to
-named pipe via http */ process.args : ("http*/print/pipe/*",
-"http*/pipe/spoolss", "http*/pipe/srvsvc")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "rundll32.exe" and
+
+  /* Rundll32 WbeDav Client  */
+  process.args : ("?:\\Windows\\System32\\davclnt.dll,DavSetCookie", "?:\\Windows\\SysWOW64\\davclnt.dll,DavSetCookie") and
 
-==== Threat mapping
+  /* Access to named pipe via http */
+  process.args : ("http*/print/pipe/*", "http*/pipe/spoolss", "http*/pipe/srvsvc")
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,26 +74,15 @@ named pipe via http */ process.args : ("http*/print/pipe/*",
 ** Name: Exploitation for Credential Access
 ** ID: T1212
 ** Reference URL: https://attack.mitre.org/techniques/T1212/
-
-[[potential-local-ntlm-relay-via-http-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "rundll32.exe" and /* Rundll32 WbeDav Client */
-process.args : ("?:\\Windows\\System32\\davclnt.dll,DavSetCookie",
-"?:\\Windows\\SysWOW64\\davclnt.dll,DavSetCookie") and /* Access
-to named pipe via http */ process.args : ("http*/print/pipe/*",
-"http*/pipe/spoolss", "http*/pipe/srvsvc")
-----------------------------------
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: Rundll32
+** ID: T1218.011
+** Reference URL: https://attack.mitre.org/techniques/T1218/011/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-lsa-authentication-package-abuse.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-lsa-authentication-package-abuse.asciidoc
index d66f616fc6..3fab405d51 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-lsa-authentication-package-abuse.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-lsa-authentication-package-abuse.asciidoc
@@ -5,50 +5,55 @@ Adversaries can use the autostart mechanism provided by the Local Security Autho
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<potential-lsa-authentication-package-abuse-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type == "change" and registry.path :
-"HKLM\\SYSTEM\\*ControlSet*\\Control\\Lsa\\Authentication Packages"
-and /* exclude SYSTEM SID - look for changes by non-SYSTEM user */
-not user.id : "S-1-5-18"
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type == "change" and
+  registry.path : (
+      "HKLM\\SYSTEM\\*ControlSet*\\Control\\Lsa\\Authentication Packages",
+      "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Control\\Lsa\\Authentication Packages"
+  ) and
+  /* exclude SYSTEM SID - look for changes by non-SYSTEM user */
+  not user.id : "S-1-5-18"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -60,8 +65,10 @@ not user.id : "S-1-5-18"
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-
+* Sub-technique:
+** Name: Authentication Package
+** ID: T1547.002
+** Reference URL: https://attack.mitre.org/techniques/T1547/002/
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -70,16 +77,7 @@ not user.id : "S-1-5-18"
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[potential-lsa-authentication-package-abuse-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Authentication Package
+** ID: T1547.002
+** Reference URL: https://attack.mitre.org/techniques/T1547/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-lsass-clone-creation-via-psscapturesnapshot.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-lsass-clone-creation-via-psscapturesnapshot.asciidoc
index f51b48caf2..5064c3c7cf 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-lsass-clone-creation-via-psscapturesnapshot.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-lsass-clone-creation-via-psscapturesnapshot.asciidoc
@@ -5,65 +5,70 @@ Identifies the creation of an LSASS process clone via PssCaptureSnapShot where t
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
+* logs-system.*
 * logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.matteomalvica.com/blog/2019/12/02/win-defender-atp-cred-bypass/
 * https://medium.com/@Achilles8284/the-birth-of-a-process-part-2-97c6fb9c42a2
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Sysmon
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Sysmon Only
 
-*Version*: 101 (<<potential-lsass-clone-creation-via-psscapturesnapshot-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.0.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This is meant to run only on datasources using Windows security event 4688 that captures the process clone creation.
 
-----------------------------------
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.code:"4688" and process.executable :
-"?:\\Windows\\System32\\lsass.exe" and process.parent.executable :
-"?:\\Windows\\System32\\lsass.exe"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.code:"4688" and
+  process.executable : "?:\\Windows\\System32\\lsass.exe" and
+  process.parent.executable : "?:\\Windows\\System32\\lsass.exe"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,19 +80,7 @@ process where event.code:"4688" and process.executable :
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[potential-lsass-clone-creation-via-psscapturesnapshot-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-lsass-memory-dump-via-psscapturesnapshot.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-lsass-memory-dump-via-psscapturesnapshot.asciidoc
index 0ecdee3cd1..02c1ff15ea 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-lsass-memory-dump-via-psscapturesnapshot.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-lsass-memory-dump-via-psscapturesnapshot.asciidoc
@@ -5,66 +5,65 @@ Identifies suspicious access to an LSASS handle via PssCaptureSnapShot where two
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.matteomalvica.com/blog/2019/12/02/win-defender-atp-cred-bypass/
 * https://twitter.com/sbousseaden/status/1280619931516747777?lang=en
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Sysmon Only
-
-*Version*: 101 (<<potential-lsass-memory-dump-via-psscapturesnapshot-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 208
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+This is meant to run only on datasources using Elastic Agent 7.14+ since versions prior to that will be missing the threshold
+rule cardinality feature.
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.code:10 and
-winlog.event_data.TargetImage:("C:\\Windows\\system32\\lsass.exe" or
-"c:\\Windows\\system32\\lsass.exe" or
-"c:\\Windows\\System32\\lsass.exe")
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and event.code:10 and
+ winlog.event_data.TargetImage:("C:\\Windows\\system32\\lsass.exe" or
+                                 "c:\\Windows\\system32\\lsass.exe" or
+                                 "c:\\Windows\\System32\\lsass.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,22 +75,7 @@ winlog.event_data.TargetImage:("C:\\Windows\\system32\\lsass.exe" or
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[potential-lsass-memory-dump-via-psscapturesnapshot-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-macos-ssh-brute-force-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-macos-ssh-brute-force-detected.asciidoc
index 61aeca22bd..223b1fdcfd 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-macos-ssh-brute-force-detected.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-macos-ssh-brute-force-detected.asciidoc
@@ -5,53 +5,86 @@ Identifies a high number (20) of macOS SSH KeyGen process executions from the sa
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://themittenmac.com/detecting-ssh-activity-via-process-monitoring/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Credential Access
 
-*Version*: 101 (<<potential-macos-ssh-brute-force-detected-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:start and process.name:"sshd-
-keygen-wrapper" and process.parent.name:launchd
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:start and process.name:"sshd-keygen-wrapper" and process.parent.name:launchd
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -63,15 +96,3 @@ keygen-wrapper" and process.parent.name:launchd
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
-
-[[potential-macos-ssh-brute-force-detected-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Rule name changed from: Potential SSH Brute Force Detected
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-browser-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-browser-process.asciidoc
new file mode 100644
index 0000000000..d8aa33986f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-browser-process.asciidoc
@@ -0,0 +1,198 @@
+[[potential-masquerading-as-browser-process]]
+=== Potential Masquerading as Browser Process
+
+Identifies suspicious instances of browser processes, such as unsigned or signed with unusual certificates, that can indicate an attempt to conceal malicious activity, bypass security features such as allowlists, or trick users into executing malware.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Persistence
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (
+    /* Chrome Related Processes */
+    (process.name : (
+      "chrome.exe", "GoogleUpdate.exe", "GoogleCrashHandler64.exe", "GoogleCrashHandler.exe",
+      "GoogleUpdateComRegisterShell64.exe", "GoogleUpdateSetup.exe", "GoogleUpdateOnDemand.exe",
+      "chrome_proxy.exe", "remote_assistance_host.exe", "remoting_native_messaging_host.exe",
+      "GoogleUpdateBroker.exe"
+     ) and not
+      (process.code_signature.subject_name : ("Google LLC", "Google Inc") and process.code_signature.trusted == true)
+     and not
+      (
+        process.executable : (
+          "?:\\Program Files\\HP\\Sure Click\\servers\\chrome.exe",
+          "?:\\Program Files\\HP\\Sure Click\\*\\servers\\chrome.exe"
+        ) and
+        process.code_signature.subject_name : ("Bromium, Inc.") and process.code_signature.trusted == true
+      ) and not
+      (
+        process.executable : (
+          "?:\\Program Files\\dynatrace\\synthetic\\Chrome-bin\\chrome.exe"
+        ) and
+        process.code_signature.subject_name : ("Dynatrace LLC") and process.code_signature.trusted == true
+      ) and
+     not (
+       process.executable : (
+         "?:\\Users\\*\\AppData\\Local\\ms-playwright\\chromium-*\\chrome-win\\chrome.exe",
+         "?:\\Users\\*\\AppData\\Local\\Programs\\synthetics-recorder\\resources\\local-browsers\\chromium-*\\chrome-win\\chrome.exe",
+         "*\\node_modules\\puppeteer\\.local-chromium\\win64-*\\chrome-win\\chrome.exe",
+         "?:\\Program Files (x86)\\Invicti Professional Edition\\chromium\\chrome.exe",
+         "?:\\Program Files\\End2End, Inc\\ARMS Html Engine\\chrome.exe",
+         "?:\\Users\\*\\AppData\\Local\\*BurpSuitePro\\burpbrowser\\*\\chrome.exe",
+         "?:\\Users\\*\\AppData\\Roaming\\*BurpSuite\\burpbrowser\\*\\chrome.exe"
+       ) and process.args: (
+               "--enable-features=NetworkService,NetworkServiceInProcess",
+               "--type=crashpad-handler", "--enable-automation", "--disable-xss-auditor"
+             )
+     )
+    ) or
+
+    /* MS Edge Related Processes */
+    (process.name : (
+      "msedge.exe", "MicrosoftEdgeUpdate.exe", "identity_helper.exe", "msedgewebview2.exe",
+      "MicrosoftEdgeWebview2Setup.exe", "MicrosoftEdge_X*.exe", "msedge_proxy.exe",
+      "MicrosoftEdgeUpdateCore.exe", "MicrosoftEdgeUpdateBroker.exe", "MicrosoftEdgeUpdateSetup_X*.exe",
+      "MicrosoftEdgeUpdateComRegisterShell64.exe", "msedgerecovery.exe", "MicrosoftEdgeUpdateSetup.exe"
+     ) and not
+      (process.code_signature.subject_name : "Microsoft Corporation" and process.code_signature.trusted == true)
+     and not
+      (
+        process.name : "msedgewebview2.exe" and
+        process.code_signature.subject_name : ("Bromium, Inc.", "Amazon.com Services LLC", "Code Systems Corporation") and process.code_signature.trusted == true
+      )
+    ) or
+
+    /* Brave Related Processes */
+    (process.name : (
+      "brave.exe", "BraveUpdate.exe", "BraveCrashHandler64.exe", "BraveCrashHandler.exe",
+      "BraveUpdateOnDemand.exe", "brave_vpn_helper.exe", "BraveUpdateSetup*.exe",
+      "BraveUpdateComRegisterShell64.exe"
+     ) and not
+      (process.code_signature.subject_name : "Brave Software, Inc." and process.code_signature.trusted == true)
+    ) or
+
+    /* Firefox Related Processes */
+    (process.name : (
+      "firefox.exe", "pingsender.exe", "default-browser-agent.exe", "maintenanceservice.exe",
+      "plugin-container.exe", "maintenanceservice_tmp.exe", "maintenanceservice_installer.exe",
+      "minidump-analyzer.exe"
+     ) and not
+      (process.code_signature.subject_name : "Mozilla Corporation" and process.code_signature.trusted == true)
+     and not
+      (
+        process.name : "default-browser-agent.exe" and
+        process.code_signature.subject_name : ("WATERFOX LIMITED") and process.code_signature.trusted == true
+      )
+    ) or
+
+    /* Island Related Processes */
+    (process.name : (
+      "Island.exe", "IslandUpdate.exe", "IslandCrashHandler.exe", "IslandCrashHandler64.exe",
+      "IslandUpdateBroker.exe", "IslandUpdateOnDemand.exe", "IslandUpdateComRegisterShell64.exe",
+      "IslandUpdateSetup.exe"
+     ) and not
+      (process.code_signature.subject_name : "Island Technology Inc." and process.code_signature.trusted == true)
+    ) or
+
+    /* Opera Related Processes */
+    (process.name : (
+      "opera.exe", "opera_*.exe", "browser_assistant.exe"
+     ) and not
+      (process.code_signature.subject_name : ("Opera Norway AS", "Opera Software AS") and process.code_signature.trusted == true)
+    ) or
+
+    /* Whale Related Processes */
+    (process.name : (
+      "whale.exe", "whale_update.exe", "wusvc.exe"
+     ) and not
+      (process.code_signature.subject_name : "NAVER Corp." and process.code_signature.trusted == true)
+    ) or
+
+    /* Chromium-based Browsers processes */
+    (process.name : (
+      "chrmstp.exe", "notification_helper.exe", "elevation_service.exe"
+     ) and not
+      (process.code_signature.subject_name : (
+        "Island Technology Inc.",
+        "Citrix Systems, Inc.",
+        "Brave Software, Inc.",
+        "Google LLC",
+        "Google Inc",
+        "Microsoft Corporation",
+        "NAVER Corp.",
+        "AVG Technologies USA, LLC",
+        "Avast Software s.r.o.",
+        "PIRIFORM SOFTWARE LIMITED",
+        "NortonLifeLock Inc.",
+        "Opera Norway AS"
+       ) and process.code_signature.trusted == true
+      )
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Compromise Client Software Binary
+** ID: T1554
+** Reference URL: https://attack.mitre.org/techniques/T1554/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-business-app-installer.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-business-app-installer.asciidoc
new file mode 100644
index 0000000000..47d674a2b1
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-business-app-installer.asciidoc
@@ -0,0 +1,217 @@
+[[potential-masquerading-as-business-app-installer]]
+=== Potential Masquerading as Business App Installer
+
+Identifies executables with names resembling legitimate business applications but lacking signatures from the original developer. Attackers may trick users into downloading malicious executables that masquerade as legitimate applications via malicious ads, forum posts, and tutorials, effectively gaining initial access.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.rapid7.com/blog/post/2023/08/31/fake-update-utilizes-new-idat-loader-to-execute-stealc-and-lumma-infostealers
+
+*Tags*: 
+
+* Domain: Endpoint
+* Data Source: Elastic Defend
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Initial Access
+* Tactic: Execution
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and
+  event.type == "start" and process.executable : "?:\\Users\\*\\Downloads\\*" and
+  not process.code_signature.status : ("errorCode_endpoint*", "errorUntrustedRoot", "errorChaining") and
+  (
+    /* Slack */
+    (process.name : "*slack*.exe" and not
+      (process.code_signature.subject_name in (
+        "Slack Technologies, Inc.",
+        "Slack Technologies, LLC"
+       ) and process.code_signature.trusted == true)
+    ) or
+
+    /* WebEx */
+    (process.name : "*webex*.exe" and not
+      (process.code_signature.subject_name in ("Cisco WebEx LLC", "Cisco Systems, Inc.") and process.code_signature.trusted == true)
+    ) or
+
+    /* Teams */
+    (process.name : "teams*.exe" and not
+      (process.code_signature.subject_name == "Microsoft Corporation" and process.code_signature.trusted == true)
+    ) or
+
+    /* Discord */
+    (process.name : "*discord*.exe" and not
+      (process.code_signature.subject_name == "Discord Inc." and process.code_signature.trusted == true)
+    ) or
+
+    /* WhatsApp */
+    (process.name : "*whatsapp*.exe" and not
+      (process.code_signature.subject_name in (
+        "WhatsApp LLC",
+        "WhatsApp, Inc",
+        "24803D75-212C-471A-BC57-9EF86AB91435"
+       ) and process.code_signature.trusted == true)
+    ) or
+
+    /* Zoom */
+    (process.name : ("*zoom*installer*.exe", "*zoom*setup*.exe", "zoom.exe")  and not
+      (process.code_signature.subject_name == "Zoom Video Communications, Inc." and process.code_signature.trusted == true)
+    ) or
+
+    /* Outlook */
+    (process.name : "*outlook*.exe" and not
+      (
+        (process.code_signature.subject_name == "Microsoft Corporation" and process.code_signature.trusted == true) or
+        (
+          process.name: "MSOutlookHelp-PST-Viewer.exe" and process.code_signature.subject_name == "Aryson Technologies Pvt. Ltd" and
+          process.code_signature.trusted == true
+        )
+      )
+    ) or
+
+    /* Thunderbird */
+    (process.name : "*thunderbird*.exe" and not
+      (process.code_signature.subject_name == "Mozilla Corporation" and process.code_signature.trusted == true)
+    ) or
+
+    /* Grammarly */
+    (process.name : "*grammarly*.exe" and not
+      (process.code_signature.subject_name == "Grammarly, Inc." and process.code_signature.trusted == true)
+    ) or
+
+    /* Dropbox */
+    (process.name : "*dropbox*.exe" and not
+      (process.code_signature.subject_name == "Dropbox, Inc" and process.code_signature.trusted == true)
+    ) or
+
+    /* Tableau */
+    (process.name : "*tableau*.exe" and not
+      (process.code_signature.subject_name == "Tableau Software LLC" and process.code_signature.trusted == true)
+    ) or
+
+    /* Google Drive */
+    (process.name : "*googledrive*.exe" and not
+      (process.code_signature.subject_name == "Google LLC" and process.code_signature.trusted == true)
+    ) or
+
+    /* MSOffice */
+    (process.name : "*office*setup*.exe" and not
+      (process.code_signature.subject_name == "Microsoft Corporation" and process.code_signature.trusted == true)
+    ) or
+
+    /* Okta */
+    (process.name : "*okta*.exe" and not
+      (process.code_signature.subject_name == "Okta, Inc." and process.code_signature.trusted == true)
+    ) or
+
+    /* OneDrive */
+    (process.name : "*onedrive*.exe" and not
+      (process.code_signature.subject_name == "Microsoft Corporation" and process.code_signature.trusted == true)
+    ) or
+
+    /* Chrome */
+    (process.name : "*chrome*.exe" and not
+      (process.code_signature.subject_name in ("Google LLC", "Google Inc") and process.code_signature.trusted == true)
+    ) or
+
+    /* Firefox */
+    (process.name : "*firefox*.exe" and not
+      (process.code_signature.subject_name == "Mozilla Corporation" and process.code_signature.trusted == true)
+    ) or
+
+    /* Edge */
+    (process.name : ("*microsoftedge*.exe", "*msedge*.exe") and not
+      (process.code_signature.subject_name == "Microsoft Corporation" and process.code_signature.trusted == true)
+    ) or
+
+    /* Brave */
+    (process.name : "*brave*.exe" and not
+      (process.code_signature.subject_name == "Brave Software, Inc." and process.code_signature.trusted == true)
+    ) or
+
+    /* GoogleCloud Related Tools */
+    (process.name : "*GoogleCloud*.exe" and not
+      (process.code_signature.subject_name == "Google LLC" and process.code_signature.trusted == true)
+    ) or
+
+    /* Github Related Tools */
+    (process.name : "*github*.exe" and not
+      (process.code_signature.subject_name == "GitHub, Inc." and process.code_signature.trusted == true)
+    ) or
+
+    /* Notion */
+    (process.name : "*notion*.exe" and not
+      (process.code_signature.subject_name == "Notion Labs, Inc." and process.code_signature.trusted == true)
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Drive-by Compromise
+** ID: T1189
+** Reference URL: https://attack.mitre.org/techniques/T1189/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: User Execution
+** ID: T1204
+** Reference URL: https://attack.mitre.org/techniques/T1204/
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-communication-apps.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-communication-apps.asciidoc
new file mode 100644
index 0000000000..0512a028cd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-communication-apps.asciidoc
@@ -0,0 +1,134 @@
+[[potential-masquerading-as-communication-apps]]
+=== Potential Masquerading as Communication Apps
+
+Identifies suspicious instances of communications apps, both unsigned and renamed ones, that can indicate an attempt to conceal malicious activity, bypass security features such as allowlists, or trick users into executing malware.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and
+  event.type == "start" and
+  (
+    /* Slack */
+    (process.name : "slack.exe" and not
+      (process.code_signature.subject_name in (
+        "Slack Technologies, Inc.",
+        "Slack Technologies, LLC"
+       ) and process.code_signature.trusted == true)
+    ) or
+
+    /* WebEx */
+    (process.name : "WebexHost.exe" and not
+      (process.code_signature.subject_name in ("Cisco WebEx LLC", "Cisco Systems, Inc.") and process.code_signature.trusted == true)
+    ) or
+
+    /* Teams */
+    (process.name : "Teams.exe" and not
+      (process.code_signature.subject_name == "Microsoft Corporation" and process.code_signature.trusted == true)
+    ) or
+
+    /* Discord */
+    (process.name : "Discord.exe" and not
+      (process.code_signature.subject_name == "Discord Inc." and process.code_signature.trusted == true)
+    ) or
+
+    /* RocketChat */
+    (process.name : "Rocket.Chat.exe" and not
+      (process.code_signature.subject_name == "Rocket.Chat Technologies Corp." and process.code_signature.trusted == true)
+    ) or
+
+    /* Mattermost */
+    (process.name : "Mattermost.exe" and not
+      (process.code_signature.subject_name == "Mattermost, Inc." and process.code_signature.trusted == true)
+    ) or
+
+    /* WhatsApp */
+    (process.name : "WhatsApp.exe" and not
+      (process.code_signature.subject_name in (
+        "WhatsApp LLC",
+        "WhatsApp, Inc",
+        "24803D75-212C-471A-BC57-9EF86AB91435"
+       ) and process.code_signature.trusted == true)
+    ) or
+
+    /* Zoom */
+    (process.name : "Zoom.exe" and not
+      (process.code_signature.subject_name == "Zoom Video Communications, Inc." and process.code_signature.trusted == true)
+    ) or
+
+    /* Outlook */
+    (process.name : "outlook.exe" and not
+      (process.code_signature.subject_name == "Microsoft Corporation" and process.code_signature.trusted == true)
+    ) or
+
+    /* Thunderbird */
+    (process.name : "thunderbird.exe" and not
+      (process.code_signature.subject_name == "Mozilla Corporation" and process.code_signature.trusted == true)
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Compromise Client Software Binary
+** ID: T1554
+** Reference URL: https://attack.mitre.org/techniques/T1554/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-system32-dll.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-system32-dll.asciidoc
new file mode 100644
index 0000000000..19fb32e4c0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-system32-dll.asciidoc
@@ -0,0 +1,157 @@
+[[potential-masquerading-as-system32-dll]]
+=== Potential Masquerading as System32 DLL
+
+Identifies suspicious instances of default system32 DLLs either unsigned or signed with non-MS certificates. This can potentially indicate the attempt to masquerade as system DLLs, perform DLL Search Order Hijacking or backdoor and resign legitimate DLLs.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* Data Source: Elastic Defend
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Persistence
+* Rule Type: BBR
+
+*Version*: 104
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+library where event.action == "load" and dll.Ext.relative_file_creation_time <= 3600 and
+    not (
+      dll.path : (
+        "?:\\Windows\\System32\\*",
+        "?:\\Windows\\SysWOW64\\*",
+        "?:\\Windows\\SystemTemp\\*",
+        "?:\\$WINDOWS.~BT\\NewOS\\Windows\\WinSxS\\*",
+        "?:\\$WINDOWS.~BT\\NewOS\\Windows\\System32\\*",
+        "?:\\$WINDOWS.~BT\\Sources\\*",
+        "?:\\$WINDOWS.~BT\\Work\\*",
+        "?:\\Windows\\WinSxS\\*",
+        "?:\\Windows\\SoftwareDistribution\\Download\\*",
+        "?:\\Windows\\assembly\\NativeImages_v*"
+      )
+    ) and
+    not (
+      dll.code_signature.subject_name in (
+        "Microsoft Windows",
+        "Microsoft Corporation",
+        "Microsoft Windows Hardware Abstraction Layer Publisher",
+        "Microsoft Windows Publisher",
+        "Microsoft Windows 3rd party Component",
+        "Microsoft 3rd Party Application Component"
+      ) and dll.code_signature.trusted == true
+    ) and not dll.code_signature.status : ("errorCode_endpoint*", "errorUntrustedRoot", "errorChaining") and
+    dll.name : (
+      "aadauthhelper.dll", "aadcloudap.dll", "aadjcsp.dll", "aadtb.dll", "aadwamextension.dll", "aarsvc.dll", "abovelockapphost.dll", "accessibilitycpl.dll", "accountaccessor.dll", "accountsrt.dll", "acgenral.dll", "aclayers.dll", "acledit.dll", "aclui.dll", "acmigration.dll", "acppage.dll", "acproxy.dll", "acspecfc.dll", "actioncenter.dll", "actioncentercpl.dll", "actionqueue.dll", "activationclient.dll", "activeds.dll", "activesynccsp.dll", "actxprxy.dll", "acwinrt.dll", "acxtrnal.dll", "adaptivecards.dll", "addressparser.dll", "adhapi.dll", "adhsvc.dll", "admtmpl.dll", "adprovider.dll", "adrclient.dll", "adsldp.dll", "adsldpc.dll", "adsmsext.dll", "adsnt.dll", "adtschema.dll", "advancedemojids.dll", "advapi32.dll", "advapi32res.dll", "advpack.dll", "aeevts.dll", "aeinv.dll", "aepic.dll", "ajrouter.dll", "altspace.dll", "amsi.dll", "amsiproxy.dll", "amstream.dll", "apds.dll", "aphostclient.dll", "aphostres.dll", "aphostservice.dll", "apisampling.dll", "apisetschema.dll", "apmon.dll", "apmonui.dll", "appcontracts.dll", "appextension.dll", "apphelp.dll", "apphlpdm.dll", "appidapi.dll", "appidsvc.dll", "appinfo.dll", "appinfoext.dll", "applicationframe.dll", "applockercsp.dll", "appmgmts.dll", "appmgr.dll", "appmon.dll", "appointmentapis.dll", "appraiser.dll", "appreadiness.dll", "apprepapi.dll", "appresolver.dll", "appsruprov.dll", "appvcatalog.dll", "appvclientps.dll", "appvetwclientres.dll", "appvintegration.dll", "appvmanifest.dll", "appvpolicy.dll", "appvpublishing.dll", "appvreporting.dll", "appvscripting.dll", "appvsentinel.dll", "appvstreamingux.dll", "appvstreammap.dll", "appvterminator.dll", "appxalluserstore.dll", "appxpackaging.dll", "appxsip.dll", "appxsysprep.dll", "archiveint.dll", "asferror.dll", "aspnet_counters.dll", "asycfilt.dll", "atl.dll", "atlthunk.dll", "atmlib.dll", "audioeng.dll", "audiohandlers.dll", "audiokse.dll", "audioses.dll", "audiosrv.dll", "auditcse.dll", "auditpolcore.dll", "auditpolmsg.dll", "authbroker.dll", "authbrokerui.dll", "authentication.dll", "authext.dll", "authfwcfg.dll", "authfwgp.dll", "authfwsnapin.dll", "authfwwizfwk.dll", "authhostproxy.dll", "authui.dll", "authz.dll", "autopilot.dll", "autopilotdiag.dll", "autoplay.dll", "autotimesvc.dll", "avicap32.dll", "avifil32.dll", "avrt.dll", "axinstsv.dll", "azroles.dll", "azroleui.dll", "azsqlext.dll", "basecsp.dll", "basesrv.dll", "batmeter.dll", "bcastdvrbroker.dll", "bcastdvrclient.dll", "bcastdvrcommon.dll", "bcd.dll", "bcdprov.dll", "bcdsrv.dll", "bcp47langs.dll", "bcp47mrm.dll", "bcrypt.dll", "bcryptprimitives.dll", "bdehdcfglib.dll", "bderepair.dll", "bdesvc.dll", "bdesysprep.dll", "bdeui.dll", "bfe.dll", "bi.dll", "bidispl.dll", "bindfltapi.dll", "bingasds.dll", "bingfilterds.dll", "bingmaps.dll", "biocredprov.dll", "bisrv.dll", "bitlockercsp.dll", "bitsigd.dll", "bitsperf.dll", "bitsproxy.dll", "biwinrt.dll", "blbevents.dll", "blbres.dll", "blb_ps.dll", "bluetoothapis.dll", "bnmanager.dll", "bootmenuux.dll", "bootstr.dll", "bootux.dll", "bootvid.dll", "bridgeres.dll", "brokerlib.dll", "browcli.dll", "browserbroker.dll", "browseui.dll", "btagservice.dll", "bthavctpsvc.dll", "bthavrcp.dll", "bthavrcpappsvc.dll", "bthci.dll", "bthpanapi.dll", "bthradiomedia.dll", "bthserv.dll", "bthtelemetry.dll", "btpanui.dll", "bwcontexthandler.dll", "cabapi.dll", "cabinet.dll", "cabview.dll", "callbuttons.dll", "cameracaptureui.dll", "capauthz.dll", "capiprovider.dll", "capisp.dll", "captureservice.dll", "castingshellext.dll", "castlaunch.dll", "catsrv.dll", "catsrvps.dll", "catsrvut.dll", "cbdhsvc.dll", "cca.dll", "cdd.dll", "cdosys.dll", "cdp.dll", "cdprt.dll", "cdpsvc.dll", "cdpusersvc.dll", "cemapi.dll", "certca.dll", "certcli.dll", "certcredprovider.dll", "certenc.dll", "certenroll.dll", "certenrollui.dll", "certmgr.dll", "certpkicmdlet.dll", "certpoleng.dll", "certprop.dll", "cewmdm.dll", "cfgbkend.dll", "cfgmgr32.dll", "cfgspcellular.dll", "cfgsppolicy.dll", "cflapi.dll", "cfmifs.dll", "cfmifsproxy.dll", "chakra.dll", "chakradiag.dll", "chakrathunk.dll", "chartv.dll", "chatapis.dll", "chkwudrv.dll", "chsstrokeds.dll", "chtbopomofods.dll", "chtcangjieds.dll", "chthkstrokeds.dll", "chtquickds.dll", "chxapds.dll", "chxdecoder.dll", "chxhapds.dll", "chxinputrouter.dll", "chxranker.dll", "ci.dll", "cic.dll", "cimfs.dll", "circoinst.dll", "ciwmi.dll", "clb.dll", "clbcatq.dll", "cldapi.dll", "cleanpccsp.dll", "clfsw32.dll", "cliconfg.dll", "clipboardserver.dll", "clipc.dll", "clipsvc.dll", "clipwinrt.dll", "cloudap.dll", "cloudidsvc.dll", "clrhost.dll", "clusapi.dll", "cmcfg32.dll", "cmdext.dll", "cmdial32.dll", "cmgrcspps.dll", "cmifw.dll", "cmintegrator.dll", "cmlua.dll", "cmpbk32.dll", "cmstplua.dll", "cmutil.dll", "cngcredui.dll", "cngprovider.dll", "cnvfat.dll", "cofiredm.dll", "colbact.dll", "colorcnv.dll", "colorui.dll", "combase.dll", "comcat.dll", "comctl32.dll", "comdlg32.dll", "coml2.dll", "comppkgsup.dll", "compstui.dll", "computecore.dll", "computenetwork.dll", "computestorage.dll", "comrepl.dll", "comres.dll", "comsnap.dll", "comsvcs.dll", "comuid.dll", "configmanager2.dll", "conhostv1.dll", "connect.dll", "consentux.dll", "consentuxclient.dll", "console.dll", "consolelogon.dll", "contactapis.dll", "container.dll", "coredpus.dll", "coreglobconfig.dll", "coremas.dll", "coremessaging.dll", "coremmres.dll", "coreshell.dll", "coreshellapi.dll", "coreuicomponents.dll", "correngine.dll", "courtesyengine.dll", "cpfilters.dll", "creddialogbroker.dll", "credprovhelper.dll", "credprovhost.dll", "credprovs.dll", "credprovslegacy.dll", "credssp.dll", "credui.dll", "crypt32.dll", "cryptbase.dll", "cryptcatsvc.dll", "cryptdlg.dll", "cryptdll.dll", "cryptext.dll", "cryptnet.dll", "cryptngc.dll", "cryptowinrt.dll", "cryptsp.dll", "cryptsvc.dll", "crypttpmeksvc.dll", "cryptui.dll", "cryptuiwizard.dll", "cryptxml.dll", "cscapi.dll", "cscdll.dll", "cscmig.dll", "cscobj.dll", "cscsvc.dll", "cscui.dll", "csplte.dll", "cspproxy.dll", "csrsrv.dll", "cxcredprov.dll", "c_g18030.dll", "c_gsm7.dll", "c_is2022.dll", "c_iscii.dll", "d2d1.dll", "d3d10.dll", "d3d10core.dll", "d3d10level9.dll", "d3d10warp.dll", "d3d10_1.dll", "d3d10_1core.dll", "d3d11.dll", "d3d11on12.dll", "d3d12.dll", "d3d12core.dll", "d3d8thk.dll", "d3d9.dll", "d3d9on12.dll", "d3dscache.dll", "dab.dll", "dabapi.dll", "daconn.dll", "dafbth.dll", "dafdnssd.dll", "dafescl.dll", "dafgip.dll", "dafiot.dll", "dafipp.dll", "dafmcp.dll", "dafpos.dll", "dafprintprovider.dll", "dafupnp.dll", "dafwcn.dll", "dafwfdprovider.dll", "dafwiprov.dll", "dafwsd.dll", "damediamanager.dll", "damm.dll", "das.dll", "dataclen.dll", "datusage.dll", "davclnt.dll", "davhlpr.dll", "davsyncprovider.dll", "daxexec.dll", "dbgcore.dll", "dbgeng.dll", "dbghelp.dll", "dbgmodel.dll", "dbnetlib.dll", "dbnmpntw.dll", "dciman32.dll", "dcntel.dll", "dcomp.dll", "ddaclsys.dll", "ddcclaimsapi.dll", "ddds.dll", "ddisplay.dll", "ddoiproxy.dll", "ddores.dll", "ddpchunk.dll", "ddptrace.dll", "ddputils.dll", "ddp_ps.dll", "ddraw.dll", "ddrawex.dll", "defragproxy.dll", "defragres.dll", "defragsvc.dll", "deploymentcsps.dll", "deskadp.dll", "deskmon.dll", "desktopshellext.dll", "devenum.dll", "deviceaccess.dll", "devicecenter.dll", "devicecredential.dll", "devicepairing.dll", "deviceuxres.dll", "devinv.dll", "devmgr.dll", "devobj.dll", "devpropmgr.dll", "devquerybroker.dll", "devrtl.dll", "dfdts.dll", "dfscli.dll", "dfshim.dll", "dfsshlex.dll", "dggpext.dll", "dhcpcmonitor.dll", "dhcpcore.dll", "dhcpcore6.dll", "dhcpcsvc.dll", "dhcpcsvc6.dll", "dhcpsapi.dll", "diagcpl.dll", "diagnosticlogcsp.dll", "diagperf.dll", "diagsvc.dll", "diagtrack.dll", "dialclient.dll", "dialserver.dll", "dictationmanager.dll", "difxapi.dll", "dimsjob.dll", "dimsroam.dll", "dinput.dll", "dinput8.dll", "direct2ddesktop.dll", "directml.dll", "discan.dll", "dismapi.dll", "dispbroker.dll", "dispex.dll", "display.dll", "displaymanager.dll", "dlnashext.dll", "dmappsres.dll", "dmcfgutils.dll", "dmcmnutils.dll", "dmcsps.dll", "dmdlgs.dll", "dmdskmgr.dll", "dmdskres.dll", "dmdskres2.dll", "dmenrollengine.dll", "dmintf.dll", "dmiso8601utils.dll", "dmloader.dll", "dmocx.dll", "dmoleaututils.dll", "dmpushproxy.dll", "dmpushroutercore.dll", "dmrcdecoder.dll", "dmrserver.dll", "dmsynth.dll", "dmusic.dll", "dmutil.dll", "dmvdsitf.dll", "dmwappushsvc.dll", "dmwmicsp.dll", "dmxmlhelputils.dll", "dnsapi.dll", "dnscmmc.dll", "dnsext.dll", "dnshc.dll", "dnsrslvr.dll", "docprop.dll", "dolbydecmft.dll", "domgmt.dll", "dosettings.dll", "dosvc.dll", "dot3api.dll", "dot3cfg.dll", "dot3conn.dll", "dot3dlg.dll", "dot3gpclnt.dll", "dot3gpui.dll", "dot3hc.dll", "dot3mm.dll", "dot3msm.dll", "dot3svc.dll", "dot3ui.dll", "dpapi.dll", "dpapiprovider.dll", "dpapisrv.dll", "dpnaddr.dll", "dpnathlp.dll", "dpnet.dll", "dpnhpast.dll", "dpnhupnp.dll", "dpnlobby.dll", "dps.dll", "dpx.dll", "drprov.dll", "drt.dll", "drtprov.dll", "drttransport.dll", "drvsetup.dll", "drvstore.dll", "dsauth.dll", "dsccore.dll", "dsccoreconfprov.dll", "dsclient.dll", "dscproxy.dll", "dsctimer.dll", "dsdmo.dll", "dskquota.dll", "dskquoui.dll", "dsound.dll", "dsparse.dll", "dsprop.dll", "dsquery.dll", "dsreg.dll", "dsregtask.dll", "dsrole.dll", "dssec.dll", "dssenh.dll", "dssvc.dll", "dsui.dll", "dsuiext.dll", "dswave.dll", "dtsh.dll", "ducsps.dll", "dui70.dll", "duser.dll", "dusmapi.dll", "dusmsvc.dll", "dwmapi.dll", "dwmcore.dll", "dwmghost.dll", "dwminit.dll", "dwmredir.dll", "dwmscene.dll", "dwrite.dll", "dxcore.dll", "dxdiagn.dll", "dxgi.dll", "dxgwdi.dll", "dxilconv.dll", "dxmasf.dll", "dxp.dll", "dxpps.dll", "dxptasksync.dll", "dxtmsft.dll", "dxtrans.dll", "dxva2.dll", "dynamoapi.dll", "eapp3hst.dll", "eappcfg.dll", "eappcfgui.dll", "eappgnui.dll", "eapphost.dll", "eappprxy.dll", "eapprovp.dll", "eapputil.dll", "eapsimextdesktop.dll", "eapsvc.dll", "eapteapauth.dll", "eapteapconfig.dll", "eapteapext.dll", "easconsent.dll", "easwrt.dll", "edgeangle.dll", "edgecontent.dll", "edgehtml.dll", "edgeiso.dll", "edgemanager.dll", "edpauditapi.dll", "edpcsp.dll", "edptask.dll", "edputil.dll", "eeprov.dll", "eeutil.dll", "efsadu.dll", "efscore.dll", "efsext.dll", "efslsaext.dll", "efssvc.dll", "efsutil.dll", "efswrt.dll", "ehstorapi.dll", "ehstorpwdmgr.dll", "ehstorshell.dll", "els.dll", "elscore.dll", "elshyph.dll", "elslad.dll", "elstrans.dll", "emailapis.dll", "embeddedmodesvc.dll", "emojids.dll", "encapi.dll", "energy.dll", "energyprov.dll", "energytask.dll", "enrollmentapi.dll", "enterpriseapncsp.dll", "enterprisecsps.dll", "enterpriseetw.dll", "eqossnap.dll", "errordetails.dll", "errordetailscore.dll", "es.dll", "esclprotocol.dll", "esclscan.dll", "esclwiadriver.dll", "esdsip.dll", "esent.dll", "esentprf.dll", "esevss.dll", "eshims.dll", "etwrundown.dll", "euiccscsp.dll", "eventaggregation.dll", "eventcls.dll", "evr.dll", "execmodelclient.dll", "execmodelproxy.dll", "explorerframe.dll", "exsmime.dll", "extrasxmlparser.dll", "f3ahvoas.dll", "facilitator.dll", "familysafetyext.dll", "faultrep.dll", "fcon.dll", "fdbth.dll", "fdbthproxy.dll", "fddevquery.dll", "fde.dll", "fdeploy.dll", "fdphost.dll", "fdpnp.dll", "fdprint.dll", "fdproxy.dll", "fdrespub.dll", "fdssdp.dll", "fdwcn.dll", "fdwnet.dll", "fdwsd.dll", "feclient.dll", "ffbroker.dll", "fhcat.dll", "fhcfg.dll", "fhcleanup.dll", "fhcpl.dll", "fhengine.dll", "fhevents.dll", "fhshl.dll", "fhsrchapi.dll", "fhsrchph.dll", "fhsvc.dll", "fhsvcctl.dll", "fhtask.dll", "fhuxadapter.dll", "fhuxapi.dll", "fhuxcommon.dll", "fhuxgraphics.dll", "fhuxpresentation.dll", "fidocredprov.dll", "filemgmt.dll", "filterds.dll", "findnetprinters.dll", "firewallapi.dll", "flightsettings.dll", "fltlib.dll", "fluencyds.dll", "fmapi.dll", "fmifs.dll", "fms.dll", "fntcache.dll", "fontext.dll", "fontprovider.dll", "fontsub.dll", "fphc.dll", "framedyn.dll", "framedynos.dll", "frameserver.dll", "frprov.dll", "fsutilext.dll", "fthsvc.dll", "fundisc.dll", "fveapi.dll", "fveapibase.dll", "fvecerts.dll", "fvecpl.dll", "fveskybackup.dll", "fveui.dll", "fvewiz.dll", "fwbase.dll", "fwcfg.dll", "fwmdmcsp.dll", "fwpolicyiomgr.dll", "fwpuclnt.dll", "fwremotesvr.dll", "gameinput.dll", "gamemode.dll", "gamestreamingext.dll", "gameux.dll", "gamingtcui.dll", "gcdef.dll", "gdi32.dll", "gdi32full.dll", "gdiplus.dll", "generaltel.dll", "geocommon.dll", "geolocation.dll", "getuname.dll", "glmf32.dll", "globinputhost.dll", "glu32.dll", "gmsaclient.dll", "gpapi.dll", "gpcsewrappercsp.dll", "gpedit.dll", "gpprefcl.dll", "gpprnext.dll", "gpscript.dll", "gpsvc.dll", "gptext.dll", "graphicscapture.dll", "graphicsperfsvc.dll", "groupinghc.dll", "hal.dll", "halextpl080.dll", "hascsp.dll", "hashtagds.dll", "hbaapi.dll", "hcproviders.dll", "hdcphandler.dll", "heatcore.dll", "helppaneproxy.dll", "hgcpl.dll", "hhsetup.dll", "hid.dll", "hidcfu.dll", "hidserv.dll", "hlink.dll", "hmkd.dll", "hnetcfg.dll", "hnetcfgclient.dll", "hnetmon.dll", "hologramworld.dll", "holoshellruntime.dll", "holoshextensions.dll", "hotplug.dll", "hrtfapo.dll", "httpapi.dll", "httpprxc.dll", "httpprxm.dll", "httpprxp.dll", "httpsdatasource.dll", "htui.dll", "hvhostsvc.dll", "hvloader.dll", "hvsigpext.dll", "hvsocket.dll", "hydrogen.dll", "ia2comproxy.dll", "ias.dll", "iasacct.dll", "iasads.dll", "iasdatastore.dll", "iashlpr.dll", "iasmigplugin.dll", "iasnap.dll", "iaspolcy.dll", "iasrad.dll", "iasrecst.dll", "iassam.dll", "iassdo.dll", "iassvcs.dll", "icfupgd.dll", "icm32.dll", "icmp.dll", "icmui.dll", "iconcodecservice.dll", "icsigd.dll", "icsvc.dll", "icsvcext.dll", "icu.dll", "icuin.dll", "icuuc.dll", "idctrls.dll", "idlisten.dll", "idndl.dll", "idstore.dll", "ieadvpack.dll", "ieapfltr.dll", "iedkcs32.dll", "ieframe.dll", "iemigplugin.dll", "iepeers.dll", "ieproxy.dll", "iernonce.dll", "iertutil.dll", "iesetup.dll", "iesysprep.dll", "ieui.dll", "ifmon.dll", "ifsutil.dll", "ifsutilx.dll", "igddiag.dll", "ihds.dll", "ikeext.dll", "imagehlp.dll", "imageres.dll", "imagesp1.dll", "imapi.dll", "imapi2.dll", "imapi2fs.dll", "imgutil.dll", "imm32.dll", "implatsetup.dll", "indexeddblegacy.dll", "inetcomm.dll", "inetmib1.dll", "inetpp.dll", "inetppui.dll", "inetres.dll", "inked.dll", "inkobjcore.dll", "inproclogger.dll", "input.dll", "inputcloudstore.dll", "inputcontroller.dll", "inputhost.dll", "inputservice.dll", "inputswitch.dll", "inseng.dll", "installservice.dll", "internetmail.dll", "internetmailcsp.dll", "invagent.dll", "iologmsg.dll", "iphlpapi.dll", "iphlpsvc.dll", "ipnathlp.dll", "ipnathlpclient.dll", "ippcommon.dll", "ippcommonproxy.dll", "iprtprio.dll", "iprtrmgr.dll", "ipsecsnp.dll", "ipsecsvc.dll", "ipsmsnap.dll", "ipxlatcfg.dll", "iri.dll", "iscsicpl.dll", "iscsidsc.dll", "iscsied.dll", "iscsiexe.dll", "iscsilog.dll", "iscsium.dll", "iscsiwmi.dll", "iscsiwmiv2.dll", "ism.dll", "itircl.dll", "itss.dll", "iuilp.dll", "iumbase.dll", "iumcrypt.dll", "iumdll.dll", "iumsdk.dll", "iyuv_32.dll", "joinproviderol.dll", "joinutil.dll", "jpmapcontrol.dll", "jpndecoder.dll", "jpninputrouter.dll", "jpnranker.dll", "jpnserviceds.dll", "jscript.dll", "jscript9.dll", "jscript9diag.dll", "jsproxy.dll", "kbd101.dll", "kbd101a.dll", "kbd101b.dll", "kbd101c.dll", "kbd103.dll", "kbd106.dll", "kbd106n.dll", "kbda1.dll", "kbda2.dll", "kbda3.dll", "kbdadlm.dll", "kbdal.dll", "kbdarme.dll", "kbdarmph.dll", "kbdarmty.dll", "kbdarmw.dll", "kbdax2.dll", "kbdaze.dll", "kbdazel.dll", "kbdazst.dll", "kbdbash.dll", "kbdbe.dll", "kbdbene.dll", "kbdbgph.dll", "kbdbgph1.dll", "kbdbhc.dll", "kbdblr.dll", "kbdbr.dll", "kbdbu.dll", "kbdbug.dll", "kbdbulg.dll", "kbdca.dll", "kbdcan.dll", "kbdcher.dll", "kbdcherp.dll", "kbdcr.dll", "kbdcz.dll", "kbdcz1.dll", "kbdcz2.dll", "kbdda.dll", "kbddiv1.dll", "kbddiv2.dll", "kbddv.dll", "kbddzo.dll", "kbdes.dll", "kbdest.dll", "kbdfa.dll", "kbdfar.dll", "kbdfc.dll", "kbdfi.dll", "kbdfi1.dll", "kbdfo.dll", "kbdfr.dll", "kbdfthrk.dll", "kbdgae.dll", "kbdgeo.dll", "kbdgeoer.dll", "kbdgeome.dll", "kbdgeooa.dll", "kbdgeoqw.dll", "kbdgkl.dll", "kbdgn.dll", "kbdgr.dll", "kbdgr1.dll", "kbdgrlnd.dll", "kbdgthc.dll", "kbdhau.dll", "kbdhaw.dll", "kbdhe.dll", "kbdhe220.dll", "kbdhe319.dll", "kbdheb.dll", "kbdhebl3.dll", "kbdhela2.dll", "kbdhela3.dll", "kbdhept.dll", "kbdhu.dll", "kbdhu1.dll", "kbdibm02.dll", "kbdibo.dll", "kbdic.dll", "kbdinasa.dll", "kbdinbe1.dll", "kbdinbe2.dll", "kbdinben.dll", "kbdindev.dll", "kbdinen.dll", "kbdinguj.dll", "kbdinhin.dll", "kbdinkan.dll", "kbdinmal.dll", "kbdinmar.dll", "kbdinori.dll", "kbdinpun.dll", "kbdintam.dll", "kbdintel.dll", "kbdinuk2.dll", "kbdir.dll", "kbdit.dll", "kbdit142.dll", "kbdiulat.dll", "kbdjav.dll", "kbdjpn.dll", "kbdkaz.dll", "kbdkhmr.dll", "kbdkni.dll", "kbdkor.dll", "kbdkurd.dll", "kbdkyr.dll", "kbdla.dll", "kbdlao.dll", "kbdlisub.dll", "kbdlisus.dll", "kbdlk41a.dll", "kbdlt.dll", "kbdlt1.dll", "kbdlt2.dll", "kbdlv.dll", "kbdlv1.dll", "kbdlvst.dll", "kbdmac.dll", "kbdmacst.dll", "kbdmaori.dll", "kbdmlt47.dll", "kbdmlt48.dll", "kbdmon.dll", "kbdmonmo.dll", "kbdmonst.dll", "kbdmyan.dll", "kbdne.dll", "kbdnec.dll", "kbdnec95.dll", "kbdnecat.dll", "kbdnecnt.dll", "kbdnepr.dll", "kbdnko.dll", "kbdno.dll", "kbdno1.dll", "kbdnso.dll", "kbdntl.dll", "kbdogham.dll", "kbdolch.dll", "kbdoldit.dll", "kbdosa.dll", "kbdosm.dll", "kbdpash.dll", "kbdphags.dll", "kbdpl.dll", "kbdpl1.dll", "kbdpo.dll", "kbdro.dll", "kbdropr.dll", "kbdrost.dll", "kbdru.dll", "kbdru1.dll", "kbdrum.dll", "kbdsf.dll", "kbdsg.dll", "kbdsl.dll", "kbdsl1.dll", "kbdsmsfi.dll", "kbdsmsno.dll", "kbdsn1.dll", "kbdsora.dll", "kbdsorex.dll", "kbdsors1.dll", "kbdsorst.dll", "kbdsp.dll", "kbdsw.dll", "kbdsw09.dll", "kbdsyr1.dll", "kbdsyr2.dll", "kbdtaile.dll", "kbdtajik.dll", "kbdtam99.dll", "kbdtat.dll", "kbdth0.dll", "kbdth1.dll", "kbdth2.dll", "kbdth3.dll", "kbdtifi.dll", "kbdtifi2.dll", "kbdtiprc.dll", "kbdtiprd.dll", "kbdtt102.dll", "kbdtuf.dll", "kbdtuq.dll", "kbdturme.dll", "kbdtzm.dll", "kbdughr.dll", "kbdughr1.dll", "kbduk.dll", "kbdukx.dll", "kbdur.dll", "kbdur1.dll", "kbdurdu.dll", "kbdus.dll", "kbdusa.dll", "kbdusl.dll", "kbdusr.dll", "kbdusx.dll", "kbduzb.dll", "kbdvntc.dll", "kbdwol.dll", "kbdyak.dll", "kbdyba.dll", "kbdycc.dll", "kbdycl.dll", "kd.dll", "kdcom.dll", "kdcpw.dll", "kdhvcom.dll", "kdnet.dll", "kdnet_uart16550.dll", "kdscli.dll", "kdstub.dll", "kdusb.dll", "kd_02_10df.dll", "kd_02_10ec.dll", "kd_02_1137.dll", "kd_02_14e4.dll", "kd_02_15b3.dll", "kd_02_1969.dll", "kd_02_19a2.dll", "kd_02_1af4.dll", "kd_02_8086.dll", "kd_07_1415.dll", "kd_0c_8086.dll", "kerbclientshared.dll", "kerberos.dll", "kernel32.dll", "kernelbase.dll", "keycredmgr.dll", "keyiso.dll", "keymgr.dll", "knobscore.dll", "knobscsp.dll", "ksuser.dll", "ktmw32.dll", "l2gpstore.dll", "l2nacp.dll", "l2sechc.dll", "laprxy.dll", "legacynetux.dll", "lfsvc.dll", "libcrypto.dll", "licensemanager.dll", "licensingcsp.dll", "licensingdiagspp.dll", "licensingwinrt.dll", "licmgr10.dll", "linkinfo.dll", "lltdapi.dll", "lltdres.dll", "lltdsvc.dll", "lmhsvc.dll", "loadperf.dll", "localsec.dll", "localspl.dll", "localui.dll", "locationapi.dll", "lockappbroker.dll", "lockcontroller.dll", "lockscreendata.dll", "loghours.dll", "logoncli.dll", "logoncontroller.dll", "lpasvc.dll", "lpk.dll", "lsasrv.dll", "lscshostpolicy.dll", "lsm.dll", "lsmproxy.dll", "lstelemetry.dll", "luainstall.dll", "luiapi.dll", "lz32.dll", "magnification.dll", "maintenanceui.dll", "manageci.dll", "mapconfiguration.dll", "mapcontrolcore.dll", "mapgeocoder.dll", "mapi32.dll", "mapistub.dll", "maprouter.dll", "mapsbtsvc.dll", "mapsbtsvcproxy.dll", "mapscsp.dll", "mapsstore.dll", "mapstoasttask.dll", "mapsupdatetask.dll", "mbaeapi.dll", "mbaeapipublic.dll", "mbaexmlparser.dll", "mbmediamanager.dll", "mbsmsapi.dll", "mbussdapi.dll", "mccsengineshared.dll", "mccspal.dll", "mciavi32.dll", "mcicda.dll", "mciqtz32.dll", "mciseq.dll", "mciwave.dll", "mcrecvsrc.dll", "mdmcommon.dll", "mdmdiagnostics.dll", "mdminst.dll", "mdmmigrator.dll", "mdmregistration.dll", "memorydiagnostic.dll", "messagingservice.dll", "mf.dll", "mf3216.dll", "mfaacenc.dll", "mfasfsrcsnk.dll", "mfaudiocnv.dll", "mfc42.dll", "mfc42u.dll", "mfcaptureengine.dll", "mfcore.dll", "mfcsubs.dll", "mfds.dll", "mfdvdec.dll", "mferror.dll", "mfh263enc.dll", "mfh264enc.dll", "mfksproxy.dll", "mfmediaengine.dll", "mfmjpegdec.dll", "mfmkvsrcsnk.dll", "mfmp4srcsnk.dll", "mfmpeg2srcsnk.dll", "mfnetcore.dll", "mfnetsrc.dll", "mfperfhelper.dll", "mfplat.dll", "mfplay.dll", "mfps.dll", "mfreadwrite.dll", "mfsensorgroup.dll", "mfsrcsnk.dll", "mfsvr.dll", "mftranscode.dll", "mfvdsp.dll", "mfvfw.dll", "mfwmaaec.dll", "mgmtapi.dll", "mi.dll", "mibincodec.dll", "midimap.dll", "migisol.dll", "miguiresource.dll", "mimefilt.dll", "mimofcodec.dll", "minstoreevents.dll", "miracastinputmgr.dll", "miracastreceiver.dll", "mirrordrvcompat.dll", "mispace.dll", "mitigationclient.dll", "miutils.dll", "mlang.dll", "mmcbase.dll", "mmcndmgr.dll", "mmcshext.dll", "mmdevapi.dll", "mmgaclient.dll", "mmgaproxystub.dll", "mmres.dll", "mobilenetworking.dll", "modemui.dll", "modernexecserver.dll", "moricons.dll", "moshost.dll", "moshostclient.dll", "moshostcore.dll", "mosstorage.dll", "mp3dmod.dll", "mp43decd.dll", "mp4sdecd.dll", "mpeval.dll", "mpg4decd.dll", "mpr.dll", "mprapi.dll", "mprddm.dll", "mprdim.dll", "mprext.dll", "mprmsg.dll", "mpssvc.dll", "mpunits.dll", "mrmcorer.dll", "mrmdeploy.dll", "mrmindexer.dll", "mrt100.dll", "mrt_map.dll", "msaatext.dll", "msac3enc.dll", "msacm32.dll", "msafd.dll", "msajapi.dll", "msalacdecoder.dll", "msalacencoder.dll", "msamrnbdecoder.dll", "msamrnbencoder.dll", "msamrnbsink.dll", "msamrnbsource.dll", "msasn1.dll", "msauddecmft.dll", "msaudite.dll", "msauserext.dll", "mscandui.dll", "mscat32.dll", "msclmd.dll", "mscms.dll", "mscoree.dll", "mscorier.dll", "mscories.dll", "msctf.dll", "msctfmonitor.dll", "msctfp.dll", "msctfui.dll", "msctfuimanager.dll", "msdadiag.dll", "msdart.dll", "msdelta.dll", "msdmo.dll", "msdrm.dll", "msdtckrm.dll", "msdtclog.dll", "msdtcprx.dll", "msdtcspoffln.dll", "msdtctm.dll", "msdtcuiu.dll", "msdtcvsp1res.dll", "msfeeds.dll", "msfeedsbs.dll", "msflacdecoder.dll", "msflacencoder.dll", "msftedit.dll", "msheif.dll", "mshtml.dll", "mshtmldac.dll", "mshtmled.dll", "mshtmler.dll", "msi.dll", "msicofire.dll", "msidcrl40.dll", "msident.dll", "msidle.dll", "msidntld.dll", "msieftp.dll", "msihnd.dll", "msiltcfg.dll", "msimg32.dll", "msimsg.dll", "msimtf.dll", "msisip.dll", "msiso.dll", "msiwer.dll", "mskeyprotcli.dll", "mskeyprotect.dll", "msls31.dll", "msmpeg2adec.dll", "msmpeg2enc.dll", "msmpeg2vdec.dll", "msobjs.dll", "msoert2.dll", "msopusdecoder.dll", "mspatcha.dll", "mspatchc.dll", "msphotography.dll", "msports.dll", "msprivs.dll", "msrahc.dll", "msrating.dll", "msrawimage.dll", "msrdc.dll", "msrdpwebaccess.dll", "msrle32.dll", "msscntrs.dll", "mssecuser.dll", "mssign32.dll", "mssip32.dll", "mssitlb.dll", "mssph.dll", "mssprxy.dll", "mssrch.dll", "mssvp.dll", "mstask.dll", "mstextprediction.dll", "mstscax.dll", "msutb.dll", "msv1_0.dll", "msvcirt.dll", "msvcp110_win.dll", "msvcp120_clr0400.dll", "msvcp140_clr0400.dll", "msvcp60.dll", "msvcp_win.dll", "msvcr100_clr0400.dll", "msvcr120_clr0400.dll", "msvcrt.dll", "msvfw32.dll", "msvidc32.dll", "msvidctl.dll", "msvideodsp.dll", "msvp9dec.dll", "msvproc.dll", "msvpxenc.dll", "mswb7.dll", "mswebp.dll", "mswmdm.dll", "mswsock.dll", "msxml3.dll", "msxml3r.dll", "msxml6.dll", "msxml6r.dll", "msyuv.dll", "mtcmodel.dll", "mtf.dll", "mtfappserviceds.dll", "mtfdecoder.dll", "mtffuzzyds.dll", "mtfserver.dll", "mtfspellcheckds.dll", "mtxclu.dll", "mtxdm.dll", "mtxex.dll", "mtxoci.dll", "muifontsetup.dll", "mycomput.dll", "mydocs.dll", "napcrypt.dll", "napinsp.dll", "naturalauth.dll", "naturallanguage6.dll", "navshutdown.dll", "ncaapi.dll", "ncasvc.dll", "ncbservice.dll", "ncdautosetup.dll", "ncdprop.dll", "nci.dll", "ncobjapi.dll", "ncrypt.dll", "ncryptprov.dll", "ncryptsslp.dll", "ncsi.dll", "ncuprov.dll", "nddeapi.dll", "ndfapi.dll", "ndfetw.dll", "ndfhcdiscovery.dll", "ndishc.dll", "ndproxystub.dll", "nduprov.dll", "negoexts.dll", "netapi32.dll", "netbios.dll", "netcenter.dll", "netcfgx.dll", "netcorehc.dll", "netdiagfx.dll", "netdriverinstall.dll", "netevent.dll", "netfxperf.dll", "neth.dll", "netid.dll", "netiohlp.dll", "netjoin.dll", "netlogon.dll", "netman.dll", "netmsg.dll", "netplwiz.dll", "netprofm.dll", "netprofmsvc.dll", "netprovfw.dll", "netprovisionsp.dll", "netsetupapi.dll", "netsetupengine.dll", "netsetupshim.dll", "netsetupsvc.dll", "netshell.dll", "nettrace.dll", "netutils.dll", "networkexplorer.dll", "networkhelper.dll", "networkicon.dll", "networkproxycsp.dll", "networkstatus.dll", "networkuxbroker.dll", "newdev.dll", "nfcradiomedia.dll", "ngccredprov.dll", "ngcctnr.dll", "ngcctnrsvc.dll", "ngcisoctnr.dll", "ngckeyenum.dll", "ngcksp.dll", "ngclocal.dll", "ngcpopkeysrv.dll", "ngcprocsp.dll", "ngcrecovery.dll", "ngcsvc.dll", "ngctasks.dll", "ninput.dll", "nlaapi.dll", "nlahc.dll", "nlasvc.dll", "nlhtml.dll", "nlmgp.dll", "nlmproxy.dll", "nlmsprep.dll", "nlsbres.dll", "nlsdata0000.dll", "nlsdata0009.dll", "nlsdl.dll", "nlslexicons0009.dll", "nmadirect.dll", "normaliz.dll", "npmproxy.dll", "npsm.dll", "nrpsrv.dll", "nshhttp.dll", "nshipsec.dll", "nshwfp.dll", "nsi.dll", "nsisvc.dll", "ntasn1.dll", "ntdll.dll", "ntdsapi.dll", "ntlanman.dll", "ntlanui2.dll", "ntlmshared.dll", "ntmarta.dll", "ntprint.dll", "ntshrui.dll", "ntvdm64.dll", "objsel.dll", "occache.dll", "ocsetapi.dll", "odbc32.dll", "odbcbcp.dll", "odbcconf.dll", "odbccp32.dll", "odbccr32.dll", "odbccu32.dll", "odbcint.dll", "odbctrac.dll", "oemlicense.dll", "offfilt.dll", "officecsp.dll", "offlinelsa.dll", "offlinesam.dll", "offreg.dll", "ole32.dll", "oleacc.dll", "oleacchooks.dll", "oleaccrc.dll", "oleaut32.dll", "oledlg.dll", "oleprn.dll", "omadmagent.dll", "omadmapi.dll", "onebackuphandler.dll", "onex.dll", "onexui.dll", "opcservices.dll", "opengl32.dll", "ortcengine.dll", "osbaseln.dll", "osksupport.dll", "osuninst.dll", "p2p.dll", "p2pgraph.dll", "p2pnetsh.dll", "p2psvc.dll", "packager.dll", "panmap.dll", "pautoenr.dll", "pcacli.dll", "pcadm.dll", "pcaevts.dll", "pcasvc.dll", "pcaui.dll", "pcpksp.dll", "pcsvdevice.dll", "pcwum.dll", "pcwutl.dll", "pdh.dll", "pdhui.dll", "peerdist.dll", "peerdistad.dll", "peerdistcleaner.dll", "peerdistsh.dll", "peerdistsvc.dll", "peopleapis.dll", "peopleband.dll", "perceptiondevice.dll", "perfctrs.dll", "perfdisk.dll", "perfnet.dll", "perfos.dll", "perfproc.dll", "perfts.dll", "phoneom.dll", "phoneproviders.dll", "phoneservice.dll", "phoneserviceres.dll", "phoneutil.dll", "phoneutilres.dll", "photowiz.dll", "pickerplatform.dll", "pid.dll", "pidgenx.dll", "pifmgr.dll", "pimstore.dll", "pkeyhelper.dll", "pktmonapi.dll", "pku2u.dll", "pla.dll", "playlistfolder.dll", "playsndsrv.dll", "playtodevice.dll", "playtomanager.dll", "playtomenu.dll", "playtoreceiver.dll", "ploptin.dll", "pmcsnap.dll", "pngfilt.dll", "pnidui.dll", "pnpclean.dll", "pnppolicy.dll", "pnpts.dll", "pnpui.dll", "pnpxassoc.dll", "pnpxassocprx.dll", "pnrpauto.dll", "pnrphc.dll", "pnrpnsp.dll", "pnrpsvc.dll", "policymanager.dll", "polstore.dll", "posetup.dll", "posyncservices.dll", "pots.dll", "powercpl.dll", "powrprof.dll", "ppcsnap.dll", "prauthproviders.dll", "prflbmsg.dll", "printui.dll", "printwsdahost.dll", "prm0009.dll", "prncache.dll", "prnfldr.dll", "prnntfy.dll", "prntvpt.dll", "profapi.dll", "profext.dll", "profprov.dll", "profsvc.dll", "profsvcext.dll", "propsys.dll", "provcore.dll", "provdatastore.dll", "provdiagnostics.dll", "provengine.dll", "provhandlers.dll", "provisioningcsp.dll", "provmigrate.dll", "provops.dll", "provplugineng.dll", "provsysprep.dll", "provthrd.dll", "proximitycommon.dll", "proximityservice.dll", "prvdmofcomp.dll", "psapi.dll", "pshed.dll", "psisdecd.dll", "psmsrv.dll", "pstask.dll", "pstorec.dll", "ptpprov.dll", "puiapi.dll", "puiobj.dll", "pushtoinstall.dll", "pwlauncher.dll", "pwrshplugin.dll", "pwsso.dll", "qasf.dll", "qcap.dll", "qdv.dll", "qdvd.dll", "qedit.dll", "qedwipes.dll", "qmgr.dll", "query.dll", "quiethours.dll", "qwave.dll", "racengn.dll", "racpldlg.dll", "radardt.dll", "radarrs.dll", "radcui.dll", "rasadhlp.dll", "rasapi32.dll", "rasauto.dll", "raschap.dll", "raschapext.dll", "rasctrs.dll", "rascustom.dll", "rasdiag.dll", "rasdlg.dll", "rasgcw.dll", "rasman.dll", "rasmans.dll", "rasmbmgr.dll", "rasmediamanager.dll", "rasmm.dll", "rasmontr.dll", "rasplap.dll", "rasppp.dll", "rastapi.dll", "rastls.dll", "rastlsext.dll", "rdbui.dll", "rdpbase.dll", "rdpcfgex.dll", "rdpcore.dll", "rdpcorets.dll", "rdpencom.dll", "rdpendp.dll", "rdpnano.dll", "rdpsaps.dll", "rdpserverbase.dll", "rdpsharercom.dll", "rdpudd.dll", "rdpviewerax.dll", "rdsappxhelper.dll", "rdsdwmdr.dll", "rdvvmtransport.dll", "rdxservice.dll", "rdxtaskfactory.dll", "reagent.dll", "reagenttask.dll", "recovery.dll", "regapi.dll", "regctrl.dll", "regidle.dll", "regsvc.dll", "reguwpapi.dll", "reinfo.dll", "remotepg.dll", "remotewipecsp.dll", "reportingcsp.dll", "resampledmo.dll", "resbparser.dll", "reseteng.dll", "resetengine.dll", "resetengonline.dll", "resourcemapper.dll", "resutils.dll", "rgb9rast.dll", "riched20.dll", "riched32.dll", "rjvmdmconfig.dll", "rmapi.dll", "rmclient.dll", "rnr20.dll", "roamingsecurity.dll", "rometadata.dll", "rotmgr.dll", "rpcepmap.dll", "rpchttp.dll", "rpcns4.dll", "rpcnsh.dll", "rpcrt4.dll", "rpcrtremote.dll", "rpcss.dll", "rsaenh.dll", "rshx32.dll", "rstrtmgr.dll", "rtffilt.dll", "rtm.dll", "rtmediaframe.dll", "rtmmvrortc.dll", "rtutils.dll", "rtworkq.dll", "rulebasedds.dll", "samcli.dll", "samlib.dll", "samsrv.dll", "sas.dll", "sbe.dll", "sbeio.dll", "sberes.dll", "sbservicetrigger.dll", "scansetting.dll", "scardbi.dll", "scarddlg.dll", "scardsvr.dll", "scavengeui.dll", "scdeviceenum.dll", "scecli.dll", "scesrv.dll", "schannel.dll", "schedcli.dll", "schedsvc.dll", "scksp.dll", "scripto.dll", "scrobj.dll", "scrptadm.dll", "scrrun.dll", "sdcpl.dll", "sdds.dll", "sdengin2.dll", "sdfhost.dll", "sdhcinst.dll", "sdiageng.dll", "sdiagprv.dll", "sdiagschd.dll", "sdohlp.dll", "sdrsvc.dll", "sdshext.dll", "searchfolder.dll", "sechost.dll", "seclogon.dll", "secproc.dll", "secproc_isv.dll", "secproc_ssp.dll", "secproc_ssp_isv.dll", "secur32.dll", "security.dll", "semgrps.dll", "semgrsvc.dll", "sendmail.dll", "sens.dll", "sensapi.dll", "sensorsapi.dll", "sensorscpl.dll", "sensorservice.dll", "sensorsnativeapi.dll", "sensorsutilsv2.dll", "sensrsvc.dll", "serialui.dll", "servicinguapi.dll", "serwvdrv.dll", "sessenv.dll", "setbcdlocale.dll", "settingmonitor.dll", "settingsync.dll", "settingsynccore.dll", "setupapi.dll", "setupcl.dll", "setupcln.dll", "setupetw.dll", "sfc.dll", "sfc_os.dll", "sgrmenclave.dll", "shacct.dll", "shacctprofile.dll", "sharedpccsp.dll", "sharedrealitysvc.dll", "sharehost.dll", "sharemediacpl.dll", "shcore.dll", "shdocvw.dll", "shell32.dll", "shellstyle.dll", "shfolder.dll", "shgina.dll", "shimeng.dll", "shimgvw.dll", "shlwapi.dll", "shpafact.dll", "shsetup.dll", "shsvcs.dll", "shunimpl.dll", "shutdownext.dll", "shutdownux.dll", "shwebsvc.dll", "signdrv.dll", "simauth.dll", "simcfg.dll", "skci.dll", "slc.dll", "slcext.dll", "slwga.dll", "smartscreenps.dll", "smbhelperclass.dll", "smbwmiv2.dll", "smiengine.dll", "smphost.dll", "smsroutersvc.dll", "sndvolsso.dll", "snmpapi.dll", "socialapis.dll", "softkbd.dll", "softpub.dll", "sortwindows61.dll", "sortwindows62.dll", "spacebridge.dll", "spacecontrol.dll", "spatializerapo.dll", "spatialstore.dll", "spbcd.dll", "speechpal.dll", "spfileq.dll", "spinf.dll", "spmpm.dll", "spnet.dll", "spoolss.dll", "spopk.dll", "spp.dll", "sppc.dll", "sppcext.dll", "sppcomapi.dll", "sppcommdlg.dll", "sppinst.dll", "sppnp.dll", "sppobjs.dll", "sppwinob.dll", "sppwmi.dll", "spwinsat.dll", "spwizeng.dll", "spwizimg.dll", "spwizres.dll", "spwmp.dll", "sqlsrv32.dll", "sqmapi.dll", "srchadmin.dll", "srclient.dll", "srcore.dll", "srevents.dll", "srh.dll", "srhelper.dll", "srm.dll", "srmclient.dll", "srmlib.dll", "srmscan.dll", "srmshell.dll", "srmstormod.dll", "srmtrace.dll", "srm_ps.dll", "srpapi.dll", "srrstr.dll", "srumapi.dll", "srumsvc.dll", "srvcli.dll", "srvsvc.dll", "srwmi.dll", "sscore.dll", "sscoreext.dll", "ssdm.dll", "ssdpapi.dll", "ssdpsrv.dll", "sspicli.dll", "sspisrv.dll", "ssshim.dll", "sstpsvc.dll", "starttiledata.dll", "startupscan.dll", "stclient.dll", "sti.dll", "sti_ci.dll", "stobject.dll", "storageusage.dll", "storagewmi.dll", "storewuauth.dll", "storprop.dll", "storsvc.dll", "streamci.dll", "structuredquery.dll", "sud.dll", "svf.dll", "svsvc.dll", "swprv.dll", "sxproxy.dll", "sxs.dll", "sxshared.dll", "sxssrv.dll", "sxsstore.dll", "synccenter.dll", "synccontroller.dll", "synchostps.dll", "syncproxy.dll", "syncreg.dll", "syncres.dll", "syncsettings.dll", "syncutil.dll", "sysclass.dll", "sysfxui.dll", "sysmain.dll", "sysntfy.dll", "syssetup.dll", "systemcpl.dll", "t2embed.dll", "tabbtn.dll", "tabbtnex.dll", "tabsvc.dll", "tapi3.dll", "tapi32.dll", "tapilua.dll", "tapimigplugin.dll", "tapiperf.dll", "tapisrv.dll", "tapisysprep.dll", "tapiui.dll", "taskapis.dll", "taskbarcpl.dll", "taskcomp.dll", "taskschd.dll", "taskschdps.dll", "tbauth.dll", "tbs.dll", "tcbloader.dll", "tcpipcfg.dll", "tcpmib.dll", "tcpmon.dll", "tcpmonui.dll", "tdh.dll", "tdlmigration.dll", "tellib.dll", "termmgr.dll", "termsrv.dll", "tetheringclient.dll", "tetheringmgr.dll", "tetheringservice.dll", "tetheringstation.dll", "textshaping.dll", "themecpl.dll", "themeservice.dll", "themeui.dll", "threadpoolwinrt.dll", "thumbcache.dll", "timebrokerclient.dll", "timebrokerserver.dll", "timesync.dll", "timesynctask.dll", "tlscsp.dll", "tokenbinding.dll", "tokenbroker.dll", "tokenbrokerui.dll", "tpmcertresources.dll", "tpmcompc.dll", "tpmtasks.dll", "tpmvsc.dll", "tquery.dll", "traffic.dll", "transportdsa.dll", "trie.dll", "trkwks.dll", "tsbyuv.dll", "tscfgwmi.dll", "tserrredir.dll", "tsf3gip.dll", "tsgqec.dll", "tsmf.dll", "tspkg.dll", "tspubwmi.dll", "tssessionux.dll", "tssrvlic.dll", "tsworkspace.dll", "ttdloader.dll", "ttdplm.dll", "ttdrecord.dll", "ttdrecordcpu.dll", "ttlsauth.dll", "ttlscfg.dll", "ttlsext.dll", "tvratings.dll", "twext.dll", "twinapi.dll", "twinui.dll", "txflog.dll", "txfw32.dll", "tzautoupdate.dll", "tzres.dll", "tzsyncres.dll", "ubpm.dll", "ucmhc.dll", "ucrtbase.dll", "ucrtbase_clr0400.dll", "ucrtbase_enclave.dll", "udhisapi.dll", "udwm.dll", "ueficsp.dll", "uexfat.dll", "ufat.dll", "uiamanager.dll", "uianimation.dll", "uiautomationcore.dll", "uicom.dll", "uireng.dll", "uiribbon.dll", "uiribbonres.dll", "ulib.dll", "umb.dll", "umdmxfrm.dll", "umpdc.dll", "umpnpmgr.dll", "umpo-overrides.dll", "umpo.dll", "umpoext.dll", "umpowmi.dll", "umrdp.dll", "unattend.dll", "unenrollhook.dll", "unimdmat.dll", "uniplat.dll", "unistore.dll", "untfs.dll", "updateagent.dll", "updatecsp.dll", "updatepolicy.dll", "upnp.dll", "upnphost.dll", "upshared.dll", "urefs.dll", "urefsv1.dll", "ureg.dll", "url.dll", "urlmon.dll", "usbcapi.dll", "usbceip.dll", "usbmon.dll", "usbperf.dll", "usbpmapi.dll", "usbtask.dll", "usbui.dll", "user32.dll", "usercpl.dll", "userdataservice.dll", "userdatatimeutil.dll", "userenv.dll", "userinitext.dll", "usermgr.dll", "usermgrcli.dll", "usermgrproxy.dll", "usoapi.dll", "usocoreps.dll", "usosvc.dll", "usp10.dll", "ustprov.dll", "utcutil.dll", "utildll.dll", "uudf.dll", "uvcmodel.dll", "uwfcfgmgmt.dll", "uwfcsp.dll", "uwfservicingapi.dll", "uxinit.dll", "uxlib.dll", "uxlibres.dll", "uxtheme.dll", "vac.dll", "van.dll", "vault.dll", "vaultcds.dll", "vaultcli.dll", "vaultroaming.dll", "vaultsvc.dll", "vbsapi.dll", "vbscript.dll", "vbssysprep.dll", "vcardparser.dll", "vdsbas.dll", "vdsdyn.dll", "vdsutil.dll", "vdsvd.dll", "vds_ps.dll", "verifier.dll", "vertdll.dll", "vfuprov.dll", "vfwwdm32.dll", "vhfum.dll", "vid.dll", "videohandlers.dll", "vidreszr.dll", "virtdisk.dll", "vmbuspipe.dll", "vmdevicehost.dll", "vmictimeprovider.dll", "vmrdvcore.dll", "voiprt.dll", "vpnike.dll", "vpnikeapi.dll", "vpnsohdesktop.dll", "vpnv2csp.dll", "vscmgrps.dll", "vssapi.dll", "vsstrace.dll", "vss_ps.dll", "w32time.dll", "w32topl.dll", "waasassessment.dll", "waasmediccapsule.dll", "waasmedicps.dll", "waasmedicsvc.dll", "wabsyncprovider.dll", "walletproxy.dll", "walletservice.dll", "wavemsp.dll", "wbemcomn.dll", "wbiosrvc.dll", "wci.dll", "wcimage.dll", "wcmapi.dll", "wcmcsp.dll", "wcmsvc.dll", "wcnapi.dll", "wcncsvc.dll", "wcneapauthproxy.dll", "wcneappeerproxy.dll", "wcnnetsh.dll", "wcnwiz.dll", "wc_storage.dll", "wdc.dll", "wdi.dll", "wdigest.dll", "wdscore.dll", "webauthn.dll", "webcamui.dll", "webcheck.dll", "webclnt.dll", "webio.dll", "webservices.dll", "websocket.dll", "wecapi.dll", "wecsvc.dll", "wephostsvc.dll", "wer.dll", "werconcpl.dll", "wercplsupport.dll", "werenc.dll", "weretw.dll", "wersvc.dll", "werui.dll", "wevtapi.dll", "wevtfwd.dll", "wevtsvc.dll", "wfapigp.dll", "wfdprov.dll", "wfdsconmgr.dll", "wfdsconmgrsvc.dll", "wfhc.dll", "whealogr.dll", "whhelper.dll", "wiaaut.dll", "wiadefui.dll", "wiadss.dll", "wiarpc.dll", "wiascanprofiles.dll", "wiaservc.dll", "wiashext.dll", "wiatrace.dll", "wificloudstore.dll", "wificonfigsp.dll", "wifidisplay.dll", "wimgapi.dll", "win32spl.dll", "win32u.dll", "winbio.dll", "winbiodatamodel.dll", "winbioext.dll", "winbrand.dll", "wincorlib.dll", "wincredprovider.dll", "wincredui.dll", "windowmanagement.dll", "windowscodecs.dll", "windowscodecsext.dll", "windowscodecsraw.dll", "windowsiotcsp.dll", "windowslivelogin.dll", "winethc.dll", "winhttp.dll", "winhttpcom.dll", "winhvemulation.dll", "winhvplatform.dll", "wininet.dll", "wininetlui.dll", "wininitext.dll", "winipcfile.dll", "winipcsecproc.dll", "winipsec.dll", "winlangdb.dll", "winlogonext.dll", "winmde.dll", "winml.dll", "winmm.dll", "winmmbase.dll", "winmsipc.dll", "winnlsres.dll", "winnsi.dll", "winreagent.dll", "winrnr.dll", "winrscmd.dll", "winrsmgr.dll", "winrssrv.dll", "winrttracing.dll", "winsatapi.dll", "winscard.dll", "winsetupui.dll", "winshfhc.dll", "winsku.dll", "winsockhc.dll", "winsqlite3.dll", "winsrpc.dll", "winsrv.dll", "winsrvext.dll", "winsta.dll", "winsync.dll", "winsyncmetastore.dll", "winsyncproviders.dll", "wintrust.dll", "wintypes.dll", "winusb.dll", "wirednetworkcsp.dll", "wisp.dll", "wkscli.dll", "wkspbrokerax.dll", "wksprtps.dll", "wkssvc.dll", "wlanapi.dll", "wlancfg.dll", "wlanconn.dll", "wlandlg.dll", "wlangpui.dll", "wlanhc.dll", "wlanhlp.dll", "wlanmediamanager.dll", "wlanmm.dll", "wlanmsm.dll", "wlanpref.dll", "wlanradiomanager.dll", "wlansec.dll", "wlansvc.dll", "wlansvcpal.dll", "wlanui.dll", "wlanutil.dll", "wldap32.dll", "wldp.dll", "wlgpclnt.dll", "wlidcli.dll", "wlidcredprov.dll", "wlidfdp.dll", "wlidnsp.dll", "wlidprov.dll", "wlidres.dll", "wlidsvc.dll", "wmadmod.dll", "wmadmoe.dll", "wmalfxgfxdsp.dll", "wmasf.dll", "wmcodecdspps.dll", "wmdmlog.dll", "wmdmps.dll", "wmdrmsdk.dll", "wmerror.dll", "wmi.dll", "wmiclnt.dll", "wmicmiplugin.dll", "wmidcom.dll", "wmidx.dll", "wmiprop.dll", "wmitomi.dll", "wmnetmgr.dll", "wmp.dll", "wmpdui.dll", "wmpdxm.dll", "wmpeffects.dll", "wmphoto.dll", "wmploc.dll", "wmpps.dll", "wmpshell.dll", "wmsgapi.dll", "wmspdmod.dll", "wmspdmoe.dll", "wmvcore.dll", "wmvdecod.dll", "wmvdspa.dll", "wmvencod.dll", "wmvsdecd.dll", "wmvsencd.dll", "wmvxencd.dll", "woftasks.dll", "wofutil.dll", "wordbreakers.dll", "workfoldersgpext.dll", "workfoldersres.dll", "workfoldersshell.dll", "workfolderssvc.dll", "wosc.dll", "wow64.dll", "wow64cpu.dll", "wow64win.dll", "wpbcreds.dll", "wpc.dll", "wpcapi.dll", "wpcdesktopmonsvc.dll", "wpcproxystubs.dll", "wpcrefreshtask.dll", "wpcwebfilter.dll", "wpdbusenum.dll", "wpdshext.dll", "wpdshserviceobj.dll", "wpdsp.dll", "wpd_ci.dll", "wpnapps.dll", "wpnclient.dll", "wpncore.dll", "wpninprc.dll", "wpnprv.dll", "wpnservice.dll", "wpnsruprov.dll", "wpnuserservice.dll", "wpportinglibrary.dll", "wpprecorderum.dll", "wptaskscheduler.dll", "wpx.dll", "ws2help.dll", "ws2_32.dll", "wscapi.dll", "wscinterop.dll", "wscisvif.dll", "wsclient.dll", "wscproxystub.dll", "wscsvc.dll", "wsdapi.dll", "wsdchngr.dll", "wsdprintproxy.dll", "wsdproviderutil.dll", "wsdscanproxy.dll", "wsecedit.dll", "wsepno.dll", "wshbth.dll", "wshcon.dll", "wshelper.dll", "wshext.dll", "wshhyperv.dll", "wship6.dll", "wshqos.dll", "wshrm.dll", "wshtcpip.dll", "wshunix.dll", "wslapi.dll", "wsmagent.dll", "wsmauto.dll", "wsmplpxy.dll", "wsmres.dll", "wsmsvc.dll", "wsmwmipl.dll", "wsnmp32.dll", "wsock32.dll", "wsplib.dll", "wsp_fs.dll", "wsp_health.dll", "wsp_sr.dll", "wtsapi32.dll", "wuapi.dll", "wuaueng.dll", "wuceffects.dll", "wudfcoinstaller.dll", "wudfplatform.dll", "wudfsmcclassext.dll", "wudfx.dll", "wudfx02000.dll", "wudriver.dll", "wups.dll", "wups2.dll", "wuuhext.dll", "wuuhosdeployment.dll", "wvc.dll", "wwaapi.dll", "wwaext.dll", "wwanapi.dll", "wwancfg.dll", "wwanhc.dll", "wwanprotdim.dll", "wwanradiomanager.dll", "wwansvc.dll", "wwapi.dll", "xamltilerender.dll", "xaudio2_8.dll", "xaudio2_9.dll", "xblauthmanager.dll", "xblgamesave.dll", "xblgamesaveext.dll", "xblgamesaveproxy.dll", "xboxgipsvc.dll", "xboxgipsynthetic.dll", "xboxnetapisvc.dll", "xinput1_4.dll", "xinput9_1_0.dll", "xinputuap.dll", "xmlfilter.dll", "xmllite.dll", "xmlprovi.dll", "xolehlp.dll", "xpsgdiconverter.dll", "xpsprint.dll", "xpspushlayer.dll", "xpsrasterservice.dll", "xpsservices.dll", "xwizards.dll", "xwreg.dll", "xwtpdui.dll", "xwtpw32.dll", "zipcontainer.dll", "zipfldr.dll", "bootsvc.dll", "halextintcpsedma.dll", "icsvcvss.dll", "ieproxydesktop.dll", "lsaadt.dll", "nlansp_c.dll", "nrtapi.dll", "opencl.dll", "pfclient.dll", "pnpdiag.dll", "prxyqry.dll", "rdpnanotransport.dll", "servicingcommon.dll", "sortwindows63.dll", "sstpcfg.dll", "tdhres.dll", "umpodev.dll", "utcapi.dll", "windlp.dll", "wow64base.dll", "wow64con.dll", "blbuires.dll", "bpainst.dll", "cbclient.dll", "certadm.dll", "certocm.dll", "certpick.dll", "csdeployres.dll", "dsdeployres.dll", "eapa3hst.dll", "eapacfg.dll", "eapahost.dll", "elsext.dll", "encdump.dll", "escmigplugin.dll", "fsclient.dll", "fsdeployres.dll", "fssminst.dll", "fssmres.dll", "fssprov.dll", "ipamapi.dll", "kpssvc.dll", "lbfoadminlib.dll", "mintdh.dll", "mmci.dll", "mmcico.dll", "mprsnap.dll", "mstsmhst.dll", "mstsmmc.dll", "muxinst.dll", "personax.dll", "rassfm.dll", "rasuser.dll", "rdmsinst.dll", "rdmsres.dll", "rtrfiltr.dll", "sacsvr.dll", "scrdenrl.dll", "sdclient.dll", "sharedstartmodel.dll", "smsrouter.dll", "spwizimg_svr.dll", "sqlcecompact40.dll", "sqlceoledb40.dll", "sqlceqp40.dll", "sqlcese40.dll", "srvmgrinst.dll", "svrmgrnc.dll", "tapisnap.dll", "tlsbrand.dll", "tsec.dll", "tsprop.dll", "tspubiconhelper.dll", "tssdjet.dll", "tsuserex.dll", "ualapi.dll", "ualsvc.dll", "umcres.dll", "updatehandlers.dll", "usocore.dll", "vssui.dll", "wsbappres.dll", "wsbonline.dll", "wsmselpl.dll", "wsmselrr.dll", "xpsfilt.dll", "xpsshhdr.dll"
+    ) and
+    not (
+      (
+        dll.name : "icuuc.dll" and dll.code_signature.subject_name in (
+          "Valve", "Valve Corp.", "Avanquest Software (7270356 Canada Inc)", "Adobe Inc."
+        ) and dll.code_signature.trusted == true
+      ) or
+      (
+        dll.name : ("timeSync.dll", "appInfo.dll") and dll.code_signature.subject_name in (
+          "VMware Inc.", "VMware, Inc."
+        ) and dll.code_signature.trusted == true
+      ) or
+      (
+        dll.name : "libcrypto.dll" and dll.code_signature.subject_name in (
+          "NoMachine S.a.r.l.", "Oculus VR, LLC"
+        ) and dll.code_signature.trusted == true
+      ) or
+      (
+        dll.name : "ucrtbase.dll" and dll.code_signature.subject_name in (
+          "Proofpoint, Inc.", "Rapid7 LLC", "Eclipse.org Foundation, Inc.", "Amazon.com Services LLC", "Windows Phone"
+        ) and dll.code_signature.trusted == true
+      ) or
+      (
+        dll.name : ("libcrypto.dll", "wmi.dll", "geolocation.dll", "kerberos.dll") and
+        dll.code_signature.subject_name == "Bitdefender SRL" and dll.code_signature.trusted == true
+      ) or
+      (dll.name : "ICMP.dll" and dll.code_signature.subject_name == "Paessler AG" and dll.code_signature.trusted == true) or
+      (dll.name : "dbghelp.dll" and dll.code_signature.trusted == true) or
+      (dll.name : "DirectML.dll" and dll.code_signature.subject_name == "Adobe Inc." and dll.code_signature.trusted == true) or
+      (dll.name : "icsvc.dll" and dll.code_signature.subject_name in ("Dell Inc", "Dell Technologies Inc.") and dll.code_signature.trusted == true) or
+      (dll.name : "offreg.dll" and dll.code_signature.subject_name == "Malwarebytes Inc." and dll.code_signature.trusted == true) or
+      (dll.name : "AppMgr.dll" and dll.code_signature.subject_name == "Autodesk, Inc" and dll.code_signature.trusted == true) or
+      (dll.name : ("SsShim.dll", "Msi.dll", "wdscore.dll") and process.name : "DismHost.exe" and dll.path : "C:\\Windows\\Temp\\*") or
+      (
+        dll.path : (
+          "?:\\Windows\\SystemApps\\*\\dxgi.dll",
+          "?:\\Windows\\SystemApps\\*\\wincorlib.dll",
+          "?:\\Windows\\dxgi.dll",
+          "?:\\Users\\*\\AppData\\Local\\LINE\\bin\\current\\dbghelp.dll"
+        )
+      )
+    )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: DLL Search Order Hijacking
+** ID: T1574.001
+** Reference URL: https://attack.mitre.org/techniques/T1574/001/
+* Sub-technique:
+** Name: DLL Side-Loading
+** ID: T1574.002
+** Reference URL: https://attack.mitre.org/techniques/T1574/002/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Compromise Client Software Binary
+** ID: T1554
+** Reference URL: https://attack.mitre.org/techniques/T1554/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-system32-executable.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-system32-executable.asciidoc
new file mode 100644
index 0000000000..237e63969c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-system32-executable.asciidoc
@@ -0,0 +1,120 @@
+[[potential-masquerading-as-system32-executable]]
+=== Potential Masquerading as System32 Executable
+
+Identifies suspicious instances of default system32 executables, either unsigned or signed with non-MS certificates. This could indicate the attempt to masquerade as system executables or backdoored and resigned legitimate executables.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* Data Source: Elastic Defend
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Persistence
+* Rule Type: BBR
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and 
+  (process.code_signature.status : "?*" or process.code_signature.exists != null) and
+  process.name: (
+      "agentactivationruntimestarter.exe", "agentservice.exe", "aitstatic.exe", "alg.exe", "apphostregistrationverifier.exe", "appidcertstorecheck.exe", "appidpolicyconverter.exe", "appidtel.exe", "applicationframehost.exe", "applysettingstemplatecatalog.exe", "applytrustoffline.exe", "approvechildrequest.exe", "appvclient.exe", "appvdllsurrogate.exe", "appvnice.exe", "appvshnotify.exe", "arp.exe", "assignedaccessguard.exe", "at.exe", "atbroker.exe", "attrib.exe", "audiodg.exe", "auditpol.exe", "authhost.exe", "autochk.exe", "autoconv.exe", "autofmt.exe", "axinstui.exe", "baaupdate.exe", "backgroundtaskhost.exe", "backgroundtransferhost.exe", "bcdboot.exe", "bcdedit.exe", "bdechangepin.exe", "bdehdcfg.exe", "bdeuisrv.exe", "bdeunlock.exe", "bioiso.exe", "bitlockerdeviceencryption.exe", "bitlockerwizard.exe", "bitlockerwizardelev.exe", "bitsadmin.exe", "bootcfg.exe", "bootim.exe", "bootsect.exe", "bridgeunattend.exe", "browserexport.exe", "browser_broker.exe", "bthudtask.exe", "bytecodegenerator.exe", "cacls.exe", "calc.exe", "camerasettingsuihost.exe", "castsrv.exe", "certenrollctrl.exe", "certreq.exe", "certutil.exe", "change.exe", "changepk.exe", "charmap.exe", "checknetisolation.exe", "chglogon.exe", "chgport.exe", "chgusr.exe", "chkdsk.exe", "chkntfs.exe", "choice.exe", "cidiag.exe", "cipher.exe", "cleanmgr.exe", "cliconfg.exe", "clip.exe", "clipup.exe", "cloudexperiencehostbroker.exe", "cloudnotifications.exe", "cmd.exe", "cmdkey.exe", "cmdl32.exe", "cmmon32.exe", "cmstp.exe", "cofire.exe", "colorcpl.exe", "comp.exe", "compact.exe", "compattelrunner.exe", "compmgmtlauncher.exe", "comppkgsrv.exe", "computerdefaults.exe", "conhost.exe", "consent.exe", "control.exe", "convert.exe", "convertvhd.exe", "coredpussvr.exe", "credentialenrollmentmanager.exe", "credentialuibroker.exe", "credwiz.exe", "cscript.exe", "csrss.exe", "ctfmon.exe", "cttune.exe", "cttunesvr.exe", "custominstallexec.exe", "customshellhost.exe", "dashost.exe", "dataexchangehost.exe", "datastorecachedumptool.exe", "dccw.exe", "dcomcnfg.exe", "ddodiag.exe", "defrag.exe", "deploymentcsphelper.exe", "desktopimgdownldr.exe", "devicecensus.exe", "devicecredentialdeployment.exe", "deviceeject.exe", "deviceenroller.exe", "devicepairingwizard.exe", "deviceproperties.exe", "dfdwiz.exe", "dfrgui.exe", "dialer.exe", "directxdatabaseupdater.exe", "diskpart.exe", "diskperf.exe", "diskraid.exe", "disksnapshot.exe", "dism.exe", "dispdiag.exe", "displayswitch.exe", "djoin.exe", "dllhost.exe", "dllhst3g.exe", "dmcertinst.exe", "dmcfghost.exe", "dmclient.exe", "dmnotificationbroker.exe", "dmomacpmo.exe", "dnscacheugc.exe", "doskey.exe", "dpapimig.exe", "dpiscaling.exe", "dpnsvr.exe", "driverquery.exe", "drvinst.exe", "dsmusertask.exe", "dsregcmd.exe", "dstokenclean.exe", "dusmtask.exe", "dvdplay.exe", "dwm.exe", "dwwin.exe", "dxdiag.exe", "dxgiadaptercache.exe", "dxpserver.exe", "eap3host.exe", "easeofaccessdialog.exe", "easinvoker.exe", "easpolicymanagerbrokerhost.exe", "edpcleanup.exe", "edpnotify.exe", "eduprintprov.exe", "efsui.exe", "ehstorauthn.exe", "eoaexperiences.exe", "esentutl.exe", "eudcedit.exe", "eventcreate.exe", "eventvwr.exe", "expand.exe", "extrac32.exe", "fc.exe", "fclip.exe", "fhmanagew.exe", "filehistory.exe", "find.exe", "findstr.exe", "finger.exe", "fixmapi.exe", "fltmc.exe", "fodhelper.exe", "fondue.exe", "fontdrvhost.exe", "fontview.exe", "forfiles.exe", "fsavailux.exe", "fsiso.exe", "fsquirt.exe", "fsutil.exe", "ftp.exe", "fvenotify.exe", "fveprompt.exe", "gamebarpresencewriter.exe", "gamepanel.exe", "genvalobj.exe", "getmac.exe", "gpresult.exe", "gpscript.exe", "gpupdate.exe", "grpconv.exe", "hdwwiz.exe", "help.exe", "hostname.exe", "hvax64.exe", "hvix64.exe", "hvsievaluator.exe", "icacls.exe", "icsentitlementhost.exe", "icsunattend.exe", "ie4uinit.exe", "ie4ushowie.exe", "iesettingsync.exe", "ieunatt.exe", "iexpress.exe", "immersivetpmvscmgrsvr.exe", "infdefaultinstall.exe", "inputswitchtoasthandler.exe", "iotstartup.exe", "ipconfig.exe", "iscsicli.exe", "iscsicpl.exe", "isoburn.exe", "klist.exe", "ksetup.exe", "ktmutil.exe", "label.exe", "languagecomponentsinstallercomhandler.exe", "launchtm.exe", "launchwinapp.exe", "legacynetuxhost.exe", "licensemanagershellext.exe", "licensingdiag.exe", "licensingui.exe", "locationnotificationwindows.exe", "locator.exe", "lockapphost.exe", "lockscreencontentserver.exe", "lodctr.exe", "logagent.exe", "logman.exe", "logoff.exe", "logonui.exe", "lpkinstall.exe", "lpksetup.exe", "lpremove.exe", "lsaiso.exe", "lsass.exe", "magnify.exe", "makecab.exe", "manage-bde.exe", "mavinject.exe", "mbaeparsertask.exe", "mblctr.exe", "mbr2gpt.exe", "mcbuilder.exe", "mdeserver.exe", "mdmagent.exe", "mdmappinstaller.exe", "mdmdiagnosticstool.exe", "mdres.exe", "mdsched.exe", "mfpmp.exe", "microsoft.uev.cscunpintool.exe", "microsoft.uev.synccontroller.exe", "microsoftedgebchost.exe", "microsoftedgecp.exe", "microsoftedgedevtools.exe", "microsoftedgesh.exe", "mmc.exe", "mmgaserver.exe", "mobsync.exe", "mountvol.exe", "mousocoreworker.exe", "mpnotify.exe", "mpsigstub.exe", "mrinfo.exe", "mschedexe.exe", "msconfig.exe", "msdt.exe", "msdtc.exe", "msfeedssync.exe", "msg.exe", "mshta.exe", "msiexec.exe", "msinfo32.exe", "mspaint.exe", "msra.exe", "msspellcheckinghost.exe", "mstsc.exe", "mtstocom.exe", "muiunattend.exe", "multidigimon.exe", "musnotification.exe", "musnotificationux.exe", "musnotifyicon.exe", "narrator.exe", "nbtstat.exe", "ndadmin.exe", "ndkping.exe", "net.exe", "net1.exe", "netbtugc.exe", "netcfg.exe", "netcfgnotifyobjecthost.exe", "netevtfwdr.exe", "nethost.exe", "netiougc.exe", "netplwiz.exe", "netsh.exe", "netstat.exe", "newdev.exe", "ngciso.exe", "nltest.exe", "notepad.exe", "nslookup.exe", "ntoskrnl.exe", "ntprint.exe", "odbcad32.exe", "odbcconf.exe", "ofdeploy.exe", "omadmclient.exe", "omadmprc.exe", "openfiles.exe", "openwith.exe", "optionalfeatures.exe", "osk.exe", "pacjsworker.exe", "packagedcwalauncher.exe", "packageinspector.exe", "passwordonwakesettingflyout.exe", "pathping.exe", "pcalua.exe", "pcaui.exe", "pcwrun.exe", "perfmon.exe", "phoneactivate.exe", "pickerhost.exe", "pinenrollmentbroker.exe", "ping.exe", "pkgmgr.exe", "pktmon.exe", "plasrv.exe", "pnpunattend.exe", "pnputil.exe", "poqexec.exe", "pospaymentsworker.exe", "powercfg.exe", "presentationhost.exe", "presentationsettings.exe", "prevhost.exe", "printbrmui.exe", "printfilterpipelinesvc.exe", "printisolationhost.exe", "printui.exe", "proquota.exe", "provlaunch.exe", "provtool.exe", "proximityuxhost.exe", "prproc.exe", "psr.exe", "pwlauncher.exe", "qappsrv.exe", "qprocess.exe", "query.exe", "quser.exe", "qwinsta.exe", "rasautou.exe", "rasdial.exe", "raserver.exe", "rasphone.exe", "rdpclip.exe", "rdpinit.exe", "rdpinput.exe", "rdpsa.exe", "rdpsaproxy.exe", "rdpsauachelper.exe", "rdpshell.exe", "rdpsign.exe", "rdrleakdiag.exe", "reagentc.exe", "recdisc.exe", "recover.exe", "recoverydrive.exe", "refsutil.exe", "reg.exe", "regedt32.exe", "regini.exe", "register-cimprovider.exe", "regsvr32.exe", "rekeywiz.exe", "relog.exe", "relpost.exe", "remoteapplifetimemanager.exe", "remoteposworker.exe", "repair-bde.exe", "replace.exe", "reset.exe", "resetengine.exe", "resmon.exe", "rmactivate.exe", "rmactivate_isv.exe", "rmactivate_ssp.exe", "rmactivate_ssp_isv.exe", "rmclient.exe", "rmttpmvscmgrsvr.exe", "robocopy.exe", "route.exe", "rpcping.exe", "rrinstaller.exe", "rstrui.exe", "runas.exe", "rundll32.exe", "runexehelper.exe", "runlegacycplelevated.exe", "runonce.exe", "runtimebroker.exe", "rwinsta.exe", "sc.exe", "schtasks.exe", "scriptrunner.exe", "sdbinst.exe", "sdchange.exe", "sdclt.exe", "sdiagnhost.exe", "searchfilterhost.exe", "searchindexer.exe", "searchprotocolhost.exe", "secedit.exe", "secinit.exe", "securekernel.exe", "securityhealthhost.exe", "securityhealthservice.exe", "securityhealthsystray.exe", "sensordataservice.exe", "services.exe", "sessionmsg.exe", "sethc.exe", "setspn.exe", "settingsynchost.exe", "setupcl.exe", "setupugc.exe", "setx.exe", "sfc.exe", "sgrmbroker.exe", "sgrmlpac.exe", "shellappruntime.exe", "shrpubw.exe", "shutdown.exe", "sigverif.exe", "sihclient.exe", "sihost.exe", "slidetoshutdown.exe", "slui.exe", "smartscreen.exe", "smss.exe", "sndvol.exe", "snippingtool.exe", "snmptrap.exe", "sort.exe", "spaceagent.exe", "spaceman.exe", "spatialaudiolicensesrv.exe", "spectrum.exe", "spoolsv.exe", "sppextcomobj.exe", "sppsvc.exe", "srdelayed.exe", "srtasks.exe", "stordiag.exe", "subst.exe", "svchost.exe", "sxstrace.exe", "syncappvpublishingserver.exe", "synchost.exe", "sysreseterr.exe", "systeminfo.exe", "systempropertiesadvanced.exe", "systempropertiescomputername.exe", "systempropertiesdataexecutionprevention.exe", "systempropertieshardware.exe", "systempropertiesperformance.exe", "systempropertiesprotection.exe", "systempropertiesremote.exe", "systemreset.exe", "systemsettingsadminflows.exe", "systemsettingsbroker.exe", "systemsettingsremovedevice.exe", "systemuwplauncher.exe", "systray.exe", "tabcal.exe", "takeown.exe", "tapiunattend.exe", "tar.exe", "taskhostw.exe", "taskkill.exe", "tasklist.exe", "taskmgr.exe", "tcblaunch.exe", "tcmsetup.exe", "tcpsvcs.exe", "thumbnailextractionhost.exe", "tieringengineservice.exe", "timeout.exe", "tokenbrokercookies.exe", "tpminit.exe", "tpmtool.exe", "tpmvscmgr.exe", "tpmvscmgrsvr.exe", "tracerpt.exe", "tracert.exe", "tscon.exe", "tsdiscon.exe", "tskill.exe", "tstheme.exe", "tswbprxy.exe", "ttdinject.exe", "tttracer.exe", "typeperf.exe", "tzsync.exe", "tzutil.exe", "ucsvc.exe", "uevagentpolicygenerator.exe", "uevappmonitor.exe", "uevtemplatebaselinegenerator.exe", "uevtemplateconfigitemgenerator.exe", "uimgrbroker.exe", "unlodctr.exe", "unregmp2.exe", "upfc.exe", "upgraderesultsui.exe", "upnpcont.exe", "upprinterinstaller.exe", "useraccountbroker.exe", "useraccountcontrolsettings.exe", "userinit.exe", "usoclient.exe", "utcdecoderhost.exe", "utilman.exe", "vaultcmd.exe", "vds.exe", "vdsldr.exe", "verclsid.exe", "verifier.exe", "verifiergui.exe", "vssadmin.exe", "vssvc.exe", "w32tm.exe", "waasmedicagent.exe", "waitfor.exe", "wallpaperhost.exe", "wbadmin.exe", "wbengine.exe", "wecutil.exe", "werfault.exe", "werfaultsecure.exe", "wermgr.exe", "wevtutil.exe", "wextract.exe", "where.exe", "whoami.exe", "wiaacmgr.exe", "wiawow64.exe", "wifitask.exe", "wimserv.exe", "winbiodatamodeloobe.exe", "windows.media.backgroundplayback.exe", "windows.warp.jitservice.exe", "windowsactiondialog.exe", "windowsupdateelevatedinstaller.exe", "wininit.exe", "winload.exe", "winlogon.exe", "winresume.exe", "winrs.exe", "winrshost.exe", "winrtnetmuahostserver.exe", "winsat.exe", "winver.exe", "wkspbroker.exe", "wksprt.exe", "wlanext.exe", "wlrmdr.exe", "wmpdmc.exe", "workfolders.exe", "wowreg32.exe", "wpcmon.exe", "wpctok.exe", "wpdshextautoplay.exe", "wpnpinst.exe", "wpr.exe", "write.exe", "wscadminui.exe", "wscollect.exe", "wscript.exe", "wsl.exe", "wsmanhttpconfig.exe", "wsmprovhost.exe", "wsqmcons.exe", "wsreset.exe", "wuapihost.exe", "wuauclt.exe", "wudfcompanionhost.exe", "wudfhost.exe", "wusa.exe", "wwahost.exe", "xblgamesavetask.exe", "xcopy.exe", "xwizard.exe", "aggregatorhost.exe", "diskusage.exe", "dtdump.exe", "ism.exe", "ndkperfcmd.exe", "ntkrla57.exe", "securekernella57.exe", "spaceutil.exe", "configure-smremoting.exe", "dcgpofix.exe", "dcpromo.exe", "dimc.exe", "diskshadow.exe", "drvcfg.exe", "escunattend.exe", "iashost.exe", "ktpass.exe", "lbfoadmin.exe", "netdom.exe", "rdspnf.exe", "rsopprov.exe", "sacsess.exe", "servermanager.exe", "servermanagerlauncher.exe", "setres.exe", "tsecimp.exe", "vssuirun.exe", "webcache.exe", "win32calc.exe", "certoc.exe", "sdndiagnosticstask.exe", "xpsrchvw.exe"
+    ) and
+  not (
+    process.code_signature.subject_name in (
+      "Microsoft Windows",
+      "Microsoft Corporation",
+      "Microsoft Windows Publisher"
+    ) and process.code_signature.trusted == true
+  ) and not process.code_signature.status: ("errorCode_endpoint*", "errorUntrustedRoot", "errorChaining") and
+  not
+  (
+    process.executable: (
+      "?:\\Program Files\\Git\\usr\\bin\\hostname.exe",
+      "?:\\Windows\\Temp\\{*}\\taskkill.exe",
+      "?:\\Users\\*\\AppData\\Local\\Temp\\{*}\\taskkill.exe",
+      "?:\\$WINDOWS.~BT\\NewOS\\Windows\\System32\\ie4ushowIE.exe",
+      "?:\\Program Files\\Git\\usr\\bin\\find.exe",
+      "?:\\Program Files (x86)\\Axence\\nVision Agent 2\\nss\\certutil.exe"
+    )
+  ) and
+  not
+  (
+    (process.name: "ucsvc.exe" and process.code_signature.subject_name == "Wellbia.com Co., Ltd." and process.code_signature.status: "trusted") or
+    (process.name: "pnputil.exe" and process.code_signature.subject_name: ("Lenovo", "HP Inc.", "Dell Inc") and process.code_signature.status: "trusted") or
+    (process.name: "convert.exe" and process.code_signature.subject_name: "ImageMagick Studio LLC" and process.code_signature.status: "trusted") or
+    (process.name: "systeminfo.exe" and process.code_signature.subject_name: "Arctic Wolf Networks, Inc." and process.code_signature.status: "trusted") or
+    (
+      process.name: "certutil.exe" and
+      process.code_signature.subject_name: (
+        "Intel(R) Online Connect Access",
+        "Fortinet Technologies (Canada) ULC"
+      ) and process.code_signature.status: "trusted"
+    ) or
+    (
+      process.name: "sfc.exe" and
+      process.code_signature.subject_name: (
+        "Cisco Systems, Inc.",
+        "CISCO SYSTEMS CANADA CO"
+      ) and process.code_signature.status: "trusted"
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Compromise Client Software Binary
+** ID: T1554
+** Reference URL: https://attack.mitre.org/techniques/T1554/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-vlc-dll.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-vlc-dll.asciidoc
new file mode 100644
index 0000000000..97240ece86
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-masquerading-as-vlc-dll.asciidoc
@@ -0,0 +1,82 @@
+[[potential-masquerading-as-vlc-dll]]
+=== Potential Masquerading as VLC DLL
+
+Identifies instances of VLC-related DLLs which are not signed by the original developer. Attackers may name their payload as legitimate applications to blend into the environment, or embedding its malicious code within legitimate applications to deceive machine learning algorithms by incorporating authentic and benign code.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* Data Source: Elastic Defend
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Persistence
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+library where host.os.type == "windows" and event.action == "load" and
+  dll.name : ("libvlc.dll", "libvlccore.dll", "axvlc.dll") and
+  not (
+    dll.code_signature.subject_name : ("VideoLAN", "716F2E5E-A03A-486B-BC67-9B18474B9D51")
+    and dll.code_signature.trusted == true
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Compromise Client Software Binary
+** ID: T1554
+** Reference URL: https://attack.mitre.org/techniques/T1554/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-memory-seeking-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-memory-seeking-activity.asciidoc
new file mode 100644
index 0000000000..d0198ceb40
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-memory-seeking-activity.asciidoc
@@ -0,0 +1,69 @@
+[[potential-memory-seeking-activity]]
+=== Potential Memory Seeking Activity
+
+Monitors for the execution of Unix utilities that may be leveraged as memory address seekers. Attackers may leverage built-in utilities to seek specific memory addresses, allowing for potential future manipulation/exploitation.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/arget13/DDexec
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and (
+  (process.name == "tail" and process.args == "-c") or
+  (process.name == "cmp" and process.args == "-i") or
+  (process.name in ("hexdump", "xxd") and process.args == "-s") or
+  (process.name == "dd" and process.args : ("skip*", "seek*"))
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Process Discovery
+** ID: T1057
+** Reference URL: https://attack.mitre.org/techniques/T1057/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-meterpreter-reverse-shell.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-meterpreter-reverse-shell.asciidoc
new file mode 100644
index 0000000000..ef9100a151
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-meterpreter-reverse-shell.asciidoc
@@ -0,0 +1,131 @@
+[[potential-meterpreter-reverse-shell]]
+=== Potential Meterpreter Reverse Shell
+
+This detection rule identifies a sample of suspicious Linux system file reads used for system fingerprinting, leveraged by the Metasploit Meterpreter shell to gather information about the target that it is executing its shell on. Detecting this pattern is indicative of a successful meterpreter shell connection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Auditbeat
+- Auditd Manager
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Auditd Manager Integration Setup*
+
+The Auditd Manager Integration receives audit events from the Linux Audit Framework which is a part of the Linux kernel.
+Auditd Manager provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system.
+
+
+*The following steps should be executed in order to add the Elastic Agent System integration "auditd_manager" on a Linux System:*
+
+- Go to the Kibana home page and click “Add integrations”.
+- In the query bar, search for “Auditd Manager” and select the integration to see more details about it.
+- Click “Add Auditd Manager”.
+- Configure the integration name and optionally add a description.
+- Review optional and advanced settings accordingly.
+- Add the newly installed “auditd manager” to an existing or a new agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+- Click “Save and Continue”.
+- For more details on the integration refer to the https://docs.elastic.co/integrations/auditd_manager[helper guide].
+
+
+*Rule Specific Setup Note*
+
+Auditd Manager subscribes to the kernel and receives events as they occur without any additional configuration.
+However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+- For this detection rule the following additional audit rules are required to be added to the integration:
+  -w /proc/net/ -p r -k audit_proc
+  -w /etc/machine-id -p wa -k machineid
+  -w /etc/passwd -p wa -k passwd
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sample by host.id, process.pid, user.id
+  [file where host.os.type == "linux" and auditd.data.syscall == "open" and auditd.data.a2 == "1b6" and file.path == "/etc/machine-id"]
+  [file where host.os.type == "linux" and auditd.data.syscall == "open" and auditd.data.a2 == "1b6" and file.path == "/etc/passwd"]
+  [file where host.os.type == "linux" and auditd.data.syscall == "open" and auditd.data.a2 == "1b6" and file.path == "/proc/net/route"]
+  [file where host.os.type == "linux" and auditd.data.syscall == "open" and auditd.data.a2 == "1b6" and file.path == "/proc/net/ipv6_route"]
+  [file where host.os.type == "linux" and auditd.data.syscall == "open" and auditd.data.a2 == "1b6" and file.path == "/proc/net/if_inet6"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-microsoft-office-sandbox-evasion.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-microsoft-office-sandbox-evasion.asciidoc
index f4d24782ac..03cc2b19ca 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-microsoft-office-sandbox-evasion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-microsoft-office-sandbox-evasion.asciidoc
@@ -5,55 +5,88 @@ Identifies the creation of a suspicious zip file prepended with special characte
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://i.blackhat.com/USA-20/Wednesday/us-20-Wardle-Office-Drama-On-macOS.pdf
 * https://www.mdsec.co.uk/2018/08/escaping-the-sandbox-microsoft-office-on-macos/
 * https://desi-jarvis.medium.com/office365-macos-sandbox-escape-fcce4fa4123c
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Defense Evasion
 
-*Version*: 100 (<<potential-microsoft-office-sandbox-evasion-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:file and not event.type:deletion and file.name:~$*.zip
-and host.os.type:macos
+[source, js]
 ----------------------------------
+event.category:file and host.os.type:(macos and macos) and not event.type:deletion and file.name:~$*.zip
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -65,18 +98,3 @@ and host.os.type:macos
 ** Name: Virtualization/Sandbox Evasion
 ** ID: T1497
 ** Reference URL: https://attack.mitre.org/techniques/T1497/
-
-[[potential-microsoft-office-sandbox-evasion-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and not event.type:deletion and file.name:~$*.zip
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-modification-of-accessibility-binaries.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-modification-of-accessibility-binaries.asciidoc
index 2a586fad0b..3846679c56 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-modification-of-accessibility-binaries.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-modification-of-accessibility-binaries.asciidoc
@@ -5,98 +5,100 @@ Windows contains accessibility features that may be launched with a key combinat
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/blog/practical-security-engineering-stateful-detection
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
-
-*Version*: 102 (<<potential-modification-of-accessibility-binaries-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Potential Modification of Accessibility Binaries
+*Triage and analysis*
+
+
 
-Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by
-accessibility features. Windows contains accessibility features that may be launched with a key combination before a
-user has logged in (ex: when the user is on the Windows logon screen). An adversary can modify the way these programs
-are launched to get a command prompt or backdoor without logging in to the system.
+*Investigating Potential Modification of Accessibility Binaries*
 
-More details can be found [here](https://attack.mitre.org/techniques/T1546/008/).
 
-This rule looks for the execution of supposed accessibility binaries that don't match any of the accessibility features
-binaries' original file names, which is likely a custom binary deployed by the attacker.
+Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by accessibility features. Windows contains accessibility features that may be launched with a key combination before a user has logged in (ex: when the user is on the Windows logon screen). An adversary can modify the way these programs are launched to get a command prompt or backdoor without logging in to the system.
+
+More details can be found https://attack.mitre.org/techniques/T1546/008/[here].
+
+This rule looks for the execution of supposed accessibility binaries that don't match any of the accessibility features binaries' original file names, which is likely a custom binary deployed by the attacker.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account and system owners and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- This activity should not happen legitimately. The security team should address any potential benign true positive (B-TP), as this configuration can put the user and the domain at risk.
 
-- This activity should not happen legitimately. The security team should address any potential benign true positive
-(B-TP), as this configuration can put the user and the domain at risk.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -104,43 +106,65 @@ for prevalence, whether they are located in expected locations, and if they are
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-("Utilman.exe", "winlogon.exe") and user.name == "SYSTEM" and
-process.args : ( "C:\\Windows\\System32\\osk.exe",
-"C:\\Windows\\System32\\Magnify.exe",
-"C:\\Windows\\System32\\Narrator.exe",
-"C:\\Windows\\System32\\Sethc.exe", "utilman.exe",
-"ATBroker.exe", "DisplaySwitch.exe", "sethc.exe" ) and
-not process.pe.original_file_name in ( "osk.exe",
-"sethc.exe", "utilman2.exe", "DisplaySwitch.exe",
-"ATBroker.exe", "ScreenMagnifier.exe", "SR.exe",
-"Narrator.exe", "magnify.exe", "MAGNIFY.EXE" ) /*
-uncomment once in winlogbeat to avoid bypass with rogue process with
-matching pe original file name */ /* and
-process.code_signature.subject_name == "Microsoft Windows" and
-process.code_signature.status == "trusted" */
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.parent.name : ("Utilman.exe", "winlogon.exe") and user.name == "SYSTEM" and
+ process.pe.original_file_name : "?*" and
+ process.args :
+    (
+    "C:\\Windows\\System32\\osk.exe",
+    "C:\\Windows\\System32\\Magnify.exe",
+    "C:\\Windows\\System32\\Narrator.exe",
+    "C:\\Windows\\System32\\Sethc.exe",
+    "utilman.exe",
+    "ATBroker.exe",
+    "DisplaySwitch.exe",
+    "sethc.exe"
+    )
+ and not process.pe.original_file_name in
+    (
+    "osk.exe",
+    "sethc.exe",
+    "utilman2.exe",
+    "DisplaySwitch.exe",
+    "ATBroker.exe",
+    "ScreenMagnifier.exe",
+    "SR.exe",
+    "Narrator.exe",
+    "magnify.exe",
+    "MAGNIFY.EXE"
+    )
+
+/* uncomment once in winlogbeat to avoid bypass with rogue process with matching pe original file name */
+/* and process.code_signature.subject_name == "Microsoft Windows" and process.code_signature.status == "trusted" */
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -152,8 +176,10 @@ process.code_signature.status == "trusted" */
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-
+* Sub-technique:
+** Name: Accessibility Features
+** ID: T1546.008
+** Reference URL: https://attack.mitre.org/techniques/T1546/008/
 * Tactic:
 ** Name: Privilege Escalation
 ** ID: TA0004
@@ -162,84 +188,7 @@ process.code_signature.status == "trusted" */
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[potential-modification-of-accessibility-binaries-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.parent.name : ("Utilman.exe", "winlogon.exe") and user.name ==
-"SYSTEM" and process.args : (
-"C:\\Windows\\System32\\osk.exe",
-"C:\\Windows\\System32\\Magnify.exe",
-"C:\\Windows\\System32\\Narrator.exe",
-"C:\\Windows\\System32\\Sethc.exe", "utilman.exe",
-"ATBroker.exe", "DisplaySwitch.exe", "sethc.exe" ) and
-not process.pe.original_file_name in ( "osk.exe",
-"sethc.exe", "utilman2.exe", "DisplaySwitch.exe",
-"ATBroker.exe", "ScreenMagnifier.exe", "SR.exe",
-"Narrator.exe", "magnify.exe", "MAGNIFY.EXE" ) /*
-uncomment once in winlogbeat to avoid bypass with rogue process with
-matching pe original file name */ /* and
-process.code_signature.subject_name == "Microsoft Windows" and
-process.code_signature.status == "trusted" */
-----------------------------------
-
-Version 11 (8.4.0 release)::
-* Formatting only
-
-Version 9 (8.3.0 release)::
-* Formatting only
-
-Version 8 (8.2.0 release)::
-* Formatting only
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:winlogon.exe and not process.name:(atbroker.exe or
-displayswitch.exe or magnify.exe or narrator.exe or osk.exe or
-sethc.exe or utilman.exe)
-----------------------------------
-
-Version 4 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.code:1 and process.parent.name:winlogon.exe and
-process.name:(atbroker.exe or displayswitch.exe or magnify.exe or
-narrator.exe or osk.exe or sethc.exe or utilman.exe)
-----------------------------------
-
-Version 3 (7.9.0 release)::
-* Formatting only
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.code:1 and process.parent.name:winlogon.exe and
-(process.name:atbroker.exe or process.name:displayswitch.exe or
-process.name:magnify.exe or process.name:narrator.exe or
-process.name:osk.exe or process.name:sethc.exe or
-process.name:utilman.exe)
-----------------------------------
-
+* Sub-technique:
+** Name: Accessibility Features
+** ID: T1546.008
+** Reference URL: https://attack.mitre.org/techniques/T1546/008/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-network-scan-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-network-scan-detected.asciidoc
new file mode 100644
index 0000000000..e904a35549
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-network-scan-detected.asciidoc
@@ -0,0 +1,74 @@
+[[potential-network-scan-detected]]
+=== Potential Network Scan Detected
+
+This rule identifies a potential port scan. A port scan is a method utilized by attackers to systematically scan a target system or network for open ports, allowing them to identify available services and potential vulnerabilities. By mapping out the open ports, attackers can gather critical information to plan and execute targeted attacks, gaining unauthorized access, compromising security, and potentially leading to data breaches, unauthorized control, or further exploitation of the targeted system or network. This rule proposes threshold logic to check for connection attempts from one source host to 20 or more destination ports.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* logs-endpoint.events.network-*
+* logs-network_traffic.*
+* packetbeat-*
+* filebeat-*
+* auditbeat-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 5
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Network
+* Tactic: Discovery
+* Tactic: Reconnaissance
+* Use Case: Network Security Monitoring
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+destination.port : * and event.action : "network_flow" and source.ip : (10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Network Service Discovery
+** ID: T1046
+** Reference URL: https://attack.mitre.org/techniques/T1046/
+* Tactic:
+** Name: Reconnaissance
+** ID: TA0043
+** Reference URL: https://attack.mitre.org/tactics/TA0043/
+* Technique:
+** Name: Active Scanning
+** ID: T1595
+** Reference URL: https://attack.mitre.org/techniques/T1595/
+* Sub-technique:
+** Name: Scanning IP Blocks
+** ID: T1595.001
+** Reference URL: https://attack.mitre.org/techniques/T1595/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-network-scan-executed-from-host.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-network-scan-executed-from-host.asciidoc
new file mode 100644
index 0000000000..cf7707acc6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-network-scan-executed-from-host.asciidoc
@@ -0,0 +1,103 @@
+[[potential-network-scan-executed-from-host]]
+=== Potential Network Scan Executed From Host
+
+This threshold rule monitors for the rapid execution of unix utilities that are capable of conducting network scans. Adversaries may leverage built-in tools such as ping, netcat or socat to execute ping sweeps across the network while attempting to evade detection or due to the lack of network mapping tools available on the compromised host.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:linux and event.action:(exec or exec_event or executed or process_started) and
+event.type:start and process.name:(ping or nping or hping or hping2 or hping3 or nc or ncat or netcat or socat)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Network Service Discovery
+** ID: T1046
+** Reference URL: https://attack.mitre.org/techniques/T1046/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-network-share-discovery.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-network-share-discovery.asciidoc
new file mode 100644
index 0000000000..035b7abf86
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-network-share-discovery.asciidoc
@@ -0,0 +1,76 @@
+[[potential-network-share-discovery]]
+=== Potential Network Share Discovery
+
+Adversaries may look for folders and drives shared on remote systems to identify sources of information to gather as a precursor for collection and identify potential systems of interest for Lateral Movement.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.*
+* logs-system.security*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Tactic: Collection
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by user.name, source.port, source.ip with maxspan=15s 
+ [file where event.action == "network-share-object-access-checked" and 
+  winlog.event_data.ShareName in ("\\\\*\\ADMIN$", "\\\\*\\C$") and 
+  source.ip != null and source.ip != "0.0.0.0" and source.ip != "::1" and source.ip != "::" and source.ip != "127.0.0.1"]
+ [file where event.action == "network-share-object-access-checked" and 
+  winlog.event_data.ShareName in ("\\\\*\\ADMIN$", "\\\\*\\C$") and 
+  source.ip != null and source.ip != "0.0.0.0" and source.ip != "::1" and source.ip != "::" and source.ip != "127.0.0.1"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Network Share Discovery
+** ID: T1135
+** Reference URL: https://attack.mitre.org/techniques/T1135/
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Data from Network Shared Drive
+** ID: T1039
+** Reference URL: https://attack.mitre.org/techniques/T1039/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-network-sweep-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-network-sweep-detected.asciidoc
new file mode 100644
index 0000000000..d8388fe0dd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-network-sweep-detected.asciidoc
@@ -0,0 +1,75 @@
+[[potential-network-sweep-detected]]
+=== Potential Network Sweep Detected
+
+This rule identifies a potential network sweep.  A network sweep is a method used by attackers to scan a target network, identifying active hosts, open ports, and available services to gather information on vulnerabilities and weaknesses. This reconnaissance helps them plan subsequent attacks and exploit potential entry points for unauthorized access, data theft, or other malicious activities. This rule proposes threshold logic to check for connection attempts from one source host to 10 or more destination hosts on commonly used network services.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* packetbeat-*
+* auditbeat-*
+* filebeat-*
+* logs-network_traffic.*
+* logs-endpoint.events.network-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 5
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Network
+* Tactic: Discovery
+* Tactic: Reconnaissance
+* Use Case: Network Security Monitoring
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+destination.port : (21 or 22 or 23 or 25 or 139 or 445 or 3389 or 5985 or 5986) and
+source.ip : (10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Network Service Discovery
+** ID: T1046
+** Reference URL: https://attack.mitre.org/techniques/T1046/
+* Tactic:
+** Name: Reconnaissance
+** ID: TA0043
+** Reference URL: https://attack.mitre.org/tactics/TA0043/
+* Technique:
+** Name: Active Scanning
+** ID: T1595
+** Reference URL: https://attack.mitre.org/techniques/T1595/
+* Sub-technique:
+** Name: Scanning IP Blocks
+** ID: T1595.001
+** Reference URL: https://attack.mitre.org/techniques/T1595/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-non-standard-port-http-https-connection.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-non-standard-port-http-https-connection.asciidoc
new file mode 100644
index 0000000000..ef179542d9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-non-standard-port-http-https-connection.asciidoc
@@ -0,0 +1,159 @@
+[[potential-non-standard-port-http-https-connection]]
+=== Potential Non-Standard Port HTTP/HTTPS connection
+
+Identifies potentially malicious processes communicating via a port paring typically not associated with HTTP/HTTPS. For example, HTTP over port 8443 or port 440 as opposed to the traditional port 80 , 443. Adversaries may make changes to the standard port a protocol uses to bypass filtering or muddle analysis/parsing of network data.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Non-Standard Port HTTP/HTTPS connection*
+
+
+Attackers may alter standard protocol ports, like using HTTP on port 8443 instead of 80, to bypass network filtering and complicate network data analysis. 
+
+This rule looks for HTTP/HTTPS processes where the destination port is not any of the default 80/443 HTTP/HTTPS ports. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Identify any signs of suspicious network activity or anomalies that may indicate command and control activity or data exfiltration. This could include unexpected traffic patterns or unusual network behavior.
+  - Investigate listening ports and open sockets to look for potential suspicious network traffic, reverse shells or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+  - !{osquery{"label":"Osquery - Retrieve Process Info","query":"SELECT name, cmdline, parent, path, uid FROM processes"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+
+
+*Related rules*
+
+
+- Suspicious Network Activity to the Internet by Previously Unknown Executable - 53617418-17b4-4e9c-8a2c-8deb8086ca4b
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors, such as reverse shells, reverse proxies, or droppers, that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+network where process.name : ("http", "https") and destination.port not in (80, 443) and event.action in (
+  "connection_attempted", "ipv4_connection_attempt_event", "connection_accepted", "ipv4_connection_accept_event"
+) and destination.ip != "127.0.0.1"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Non-Standard Port
+** ID: T1571
+** Reference URL: https://attack.mitre.org/techniques/T1571/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
+* Sub-technique:
+** Name: Web Protocols
+** ID: T1071.001
+** Reference URL: https://attack.mitre.org/techniques/T1071/001/
+* Technique:
+** Name: Encrypted Channel
+** ID: T1573
+** Reference URL: https://attack.mitre.org/techniques/T1573/
+* Sub-technique:
+** Name: Symmetric Cryptography
+** ID: T1573.001
+** Reference URL: https://attack.mitre.org/techniques/T1573/001/
+* Sub-technique:
+** Name: Asymmetric Cryptography
+** ID: T1573.002
+** Reference URL: https://attack.mitre.org/techniques/T1573/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-non-standard-port-ssh-connection.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-non-standard-port-ssh-connection.asciidoc
index c5da69891f..f3c4e345f7 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-non-standard-port-ssh-connection.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-non-standard-port-ssh-connection.asciidoc
@@ -5,7 +5,7 @@ Identifies potentially malicious processes communicating via a port paring typic
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
 
@@ -13,50 +13,50 @@ Identifies potentially malicious processes communicating via a port paring typic
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://attack.mitre.org/techniques/T1571/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Command and Control
-* macOS
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* OS: macOS
+* Data Source: Elastic Defend
 
-*Version*: 1
+*Version*: 5
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-SSH over ports apart from the traditional port 22 is highly uncommon. This rule alerts the usage of the such uncommon ports by the ssh service. Tuning is needed to have higher confidence. If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination whitelisted ports for such legitimate ssh activities.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id with maxspan=1m [process where
-event.action == "exec" and process.name:"ssh"] [network where
-process.name:"ssh" and event.action in ("connection_attempted",
-"connection_accepted") and destination.port != 22 and destination.ip
-!= "127.0.0.1" and network.transport: "tcp" ]
+[source, js]
 ----------------------------------
+sequence by process.entity_id with maxspan=1m
+  [process where event.action == "exec" and process.name:"ssh" and not process.parent.name in (
+   "rsync", "pyznap", "git", "ansible-playbook", "scp", "pgbackrest", "git-lfs", "expect", "Sourcetree", "ssh-copy-id",
+   "run"
+   )
+  ]
+  [network where process.name:"ssh" and event.action in ("connection_attempted", "connection_accepted") and 
+   destination.port != 22 and destination.ip != "127.0.0.1" and network.transport: "tcp"
+  ]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-okta-mfa-bombing-via-push-notifications.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-okta-mfa-bombing-via-push-notifications.asciidoc
new file mode 100644
index 0000000000..b7fa21b76b
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-okta-mfa-bombing-via-push-notifications.asciidoc
@@ -0,0 +1,129 @@
+[[potential-okta-mfa-bombing-via-push-notifications]]
+=== Potential Okta MFA Bombing via Push Notifications
+
+Detects when an attacker abuses the Multi-Factor authentication mechanism by repeatedly issuing login requests until the user eventually accepts the Okta push notification. An adversary may attempt to bypass the Okta MFA policies configured for an organization to obtain unauthorized access.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.mandiant.com/resources/russian-targeting-gov-business
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+* https://www.rezonate.io/blog/okta-logs-decoded-unveiling-identity-threats-through-threat-hunting/
+
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
+* Data Source: Okta
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Okta MFA Bombing via Push Notifications*
+
+
+Multi-Factor Authentication (MFA) is an effective method to prevent unauthorized access. However, some adversaries may abuse the system by repeatedly sending MFA push notifications until the user unwittingly approves the access.
+
+This rule detects when a user denies MFA Okta Verify push notifications twice, followed by a successful authentication event within a 10-minute window. This sequence could indicate an adversary's attempt to bypass the Okta MFA policy.
+
+
+*Possible investigation steps:*
+
+
+- Identify the user who received the MFA notifications by reviewing the `user.email` field.
+- Identify the time, source IP, and geographical location of the MFA requests and the subsequent successful login.
+- Review the `event.action` field to understand the nature of the events. It should include two `user.mfa.okta_verify.deny_push` actions and one `user.authentication.sso` action.
+- Ask the user if they remember receiving the MFA notifications and subsequently logging into their account.
+- Check if the MFA requests and the successful login occurred during the user's regular activity hours.
+- Look for any other suspicious activity on the account around the same time.
+- Identify whether the same pattern is repeated for other users in your organization. Multiple users receiving push notifications simultaneously might indicate a larger attack.
+
+
+*False positive analysis:*
+
+
+- Determine if the MFA push notifications were legitimate. Sometimes, users accidentally trigger MFA requests or deny them unintentionally and later approve them.
+- Check if there are known issues with the MFA system causing false denials.
+
+
+*Response and remediation:*
+
+
+- If unauthorized access is confirmed, initiate your incident response process.
+- Alert the user and your IT department immediately.
+- If possible, isolate the user's account until the issue is resolved.
+- Investigate the source of the unauthorized access.
+- If the account was accessed by an unauthorized party, determine the actions they took after logging in.
+- Consider enhancing your MFA policy to prevent such incidents in the future.
+- Encourage users to report any unexpected MFA notifications immediately.
+- Review and update your incident response plans and security policies based on the findings from the incident.
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by okta.actor.id with maxspan=10m
+  [authentication where event.dataset == "okta.system"
+    and okta.event_type == "user.mfa.okta_verify.deny_push"] with runs=5
+  until [authentication where event.dataset == "okta.system"
+    and (okta.event_type: (
+      "user.authentication.sso",
+      "user.authentication.auth_via_mfa",
+      "user.authentication.verify",
+      "user.session.start") and okta.outcome.result == "SUCCESS")]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Multi-Factor Authentication Request Generation
+** ID: T1621
+** Reference URL: https://attack.mitre.org/techniques/T1621/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-openssh-backdoor-logging-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-openssh-backdoor-logging-activity.asciidoc
index 022a884672..376f5997d7 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-openssh-backdoor-logging-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-openssh-backdoor-logging-activity.asciidoc
@@ -5,81 +5,141 @@ Identifies a Secure Shell (SSH) client or server process creating or writing to
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/eset/malware-ioc/tree/master/sshdoor
 * https://www.welivesecurity.com/wp-content/uploads/2021/01/ESET_Kobalos.pdf
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 109
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Persistence
-* Credential Access
 
-*Version*: 100 (<<potential-openssh-backdoor-logging-activity-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
 
-Updates to approved and trusted SSH executables can trigger this rule.
 
-==== Investigation guide
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
 
 
-[source,markdown]
-----------------------------------
+*Elastic Defend Integration Setup*
 
-----------------------------------
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Custom Ingest Pipeline*
+
+For versions <8.2, you need to add a custom ingest pipeline to populate `event.ingested` with @timestamp for non-elastic-agent indexes, like auditbeats/filebeat/winlogbeat etc. For more details to add a custom ingest pipeline refer to the https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html[guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type == "change" and process.executable :
-("/usr/sbin/sshd", "/usr/bin/ssh") and ( (file.name : (".*",
-"~*", "*~") and not file.name : (".cache", ".viminfo",
-".bash_history")) or file.extension : ("in", "out", "ini", "h",
-"gz", "so", "sock", "sync", "0", "1", "2", "3", "4", "5", "6", "7",
-"8", "9") or file.path : ( "/private/etc/*--",
-"/usr/share/*", "/usr/include/*", "/usr/local/include/*",
-"/private/tmp/*", "/private/var/tmp/*", "/usr/tmp/*",
-"/usr/share/man/*", "/usr/local/share/*",
-"/usr/lib/*.so.*", "/private/etc/ssh/.sshd_auth",
-"/usr/bin/ssd", "/private/var/opt/power",
-"/private/etc/ssh/ssh_known_hosts", "/private/var/html/lol",
-"/private/var/log/utmp", "/private/var/lib",
-"/var/run/sshd/sshd.pid", "/var/run/nscd/ns.pid",
-"/var/run/udev/ud.pid", "/var/run/udevd.pid" ) )
+[source, js]
 ----------------------------------
+file where host.os.type == "linux" and event.type == "change" and process.executable : ("/usr/sbin/sshd", "/usr/bin/ssh") and
+  (
+    (file.name : (".*", "~*", "*~") and not file.name : (".cache", ".viminfo", ".bash_history", ".google_authenticator",
+      ".jelenv", ".csvignore", ".rtreport")) or
+    file.extension : ("in", "out", "ini", "h", "gz", "so", "sock", "sync", "0", "1", "2", "3", "4", "5", "6", "7", "8", "9") or
+    file.path :
+    (
+      "/private/etc/*--",
+      "/usr/share/*",
+      "/usr/include/*",
+      "/usr/local/include/*",
+      "/private/tmp/*",
+      "/private/var/tmp/*",
+      "/usr/tmp/*",
+      "/usr/share/man/*",
+      "/usr/local/share/*",
+      "/usr/lib/*.so.*",
+      "/private/etc/ssh/.sshd_auth",
+      "/usr/bin/ssd",
+      "/private/var/opt/power",
+      "/private/etc/ssh/ssh_known_hosts",
+      "/private/var/html/lol",
+      "/private/var/log/utmp",
+      "/private/var/lib",
+      "/var/run/sshd/sshd.pid",
+      "/var/run/nscd/ns.pid",
+      "/var/run/udev/ud.pid",
+      "/var/run/udevd.pid"
+    )
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -91,8 +151,6 @@ file where event.type == "change" and process.executable :
 ** Name: Modify Authentication Process
 ** ID: T1556
 ** Reference URL: https://attack.mitre.org/techniques/T1556/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -101,34 +159,3 @@ file where event.type == "change" and process.executable :
 ** Name: Compromise Client Software Binary
 ** ID: T1554
 ** Reference URL: https://attack.mitre.org/techniques/T1554/
-
-[[potential-openssh-backdoor-logging-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type == "change" and process.executable :
-("/usr/sbin/sshd", "/usr/bin/ssh") and ( file.name : (".*",
-"~*") or file.extension : ("in", "out", "ini", "h", "gz", "so",
-"sock", "sync", "0", "1", "2", "3", "4", "5", "6", "7", "8", "9") or
-file.path : ( "/private/etc/*--", "/usr/share/*",
-"/usr/include/*", "/usr/local/include/*",
-"/private/tmp/*", "/private/var/tmp/*", "/usr/tmp/*",
-"/usr/share/man/*", "/usr/local/share/*",
-"/usr/lib/*.so.*", "/private/etc/ssh/.sshd_auth",
-"/usr/bin/ssd", "/private/var/opt/power",
-"/private/etc/ssh/ssh_known_hosts", "/private/var/html/lol",
-"/private/var/log/utmp", "/private/var/lib",
-"/var/run/sshd/sshd.pid", "/var/run/nscd/ns.pid",
-"/var/run/udev/ud.pid", "/var/run/udevd.pid" ) )
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-outgoing-rdp-connection-by-unusual-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-outgoing-rdp-connection-by-unusual-process.asciidoc
new file mode 100644
index 0000000000..4f6c1e4fd6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-outgoing-rdp-connection-by-unusual-process.asciidoc
@@ -0,0 +1,77 @@
+[[potential-outgoing-rdp-connection-by-unusual-process]]
+=== Potential Outgoing RDP Connection by Unusual Process
+
+Adversaries may attempt to connect to a remote system over Windows Remote Desktop Protocol (RDP) to achieve lateral movement. Adversaries may avoid using the Microsoft Terminal Services Client (mstsc.exe) binary to establish an RDP connection to evade detection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.network-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+network where host.os.type == "windows" and
+  event.action == "connection_attempted" and destination.port == 3389 and
+  destination.ip != "::1" and destination.ip != "127.0.0.1" and
+  not (
+    process.executable : (
+      "?:\\Windows\\System32\\mstsc.exe",
+      "?:\\Program Files (x86)\\mRemoteNG\\mRemoteNG.exe",
+      "?:\\Program Files (x86)\\PRTG Network Monitor\\PRTG Probe.exe",
+      "?:\\Program Files\\Azure Advanced Threat Protection Sensor\\*\\Microsoft.Tri.Sensor.exe",
+      "?:\\Program Files (x86)\\Microsoft\\Remote Desktop Connection Manager\\RDCMan.exe",
+      "?:\\Program Files\\SentinelOne\\Sentinel Agent*\\Ranger\\SentinelRanger.exe",
+      "?:\\Program Files\\Devolutions\\Remote Desktop Manager\\RemoteDesktopManager.exe",
+      "?:\\Program Files (x86)\\Devolutions\\Remote Desktop Manager\\RemoteDesktopManager.exe"
+    ) and process.code_signature.trusted == true
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: Remote Desktop Protocol
+** ID: T1021.001
+** Reference URL: https://attack.mitre.org/techniques/T1021/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-pass-the-hash-pth-attempt.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-pass-the-hash-pth-attempt.asciidoc
new file mode 100644
index 0000000000..4b9fa2e62b
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-pass-the-hash-pth-attempt.asciidoc
@@ -0,0 +1,69 @@
+[[potential-pass-the-hash-pth-attempt]]
+=== Potential Pass-the-Hash (PtH) Attempt
+
+Adversaries may pass the hash using stolen password hashes to move laterally within an environment, bypassing normal system access controls. Pass the hash (PtH) is a method of authenticating as a user without having access to the user's cleartext password.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.*
+* logs-system.security*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://attack.mitre.org/techniques/T1550/002/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:"windows" and 
+event.category : "authentication" and event.action : "logged-in" and 
+winlog.logon.type : "NewCredentials" and event.outcome : "success" and 
+user.id : (S-1-5-21-* or S-1-12-1-*) and winlog.event_data.LogonProcessName : "seclogo"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Use Alternate Authentication Material
+** ID: T1550
+** Reference URL: https://attack.mitre.org/techniques/T1550/
+* Sub-technique:
+** Name: Pass the Hash
+** ID: T1550.002
+** Reference URL: https://attack.mitre.org/techniques/T1550/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-password-spraying-of-microsoft-365-user-accounts.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-password-spraying-of-microsoft-365-user-accounts.asciidoc
index 581a86fb07..fc68f9d1ec 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-password-spraying-of-microsoft-365-user-accounts.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-password-spraying-of-microsoft-365-user-accounts.asciidoc
@@ -5,7 +5,7 @@ Identifies a high number (25) of failed Microsoft 365 user authentication attemp
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,56 +14,49 @@ Identifies a high number (25) of failed Microsoft 365 user authentication attemp
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Identity and Access
+*Tags*: 
 
-*Version*: 101 (<<potential-password-spraying-of-microsoft-365-user-accounts-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 207
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Automated processes that attempt to authenticate using expired credentials and unbounded retries may lead to false positives.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:(Exchange or
-AzureActiveDirectory) and event.category:authentication and
-event.action:("UserLoginFailed" or
-"PasswordLogonInitialAuthUsingPassword")
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:(Exchange or AzureActiveDirectory) and event.category:authentication and
+event.action:("UserLoginFailed" or "PasswordLogonInitialAuthUsingPassword")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,62 +68,3 @@ event.action:("UserLoginFailed" or
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
-
-[[potential-password-spraying-of-microsoft-365-user-accounts-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:(Exchange or
-AzureActiveDirectory) and event.category:authentication and
-event.action:("UserLoginFailed" or
-"PasswordLogonInitialAuthUsingPassword")
-----------------------------------
-
-Version 6 (8.3.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:(Exchange or
-AzureActiveDirectory) and event.category:authentication and
-event.action:("UserLoginFailed" or
-"PasswordLogonInitialAuthUsingPassword") and event.outcome:success
-----------------------------------
-
-Version 5 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:(Exchange or
-AzureActiveDirectory) and event.category:authentication and
-event.action:("UserLoginFailed" or
-"PasswordLogonInitialAuthUsingPassword") and event.outcome:failure
-----------------------------------
-
-Version 4 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:o365.audit and event.provider:AzureActiveDirectory and
-event.category:authentication and event.action:UserLoginFailed and
-event.outcome:failure
-----------------------------------
-
-Version 3 (7.13.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-init-d-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-init-d-detected.asciidoc
new file mode 100644
index 0000000000..7cd6752b03
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-init-d-detected.asciidoc
@@ -0,0 +1,189 @@
+[[potential-persistence-through-init-d-detected]]
+=== Potential Persistence Through init.d Detected
+
+Files that are placed in the /etc/init.d/ directory in Unix can be used to start custom applications, services, scripts or commands during start-up. Init.d has been mostly replaced in favor of Systemd. However, the "systemd-sysv-generator" can convert init.d files to service unit files that run at boot. Adversaries may add or alter files located in the /etc/init.d/ directory to execute malicious code upon boot in order to gain persistence on the system.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.intezer.com/blog/malware-analysis/hiddenwasp-malware-targeting-linux-systems/
+* https://pberba.github.io/security/2022/02/06/linux-threat-hunting-for-persistence-initialization-scripts-and-shell-configuration/#8-boot-or-logon-initialization-scripts-rc-scripts
+* https://www.cyberciti.biz/faq/how-to-enable-rc-local-shell-script-on-systemd-while-booting-linux-system/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 9
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Persistence Through init.d Detected*
+
+
+The `/etc/init.d` directory is used in Linux systems to store the initialization scripts for various services and daemons that are executed during system startup and shutdown.
+
+Attackers can abuse files within the `/etc/init.d/` directory to run scripts, commands or malicious software every time a system is rebooted by converting an executable file into a service file through the `systemd-sysv-generator`. After conversion, a unit file is created within the `/run/systemd/generator.late/` directory.
+
+This rule looks for the creation of new files within the `/etc/init.d/` directory. Executable files in these directories will automatically run at boot with root privileges.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+*Possible Investigation Steps*
+
+
+- Investigate the file that was created or modified.
+  - !{osquery{"label":"Osquery - Retrieve File Information","query":"SELECT * FROM file WHERE path = {{file.path}}"}}
+- Investigate whether any other files in the `/etc/init.d/` or `/run/systemd/generator.late/` directories have been altered.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE (path LIKE '/etc/init.d/%' OR path LIKE '/run/systemd/generator.late/%')"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE (path LIKE '/etc/init.d/%' OR path LIKE '/run/systemd/generator.late/%')\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate syslog through the `sudo cat /var/log/syslog | grep 'LSB'` command to find traces of the LSB header of the script (if present). If syslog is being ingested into Elasticsearch, the same can be accomplished through Kibana.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate whether this activity is related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+
+
+*False Positive Analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator who uses init.d for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Related Rules*
+
+
+- Suspicious File Creation in /etc for Persistence - 1c84dd64-7e6c-4bad-ac73-a5014ee37042
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Delete the maliciously created service/init.d files or restore it to the original configuration.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type :"linux" and event.action:("creation" or "file_create_event" or "rename" or "file_rename_event") and 
+file.path : /etc/init.d/* and not (
+  (process.name : ("dpkg" or "dockerd" or "rpm" or "dnf" or "chef-client" or "apk" or "yum" or "rpm" or
+  "vmis-launcher" or "exe" or "platform-python" or "executor" or "podman")) or
+  (file.extension : ("swp" or "swpx")) or
+  (process.name:mv and file.name:*.dpkg-remove) or
+  (process.name:sed and file.name:sed*) or
+  (process.name:systemd and file.name:*.dpkg-new)
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Initialization Scripts
+** ID: T1037
+** Reference URL: https://attack.mitre.org/techniques/T1037/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-motd-file-creation-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-motd-file-creation-detected.asciidoc
new file mode 100644
index 0000000000..803126a3db
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-motd-file-creation-detected.asciidoc
@@ -0,0 +1,181 @@
+[[potential-persistence-through-motd-file-creation-detected]]
+=== Potential Persistence Through MOTD File Creation Detected
+
+Message of the day (MOTD) is the message that is presented to the user when a user connects to a Linux server via SSH or a serial connection. Linux systems contain several default MOTD files located in the "/etc/update-motd.d/" and "/usr/lib/update-notifier/" directories. These scripts run as the root user every time a user connects over SSH or a serial connection. Adversaries may create malicious MOTD files that grant them persistence onto the target every time a user connects to the system by executing a backdoor script or command. This rule detects the creation of potentially malicious files within the default MOTD file directories.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://pberba.github.io/security/2022/02/06/linux-threat-hunting-for-persistence-initialization-scripts-and-shell-configuration/#10-boot-or-logon-initialization-scripts-motd
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 9
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Persistence Through MOTD File Creation Detected*
+
+
+The message-of-the-day (MOTD) is used to display a customizable system-wide message or information to users upon login in Linux.
+
+Attackers can abuse message-of-the-day (motd) files to run scripts, commands or malicious software every time a user connects to a system over SSH or a serial connection, by creating a new file within the `/etc/update-motd.d/` or `/usr/lib/update-notifier/` directory. Executable files in these directories automatically run with root privileges.
+
+This rule identifies the creation of new files within the `/etc/update-motd.d/` or `/usr/lib/update-notifier/` directories.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible Investigation Steps*
+
+
+- Investigate the file that was created or modified.
+  - !{osquery{"label":"Osquery - Retrieve File Information","query":"SELECT * FROM file WHERE path = {{file.path}}"}}
+- Investigate whether any other files in the `/etc/update-motd.d/` or `/usr/lib/update-notifier/` directories have been altered.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE (path LIKE '/etc/update-motd.d/%' OR path LIKE '/usr/lib/update-notifier/%')"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE (path LIKE '/etc/update-motd.d/%' OR path LIKE '/usr/lib/update-notifier/%')\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate whether the modified scripts call other malicious scripts elsewhere on the file system.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+
+
+*Related Rules*
+
+
+- Suspicious Process Spawned from MOTD Detected - 4ec47004-b34a-42e6-8003-376a123ea447
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Delete the MOTD files or restore their original configuration.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type :linux and event.action:(creation or file_create_event or rename or file_rename_event) and
+file.path : (/etc/update-motd.d/* or /usr/lib/update-notifier/*) and not process.name : (
+  dpkg or dockerd or rpm or executor or dnf or podman or ln or yum 
+) and not (
+  (process.name:mv and file.extension:dpkg-remove) or
+  (file.extension:(swp or swpx))
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Initialization Scripts
+** ID: T1037
+** Reference URL: https://attack.mitre.org/techniques/T1037/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-run-control-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-run-control-detected.asciidoc
new file mode 100644
index 0000000000..c853f22dc6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-run-control-detected.asciidoc
@@ -0,0 +1,184 @@
+[[potential-persistence-through-run-control-detected]]
+=== Potential Persistence Through Run Control Detected
+
+This rule monitors the creation/alteration of the rc.local file by a previously unknown process executable through the use of the new terms rule type. The /etc/rc.local file is used to start custom applications, services, scripts or commands during start-up. The rc.local file has mostly been replaced by Systemd. However, through the "systemd-rc-local-generator", rc.local files can be converted to services that run at boot. Adversaries may alter rc.local to execute malicious code at start-up, and gain persistence onto the system.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.intezer.com/blog/malware-analysis/hiddenwasp-malware-targeting-linux-systems/
+* https://pberba.github.io/security/2022/02/06/linux-threat-hunting-for-persistence-initialization-scripts-and-shell-configuration/#8-boot-or-logon-initialization-scripts-rc-scripts
+* https://www.cyberciti.biz/faq/how-to-enable-rc-local-shell-script-on-systemd-while-booting-linux-system/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 110
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Persistence Through Run Control Detected*
+
+
+The `rc.local` file executes custom commands or scripts during system startup on Linux systems. `rc.local` has been deprecated in favor of the use of `systemd services`, and more recent Unix distributions no longer leverage this method of on-boot script execution.
+
+There might still be users that use `rc.local` in a benign matter, so investigation to see whether the file is malicious is vital.
+
+Detection alerts from this rule indicate the creation of a new `/etc/rc.local` file.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible Investigation Steps*
+
+
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate the file that was created or modified.
+  - !{osquery{"label":"Osquery - Retrieve File Information","query":"SELECT * FROM file WHERE path = {{file.path}}"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate whether the `/lib/systemd/system/rc-local.service` and `/run/systemd/generator/multi-user.target.wants/rc-local.service` files were created through the `systemd-rc-local-generator` located at `/usr/lib/systemd/system-generators/systemd-rc-local-generator`.
+  - !{osquery{"label":"Osquery - Retrieve rc-local.service File Information","query":"SELECT * FROM file WHERE (path = '/run/systemd/generator/multi-user.target.wants/rc-local.service' OR path = '/run/systemd/generator/multi-user.target.wants/rc-local.service')"}}
+  - In case the file is not present here, `sudo systemctl status rc-local` can be executed to find the location of the rc-local unit file.
+  - If `rc-local.service` is found, manual investigation is required to check for the rc script execution. Systemd will generate syslogs in case of the execution of the rc-local service. `sudo cat /var/log/syslog | grep "rc-local.service|/etc/rc.local Compatibility"` can be executed to check for the execution of the service.
+    - If logs are found, it's likely that the contents of the `rc.local` file have been executed. Analyze the logs. In case several syslog log files are available, use a wildcard to search through all of the available logs.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate whether this activity is related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+
+
+*False Positive Analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator who uses `rc.local` for administrative purposes, consider adding exceptions for this specific administrator user account.
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Delete the `service/rc.local` files or restore their original configuration.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type : "linux" and event.category : "file" and
+event.type : ("change" or "file_modify_event" or "creation" or "file_create_event") and
+file.path : "/etc/rc.local" and not process.name : (
+  "dockerd" or "docker" or "dnf" or "dnf-automatic" or "yum" or "rpm" or "dpkg"
+) and not file.extension : ("swp" or "swpx")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Initialization Scripts
+** ID: T1037
+** Reference URL: https://attack.mitre.org/techniques/T1037/
+* Sub-technique:
+** Name: RC Scripts
+** ID: T1037.004
+** Reference URL: https://attack.mitre.org/techniques/T1037/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-systemd-udevd.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-systemd-udevd.asciidoc
new file mode 100644
index 0000000000..2f7f06b66e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-persistence-through-systemd-udevd.asciidoc
@@ -0,0 +1,104 @@
+[[potential-persistence-through-systemd-udevd]]
+=== Potential Persistence Through Systemd-udevd
+
+Monitors for the creation of rule files that are used by systemd-udevd to manage device nodes and handle kernel device events in the Linux operating system. Systemd-udevd can be exploited for persistence by adversaries by creating malicious udev rules that trigger on specific events, executing arbitrary commands or payloads whenever a certain device is plugged in or recognized by the system.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click Add integrations.
+- In the query bar, search for Elastic Defend and select the integration to see more details about it.
+- Click Add Elastic Defend.
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either Traditional Endpoints or Cloud Workloads.
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in New agent policy name. If other agent policies already exist, you can click the Existing hosts tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click Save and Continue.
+- To complete the integration, select Add Elastic Agent to your hosts and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:"linux" and event.category:"file" and
+event.type:("change" or "file_modify_event" or "creation" or "file_create_event") and
+file.path:/lib/udev/* and process.executable:* and not (
+   process.name:("dockerd" or "docker" or "dpkg" or "dnf" or "dnf-automatic" or "yum" or "rpm" or "systemd-hwdb" or
+     "podman" or "buildah") or file.extension : ("swp" or "swpx")
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Initialization Scripts
+** ID: T1037
+** Reference URL: https://attack.mitre.org/techniques/T1037/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-atom-init-script-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-atom-init-script-modification.asciidoc
index 027f323462..b747622fe0 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-atom-init-script-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-atom-init-script-modification.asciidoc
@@ -5,55 +5,88 @@ Identifies modifications to the Atom desktop text editor Init File. Adversaries
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/D00MFist/PersistentJXA/blob/master/AtomPersist.js
 * https://flight-manual.atom.io/hacking-atom/sections/the-init-file/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<potential-persistence-via-atom-init-script-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:"file" and not event.type:"deletion" and
-file.path:/Users/*/.atom/init.coffee and not process.name:(Atom or
-xpcproxy) and not user.name:root
+[source, js]
 ----------------------------------
+event.category:file and host.os.type:macos and not event.type:"deletion" and
+ file.path:/Users/*/.atom/init.coffee and not process.name:(Atom or xpcproxy) and not user.name:root
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -65,13 +98,3 @@ xpcproxy) and not user.name:root
 ** Name: Boot or Logon Initialization Scripts
 ** ID: T1037
 ** Reference URL: https://attack.mitre.org/techniques/T1037/
-
-[[potential-persistence-via-atom-init-script-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-login-hook.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-login-hook.asciidoc
index fad726a0ed..2c2fba5d7a 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-login-hook.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-login-hook.asciidoc
@@ -5,67 +5,97 @@ Identifies the creation or modification of the login window property list (plist
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/D00MFist/PersistentJXA/blob/master/LoginScript.js
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
-
-*Version*: 101 (<<potential-persistence-via-login-hook-history, version history>>)
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+
+*Triage and analysis*
+
 
 Starting in Mac OS X 10.7 (Lion), users can specify certain applications to be re-opened when a user reboots their machine. This can be abused to establish or maintain persistence on a compromised system.
-----------------------------------
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:"file" and not event.type:"deletion" and
-file.name:"com.apple.loginwindow.plist" and process.name:(* and not
-(systemmigrationd or DesktopServicesHelper or diskmanagementd or rsync
-or launchd or cfprefsd or xpcproxy or ManagedClient or MCXCompositor
-or backupd or "iMazing Profile Editor" ))
+[source, js]
 ----------------------------------
+event.category:file and host.os.type:macos and not event.type:"deletion" and
+ file.name:"com.apple.loginwindow.plist" and
+ not process.name: (systemmigrationd or DesktopServicesHelper or diskmanagementd or rsync or launchd or cfprefsd or xpcproxy or ManagedClient or MCXCompositor or backupd or "iMazing Profile Editor" or storagekitd or CloneKitService)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,8 +107,6 @@ or backupd or "iMazing Profile Editor" ))
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -87,27 +115,3 @@ or backupd or "iMazing Profile Editor" ))
 ** Name: Plist File Modification
 ** ID: T1647
 ** Reference URL: https://attack.mitre.org/techniques/T1647/
-
-[[potential-persistence-via-login-hook-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:"file" and not event.type:"deletion" and
-file.name:"com.apple.loginwindow.plist" and process.name:(* and not
-(systemmigrationd or DesktopServicesHelper or diskmanagementd or rsync
-or launchd or cfprefsd or xpcproxy or ManagedClient or MCXCompositor))
-----------------------------------
-
-Version 2 (7.13.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-periodic-tasks.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-periodic-tasks.asciidoc
index 10a37f4639..347b4f9b69 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-periodic-tasks.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-periodic-tasks.asciidoc
@@ -5,56 +5,89 @@ Identifies the creation or modification of the default configuration for periodi
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://opensource.apple.com/source/crontabs/crontabs-13/private/etc/defaults/periodic.conf.auto.html
 * https://www.oreilly.com/library/view/mac-os-x/0596003706/re328.html
 * https://github.com/D00MFist/PersistentJXA/blob/master/PeriodicPersist.js
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<potential-persistence-via-periodic-tasks-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:"file" and not event.type:"deletion" and
-file.path:(/private/etc/periodic/* or
-/private/etc/defaults/periodic.conf or /private/etc/periodic.conf)
+[source, js]
 ----------------------------------
+event.category:file and host.os.type:macos and not event.type:"deletion" and
+ file.path:(/private/etc/periodic/* or /private/etc/defaults/periodic.conf or /private/etc/periodic.conf)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,13 +99,7 @@ file.path:(/private/etc/periodic/* or
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[potential-persistence-via-periodic-tasks-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Cron
+** ID: T1053.003
+** Reference URL: https://attack.mitre.org/techniques/T1053/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-time-provider-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-time-provider-modification.asciidoc
index 8b5062dcc3..a6d7ce5526 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-time-provider-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-persistence-via-time-provider-modification.asciidoc
@@ -5,53 +5,128 @@ Identifies modification of the Time Provider. Adversaries may establish persiste
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://pentestlab.blog/2019/10/22/persistence-time-providers/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 109
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<potential-persistence-via-time-provider-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Persistence via Time Provider Modification*
+
+
+The Time Provider architecture in Windows is responsible for obtaining accurate timestamps from network devices or clients. It is implemented as a DLL file in the System32 folder and is initiated by the W32Time service during Windows startup. Adversaries may exploit this by registering and enabling a malicious DLL as a time provider to establish persistence. 
+
+This rule identifies changes in the registry paths associated with Time Providers, specifically targeting the addition of new DLL files.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Examine whether the DLL is signed.
+- Retrieve the DLL and determine if it is malicious:
+  - Analyze the file using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Restore Time Provider settings to the desired state.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type:"change" and registry.path:"HKLM\\SYSTEM\\
-*ControlSet*\\Services\\W32Time\\TimeProviders\\*" and
-registry.data.strings:"*.dll"
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type:"change" and
+  registry.path: (
+    "HKLM\\SYSTEM\\*ControlSet*\\Services\\W32Time\\TimeProviders\\*",
+    "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\W32Time\\TimeProviders\\*"
+  ) and
+  registry.data.strings:"*.dll" and
+  not
+  (
+    process.executable : "?:\\Windows\\System32\\msiexec.exe" and
+    registry.data.strings : "?:\\Program Files\\VMware\\VMware Tools\\vmwTimeProvider\\vmwTimeProvider.dll"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -63,19 +138,19 @@ registry.data.strings:"*.dll"
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[potential-persistence-via-time-provider-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Time Providers
+** ID: T1547.003
+** Reference URL: https://attack.mitre.org/techniques/T1547/003/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Sub-technique:
+** Name: Time Providers
+** ID: T1547.003
+** Reference URL: https://attack.mitre.org/techniques/T1547/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-port-monitor-or-print-processor-registration-abuse.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-port-monitor-or-print-processor-registration-abuse.asciidoc
index 9485d49086..72a0e1bc19 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-port-monitor-or-print-processor-registration-abuse.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-port-monitor-or-print-processor-registration-abuse.asciidoc
@@ -5,57 +5,59 @@ Identifies port monitor and print processor registry modifications. Adversaries
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.welivesecurity.com/2020/05/21/no-game-over-winnti-group/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 100 (<<potential-port-monitor-or-print-processor-registration-abuse-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-registry.path :
-("HKLM\\SYSTEM\\*ControlSet*\\Control\\Print\\Monitors\\*", "HKLM\
-\SYSTEM\\*ControlSet*\\Control\\Print\\Environments\\Windows*\\Print
-Processors\\*") and registry.data.strings : "*.dll" and /* exclude
-SYSTEM SID - look for changes by non-SYSTEM user */ not user.id :
-"S-1-5-18"
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type in ("creation", "change") and
+  registry.path : (
+      "HKLM\\SYSTEM\\*ControlSet*\\Control\\Print\\Monitors\\*",
+      "HKLM\\SYSTEM\\*ControlSet*\\Control\\Print\\Environments\\Windows*\\Print Processors\\*",
+      "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Control\\Print\\Monitors\\*",
+      "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Control\\Print\\Environments\\Windows*\\Print Processors\\*"
+  ) and registry.data.strings : "*.dll" and
+  /* exclude SYSTEM SID - look for changes by non-SYSTEM user */
+  not user.id : "S-1-5-18"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -67,8 +69,14 @@ SYSTEM SID - look for changes by non-SYSTEM user */ not user.id :
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-
+* Sub-technique:
+** Name: Port Monitors
+** ID: T1547.010
+** Reference URL: https://attack.mitre.org/techniques/T1547/010/
+* Sub-technique:
+** Name: Print Processors
+** ID: T1547.012
+** Reference URL: https://attack.mitre.org/techniques/T1547/012/
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -77,27 +85,11 @@ SYSTEM SID - look for changes by non-SYSTEM user */ not user.id :
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[potential-port-monitor-or-print-processor-registration-abuse-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-registry.path :
-("HKLM\\SYSTEM\\*ControlSet*\\Control\\Print\\Monitors\\*", "HLLM\
-\SYSTEM\\*ControlSet*\\Control\\Print\\Environments\\Windows*\\Print
-Processors\\*") and registry.data.strings : "*.dll" and /* exclude
-SYSTEM SID - look for changes by non-SYSTEM user */ not user.id :
-"S-1-5-18"
-----------------------------------
-
+* Sub-technique:
+** Name: Port Monitors
+** ID: T1547.010
+** Reference URL: https://attack.mitre.org/techniques/T1547/010/
+* Sub-technique:
+** Name: Print Processors
+** ID: T1547.012
+** Reference URL: https://attack.mitre.org/techniques/T1547/012/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-powershell-hacktool-script-by-author.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-powershell-hacktool-script-by-author.asciidoc
new file mode 100644
index 0000000000..0e70bdba80
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-powershell-hacktool-script-by-author.asciidoc
@@ -0,0 +1,115 @@
+[[potential-powershell-hacktool-script-by-author]]
+=== Potential PowerShell HackTool Script by Author
+
+Detects known PowerShell offensive tooling author's name in PowerShell scripts. Attackers commonly use out-of-the-box offensive tools without modifying the code, which may still contain the author artifacts. This rule identifies common author handles found in popular PowerShell scripts used for red team exercises.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0109_windows_powershell_script_block_log.md
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: PowerShell Logs
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:windows and event.category:process and
+  powershell.file.script_block_text : (
+      "mattifestation" or "JosephBialek" or
+      "harmj0y" or "ukstufus" or
+      "SecureThisShit" or "Matthew Graeber" or
+      "secabstraction" or "mgeeky" or
+      "oddvarmoe" or "am0nsec" or
+      "obscuresec" or "sixdub" or
+      "darkoperator" or "funoverip" or
+      "rvrsh3ll" or "kevin_robertson" or
+      "dafthack" or "r4wd3r" or
+      "danielhbohannon" or "OneLogicalMyth" or
+      "cobbr_io" or "xorrior" or
+      "PetrMedonos" or "citronneur" or
+      "eladshamir" or "RastaMouse" or
+      "enigma0x3" or "FuzzySec" or
+      "424f424f" or "jaredhaight" or
+      "fullmetalcache" or "Hubbl3" or
+      "curi0usJack" or "Cx01N" or
+      "itm4n" or "nurfed1" or
+      "cfalta" or "Scott Sutherland" or
+      "_nullbind" or "_tmenochet" or
+      "Boe Prox" or "jaredcatkinson" or
+      "ChrisTruncer" or "monoxgas" or
+      "TheRealWover" or "splinter_code"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-powershell-hacktool-script-by-function-names.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-powershell-hacktool-script-by-function-names.asciidoc
new file mode 100644
index 0000000000..01d2847330
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-powershell-hacktool-script-by-function-names.asciidoc
@@ -0,0 +1,353 @@
+[[potential-powershell-hacktool-script-by-function-names]]
+=== Potential PowerShell HackTool Script by Function Names
+
+Detects known PowerShell offensive tooling functions names in PowerShell scripts. Attackers commonly use out-of-the-box offensive tools without modifying the code. This rule aim is to take advantage of that.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0109_windows_powershell_script_block_log.md
+* https://github.com/BC-SECURITY/Empire
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: PowerShell Logs
+
+*Version*: 111
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential PowerShell HackTool Script by Function Names*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+Adversaries often exploit PowerShell's capabilities to execute malicious scripts and perform various attacks. This rule identifies known offensive tooling function names in PowerShell scripts, as attackers commonly use out-of-the-box tools without modifying the code. By monitoring these specific function names, the rule aims to detect and alert potential malicious PowerShell activity.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine the script's execution context, such as the user account, privileges, the role of the system on which it was executed, and any relevant timestamps.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Evaluate whether the user needs to use PowerShell to complete tasks.
+- Investigate the origin of the PowerShell script, including its source, download method, and any associated URLs or IP addresses.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the script using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+
+*False positive analysis*
+
+
+- This rule may generate false positives if legitimate scripts or tools used by administrators contain any of the listed function names. These function names are commonly associated with offensive tooling, but they may also be present in benign scripts or tools.
+- To handle these false positives consider adding exceptions - preferably with a combination of full file path and users.
+
+
+*Related Rules*
+
+
+- PowerShell Invoke-NinjaCopy script - b8386923-b02c-4b94-986a-d223d9b01f88
+- PowerShell Suspicious Discovery Related Windows API Functions - 61ac3638-40a3-44b2-855a-985636ca985e
+- Potential Process Injection via PowerShell - 2e29e96a-b67c-455a-afe4-de6183431d0d
+- PowerShell Keylogging Script - bd2c86a0-8b61-4457-ab38-96943984e889
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+  - If malicious activity is confirmed, perform a broader investigation to identify the scope of the compromise and determine the appropriate remediation steps.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Reimage the host operating system or restore the compromised files to clean versions.
+- Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    "Add-DomainGroupMember" or "Add-DomainObjectAcl" or
+    "Add-RemoteConnection" or "Add-ServiceDacl" or
+    "Add-Win32Type" or "Convert-ADName" or
+    "Convert-LDAPProperty" or "ConvertFrom-LDAPLogonHours" or
+    "ConvertFrom-UACValue" or "Copy-ArrayOfMemAddresses" or
+    "Create-NamedPipe" or "Create-ProcessWithToken" or
+    "Create-RemoteThread" or "Create-SuspendedWinLogon" or
+    "Create-WinLogonProcess" or "Emit-CallThreadStub" or
+    "Enable-SeAssignPrimaryTokenPrivilege" or "Enable-SeDebugPrivilege" or
+    "Enum-AllTokens" or "Export-PowerViewCSV" or
+    "Find-AVSignature" or "Find-AppLockerLog" or
+    "Find-DomainLocalGroupMember" or "Find-DomainObjectPropertyOutlier" or
+    "Find-DomainProcess" or "Find-DomainShare" or
+    "Find-DomainUserEvent" or "Find-DomainUserLocation" or
+    "Find-InterestingDomainAcl" or "Find-InterestingDomainShareFile" or
+    "Find-InterestingFile" or "Find-LocalAdminAccess" or
+    "Find-PSScriptsInPSAppLog" or "Find-PathDLLHijack" or
+    "Find-ProcessDLLHijack" or "Find-RDPClientConnection" or
+    "Get-AllAttributesForClass" or "Get-CachedGPPPassword" or
+    "Get-DecryptedCpassword" or "Get-DecryptedSitelistPassword" or
+    "Get-DelegateType" or "New-RelayEnumObject" or
+    "Get-DomainDFSShare" or "Get-DomainDFSShareV1" or
+    "Get-DomainDFSShareV2" or "Get-DomainDNSRecord" or
+    "Get-DomainDNSZone" or "Get-DomainFileServer" or
+    "Get-DomainForeignGroupMember" or "Get-DomainForeignUser" or
+    "Get-DomainGPO" or "Get-DomainGPOComputerLocalGroupMapping" or
+    "Get-DomainGPOLocalGroup" or "Get-DomainGPOUserLocalGroupMapping" or
+    "Get-DomainGUIDMap" or "Get-DomainGroup" or
+    "Get-DomainGroupMember" or "Get-DomainGroupMemberDeleted" or
+    "Get-DomainManagedSecurityGroup" or "Get-DomainOU" or
+    "Get-DomainObject" or "Get-DomainObjectAcl" or
+    "Get-DomainObjectAttributeHistory" or "Get-DomainObjectLinkedAttributeHistory" or
+    "Get-DomainPolicyData" or "Get-DomainSID" or
+    "Get-DomainSPNTicket" or "Get-DomainSearcher" or
+    "Get-DomainSite" or "Get-DomainSubnet" or
+    "Get-DomainTrust" or "Get-DomainTrustMapping" or
+    "Get-DomainUser" or "Get-DomainUserEvent" or
+    "Get-Forest" or "Get-ForestDomain" or
+    "Get-ForestGlobalCatalog" or "Get-ForestSchemaClass" or
+    "Get-ForestTrust" or "Get-GPODelegation" or
+    "Get-GPPAutologon" or "Get-GPPInnerField" or
+    "Get-GPPInnerFields" or "Get-GPPPassword" or
+    "Get-GptTmpl" or "Get-GroupsXML" or
+    "Get-HttpStatus" or "Get-ImageNtHeaders" or
+    "Get-Keystrokes" or "New-SOASerialNumberArray" or 
+    "Get-MemoryProcAddress" or "Get-MicrophoneAudio" or
+    "Get-ModifiablePath" or "Get-ModifiableRegistryAutoRun" or
+    "Get-ModifiableScheduledTaskFile" or "Get-ModifiableService" or
+    "Get-ModifiableServiceFile" or "Get-Name" or
+    "Get-NetComputerSiteName" or "Get-NetLocalGroup" or
+    "Get-NetLocalGroupMember" or "Get-NetLoggedon" or
+    "Get-NetRDPSession" or "Get-NetSession" or
+    "Get-NetShare" or "Get-PEArchitecture" or
+    "Get-PEBasicInfo" or "Get-PEDetailedInfo" or
+    "Get-PathAcl" or "Get-PrimaryToken" or
+    "Get-ProcAddress" or "Get-ProcessTokenGroup" or
+    "Get-ProcessTokenPrivilege" or "Get-ProcessTokenType" or
+    "Get-RegLoggedOn" or "Get-RegistryAlwaysInstallElevated" or
+    "Get-RegistryAutoLogon" or "Get-RemoteProcAddress" or
+    "Get-Screenshot" or "Get-ServiceDetail" or
+    "Get-SiteListPassword" or "Get-SitelistField" or
+    "Get-System" or "Get-SystemNamedPipe" or
+    "Get-SystemToken" or "Get-ThreadToken" or
+    "Get-TimedScreenshot" or "Get-TokenInformation" or
+    "Get-TopPort" or "Get-UnattendedInstallFile" or
+    "Get-UniqueTokens" or "Get-UnquotedService" or
+    "Get-VaultCredential" or "Get-VaultElementValue" or
+    "Get-VirtualProtectValue" or "Get-VolumeShadowCopy" or
+    "Get-WMIProcess" or "Get-WMIRegCachedRDPConnection" or
+    "Get-WMIRegLastLoggedOn" or "Get-WMIRegMountedDrive" or
+    "Get-WMIRegProxy" or "Get-WebConfig" or
+    "Get-Win32Constants" or "Get-Win32Functions" or
+    "Get-Win32Types" or "Import-DllImports" or
+    "Import-DllInRemoteProcess" or "Inject-LocalShellcode" or
+    "Inject-RemoteShellcode" or "Install-ServiceBinary" or
+    "Invoke-CompareAttributesForClass" or "Invoke-CreateRemoteThread" or
+    "Invoke-CredentialInjection" or "Invoke-DllInjection" or
+    "Invoke-EventVwrBypass" or "Invoke-ImpersonateUser" or
+    "Invoke-Kerberoast" or "Invoke-MemoryFreeLibrary" or
+    "Invoke-MemoryLoadLibrary" or
+    "Invoke-Mimikatz" or "Invoke-NinjaCopy" or
+    "Invoke-PatchDll" or "Invoke-Portscan" or
+    "Invoke-PrivescAudit" or "Invoke-ReflectivePEInjection" or
+    "Invoke-ReverseDnsLookup" or "Invoke-RevertToSelf" or
+    "Invoke-ServiceAbuse" or "Invoke-Shellcode" or
+    "Invoke-TokenManipulation" or "Invoke-UserImpersonation" or
+    "Invoke-WmiCommand" or "Mount-VolumeShadowCopy" or
+    "New-ADObjectAccessControlEntry" or "New-DomainGroup" or
+    "New-DomainUser" or "New-DynamicParameter" or
+    "New-InMemoryModule" or
+    "New-ThreadedFunction" or "New-VolumeShadowCopy" or
+    "Out-CompressedDll" or "Out-EncodedCommand" or
+    "Out-EncryptedScript" or "Out-Minidump" or
+    "PortScan-Alive" or "Portscan-Port" or
+    "Remove-DomainGroupMember" or "Remove-DomainObjectAcl" or
+    "Remove-RemoteConnection" or "Remove-VolumeShadowCopy" or
+    "Restore-ServiceBinary" or "Set-DesktopACLToAllowEveryone" or
+    "Set-DesktopACLs" or "Set-DomainObject" or
+    "Set-DomainObjectOwner" or "Set-DomainUserPassword" or
+    "Set-ServiceBinaryPath" or "Sub-SignedIntAsUnsigned" or
+    "Test-AdminAccess" or "Test-MemoryRangeValid" or
+    "Test-ServiceDaclPermission" or "Update-ExeFunctions" or
+    "Update-MemoryAddresses" or "Update-MemoryProtectionFlags" or
+    "Write-BytesToMemory" or "Write-HijackDll" or
+    "Write-PortscanOut" or "Write-ServiceBinary" or
+    "Write-UserAddMSI" or "Invoke-Privesc" or
+    "func_get_proc_address" or "Invoke-BloodHound" or
+    "Invoke-HostEnum" or "Get-BrowserInformation" or
+    "Get-DomainAccountPolicy" or "Get-DomainAdmins" or
+    "Get-AVProcesses" or "Get-AVInfo" or
+    "Get-RecycleBin" or "Invoke-BruteForce" or
+    "Get-PassHints" or "Invoke-SessionGopher" or
+    "Get-LSASecret" or "Get-PassHashes" or
+    "Invoke-WdigestDowngrade" or "Get-ChromeDump" or
+    "Invoke-DomainPasswordSpray" or "Get-FoxDump" or
+    "New-HoneyHash" or "Invoke-DCSync" or
+    "Invoke-PowerDump" or "Invoke-SSIDExfil" or
+    "Invoke-PowerShellTCP" or "Add-Exfiltration" or
+    "Do-Exfiltration" or "Invoke-DropboxUpload" or
+    "Invoke-ExfilDataToGitHub" or "Invoke-EgressCheck" or
+    "Invoke-PostExfil" or "Create-MultipleSessions" or
+    "Invoke-NetworkRelay" or "New-GPOImmediateTask" or
+    "Invoke-WMIDebugger" or "Invoke-SQLOSCMD" or
+    "Invoke-SMBExec" or "Invoke-PSRemoting" or
+    "Invoke-ExecuteMSBuild" or "Invoke-DCOM" or
+    "Invoke-InveighRelay" or "Invoke-PsExec" or
+    "Invoke-SSHCommand" or "Find-ActiveUsersWMI" or
+    "Get-SystemDrivesWMI" or "Get-ActiveNICSWMI" or
+    "Remove-Persistence" or "DNS_TXT_Pwnage" or
+    "Execute-OnTime" or "HTTP-Backdoor" or
+    "Add-ConstrainedDelegationBackdoor" or "Add-RegBackdoor" or
+    "Add-ScrnSaveBackdoor" or "Gupt-Backdoor" or
+    "Invoke-ADSBackdoor" or "Add-Persistence" or
+    "Invoke-ResolverBackdoor" or "Invoke-EventLogBackdoor" or
+    "Invoke-DeadUserBackdoor" or "Invoke-DisableMachineAcctChange" or
+    "Invoke-AccessBinary" or "Add-NetUser" or
+    "Invoke-Schtasks" or "Invoke-JSRatRegsvr" or
+    "Invoke-JSRatRundll" or "Invoke-PoshRatHttps" or
+    "Invoke-PsGcatAgent" or "Remove-PoshRat" or
+    "Install-SSP" or "Invoke-BackdoorLNK" or
+    "PowerBreach" or "InstallEXE-Persistence" or
+    "RemoveEXE-Persistence" or "Install-ServiceLevel-Persistence" or
+    "Remove-ServiceLevel-Persistence" or "Invoke-Prompt" or
+    "Invoke-PacketCapture" or "Start-WebcamRecorder" or
+    "Get-USBKeyStrokes" or "Invoke-KeeThief" or
+    "Get-Keystrokes" or "Invoke-NetRipper" or
+    "Get-EmailItems" or "Invoke-MailSearch" or
+    "Invoke-SearchGAL" or "Get-WebCredentials" or
+    "Start-CaptureServer" or "Invoke-PowerShellIcmp" or
+    "Invoke-PowerShellTcpOneLine" or "Invoke-PowerShellTcpOneLineBind" or
+    "Invoke-PowerShellUdp" or "Invoke-PowerShellUdpOneLine" or
+    "Run-EXEonRemote" or "Download-Execute-PS" or
+    "Out-RundllCommand" or "Set-RemoteWMI" or
+    "Set-DCShadowPermissions" or "Invoke-PowerShellWMI" or
+    "Invoke-Vnc" or "Invoke-LockWorkStation" or
+    "Invoke-EternalBlue" or "Invoke-ShellcodeMSIL" or
+    "Invoke-MetasploitPayload" or "Invoke-DowngradeAccount" or
+    "Invoke-RunAs" or "ExetoText" or
+    "Disable-SecuritySettings" or "Set-MacAttribute" or
+    "Invoke-MS16032" or "Invoke-BypassUACTokenManipulation" or
+    "Invoke-SDCLTBypass" or "Invoke-FodHelperBypass" or
+    "Invoke-EventVwrBypass" or "Invoke-EnvBypass" or
+    "Get-ServiceUnquoted" or "Get-ServiceFilePermission" or
+    "Get-ServicePermission" or
+    "Enable-DuplicateToken" or "Invoke-PsUaCme" or
+    "Invoke-Tater" or "Invoke-WScriptBypassUAC" or
+    "Invoke-AllChecks" or "Find-TrustedDocuments" or
+    "Invoke-Interceptor" or "Invoke-PoshRatHttp" or
+    "Invoke-ExecCommandWMI" or "Invoke-KillProcessWMI" or
+    "Invoke-CreateShareandExecute" or "Invoke-RemoteScriptWithOutput" or
+    "Invoke-SchedJobManipulation" or "Invoke-ServiceManipulation" or
+    "Invoke-PowerOptionsWMI" or "Invoke-DirectoryListing" or
+    "Invoke-FileTransferOverWMI" or "Invoke-WMImplant" or
+    "Invoke-WMIObfuscatedPSCommand" or "Invoke-WMIDuplicateClass" or
+    "Invoke-WMIUpload" or "Invoke-WMIRemoteExtract" or "Invoke-winPEAS"
+  ) and
+  not powershell.file.script_block_text : (
+    "sentinelbreakpoints" and "Set-PSBreakpoint"
+  ) and
+  not user.id : ("S-1-5-18" or "S-1-5-19")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-powershell-pass-the-hash-relay-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-powershell-pass-the-hash-relay-script.asciidoc
new file mode 100644
index 0000000000..eb0acf3f6f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-powershell-pass-the-hash-relay-script.asciidoc
@@ -0,0 +1,123 @@
+[[potential-powershell-pass-the-hash-relay-script]]
+=== Potential PowerShell Pass-the-Hash/Relay Script
+
+Detects PowerShell scripts that can execute pass-the-hash (PtH) attacks, intercept and relay NTLM challenges, and carry out other man-in-the-middle (MitM) attacks.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/Kevin-Robertson/Invoke-TheHash/blob/master/Invoke-WMIExec.ps1
+* https://github.com/Kevin-Robertson/Invoke-TheHash/blob/master/Invoke-SMBExec.ps1
+* https://github.com/dafthack/Check-LocalAdminHash/blob/master/Check-LocalAdminHash.ps1
+* https://github.com/nettitude/PoshC2/blob/master/resources/modules/Invoke-Tater.ps1
+* https://github.com/Kevin-Robertson/Inveigh/blob/master/Inveigh.ps1
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    ("NTLMSSPNegotiate" and ("NegotiateSMB" or "NegotiateSMB2")) or
+    "4E544C4D53535000" or
+    "0x4e,0x54,0x4c,0x4d,0x53,0x53,0x50" or
+    "0x4e,0x54,0x20,0x4c,0x4d" or
+    "0x53,0x4d,0x42,0x20,0x32" or
+    "0x81,0xbb,0x7a,0x36,0x44,0x98,0xf1,0x35,0xad,0x32,0x98,0xf0,0x38"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Adversary-in-the-Middle
+** ID: T1557
+** Reference URL: https://attack.mitre.org/techniques/T1557/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Use Alternate Authentication Material
+** ID: T1550
+** Reference URL: https://attack.mitre.org/techniques/T1550/
+* Sub-technique:
+** Name: Pass the Hash
+** ID: T1550.002
+** Reference URL: https://attack.mitre.org/techniques/T1550/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privacy-control-bypass-via-localhost-secure-copy.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privacy-control-bypass-via-localhost-secure-copy.asciidoc
index 0f07d511b3..25ef0afb6a 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-privacy-control-bypass-via-localhost-secure-copy.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privacy-control-bypass-via-localhost-secure-copy.asciidoc
@@ -5,65 +5,91 @@ Identifies use of the Secure Copy Protocol (SCP) to copy files locally by abusin
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.trendmicro.com/en_us/research/20/h/xcsset-mac-malware--infects-xcode-projects--uses-0-days.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Privilege Escalation
-* Defense Evasion
 
-*Version*: 100 (<<potential-privacy-control-bypass-via-localhost-secure-copy-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.12.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
 
-==== Investigation guide
 
+This rule requires data coming in from Elastic Defend.
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name:"scp" and process.args:"StrictHostKeyChecking=no" and
-process.command_line:("scp *localhost:/*", "scp *127.0.0.1:/*") and
-not process.args:"vagrant@*127.0.0.1*"
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and
+ process.name:"scp" and
+ process.args:"StrictHostKeyChecking=no" and
+ process.command_line:("scp *localhost:/*", "scp *127.0.0.1:/*") and
+ not process.args:"vagrant@*127.0.0.1*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,8 +101,6 @@ not process.args:"vagrant@*127.0.0.1*"
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-
 * Tactic:
 ** Name: Privilege Escalation
 ** ID: TA0004
@@ -85,27 +109,3 @@ not process.args:"vagrant@*127.0.0.1*"
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[potential-privacy-control-bypass-via-localhost-secure-copy-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name:"scp" and process.args:"StrictHostKeyChecking=no" and
-process.command_line:("scp *localhost:/*", "scp *127.0.0.1:/*") and
-not process.args:"vagrant@*127.0.0.1*"
-----------------------------------
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privacy-control-bypass-via-tccdb-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privacy-control-bypass-via-tccdb-modification.asciidoc
index 610b9ba6e0..7b31ce69dd 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-privacy-control-bypass-via-tccdb-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privacy-control-bypass-via-tccdb-modification.asciidoc
@@ -5,66 +5,90 @@ Identifies the use of sqlite3 to directly modify the Transparency, Consent, and
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://applehelpwriter.com/2016/08/29/discovering-how-dropbox-hacks-your-mac/
 * https://github.com/bp88/JSS-Scripts/blob/master/TCC.db%20Modifier.sh
 * https://medium.com/@mattshockl/cve-2020-9934-bypassing-the-os-x-transparency-consent-and-control-tcc-framework-for-4e14806f1de8
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Defense Evasion
 
-*Version*: 100 (<<potential-privacy-control-bypass-via-tccdb-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This rule requires data coming in from Elastic Defend.
 
-----------------------------------
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "sqlite*" and process.args : "/*/Application
-Support/com.apple.TCC/TCC.db" and not process.parent.executable :
-"/Library/Bitdefender/AVP/product/bin/*"
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and process.name : "sqlite*" and
+ process.args : "/*/Application Support/com.apple.TCC/TCC.db" and
+ not process.parent.executable : "/Library/Bitdefender/AVP/product/bin/*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,26 +100,7 @@ Support/com.apple.TCC/TCC.db" and not process.parent.executable :
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[potential-privacy-control-bypass-via-tccdb-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "sqlite*" and process.args : "/*/Application
-Support/com.apple.TCC/TCC.db"
-----------------------------------
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-through-writable-docker-socket.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-through-writable-docker-socket.asciidoc
new file mode 100644
index 0000000000..41be2a850e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-through-writable-docker-socket.asciidoc
@@ -0,0 +1,104 @@
+[[potential-privilege-escalation-through-writable-docker-socket]]
+=== Potential Privilege Escalation through Writable Docker Socket
+
+This rule monitors for the usage of Docker runtime sockets to escalate privileges on Linux systems. Docker sockets by default are only be writable by the root user and docker group. Attackers that have permissions to write to these sockets may be able to create and run a container that allows them to escalate privileges and gain further access onto the host file system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://book.hacktricks.xyz/linux-hardening/privilege-escalation/docker-security/docker-breakout-privilege-escalation#automatic-enumeration-and-escape
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Domain: Container
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+(
+  (process.name == "docker" and process.args : "run" and process.args : "-it"  and 
+   process.args : ("unix://*/docker.sock", "unix://*/dockershim.sock")) or 
+  (process.name == "socat" and process.args : ("UNIX-CONNECT:*/docker.sock", "UNIX-CONNECT:*/dockershim.sock"))
+) and not user.Ext.real.id : "0" and not group.Ext.real.id : "0"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Escape to Host
+** ID: T1611
+** Reference URL: https://attack.mitre.org/techniques/T1611/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-container-misconfiguration.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-container-misconfiguration.asciidoc
new file mode 100644
index 0000000000..a5e197f614
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-container-misconfiguration.asciidoc
@@ -0,0 +1,115 @@
+[[potential-privilege-escalation-via-container-misconfiguration]]
+=== Potential Privilege Escalation via Container Misconfiguration
+
+This rule monitors for the execution of processes that interact with Linux containers through an interactive shell without root permissions. Utilities such as runc and ctr are universal command-line utilities leveraged to interact with containers via root permissions. On systems where the access to these utilities are misconfigured, attackers might be able to create and run a container that mounts the root folder or spawn a privileged container vulnerable to a container escape attack, which might allow them to escalate privileges and gain further access onto the host file system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://book.hacktricks.xyz/linux-hardening/privilege-escalation/runc-privilege-escalation
+* https://book.hacktricks.xyz/linux-hardening/privilege-escalation/containerd-ctr-privilege-escalation
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Domain: Container
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+Session View uses process data collected by the Elastic Defend integration, but this data is not always collected by default. Session View is available on enterprise subscription for versions 8.3 and above.
+
+*To confirm that Session View data is enabled:*
+
+- Go to “Manage → Policies”, and edit one or more of your Elastic Defend integration policies.
+- Select the” Policy settings” tab, then scroll down to the “Linux event collection” section near the bottom.
+- Check the box for “Process events”, and turn on the “Include session data” toggle.
+- If you want to include file and network alerts in Session View, check the boxes for “Network and File events”.
+- If you want to enable terminal output capture, turn on the “Capture terminal output” toggle.
+For more information about the additional fields collected when this setting is enabled and the usage of Session View for Analysis refer to the https://www.elastic.co/guide/en/security/current/session-view.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and (
+  (process.name == "runc" and process.args == "run") or
+  (process.name == "ctr" and process.args == "run" and process.args in ("--privileged", "--mount"))
+) and not user.Ext.real.id == "0" and not group.Ext.real.id == "0" and 
+process.interactive == true and process.parent.interactive == true
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Escape to Host
+** ID: T1611
+** Reference URL: https://attack.mitre.org/techniques/T1611/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-cve-2022-38028.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-cve-2022-38028.asciidoc
new file mode 100644
index 0000000000..30e243ae91
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-cve-2022-38028.asciidoc
@@ -0,0 +1,76 @@
+[[potential-privilege-escalation-via-cve-2022-38028]]
+=== Potential privilege escalation via CVE-2022-38028
+
+Identifies a privilege escalation attempt via exploiting CVE-2022-38028 to hijack the print spooler service execution.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.microsoft.com/en-us/security/blog/2024/04/22/analyzing-forest-blizzards-custom-post-compromise-tool-for-exploiting-cve-2022-38028-to-obtain-credentials/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and
+           file.path : ("?:\\*\\Windows\\system32\\DriVerStoRe\\FiLeRePoSiToRy\\*\\MPDW-constraints.js",
+                        "?:\\*\\Windows\\WinSxS\\amd64_microsoft-windows-printing-printtopdf_*\\MPDW-constraints.js")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-cve-2023-4911.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-cve-2023-4911.asciidoc
new file mode 100644
index 0000000000..fde07e1925
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-cve-2023-4911.asciidoc
@@ -0,0 +1,114 @@
+[[potential-privilege-escalation-via-cve-2023-4911]]
+=== Potential Privilege Escalation via CVE-2023-4911
+
+This rule detects potential privilege escalation attempts through Looney Tunables (CVE-2023-4911). Looney Tunables is a buffer overflow vulnerability in GNU C Library's dynamic loader's processing of the GLIBC_TUNABLES environment variable.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.qualys.com/vulnerabilities-threat-research/2023/10/03/cve-2023-4911-looney-tunables-local-privilege-escalation-in-the-glibcs-ld-so
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+Elastic Defend integration does not collect environment variable logging by default.
+In order to capture this behavior, this rule requires a specific configuration option set within the advanced settings of the Elastic Defend integration.
+ #### To set up environment variable capture for an Elastic Agent policy:
+- Go to “Security → Manage → Policies”.
+- Select an “Elastic Agent policy”.
+- Click “Show advanced settings”.
+- Scroll down or search for “linux.advanced.capture_env_vars”.
+- Enter the names of environment variables you want to capture, separated by commas.
+- For this rule the linux.advanced.capture_env_vars variable should be set to "GLIBC_TUNABLES".
+- Click “Save”.
+After saving the integration change, the Elastic Agents running this policy will be updated and the rule will function properly.
+For more information on capturing environment variables refer to the https://www.elastic.co/guide/en/security/current/environment-variable-capture.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.parent.entity_id, process.executable with maxspan=5s
+ [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+  process.env_vars : "*GLIBC_TUNABLES=glibc.*=glibc.*=*"] with runs=5
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-enlightenment.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-enlightenment.asciidoc
new file mode 100644
index 0000000000..d83371baaa
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-enlightenment.asciidoc
@@ -0,0 +1,104 @@
+[[potential-privilege-escalation-via-enlightenment]]
+=== Potential Privilege Escalation via Enlightenment
+
+Identifies an attempt to exploit a local privilege escalation CVE-2022-37706 via a flaw in Linux window manager package Enlightenment. enlightenment_sys in Enlightenment before 0.25.4 allows local users to gain privileges because it is setuid root, and the system library function mishandles pathnames that begin with a /dev/.. substring.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://ubuntu.com/security/CVE-2022-37706
+* https://www.exploit-db.com/exploits/51180
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.parent.entity_id with maxspan=5s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+    process.name == "enlightenment_sys" and process.args in ("/bin/mount/", "-o","noexec","nosuid","nodev","uid=*") ]
+  [process where host.os.type == "linux" and event.action == "uid_change" and event.type == "change" and user.id == "0"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-installerfiletakeover.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-installerfiletakeover.asciidoc
index 029666ff88..287ca9c663 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-installerfiletakeover.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-installerfiletakeover.asciidoc
@@ -5,97 +5,99 @@ Identifies a potential exploitation of InstallerTakeOver (CVE-2021-41379) defaul
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/klinix5/InstallerFileTakeOver
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Investigation Guide
-
-*Version*: 102 (<<potential-privilege-escalation-via-installerfiletakeover-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Resources: Investigation Guide
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Potential Privilege Escalation via InstallerFileTakeOver
+*Triage and analysis*
+
 
-InstallerFileTakeOver is a weaponized escalation of privilege proof of concept (EoP PoC) to the CVE-2021-41379 vulnerability. Upon successful exploitation, an
-unprivileged user will escalate privileges to SYSTEM/NT AUTHORITY.
 
-This rule detects the default execution of the PoC, which overwrites the `elevation_service.exe` DACL and copies itself
-to the location to escalate privileges. An attacker is able to still take over any file that is not in use (locked),
-which is outside the scope of this rule.
+*Investigating Potential Privilege Escalation via InstallerFileTakeOver*
+
+
+InstallerFileTakeOver is a weaponized escalation of privilege proof of concept (EoP PoC) to the CVE-2021-41379 vulnerability. Upon successful exploitation, an unprivileged user will escalate privileges to SYSTEM/NT AUTHORITY.
+
+This rule detects the default execution of the PoC, which overwrites the `elevation_service.exe` DACL and copies itself to the location to escalate privileges. An attacker is able to still take over any file that is not in use (locked), which is outside the scope of this rule.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Look for additional processes spawned by the process, command lines, and network communications.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - Verify whether a digital signature exists in the executable, and if it is valid.
 
-### Related rules
+
+*Related rules*
+
 
 - Suspicious DLL Loaded for Persistence or Privilege Escalation - bfeaf89b-a2a7-48a3-817f-e41829dc61ee
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -103,36 +105,52 @@ for prevalence, whether they are located in expected locations, and if they are
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-/* This rule is compatible with both Sysmon and Elastic Endpoint */
-process where event.type == "start" and
-(?process.Ext.token.integrity_level_name : "System" or
-?winlog.event_data.IntegrityLevel : "System") and (
-(process.name : "elevation_service.exe" and not
-process.pe.original_file_name == "elevation_service.exe") or
-(process.parent.name : "elevation_service.exe" and process.name
-: ("rundll32.exe", "cmd.exe", "powershell.exe")) )
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+    process.Ext.token.integrity_level_name : "System" and
+    (
+      (process.name : "elevation_service.exe" and
+       not process.pe.original_file_name == "elevation_service.exe") or
+      
+      (process.name : "elevation_service.exe" and
+       not process.code_signature.trusted == true) or
+
+      (process.parent.name : "elevation_service.exe" and
+       process.name : ("rundll32.exe", "cmd.exe", "powershell.exe"))
+    ) and
+    not
+    (
+      process.name : "elevation_service.exe" and process.code_signature.trusted == true and
+      process.pe.original_file_name == null
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -144,59 +162,3 @@ process.pe.original_file_name == "elevation_service.exe") or
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-[[potential-privilege-escalation-via-installerfiletakeover-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* This rule is compatible with both Sysmon and Elastic Endpoint */
-process where event.type == "start" and
-(?process.Ext.token.integrity_level_name : "System" or
-?winlog.event_data.IntegrityLevel : "System") and (
-(process.name : "elevation_service.exe" and not
-process.pe.original_file_name == "elevation_service.exe") or
-(process.parent.name : "elevation_service.exe" and
-process.name : ("rundll32.exe", "cmd.exe", "powershell.exe")) )
-----------------------------------
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* This rule is compatible with both Sysmon and Elastic Endpoint */
-process where event.type == "start" and
-(process.Ext.token.integrity_level_name : "System" or
-winlog.event_data.IntegrityLevel : "System") and (
-(process.name : "elevation_service.exe" and not
-process.pe.original_file_name == "elevation_service.exe") or
-(process.parent.name : "elevation_service.exe" and
-process.name : ("rundll32.exe", "cmd.exe", "powershell.exe")) )
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* This rule is compatible with both Sysmon and Elastic Endpoint */
-process where event.type == "start" and user.id : "S-1-5-18" and
-( (process.name : "elevation_service.exe" and not
-process.pe.original_file_name == "elevation_service.exe") or
-(process.parent.name : "elevation_service.exe" and
-process.name : ("rundll32.exe", "cmd.exe", "powershell.exe")) )
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-linux-dac-permissions.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-linux-dac-permissions.asciidoc
new file mode 100644
index 0000000000..79c40443ad
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-linux-dac-permissions.asciidoc
@@ -0,0 +1,99 @@
+[[potential-privilege-escalation-via-linux-dac-permissions]]
+=== Potential Privilege Escalation via Linux DAC permissions
+
+Identifies potential privilege escalation exploitation of DAC (Discretionary access control) file permissions. The rule identifies exploitation of DAC checks on sensitive file paths via suspicious processes whose capabilities include CAP_DAC_OVERRIDE (where a process can bypass all read write and execution checks) or CAP_DAC_READ_SEARCH (where a process can read any file or perform any executable permission on the directories).
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:linux and event.type:start and event.action:exec and
+(process.thread.capabilities.permitted:CAP_DAC_* or process.thread.capabilities.effective: CAP_DAC_*) and
+process.command_line:(*sudoers* or *passwd* or *shadow* or */root/*) and not user.id:"0"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-overlayfs.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-overlayfs.asciidoc
new file mode 100644
index 0000000000..6c54e79f06
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-overlayfs.asciidoc
@@ -0,0 +1,104 @@
+[[potential-privilege-escalation-via-overlayfs]]
+=== Potential Privilege Escalation via OverlayFS
+
+Identifies an attempt to exploit a local privilege escalation (CVE-2023-2640 and CVE-2023-32629) via a flaw in Ubuntu's modifications to OverlayFS. These flaws allow the creation of specialized executables, which, upon execution, grant the ability to escalate privileges to root on the affected machine.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.wiz.io/blog/ubuntu-overlayfs-vulnerability
+* https://twitter.com/liadeliyahu/status/1684841527959273472
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by process.parent.entity_id, host.id with maxspan=5s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+    process.name == "unshare" and process.args : ("-r", "-rm", "m") and process.args : "*cap_setuid*"  and user.id != "0"]
+  [process where host.os.type == "linux" and event.action == "uid_change" and event.type == "change" and 
+    user.id == "0"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-pkexec.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-pkexec.asciidoc
index 65b4d15560..eeb1303998 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-pkexec.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-pkexec.asciidoc
@@ -5,52 +5,90 @@ Identifies an attempt to exploit a local privilege escalation in polkit pkexec (
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://seclists.org/oss-sec/2022/q1/80
 * https://haxx.in/files/blasty-vs-pkexec.c
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Privilege Escalation
 
-*Version*: 100 (<<potential-privilege-escalation-via-pkexec-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.1.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where file.path : "/*GCONV_PATH*"
+[source, js]
 ----------------------------------
+file where host.os.type == "linux" and file.path : "/*GCONV_PATH*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -62,8 +100,6 @@ file where file.path : "/*GCONV_PATH*"
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -72,16 +108,7 @@ file where file.path : "/*GCONV_PATH*"
 ** Name: Hijack Execution Flow
 ** ID: T1574
 ** Reference URL: https://attack.mitre.org/techniques/T1574/
-
-[[potential-privilege-escalation-via-pkexec-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Path Interception by PATH Environment Variable
+** ID: T1574.007
+** Reference URL: https://attack.mitre.org/techniques/T1574/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-python-cap-setuid.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-python-cap-setuid.asciidoc
new file mode 100644
index 0000000000..ec7e4534d6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-python-cap-setuid.asciidoc
@@ -0,0 +1,109 @@
+[[potential-privilege-escalation-via-python-cap-setuid]]
+=== Potential Privilege Escalation via Python cap_setuid
+
+This detection rule monitors for the execution of a system command with setuid or setgid capabilities via Python, followed by a uid or gid change to the root user. This sequence of events may indicate successful privilege escalation. Setuid (Set User ID) and setgid (Set Group ID) are Unix-like OS features that enable processes to run with elevated privileges, based on the file owner or group. Threat actors can exploit these attributes to escalate privileges to the privileges that are set on the binary that is being executed.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.entity_id with maxspan=1s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+   process.args : "import os;os.set?id(0);os.system(*)" and process.args : "*python*" and user.id != "0"]
+  [process where host.os.type == "linux" and event.action in ("uid_change", "gid_change") and event.type == "change" and 
+   (user.id == "0" or group.id == "0")]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Setuid and Setgid
+** ID: T1548.001
+** Reference URL: https://attack.mitre.org/techniques/T1548/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-recently-compiled-executable.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-recently-compiled-executable.asciidoc
new file mode 100644
index 0000000000..98e6d93a10
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-recently-compiled-executable.asciidoc
@@ -0,0 +1,105 @@
+[[potential-privilege-escalation-via-recently-compiled-executable]]
+=== Potential Privilege Escalation via Recently Compiled Executable
+
+This rule monitors a sequence involving a program compilation event followed by its execution and a subsequent alteration of UID permissions to root privileges. This behavior can potentially indicate the execution of a kernel or software privilege escalation exploit.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=1m
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+   process.name in ("gcc", "g++", "cc") and user.id != "0"] by process.args
+  [file where host.os.type == "linux" and event.action == "creation" and event.type == "creation" and 
+   process.name == "ld" and user.id != "0"] by file.name
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+   user.id != "0"] by process.name
+  [process where host.os.type == "linux" and event.action in ("uid_change", "guid_change") and event.type == "change" and 
+   user.id == "0"] by process.name
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-sudoers-file-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-sudoers-file-modification.asciidoc
index d179933ad5..216e4cd6ec 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-sudoers-file-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-sudoers-file-modification.asciidoc
@@ -5,7 +5,7 @@ A sudoers file specifies the commands users or groups can run and from which ter
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,41 +14,40 @@ A sudoers file specifies the commands users or groups can run and from which ter
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* macOS
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<potential-privilege-escalation-via-sudoers-file-modification-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:start and process.args:(echo and
-*NOPASSWD*ALL*)
+[source, js]
 ----------------------------------
+event.category:process and event.type:start and process.args:(echo and *NOPASSWD*ALL*)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -60,13 +59,7 @@ event.category:process and event.type:start and process.args:(echo and
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[potential-privilege-escalation-via-sudoers-file-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Sudo and Sudo Caching
+** ID: T1548.003
+** Reference URL: https://attack.mitre.org/techniques/T1548/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-uid-int-max-bug-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-uid-int-max-bug-detected.asciidoc
new file mode 100644
index 0000000000..b23603f4b0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privilege-escalation-via-uid-int-max-bug-detected.asciidoc
@@ -0,0 +1,103 @@
+[[potential-privilege-escalation-via-uid-int-max-bug-detected]]
+=== Potential Privilege Escalation via UID INT_MAX Bug Detected
+
+This rule monitors for the execution of the systemd-run command by a user with a UID that is larger than the maximum allowed UID size (INT_MAX). Some older Linux versions were affected by a bug which allows user accounts with a UID greater than INT_MAX to escalate privileges by spawning a shell through systemd-run.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://twitter.com/paragonsec/status/1071152249529884674
+* https://github.com/mirchr/security-research/blob/master/vulnerabilities/CVE-2018-19788.sh
+* https://gitlab.freedesktop.org/polkit/polkit/-/issues/74
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and 
+process.name == "systemd-run" and process.args == "-t" and process.args_count >= 3 and user.id >= "1000000000"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-privileged-escalation-via-samaccountname-spoofing.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-privileged-escalation-via-samaccountname-spoofing.asciidoc
index b3c92123c1..28d864ce8c 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-privileged-escalation-via-samaccountname-spoofing.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-privileged-escalation-via-samaccountname-spoofing.asciidoc
@@ -5,22 +5,23 @@ Identifies a suspicious computer account name rename event, which may indicate a
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://support.microsoft.com/en-us/topic/kb5008102-active-directory-security-accounts-manager-hardening-changes-cve-2021-42278-5975b463-4c95-45e1-831a-d120004e258e
 * https://cloudbrothers.info/en/exploit-kerberos-samaccountname-spoofing/
@@ -28,46 +29,50 @@ Identifies a suspicious computer account name rename event, which may indicate a
 * https://twitter.com/exploitph/status/1469157138928914432
 * https://exploit.ph/cve-2021-42287-cve-2021-42278-weaponisation.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Privilege Escalation
-
-*Version*: 100 (<<potential-privileged-escalation-via-samaccountname-spoofing-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Use Case: Active Directory Monitoring
+* Data Source: Active Directory
+* Use Case: Vulnerability
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-iam where event.action == "renamed-user-account" and /* machine
-account name renamed to user like account name */
-winlog.event_data.OldTargetUserName : "*$" and not
-winlog.event_data.NewTargetUserName : "*$"
+[source, js]
 ----------------------------------
+iam where event.action == "renamed-user-account" and
+  /* machine account name renamed to user like account name */
+  winlog.event_data.OldTargetUserName : "*$" and not winlog.event_data.NewTargetUserName : "*$"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,11 +81,17 @@ winlog.event_data.NewTargetUserName : "*$"
 ** ID: TA0004
 ** Reference URL: https://attack.mitre.org/tactics/TA0004/
 * Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
+* Technique:
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
+* Sub-technique:
+** Name: Domain Accounts
+** ID: T1078.002
+** Reference URL: https://attack.mitre.org/techniques/T1078/002/
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -89,16 +100,3 @@ winlog.event_data.NewTargetUserName : "*$"
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[potential-privileged-escalation-via-samaccountname-spoofing-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-process-injection-from-malicious-document.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-process-injection-from-malicious-document.asciidoc
new file mode 100644
index 0000000000..7fdce260b0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-process-injection-from-malicious-document.asciidoc
@@ -0,0 +1,93 @@
+[[potential-process-injection-from-malicious-document]]
+=== Potential Process Injection from Malicious Document
+
+Identifies child processes of frequently targeted Microsoft Office applications (Word, PowerPoint, Excel) with unusual process arguments and path. This behavior is often observed during exploitation of Office applications or from documents with malicious macros.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Privilege Escalation
+* Tactic: Initial Access
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.action == "start" and
+  process.parent.name : ("excel.exe", "powerpnt.exe", "winword.exe") and
+  process.args_count == 1 and
+  process.executable : (
+    "?:\\Windows\\SysWOW64\\*.exe", "?:\\Windows\\system32\\*.exe"
+  ) and
+  not (process.executable : "?:\\Windows\\System32\\spool\\drivers\\x64\\*" and
+       process.code_signature.trusted == true and not process.code_signature.subject_name : "Microsoft *") and
+  not process.executable : (
+    "?:\\Windows\\Sys*\\Taskmgr.exe",
+    "?:\\Windows\\Sys*\\ctfmon.exe",
+    "?:\\Windows\\System32\\notepad.exe")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-process-injection-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-process-injection-via-powershell.asciidoc
index d5767d1671..e8824f61ba 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-process-injection-via-powershell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-process-injection-via-powershell.asciidoc
@@ -5,172 +5,173 @@ Detects the use of Windows API functions that are commonly abused by malware and
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
-*Severity*: high
+*Severity*: medium
 
-*Risk score*: 73
+*Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/EmpireProject/Empire/blob/master/data/module_source/management/Invoke-PSInject.ps1
 * https://github.com/EmpireProject/Empire/blob/master/data/module_source/management/Invoke-ReflectivePEInjection.ps1
 * https://github.com/BC-SECURITY/Empire/blob/master/empire/server/data/module_source/credentials/Invoke-Mimikatz.ps1
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
+
+*Version*: 110
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
 
-*Version*: 102 (<<potential-process-injection-via-powershell-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.0.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Legitimate PowerShell scripts that make use of these functions.
 
-==== Investigation guide
 
+*Investigating Potential Process Injection via PowerShell*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Potential Process Injection via PowerShell
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+PowerShell also has solid capabilities to make the interaction with the Win32 API in an uncomplicated and reliable way, like the execution of inline C# code, PSReflect, Get-ProcAddress, etc.
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This
-makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+Red Team tooling and malware developers take advantage of these capabilities to develop stagers and loaders that inject payloads directly into the memory without touching the disk to circumvent file-based security protections.
 
-PowerShell also has solid capabilities to make the interaction with the Win32 API in an uncomplicated and reliable way,
-like the execution of inline C# code, PSReflect, Get-ProcAddress, etc.
 
-Red Team tooling and malware developers take advantage of these capabilities to develop stagers and loaders that inject
-payloads directly into the memory without touching the disk to circumvent file-based security protections.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Examine file or network events from the involved PowerShell process for suspicious behavior.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
 - Check if the imported function was executed and which process it targeted.
 - Check if the injected code can be retrieved (hardcoded in the script or on command line logs).
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Related rules
+
+*Related rules*
+
 
 - PowerShell PSReflect Script - 56f2e9b5-4803-4e44-a0a4-a52dc79d57fe
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
-==== Rule query
+==== Setup
 
 
-[source,js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-(VirtualAlloc or VirtualAllocEx or VirtualProtect or LdrLoadDll or
-LoadLibrary or LoadLibraryA or LoadLibraryEx or GetProcAddress
-or OpenProcess or OpenProcessToken or AdjustTokenPrivileges) and
-(WriteProcessMemory or CreateRemoteThread or NtCreateThreadEx or
-CreateThread or QueueUserAPC or SuspendThread or ResumeThread or
-GetDelegateForFunctionPointer) )
-----------------------------------
 
-==== Threat mapping
+*Setup*
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Process Injection
-** ID: T1055
-** Reference URL: https://attack.mitre.org/techniques/T1055/
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
 
-[[potential-process-injection-via-powershell-history]]
-==== Rule version history
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
 
-Version 102 (8.6.0 release)::
-* Formatting only
+Steps to implement the logging policy via registry:
 
-Version 101 (8.5.0 release)::
-* Formatting only
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
 
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-(VirtualAlloc or VirtualAllocEx or VirtualProtect or LdrLoadDll or
-LoadLibrary or LoadLibraryA or LoadLibraryEx or GetProcAddress
-or OpenProcess or OpenProcessToken or AdjustTokenPrivileges) and
-(WriteProcessMemory or CreateRemoteThread or NtCreateThreadEx or
-CreateThread or QueueUserAPC or SuspendThread or ResumeThread or
-GetDelegateForFunctionPointer) )
-----------------------------------
 
-Version 5 (8.3.0 release)::
-* Formatting only
+==== Rule query
+
 
-Version 4 (8.2.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.category:process and powershell.file.script_block_text : (
-(VirtualAlloc or VirtualAllocEx or VirtualProtect or LdrLoadDll or
-LoadLibrary or LoadLibraryA or LoadLibraryEx or GetProcAddress
-or OpenProcess or OpenProcessToken or AdjustTokenPrivileges) and
-(WriteProcessMemory or CreateRemoteThread or NtCreateThreadEx or
-CreateThread or QueueUserAPC or SuspendThread or ResumeThread)
-)
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+   (VirtualAlloc or VirtualAllocEx or VirtualProtect or LdrLoadDll or LoadLibrary or LoadLibraryA or
+      LoadLibraryEx or GetProcAddress or OpenProcess or OpenProcessToken or AdjustTokenPrivileges) and
+   (WriteProcessMemory or CreateRemoteThread or NtCreateThreadEx or CreateThread or QueueUserAPC or
+      SuspendThread or ResumeThread or GetDelegateForFunctionPointer)
+  ) and not 
+  (user.id:("S-1-5-18" or "S-1-5-19") and
+   file.directory: "C:\\ProgramData\\Microsoft\\Windows Defender Advanced Threat Protection\\SenseCM")
+
 ----------------------------------
 
-Version 3 (8.1.0 release)::
-* Formatting only
+*Framework*: MITRE ATT&CK^TM^
 
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
+* Sub-technique:
+** Name: Dynamic-link Library Injection
+** ID: T1055.001
+** Reference URL: https://attack.mitre.org/techniques/T1055/001/
+* Sub-technique:
+** Name: Portable Executable Injection
+** ID: T1055.002
+** Reference URL: https://attack.mitre.org/techniques/T1055/002/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Technique:
+** Name: Native API
+** ID: T1106
+** Reference URL: https://attack.mitre.org/techniques/T1106/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-chisel-client.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-chisel-client.asciidoc
new file mode 100644
index 0000000000..25528aeeac
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-chisel-client.asciidoc
@@ -0,0 +1,184 @@
+[[potential-protocol-tunneling-via-chisel-client]]
+=== Potential Protocol Tunneling via Chisel Client
+
+This rule monitors for common command line flags leveraged by the Chisel client utility followed by a connection attempt. Chisel is a command-line utility used for creating and managing TCP and UDP tunnels, enabling port forwarding and secure communication between machines. Attackers can abuse the Chisel utility to establish covert communication channels, bypass network restrictions, and carry out malicious activities by creating tunnels that allow unauthorized access to internal systems.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.bitsadmin.com/living-off-the-foreign-land-windows-as-offensive-platform
+* https://book.hacktricks.xyz/generic-methodologies-and-resources/tunneling-and-port-forwarding
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Protocol Tunneling via Chisel Client*
+
+
+Attackers can leverage `chisel` to clandestinely tunnel network communications and evade security measures, potentially gaining unauthorized access to sensitive systems.
+
+This rule looks for a sequence of command line arguments that are consistent with `chisel` client tunneling behavior, followed by a network event by an uncommon process. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Identify any signs of suspicious network activity or anomalies that may indicate protocol tunneling. This could include unexpected traffic patterns or unusual network behavior.
+  - Investigate listening ports and open sockets to look for potential protocol tunneling, reverse shells, or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+  - !{osquery{"label":"Osquery - Retrieve Process Info","query":"SELECT name, cmdline, parent, path, uid FROM processes"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+
+
+*Related rules*
+
+
+- Potential Protocol Tunneling via Chisel Server - ac8805f6-1e08-406c-962e-3937057fa86f
+- Potential Linux Tunneling and/or Port Forwarding - 6ee947e9-de7e-4281-a55d-09289bdf947e
+- Potential Protocol Tunneling via EarthWorm - 9f1c4ca3-44b5-481d-ba42-32dc215a2769
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator or developer who uses port tunneling for benign purposes, consider adding exceptions for specific user accounts or hosts. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors, such as reverse shells, reverse proxies, or droppers, that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.entity_id with maxspan=1s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+   process.args == "client" and process.args : ("R*", "*:*", "*socks*", "*.*") and process.args_count >= 4 and 
+   process.parent.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")]
+  [network where host.os.type == "linux" and event.action == "connection_attempted" and event.type == "start" and 
+   destination.ip != null and destination.ip != "127.0.0.1" and destination.ip != "::1" and 
+   not process.name : (
+     "python*", "php*", "perl", "ruby", "lua*", "openssl", "nc", "netcat", "ncat", "telnet", "awk", "java", "telnet",
+     "ftp", "socat", "curl", "wget", "dpkg", "docker", "dockerd", "yum", "apt", "rpm", "dnf", "ssh", "sshd")]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Protocol Tunneling
+** ID: T1572
+** Reference URL: https://attack.mitre.org/techniques/T1572/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-chisel-server.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-chisel-server.asciidoc
new file mode 100644
index 0000000000..c576eb29fb
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-chisel-server.asciidoc
@@ -0,0 +1,184 @@
+[[potential-protocol-tunneling-via-chisel-server]]
+=== Potential Protocol Tunneling via Chisel Server
+
+This rule monitors for common command line flags leveraged by the Chisel server utility followed by a received connection within a timespan of 1 minute. Chisel is a command-line utility used for creating and managing TCP and UDP tunnels, enabling port forwarding and secure communication between machines. Attackers can abuse the Chisel utility to establish covert communication channels, bypass network restrictions, and carry out malicious activities by creating tunnels that allow unauthorized access to internal systems.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.bitsadmin.com/living-off-the-foreign-land-windows-as-offensive-platform
+* https://book.hacktricks.xyz/generic-methodologies-and-resources/tunneling-and-port-forwarding
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Protocol Tunneling via Chisel Server*
+
+
+Attackers can leverage `chisel` to clandestinely tunnel network communications and evade security measures, potentially gaining unauthorized access to sensitive systems.
+
+This rule looks for a sequence of command line arguments that are consistent with `chisel` server tunneling behavior, followed by a network event by an uncommon process. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Identify any signs of suspicious network activity or anomalies that may indicate protocol tunneling. This could include unexpected traffic patterns or unusual network behavior.
+  - Investigate listening ports and open sockets to look for potential protocol tunneling, reverse shells, or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+  - !{osquery{"label":"Osquery - Retrieve Process Info","query":"SELECT name, cmdline, parent, path, uid FROM processes"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+
+
+*Related rules*
+
+
+- Potential Protocol Tunneling via Chisel Client - 3f12325a-4cc6-410b-8d4c-9fbbeb744cfd
+- Potential Linux Tunneling and/or Port Forwarding - 6ee947e9-de7e-4281-a55d-09289bdf947e
+- Potential Protocol Tunneling via EarthWorm - 9f1c4ca3-44b5-481d-ba42-32dc215a2769
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator or developer who uses port tunneling for benign purposes, consider adding exceptions for specific user accounts or hosts. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors, such as reverse shells, reverse proxies, or droppers, that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.entity_id with maxspan=1m
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+   process.args == "server" and process.args in ("--port", "-p", "--reverse", "--backend", "--socks5") and 
+   process.args_count >= 3 and process.parent.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")]
+  [network where host.os.type == "linux" and event.type == "start" and event.action == "connection_accepted" and 
+   destination.ip != null and destination.ip != "127.0.0.1" and destination.ip != "::1" and 
+   not process.name : (
+     "python*", "php*", "perl", "ruby", "lua*", "openssl", "nc", "netcat", "ncat", "telnet", "awk", "java", "telnet",
+     "ftp", "socat", "curl", "wget", "dpkg", "docker", "dockerd", "yum", "apt", "rpm", "dnf", "ssh", "sshd", "hugo")]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Protocol Tunneling
+** ID: T1572
+** Reference URL: https://attack.mitre.org/techniques/T1572/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-earthworm.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-earthworm.asciidoc
index c6a30d5903..1a43497f8e 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-earthworm.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-protocol-tunneling-via-earthworm.asciidoc
@@ -5,63 +5,187 @@ Identifies the execution of the EarthWorm tunneler. Adversaries may tunnel netwo
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * http://rootkiter.com/EarthWorm/
 * https://decoded.avast.io/luigicamastra/apt-group-targeting-governmental-agencies-in-east-asia/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Command and Control
-
-*Version*: 100 (<<potential-protocol-tunneling-via-earthworm-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.13.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating Potential Protocol Tunneling via EarthWorm*
+
+
+Attackers can leverage `earthworm` to clandestinely tunnel network communications and evade security measures, potentially gaining unauthorized access to sensitive systems.
+
+This rule looks for several command line arguments that are consistent with `earthworm` tunneling behavior. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Identify any signs of suspicious network activity or anomalies that may indicate protocol tunneling. This could include unexpected traffic patterns or unusual network behavior.
+  - Investigate listening ports and open sockets to look for potential protocol tunneling, reverse shells, or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+  - !{osquery{"label":"Osquery - Retrieve Process Info","query":"SELECT name, cmdline, parent, path, uid FROM processes"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+
+
+*Related rules*
+
+
+- Potential Protocol Tunneling via Chisel Client - 3f12325a-4cc6-410b-8d4c-9fbbeb744cfd
+- Potential Protocol Tunneling via Chisel Server - ac8805f6-1e08-406c-962e-3937057fa86f
+- Potential Linux Tunneling and/or Port Forwarding - 6ee947e9-de7e-4281-a55d-09289bdf947e
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator or developer who uses port tunneling for benign purposes, consider adding exceptions for specific user accounts or hosts. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors, such as reverse shells, reverse proxies, or droppers, that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in either from Elastic Defend, or Auditbeat integration.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Custom Ingest Pipeline*
+
+For versions <8.2, you need to add a custom ingest pipeline to populate `event.ingested` with @timestamp for non-elastic-agent indexes, like auditbeats/filebeat/winlogbeat etc. For more details to add a custom ingest pipeline refer to the https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html[guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.args : "-s" and
-process.args : "-d" and process.args : "rssocks"
+[source, js]
 ----------------------------------
+process where host.os.type == "linux" and event.type == "start" and
+ process.args : "-s" and process.args : "-d" and process.args : "rssocks"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,16 +197,3 @@ process.args : "-d" and process.args : "rssocks"
 ** Name: Protocol Tunneling
 ** ID: T1572
 ** Reference URL: https://attack.mitre.org/techniques/T1572/
-
-[[potential-protocol-tunneling-via-earthworm-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-pspy-process-monitoring-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-pspy-process-monitoring-detected.asciidoc
new file mode 100644
index 0000000000..69ae402598
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-pspy-process-monitoring-detected.asciidoc
@@ -0,0 +1,103 @@
+[[potential-pspy-process-monitoring-detected]]
+=== Potential Pspy Process Monitoring Detected
+
+This rule leverages auditd to monitor for processes scanning different processes within the /proc directory using the openat syscall. This is a strong indication for the usage of the pspy utility. Attackers may leverage the pspy process monitoring utility to monitor system processes without requiring root permissions, in order to find potential privilege escalation vectors.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/DominicBreuker/pspy
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Auditd Manager.
+
+
+*Auditd Manager Integration Setup*
+
+The Auditd Manager Integration receives audit events from the Linux Audit Framework which is a part of the Linux kernel.
+Auditd Manager provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system.
+
+
+*The following steps should be executed in order to add the Elastic Agent System integration "auditd_manager" on a Linux System:*
+
+- Go to the Kibana home page and click “Add integrations”.
+- In the query bar, search for “Auditd Manager” and select the integration to see more details about it.
+- Click “Add Auditd Manager”.
+- Configure the integration name and optionally add a description.
+- Review optional and advanced settings accordingly.
+- Add the newly installed “auditd manager” to an existing or a new agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+- Click “Save and Continue”.
+- For more details on the integration refer to the https://docs.elastic.co/integrations/auditd_manager[helper guide].
+
+
+*Rule Specific Setup Note*
+
+Auditd Manager subscribes to the kernel and receives events as they occur without any additional configuration.
+However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+- For this detection rule the following additional audit rules are required to be added to the integration:
+  -- "-w /proc/ -p r -k audit_proc"
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by process.pid, host.id with maxspan=5s
+  [file where host.os.type == "linux" and auditd.data.syscall == "openat" and file.path == "/proc" and
+   auditd.data.a0 : ("ffffffffffffff9c", "ffffff9c") and auditd.data.a2 : ("80000", "88000") ] with runs=10
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Process Discovery
+** ID: T1057
+** Reference URL: https://attack.mitre.org/techniques/T1057/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-ransomware-behavior-high-count-of-readme-files-by-system.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-ransomware-behavior-high-count-of-readme-files-by-system.asciidoc
new file mode 100644
index 0000000000..3bbbb295aa
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-ransomware-behavior-high-count-of-readme-files-by-system.asciidoc
@@ -0,0 +1,125 @@
+[[potential-ransomware-behavior-high-count-of-readme-files-by-system]]
+=== Potential Ransomware Behavior - High count of Readme files by System
+
+This rule identifies a high number (20) of file creation event by the System virtual process from the same host and with same file name containing keywords similar to ransomware note files and all within a short time period.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-1m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://news.sophos.com/en-us/2023/12/21/akira-again-the-ransomware-that-keeps-on-taking/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Possible investigation steps*
+
+
+- Investigate the content of the readme files.
+- Investigate any file names with unusual extensions.
+- Investigate any incoming network connection to port 445 on this host.
+- Investigate any network logon events to this host.
+- Identify the total number and type of modified files by pid 4.
+- If the number of files is too high and source.ip connecting over SMB is unusual isolate the host and block the used credentials.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Local file modification from a Kernel mode driver.
+
+
+*Related rules*
+
+
+- Third-party Backup Files Deleted via Unexpected Process - 11ea6bec-ebde-4d71-a8e9-784948f8e3e9
+- Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
+- Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
+- Volume Shadow Copy Deletion via WMIC - dc9c1f74-dac3-48e3-b47f-eb79db358f57
+- Potential Ransomware Note File Dropped via SMB - 02bab13d-fb14-4d7c-b6fe-4a28874d37c5
+- Suspicious File Renamed via SMB - 78e9b5d5-7c07-40a7-a591-3dbbf464c386
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look for ransomware preparation and execution activities.
+- If any backups were affected:
+  - Perform data recovery locally or restore the backups from replicated copies (cloud, other servers, etc.).
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:file and host.os.type:windows and process.pid:4 and event.action:creation and
+ file.name:(*read*me* or *README* or *lock* or *LOCK* or *how*to* or *HOW*TO* or *@* or *recover* or *RECOVER* or *decrypt* or *DECRYPT* or *restore* or *RESTORE* or *FILES_BACK* or *files_back*)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Data Destruction
+** ID: T1485
+** Reference URL: https://attack.mitre.org/techniques/T1485/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-ransomware-note-file-dropped-via-smb.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-ransomware-note-file-dropped-via-smb.asciidoc
new file mode 100644
index 0000000000..16bb06ed6d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-ransomware-note-file-dropped-via-smb.asciidoc
@@ -0,0 +1,136 @@
+[[potential-ransomware-note-file-dropped-via-smb]]
+=== Potential Ransomware Note File Dropped via SMB
+
+Identifies an incoming SMB connection followed by the creation of a file with a name similar to ransomware note files. This may indicate a remote ransomware attack via the SMB protocol.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Performance*
+
+
+- This rule may cause medium to high performance impact due to logic scoping all icoming SMB network events.
+
+
+*Possible investigation steps*
+
+
+- Investigate the source.ip address connecting to port 445 on this host.
+- Identify the user account that performed the file creation via SMB.
+- If the number of files is too high and source.ip connecting over SMB is unusual isolate the host and block the used credentials.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Remote file creation with similar file naming convention via SMB.
+
+
+
+*Related rules*
+
+
+- Third-party Backup Files Deleted via Unexpected Process - 11ea6bec-ebde-4d71-a8e9-784948f8e3e9
+- Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
+- Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
+- Volume Shadow Copy Deletion via WMIC - dc9c1f74-dac3-48e3-b47f-eb79db358f57
+- Suspicious File Renamed via SMB - 78e9b5d5-7c07-40a7-a591-3dbbf464c386
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look for ransomware preparation and execution activities.
+- If any backups were affected:
+  - Perform data recovery locally or restore the backups from replicated copies (cloud, other servers, etc.).
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=1s
+ [network where host.os.type == "windows" and
+  event.action == "connection_accepted" and destination.port == 445 and source.port >= 49152 and process.pid == 4 and
+  source.ip != "127.0.0.1" and source.ip != "::1"]
+ [file where host.os.type == "windows" and event.action == "creation" and
+  process.pid == 4 and user.id : ("S-1-5-21*", "S-1-12-*") and file.extension : ("hta", "txt", "readme", "htm*") and
+   /* ransom file name keywords */
+    file.name : ("*read*me*", "*lock*", "*@*", "*RECOVER*", "*decrypt*", "*restore*file*", "*FILES_BACK*", "*how*to*")] with runs=3
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Inhibit System Recovery
+** ID: T1490
+** Reference URL: https://attack.mitre.org/techniques/T1490/
+* Technique:
+** Name: Data Destruction
+** ID: T1485
+** Reference URL: https://attack.mitre.org/techniques/T1485/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-remote-code-execution-via-web-server.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-remote-code-execution-via-web-server.asciidoc
new file mode 100644
index 0000000000..5e04750afd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-remote-code-execution-via-web-server.asciidoc
@@ -0,0 +1,201 @@
+[[potential-remote-code-execution-via-web-server]]
+=== Potential Remote Code Execution via Web Server
+
+Identifies suspicious commands executed via a web server, which may suggest a vulnerability and remote shell access. Attackers may exploit a vulnerability in a web application to execute commands via a web server, or place a backdoor file that can be abused to gain code execution as a mechanism for persistence.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://pentestlab.blog/tag/web-shell/
+* https://www.elastic.co/security-labs/elastic-response-to-the-the-spring4shell-vulnerability-cve-2022-22965
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Initial Access
+* Data Source: Elastic Endgame
+* Use Case: Vulnerability
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Remote Code Execution via Web Server*
+
+
+Adversaries may backdoor web servers with web shells to establish persistent access to systems. A web shell is a malicious script, often embedded into a compromised web server, that grants an attacker remote access and control over the server. This enables the execution of arbitrary commands, data exfiltration, and further exploitation of the target network.
+
+This rule detects a web server process spawning script and command line interface programs, potentially indicating attackers executing commands using the web shell.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Investigate abnormal behaviors by the subject process such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential reverse shells or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+  - Investigate the process information for malicious or uncommon processes/process trees.
+    - !{osquery{"label":"Osquery - Retrieve Process Info","query":"SELECT name, cmdline, parent, path, uid FROM processes"}}
+  - Investigate the process tree spawned from the user that is used to run the web application service. A user that is running a web application should not spawn other child processes.
+    - !{osquery{"label":"Osquery - Retrieve Process Info for Webapp User","query":"SELECT name, cmdline, parent, path, uid FROM processes WHERE uid = {{process.user.id}}"}}
+- Examine the command line to determine which commands or scripts were executed.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+  - Use a private sandboxed malware analysis system to perform analysis.
+    - Observe and collect information about the following activities:
+      - Attempts to contact external domains and addresses.
+        - Check if the domain is newly registered or unexpected.
+        - Check the reputation of the domain or IP address.
+      - File access, modification, and creation activities.
+      - Cron jobs, services and other persistence mechanisms.
+        - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and
+event.action in ("exec", "exec_event") and process.parent.executable : (
+  "/usr/sbin/nginx", "/usr/local/sbin/nginx",
+  "/usr/sbin/apache", "/usr/local/sbin/apache",
+  "/usr/sbin/apache2", "/usr/local/sbin/apache2",
+  "/usr/sbin/php*", "/usr/local/sbin/php*",
+  "/usr/sbin/lighttpd", "/usr/local/sbin/lighttpd",
+  "/usr/sbin/hiawatha", "/usr/local/sbin/hiawatha",
+  "/usr/local/bin/caddy", 
+  "/usr/local/lsws/bin/lswsctrl",
+  "*/bin/catalina.sh"
+) and
+process.name : (
+  "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "python*", "php*", "perl", "ruby", "lua*", "openssl", "nc",
+  "netcat", "ncat", "telnet", "awk", "socat"
+  ) and process.args : (
+  "whoami", "id", "uname", "cat", "hostname", "ip", "curl", "wget", "pwd", "ls", "cd", "python*", "php*", "perl",
+  "ruby", "lua*", "openssl", "nc", "netcat", "ncat", "telnet", "awk", "socat"
+  ) and not process.name == "phpquery"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Server Software Component
+** ID: T1505
+** Reference URL: https://attack.mitre.org/techniques/T1505/
+* Sub-technique:
+** Name: Web Shell
+** ID: T1505.003
+** Reference URL: https://attack.mitre.org/techniques/T1505/003/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Exploit Public-Facing Application
+** ID: T1190
+** Reference URL: https://attack.mitre.org/techniques/T1190/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-remote-credential-access-via-registry.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-remote-credential-access-via-registry.asciidoc
index 7a95806278..be83731103 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-remote-credential-access-via-registry.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-remote-credential-access-via-registry.asciidoc
@@ -5,120 +5,122 @@ Identifies remote access to the registry to potentially dump credential data fro
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* winlogbeat-*
-* logs-system.*
-* logs-endpoint.events.*
+* logs-endpoint.events.file-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/SecureAuthCorp/impacket/blob/master/examples/secretsdump.py
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-* Credential Access
-* Investigation Guide
-
-*Version*: 102 (<<potential-remote-credential-access-via-registry-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 8.2.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Potential Remote Credential Access via Registry
+*Triage and analysis*
+
+
+
+*Investigating Potential Remote Credential Access via Registry*
+
+
+Dumping registry hives is a common way to access credential information. Some hives store credential material, such as the SAM hive, which stores locally cached credentials (SAM secrets), and the SECURITY hive, which stores domain cached credentials (LSA secrets). Dumping these hives in combination with the SYSTEM hive enables the attacker to decrypt these secrets.
+
+Attackers can use tools like secretsdump.py or CrackMapExec to dump the registry hives remotely, and use dumped credentials to access other systems in the domain.
 
-Dumping registry hives is a common way to access credential information. Some hives store credential material,
-such as the SAM hive, which stores locally cached credentials (SAM secrets), and the SECURITY hive, which stores domain
-cached credentials (LSA secrets). Dumping these hives in combination with the SYSTEM hive enables the attacker to
-decrypt these secrets.
 
-Attackers can use tools like secretsdump.py or CrackMapExec to dump the registry hives remotely, and use dumped
-credentials to access other systems in the domain.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the specifics of the involved assets, such as their role, criticality, and associated users.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Determine the privileges of the compromised accounts.
 - Investigate other alerts associated with the user/source host during the past 48 hours.
-- Investigate potentially compromised accounts. Analysts can do this by searching for login events (e.g., 4624) to the target
-host.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (e.g., 4624) to the target host.
 
-### False positive analysis
 
-- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious
-must be monitored by the security team.
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+
+
+*Related rules*
 
-### Related rules
 
 - Credential Acquisition via Registry Hive Dumping - a7e7bfa3-088e-4f13-b29e-3986e0e756b8
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine if other hosts were compromised.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Reimage the host operating system or restore the compromised files to clean versions.
 - Ensure that the machine has the latest security updates and is not running unsupported Windows versions.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule uses Elastic Endpoint file creation and system integration events for correlation. Both data should be collected from the host for this detection to work.
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, user.id with maxspan=1m [authentication where
-event.outcome == "success" and event.action == "logged-in" and
-winlog.logon.type == "Network" and not user.name == "ANONYMOUS LOGON"
-and not user.domain == "NT AUTHORITY" and source.ip != "127.0.0.1"
-and source.ip !="::1"] [file where event.action == "creation" and
-process.name : "svchost.exe" and file.Ext.header_bytes : "72656766*"
-and user.id : ("S-1-5-21-*", "S-1-12-1-*") and file.size >= 30000 and
-not file.path : ("?:\\Windows\\system32\\HKEY_LOCAL_MACHINE
-_SOFTWARE_Microsoft_*.registry",
-"?:\\Users\\*\\AppData\\Local\\Microsoft\\Windows\\UsrClass.dat.LOG?",
-"?:\\Users\\*\\AppData\\Local\\Microsoft\\Windows\\UsrClass.dat",
-"?:\\Users\\*\\ntuser.dat.LOG?",
-"?:\\Users\\*\\NTUSER.DAT")]
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and
+  event.action == "creation" and process.name : "svchost.exe" and
+  file.Ext.header_bytes : "72656766*" and user.id : ("S-1-5-21-*", "S-1-12-1-*") and file.size >= 30000 and
+  file.path : ("?:\\Windows\\system32\\*.tmp", "?:\\WINDOWS\\Temp\\*.tmp")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -130,8 +132,10 @@ _SOFTWARE_Microsoft_*.registry",
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-
+* Sub-technique:
+** Name: Security Account Manager
+** ID: T1003.002
+** Reference URL: https://attack.mitre.org/techniques/T1003/002/
 * Tactic:
 ** Name: Lateral Movement
 ** ID: TA0008
@@ -140,47 +144,3 @@ _SOFTWARE_Microsoft_*.registry",
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[potential-remote-credential-access-via-registry-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, user.id with maxspan=1m [authentication where
-event.outcome == "success" and event.action == "logged-in" and
-winlog.logon.type == "Network" and not user.name == "ANONYMOUS LOGON"
-and not user.domain == "NT AUTHORITY" and source.ip != "127.0.0.1"
-and source.ip !="::1"] [file where event.action == "creation" and
-process.name : "svchost.exe" and file.Ext.header_bytes : "72656766*"
-and user.id : "S-1-5-21-*" and file.size >= 30000 and not file.path
-: ("?:\\Windows\\system32\\HKEY_LOCAL_MACHINE_SOFTWARE_Micr
-osoft_*.registry",
-"?:\\Users\\*\\AppData\\Local\\Microsoft\\Windows\\UsrClass.dat.LOG?",
-"?:\\Users\\*\\AppData\\Local\\Microsoft\\Windows\\UsrClass.dat",
-"?:\\Users\\*\\ntuser.dat.LOG?",
-"?:\\Users\\*\\NTUSER.DAT")]
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, user.id with maxspan=1m [authentication where
-event.outcome == "success" and winlog.logon.type == "Network" and
-not user.name == "ANONYMOUS LOGON" and not user.domain == "NT
-AUTHORITY" and source.ip != "127.0.0.1" and source.ip !="::1"] [file
-where event.action == "creation" and process.name : "svchost.exe" and
-file.Ext.header_bytes : "72656766*" and user.id : "S-1-5-21-*" and
-file.size >= 30000]
-----------------------------------
-
-Version 2 (8.3.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-remote-desktop-shadowing-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-remote-desktop-shadowing-activity.asciidoc
index a924e2b657..f421721c01 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-remote-desktop-shadowing-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-remote-desktop-shadowing-activity.asciidoc
@@ -5,71 +5,85 @@ Identifies the modification of the Remote Desktop Protocol (RDP) Shadow registry
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.registry-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://bitsadm.in/blog/spying-on-users-using-rdp-shadowing
 * https://swarm.ptsecurity.com/remote-desktop-services-shadowing/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-
-*Version*: 100 (<<potential-remote-desktop-shadowing-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.13.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-/* Identifies the modification of RDP Shadow registry or the
-execution of processes indicative of active shadow RDP session */ any
-where (event.category == "registry" and registry.path :
-"HKLM\\Software\\Policies\\Microsoft\\Windows NT\\Terminal
-Services\\Shadow" ) or (event.category == "process" and
-(process.name : ("RdpSaUacHelper.exe", "RdpSaProxy.exe") and
-process.parent.name : "svchost.exe") or
-(process.pe.original_file_name : "mstsc.exe" and process.args :
-"/shadow:*") )
+[source, js]
 ----------------------------------
+/* Identifies the modification of RDP Shadow registry or
+  the execution of processes indicative of active shadow RDP session */
+
+any where host.os.type == "windows" and
+(
+  (event.category == "registry" and
+     registry.path : (
+      "HKLM\\Software\\Policies\\Microsoft\\Windows NT\\Terminal Services\\Shadow",
+      "\\REGISTRY\\MACHINE\\Software\\Policies\\Microsoft\\Windows NT\\Terminal Services\\Shadow"
+    )
+  ) or
+  (event.category == "process" and event.type == "start" and
+     (process.name : ("RdpSaUacHelper.exe", "RdpSaProxy.exe") and process.parent.name : "svchost.exe") or
+     (process.pe.original_file_name : "mstsc.exe" and process.args : "/shadow:*")
+  )
+)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,29 +95,7 @@ process.parent.name : "svchost.exe") or
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[potential-remote-desktop-shadowing-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* Identifies the modification of RDP Shadow registry or the
-execution of processes indicative of active shadow RDP session */ any
-where (event.category == "registry" and registry.path :
-"HKLM\\Software\\Policies\\Microsoft\\Windows NT\\Terminal
-Services\\Shadow" ) or (event.category == "process" and
-(process.name : ("RdpSaUacHelper.exe", "RdpSaProxy.exe") and
-process.parent.name : "svchost.exe") or
-(process.pe.original_file_name : "mstsc.exe" and process.args :
-"/shadow:*") )
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Remote Desktop Protocol
+** ID: T1021.001
+** Reference URL: https://attack.mitre.org/techniques/T1021/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-remote-desktop-tunneling-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-remote-desktop-tunneling-detected.asciidoc
index 039bc8f140..d6f1b8909f 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-remote-desktop-tunneling-detected.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-remote-desktop-tunneling-detected.asciidoc
@@ -5,109 +5,121 @@ Identifies potential use of an SSH utility to establish RDP over a reverse SSH T
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.netspi.com/how-to-access-rdp-over-a-reverse-ssh-tunnel/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<potential-remote-desktop-tunneling-detected-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Tactic: Lateral Movement
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Potential Remote Desktop Tunneling Detected
+*Triage and analysis*
+
 
-Protocol Tunneling is a mechanism that involves explicitly encapsulating a protocol within another for various use cases,
-ranging from providing an outer layer of encryption (similar to a VPN) to enabling traffic that network appliances would
-filter to reach their destination.
 
-Attackers may tunnel Remote Desktop Protocol (RDP) traffic through other protocols like Secure Shell (SSH) to bypass network restrictions that block incoming RDP
-connections but may be more permissive to other protocols.
+*Investigating Potential Remote Desktop Tunneling Detected*
 
-This rule looks for command lines involving the `3389` port, which RDP uses by default and options commonly associated
-with tools that perform tunneling.
 
-#### Possible investigation steps
+Protocol Tunneling is a mechanism that involves explicitly encapsulating a protocol within another for various use cases, ranging from providing an outer layer of encryption (similar to a VPN) to enabling traffic that network appliances would filter to reach their destination.
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+Attackers may tunnel Remote Desktop Protocol (RDP) traffic through other protocols like Secure Shell (SSH) to bypass network restrictions that block incoming RDP connections but may be more permissive to other protocols.
+
+This rule looks for command lines involving the `3389` port, which RDP uses by default and options commonly associated with tools that perform tunneling.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account and system owners and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
 - Examine network data to determine if the host communicated with external servers using the tunnel.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 - Investigate the command line for the execution of programs that are unrelated to tunneling, like Remote Desktop clients.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Take the necessary actions to disable the tunneling, which can be a process kill, service deletion, registry key
-modification, etc. Inspect the host to learn which method was used and to determine a response for the case.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Take the necessary actions to disable the tunneling, which can be a process kill, service deletion, registry key modification, etc. Inspect the host to learn which method was used and to determine a response for the case.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and /* RDP port and usual SSH
-tunneling related switches in command line */ process.args :
-"*:3389" and process.args : ("-L", "-P", "-R", "-pw", "-ssh")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  /* RDP port and usual SSH tunneling related switches in command line */
+  process.args : "*:3389" and
+  process.args : ("-L", "-P", "-R", "-pw", "-ssh")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -119,55 +131,15 @@ tunneling related switches in command line */ process.args :
 ** Name: Protocol Tunneling
 ** ID: T1572
 ** Reference URL: https://attack.mitre.org/techniques/T1572/
-
-[[potential-remote-desktop-tunneling-detected-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and /* RDP
-port and usual SSH tunneling related switches in command line */
-process.args : "*:3389" and process.args : ("-L", "-P", "-R", "-pw",
-"-ssh")
-----------------------------------
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-/* RDP port and usual SSH tunneling related switches in commandline */
-wildcard(process.args, "*:3389") and wildcard(process.args,"-L", "-P",
-"-R", "-pw", "-ssh")
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-/* RDP port and usual SSH tunneling related switches in commandline */
-wildcard(process.args, "*:3389") and wildcard(process.args,"-L", "-P",
-"-R", "-pw", "-ssh")
-----------------------------------
-
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SSH
+** ID: T1021.004
+** Reference URL: https://attack.mitre.org/techniques/T1021/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-remote-file-execution-via-msiexec.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-remote-file-execution-via-msiexec.asciidoc
new file mode 100644
index 0000000000..b3bbca7d0d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-remote-file-execution-via-msiexec.asciidoc
@@ -0,0 +1,107 @@
+[[potential-remote-file-execution-via-msiexec]]
+=== Potential Remote File Execution via MSIEXEC
+
+Identifies the execution of the built-in Windows Installer, msiexec.exe, to install a remote package. Adversaries may abuse msiexec.exe to launch local or network accessible MSI files.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence with maxspan=1m
+ [process where host.os.type == "windows" and event.action == "start" and
+    process.name : "msiexec.exe" and process.args : "/V"] by process.entity_id
+ [network where host.os.type == "windows" and process.name : "msiexec.exe" and
+    event.action == "connection_attempted"] by process.entity_id
+ [process where host.os.type == "windows" and event.action == "start" and
+  process.parent.name : "msiexec.exe" and user.id : ("S-1-5-21-*", "S-1-5-12-1-*") and
+  not process.executable : ("?:\\Windows\\SysWOW64\\msiexec.exe",
+                            "?:\\Windows\\System32\\msiexec.exe",
+                            "?:\\Windows\\System32\\srtasks.exe",
+                            "?:\\Windows\\SysWOW64\\srtasks.exe",
+                            "?:\\Windows\\System32\\taskkill.exe",
+                            "?:\\Windows\\Installer\\MSI*.tmp",
+                            "?:\\Program Files\\*.exe",
+                            "?:\\Program Files (x86)\\*.exe",
+                            "?:\\Windows\\System32\\ie4uinit.exe",
+                            "?:\\Windows\\SysWOW64\\ie4uinit.exe",
+                            "?:\\Windows\\System32\\sc.exe",
+                            "?:\\Windows\\system32\\Wbem\\mofcomp.exe",
+                            "?:\\Windows\\twain_32\\fjscan32\\SOP\\crtdmprc.exe",
+                            "?:\\Windows\\SysWOW64\\taskkill.exe",
+                            "?:\\Windows\\SysWOW64\\schtasks.exe",
+                            "?:\\Windows\\system32\\schtasks.exe",
+                            "?:\\Windows\\System32\\sdbinst.exe") and
+  not (process.code_signature.subject_name == "Citrix Systems, Inc." and process.code_signature.trusted == true) and
+  not (process.name : ("regsvr32.exe", "powershell.exe", "rundll32.exe", "wscript.exe") and
+       process.Ext.token.integrity_level_name == "high" and
+       process.args : ("?:\\Program Files\\*", "?:\\Program Files (x86)\\*")) and
+  not (process.executable : ("?:\\Program Files\\*.exe", "?:\\Program Files (x86)\\*.exe") and process.code_signature.trusted == true) and
+  not (process.name : "rundll32.exe" and process.args : "printui.dll,PrintUIEntry")
+  ] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: Msiexec
+** ID: T1218.007
+** Reference URL: https://attack.mitre.org/techniques/T1218/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-activity-via-terminal.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-activity-via-terminal.asciidoc
index 14874d8a1b..aad4023b35 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-activity-via-terminal.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-activity-via-terminal.asciidoc
@@ -5,7 +5,7 @@ Identifies the execution of a shell process with suspicious arguments which may
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,106 +14,114 @@ Identifies the execution of a shell process with suspicious arguments which may
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Methodology%20and%20Resources/Reverse%20Shell%20Cheatsheet.md
 * https://github.com/WangYihang/Reverse-Shell-Manager
 * https://www.netsparker.com/blog/web-security/understanding-reverse-shells/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* macOS
-* Threat Detection
-* Execution
-* Investigation Guide
-
-*Version*: 102 (<<potential-reverse-shell-activity-via-terminal-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Potential Reverse Shell Activity via Terminal
+*Triage and analysis*
 
-A reverse shell is a mechanism that's abused to connect back to an attacker-controlled system. It effectively redirects
-the system's input and output and delivers a fully functional remote shell to the attacker. Even private systems are
-vulnerable since the connection is outgoing. This activity is typically the result of vulnerability exploitation,
-malware infection, or penetration testing.
+
+
+*Investigating Potential Reverse Shell Activity via Terminal*
+
+
+A reverse shell is a mechanism that's abused to connect back to an attacker-controlled system. It effectively redirects the system's input and output and delivers a fully functional remote shell to the attacker. Even private systems are vulnerable since the connection is outgoing. This activity is typically the result of vulnerability exploitation, malware infection, or penetration testing.
 
 This rule identifies commands that are potentially related to reverse shell activities using shell applications.
 
-#### Possible investigation steps
+
+*Possible investigation steps*
+
 
 - Examine the command line and extract the target domain or IP address information.
   - Check if the domain is newly registered or unexpected.
   - Check the reputation of the domain or IP address.
-  - Scope other potentially compromised hosts in your environment by mapping hosts that also communicated with the
-  domain or IP address.
+  - Scope other potentially compromised hosts in your environment by mapping hosts that also communicated with the domain or IP address.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
-- Investigate any abnormal behavior by the subject process such as network connections, file modifications, and any
-spawned child processes.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+- Investigate any abnormal behavior by the subject process such as network connections, file modifications, and any spawned child processes.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
 
-### False positive analysis
 
-- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently
-malicious must be monitored by the security team.
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Take actions to terminate processes and connections used by the attacker.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 process where event.type in ("start", "process_started") and
-process.name in ("sh", "bash", "zsh", "dash", "zmodload") and
-process.args : ("*/dev/tcp/*", "*/dev/udp/*", "*zsh/net/tcp*",
-"*zsh/net/udp*") and /* noisy FPs */ not (process.parent.name :
-"timeout" and process.executable : "/var/lib/docker/overlay*") and
-not process.command_line : ("*/dev/tcp/sirh_db/*",
-"*/dev/tcp/remoteiot.com/*", "*dev/tcp/elk.stag.one/*",
-"*dev/tcp/kafka/*", "*/dev/tcp/$0/$1*", "*/dev/tcp/127.*",
-"*/dev/udp/127.*", "*/dev/tcp/localhost/*") and not
-process.parent.command_line : "runc init"
-----------------------------------
+  process.name in ("sh", "bash", "zsh", "dash", "zmodload") and
+  process.args : ("*/dev/tcp/*", "*/dev/udp/*", "*zsh/net/tcp*", "*zsh/net/udp*") and
+
+  /* noisy FPs */
+  not (process.parent.name : "timeout" and process.executable : "/var/lib/docker/overlay*") and
+  not process.command_line : (
+    "*/dev/tcp/sirh_db/*", "*/dev/tcp/remoteiot.com/*", "*dev/tcp/elk.stag.one/*", "*dev/tcp/kafka/*",
+    "*/dev/tcp/$0/$1*", "*/dev/tcp/127.*", "*/dev/udp/127.*", "*/dev/tcp/localhost/*", "*/dev/tcp/itom-vault/*") and
+  not process.parent.command_line : "runc init"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -125,27 +133,3 @@ process.parent.command_line : "runc init"
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[potential-reverse-shell-activity-via-terminal-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name in ("sh", "bash", "zsh", "dash", "zmodload") and
-process.args:("*/dev/tcp/*", "*/dev/udp/*", "zsh/net/tcp",
-"zsh/net/udp")
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-background-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-background-process.asciidoc
new file mode 100644
index 0000000000..a067dc277c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-background-process.asciidoc
@@ -0,0 +1,112 @@
+[[potential-reverse-shell-via-background-process]]
+=== Potential Reverse Shell via Background Process
+
+Monitors for the execution of background processes with process arguments capable of opening a socket in the /dev/tcp channel. This may indicate the creation of a backdoor reverse connection, and should be investigated further.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and 
+process.name in ("setsid", "nohup") and process.args : "*/dev/tcp/*0>&1*" and 
+process.parent.name in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-child.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-child.asciidoc
new file mode 100644
index 0000000000..6af72f1eba
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-child.asciidoc
@@ -0,0 +1,119 @@
+[[potential-reverse-shell-via-child]]
+=== Potential Reverse Shell via Child
+
+This detection rule identifies suspicious network traffic patterns associated with TCP reverse shell activity. This activity consists of a network event that is followed by the creation of a shell process with suspicious command line arguments. An attacker may establish a Linux TCP reverse shell to gain remote access to a target system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Methodology%20and%20Resources/Reverse%20Shell%20Cheatsheet.md
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click Add integrations.
+- In the query bar, search for Elastic Defend and select the integration to see more details about it.
+- Click Add Elastic Defend.
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either Traditional Endpoints or Cloud Workloads.
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in New agent policy name. If other agent policies already exist, you can click the Existing hosts tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click Save and Continue.
+- To complete the integration, select Add Elastic Agent to your hosts and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.entity_id with maxspan=5s
+  [network where event.type == "start" and event.action in ("connection_attempted", "connection_accepted") and 
+   process.name : ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "socat") and destination.ip != null and 
+   not cidrmatch(destination.ip, "127.0.0.0/8", "169.254.0.0/16", "224.0.0.0/4", "::1")]
+  [process where event.type == "start" and event.action == "exec" and 
+   process.name in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") and (
+     (process.args : ("-i", "-l")) or (process.parent.name == "socat" and process.parent.args : "*exec*")
+   )]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-java.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-java.asciidoc
new file mode 100644
index 0000000000..3f0ab8110a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-java.asciidoc
@@ -0,0 +1,127 @@
+[[potential-reverse-shell-via-java]]
+=== Potential Reverse Shell via Java
+
+This detection rule identifies the execution of a Linux shell process from a Java JAR application post an incoming network connection. This behavior may indicate reverse shell activity via a Java application.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Methodology%20and%20Resources/Reverse%20Shell%20Cheatsheet.md
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=5s
+  [network where host.os.type == "linux" and event.action in ("connection_accepted", "connection_attempted") and 
+   process.executable : ("/usr/bin/java", "/bin/java", "/usr/lib/jvm/*", "/usr/java/*") and 
+   not (destination.ip == null or destination.ip == "0.0.0.0" or cidrmatch(
+     destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.0.0.0/29",
+     "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
+     "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
+     "192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
+     "FF00::/8"
+    )
+  )] by process.entity_id
+  [process where host.os.type == "linux" and event.action == "exec" and 
+   process.parent.executable : ("/usr/bin/java", "/bin/java", "/usr/lib/jvm/*", "/usr/java/*") and
+   process.parent.args : "-jar" and process.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")
+   and not process.parent.args in (
+     "/usr/share/java/jenkins.war", "/etc/remote-iot/services/remoteiot.jar",
+     "/usr/lib64/NetExtender.jar", "/usr/lib/jenkins/jenkins.war"
+   )] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-suspicious-binary.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-suspicious-binary.asciidoc
new file mode 100644
index 0000000000..370e8ba664
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-suspicious-binary.asciidoc
@@ -0,0 +1,127 @@
+[[potential-reverse-shell-via-suspicious-binary]]
+=== Potential Reverse Shell via Suspicious Binary
+
+This detection rule detects the creation of a shell through a chain consisting of the execution of a suspicious binary (located in a commonly abused location or executed manually) followed by a network event and ending with a shell being spawned. Stageless reverse tcp shells display this behaviour. Attackers may spawn reverse shells to establish persistence onto a target system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Methodology%20and%20Resources/Reverse%20Shell%20Cheatsheet.md
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.entity_id with maxspan=1s
+[ process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+  process.executable : (
+  "./*", "/tmp/*", "/var/tmp/*", "/var/www/*", "/dev/shm/*", "/etc/init.d/*", "/etc/rc*.d/*",
+  "/etc/crontab", "/etc/cron.*", "/etc/update-motd.d/*", "/usr/lib/update-notifier/*",
+  "/boot/*", "/srv/*", "/run/*", "/root/*", "/etc/rc.local"
+   ) and
+  process.parent.name : ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") and not
+  process.name : ("curl", "wget", "ping", "apt", "dpkg", "yum", "rpm", "dnf", "dockerd") ]
+[ network where host.os.type == "linux" and event.type == "start" and event.action in ("connection_attempted", "connection_accepted") and
+  process.executable : (
+  "./*", "/tmp/*", "/var/tmp/*", "/var/www/*", "/dev/shm/*", "/etc/init.d/*", "/etc/rc*.d/*",
+  "/etc/crontab", "/etc/cron.*", "/etc/update-motd.d/*", "/usr/lib/update-notifier/*",
+  "/boot/*", "/srv/*", "/run/*", "/root/*", "/etc/rc.local"
+   ) and destination.ip != null and destination.ip != "127.0.0.1" and destination.ip != "::1" ]
+[ process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+  process.name : ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") and 
+  process.parent.name : ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") ]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-suspicious-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-suspicious-child-process.asciidoc
new file mode 100644
index 0000000000..58ae9136e8
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-suspicious-child-process.asciidoc
@@ -0,0 +1,135 @@
+[[potential-reverse-shell-via-suspicious-child-process]]
+=== Potential Reverse Shell via Suspicious Child Process
+
+This detection rule detects the creation of a shell through a suspicious process chain. Any reverse shells spawned by the specified utilities that are initialized from a single process followed by a network connection attempt will be captured through this rule. Attackers may spawn reverse shells to establish persistence onto a target system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Methodology%20and%20Resources/Reverse%20Shell%20Cheatsheet.md
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 9
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.entity_id with maxspan=1s
+  [process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "fork") and (
+    (process.name : "python*" and process.args : "-c" and process.args : (
+     "*import*pty*spawn*", "*import*subprocess*call*"
+    )) or
+    (process.name : "perl*" and process.args : "-e" and process.args : "*socket*" and process.args : (
+     "*exec*", "*system*"
+    )) or
+    (process.name : "ruby*" and process.args : ("-e", "-rsocket") and process.args : (
+     "*TCPSocket.new*", "*TCPSocket.open*"
+     )) or
+    (process.name : "lua*" and process.args : "-e" and process.args : "*socket.tcp*" and process.args : (
+     "*io.popen*", "*os.execute*"
+    )) or
+    (process.name : "php*" and process.args : "-r" and process.args : "*fsockopen*" and process.args : "*/bin/*sh*") or 
+    (process.name : ("awk", "gawk", "mawk", "nawk") and process.args : "*/inet/tcp/*") or
+    (process.name : "openssl" and process.args : "-connect") or
+    (process.name : ("nc", "ncat", "netcat") and process.args == "-e" and process.args_count >= 3 and 
+     not process.args == "-z") or
+    (process.name : "telnet" and process.args_count >= 3)
+  ) and process.parent.name : (
+    "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "python*", "php*", "perl", "ruby", "lua*",
+    "openssl", "nc", "netcat", "ncat", "telnet", "awk")]
+  [network where host.os.type == "linux" and event.type == "start" and event.action in ("connection_attempted", "connection_accepted") and 
+    process.name : ("python*", "php*", "perl", "ruby", "lua*", "openssl", "nc", "netcat", "ncat", "telnet", "awk") and 
+    destination.ip != null and not cidrmatch(destination.ip, "127.0.0.0/8", "169.254.0.0/16", "224.0.0.0/4", "::1")]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-udp.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-udp.asciidoc
new file mode 100644
index 0000000000..1f8b91630b
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell-via-udp.asciidoc
@@ -0,0 +1,139 @@
+[[potential-reverse-shell-via-udp]]
+=== Potential Reverse Shell via UDP
+
+This detection rule identifies suspicious network traffic patterns associated with UDP reverse shell activity. This activity consists of a sample of an execve, socket and connect syscall executed by the same process, where the auditd.data.a0-1 indicate a UDP connection, ending with an egress connection event. An attacker may establish a Linux UDP reverse shell to bypass traditional firewall restrictions and gain remote access to a target system covertly.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Methodology%20and%20Resources/Reverse%20Shell%20Cheatsheet.md
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Auditbeat
+- Auditd Manager
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Auditd Manager Integration Setup*
+
+The Auditd Manager Integration receives audit events from the Linux Audit Framework which is a part of the Linux kernel.
+Auditd Manager provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system.
+
+
+*The following steps should be executed in order to add the Elastic Agent System integration "auditd_manager" on a Linux System:*
+
+- Go to the Kibana home page and click “Add integrations”.
+- In the query bar, search for “Auditd Manager” and select the integration to see more details about it.
+- Click “Add Auditd Manager”.
+- Configure the integration name and optionally add a description.
+- Review optional and advanced settings accordingly.
+- Add the newly installed “auditd manager” to an existing or a new agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+- Click “Save and Continue”.
+- For more details on the integration refer to the https://docs.elastic.co/integrations/auditd_manager[helper guide].
+
+
+*Rule Specific Setup Note*
+
+Auditd Manager subscribes to the kernel and receives events as they occur without any additional configuration.
+However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+- For this detection rule no additional audit rules are required to be added to the integration.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sample by host.id, process.pid, process.parent.pid
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "executed" and process.name : (
+    "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "perl", "python*", "nc", "ncat", "netcat", "php*",
+    "ruby", "openssl", "awk", "telnet", "lua*", "socat"
+    )]
+  [process where host.os.type == "linux" and auditd.data.syscall == "socket" and process.name : (
+    "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "perl", "python*", "nc", "ncat", "netcat", "php*",
+    "ruby", "openssl", "awk", "telnet", "lua*", "socat"
+    ) and auditd.data.a1 == "2"]
+  [network where host.os.type == "linux" and event.type == "start" and event.action == "connected-to" and
+   process.name : (
+    "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "perl", "python*", "nc", "ncat", "netcat", "php*",
+    "ruby", "openssl", "awk", "telnet", "lua*", "socat"
+    ) and network.direction == "egress" and destination.ip != null and
+   not cidrmatch(destination.ip, "127.0.0.0/8", "169.254.0.0/16", "224.0.0.0/4", "::1")]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell.asciidoc
new file mode 100644
index 0000000000..6a78e3dcb2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-reverse-shell.asciidoc
@@ -0,0 +1,117 @@
+[[potential-reverse-shell]]
+=== Potential Reverse Shell
+
+This detection rule identifies suspicious network traffic patterns associated with TCP reverse shell activity. This activity consists of a parent-child relationship where a network event is followed by the creation of a shell process. An attacker may establish a Linux TCP reverse shell to gain remote access to a target system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Methodology%20and%20Resources/Reverse%20Shell%20Cheatsheet.md
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=5s
+  [network where event.type == "start" and event.action in ("connection_attempted", "connection_accepted") and 
+   process.name : ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "socat") and destination.ip != null and 
+   not cidrmatch(destination.ip, "127.0.0.0/8", "169.254.0.0/16", "224.0.0.0/4", "::1")] by process.entity_id
+  [process where event.type == "start" and event.action in ("exec", "fork") and 
+   process.name in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") and (
+     (process.args : ("-i", "-l")) or (process.parent.name == "socat" and process.parent.args : "*exec*")
+   )] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-secure-file-deletion-via-sdelete-utility.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-secure-file-deletion-via-sdelete-utility.asciidoc
index 55b0170c28..69aab17d3f 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-secure-file-deletion-via-sdelete-utility.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-secure-file-deletion-via-sdelete-utility.asciidoc
@@ -5,108 +5,120 @@ Detects file name patterns generated by the use of Sysinternals SDelete utility
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 101 (<<potential-secure-file-deletion-via-sdelete-utility-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Impact
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-Verify process details such as command line and hash to confirm this activity legitimacy.
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Potential Secure File Deletion via SDelete Utility*
 
-[source,js]
-----------------------------------
-file where event.type == "change" and file.name : "*AAA.AAA"
-----------------------------------
 
-==== Threat mapping
+SDelete is a tool primarily used for securely deleting data from storage devices, making it unrecoverable. Microsoft develops it as part of the Sysinternals Suite. Although commonly used to delete data securely, attackers can abuse it to delete forensic indicators and remove files as a post-action to a destructive action such as ransomware or data theft to hinder recovery efforts.
 
-*Framework*: MITRE ATT&CK^TM^
+This rule identifies file name patterns generated by the use of SDelete utility to securely delete a file via multiple file overwrite and rename operations.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Indicator Removal on Host
-** ID: T1070
-** Reference URL: https://attack.mitre.org/techniques/T1070/
 
-[[potential-secure-file-deletion-via-sdelete-utility-history]]
-==== Rule version history
+*Possible investigation steps*
 
-Version 101 (8.6.0 release)::
-* Formatting only
 
-Version 100 (8.5.0 release)::
-* Formatting only
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Examine the command line and identify the files deleted, their importance and whether they could be the target of antiforensics activity.
 
-Version 8 (8.4.0 release)::
-* Formatting only
 
-Version 6 (8.2.0 release)::
-* Formatting only
+*False positive analysis*
 
-Version 5 (7.13.0 release)::
-* Formatting only
 
-Version 4 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type == "change" and wildcard(file.name,"*AAA.AAA")
-----------------------------------
+- This is a dual-use tool, meaning its usage is not inherently malicious. Analysts can dismiss the alert if the administrator is aware of the activity, no other suspicious activity was identified, and there are justifications for the execution.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+  - Prioritize cases involving critical servers and users.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If important data was encrypted, deleted, or modified, activate your data recovery plan.
+    - Perform data recovery locally or restore the backups from replicated copies (cloud, other servers, etc.).
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Review the privileges assigned to the user to ensure that the least privilege principle is being followed.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
 
-Version 3 (7.11.2 release)::
-* Formatting only
 
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.category:file AND event.type:change AND file.name:/.+A+\.AAA/
+file where host.os.type == "windows" and event.type == "change" and file.name : "*AAA.AAA"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indicator Removal
+** ID: T1070
+** Reference URL: https://attack.mitre.org/techniques/T1070/
+* Sub-technique:
+** Name: File Deletion
+** ID: T1070.004
+** Reference URL: https://attack.mitre.org/techniques/T1070/004/
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Data Destruction
+** ID: T1485
+** Reference URL: https://attack.mitre.org/techniques/T1485/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-shadow-credentials-added-to-ad-object.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-shadow-credentials-added-to-ad-object.asciidoc
index 0563d1b308..118ad6862f 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-shadow-credentials-added-to-ad-object.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-shadow-credentials-added-to-ad-object.asciidoc
@@ -5,71 +5,132 @@ Identify the modification of the msDS-KeyCredentialLink attribute in an Active D
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://posts.specterops.io/shadow-credentials-abusing-key-trust-account-mapping-for-takeover-8ee1a53566ab
 * https://www.thehacker.recipes/ad/movement/kerberos/shadow-credentials
 * https://github.com/OTRF/Set-AuditRule
 * https://cyberstoph.org/posts/2022/03/detecting-shadow-credentials/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Active Directory
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Active Directory
 
-*Version*: 101 (<<potential-shadow-credentials-added-to-ad-object-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.1.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Modifications in the msDS-KeyCredentialLink attribute can be done legitimately by the Azure AD Connect synchronization account or the ADFS service account. These accounts can be added as Exceptions.
 
-==== Investigation guide
 
+*Investigating Potential Shadow Credentials added to AD Object*
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+The msDS-KeyCredentialLink is an Active Directory (AD) attribute that links cryptographic certificates to a user or computer for domain authentication.
+
+Attackers with write privileges on this attribute over an object can abuse it to gain access to the object or maintain persistence. This means they can authenticate and perform actions on behalf of the exploited identity, and they can use Shadow Credentials to request Ticket Granting Tickets (TGTs) on behalf of the identity.
+
+
+*Possible investigation steps*
+
+
+- Identify whether Windows Hello for Business (WHfB) and/or Azure AD is used in the environment.
+  - Review the event ID 4624 for logon events involving the subject identity (`winlog.event_data.SubjectUserName`).
+    - Check whether the `source.ip` is the server running Azure AD Connect.
+- Contact the account and system owners and confirm whether they are aware of this activity.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Review the event IDs 4768 and 4769 for suspicious ticket requests involving the modified identity (`winlog.event_data.ObjectDN`).
+  - Extract the source IP addresses from these events and use them as indicators of compromise (IoCs) to investigate whether the host is compromised and to scope the attacker's access to the environment.
+
+
+*False positive analysis*
+
+
+- Administrators might use custom accounts on Azure AD Connect. If this is the case, make sure the account is properly secured. You can also create an exception for the account if expected activity makes too much noise in your environment.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+  - Remove the Shadow Credentials from the object.
+- Investigate how the attacker escalated privileges and identify systems they used to conduct lateral movement. Use this information to determine ways the attacker could regain access to the environment.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Directory Service Changes' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Changes (Success,Failure)
+```
+
+The above policy does not cover User objects, so we need to set up an AuditRule using https://github.com/OTRF/Set-AuditRule.
+As this specifies the msDS-KeyCredentialLink Attribute GUID, it is expected to be low noise.
+
+```
+Set-AuditRule -AdObjectPath 'AD:\CN=Users,DC=Domain,DC=com' -WellKnownSidType WorldSid -Rights WriteProperty -InheritanceFlags Children -AttributeGUID 5b47d60f-6090-40b2-9f37-2a4de88f3063 -AuditFlags Success
+```
 
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.action:"Directory Service Changes" and event.code:"5136" and
-winlog.event_data.AttributeLDAPDisplayName:"msDS-KeyCredentialLink"
-and winlog.event_data.AttributeValue :B\:828*
-----------------------------------
+ winlog.event_data.AttributeLDAPDisplayName:"msDS-KeyCredentialLink" and winlog.event_data.AttributeValue :B\:828* and
+ not winlog.event_data.SubjectUserName: MSOL_*
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,25 +142,3 @@ and winlog.event_data.AttributeValue :B\:828*
 ** Name: Modify Authentication Process
 ** ID: T1556
 ** Reference URL: https://attack.mitre.org/techniques/T1556/
-
-[[potential-shadow-credentials-added-to-ad-object-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Directory Service Changes" and event.code:"5136" and
-winlog.event_data.AttributeLDAPDisplayName:"msDS-KeyCredentialLink"
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-shadow-file-read-via-command-line-utilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-shadow-file-read-via-command-line-utilities.asciidoc
index cea57da0f6..34b149bf4c 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-shadow-file-read-via-command-line-utilities.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-shadow-file-read-via-command-line-utilities.asciidoc
@@ -3,65 +3,94 @@
 
 Identifies access to the /etc/shadow file via the commandline using standard system utilities. After elevating privileges to root, threat actors may attempt to read or dump this file in order to gain valid credentials. They may utilize these to move laterally undetected and access additional resources.
 
-*Rule type*: eql
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.cyberciti.biz/faq/unix-linux-password-cracking-john-the-ripper/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 208
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Privilege Escalation
-* Credential Access
 
-*Version*: 2 (<<potential-shadow-file-read-via-command-line-utilities-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 8.5.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.6.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and event.action == "exec" and
-user.name == "root" and (process.args : "/etc/shadow" or
-(process.working_directory: "/etc" and process.args: "shadow")) and
-not process.executable: ("/usr/bin/tar", "/bin/tar",
-"/usr/bin/gzip", "/bin/gzip", "/usr/bin/zip",
-"/bin/zip", "/usr/bin/stat", "/bin/stat",
-"/usr/bin/cmp", "/bin/cmp", "/usr/bin/sudo",
-"/bin/sudo", "/usr/bin/find", "/bin/find",
-"/usr/bin/ls", "/bin/ls", "/usr/bin/uniq", "/bin/uniq",
-"/usr/bin/unzip", "/bin/unzip") and not
-process.parent.executable: "/bin/dracut"
+[source, js]
 ----------------------------------
+host.os.type : "linux" and event.category : "process" and event.action : ("exec" or "exec_event") and
+(process.args : "/etc/shadow" or (process.working_directory: "/etc" and process.args: "shadow")) and not 
+(process.executable : ("/bin/chown" or "/usr/bin/chown") and process.args : "root:shadow") and not 
+(process.executable : ("/bin/chmod" or "/usr/bin/chmod") and process.args : "640")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,8 +102,6 @@ process.parent.executable: "/bin/dracut"
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-
 * Tactic:
 ** Name: Credential Access
 ** ID: TA0006
@@ -83,21 +110,7 @@ process.parent.executable: "/bin/dracut"
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[potential-shadow-file-read-via-command-line-utilities-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Rule name changed from: Shadow File Read via Command Line Utilities
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and event.action == "exec" and
-user.name == "root" and process.args : "/etc/shadow" and not
-process.executable: ("/usr/bin/find", "/usr/bin/cmp", "/bin/ls",
-"/usr/sbin/restorecon", "/usr/bin/uniq") and not
-process.parent.executable: "/bin/dracut"
-----------------------------------
-
+* Sub-technique:
+** Name: /etc/passwd and /etc/shadow
+** ID: T1003.008
+** Reference URL: https://attack.mitre.org/techniques/T1003/008/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-sharprdp-behavior.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-sharprdp-behavior.asciidoc
index e2ba83a329..118b5c7ec2 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-sharprdp-behavior.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-sharprdp-behavior.asciidoc
@@ -5,65 +5,68 @@ Identifies potential behavior of SharpRDP, which is a tool that can be used to p
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.registry-*
+* logs-endpoint.events.network-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://posts.specterops.io/revisiting-remote-desktop-lateral-movement-8fb905cb46c3
 * https://github.com/sbousseaden/EVTX-ATTACK-SAMPLES/blob/master/Lateral%20Movement/LM_sysmon_3_12_13_1_SharpRDP.evtx
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-
-*Version*: 101 (<<potential-sharprdp-behavior-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-/* Incoming RDP followed by a new RunMRU string value set to cmd,
-powershell, taskmgr or tsclient, followed by process execution within
-1m */ sequence by host.id with maxspan=1m [network where event.type
-== "start" and process.name : "svchost.exe" and destination.port ==
-3389 and network.direction : ("incoming", "ingress") and
-network.transport == "tcp" and source.ip != "127.0.0.1" and
-source.ip != "::1" ] [registry where process.name :
-"explorer.exe" and registry.path : ("HKEY_USERS\\*\\Software\\Micro
-soft\\Windows\\CurrentVersion\\Explorer\\RunMRU\\*") and
-registry.data.strings : ("cmd.exe*", "powershell.exe*", "taskmgr*",
-"\\\\tsclient\\*.exe\\*") ] [process where event.type == "start"
-and (process.parent.name : ("cmd.exe", "powershell.exe",
-"taskmgr.exe") or process.args : ("\\\\tsclient\\*.exe")) and not
-process.name : "conhost.exe" ]
+[source, js]
 ----------------------------------
+/* Incoming RDP followed by a new RunMRU string value set to cmd, powershell, taskmgr or tsclient, followed by process execution within 1m */
+
+sequence by host.id with maxspan=1m
+  [network where host.os.type == "windows" and event.type == "start" and process.name : "svchost.exe" and destination.port == 3389 and
+   network.direction : ("incoming", "ingress") and network.transport == "tcp" and
+   source.ip != "127.0.0.1" and source.ip != "::1"
+  ]
 
-==== Threat mapping
+  [registry where host.os.type == "windows" and process.name : "explorer.exe" and
+   registry.path : ("HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\RunMRU\\*") and
+   registry.data.strings : ("cmd.exe*", "powershell.exe*", "taskmgr*", "\\\\tsclient\\*.exe\\*")
+  ]
+
+  [process where host.os.type == "windows" and event.type == "start" and
+   (process.parent.name : ("cmd.exe", "powershell.exe", "taskmgr.exe") or process.args : ("\\\\tsclient\\*.exe")) and
+   not process.name : "conhost.exe"
+   ]
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,79 +78,7 @@ process.name : "conhost.exe" ]
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[potential-sharprdp-behavior-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* Incoming RDP followed by a new RunMRU string value set to cmd,
-powershell, taskmgr or tsclient, followed by process execution within
-1m */ sequence by host.id with maxspan=1m [network where event.type
-== "start" and process.name : "svchost.exe" and destination.port ==
-3389 and network.direction : ("incoming", "ingress") and
-network.transport == "tcp" and source.ip != "127.0.0.1" and
-source.ip != "::1" ] [registry where process.name :
-"explorer.exe" and registry.path : ("HKEY_USERS\\*\\Software\\Micr
-osoft\\Windows\\CurrentVersion\\Explorer\\RunMRU\\*") and
-registry.data.strings : ("cmd.exe*", "powershell.exe*", "taskmgr*",
-"\\\\tsclient\\*.exe\\*") ] [process where event.type in
-("start", "process_started") and (process.parent.name : ("cmd.exe",
-"powershell.exe", "taskmgr.exe") or process.args :
-("\\\\tsclient\\*.exe")) and not process.name : "conhost.exe" ]
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* Incoming RDP followed by a new RunMRU string value set to cmd,
-powershell, taskmgr or tsclient, followed by process execution within
-1m */ sequence by host.id with maxspan=1m [network where event.type
-== "start" and process.name : "svchost.exe" and destination.port ==
-3389 and network.direction : ("incoming", "ingress") and
-network.transport == "tcp" and source.address != "127.0.0.1" and
-source.address != "::1" ] [registry where process.name :
-"explorer.exe" and registry.path : ("HKEY_USERS\\*\\Software\\Micr
-osoft\\Windows\\CurrentVersion\\Explorer\\RunMRU\\*") and
-registry.data.strings : ("cmd.exe*", "powershell.exe*", "taskmgr*",
-"\\\\tsclient\\*.exe\\*") ] [process where event.type in
-("start", "process_started") and (process.parent.name : ("cmd.exe",
-"powershell.exe", "taskmgr.exe") or process.args :
-("\\\\tsclient\\*.exe")) and not process.name : "conhost.exe" ]
-----------------------------------
-
-Version 4 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* Incoming RDP followed by a new RunMRU string value set to cmd,
-powershell, taskmgr or tsclient, followed by process execution within
-1m */ sequence by host.id with maxspan=1m [network where event.type
-== "start" and process.name : "svchost.exe" and destination.port ==
-3389 and network.direction == "incoming" and network.transport ==
-"tcp" and source.address != "127.0.0.1" and source.address != "::1"
-] [registry where process.name : "explorer.exe" and
-registry.path : ("HKEY_USERS\\*\\Software\\Microsoft\\Windows\\Current
-Version\\Explorer\\RunMRU\\*") and registry.data.strings :
-("cmd.exe*", "powershell.exe*", "taskmgr*", "\\\\tsclient\\*.exe\\*")
-] [process where event.type in ("start", "process_started") and
-(process.parent.name : ("cmd.exe", "powershell.exe", "taskmgr.exe") or
-process.args : ("\\\\tsclient\\*.exe")) and not process.name :
-"conhost.exe" ]
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Remote Desktop Protocol
+** ID: T1021.001
+** Reference URL: https://attack.mitre.org/techniques/T1021/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-shell-via-wildcard-injection-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-shell-via-wildcard-injection-detected.asciidoc
new file mode 100644
index 0000000000..b6aa32ff5f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-shell-via-wildcard-injection-detected.asciidoc
@@ -0,0 +1,114 @@
+[[potential-shell-via-wildcard-injection-detected]]
+=== Potential Shell via Wildcard Injection Detected
+
+This rule monitors for the execution of a set of linux binaries, that are potentially vulnerable to wildcard injection, with suspicious command line flags followed by a shell spawn event. Linux wildcard injection is a type of security vulnerability where attackers manipulate commands or input containing wildcards (e.g., *, ?, []) to execute unintended operations or access sensitive data by tricking the system into interpreting the wildcard characters in unexpected ways.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.exploit-db.com/papers/33930
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=1s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and (
+    (process.name == "tar" and process.args : "--checkpoint=*" and process.args : "--checkpoint-action=*") or
+    (process.name == "rsync" and process.args : "-e*") or
+    (process.name == "zip" and process.args == "--unzip-command") )]  by process.entity_id
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+     process.parent.name : ("tar", "rsync", "zip") and 
+     process.name : ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-ssh-it-ssh-worm-downloaded.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-ssh-it-ssh-worm-downloaded.asciidoc
new file mode 100644
index 0000000000..ff7d9a922f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-ssh-it-ssh-worm-downloaded.asciidoc
@@ -0,0 +1,120 @@
+[[potential-ssh-it-ssh-worm-downloaded]]
+=== Potential SSH-IT SSH Worm Downloaded
+
+Identifies processes that are capable of downloading files with command line arguments containing URLs to SSH-IT's autonomous SSH worm. This worm intercepts outgoing SSH connections every time a user uses ssh.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.thc.org/ssh-it/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name in ("curl", "wget") and process.args : (
+  "https://thc.org/ssh-it/x", "http://nossl.segfault.net/ssh-it-deploy.sh", "https://gsocket.io/x",
+  "https://thc.org/ssh-it/bs", "http://nossl.segfault.net/bs"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SSH
+** ID: T1021.004
+** Reference URL: https://attack.mitre.org/techniques/T1021/004/
+* Technique:
+** Name: Remote Service Session Hijacking
+** ID: T1563
+** Reference URL: https://attack.mitre.org/techniques/T1563/
+* Sub-technique:
+** Name: SSH Hijacking
+** ID: T1563.001
+** Reference URL: https://attack.mitre.org/techniques/T1563/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-successful-linux-ftp-brute-force-attack-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-successful-linux-ftp-brute-force-attack-detected.asciidoc
new file mode 100644
index 0000000000..ac8065916c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-successful-linux-ftp-brute-force-attack-detected.asciidoc
@@ -0,0 +1,125 @@
+[[potential-successful-linux-ftp-brute-force-attack-detected]]
+=== Potential Successful Linux FTP Brute Force Attack Detected
+
+An FTP (file transfer protocol) brute force attack is a method where an attacker systematically tries different combinations of usernames and passwords to gain unauthorized access to an FTP server, and if successful, the impact can include unauthorized data access, manipulation, or theft, compromising the security and integrity of the server and potentially exposing sensitive information. This rule identifies multiple consecutive authentication failures targeting a specific user account from the same source address and within a short time interval, followed by a successful authentication.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Auditbeat
+- Auditd Manager
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Auditd Manager Integration Setup*
+
+The Auditd Manager Integration receives audit events from the Linux Audit Framework which is a part of the Linux kernel.
+Auditd Manager provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system.
+
+
+*The following steps should be executed in order to add the Elastic Agent System integration "auditd_manager" on a Linux System:*
+
+- Go to the Kibana home page and click “Add integrations”.
+- In the query bar, search for “Auditd Manager” and select the integration to see more details about it.
+- Click “Add Auditd Manager”.
+- Configure the integration name and optionally add a description.
+- Review optional and advanced settings accordingly.
+- Add the newly installed “auditd manager” to an existing or a new agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+- Click “Save and Continue”.
+- For more details on the integration refer to the https://docs.elastic.co/integrations/auditd_manager[helper guide].
+
+
+*Rule Specific Setup Note*
+
+Auditd Manager subscribes to the kernel and receives events as they occur without any additional configuration.
+However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+- For this detection rule no additional audit rules are required to be added to the integration.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, auditd.data.addr, related.user with maxspan=5s
+  [authentication where host.os.type == "linux" and event.action == "authenticated" and
+   auditd.data.terminal == "ftp" and event.outcome == "failure" and auditd.data.addr != null and
+   auditd.data.addr != "0.0.0.0" and auditd.data.addr != "::"] with runs=10
+  [authentication where host.os.type == "linux" and event.action  == "authenticated" and
+   auditd.data.terminal == "ftp" and event.outcome == "success" and auditd.data.addr != null and
+   auditd.data.addr != "0.0.0.0" and auditd.data.addr != "::"] | tail 1
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Brute Force
+** ID: T1110
+** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Sub-technique:
+** Name: Password Guessing
+** ID: T1110.001
+** Reference URL: https://attack.mitre.org/techniques/T1110/001/
+* Sub-technique:
+** Name: Password Spraying
+** ID: T1110.003
+** Reference URL: https://attack.mitre.org/techniques/T1110/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-successful-linux-rdp-brute-force-attack-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-successful-linux-rdp-brute-force-attack-detected.asciidoc
new file mode 100644
index 0000000000..869628fbed
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-successful-linux-rdp-brute-force-attack-detected.asciidoc
@@ -0,0 +1,123 @@
+[[potential-successful-linux-rdp-brute-force-attack-detected]]
+=== Potential Successful Linux RDP Brute Force Attack Detected
+
+An RDP (Remote Desktop Protocol) brute force attack involves an attacker repeatedly attempting various username and password combinations to gain unauthorized access to a remote computer via RDP, and if successful, the potential impact can include unauthorized control over the compromised system, data theft, or the ability to launch further attacks within the network, jeopardizing the security and confidentiality of the targeted system and potentially compromising the entire network infrastructure. This rule identifies multiple consecutive authentication failures targeting a specific user account within a short time interval, followed by a successful authentication.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Auditbeat
+- Auditd Manager
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Auditd Manager Integration Setup*
+
+The Auditd Manager Integration receives audit events from the Linux Audit Framework which is a part of the Linux kernel.
+Auditd Manager provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system.
+
+
+*The following steps should be executed in order to add the Elastic Agent System integration "auditd_manager" on a Linux System:*
+
+- Go to the Kibana home page and click “Add integrations”.
+- In the query bar, search for “Auditd Manager” and select the integration to see more details about it.
+- Click “Add Auditd Manager”.
+- Configure the integration name and optionally add a description.
+- Review optional and advanced settings accordingly.
+- Add the newly installed “auditd manager” to an existing or a new agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+- Click “Save and Continue”.
+- For more details on the integration refer to the https://docs.elastic.co/integrations/auditd_manager[helper guide].
+
+
+*Rule Specific Setup Note*
+
+Auditd Manager subscribes to the kernel and receives events as they occur without any additional configuration.
+However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+- For this detection rule no additional audit rules are required to be added to the integration.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, related.user with maxspan=5s
+  [authentication where host.os.type == "linux" and event.action == "authenticated" and
+   auditd.data.terminal : "*rdp*" and event.outcome == "failure"] with runs=10
+  [authentication where host.os.type == "linux" and event.action  == "authenticated" and
+   auditd.data.terminal : "*rdp*" and event.outcome == "success"] | tail 1
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Brute Force
+** ID: T1110
+** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Sub-technique:
+** Name: Password Guessing
+** ID: T1110.001
+** Reference URL: https://attack.mitre.org/techniques/T1110/001/
+* Sub-technique:
+** Name: Password Spraying
+** ID: T1110.003
+** Reference URL: https://attack.mitre.org/techniques/T1110/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-successful-ssh-brute-force-attack.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-successful-ssh-brute-force-attack.asciidoc
new file mode 100644
index 0000000000..f52f866a7a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-successful-ssh-brute-force-attack.asciidoc
@@ -0,0 +1,164 @@
+[[potential-successful-ssh-brute-force-attack]]
+=== Potential Successful SSH Brute Force Attack
+
+Identifies multiple SSH login failures followed by a successful one from the same source address. Adversaries can attempt to login into multiple users with a common or known password to gain access to accounts.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* auditbeat-*
+* filebeat-*
+* logs-system.auth-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+
+*Version*: 11
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Successful SSH Brute Force Attack*
+
+
+The rule identifies consecutive SSH login failures followed by a successful login from the same source IP address to the same target host indicating a successful attempt of brute force password guessing.
+
+
+*Possible investigation steps*
+
+
+- Investigate the login failure user name(s).
+- Investigate the source IP address of the failed ssh login attempt(s).
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Identify the source and the target computer and their roles in the IT environment.
+
+
+*False positive analysis*
+
+
+- Authentication misconfiguration or obsolete credentials.
+- Service account password expired.
+- Infrastructure or availability issue.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Ensure active session(s) on the host(s) are terminated as the attacker could have gained initial access to the system(s).
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Auditbeat
+- Filebeat
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Filebeat Setup*
+
+Filebeat is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to Elasticsearch or Logstash for indexing.
+
+
+*The following steps should be executed in order to add the Filebeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html[helper guide].
+- To run Filebeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-docker.html[helper guide].
+- To run Filebeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html[helper guide].
+- For quick start information for Filebeat refer to the https://www.elastic.co/guide/en/beats/filebeat/8.11/filebeat-installation-configuration.html[helper guide].
+- For complete “Setup and Run Filebeat” information refer to the https://www.elastic.co/guide/en/beats/filebeat/current/setting-up-and-running.html[helper guide].
+
+
+*Rule Specific Setup Note*
+
+- This rule requires the “Filebeat System Module” to be enabled.
+- The system module collects and parses logs created by the system logging service of common Unix/Linux based distributions.
+- To run the system module of Filebeat on Linux follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-system.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, source.ip, user.name with maxspan=15s
+  [authentication where host.os.type == "linux" and event.action  in ("ssh_login", "user_login") and
+   event.outcome == "failure" and source.ip != null and source.ip != "0.0.0.0" and source.ip != "::" ] with runs=10
+
+  [authentication where host.os.type == "linux" and event.action  in ("ssh_login", "user_login") and
+   event.outcome == "success" and source.ip != null and source.ip != "0.0.0.0" and source.ip != "::" ]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Brute Force
+** ID: T1110
+** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Sub-technique:
+** Name: Password Guessing
+** ID: T1110.001
+** Reference URL: https://attack.mitre.org/techniques/T1110/001/
+* Sub-technique:
+** Name: Password Spraying
+** ID: T1110.003
+** Reference URL: https://attack.mitre.org/techniques/T1110/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-sudo-hijacking-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-sudo-hijacking-detected.asciidoc
new file mode 100644
index 0000000000..138d360f2a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-sudo-hijacking-detected.asciidoc
@@ -0,0 +1,114 @@
+[[potential-sudo-hijacking-detected]]
+=== Potential Sudo Hijacking Detected
+
+Identifies the creation of a sudo binary located at /usr/bin/sudo. Attackers may hijack the default sudo binary and replace it with a custom binary or script that can read the user's password in clear text to escalate privileges or enable persistence onto the system every time the sudo binary is executed.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://eapolsniper.github.io/2020/08/17/Sudo-Hijacking/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 105
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.category:file and event.type:("creation" or "file_create_event") and
+file.path:("/usr/bin/sudo" or "/bin/sudo") and not process.name:(docker or dockerd or pacman)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Sudo and Sudo Caching
+** ID: T1548.003
+** Reference URL: https://attack.mitre.org/techniques/T1548/003/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-sudo-privilege-escalation-via-cve-2019-14287.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-sudo-privilege-escalation-via-cve-2019-14287.asciidoc
new file mode 100644
index 0000000000..13ed13faf4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-sudo-privilege-escalation-via-cve-2019-14287.asciidoc
@@ -0,0 +1,105 @@
+[[potential-sudo-privilege-escalation-via-cve-2019-14287]]
+=== Potential Sudo Privilege Escalation via CVE-2019-14287
+
+This rule monitors for the execution of a suspicious sudo command that is leveraged in CVE-2019-14287 to escalate privileges to root. Sudo does not verify the presence of the designated user ID and proceeds to execute using a user ID that can be chosen arbitrarily. By using the sudo privileges, the command "sudo -u#-1" translates to an ID of 0, representing the root user. This exploit may work for sudo versions prior to v1.28.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.exploit-db.com/exploits/47502
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+* Use Case: Vulnerability
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "sudo" and process.args == "-u#-1"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-sudo-token-manipulation-via-process-injection.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-sudo-token-manipulation-via-process-injection.asciidoc
new file mode 100644
index 0000000000..d88fd80ba9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-sudo-token-manipulation-via-process-injection.asciidoc
@@ -0,0 +1,114 @@
+[[potential-sudo-token-manipulation-via-process-injection]]
+=== Potential Sudo Token Manipulation via Process Injection
+
+This rule detects potential sudo token manipulation attacks through process injection by monitoring the use of a debugger (gdb) process followed by a successful uid change event during the execution of the sudo process. A sudo token manipulation attack is performed by injecting into a process that has a valid sudo token, which can then be used by attackers to activate their own sudo token. This attack requires ptrace to be enabled in conjunction with the existence of a living process that has a valid sudo token with the same uid as the current user.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/nongiach/sudo_inject
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.session_leader.entity_id with maxspan=15s
+[ process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+  process.name == "gdb" and process.user.id != "0" and process.group.id != "0" ]
+[ process where host.os.type == "linux" and event.action == "uid_change" and event.type == "change" and 
+  process.name == "sudo" and process.user.id == "0" and process.group.id == "0" ]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
+* Sub-technique:
+** Name: Ptrace System Calls
+** ID: T1055.008
+** Reference URL: https://attack.mitre.org/techniques/T1055/008/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Sudo and Sudo Caching
+** ID: T1548.003
+** Reference URL: https://attack.mitre.org/techniques/T1548/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-suspicious-clipboard-activity-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-suspicious-clipboard-activity-detected.asciidoc
new file mode 100644
index 0000000000..80456d56a2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-suspicious-clipboard-activity-detected.asciidoc
@@ -0,0 +1,67 @@
+[[potential-suspicious-clipboard-activity-detected]]
+=== Potential Suspicious Clipboard Activity Detected
+
+This rule monitors for the usage of the most common clipboard utilities on unix systems by an uncommon process group leader. Adversaries may collect data stored in the clipboard from users copying information within or between applications.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Collection
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:"linux" and
+event.type:"start" and event.action:("exec" or "exec_event" or "executed" or "process_started") and
+process.name:("xclip" or "xsel" or "wl-clipboard" or "clipman" or "copyq")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Clipboard Data
+** ID: T1115
+** Reference URL: https://attack.mitre.org/techniques/T1115/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-suspicious-debugfs-root-device-access.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-suspicious-debugfs-root-device-access.asciidoc
new file mode 100644
index 0000000000..cbfa9da64c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-suspicious-debugfs-root-device-access.asciidoc
@@ -0,0 +1,106 @@
+[[potential-suspicious-debugfs-root-device-access]]
+=== Potential Suspicious DebugFS Root Device Access
+
+This rule monitors for the usage of the built-in Linux DebugFS utility to access a disk device without root permissions. Linux users that are part of the "disk" group have sufficient privileges to access all data inside of the machine through DebugFS. Attackers may leverage DebugFS in conjunction with "disk" permissions to read sensitive files owned by root, such as the shadow file, root ssh private keys or other sensitive files that may allow them to further escalate privileges.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://book.hacktricks.xyz/linux-hardening/privilege-escalation/interesting-groups-linux-pe#disk-group
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and 
+process.name == "debugfs" and process.args : "/dev/sd*" and not process.args == "-R" and 
+not user.Ext.real.id == "0" and not group.Ext.real.id == "0"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Local Accounts
+** ID: T1078.003
+** Reference URL: https://attack.mitre.org/techniques/T1078/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-suspicious-file-edit.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-suspicious-file-edit.asciidoc
new file mode 100644
index 0000000000..0d8a2937d4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-suspicious-file-edit.asciidoc
@@ -0,0 +1,112 @@
+[[potential-suspicious-file-edit]]
+=== Potential Suspicious File Edit
+
+This rule monitors for the potential edit of a suspicious file. In Linux, when editing a file through an editor, a temporary .swp file is created. By monitoring for the creation of this .swp file, we can detect potential file edits of suspicious files. The execution of this rule is not a clear sign of the file being edited, as just opening the file through an editor will trigger this event. Attackers may alter any of the files added in this rule to establish persistence, escalate privileges or perform reconnaisance on the system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 1
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where event.action in ("creation", "file_create_event") and file.extension == "swp" and 
+file.path : (
+  /* common interesting files and locations */
+  "/etc/.shadow.swp", "/etc/.shadow-.swp", "/etc/.shadow~.swp", "/etc/.gshadow.swp", "/etc/.gshadow-.swp",
+  "/etc/.passwd.swp", "/etc/.pwd.db.swp", "/etc/.master.passwd.swp", "/etc/.spwd.db.swp", "/etc/security/.opasswd.swp",
+  "/etc/.environment.swp", "/etc/.profile.swp", "/etc/sudoers.d/.*.swp", "/etc/ld.so.conf.d/.*.swp",
+  "/etc/init.d/.*.swp", "/etc/.rc.local.swp", "/etc/rc*.d/.*.swp", "/dev/shm/.*.swp", "/etc/update-motd.d/.*.swp",
+  "/usr/lib/update-notifier/.*.swp",
+
+  /* service, timer, want, socket and lock files */
+  "/etc/systemd/system/.*.swp", "/usr/local/lib/systemd/system/.*.swp", "/lib/systemd/system/.*.swp",
+  "/usr/lib/systemd/system/.*.swp","/home/*/.config/systemd/user/.*.swp", "/run/.*.swp", "/var/run/.*.swp/",
+
+  /* profile and shell configuration files */  
+  "/home/*.profile.swp", "/home/*.bash_profile.swp", "/home/*.bash_login.swp", "/home/*.bashrc.swp", "/home/*.bash_logout.swp",
+  "/home/*.zshrc.swp", "/home/*.zlogin.swp", "/home/*.tcshrc.swp", "/home/*.kshrc.swp", "/home/*.config.fish.swp",
+  "/root/*.profile.swp", "/root/*.bash_profile.swp", "/root/*.bash_login.swp", "/root/*.bashrc.swp", "/root/*.bash_logout.swp",
+  "/root/*.zshrc.swp", "/root/*.zlogin.swp", "/root/*.tcshrc.swp", "/root/*.kshrc.swp", "/root/*.config.fish.swp"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Initialization Scripts
+** ID: T1037
+** Reference URL: https://attack.mitre.org/techniques/T1037/
+* Sub-technique:
+** Name: RC Scripts
+** ID: T1037.004
+** Reference URL: https://attack.mitre.org/techniques/T1037/004/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: Dynamic Linker Hijacking
+** ID: T1574.006
+** Reference URL: https://attack.mitre.org/techniques/T1574/006/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Systemd Service
+** ID: T1543.002
+** Reference URL: https://attack.mitre.org/techniques/T1543/002/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Sudo and Sudo Caching
+** ID: T1548.003
+** Reference URL: https://attack.mitre.org/techniques/T1548/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-syn-based-network-scan-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-syn-based-network-scan-detected.asciidoc
new file mode 100644
index 0000000000..daf19fbfe2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-syn-based-network-scan-detected.asciidoc
@@ -0,0 +1,74 @@
+[[potential-syn-based-network-scan-detected]]
+=== Potential SYN-Based Network Scan Detected
+
+This rule identifies a potential SYN-Based port scan. A SYN port scan is a technique employed by attackers to scan a target network for open ports by sending SYN packets to multiple ports and observing the response. Attackers use this method to identify potential entry points or services that may be vulnerable to exploitation, allowing them to launch targeted attacks or gain unauthorized access to the system or network, compromising its security and potentially leading to data breaches or further malicious activities. This rule proposes threshold logic to check for connection attempts from one source host to 10 or more destination ports using 2 or less packets per port.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* logs-endpoint.events.network-*
+* logs-network_traffic.*
+* packetbeat-*
+* auditbeat-*
+* filebeat-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 5
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Network
+* Tactic: Discovery
+* Tactic: Reconnaissance
+* Use Case: Network Security Monitoring
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+destination.port : * and network.packets <= 2 and source.ip : (10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Network Service Discovery
+** ID: T1046
+** Reference URL: https://attack.mitre.org/techniques/T1046/
+* Tactic:
+** Name: Reconnaissance
+** ID: TA0043
+** Reference URL: https://attack.mitre.org/tactics/TA0043/
+* Technique:
+** Name: Active Scanning
+** ID: T1595
+** Reference URL: https://attack.mitre.org/techniques/T1595/
+* Sub-technique:
+** Name: Scanning IP Blocks
+** ID: T1595.001
+** Reference URL: https://attack.mitre.org/techniques/T1595/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-unauthorized-access-via-wildcard-injection-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-unauthorized-access-via-wildcard-injection-detected.asciidoc
new file mode 100644
index 0000000000..d1bfd9448c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-unauthorized-access-via-wildcard-injection-detected.asciidoc
@@ -0,0 +1,117 @@
+[[potential-unauthorized-access-via-wildcard-injection-detected]]
+=== Potential Unauthorized Access via Wildcard Injection Detected
+
+This rule monitors for the execution of the "chown" and "chmod" commands with command line flags that could indicate a wildcard injection attack. Linux wildcard injection is a type of security vulnerability where attackers manipulate commands or input containing wildcards (e.g., *, ?, []) to execute unintended operations or access sensitive data by tricking the system into interpreting the wildcard characters in unexpected ways.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.exploit-db.com/papers/33930
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name in ("chown", "chmod") and process.args == "-R" and process.args : "--reference=*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: /etc/passwd and /etc/shadow
+** ID: T1003.008
+** Reference URL: https://attack.mitre.org/techniques/T1003/008/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-upgrade-of-non-interactive-shell.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-upgrade-of-non-interactive-shell.asciidoc
new file mode 100644
index 0000000000..efb430c0b4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-upgrade-of-non-interactive-shell.asciidoc
@@ -0,0 +1,106 @@
+[[potential-upgrade-of-non-interactive-shell]]
+=== Potential Upgrade of Non-interactive Shell
+
+Identifies when a non-interactive terminal (tty) is being upgraded to a fully interactive shell. Attackers may upgrade a simple reverse shell to a fully interactive tty after obtaining initial access to a host, in order to obtain a more stable connection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and (
+  (process.name == "stty" and process.args == "raw" and process.args == "-echo" and process.args_count >= 3) or
+  (process.name == "script" and process.args in ("-qc", "-c") and process.args == "/dev/null" and 
+   process.args_count == 4)
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-veeam-credential-access-command.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-veeam-credential-access-command.asciidoc
new file mode 100644
index 0000000000..190aaa57d4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-veeam-credential-access-command.asciidoc
@@ -0,0 +1,88 @@
+[[potential-veeam-credential-access-command]]
+=== Potential Veeam Credential Access Command
+
+Identifies commands that can access and decrypt Veeam credentials stored in MSSQL databases. Attackers can use Veeam Credentials to target backups as part of destructive operations such as Ransomware attacks.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://thedfirreport.com/2021/12/13/diavol-ransomware/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (
+    (process.name : "sqlcmd.exe" or process.pe.original_file_name : "sqlcmd.exe") or
+    process.args : ("Invoke-Sqlcmd", "Invoke-SqlExecute", "Invoke-DbaQuery", "Invoke-SqlQuery")
+  ) and
+  process.args : "*[VeeamBackup].[dbo].[Credentials]*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-widespread-malware-infection-across-multiple-hosts.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-widespread-malware-infection-across-multiple-hosts.asciidoc
new file mode 100644
index 0000000000..5a9672c62c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-widespread-malware-infection-across-multiple-hosts.asciidoc
@@ -0,0 +1,66 @@
+[[potential-widespread-malware-infection-across-multiple-hosts]]
+=== Potential Widespread Malware Infection Across Multiple Hosts
+
+This rule uses alert data to determine when a malware signature is triggered in multiple hosts. Analysts can use this to prioritize triage and response, as this can potentially indicate a widespread malware infection.
+
+*Rule type*: esql
+
+*Rule indices*: None
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/elastic/protections-artifacts/tree/main/yara/rules
+
+*Tags*: 
+
+* Domain: Endpoint
+* Data Source: Elastic Defend
+* Use Case: Threat Detection
+* Tactic: Execution
+* Rule Type: Higher-Order Rule
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+from logs-endpoint.alerts-*
+| where event.code in ("malicious_file", "memory_signature", "shellcode_thread") and rule.name is not null
+| stats hosts = count_distinct(host.id) by rule.name, event.code
+| where hosts >= 3
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: User Execution
+** ID: T1204
+** Reference URL: https://attack.mitre.org/techniques/T1204/
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-windows-error-manager-masquerading.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-windows-error-manager-masquerading.asciidoc
index 147751663d..5fb53415c8 100644
--- a/docs/detections/prebuilt-rules/rule-details/potential-windows-error-manager-masquerading.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/potential-windows-error-manager-masquerading.asciidoc
@@ -5,64 +5,124 @@ Identifies suspicious instances of the Windows Error Reporting process (WerFault
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://twitter.com/SBousseaden/status/1235533224337641473
 * https://www.hexacorn.com/blog/2019/09/20/werfault-command-line-switches-v0-1/
 * https://app.any.run/tasks/26051d84-b68e-4afb-8a9a-76921a271b81/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
 
-*Version*: 100 (<<potential-windows-error-manager-masquerading-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.10.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
+
+
+
+*Investigating Potential Windows Error Manager Masquerading*
+
+
+By examining the specific traits of Windows binaries -- such as process trees, command lines, network connections, registry modifications, and so on -- it's possible to establish a baseline of normal activity. Deviations from this baseline can indicate malicious activity, such as masquerading and deserve further investigation.
+
+This rule identifies a potential malicious process masquerading as `wermgr.exe` or `WerFault.exe`, by looking for a process creation with no arguments followed by a network connection.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Legit Application Crash with rare Werfault commandline value
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan = 5s [process
-where event.type:"start" and process.name : ("wermgr.exe",
-"WerFault.exe") and process.args_count == 1] [network where
-process.name : ("wermgr.exe", "WerFault.exe") and network.protocol !=
-"dns" and network.direction : ("outgoing", "egress") and
-destination.ip !="::1" and destination.ip !="127.0.0.1" ]
+[source, js]
 ----------------------------------
+sequence by host.id, process.entity_id with maxspan = 5s
+  [process where host.os.type == "windows" and event.type:"start" and process.name : ("wermgr.exe", "WerFault.exe") and process.args_count == 1]
+  [network where host.os.type == "windows" and process.name : ("wermgr.exe", "WerFault.exe") and network.protocol != "dns" and
+    network.direction : ("outgoing", "egress") and destination.ip !="::1" and destination.ip !="127.0.0.1"
+  ]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,41 +134,7 @@ destination.ip !="::1" and destination.ip !="127.0.0.1" ]
 ** Name: Masquerading
 ** ID: T1036
 ** Reference URL: https://attack.mitre.org/techniques/T1036/
-
-[[potential-windows-error-manager-masquerading-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan = 5s [process
-where event.type:"start" and process.name : ("wermgr.exe",
-"WerFault.exe") and process.args_count == 1] [network where
-process.name : ("wermgr.exe", "WerFault.exe") and network.protocol !=
-"dns" and network.direction == "outgoing" and destination.ip
-!="::1" and destination.ip !="127.0.0.1" ]
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Rule name changed from: Process Potentially Masquerading as WerFault
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:WerFault.exe and not process.args:((("-u" or "-pss") and
-"-p" and "-s") or ("/h" and "/shared") or ("-k" and "-lcq"))
-----------------------------------
-
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/potential-windows-session-hijacking-via-ccmexec.asciidoc b/docs/detections/prebuilt-rules/rule-details/potential-windows-session-hijacking-via-ccmexec.asciidoc
new file mode 100644
index 0000000000..a7b64e011e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potential-windows-session-hijacking-via-ccmexec.asciidoc
@@ -0,0 +1,63 @@
+[[potential-windows-session-hijacking-via-ccmexec]]
+=== Potential Windows Session Hijacking via CcmExec
+
+This detection rule identifies when 'SCNotification.exe' loads an untrusted DLL, which is a potential indicator of an attacker attempt to hijack/impersonate a Windows user session.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://cloud.google.com/blog/topics/threat-intelligence/windows-session-hijacking-via-ccmexec
+* https://mayfly277.github.io/posts/SCCM-LAB-part0x3/#impersonate-users---revshell-connected-users
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+library where host.os.type == "windows" and process.name : "SCNotification.exe" and
+  (dll.Ext.relative_file_creation_time < 86400 or dll.Ext.relative_file_name_modify_time <= 500) and dll.code_signature.status != "trusted"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
diff --git a/docs/detections/prebuilt-rules/rule-details/potentially-successful-mfa-bombing-via-push-notifications.asciidoc b/docs/detections/prebuilt-rules/rule-details/potentially-successful-mfa-bombing-via-push-notifications.asciidoc
new file mode 100644
index 0000000000..3c853ea541
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potentially-successful-mfa-bombing-via-push-notifications.asciidoc
@@ -0,0 +1,123 @@
+[[potentially-successful-mfa-bombing-via-push-notifications]]
+=== Potentially Successful MFA Bombing via Push Notifications
+
+Detects when an attacker abuses the Multi-Factor authentication mechanism by repeatedly issuing login requests until the user eventually accepts the Okta push notification. An adversary may attempt to bypass the Okta MFA policies configured for an organization to obtain unauthorized access.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.mandiant.com/resources/russian-targeting-gov-business
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+* https://www.rezonate.io/blog/okta-logs-decoded-unveiling-identity-threats-through-threat-hunting/
+
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Tactic: Credential Access
+* Data Source: Okta
+
+*Version*: 209
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Potential Abuse of Repeated MFA Push Notifications*
+
+
+Multi-Factor Authentication (MFA) is an effective method to prevent unauthorized access. However, some adversaries may abuse the system by repeatedly sending MFA push notifications until the user unwittingly approves the access.
+
+This rule detects when a user denies MFA Okta Verify push notifications twice, followed by a successful authentication event within a 10-minute window. This sequence could indicate an adversary's attempt to bypass the Okta MFA policy.
+
+
+*Possible investigation steps:*
+
+
+- Identify the user who received the MFA notifications by reviewing the `user.email` field.
+- Identify the time, source IP, and geographical location of the MFA requests and the subsequent successful login.
+- Review the `event.action` field to understand the nature of the events. It should include two `user.mfa.okta_verify.deny_push` actions and one `user.authentication.sso` action.
+- Ask the user if they remember receiving the MFA notifications and subsequently logging into their account.
+- Check if the MFA requests and the successful login occurred during the user's regular activity hours.
+- Look for any other suspicious activity on the account around the same time.
+- Identify whether the same pattern is repeated for other users in your organization. Multiple users receiving push notifications simultaneously might indicate a larger attack.
+
+
+*False positive analysis:*
+
+
+- Determine if the MFA push notifications were legitimate. Sometimes, users accidentally trigger MFA requests or deny them unintentionally and later approve them.
+- Check if there are known issues with the MFA system causing false denials.
+
+
+*Response and remediation:*
+
+
+- If unauthorized access is confirmed, initiate your incident response process.
+- Alert the user and your IT department immediately.
+- If possible, isolate the user's account until the issue is resolved.
+- Investigate the source of the unauthorized access.
+- If the account was accessed by an unauthorized party, determine the actions they took after logging in.
+- Consider enhancing your MFA policy to prevent such incidents in the future.
+- Encourage users to report any unexpected MFA notifications immediately.
+- Review and update your incident response plans and security policies based on the findings from the incident.
+
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by okta.actor.id with maxspan=10m
+  [authentication where event.dataset == "okta.system" and event.module == "okta"
+    and event.action == "user.mfa.okta_verify.deny_push"] with runs=3
+  [authentication where event.dataset == "okta.system" and event.module == "okta"
+    and (event.action : (
+      "user.authentication.sso",
+      "user.authentication.auth_via_mfa",
+      "user.authentication.verify",
+      "user.session.start") and okta.outcome.result == "SUCCESS")]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Multi-Factor Authentication Request Generation
+** ID: T1621
+** Reference URL: https://attack.mitre.org/techniques/T1621/
diff --git a/docs/detections/prebuilt-rules/rule-details/potentially-suspicious-process-started-via-tmux-or-screen.asciidoc b/docs/detections/prebuilt-rules/rule-details/potentially-suspicious-process-started-via-tmux-or-screen.asciidoc
new file mode 100644
index 0000000000..45f347fa6f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/potentially-suspicious-process-started-via-tmux-or-screen.asciidoc
@@ -0,0 +1,65 @@
+[[potentially-suspicious-process-started-via-tmux-or-screen]]
+=== Potentially Suspicious Process Started via tmux or screen
+
+This rule monitors for the execution of suspicious commands via screen and tmux. When launching a command and detaching directly, the commands will be executed in the background via its parent process. Attackers may leverage screen or tmux to execute commands while attempting to evade detection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and 
+process.parent.name in ("screen", "tmux") and process.name : (
+  "nmap", "nc", "ncat", "netcat", "socat", "nc.openbsd", "ngrok", "ping", "java", "python*", "php*", "perl", "ruby",
+  "lua*", "openssl", "telnet", "awk", "wget", "curl", "id"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-invoke-ninjacopy-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-invoke-ninjacopy-script.asciidoc
new file mode 100644
index 0000000000..298cd07645
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-invoke-ninjacopy-script.asciidoc
@@ -0,0 +1,150 @@
+[[powershell-invoke-ninjacopy-script]]
+=== PowerShell Invoke-NinjaCopy script
+
+Detects PowerShell scripts that contain the default exported functions used on Invoke-NinjaCopy. Attackers can use Invoke-NinjaCopy to read SYSTEM files that are normally locked, such as the NTDS.dit file or registry hives.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/BC-SECURITY/Empire/blob/main/empire/server/data/module_source/collection/Invoke-NinjaCopy.ps1
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: PowerShell Logs
+* Resources: Investigation Guide
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating PowerShell Invoke-NinjaCopy script*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks, making it available for use in various environments, creating an attractive way for attackers to execute code.
+
+Invoke-NinjaCopy is a PowerShell script capable of reading SYSTEM files that were normally locked, such as `NTDS.dit` or sensitive registry locations. It does so by using the direct volume access technique, which enables attackers to bypass access control mechanisms and file system monitoring by reading the raw data directly from the disk and extracting the file by parsing the file system structures.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine file or network events from the involved PowerShell process for suspicious behavior.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Evaluate whether the user needs to use PowerShell to complete tasks.
+- Determine whether the script stores the captured data locally.
+- Check if the imported function was executed and which file it targeted.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    "StealthReadFile" or
+    "StealthReadFileAddr" or
+    "StealthCloseFileDelegate" or
+    "StealthOpenFile" or
+    "StealthCloseFile" or
+    "StealthReadFile" or
+    "Invoke-NinjaCopy"
+   )
+  and not user.id : "S-1-5-18"
+  and not powershell.file.script_block_text : (
+    "sentinelbreakpoints" and "Set-PSBreakpoint" and "PowerSploitIndicators"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: Security Account Manager
+** ID: T1003.002
+** Reference URL: https://attack.mitre.org/techniques/T1003/002/
+* Sub-technique:
+** Name: NTDS
+** ID: T1003.003
+** Reference URL: https://attack.mitre.org/techniques/T1003/003/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Direct Volume Access
+** ID: T1006
+** Reference URL: https://attack.mitre.org/techniques/T1006/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-kerberos-ticket-dump.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-kerberos-ticket-dump.asciidoc
new file mode 100644
index 0000000000..0bf5c81549
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-kerberos-ticket-dump.asciidoc
@@ -0,0 +1,174 @@
+[[powershell-kerberos-ticket-dump]]
+=== PowerShell Kerberos Ticket Dump
+
+Detects PowerShell scripts that have the capability of dumping Kerberos tickets from LSA, which potentially indicates an attacker's attempt to acquire credentials for lateral movement.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/MzHmO/PowershellKerberos/blob/main/dumper.ps1
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: PowerShell Logs
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating PowerShell Kerberos Ticket Dump*
+
+
+Kerberos is an authentication protocol that relies on tickets to grant access to network resources. Adversaries may abuse this protocol to acquire credentials for lateral movement within a network.
+
+This rule indicates the use of scripts that contain code capable of dumping Kerberos tickets, which can indicate potential PowerShell abuse for credential theft.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate if the script was executed, and if so, which account was targeted.
+- Identify the account involved and contact the owner to confirm whether they are aware of this activity.
+- Check if the script has any other functionality that can be potentially malicious.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate other potentially compromised accounts and hosts. Review login events (like 4624) for suspicious events involving the subject and target accounts.
+
+
+*False positive analysis*
+
+
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of file path and user ID conditions.
+
+
+*Related Rules*
+
+
+- PowerShell Kerberos Ticket Request - eb610e70-f9e6-4949-82b9-f1c5bcd37c39
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+  - If malicious activity is confirmed, perform a broader investigation to identify the scope of the compromise and determine the appropriate remediation steps.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Disable or limit involved accounts during the investigation and response.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Reimage the host operating system or restore the compromised files to clean versions.
+- Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    "LsaCallAuthenticationPackage" and
+    (
+      "KerbRetrieveEncodedTicketMessage" or
+      "KerbQueryTicketCacheMessage" or
+      "KerbQueryTicketCacheExMessage" or
+      "KerbQueryTicketCacheEx2Message" or
+      "KerbRetrieveTicketMessage" or
+      "KerbDecryptDataMessage"
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Technique:
+** Name: Steal or Forge Kerberos Tickets
+** ID: T1558
+** Reference URL: https://attack.mitre.org/techniques/T1558/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-kerberos-ticket-request.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-kerberos-ticket-request.asciidoc
index 4089f59ef4..44cc4861ba 100644
--- a/docs/detections/prebuilt-rules/rule-details/powershell-kerberos-ticket-request.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-kerberos-ticket-request.asciidoc
@@ -5,107 +5,131 @@ Detects PowerShell scripts that have the capability of requesting kerberos ticke
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cobalt.io/blog/kerberoast-attack-techniques
 * https://github.com/EmpireProject/Empire/blob/master/data/module_source/credentials/Invoke-Kerberoast.ps1
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
-
-*Version*: 102 (<<powershell-kerberos-ticket-request-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Explicit PowerShell Kerberos Ticket Request
+*Triage and analysis*
+
+
+
+*Investigating PowerShell Kerberos Ticket Request*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks, making it available for use in various environments, creating an attractive way for attackers to execute code.
+
+Accounts associated with a service principal name (SPN) are viable targets for Kerberoasting attacks, which use brute force to crack the user password, which is used to encrypt a Kerberos TGS ticket.
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks, making
-it available for use in various environments, creating an attractive way for attackers to execute code.
+Attackers can use PowerShell to request these Kerberos tickets, with the intent of extracting them from memory to perform Kerberoasting.
 
-Accounts associated with a service principal name (SPN) are viable targets for Kerberoasting attacks, which use brute
-force to crack the user password, which is used to encrypt a Kerberos TGS ticket.
 
-Attackers can use PowerShell to request these Kerberos tickets, with the intent of extracting them from memory to
-perform Kerberoasting.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate if the script was executed, and if so, which account was targeted.
 - Validate if the account has an SPN associated with it.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Check if the script has any other functionality that can be potentially malicious.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Review event ID [4769](https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4769)
-related to this account and service name for additional information.
+- Review event ID https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4769[4769] related to this account and service name for additional information.
 
-### False positive analysis
 
-- A possible false positive can be identified if the script content is not malicious/harmful or does not request
-Kerberos tickets for user accounts, as computer accounts are not vulnerable to Kerberoasting due to complex password
-requirements and policy.
+*False positive analysis*
+
+
+- A possible false positive can be identified if the script content is not malicious/harmful or does not request Kerberos tickets for user accounts, as computer accounts are not vulnerable to Kerberoasting due to complex password requirements and policy.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services. Prioritize privileged accounts.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services. Prioritize privileged accounts.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-KerberosRequestorSecurityToken )
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    KerberosRequestorSecurityToken
+  ) and not user.id : ("S-1-5-18" or "S-1-5-20") and
+  not powershell.file.script_block_text : (
+    ("sentinelbreakpoints" and ("Set-PSBreakpoint" or "Set-HookFunctionTabs")) or
+    ("function global" and "\\windows\\sentinel\\4")
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -117,8 +141,14 @@ KerberosRequestorSecurityToken )
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-
+* Technique:
+** Name: Steal or Forge Kerberos Tickets
+** ID: T1558
+** Reference URL: https://attack.mitre.org/techniques/T1558/
+* Sub-technique:
+** Name: Kerberoasting
+** ID: T1558.003
+** Reference URL: https://attack.mitre.org/techniques/T1558/003/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -127,28 +157,7 @@ KerberosRequestorSecurityToken )
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[powershell-kerberos-ticket-request-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-KerberosRequestorSecurityToken )
-----------------------------------
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-keylogging-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-keylogging-script.asciidoc
index 194e37370f..7e9e40ce21 100644
--- a/docs/detections/prebuilt-rules/rule-details/powershell-keylogging-script.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-keylogging-script.asciidoc
@@ -5,114 +5,140 @@ Detects the use of Win32 API Functions that can be used to capture user keystrok
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
-*Severity*: high
+*Severity*: medium
 
-*Risk score*: 73
+*Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/EmpireProject/Empire/blob/master/data/module_source/collection/Get-Keystrokes.ps1
 * https://github.com/MojtabaTajik/FunnyKeylogger/blob/master/FunnyLogger.ps1
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Collection
-* Investigation Guide
-
-*Version*: 102 (<<powershell-keylogging-script-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating PowerShell Keylogging Script
+*Triage and analysis*
+
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This
-makes it available for use in various environments, and creates an attractive way for attackers to execute code.
 
-Attackers can abuse PowerShell capabilities to capture user keystrokes with the goal of stealing credentials and other
-valuable information as credit card data and confidential conversations.
+*Investigating PowerShell Keylogging Script*
 
-#### Possible investigation steps
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+Attackers can abuse PowerShell capabilities to capture user keystrokes with the goal of stealing credentials and other valuable information as credit card data and confidential conversations.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Examine file or network events from the involved PowerShell process for suspicious behavior.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
-- Investigate if the script stores the captured data locally.
-- Investigate if the script contains exfiltration capabilities and the destination of this exfiltration.
+- Determine whether the script stores the captured data locally.
+- Investigate whether the script contains exfiltration capabilities and identify the exfiltration server.
 - Assess network data to determine if the host communicated with the exfiltration server.
 
-### False positive analysis
 
-- Regular users do not have a business justification for using scripting utilities to capture keystrokes, making
-false positives unlikely. In the case of authorized benign true positives (B-TPs), exceptions can be added.
+*False positive analysis*
+
+
+- Regular users do not have a business justification for using scripting utilities to capture keystrokes, making false positives unlikely. In the case of authorized benign true positives (B-TPs), exceptions can be added.
+
+
+*Related rules*
 
-### Related rules
 
 - PowerShell PSReflect Script - 56f2e9b5-4803-4e44-a0a4-a52dc79d57fe
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- The response must be prioritized if this alert involves key executives or potentially valuable targets for espionage.
+- Prioritize the response if this alert involves key executives or potentially valuable targets for espionage.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and ( powershell.file.script_block_text :
-(GetAsyncKeyState or NtUserGetAsyncKeyState or GetKeyboardState or
-"Get-Keystrokes") or powershell.file.script_block_text : (
-(SetWindowsHookA or SetWindowsHookW or SetWindowsHookEx or
-SetWindowsHookExA or NtUserSetWindowsHookEx) and
-(GetForegroundWindow or GetWindowTextA or GetWindowTextW or
-"WM_KEYBOARD_LL") ) )
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and
+  (
+   powershell.file.script_block_text : (GetAsyncKeyState or NtUserGetAsyncKeyState or GetKeyboardState or "Get-Keystrokes") or
+   powershell.file.script_block_text : (
+        (SetWindowsHookA or SetWindowsHookW or SetWindowsHookEx or SetWindowsHookExA or NtUserSetWindowsHookEx) and
+        (GetForegroundWindow or GetWindowTextA or GetWindowTextW or "WM_KEYBOARD_LL" or "WH_MOUSE_LL")
+   )
+   ) and not user.id : "S-1-5-18"
+  and not powershell.file.script_block_text : (
+    "sentinelbreakpoints" and "Set-PSBreakpoint"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -124,8 +150,10 @@ SetWindowsHookExA or NtUserSetWindowsHookEx) and
 ** Name: Input Capture
 ** ID: T1056
 ** Reference URL: https://attack.mitre.org/techniques/T1056/
-
-
+* Sub-technique:
+** Name: Keylogging
+** ID: T1056.001
+** Reference URL: https://attack.mitre.org/techniques/T1056/001/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -134,46 +162,11 @@ SetWindowsHookExA or NtUserSetWindowsHookEx) and
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[powershell-keylogging-script-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and ( powershell.file.script_block_text
-: (GetAsyncKeyState or NtUserGetAsyncKeyState or GetKeyboardState or
-"Get-Keystrokes") or powershell.file.script_block_text : (
-(SetWindowsHookA or SetWindowsHookW or SetWindowsHookEx or
-SetWindowsHookExA or NtUserSetWindowsHookEx) and
-(GetForegroundWindow or GetWindowTextA or GetWindowTextW or
-"WM_KEYBOARD_LL") ) )
-----------------------------------
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and ( powershell.file.script_block_text
-: (GetAsyncKeyState or NtUserGetAsyncKeyState or GetKeyboardState or
-Get-Keystrokes) or powershell.file.script_block_text :
-((SetWindowsHookA or SetWindowsHookW or SetWindowsHookEx or
-SetWindowsHookExA or NtUserSetWindowsHookEx) and (GetForegroundWindow
-or GetWindowTextA or GetWindowTextW or WM_KEYBOARD_LL)) )
-----------------------------------
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Technique:
+** Name: Native API
+** ID: T1106
+** Reference URL: https://attack.mitre.org/techniques/T1106/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-mailbox-collection-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-mailbox-collection-script.asciidoc
new file mode 100644
index 0000000000..a9383eaf84
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-mailbox-collection-script.asciidoc
@@ -0,0 +1,174 @@
+[[powershell-mailbox-collection-script]]
+=== PowerShell Mailbox Collection Script
+
+Detects PowerShell scripts that can be used to collect data from mailboxes. Adversaries may target user email to collect sensitive information.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/dafthack/MailSniper/blob/master/MailSniper.ps1
+* https://github.com/center-for-threat-informed-defense/adversary_emulation_library/blob/master/apt29/Archive/CALDERA_DIY/evals/payloads/stepSeventeen_email.ps1
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Data Source: PowerShell Logs
+* Resources: Investigation Guide
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating PowerShell Mailbox Collection Script*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+Email mailboxes and their information can be valuable assets for attackers. Company mailboxes often contain sensitive information such as login credentials, intellectual property, financial data, and personal information, making them high-value targets for malicious actors.
+
+This rule identifies scripts that contains methods and classes that can be abused to collect emails from local and remote mailboxes.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Determine whether the script was executed and capture relevant information, such as arguments that reveal intent or are indicators of compromise (IoCs).
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Evaluate whether the user needs to use PowerShell to complete tasks.
+- Determine whether the script stores the captured data locally.
+- Investigate whether the script contains exfiltration capabilities and identify the exfiltration server.
+  - Assess network data to determine if the host communicated with the exfiltration server.
+
+
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity and it is done with proper approval.
+
+
+*Related rules*
+
+
+- Exporting Exchange Mailbox via PowerShell - 6aace640-e631-4870-ba8e-5fdda09325db
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- If the involved host is not the Exchange server, isolate the host to prevent further post-compromise behavior.
+- Prioritize cases that involve personally identifiable information (PII) or other classified data.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  (
+   powershell.file.script_block_text : (
+      "Microsoft.Office.Interop.Outlook" or
+      "Interop.Outlook.olDefaultFolders" or
+      "::olFolderInBox"
+   ) or
+   powershell.file.script_block_text : (
+      "Microsoft.Exchange.WebServices.Data.Folder" or
+      "Microsoft.Exchange.WebServices.Data.FileAttachment"
+   )
+  ) and not user.id : "S-1-5-18"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Email Collection
+** ID: T1114
+** Reference URL: https://attack.mitre.org/techniques/T1114/
+* Sub-technique:
+** Name: Local Email Collection
+** ID: T1114.001
+** Reference URL: https://attack.mitre.org/techniques/T1114/001/
+* Sub-technique:
+** Name: Remote Email Collection
+** ID: T1114.002
+** Reference URL: https://attack.mitre.org/techniques/T1114/002/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-minidump-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-minidump-script.asciidoc
index 810dc6aaf0..b8270354fb 100644
--- a/docs/detections/prebuilt-rules/rule-details/powershell-minidump-script.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-minidump-script.asciidoc
@@ -5,113 +5,129 @@ This rule detects PowerShell scripts capable of dumping process memory using Win
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/PowerShellMafia/PowerSploit/blob/master/Exfiltration/Out-Minidump.ps1
 * https://github.com/FuzzySecurity/PowerShell-Suite/blob/master/Get-ProcessMiniDump.ps1
 * https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0109_windows_powershell_script_block_log.md
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
+
+*Version*: 108
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
 
-*Version*: 102 (<<powershell-minidump-script-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.16.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-PowerShell scripts that use this capability for troubleshooting.
 
-==== Investigation guide
 
+*Investigating PowerShell MiniDump Script*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating PowerShell MiniDump Script
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+Attackers can abuse Process Memory Dump capabilities to extract credentials from LSASS or to obtain other privileged information stored in the process memory.
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This
-makes it available for use in various environments, and creates an attractive way for attackers to execute code.
 
-Attackers can abuse Process Memory Dump capabilities to extract credentials from LSASS or to obtain other
-privileged information stored in the process memory.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Examine file or network events from the involved PowerShell process for suspicious behavior.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
 - Check if the imported function was executed and which process it targeted.
 
-### False positive analysis
 
-- Regular users do not have a business justification for using scripting utilities to dump process memory, making false
-positives unlikely.
+*False positive analysis*
+
+
+- Regular users do not have a business justification for using scripting utilities to dump process memory, making false positives unlikely.
+
+
+*Related rules*
 
-### Related rules
 
 - PowerShell PSReflect Script - 56f2e9b5-4803-4e44-a0a4-a52dc79d57fe
 - Potential Process Injection via PowerShell - 2e29e96a-b67c-455a-afe4-de6183431d0d
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and
-powershell.file.script_block_text:(MiniDumpWriteDump or
-MiniDumpWithFullMemory or pmuDetirWpmuDiniM)
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and powershell.file.script_block_text:(MiniDumpWriteDump or MiniDumpWithFullMemory or pmuDetirWpmuDiniM) and not user.id : "S-1-5-18"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -123,8 +139,10 @@ MiniDumpWithFullMemory or pmuDetirWpmuDiniM)
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -133,35 +151,7 @@ MiniDumpWithFullMemory or pmuDetirWpmuDiniM)
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[powershell-minidump-script-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.3.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 3 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.code:"4104" and
-powershell.file.script_block_text:(MiniDumpWriteDump or
-MiniDumpWithFullMemory or pmuDetirWpmuDiniM)
-----------------------------------
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-psreflect-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-psreflect-script.asciidoc
index 4110966dcc..580759a198 100644
--- a/docs/detections/prebuilt-rules/rule-details/powershell-psreflect-script.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-psreflect-script.asciidoc
@@ -5,106 +5,99 @@ Detects the use of PSReflect in PowerShell scripts. Attackers leverage PSReflect
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/mattifestation/PSReflect/blob/master/PSReflect.psm1
 * https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0109_windows_powershell_script_block_log.md
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Investigation Guide
-
-*Version*: 102 (<<powershell-psreflect-script-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 210
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Legitimate PowerShell scripts that make use of PSReflect to access the win32 API
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating PowerShell PSReflect Script
+*Triage and analysis*
+
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This
-makes it available for use in various environments, and creates an attractive way for attackers to execute code.
 
-PSReflect is a library that enables PowerShell to access win32 API functions in an uncomplicated way. It also helps to
-create enums and structs easily—all without touching the disk.
+*Investigating PowerShell PSReflect Script*
 
-Although this is an interesting project for every developer and admin out there, it is mainly used in the red team and
-malware tooling for its capabilities.
 
-Detecting the core implementation of PSReflect means detecting most of the tooling that uses Windows API through
-PowerShell, enabling defenders to discover tools being dropped in the environment.
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+PSReflect is a library that enables PowerShell to access win32 API functions in an uncomplicated way. It also helps to create enums and structs easily—all without touching the disk.
+
+Although this is an interesting project for every developer and admin out there, it is mainly used in the red team and malware tooling for its capabilities.
+
+Detecting the core implementation of PSReflect means detecting most of the tooling that uses Windows API through PowerShell, enabling defenders to discover tools being dropped in the environment.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-#### Possible investigation steps
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics. The
-script content that may be split into multiple script blocks (you can use the field `powershell.file.script_block_id`
-for filtering).
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics. The script content that may be split into multiple script blocks (you can use the field `powershell.file.script_block_id` for filtering).
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Check for additional PowerShell and command-line logs that indicate that imported functions were run.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the script using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Related rules
+
+*Related rules*
+
 
 - PowerShell Suspicious Discovery Related Windows API Functions - 61ac3638-40a3-44b2-855a-985636ca985e
 - PowerShell Keylogging Script - bd2c86a0-8b61-4457-ab38-96943984e889
@@ -114,7 +107,9 @@ prevalence, whether they are located in expected locations, and if they are sign
 - PowerShell Suspicious Payload Encoded and Compressed - 81fe9dc6-a2d7-4192-a2d8-eed98afc766a
 - PowerShell Suspicious Script with Screenshot Capabilities - 959a7353-1129-4aa7-9084-30746b256a70
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
@@ -122,82 +117,75 @@ prevalence, whether they are located in expected locations, and if they are sign
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
-==== Rule query
+==== Setup
 
 
-[source,js]
-----------------------------------
-event.category:process and powershell.file.script_block_text:(
-"New-InMemoryModule" or "Add-Win32Type" or psenum or
-DefineDynamicAssembly or DefineDynamicModule or
-"Reflection.TypeAttributes" or "Reflection.Emit.OpCodes" or
-"Reflection.Emit.CustomAttributeBuilder" or
-"Runtime.InteropServices.DllImportAttribute" )
-----------------------------------
 
-==== Threat mapping
+*Setup*
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Execution
-** ID: TA0002
-** Reference URL: https://attack.mitre.org/tactics/TA0002/
-* Technique:
-** Name: Command and Scripting Interpreter
-** ID: T1059
-** Reference URL: https://attack.mitre.org/techniques/T1059/
+The 'PowerShell Script Block Logging' logging policy must be configured (Enable).
 
-[[powershell-psreflect-script-history]]
-==== Rule version history
+Steps to implement the logging policy with Advanced Audit Configuration:
 
-Version 102 (8.6.0 release)::
-* Formatting only
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
 
-Version 101 (8.5.0 release)::
-* Formatting only
+Steps to implement the logging policy via registry:
 
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and powershell.file.script_block_text:(
-"New-InMemoryModule" or "Add-Win32Type" or psenum or
-DefineDynamicAssembly or DefineDynamicModule or
-"Reflection.TypeAttributes" or "Reflection.Emit.OpCodes" or
-"Reflection.Emit.CustomAttributeBuilder" or
-"Runtime.InteropServices.DllImportAttribute" )
-----------------------------------
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
 
-Version 4 (8.3.0 release)::
-* Formatting only
 
-Version 3 (8.2.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.category:process and powershell.file.script_block_text:(
-New-InMemoryModule or Add-Win32Type or psenum or
-DefineDynamicAssembly or DefineDynamicModule or
-Reflection.TypeAttributes or Reflection.Emit.OpCodes or
-Reflection.Emit.CustomAttributeBuilder or
-Runtime.InteropServices.DllImportAttribute )
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text:(
+    "New-InMemoryModule" or
+    "Add-Win32Type" or
+    psenum or
+    DefineDynamicAssembly or
+    DefineDynamicModule or
+    "Reflection.TypeAttributes" or
+    "Reflection.Emit.OpCodes" or
+    "Reflection.Emit.CustomAttributeBuilder" or
+    "Runtime.InteropServices.DllImportAttribute"
+  ) and
+  not user.id : "S-1-5-18"
+
 ----------------------------------
 
-Version 2 (8.1.0 release)::
-* Formatting only
+*Framework*: MITRE ATT&CK^TM^
 
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Technique:
+** Name: Native API
+** ID: T1106
+** Reference URL: https://attack.mitre.org/techniques/T1106/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-script-block-logging-disabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-script-block-logging-disabled.asciidoc
index de06aad999..a7b919fc59 100644
--- a/docs/detections/prebuilt-rules/rule-details/powershell-script-block-logging-disabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-script-block-logging-disabled.asciidoc
@@ -5,76 +5,81 @@ Identifies attempts to disable PowerShell Script Block Logging via registry modi
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.PowerShell::EnableScriptBlockLogging
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<powershell-script-block-logging-disabled-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating PowerShell Script Block Logging Disabled
+*Triage and analysis*
+
+
+
+*Investigating PowerShell Script Block Logging Disabled*
+
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks, making
-it available in various environments and creating an attractive way for attackers to execute code.
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks, making it available in various environments and creating an attractive way for attackers to execute code.
 
-PowerShell Script Block Logging is a feature of PowerShell that records the content of all script blocks that it
-processes, giving defenders visibility of PowerShell scripts and sequences of executed commands.
+PowerShell Script Block Logging is a feature of PowerShell that records the content of all script blocks that it processes, giving defenders visibility of PowerShell scripts and sequences of executed commands.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Check whether it makes sense for the user to use PowerShell to complete tasks.
 - Investigate if PowerShell scripts were run after logging was disabled.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Related rules
+
+*Related rules*
+
 
 - PowerShell Suspicious Discovery Related Windows API Functions - 61ac3638-40a3-44b2-855a-985636ca985e
 - PowerShell Keylogging Script - bd2c86a0-8b61-4457-ab38-96943984e889
@@ -84,34 +89,31 @@ for prevalence, whether they are located in expected locations, and if they are
 - PowerShell Suspicious Payload Encoded and Compressed - 81fe9dc6-a2d7-4192-a2d8-eed98afc766a
 - PowerShell Suspicious Script with Screenshot Capabilities - 959a7353-1129-4aa7-9084-30746b256a70
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type == "change" and registry.path : (
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\PowerShell\\ScriptBlock
-Logging\\EnableScriptBlockLogging", "\\REGISTRY\\MACHINE\\SOFT
-WARE\\Policies\\Microsoft\\Windows\\PowerShell\\ScriptBlockLogging\\En
-ableScriptBlockLogging" ) and registry.data.strings : ("0",
-"0x00000000")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type == "change" and
+    registry.path : (
+        "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\PowerShell\\ScriptBlockLogging\\EnableScriptBlockLogging",
+        "\\REGISTRY\\MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\PowerShell\\ScriptBlockLogging\\EnableScriptBlockLogging"
+    ) and registry.data.strings : ("0", "0x00000000")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -123,38 +125,11 @@ ableScriptBlockLogging" ) and registry.data.strings : ("0",
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[powershell-script-block-logging-disabled-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type == "change" and registry.path : 
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\PowerShell\\ScriptBlock
-Logging\\EnableScriptBlockLogging" and registry.data.strings :
-("0", "0x00000000")
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type == "change" and registry.path :
-"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\PowerShell\\ScriptBlock
-Logging\\EnableScriptBlockLogging" and registry.data.strings :
-("0", "0x00000000")
-----------------------------------
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable Windows Event Logging
+** ID: T1562.002
+** Reference URL: https://attack.mitre.org/techniques/T1562/002/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-script-with-archive-compression-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-archive-compression-capabilities.asciidoc
new file mode 100644
index 0000000000..b762f42557
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-archive-compression-capabilities.asciidoc
@@ -0,0 +1,114 @@
+[[powershell-script-with-archive-compression-capabilities]]
+=== PowerShell Script with Archive Compression Capabilities
+
+Identifies the use of Cmdlets and methods related to archive compression activities. Adversaries will often compress and encrypt data in preparation for exfiltration.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Data Source: PowerShell Logs
+* Rule Type: BBR
+
+*Version*: 105
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+(
+  powershell.file.script_block_text : (
+    "IO.Compression.ZipFile" or
+    "IO.Compression.ZipArchive" or
+    "ZipFile.CreateFromDirectory" or
+    "IO.Compression.BrotliStream" or
+    "IO.Compression.DeflateStream" or
+    "IO.Compression.GZipStream" or
+    "IO.Compression.ZLibStream"
+  ) and 
+  powershell.file.script_block_text : (
+    "CompressionLevel" or
+    "CompressionMode" or
+    "ZipArchiveMode"
+  ) or
+  powershell.file.script_block_text : "Compress-Archive"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Archive Collected Data
+** ID: T1560
+** Reference URL: https://attack.mitre.org/techniques/T1560/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-script-with-discovery-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-discovery-capabilities.asciidoc
new file mode 100644
index 0000000000..349cbca1ee
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-discovery-capabilities.asciidoc
@@ -0,0 +1,250 @@
+[[powershell-script-with-discovery-capabilities]]
+=== PowerShell Script with Discovery Capabilities
+
+Identifies the use of Cmdlets and methods related to discovery activities. Attackers can use these to perform various situational awareness related activities, like enumerating users, shares, sessions, domain trusts, groups, etc.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Tactic: Discovery
+* Data Source: PowerShell Logs
+* Rule Type: BBR
+
+*Version*: 107
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    (
+      "Get-ADDefaultDomainPasswordPolicy" or
+      "Get-ADDomain" or "Get-ComputerInfo" or
+      "Get-Disk" or "Get-DnsClientCache" or
+      "Get-GPOReport" or "Get-HotFix" or
+      "Get-LocalUser" or "Get-NetFirewallProfile" or
+      "get-nettcpconnection" or "Get-NetAdapter" or
+      "Get-PhysicalDisk" or "Get-Process" or
+      "Get-PSDrive" or "Get-Service" or
+      "Get-SmbShare" or "Get-WinEvent"
+    ) or
+    (
+      ("Get-WmiObject" or "gwmi" or "Get-CimInstance" or
+       "gcim" or "Management.ManagementObjectSearcher" or
+       "System.Management.ManagementClass" or
+       "[WmiClass]" or "[WMI]") and
+      (
+        "AntiVirusProduct" or "CIM_BIOSElement" or "CIM_ComputerSystem" or "CIM_Product" or "CIM_DiskDrive" or
+        "CIM_LogicalDisk" or "CIM_NetworkAdapter" or "CIM_StorageVolume" or "CIM_OperatingSystem" or
+        "CIM_Process" or "CIM_Service" or "MSFT_DNSClientCache" or "Win32_BIOS" or "Win32_ComputerSystem" or
+        "Win32_ComputerSystemProduct" or "Win32_DiskDrive" or "win32_environment" or "Win32_Group" or
+        "Win32_groupuser" or "Win32_IP4RouteTable" or "Win32_logicaldisk" or "Win32_MappedLogicalDisk" or
+        "Win32_NetworkAdapterConfiguration" or "win32_ntdomain" or "Win32_OperatingSystem" or
+        "Win32_PnPEntity" or "Win32_Process" or "Win32_Product" or "Win32_quickfixengineering" or
+        "win32_service" or "Win32_Share" or "Win32_UserAccount"
+      )
+    ) or
+    (
+      ("ADSI" and "WinNT") or
+      ("Get-ChildItem" and "sysmondrv.sys") or
+      ("::GetIPGlobalProperties()" and "GetActiveTcpConnections()") or
+      ("ServiceProcess.ServiceController" and "::GetServices") or
+      ("Diagnostics.Process" and "::GetProcesses") or
+      ("DirectoryServices.Protocols.GroupPolicy" and ".GetGPOReport()") or
+      ("DirectoryServices.AccountManagement" and "PrincipalSearcher") or
+      ("NetFwTypeLib.NetFwMgr" and "CurrentProfile") or
+      ("NetworkInformation.NetworkInterface" and "GetAllNetworkInterfaces") or
+      ("Automation.PSDriveInfo") or
+      ("Microsoft.Win32.RegistryHive")
+    ) or
+    (
+      "Get-ItemProperty" and
+      (
+        "\Control\SecurityProviders\WDigest" or
+        "\microsoft\windows\currentversion\explorer\runmru" or
+        "\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters" or
+        "\Microsoft\Windows\CurrentVersion\Uninstall" or
+        "\Microsoft\Windows\WindowsUpdate" or
+        "Policies\Microsoft\Windows\Installer" or
+        "Software\Microsoft\Windows\CurrentVersion\Policies" or
+        ("\Services\SharedAccess\Parameters\FirewallPolicy" and "EnableFirewall") or
+        ("Microsoft\Windows\CurrentVersion\Internet Settings" and "proxyEnable")
+      )
+    ) or
+    (
+      ("Directoryservices.Activedirectory" or
+      "DirectoryServices.AccountManagement") and 
+      (
+        "Domain Admins" or "DomainControllers" or
+        "FindAllGlobalCatalogs" or "GetAllTrustRelationships" or
+        "GetCurrentDomain" or "GetCurrentForest"
+      ) or
+      "DirectoryServices.DirectorySearcher" and
+      (
+        "samAccountType=805306368" or
+        "samAccountType=805306369" or
+        "objectCategory=group" or
+        "objectCategory=groupPolicyContainer" or
+        "objectCategory=site" or
+        "objectCategory=subnet" or
+        "objectClass=trustedDomain"
+      )
+    ) or
+    (
+      "Get-Process" and
+      (
+        "mcshield" or "windefend" or "savservice" or
+        "TMCCSF" or "symantec antivirus" or
+        "CSFalcon" or "TmPfw" or "kvoop"
+      )
+    )
+  ) and
+  not powershell.file.script_block_text : (
+    (
+      "__cmdletization_BindCommonParameters" and
+      "Microsoft.PowerShell.Core\Export-ModuleMember" and
+      "Microsoft.PowerShell.Cmdletization.Cim.CimCmdletAdapter"
+    ) or
+    "CmdletsToExport=@(\"Add-Content\","
+  ) and
+  not user.id : ("S-1-5-18" or "S-1-5-19" or "S-1-5-20")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Account Discovery
+** ID: T1087
+** Reference URL: https://attack.mitre.org/techniques/T1087/
+* Sub-technique:
+** Name: Local Account
+** ID: T1087.001
+** Reference URL: https://attack.mitre.org/techniques/T1087/001/
+* Sub-technique:
+** Name: Domain Account
+** ID: T1087.002
+** Reference URL: https://attack.mitre.org/techniques/T1087/002/
+* Technique:
+** Name: Domain Trust Discovery
+** ID: T1482
+** Reference URL: https://attack.mitre.org/techniques/T1482/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
+* Technique:
+** Name: File and Directory Discovery
+** ID: T1083
+** Reference URL: https://attack.mitre.org/techniques/T1083/
+* Technique:
+** Name: Group Policy Discovery
+** ID: T1615
+** Reference URL: https://attack.mitre.org/techniques/T1615/
+* Technique:
+** Name: Network Share Discovery
+** ID: T1135
+** Reference URL: https://attack.mitre.org/techniques/T1135/
+* Technique:
+** Name: Password Policy Discovery
+** ID: T1201
+** Reference URL: https://attack.mitre.org/techniques/T1201/
+* Technique:
+** Name: Process Discovery
+** ID: T1057
+** Reference URL: https://attack.mitre.org/techniques/T1057/
+* Technique:
+** Name: Software Discovery
+** ID: T1518
+** Reference URL: https://attack.mitre.org/techniques/T1518/
+* Sub-technique:
+** Name: Security Software Discovery
+** ID: T1518.001
+** Reference URL: https://attack.mitre.org/techniques/T1518/001/
+* Technique:
+** Name: Query Registry
+** ID: T1012
+** Reference URL: https://attack.mitre.org/techniques/T1012/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
+* Technique:
+** Name: System Network Connections Discovery
+** ID: T1049
+** Reference URL: https://attack.mitre.org/techniques/T1049/
+* Technique:
+** Name: System Service Discovery
+** ID: T1007
+** Reference URL: https://attack.mitre.org/techniques/T1007/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-script-with-encryption-decryption-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-encryption-decryption-capabilities.asciidoc
new file mode 100644
index 0000000000..d2857b7798
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-encryption-decryption-capabilities.asciidoc
@@ -0,0 +1,129 @@
+[[powershell-script-with-encryption-decryption-capabilities]]
+=== PowerShell Script with Encryption/Decryption Capabilities
+
+Identifies the use of Cmdlets and methods related to encryption/decryption of files in PowerShell scripts, which malware and offensive security tools can abuse to encrypt data or decrypt payloads to bypass security solutions.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: PowerShell Logs
+* Resources: Investigation Guide
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating PowerShell Script with Encryption/Decryption Capabilities*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks, making it available for use in various environments, creating an attractive way for attackers to execute code.
+
+PowerShell offers encryption and decryption functionalities that attackers can abuse for various purposes, such as concealing payloads, C2 communications, and encrypting data as part of ransomware operations.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine file or network events from the involved PowerShell process for suspicious behavior.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Evaluate whether the user needs to use PowerShell to complete tasks.
+
+
+*False positive analysis*
+
+
+- This is a dual-use mechanism, meaning its usage is not inherently malicious. Analysts can dismiss the alert if the script doesn't contain malicious functions or potential for abuse, no other suspicious activity was identified, and there are justifications for the execution.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    (
+      "Cryptography.AESManaged" or
+      "Cryptography.RijndaelManaged" or
+      "Cryptography.SHA1Managed" or
+      "Cryptography.SHA256Managed" or
+      "Cryptography.SHA384Managed" or
+      "Cryptography.SHA512Managed" or
+      "Cryptography.SymmetricAlgorithm" or
+      "PasswordDeriveBytes" or
+      "Rfc2898DeriveBytes"
+    ) and
+    (
+      CipherMode and PaddingMode
+    ) and
+    (
+      ".CreateEncryptor" or
+      ".CreateDecryptor"
+    )
+  ) and not user.id : "S-1-5-18"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Obfuscated Files or Information
+** ID: T1027
+** Reference URL: https://attack.mitre.org/techniques/T1027/
+* Technique:
+** Name: Deobfuscate/Decode Files or Information
+** ID: T1140
+** Reference URL: https://attack.mitre.org/techniques/T1140/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-script-with-log-clear-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-log-clear-capabilities.asciidoc
new file mode 100644
index 0000000000..6e45171ad2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-log-clear-capabilities.asciidoc
@@ -0,0 +1,113 @@
+[[powershell-script-with-log-clear-capabilities]]
+=== PowerShell Script with Log Clear Capabilities
+
+Identifies the use of Cmdlets and methods related to Windows event log deletion activities. This is often done by attackers in an attempt to evade detection or destroy forensic evidence on a system.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.eventlog.clear
+* https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.eventing.reader.eventlogsession.clearlog
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: PowerShell Logs
+* Rule Type: BBR
+
+*Version*: 105
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    "Clear-EventLog" or
+    "Remove-EventLog" or
+    ("Eventing.Reader.EventLogSession" and ".ClearLog") or
+    ("Diagnostics.EventLog" and ".Clear")
+  ) and
+  not powershell.file.script_block_text : (
+    "CmdletsToExport=@(\"Add-Content\""
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indicator Removal
+** ID: T1070
+** Reference URL: https://attack.mitre.org/techniques/T1070/
+* Sub-technique:
+** Name: Clear Windows Event Logs
+** ID: T1070.001
+** Reference URL: https://attack.mitre.org/techniques/T1070/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-script-with-password-policy-discovery-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-password-policy-discovery-capabilities.asciidoc
new file mode 100644
index 0000000000..7c5ad45b7b
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-password-policy-discovery-capabilities.asciidoc
@@ -0,0 +1,134 @@
+[[powershell-script-with-password-policy-discovery-capabilities]]
+=== PowerShell Script with Password Policy Discovery Capabilities
+
+Identifies the use of Cmdlets and methods related to remote execution activities using WinRM. Attackers can abuse WinRM to perform lateral movement using built-in tools.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Tactic: Execution
+* Data Source: PowerShell Logs
+* Rule Type: BBR
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category: "process" and host.os.type:windows and
+(
+  powershell.file.script_block_text: (
+    "Get-ADDefaultDomainPasswordPolicy" or
+    "Get-ADFineGrainedPasswordPolicy" or
+    "Get-ADUserResultantPasswordPolicy" or
+    "Get-DomainPolicy" or
+    "Get-GPPPassword" or
+    "Get-PassPol"
+  )
+  or
+  powershell.file.script_block_text: (
+    ("defaultNamingContext" or "ActiveDirectory.DirectoryContext" or "ActiveDirectory.DirectorySearcher") and
+    (
+      (
+        ".MinLengthPassword" or
+        ".MinPasswordAge" or
+        ".MaxPasswordAge"
+      ) or
+      (
+        "minPwdAge" or
+        "maxPwdAge" or
+        "minPwdLength"
+      ) or
+      (
+        "msDS-PasswordSettings"
+      )
+    )
+  )
+) and not powershell.file.script_block_text : (
+    "sentinelbreakpoints" and "Set-PSBreakpoint" and "PowerSploitIndicators"
+  )
+  and not 
+  (
+    powershell.file.script_block_text : ("43c15630-959c-49e4-a977-758c5cc93408" and "CmdletsToExport" and "ActiveDirectory.Types.ps1xml")
+  )
+  and not user.id : "S-1-5-18"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Password Policy Discovery
+** ID: T1201
+** Reference URL: https://attack.mitre.org/techniques/T1201/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-script-with-remote-execution-capabilities-via-winrm.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-remote-execution-capabilities-via-winrm.asciidoc
new file mode 100644
index 0000000000..c7c343e532
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-remote-execution-capabilities-via-winrm.asciidoc
@@ -0,0 +1,117 @@
+[[powershell-script-with-remote-execution-capabilities-via-winrm]]
+=== PowerShell Script with Remote Execution Capabilities via WinRM
+
+Identifies the use of Cmdlets and methods related to remote execution activities using WinRM. Attackers can abuse WinRM to perform lateral movement using built-in tools.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://attack.mitre.org/techniques/T1021/006/
+* https://github.com/cobbr/SharpSploit/blob/master/SharpSploit/LateralMovement/PowerShellRemoting.cs
+* https://github.com/BC-SECURITY/Empire/blob/main/empire/server/modules/powershell/lateral_movement/invoke_psremoting.py
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Execution
+* Data Source: PowerShell Logs
+* Rule Type: BBR
+
+*Version*: 106
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    ("Invoke-WmiMethod" or "Invoke-Command" or "Enter-PSSession") and "ComputerName"
+  ) and
+  not user.id : "S-1-5-18" and
+  not file.directory : (
+    "C:\\Program Files\\LogicMonitor\\Agent\\tmp"
+  ) and not
+  powershell.file.script_block_text : (
+    "Export-ModuleMember -Function @('Invoke-Expression''Invoke-Command')" and
+    "function Invoke-Command {"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: Windows Remote Management
+** ID: T1021.006
+** Reference URL: https://attack.mitre.org/techniques/T1021/006/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-script-with-token-impersonation-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-token-impersonation-capabilities.asciidoc
index a2e04f142f..a4047f286a 100644
--- a/docs/detections/prebuilt-rules/rule-details/powershell-script-with-token-impersonation-capabilities.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-token-impersonation-capabilities.asciidoc
@@ -5,70 +5,175 @@ Detects scripts that contain PowerShell functions, structures, or Windows API fu
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/decoder-it/psgetsystem
 * https://github.com/PowerShellMafia/PowerSploit/blob/master/Privesc/Get-System.ps1
 * https://github.com/EmpireProject/Empire/blob/master/data/module_source/privesc/Invoke-MS16032.ps1
 * https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0109_windows_powershell_script_block_log.md
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: PowerShell Logs
 
-*Version*: 1
+*Version*: 11
 
-*Added ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating PowerShell Script with Token Impersonation Capabilities*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+Adversaries can abuse PowerShell to perform token impersonation, which involves duplicating and impersonating another user's token to escalate privileges and bypass access controls. This rule identifies scripts containing PowerShell functions, structures, or Windows API functions related to token impersonation/theft.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Examine PowerShell process creation and script block logs to identify command line arguments or hardcoded information that can indicate which user was the target of the impersonation.
+- Investigate any abnormal behavior by the subject process (PowerShell), such as network connections, registry or file modifications, and any spawned child processes.
+- Evaluate whether the user needs to use PowerShell to complete tasks.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the script using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
+
+
+- Regular users should not need to impersonate other users, which makes false positives unlikely. In the case of authorized benign true positives (B-TPs), exceptions can be added.
 
 
+*Related Rules*
+
+
+- PowerShell PSReflect Script - 56f2e9b5-4803-4e44-a0a4-a52dc79d57fe
+- Potential Process Injection via PowerShell - 2e29e96a-b67c-455a-afe4-de6183431d0d
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+==== Setup
+
+
+The 'PowerShell Script Block Logging' logging policy must be configured (Enable).
+
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and powershell.file.script_block_text:(
-"Invoke-TokenManipulation" or "ImpersonateNamedPipeClient" or
-"NtImpersonateThread" or ( "STARTUPINFOEX" and
-"UpdateProcThreadAttribute" ) or (
-"AdjustTokenPrivileges" and "SeDebugPrivilege" ) or (
-("DuplicateToken" or "DuplicateTokenEx") and
-("SetThreadToken" or "ImpersonateLoggedOnUser" or
-"CreateProcessWithTokenW" or "CreatePRocessAsUserW" or
-"CreateProcessAsUserA") ) )
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text:(
+    "Invoke-TokenManipulation" or
+    "ImpersonateNamedPipeClient" or
+    "NtImpersonateThread" or
+    (
+      "STARTUPINFOEX" and
+      "UpdateProcThreadAttribute"
+    ) or
+    (
+      "AdjustTokenPrivileges" and
+      "SeDebugPrivilege"
+    ) or
+    (
+      ("DuplicateToken" or
+      "DuplicateTokenEx") and
+      ("SetThreadToken" or
+      "ImpersonateLoggedOnUser" or
+      "CreateProcessWithTokenW" or
+      "CreatePRocessAsUserW" or
+      "CreateProcessAsUserA")
+    ) 
+  ) and
+  not (
+    user.id:("S-1-5-18" or "S-1-5-19" or "S-1-5-20") and
+    file.directory: "C:\\ProgramData\\Microsoft\\Windows Defender Advanced Threat Protection\\Downloads"
+  ) and
+  not powershell.file.script_block_text : (
+    "sentinelbreakpoints" and "Set-PSBreakpoint" and "PowerSploitIndicators"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,8 +185,10 @@ event.category:process and powershell.file.script_block_text:(
 ** Name: Access Token Manipulation
 ** ID: T1134
 ** Reference URL: https://attack.mitre.org/techniques/T1134/
-
-
+* Sub-technique:
+** Name: Token Impersonation/Theft
+** ID: T1134.001
+** Reference URL: https://attack.mitre.org/techniques/T1134/001/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -90,3 +197,11 @@ event.category:process and powershell.file.script_block_text:(
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Technique:
+** Name: Native API
+** ID: T1106
+** Reference URL: https://attack.mitre.org/techniques/T1106/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-script-with-veeam-credential-access-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-veeam-credential-access-capabilities.asciidoc
new file mode 100644
index 0000000000..a7a04707b6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-veeam-credential-access-capabilities.asciidoc
@@ -0,0 +1,110 @@
+[[powershell-script-with-veeam-credential-access-capabilities]]
+=== PowerShell Script with Veeam Credential Access Capabilities
+
+Identifies PowerShell scripts that can access and decrypt Veeam credentials stored in MSSQL databases. Attackers can use Veeam Credentials to target backups as part of destructive operations such as Ransomware attacks.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://forums.veeam.com/veeam-backup-replication-f2/recover-esxi-password-in-veeam-t34630.html
+* https://www.crowdstrike.com/blog/anatomy-of-alpha-spider-ransomware/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: PowerShell Logs
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    (
+      "[dbo].[Credentials]" and
+      ("Veeam" or "VeeamBackup")
+    ) or
+    "ProtectedStorage]::GetLocalString"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-script-with-webcam-video-capture-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-webcam-video-capture-capabilities.asciidoc
new file mode 100644
index 0000000000..7eac664329
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-script-with-webcam-video-capture-capabilities.asciidoc
@@ -0,0 +1,111 @@
+[[powershell-script-with-webcam-video-capture-capabilities]]
+=== PowerShell Script with Webcam Video Capture Capabilities
+
+Detects PowerShell scripts that can be used to record webcam video. Attackers can capture this information to extort or spy on victims.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/EmpireProject/Empire/blob/master/lib/modules/powershell/collection/WebcamRecorder.py
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Data Source: PowerShell Logs
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    "NewFrameEventHandler" or
+    "VideoCaptureDevice" or
+    "DirectX.Capture.Filters" or
+    "VideoCompressors" or
+    "Start-WebcamRecorder" or
+    (
+      ("capCreateCaptureWindowA" or
+       "capCreateCaptureWindow" or
+       "capGetDriverDescription") and
+      ("avicap32.dll" or "avicap32")
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Video Capture
+** ID: T1125
+** Reference URL: https://attack.mitre.org/techniques/T1125/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-share-enumeration-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-share-enumeration-script.asciidoc
index daf4471e98..cb57836422 100644
--- a/docs/detections/prebuilt-rules/rule-details/powershell-share-enumeration-script.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-share-enumeration-script.asciidoc
@@ -5,105 +5,138 @@ Detects scripts that contain PowerShell functions, structures, or Windows API fu
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.advintel.io/post/hunting-for-corporate-insurance-policies-indicators-of-ransom-exfiltrations
 * https://thedfirreport.com/2022/04/04/stolen-images-campaign-ends-in-conti-ransomware/
 * https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0109_windows_powershell_script_block_log.md
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
-
-*Version*: 2 (<<powershell-share-enumeration-script-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Tactic: Collection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
 
-*Added ({stack} release)*: 8.5.0
+*Version*: 9
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating PowerShell Share Enumeration Script
+*Triage and analysis*
+
+
+
+*Investigating PowerShell Share Enumeration Script*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This
-makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+Attackers can use PowerShell to enumerate shares to search for sensitive data like documents, scripts, and other kinds of valuable data for encryption, exfiltration, and lateral movement.
 
-Attackers can use PowerShell to enumerate shares to search for sensitive data like documents, scripts, and other kinds
-of valuable data for encryption, exfiltration, and lateral movement.
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
 - Check for additional PowerShell and command line logs that indicate that imported functions were run.
   - Evaluate which information was potentially mapped and accessed by the attacker.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be configured (Enable).
+
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and powershell.file.script_block_text:(
-"Invoke-ShareFinder" or "Invoke-ShareFinderThreaded" or (
-"shi1_netname" and "shi1_remark" ) or (
-"NetShareEnum" and "NetApiBufferFree" ) )
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text:(
+    "Invoke-ShareFinder" or
+    "Invoke-ShareFinderThreaded" or
+    (
+      "shi1_netname" and
+      "shi1_remark"
+    ) or
+    (
+      "NetShareEnum" and
+      "NetApiBufferFree"
+    )
+  ) and not user.id : "S-1-5-18"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -115,8 +148,6 @@ event.category:process and powershell.file.script_block_text:(
 ** Name: Network Share Discovery
 ** ID: T1135
 ** Reference URL: https://attack.mitre.org/techniques/T1135/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -125,10 +156,19 @@ event.category:process and powershell.file.script_block_text:(
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[powershell-share-enumeration-script-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Technique:
+** Name: Native API
+** ID: T1106
+** Reference URL: https://attack.mitre.org/techniques/T1106/
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Data from Network Shared Drive
+** ID: T1039
+** Reference URL: https://attack.mitre.org/techniques/T1039/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-discovery-related-windows-api-functions.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-discovery-related-windows-api-functions.asciidoc
index 9c21bb449a..8a3d17a2f2 100644
--- a/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-discovery-related-windows-api-functions.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-discovery-related-windows-api-functions.asciidoc
@@ -5,112 +5,154 @@ This rule detects the use of discovery-related Windows API functions in PowerShe
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/BC-SECURITY/Empire/blob/9259e5106986847d2bb770c4289c0c0f1adf2344/data/module_source/situational_awareness/network/powerview.ps1#L21413
 * https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0109_windows_powershell_script_block_log.md
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Tactic: Collection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
+
+*Version*: 213
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
 
-*Version*: 102 (<<powershell-suspicious-discovery-related-windows-api-functions-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.16.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Legitimate PowerShell scripts that make use of these functions.
 
-==== Investigation guide
 
+*Investigating PowerShell Suspicious Discovery Related Windows API Functions*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating PowerShell Suspicious Discovery Related Windows API Functions
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+Attackers can use PowerShell to interact with the Win32 API to bypass command line based detections, using libraries like PSReflect or Get-ProcAddress Cmdlet.
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This
-makes it available for use in various environments, and creates an attractive way for attackers to execute code.
 
-Attackers can use PowerShell to interact with the Win32 API to bypass command line based detections, using libraries
-like PSReflect or Get-ProcAddress Cmdlet.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Examine file or network events from the involved PowerShell process for suspicious behavior.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
 - Check for additional PowerShell and command-line logs that indicate that imported functions were run.
 
-### False positive analysis
 
-- Discovery activities themselves are not inherently malicious if occurring in isolation, as long as the script does not
-contain other capabilities, and there are no other alerts related to the user or host; such alerts can be dismissed.
-However, analysts should keep in mind that this is not a common way of getting information, making it suspicious.
+*False positive analysis*
+
+
+- Discovery activities themselves are not inherently malicious if occurring in isolation, as long as the script does not contain other capabilities, and there are no other alerts related to the user or host; such alerts can be dismissed. However, analysts should keep in mind that this is not a common way of getting information, making it suspicious.
+
+
+*Related rules*
 
-### Related rules
 
 - PowerShell PSReflect Script - 56f2e9b5-4803-4e44-a0a4-a52dc79d57fe
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-NetShareEnum or NetWkstaUserEnum or NetSessionEnum or
-NetLocalGroupEnum or NetLocalGroupGetMembers or DsGetSiteName
-or DsEnumerateDomainTrusts or WTSEnumerateSessionsEx or
-WTSQuerySessionInformation or LsaGetLogonSessionData or
-QueryServiceObjectSecurity )
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    NetShareEnum or
+    NetWkstaUserEnum or
+    NetSessionEnum or
+    NetLocalGroupEnum or
+    NetLocalGroupGetMembers or
+    DsGetSiteName or
+    DsEnumerateDomainTrusts or
+    WTSEnumerateSessionsEx or
+    WTSQuerySessionInformation or
+    LsaGetLogonSessionData or
+    QueryServiceObjectSecurity or
+    GetComputerNameEx or
+    NetWkstaGetInfo or
+    GetUserNameEx or
+    NetUserEnum or
+    NetUserGetInfo or
+    NetGroupEnum or
+    NetGroupGetInfo or
+    NetGroupGetUsers or
+    NetWkstaTransportEnum or
+    NetServerGetInfo or
+    LsaEnumerateTrustedDomains  or
+    NetScheduleJobEnum or
+    NetUserModalsGet
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -119,11 +161,29 @@ QueryServiceObjectSecurity )
 ** ID: TA0007
 ** Reference URL: https://attack.mitre.org/tactics/TA0007/
 * Technique:
+** Name: Permission Groups Discovery
+** ID: T1069
+** Reference URL: https://attack.mitre.org/techniques/T1069/
+* Sub-technique:
+** Name: Local Groups
+** ID: T1069.001
+** Reference URL: https://attack.mitre.org/techniques/T1069/001/
+* Technique:
+** Name: Account Discovery
+** ID: T1087
+** Reference URL: https://attack.mitre.org/techniques/T1087/
+* Sub-technique:
+** Name: Local Account
+** ID: T1087.001
+** Reference URL: https://attack.mitre.org/techniques/T1087/001/
+* Technique:
+** Name: Domain Trust Discovery
+** ID: T1482
+** Reference URL: https://attack.mitre.org/techniques/T1482/
+* Technique:
 ** Name: Network Share Discovery
 ** ID: T1135
 ** Reference URL: https://attack.mitre.org/techniques/T1135/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -132,48 +192,19 @@ QueryServiceObjectSecurity )
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[powershell-suspicious-discovery-related-windows-api-functions-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-NetShareEnum or NetWkstaUserEnum or NetSessionEnum or
-NetLocalGroupEnum or NetLocalGroupGetMembers or DsGetSiteName
-or DsEnumerateDomainTrusts or WTSEnumerateSessionsEx or
-WTSQuerySessionInformation or LsaGetLogonSessionData or
-QueryServiceObjectSecurity )
-----------------------------------
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (8.1.0 release)::
-* Formatting only
-
-Version 3 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.code:"4104" and powershell.file.script_block_text : (
-NetShareEnum or NetWkstaUserEnum or NetSessionEnum or
-NetLocalGroupEnum or NetLocalGroupGetMembers or DsGetSiteName
-or DsEnumerateDomainTrusts or WTSEnumerateSessionsEx or
-WTSQuerySessionInformation or LsaGetLogonSessionData or
-QueryServiceObjectSecurity )
-----------------------------------
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Technique:
+** Name: Native API
+** ID: T1106
+** Reference URL: https://attack.mitre.org/techniques/T1106/
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Data from Network Shared Drive
+** ID: T1039
+** Reference URL: https://attack.mitre.org/techniques/T1039/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-payload-encoded-and-compressed.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-payload-encoded-and-compressed.asciidoc
index 8357114483..9bfa8afb2f 100644
--- a/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-payload-encoded-and-compressed.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-payload-encoded-and-compressed.asciidoc
@@ -5,100 +5,100 @@ Identifies the use of .NET functionality for decompression and base64 decoding c
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<powershell-suspicious-payload-encoded-and-compressed-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 211
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Legitimate PowerShell Scripts which makes use of compression and encoding.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating PowerShell Suspicious Payload Encoded and Compressed
+*Triage and analysis*
+
+
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This
-makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+*Investigating PowerShell Suspicious Payload Encoded and Compressed*
 
-Attackers can embed compressed and encoded payloads in scripts to load directly into the memory without touching the
-disk. This strategy can circumvent string and file-based security protections.
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+Attackers can embed compressed and encoded payloads in scripts to load directly into the memory without touching the disk. This strategy can circumvent string and file-based security protections.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Examine file or network events from the involved PowerShell process for suspicious behavior.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the script using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
-- This activity is unlikely to happen legitimately outside engineering or IT business units. As long as the analyst did
-not identify malware or suspicious activity related to the user or host, this alert can be dismissed.
+- This activity is unlikely to happen legitimately outside engineering or IT business units. As long as the analyst did not identify malware or suspicious activity related to the user or host, this alert can be dismissed.
+
+
+*Related rules*
 
-### Related rules
 
 - PowerShell PSReflect Script - 56f2e9b5-4803-4e44-a0a4-a52dc79d57fe
 - Potential Process Injection via PowerShell - 2e29e96a-b67c-455a-afe4-de6183431d0d
 - Suspicious .NET Reflection via PowerShell - e26f042e-c590-4e82-8e05-41e81bd822ad
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
@@ -106,34 +106,57 @@ not identify malware or suspicious activity related to the user or host, this al
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-( "System.IO.Compression.DeflateStream" or
-"System.IO.Compression.GzipStream" or
-"IO.Compression.DeflateStream" or "IO.Compression.GzipStream"
-) and FromBase64String )
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    (
+      "System.IO.Compression.DeflateStream" or
+      "System.IO.Compression.GzipStream" or
+      "IO.Compression.DeflateStream" or
+      "IO.Compression.GzipStream"
+    ) and
+    FromBase64String
+  ) and
+  not user.id : "S-1-5-18"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -142,11 +165,13 @@ event.category:process and powershell.file.script_block_text : (
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
 * Technique:
+** Name: Obfuscated Files or Information
+** ID: T1027
+** Reference URL: https://attack.mitre.org/techniques/T1027/
+* Technique:
 ** Name: Deobfuscate/Decode Files or Information
 ** ID: T1140
 ** Reference URL: https://attack.mitre.org/techniques/T1140/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -155,42 +180,7 @@ event.category:process and powershell.file.script_block_text : (
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[powershell-suspicious-payload-encoded-and-compressed-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-( "System.IO.Compression.DeflateStream" or
-"System.IO.Compression.GzipStream" or
-"IO.Compression.DeflateStream" or "IO.Compression.GzipStream"
-) and FromBase64String )
-----------------------------------
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-(System.IO.Compression.DeflateStream or
-System.IO.Compression.GzipStream or IO.Compression.DeflateStream or
-IO.Compression.GzipStream) and FromBase64String )
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-audio-capture-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-audio-capture-capabilities.asciidoc
index 5105335fc9..c4472c1120 100644
--- a/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-audio-capture-capabilities.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-audio-capture-capabilities.asciidoc
@@ -5,109 +5,139 @@ Detects PowerShell scripts that can record audio, a common feature in popular po
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/PowerShellMafia/PowerSploit/blob/master/Exfiltration/Get-MicrophoneAudio.ps1
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Collection
-* Investigation Guide
-
-*Version*: 102 (<<powershell-suspicious-script-with-audio-capture-capabilities-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating PowerShell Suspicious Script with Audio Capture Capabilities
+*Triage and analysis*
+
+
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This
-makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+*Investigating PowerShell Suspicious Script with Audio Capture Capabilities*
 
-Attackers can use PowerShell to interact with the Windows API with the intent of capturing audio from input devices
-connected to the victim's computer.
 
-#### Possible investigation steps
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+Attackers can use PowerShell to interact with the Windows API with the intent of capturing audio from input devices connected to the victim's computer.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Examine file or network events from the involved PowerShell process for suspicious behavior.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
 - Investigate if the script stores the recorded data locally and determine if anything was recorded.
-- Investigate if the script contains exfiltration capabilities and the destination of this exfiltration.
+- Investigate whether the script contains exfiltration capabilities and identify the exfiltration server.
 - Assess network data to determine if the host communicated with the exfiltration server.
 
-### False positive analysis
 
-- Regular users should not need scripts to capture audio, which makes false positives unlikely. In the case of
-authorized benign true positives (B-TPs), exceptions can be added.
+*False positive analysis*
+
+
+- Regular users should not need scripts to capture audio, which makes false positives unlikely. In the case of authorized benign true positives (B-TPs), exceptions can be added.
+
+
+*Related rules*
 
-### Related rules
 
 - PowerShell PSReflect Script - 56f2e9b5-4803-4e44-a0a4-a52dc79d57fe
 - Potential Process Injection via PowerShell - 2e29e96a-b67c-455a-afe4-de6183431d0d
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- The response must be prioritized if this alert involves key executives or potentially valuable targets for espionage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Prioritize the response if this alert involves key executives or potentially valuable targets for espionage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-"Get-MicrophoneAudio" or (waveInGetNumDevs and mciSendStringA) )
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    "Get-MicrophoneAudio" or
+    "WindowsAudioDevice-Powershell-Cmdlet" or
+    (waveInGetNumDevs and mciSendStringA)
+  )
+  and not powershell.file.script_block_text : (
+    "sentinelbreakpoints" and "Set-PSBreakpoint" and "PowerSploitIndicators"
+  )
+  and not user.id : "S-1-5-18"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -119,8 +149,6 @@ event.category:process and powershell.file.script_block_text : (
 ** Name: Audio Capture
 ** ID: T1123
 ** Reference URL: https://attack.mitre.org/techniques/T1123/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -129,46 +157,11 @@ event.category:process and powershell.file.script_block_text : (
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[powershell-suspicious-script-with-audio-capture-capabilities-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-"Get-MicrophoneAudio" or (waveInGetNumDevs and mciSendStringA) )
-----------------------------------
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-Get-MicrophoneAudio or (waveInGetNumDevs and mciSendStringA) )
-----------------------------------
-
-Version 4 (8.1.0 release)::
-* Formatting only
-
-Version 3 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.code:"4104" and powershell.file.script_block_text : (
-Get-MicrophoneAudio or (waveInGetNumDevs and mciSendStringA) )
-----------------------------------
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Technique:
+** Name: Native API
+** ID: T1106
+** Reference URL: https://attack.mitre.org/techniques/T1106/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-clipboard-retrieval-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-clipboard-retrieval-capabilities.asciidoc
new file mode 100644
index 0000000000..5d1b53e5b6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-clipboard-retrieval-capabilities.asciidoc
@@ -0,0 +1,171 @@
+[[powershell-suspicious-script-with-clipboard-retrieval-capabilities]]
+=== PowerShell Suspicious Script with Clipboard Retrieval Capabilities
+
+Detects PowerShell scripts that can get the contents of the clipboard, which attackers can abuse to retrieve sensitive information like credentials, messages, etc.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/get-clipboard
+* https://github.com/EmpireProject/Empire/blob/master/data/module_source/collection/Get-ClipboardContents.ps1
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Data Source: PowerShell Logs
+* Resources: Investigation Guide
+
+*Version*: 108
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating PowerShell Suspicious Script with Clipboard Retrieval Capabilities*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+Attackers can abuse PowerShell capabilities to get the contents of the clipboard with the goal of stealing credentials and other valuable information, such as credit card data and confidential conversations.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine file or network events from the involved PowerShell process for suspicious behavior.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Evaluate whether the user needs to use PowerShell to complete tasks.
+- Determine whether the script stores the captured data locally.
+- Investigate whether the script contains exfiltration capabilities and identify the exfiltration server.
+- Assess network data to determine if the host communicated with the exfiltration server.
+
+
+*False positive analysis*
+
+
+- Regular users are unlikely to use scripting utilities to capture contents of the clipboard, making false positives unlikely. In the case of authorized benign true positives (B-TPs), exceptions can be added.
+
+
+*Related rules*
+
+
+- PowerShell Keylogging Script - bd2c86a0-8b61-4457-ab38-96943984e889
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Prioritize the response if this alert involves key executives or potentially valuable targets for espionage.
+- Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  (powershell.file.script_block_text : (
+    "Windows.Clipboard" or
+    "Windows.Forms.Clipboard" or
+    "Windows.Forms.TextBox"
+   ) and
+   powershell.file.script_block_text : (
+    "]::GetText" or
+    ".Paste()"
+  )) or powershell.file.script_block_text : "Get-Clipboard" and
+  not powershell.file.script_block_text : (
+    "sentinelbreakpoints" and "Set-PSBreakpoint" and "PowerSploitIndicators"
+  ) and
+  not user.id : "S-1-5-18" and
+  not (
+    file.path : C\:\\Program?Files\\WindowsPowerShell\\*Modules*.ps1 and
+    file.name : ("Convert-ExcelRangeToImage.ps1" or "Read-Clipboard.ps1")
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Clipboard Data
+** ID: T1115
+** Reference URL: https://attack.mitre.org/techniques/T1115/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-screenshot-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-screenshot-capabilities.asciidoc
index 25f3808e42..4c5af2674c 100644
--- a/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-screenshot-capabilities.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/powershell-suspicious-script-with-screenshot-capabilities.asciidoc
@@ -5,108 +5,132 @@ Detects PowerShell scripts that can take screenshots, which is a common feature
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/dotnet/api/system.drawing.graphics.copyfromscreen
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Collection
-* Investigation Guide
-
-*Version*: 102 (<<powershell-suspicious-script-with-screenshot-capabilities-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating PowerShell Suspicious Script with Screenshot Capabilities
+*Triage and analysis*
+
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks, which makes
-it available for use in various environments and creates an attractive way for attackers to execute code.
 
-Attackers can abuse PowerShell capabilities and take screen captures of desktops to gather information over the course
-of an operation.
+*Investigating PowerShell Suspicious Script with Screenshot Capabilities*
 
-#### Possible investigation steps
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks, which makes it available for use in various environments and creates an attractive way for attackers to execute code.
+
+Attackers can abuse PowerShell capabilities and take screen captures of desktops to gather information over the course of an operation.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Examine file or network events from the involved PowerShell process for suspicious behavior.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
-- Investigate if the script stores the captured data locally.
-- Investigate if the script contains exfiltration capabilities and the destination of this exfiltration.
+- Determine whether the script stores the captured data locally.
+- Investigate whether the script contains exfiltration capabilities and identify the exfiltration server.
 - Assess network data to determine if the host communicated with the exfiltration server.
 
-### False positive analysis
 
-- Regular users do not have a business justification for using scripting utilities to take screenshots, which makes false
-positives unlikely. In the case of authorized benign true positives (B-TPs), exceptions can be added.
+*False positive analysis*
+
+
+- Regular users do not have a business justification for using scripting utilities to take screenshots, which makes false positives unlikely. In the case of authorized benign true positives (B-TPs), exceptions can be added.
+
+
+*Related rules*
 
-### Related rules
 
 - PowerShell Keylogging Script - bd2c86a0-8b61-4457-ab38-96943984e889
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-CopyFromScreen and ("System.Drawing.Bitmap" or "Drawing.Bitmap")
-)
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    CopyFromScreen and
+    ("System.Drawing.Bitmap" or "Drawing.Bitmap")
+  ) and not user.id : "S-1-5-18"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -118,8 +142,6 @@ CopyFromScreen and ("System.Drawing.Bitmap" or "Drawing.Bitmap")
 ** Name: Screen Capture
 ** ID: T1113
 ** Reference URL: https://attack.mitre.org/techniques/T1113/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -128,38 +150,7 @@ CopyFromScreen and ("System.Drawing.Bitmap" or "Drawing.Bitmap")
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[powershell-suspicious-script-with-screenshot-capabilities-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-CopyFromScreen and ("System.Drawing.Bitmap" or "Drawing.Bitmap")
-)
-----------------------------------
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-CopyFromScreen and (System.Drawing.Bitmap or Drawing.Bitmap) )
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-cap-chown-cap-fowner-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-cap-chown-cap-fowner-capabilities.asciidoc
new file mode 100644
index 0000000000..f1c4f6c08f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-cap-chown-cap-fowner-capabilities.asciidoc
@@ -0,0 +1,111 @@
+[[privilege-escalation-via-cap-chown-cap-fowner-capabilities]]
+=== Privilege Escalation via CAP_CHOWN/CAP_FOWNER Capabilities
+
+Identifies instances where a processes (granted CAP_CHOWN and/or CAP_FOWNER capabilities) is executed, after which the ownership of a suspicious file or binary is changed. In Linux, the CAP_CHOWN capability allows a process to change the owner of a file, while CAP_FOWNER permits it to bypass permission checks on operations that require file ownership (like reading, writing, and executing). Attackers may abuse these capabilities to obtain unauthorized access to files.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Auditd Manager.
+
+
+*Auditd Manager Integration Setup*
+
+The Auditd Manager Integration receives audit events from the Linux Audit Framework which is a part of the Linux kernel.
+Auditd Manager provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system.
+
+
+*The following steps should be executed in order to add the Elastic Agent System integration "auditd_manager" on a Linux System:*
+
+- Go to the Kibana home page and click “Add integrations”.
+- In the query bar, search for “Auditd Manager” and select the integration to see more details about it.
+- Click “Add Auditd Manager”.
+- Configure the integration name and optionally add a description.
+- Review optional and advanced settings accordingly.
+- Add the newly installed “auditd manager” to an existing or a new agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+- Click “Save and Continue”.
+- For more details on the integration refer to the https://docs.elastic.co/integrations/auditd_manager[helper guide].
+
+
+*Rule Specific Setup Note*
+
+Auditd Manager subscribes to the kernel and receives events as they occur without any additional configuration.
+However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+- For this detection rule the following additional audit rules are required to be added to the integration:
+  -- "-w /etc/ -p rwxa -k audit_recursive_etc"
+  -- "-w /root/ -p rwxa -k audit_root"
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.pid with maxspan=1s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+   process.name != null and process.thread.capabilities.effective : ("CAP_CHOWN", "CAP_FOWNER") and
+   process.command_line : ("*sudoers*", "*passwd*", "*shadow*", "*/root/*") and user.id != "0"]
+  [file where host.os.type == "linux" and event.action == "changed-file-ownership-of" and event.type == "change" and
+   event.outcome == "success" and file.path in (
+     "/etc/passwd",
+     "/etc/shadow",
+     "/etc/sudoers",
+     "/root/.ssh/*"
+   ) and user.id != "0"
+  ]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-cap-setuid-setgid-capabilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-cap-setuid-setgid-capabilities.asciidoc
new file mode 100644
index 0000000000..f906abb46a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-cap-setuid-setgid-capabilities.asciidoc
@@ -0,0 +1,111 @@
+[[privilege-escalation-via-cap-setuid-setgid-capabilities]]
+=== Privilege Escalation via CAP_SETUID/SETGID Capabilities
+
+Identifies instances where a process (granted CAP_SETUID and/or CAP_SETGID capabilities) is executed, after which the user's access is elevated to UID/GID 0 (root). In Linux, the CAP_SETUID and CAP_SETGID capabilities allow a process to change its UID and GID, respectively, providing control over user and group identity management. Attackers may leverage a misconfiguration for exploitation in order to escalate their privileges to root.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.entity_id with maxspan=1s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and process.name != null and
+   (process.thread.capabilities.effective : "CAP_SET?ID" or process.thread.capabilities.permitted : "CAP_SET?ID") and 
+   user.id != "0"]
+  [process where host.os.type == "linux" and event.action == "uid_change" and event.type == "change" and 
+   (process.thread.capabilities.effective : "CAP_SET?ID" or process.thread.capabilities.permitted : "CAP_SET?ID")
+   and user.id == "0"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Setuid and Setgid
+** ID: T1548.001
+** Reference URL: https://attack.mitre.org/techniques/T1548/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-gdb-cap-sys-ptrace.asciidoc b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-gdb-cap-sys-ptrace.asciidoc
new file mode 100644
index 0000000000..c4403c1c05
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-gdb-cap-sys-ptrace.asciidoc
@@ -0,0 +1,110 @@
+[[privilege-escalation-via-gdb-cap-sys-ptrace]]
+=== Privilege Escalation via GDB CAP_SYS_PTRACE
+
+Identifies instances where GDB (granted the CAP_SYS_PTRACE capability) is executed, after which the user's access is elevated to UID/GID 0 (root). In Linux, the CAP_SYS_PTRACE capability grants a process the ability to use the ptrace system call, which is typically used for debugging and allows the process to trace and control other processes. Attackers may leverage this capability to hook and inject into a process that is running with root permissions in order to escalate their privileges to root.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.entry_leader.entity_id with maxspan=1m
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and process.name == "gdb" and
+   (process.thread.capabilities.effective : "CAP_SYS_PTRACE" or process.thread.capabilities.permitted : "CAP_SYS_PTRACE") and 
+   user.id != "0"]
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+   process.name != null and user.id == "0"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
+* Sub-technique:
+** Name: Ptrace System Calls
+** ID: T1055.008
+** Reference URL: https://attack.mitre.org/techniques/T1055/008/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-named-pipe-impersonation.asciidoc b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-named-pipe-impersonation.asciidoc
index 623f3a9ee1..61c31796c5 100644
--- a/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-named-pipe-impersonation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-named-pipe-impersonation.asciidoc
@@ -5,64 +5,137 @@ Identifies a privilege escalation attempt via named pipe impersonation. An adver
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.ired.team/offensive-security/privilege-escalation/windows-namedpipes-privilege-escalation
+* https://www.cobaltstrike.com/blog/what-happens-when-i-type-getsystem/
+* https://redcanary.com/blog/getsystem-offsec/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 101 (<<privilege-escalation-via-named-pipe-impersonation-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating Privilege Escalation via Named Pipe Impersonation*
+
+
+A named pipe is a type of inter-process communication (IPC) mechanism used in operating systems like Windows, which allows two or more processes to communicate with each other by sending and receiving data through a well-known point.
+
+Attackers can abuse named pipes to elevate their privileges by impersonating the security context in which they execute code. Metasploit, for example, creates a service and a random pipe, and then uses the service to connect to the pipe and impersonate the service security context, which is SYSTEM.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Inspect the host for suspicious or abnormal behavior in the alert timeframe.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - If any suspicious processes were found, examine the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.pe.original_file_name
-in ("Cmd.Exe", "PowerShell.EXE") and process.args : "echo" and
-process.args : ">" and process.args : "\\\\.\\pipe\\*"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ (process.name : ("Cmd.Exe", "PowerShell.EXE") or ?process.pe.original_file_name in ("Cmd.Exe", "PowerShell.EXE")) and
+ process.args : "echo" and process.args : ">" and process.args : "\\\\.\\pipe\\*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,38 +147,3 @@ process.args : ">" and process.args : "\\\\.\\pipe\\*"
 ** Name: Access Token Manipulation
 ** ID: T1134
 ** Reference URL: https://attack.mitre.org/techniques/T1134/
-
-[[privilege-escalation-via-named-pipe-impersonation-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.pe.original_file_name in ("Cmd.Exe", "PowerShell.EXE") and
-process.args : "echo" and process.args : ">" and process.args :
-"\\\\.\\pipe\\*"
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.pe.original_file_name in ("Cmd.Exe", "PowerShell.EXE") and
-process.args : "echo" and process.args : ">" and process.args :
-"\\\\.\\pipe\\*"
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-rogue-named-pipe-impersonation.asciidoc b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-rogue-named-pipe-impersonation.asciidoc
index a313c3cc6e..8039b237f1 100644
--- a/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-rogue-named-pipe-impersonation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-rogue-named-pipe-impersonation.asciidoc
@@ -5,69 +5,71 @@ Identifies a privilege escalation attempt via rogue named pipe impersonation. An
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://itm4n.github.io/printspoofer-abusing-impersonate-privileges/
 * https://github.com/zcgonvh/EfsPotato
 * https://twitter.com/SBousseaden/status/1429530155291193354
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Sysmon
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Sysmon Only
 
-*Version*: 101 (<<privilege-escalation-via-rogue-named-pipe-impersonation-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.0.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
 Named Pipe Creation Events need to be enabled within the Sysmon configuration by including the following settings:
 `condition equal "contains" and keyword equal "pipe"`
 
-If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define `event.ingested` and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate `event.ingested` to @timestamp for this rule to work.
-----------------------------------
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.action : "Pipe Created*" and /* normal sysmon named
-pipe creation events truncate the pipe keyword */ file.name :
-"\\*\\Pipe\\*"
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.action : "Pipe Created*" and
+ /* normal sysmon named pipe creation events truncate the pipe keyword */
+  file.name : "\\*\\Pipe\\*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,19 +81,3 @@ pipe creation events truncate the pipe keyword */ file.name :
 ** Name: Access Token Manipulation
 ** ID: T1134
 ** Reference URL: https://attack.mitre.org/techniques/T1134/
-
-[[privilege-escalation-via-rogue-named-pipe-impersonation-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-root-crontab-file-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-root-crontab-file-modification.asciidoc
index 6b55047b30..a15c728588 100644
--- a/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-root-crontab-file-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-root-crontab-file-modification.asciidoc
@@ -5,55 +5,88 @@ Identifies modifications to the root crontab file. Adversaries may overwrite thi
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://phoenhex.re/2017-06-09/pwn2own-diskarbitrationd-privesc
 * https://www.exploit-db.com/exploits/42146
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Privilege Escalation
 
-*Version*: 100 (<<privilege-escalation-via-root-crontab-file-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:file and not event.type:deletion and
-file.path:/private/var/at/tabs/root and not
-process.executable:/usr/bin/crontab
+[source, js]
 ----------------------------------
+event.category:file and host.os.type:macos and not event.type:deletion and
+ file.path:/private/var/at/tabs/root and not process.executable:/usr/bin/crontab
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -65,13 +98,7 @@ process.executable:/usr/bin/crontab
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[privilege-escalation-via-root-crontab-file-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Cron
+** ID: T1053.003
+** Reference URL: https://attack.mitre.org/techniques/T1053/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-windir-environment-variable.asciidoc b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-windir-environment-variable.asciidoc
index e5e680aab5..7b208f89dd 100644
--- a/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-windir-environment-variable.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/privilege-escalation-via-windir-environment-variable.asciidoc
@@ -5,53 +5,61 @@ Identifies a privilege escalation attempt via a rogue Windows directory (Windir)
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.tiraniddo.dev/2017/05/exploiting-environment-variables-in.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 100 (<<privilege-escalation-via-windir-environment-variable-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.path : ("HKEY_USERS\\*\\Environment\\windir",
-"HKEY_USERS\\*\\Environment\\systemroot") and not
-registry.data.strings : ("C:\\windows", "%SystemRoot%")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and registry.path : (
+    "HKEY_USERS\\*\\Environment\\windir",
+    "HKEY_USERS\\*\\Environment\\systemroot",
+    "HKU\\*\\Environment\\windir",
+    "HKU\\*\\Environment\\systemroot",
+    "\\REGISTRY\\USER\\*\\Environment\\windir",
+    "\\REGISTRY\\USER\\*\\Environment\\systemroot"
+    ) and
+ not registry.data.strings : ("C:\\windows", "%SystemRoot%")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -63,29 +71,7 @@ registry.data.strings : ("C:\\windows", "%SystemRoot%")
 ** Name: Hijack Execution Flow
 ** ID: T1574
 ** Reference URL: https://attack.mitre.org/techniques/T1574/
-
-[[privilege-escalation-via-windir-environment-variable-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path : ("HKEY_USERS\\*\\Environment\\windir",
-"HKEY_USERS\\*\\Environment\\systemroot") and not
-registry.data.strings : ("C:\\windows", "%SystemRoot%")
-----------------------------------
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.1.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Path Interception by PATH Environment Variable
+** ID: T1574.007
+** Reference URL: https://attack.mitre.org/techniques/T1574/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/privileged-account-brute-force.asciidoc b/docs/detections/prebuilt-rules/rule-details/privileged-account-brute-force.asciidoc
index dc361a47dc..0005588c80 100644
--- a/docs/detections/prebuilt-rules/rule-details/privileged-account-brute-force.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/privileged-account-brute-force.asciidoc
@@ -5,96 +5,133 @@ Identifies multiple consecutive logon failures targeting an Admin account from t
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-system.*
+* logs-system.security*
+* logs-windows.forwarded*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4625
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
 
-*Version*: 1
+*Version*: 9
 
-*Added ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-#### Possible investigation steps
+*Triage and analysis*
+
+
+
+*Investigating Privileged Account Brute Force*
+
 
-- Investigate the logon failure reason code and the targeted user names.
+Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts. Without knowledge of the password for an account, an adversary may opt to guess the password using a repetitive or iterative mechanism systematically. More details can be found https://attack.mitre.org/techniques/T1110/001/[here].
+
+This rule identifies potential password guessing/brute force activity from a single address against an account that contains the `admin` pattern on its name, which is likely a highly privileged account.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the logon failure reason code and the targeted user name.
+  - Prioritize the investigation if the account is critical or has administrative privileges over the domain.
 - Investigate the source IP address of the failed Network Logon attempts.
-- Investigate other alerts associated with the user/host during the past 48 hours.
+  - Identify whether these attempts are coming from the internet or are internal.
+- Investigate other alerts associated with the involved users and source host during the past 48 hours.
 - Identify the source and the target computer and their roles in the IT environment.
+- Check whether the involved credentials are used in automation or scheduled tasks.
+- If this activity is suspicious, contact the account owner and confirm whether they are aware of it.
+- Examine the source host for derived artifacts that indicate compromise:
+  - Observe and collect information about the following activities in the alert source host:
+    - Attempts to contact external domains and addresses.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the host which is the source of this activity.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - Authentication misconfiguration or obsolete credentials.
 - Service account password expired.
-- Trust relationship between the primary domain and the trusted domain issue.
-- Infrastructure or availability issue.
+- Domain trust relationship issues.
+- Infrastructure or availability issues.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
-- If the host is a domain controller (DC):
-  - Activate your incident response plan for total Active Directory compromise.
-  - Review the privileges assigned to users that can access the DCs, to ensure that the least privilege principle is
-  being followed and to reduce the attack surface.
-- Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Isolate the source host to prevent further post-compromise behavior.
+- If the asset is exposed to the internet with RDP or other remote services available, take the necessary measures to restrict access to the asset. If not possible, limit the access via the firewall to only the needed IP addresses. Also, ensure the system uses robust authentication mechanisms and is patched regularly.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, source.ip with maxspan=10s [authentication
-where event.action == "logon-failed" and winlog.logon.type :
-"Network" and source.ip != null and source.ip != "127.0.0.1" and
-source.ip != "::1" and user.name : "*admin*" and /* noisy failure
-status codes often associated to authentication misconfiguration */
-not winlog.event_data.Status : ("0xC000015B", "0XC000005E",
-"0XC0000133", "0XC0000192")] with runs=5
+[source, js]
 ----------------------------------
+sequence by winlog.computer_name, source.ip with maxspan=10s
+  [authentication where event.action == "logon-failed" and winlog.logon.type : "Network" and
+    source.ip != null and source.ip != "127.0.0.1" and source.ip != "::1" and user.name : "*admin*" and
+
+    /* noisy failure status codes often associated to authentication misconfiguration */
+    not winlog.event_data.Status : ("0xC000015B", "0XC000005E", "0XC0000133", "0XC0000192")] with runs=5
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -106,3 +143,11 @@ not winlog.event_data.Status : ("0xC000015B", "0XC000005E",
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Sub-technique:
+** Name: Password Guessing
+** ID: T1110.001
+** Reference URL: https://attack.mitre.org/techniques/T1110/001/
+* Sub-technique:
+** Name: Password Spraying
+** ID: T1110.003
+** Reference URL: https://attack.mitre.org/techniques/T1110/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/privileges-elevation-via-parent-process-pid-spoofing.asciidoc b/docs/detections/prebuilt-rules/rule-details/privileges-elevation-via-parent-process-pid-spoofing.asciidoc
index 7ca3a7ec65..626e9394e1 100644
--- a/docs/detections/prebuilt-rules/rule-details/privileges-elevation-via-parent-process-pid-spoofing.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/privileges-elevation-via-parent-process-pid-spoofing.asciidoc
@@ -5,69 +5,110 @@ Identifies parent process spoofing used to create an elevated child process. Adv
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://gist.github.com/xpn/a057a26ec81e736518ee50848b9c2cd6
 * https://blog.didierstevens.com/2017/03/20/
 * https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-updateprocthreadattribute
 * https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1134.002/T1134.002.md
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
 
-*Version*: 1
+*Version*: 7
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-/* This rule is compatible with Elastic Endpoint only */ process
-where event.action == "start" and /* process creation via seclogon
-*/ process.parent.Ext.real.pid > 0 and /* PrivEsc to SYSTEM */
-user.id : "S-1-5-18" and /* Common FPs - evasion via hollowing is
-possible, should be covered by code injection */ not
-process.executable : ("?:\\Windows\\System32\\WerFault.exe",
-"?:\\Windows\\SysWOW64\\WerFault.exe",
-"?:\\Windows\\System32\\WerFaultSecure.exe",
-"?:\\Windows\\SysWOW64\\WerFaultSecure.exe",
-"?:\\Windows\\System32\\Wermgr.exe",
-"?:\\Windows\\SysWOW64\\Wermgr.exe", "?:\\W
-indows\\SoftwareDistribution\\Download\\Install\\securityhealthsetup.e
-xe") and not process.parent.executable :
-"?:\\Windows\\System32\\AtBroker.exe" and not
-(process.code_signature.subject_name in ("philandro
-Software GmbH", "Freedom Scientific Inc.", "TeamViewer Germany GmbH",
-"Projector.is, Inc.", "TeamViewer GmbH", "Cisco WebEx
-LLC", "Dell Inc") and process.code_signature.trusted == true)
+[source, js]
 ----------------------------------
+/* This rule is compatible with Elastic Endpoint only */
+
+process where host.os.type == "windows" and event.action == "start" and
+
+ /* process creation via seclogon */
+ process.parent.Ext.real.pid > 0 and
+
+ /* PrivEsc to SYSTEM */
+ user.id : "S-1-5-18"  and
+
+ /* Common FPs - evasion via hollowing is possible, should be covered by code injection */
+ not process.executable : ("?:\\Windows\\System32\\WerFault.exe",
+                           "?:\\Windows\\SysWOW64\\WerFault.exe",
+                           "?:\\Windows\\System32\\WerFaultSecure.exe",
+                           "?:\\Windows\\SysWOW64\\WerFaultSecure.exe",
+                           "?:\\Windows\\System32\\Wermgr.exe",
+                           "?:\\Windows\\SysWOW64\\Wermgr.exe",
+                           "?:\\Windows\\SoftwareDistribution\\Download\\Install\\securityhealthsetup.exe") and
+ /* Logon Utilities */
+ not (process.parent.executable : "?:\\Windows\\System32\\Utilman.exe" and
+     process.executable : ("?:\\Windows\\System32\\osk.exe",
+                           "?:\\Windows\\System32\\Narrator.exe",
+                           "?:\\Windows\\System32\\Magnify.exe")) and
+
+ not process.parent.executable : "?:\\Windows\\System32\\AtBroker.exe" and
+
+ not (process.code_signature.subject_name in
+           ("philandro Software GmbH", "Freedom Scientific Inc.", "TeamViewer Germany GmbH", "Projector.is, Inc.",
+            "TeamViewer GmbH", "Cisco WebEx LLC", "Dell Inc") and process.code_signature.trusted == true) and 
+
+ /* AM_Delta_Patch Windows Update */
+ not (process.executable : ("?:\\Windows\\System32\\MpSigStub.exe", "?:\\Windows\\SysWOW64\\MpSigStub.exe") and
+      process.parent.executable : ("?:\\Windows\\System32\\wuauclt.exe", 
+                                   "?:\\Windows\\SysWOW64\\wuauclt.exe", 
+                                   "?:\\Windows\\UUS\\Packages\\Preview\\*\\wuaucltcore.exe", 
+                                   "?:\\Windows\\UUS\\amd64\\wuauclt.exe", 
+                                   "?:\\Windows\\UUS\\amd64\\wuaucltcore.exe", 
+                                   "?:\\ProgramData\\Microsoft\\Windows\\UUS\\*\\wuaucltcore.exe")) and
+ not (process.executable : ("?:\\Windows\\System32\\MpSigStub.exe", "?:\\Windows\\SysWOW64\\MpSigStub.exe") and process.parent.executable == null) and
+
+ /* Other third party SW */
+ not process.parent.executable :
+                   ("?:\\Program Files (x86)\\HEAT Software\\HEAT Remote\\HEATRemoteServer.exe",
+                    "?:\\Program Files (x86)\\VisualCron\\VisualCronService.exe",
+                    "?:\\Program Files\\BinaryDefense\\Vision\\Agent\\bds-vision-agent-app.exe",
+                    "?:\\Program Files\\Tablet\\Wacom\\WacomHost.exe",
+                    "?:\\Program Files (x86)\\LogMeIn\\x64\\LogMeIn.exe",
+                    "?:\\Program Files (x86)\\EMC Captiva\\Captiva Cloud Runtime\\Emc.Captiva.WebCaptureRunner.exe",
+                    "?:\\Program Files\\Freedom Scientific\\*.exe",
+                    "?:\\Program Files (x86)\\Google\\Chrome Remote Desktop\\*\\remoting_host.exe",
+                    "?:\\Program Files (x86)\\GoToAssist Remote Support Customer\\*\\g2ax_comm_customer.exe") and
+ not (
+    process.code_signature.trusted == true and process.code_signature.subject_name == "Netwrix Corporation" and
+    process.name : "adcrcpy.exe" and process.parent.executable : (
+      "?:\\Program Files (x86)\\Netwrix Auditor\\Active Directory Auditing\\Netwrix.ADA.EventCollector.exe",
+      "?:\\Program Files (x86)\\Netwrix Auditor\\Active Directory Auditing\\Netwrix.ADA.Analyzer.exe",
+      "?:\\Netwrix Auditor\\Active Directory Auditing\\Netwrix.ADA.EventCollector.exe"
+    )
+ )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,3 +120,11 @@ LLC", "Dell Inc") and process.code_signature.trusted == true)
 ** Name: Access Token Manipulation
 ** ID: T1134
 ** Reference URL: https://attack.mitre.org/techniques/T1134/
+* Sub-technique:
+** Name: Create Process with Token
+** ID: T1134.002
+** Reference URL: https://attack.mitre.org/techniques/T1134/002/
+* Sub-technique:
+** Name: Parent PID Spoofing
+** ID: T1134.004
+** Reference URL: https://attack.mitre.org/techniques/T1134/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/process-activity-via-compiled-html-file.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-activity-via-compiled-html-file.asciidoc
index 26e989c5a3..246d688ebe 100644
--- a/docs/detections/prebuilt-rules/rule-details/process-activity-via-compiled-html-file.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/process-activity-via-compiled-html-file.asciidoc
@@ -5,67 +5,140 @@ Compiled HTML files (.chm) are commonly distributed as part of the Microsoft HTM
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<process-activity-via-compiled-html-file-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-The HTML Help executable program (hh.exe) runs whenever a user clicks a compiled help (.chm) file or menu item that opens the help file inside the Help Viewer. This is not always malicious, but adversaries may abuse this technology to conceal malicious code.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating Process Activity via Compiled HTML File*
+
+
+CHM (Compiled HTML) files are a format for delivering online help files on Windows. CHM files are compressed compilations of various content, such as HTML documents, images, and scripting/web-related programming languages such as VBA, JScript, Java, and ActiveX.
+
+When users double-click CHM files, the HTML Help executable program (`hh.exe`) will execute them. `hh.exe` also can be used to execute code embedded in those files, PowerShell scripts, and executables. This makes it useful for attackers not only to proxy the execution of malicious payloads via a signed binary that could bypass security controls, but also to gain initial access to environments via social engineering methods.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Investigate the parent process to gain understanding of what triggered this behavior.
+  - Retrieve `.chm`, `.ps1`, and other files that were involved to further examination.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executables, scripts and help files retrieved from the system using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- If the malicious file was delivered via phishing:
+  - Block the email sender from sending future emails.
+  - Block the malicious web pages.
+  - Remove emails from the sender from mailboxes.
+  - Consider improvements to the security awareness program.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"hh.exe" and process.name : ("mshta.exe", "cmd.exe",
-"powershell.exe", "pwsh.exe", "powershell_ise.exe", "cscript.exe",
-"wscript.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.parent.name : "hh.exe" and
+ process.name : ("mshta.exe", "cmd.exe", "powershell.exe", "pwsh.exe", "powershell_ise.exe", "cscript.exe", "wscript.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,8 +150,10 @@ process where event.type == "start" and process.parent.name :
 ** Name: User Execution
 ** ID: T1204
 ** Reference URL: https://attack.mitre.org/techniques/T1204/
-
-
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -87,77 +162,7 @@ process where event.type == "start" and process.parent.name :
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[process-activity-via-compiled-html-file-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "hh.exe" and process.name : ("mshta.exe",
-"cmd.exe", "powershell.exe", "pwsh.exe", "powershell_ise.exe",
-"cscript.exe", "wscript.exe")
-----------------------------------
-
-Version 13 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "hh.exe" and process.name : ("mshta.exe",
-"cmd.exe", "powershell.exe", "pwsh.exe", "powershell_ise.exe",
-"cscript.exe", "wscript.exe")
-----------------------------------
-
-Version 11 (8.2.0 release)::
-* Formatting only
-
-Version 10 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "hh.exe" and process.name : ("mshta.exe",
-"cmd.exe", "powershell.exe", "pwsh.exe", "cscript.exe", "wscript.exe")
-----------------------------------
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:hh.exe
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.code:1 and process.name:hh.exe
-----------------------------------
-
-Version 3 (7.9.0 release)::
-* Formatting only
-
-Version 2 (7.7.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Compiled HTML File
+** ID: T1218.001
+** Reference URL: https://attack.mitre.org/techniques/T1218/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/process-capability-enumeration.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-capability-enumeration.asciidoc
new file mode 100644
index 0000000000..88cfd1e639
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/process-capability-enumeration.asciidoc
@@ -0,0 +1,101 @@
+[[process-capability-enumeration]]
+=== Process Capability Enumeration
+
+Identifies recursive process capability enumeration of the entire filesystem through the getcap command. Malicious users may manipulate identified capabilities to gain root privileges.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
+process.name == "getcap" and process.args == "-r" and process.args == "/" and process.args_count == 3 and
+user.id != "0"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Process Discovery
+** ID: T1057
+** Reference URL: https://attack.mitre.org/techniques/T1057/
diff --git a/docs/detections/prebuilt-rules/rule-details/process-created-with-a-duplicated-token.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-created-with-a-duplicated-token.asciidoc
new file mode 100644
index 0000000000..925d7210c4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/process-created-with-a-duplicated-token.asciidoc
@@ -0,0 +1,95 @@
+[[process-created-with-a-duplicated-token]]
+=== Process Created with a Duplicated Token
+
+Identifies the creation of a process impersonating the token of another user logon session. Adversaries may create a new process with a different token to escalate privileges and bypass access controls.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-createprocesswithtokenw
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+/* This rule is only compatible with Elastic Endpoint 8.4+ */
+
+process where host.os.type == "windows" and event.action == "start" and
+
+ user.id : ("S-1-5-21-*", "S-1-12-1-*") and
+
+ (process.Ext.effective_parent.executable regex~ """[C-Z]:\\Windows\\(System32|SysWOW64)\\[a-zA-Z0-9\-\_\.]+\.exe""" or
+  process.Ext.effective_parent.executable : "?:\\Windows\\explorer.exe") and
+
+ (
+  process.name : ("powershell.exe", "cmd.exe", "rundll32.exe", "notepad.exe", "net.exe", "ntdsutil.exe",
+                  "tasklist.exe", "reg.exe", "certutil.exe", "bitsadmin.exe", "msbuild.exe", "esentutl.exe") or
+
+  ((process.Ext.relative_file_creation_time <= 900 or process.Ext.relative_file_name_modify_time <= 900) and
+   not process.code_signature.status : ("trusted", "errorExpired", "errorCode_endpoint*") and
+   not process.executable : ("?:\\Program Files\\*", "?:\\Program Files (x86)\\*"))
+ ) and
+ not (process.name : "rundll32.exe" and
+      process.command_line : ("*davclnt.dll,DavSetCookie*", "*?:\\Program Files*",
+                              "*\\Windows\\System32\\winethc.dll*", "*\\Windows\\SYSTEM32\\EDGEHTML.dll*",
+                              "*shell32.dll,SHCreateLocalServerRunDll*")) and
+ not startswith~(process.Ext.effective_parent.name, process.parent.name) and 
+ not (process.name : "powershell.exe" and process.parent.name : "wmiprvse.exe" and process.Ext.effective_parent.executable : "?:\\Windows\\System32\\wsmprovhost.exe") and 
+ not (process.Ext.effective_parent.executable : "?:\\Windows\\System32\\RuntimeBroker.exe" and process.parent.executable : "?:\\Windows\\System32\\sihost.exe") and 
+ not (process.Ext.effective_parent.executable : "?:\\Windows\\System32\\sethc.exe" and process.parent.executable : "?:\\Windows\\System32\\svchost.exe") and 
+ not (process.Ext.effective_parent.executable : "?:\\Windows\\explorer.exe" and 
+      process.parent.executable : ("?:\\Windows\\System32\\svchost.exe", "?:\\Windows\\System32\\msiexec.exe", "?:\\Windows\\twain_32\\*.exe"))
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Access Token Manipulation
+** ID: T1134
+** Reference URL: https://attack.mitre.org/techniques/T1134/
+* Sub-technique:
+** Name: Token Impersonation/Theft
+** ID: T1134.001
+** Reference URL: https://attack.mitre.org/techniques/T1134/001/
+* Sub-technique:
+** Name: Create Process with Token
+** ID: T1134.002
+** Reference URL: https://attack.mitre.org/techniques/T1134/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/process-created-with-an-elevated-token.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-created-with-an-elevated-token.asciidoc
index 6ad0c753d1..d6a5e6da50 100644
--- a/docs/detections/prebuilt-rules/rule-details/process-created-with-an-elevated-token.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/process-created-with-an-elevated-token.asciidoc
@@ -5,78 +5,113 @@ Identifies the creation of a process running as SYSTEM and impersonating a Windo
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://lengjibo.github.io/token/
 * https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-createprocesswithtokenw
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
 
-*Version*: 1
+*Version*: 6
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-/* This rule is only compatible with Elastic Endpoint 8.4+ */ process
-where event.action == "start" and /* CreateProcessWithToken and
-effective parent is a privileged MS native binary used as a target for
-token theft */ user.id : "S-1-5-18" and /* Token Theft target
-process usually running as service are located in one of the following
-paths */ process.Ext.effective_parent.executable :
-("?:\\Windows\\*.exe", "?:\\Program Files\\*.exe",
-"?:\\Program Files (x86)\\*.exe",
-"?:\\ProgramData\\*") and not
-(process.Ext.effective_parent.executable :
-"?:\\Windows\\System32\\Utilman.exe" and
-process.parent.executable : "?:\\Windows\\System32\\Utilman.exe" and
-process.parent.args : "/debug") and not process.executable :
-("?:\\Windows\\System32\\WerFault.exe",
-"?:\\Windows\\SysWOW64\\WerFault.exe",
-"?:\\Windows\\System32\\WerFaultSecure.exe",
-"?:\\Windows\\SysWOW64\\WerFaultSecure.exe",
-"?:\\windows\\system32\\WerMgr.exe", "?:\\W
-indows\\SoftwareDistribution\\Download\\Install\\securityhealthsetup.e
-xe") and not process.parent.executable :
-("?:\\Windows\\System32\\AtBroker.exe",
-"?:\\Windows\\system32\\svchost.exe", "?:\\Program Files
-(x86)\\*.exe", "?:\\Program Files\\*.exe",
-"?:\\Windows\\System32\\msiexec.exe",
-"C:\\Windows\\System32\\DriverStore\\*") and not
-(process.code_signature.trusted == true and
-process.code_signature.subject_name in ("philandro Software GmbH",
-"Freedom Scientific Inc.", "TeamViewer Germany GmbH", "Projector.is,
-Inc.", "TeamViewer GmbH", "Cisco WebEx LLC", "Dell Inc"))
+[source, js]
 ----------------------------------
+/* This rule is only compatible with Elastic Endpoint 8.4+ */
+
+process where host.os.type == "windows" and event.action == "start" and
+
+ /* CreateProcessWithToken and effective parent is a privileged MS native binary used as a target for token theft */
+ user.id : "S-1-5-18"  and
+
+ /* Token Theft target process usually running as service are located in one of the following paths */
+ process.Ext.effective_parent.executable :
+                ("?:\\Windows\\*.exe",
+                 "?:\\Program Files\\*.exe",
+                 "?:\\Program Files (x86)\\*.exe",
+                 "?:\\ProgramData\\*") and
+
+/* Ignores Utility Manager in Windows running in debug mode */
+ not (process.Ext.effective_parent.executable : "?:\\Windows\\System32\\Utilman.exe" and
+      process.parent.executable : "?:\\Windows\\System32\\Utilman.exe" and process.parent.args : "/debug") and
+
+/* Ignores Windows print spooler service with correlation to Access Intelligent Form */
+not (process.parent.executable : "?\\Windows\\System32\\spoolsv.exe" and
+     process.executable: "?:\\Program Files*\\Access\\Intelligent Form\\*\\LaunchCreate.exe") and 
+
+/* Ignores Windows error reporting executables */
+ not process.executable : ("?:\\Windows\\System32\\WerFault.exe",
+                           "?:\\Windows\\SysWOW64\\WerFault.exe",
+                           "?:\\Windows\\System32\\WerFaultSecure.exe",
+                           "?:\\Windows\\SysWOW64\\WerFaultSecure.exe",
+                           "?:\\windows\\system32\\WerMgr.exe",
+                           "?:\\Windows\\SoftwareDistribution\\Download\\Install\\securityhealthsetup.exe")  and
+
+ /* Ignores Windows updates from TiWorker.exe that runs with elevated privileges */
+ not (process.parent.executable : "?:\\Windows\\WinSxS\\*\\TiWorker.exe" and
+      process.executable : ("?:\\Windows\\Microsoft.NET\\Framework*.exe",
+                            "?:\\Windows\\WinSxS\\*.exe",
+                            "?:\\Windows\\System32\\inetsrv\\iissetup.exe",
+                            "?:\\Windows\\SysWOW64\\inetsrv\\iissetup.exe",
+                            "?:\\Windows\\System32\\inetsrv\\aspnetca.exe",
+                            "?:\\Windows\\SysWOW64\\inetsrv\\aspnetca.exe",
+                            "?:\\Windows\\System32\\lodctr.exe",
+                            "?:\\Windows\\SysWOW64\\lodctr.exe",
+                            "?:\\Windows\\System32\\netcfg.exe",
+                            "?:\\Windows\\Microsoft.NET\\Framework*\\*\\ngen.exe",
+                            "?:\\Windows\\Microsoft.NET\\Framework*\\*\\aspnet_regiis.exe")) and
+
+
+/* Ignores additional parent executables that run with elevated privileges */
+ not process.parent.executable : 
+               ("?:\\Windows\\System32\\AtBroker.exe", 
+                "?:\\Windows\\system32\\svchost.exe", 
+                "?:\\Program Files (x86)\\*.exe", 
+                "?:\\Program Files\\*.exe", 
+                "?:\\Windows\\System32\\msiexec.exe",
+                "?:\\Windows\\System32\\DriverStore\\*") and
+
+/* Ignores Windows binaries with a trusted signature and specific signature name */
+ not (process.code_signature.trusted == true and
+      process.code_signature.subject_name : 
+                ("philandro Software GmbH", 
+                 "Freedom Scientific Inc.", 
+                 "TeamViewer Germany GmbH", 
+                 "Projector.is, Inc.", 
+                 "TeamViewer GmbH", 
+                 "Cisco WebEx LLC", 
+                 "Dell Inc"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -88,3 +123,7 @@ Inc.", "TeamViewer GmbH", "Cisco WebEx LLC", "Dell Inc"))
 ** Name: Access Token Manipulation
 ** ID: T1134
 ** Reference URL: https://attack.mitre.org/techniques/T1134/
+* Sub-technique:
+** Name: Create Process with Token
+** ID: T1134.002
+** Reference URL: https://attack.mitre.org/techniques/T1134/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/process-creation-via-secondary-logon.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-creation-via-secondary-logon.asciidoc
index ca1b462561..b461bea0be 100644
--- a/docs/detections/prebuilt-rules/rule-details/process-creation-via-secondary-logon.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/process-creation-via-secondary-logon.asciidoc
@@ -5,67 +5,75 @@ Identifies process creation with alternate credentials. Adversaries may create a
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://attack.mitre.org/techniques/T1134/002/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 9
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
 
-*Version*: 2 (<<process-creation-via-secondary-logon-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.5.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+Audit events 4624 and 4688 are needed to trigger this rule.
 
-----------------------------------
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=1m [authentication where
-event.action:"logged-in" and event.outcome == "success" and user.id :
-("S-1-5-21-*", "S-1-12-1-*") and /* seclogon service */
-process.name == "svchost.exe" and winlog.event_data.LogonProcessName
-: "seclogo*" and source.ip == "::1" ] by
-winlog.event_data.TargetLogonId [process where event.type == "start"]
-by winlog.event_data.TargetLogonId
+[source, js]
 ----------------------------------
+sequence by winlog.computer_name with maxspan=1m
+
+[authentication where event.action:"logged-in" and
+ event.outcome == "success" and user.id : ("S-1-5-21-*", "S-1-12-1-*") and
 
-==== Threat mapping
+ /* seclogon service */
+ process.name == "svchost.exe" and
+ winlog.event_data.LogonProcessName : "seclogo*" and source.ip == "::1" ] by winlog.event_data.TargetLogonId
+
+[process where event.type == "start"] by winlog.event_data.TargetLogonId
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,20 +85,11 @@ by winlog.event_data.TargetLogonId
 ** Name: Access Token Manipulation
 ** ID: T1134
 ** Reference URL: https://attack.mitre.org/techniques/T1134/
-
-[[process-creation-via-secondary-logon-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=1m [authentication where
-event.action:"logged-in" and event.outcome == "success" and
-user.id:"S-1-5-21-*" and /* seclogon service */ process.name ==
-"svchost.exe" and winlog.event_data.LogonProcessName : "seclogo*"
-and source.ip == "::1" ] by winlog.event_data.TargetLogonId [process
-where event.type == "start"] by winlog.event_data.TargetLogonId
-----------------------------------
-
+* Sub-technique:
+** Name: Create Process with Token
+** ID: T1134.002
+** Reference URL: https://attack.mitre.org/techniques/T1134/002/
+* Sub-technique:
+** Name: Make and Impersonate Token
+** ID: T1134.003
+** Reference URL: https://attack.mitre.org/techniques/T1134/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/process-discovery-using-built-in-tools.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-discovery-using-built-in-tools.asciidoc
new file mode 100644
index 0000000000..67a7bf8c95
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/process-discovery-using-built-in-tools.asciidoc
@@ -0,0 +1,72 @@
+[[process-discovery-using-built-in-tools]]
+=== Process Discovery Using Built-in Tools
+
+This rule identifies the execution of commands that can be used to enumerate running processes. Adversaries may enumerate processes to identify installed applications and security solutions.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* logs-system.security*
+* winlogbeat-*
+* logs-windows.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (
+    process.name :("PsList.exe", "qprocess.exe") or 
+   (process.name : "powershell.exe" and process.args : ("*get-process*", "*Win32_Process*")) or 
+   (process.name : "wmic.exe" and process.args : ("process", "*Win32_Process*")) or
+   (process.name : "tasklist.exe" and not process.args : ("pid eq*")) or
+   (process.name : "query.exe" and process.args : "process")
+  ) and not user.id : "S-1-5-18"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Process Discovery
+** ID: T1057
+** Reference URL: https://attack.mitre.org/techniques/T1057/
diff --git a/docs/detections/prebuilt-rules/rule-details/process-discovery-via-built-in-applications.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-discovery-via-built-in-applications.asciidoc
new file mode 100644
index 0000000000..d1a5805586
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/process-discovery-via-built-in-applications.asciidoc
@@ -0,0 +1,74 @@
+[[process-discovery-via-built-in-applications]]
+=== Process Discovery via Built-In Applications
+
+Identifies the use of built-in tools attackers can use to discover running processes on an endpoint.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and event.action in ("exec", "exec_event") and process.name in (
+  "ps", "pstree", "htop", "pgrep"
+) and 
+not process.parent.name in ("amazon-ssm-agent", "snap")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Process Discovery
+** ID: T1057
+** Reference URL: https://attack.mitre.org/techniques/T1057/
+* Technique:
+** Name: Software Discovery
+** ID: T1518
+** Reference URL: https://attack.mitre.org/techniques/T1518/
+* Sub-technique:
+** Name: Security Software Discovery
+** ID: T1518.001
+** Reference URL: https://attack.mitre.org/techniques/T1518/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/process-execution-from-an-unusual-directory.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-execution-from-an-unusual-directory.asciidoc
index d6af5332e6..86b8746e28 100644
--- a/docs/detections/prebuilt-rules/rule-details/process-execution-from-an-unusual-directory.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/process-execution-from-an-unusual-directory.asciidoc
@@ -5,103 +5,180 @@ Identifies process execution from suspicious default Windows directories. This i
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<process-execution-from-an-unusual-directory-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating Process Execution from an Unusual Directory*
+
+
+This rule identifies processes that are executed from suspicious default Windows directories. Adversaries may abuse this technique by planting malware in trusted paths, making it difficult for security analysts to discern if their activities are malicious or take advantage of exceptions that may apply to these paths.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes, examining their executable files for prevalence, location, and valid digital signatures.
+- Investigate any abnormal behavior by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
+- Examine arguments and working directory to determine the program's source or the nature of the tasks it is performing.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Inspect the host for suspicious or abnormal behavior in the alert timeframe.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of executable and signature conditions.
+
+
+*Related Rules*
+
+
+- Unusual Windows Path Activity - 445a342e-03fb-42d0-8656-0367eb2dead5
+- Execution from Unusual Directory - Command Line - cff92c41-2225-4763-b4ce-6f71e5bda5e6
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and /* add suspicious execution
-paths here */ process.executable : ("C:\\PerfLogs\\*.exe","C:\\Users\\
-Public\\*.exe","C:\\Windows\\Tasks\\*.exe","C:\\Intel\\*.exe","C:\\AMD
-\\Temp\\*.exe","C:\\Windows\\AppReadiness\\*.exe", "C:\\Windows\\Servi
-ceState\\*.exe","C:\\Windows\\security\\*.exe","C:\\Windows\\IdentityC
-RL\\*.exe","C:\\Windows\\Branding\\*.exe","C:\\Windows\\csc\\*.exe",
-"C:\\Windows\\DigitalLocker\\*.exe","C:\\Windows\\en-US\\*.exe","C:\\W
-indows\\wlansvc\\*.exe","C:\\Windows\\Prefetch\\*.exe","C:\\Windows\\F
-onts\\*.exe", "C:\\Windows\\diagnostics\\*.exe","C:\\Windows\\TAPI\\*
-.exe","C:\\Windows\\INF\\*.exe","C:\\Windows\\System32\\Speech\\*.exe"
-,"C:\\windows\\tracing\\*.exe", "c:\\windows\\IME\\*.exe","c:\\Window
-s\\Performance\\*.exe","c:\\windows\\intel\\*.exe","c:\\windows\\ms\\*
-.exe","C:\\Windows\\dot3svc\\*.exe", "C:\\Windows\\panther\\*.exe","C
-:\\Windows\\RemotePackages\\*.exe","C:\\Windows\\OCR\\*.exe","C:\\Wind
-ows\\appcompat\\*.exe","C:\\Windows\\apppatch\\*.exe","C:\\Windows\\ad
-dins\\*.exe", "C:\\Windows\\Setup\\*.exe","C:\\Windows\\Help\\*.exe",
-"C:\\Windows\\SKB\\*.exe","C:\\Windows\\Vss\\*.exe","C:\\Windows\\Web\
-\*.exe","C:\\Windows\\servicing\\*.exe","C:\\Windows\\CbsTemp\\*.exe",
-"C:\\Windows\\Logs\\*.exe","C:\\Windows\\WaaS\\*.exe","C:\\Windows\\Sh
-ellExperiences\\*.exe","C:\\Windows\\ShellComponents\\*.exe","C:\\Wind
-ows\\PLA\\*.exe", "C:\\Windows\\Migration\\*.exe","C:\\Windows\\debug
-\\*.exe","C:\\Windows\\Cursors\\*.exe","C:\\Windows\\Containers\\*.exe
-","C:\\Windows\\Boot\\*.exe","C:\\Windows\\bcastdvr\\*.exe", "C:\\Win
-dows\\assembly\\*.exe","C:\\Windows\\TextInput\\*.exe","C:\\Windows\\s
-ecurity\\*.exe","C:\\Windows\\schemas\\*.exe","C:\\Windows\\SchCache\\
-*.exe","C:\\Windows\\Resources\\*.exe", "C:\\Windows\\rescache\\*.exe
-","C:\\Windows\\Provisioning\\*.exe","C:\\Windows\\PrintDialog\\*.exe"
-,"C:\\Windows\\PolicyDefinitions\\*.exe","C:\\Windows\\media\\*.exe",
-"C:\\Windows\\Globalization\\*.exe","C:\\Windows\\L2Schemas\\*.exe","C
-:\\Windows\\LiveKernelReports\\*.exe","C:\\Windows\\ModemLogs\\*.exe",
-"C:\\Windows\\ImmersiveControlPanel\\*.exe") and not process.name : (
-"SpeechUXWiz.exe","SystemSettings.exe","TrustedInstaller.exe","PrintDi
-alog.exe","MpSigStub.exe","LMS.exe","mpam-*.exe") and not
-process.executable :
-("?:\\Intel\\Wireless\\WUSetupLauncher.exe",
-"?:\\Intel\\Wireless\\Setup.exe", "?:\\Intel\\Move
-Mouse.exe", "?:\\windows\\Panther\\DiagTrackRunner.exe",
-"?:\\Windows\\servicing\\GC64\\tzupd.exe",
-"?:\\Users\\Public\\res\\RemoteLite.exe",
-"?:\\Users\\Public\\IBM\\ClientSolutions\\*.exe",
-"?:\\Users\\Public\\Documents\\syspin.exe",
-"?:\\Users\\Public\\res\\FileWatcher.exe") /* uncomment once in
-winlogbeat */ /* and not (process.code_signature.subject_name ==
-"Microsoft Corporation" and process.code_signature.trusted == true) */
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  /* add suspicious execution paths here */
+  process.executable : (
+    "?:\\PerfLogs\\*.exe", "?:\\Users\\Public\\*.exe", "?:\\Windows\\Tasks\\*.exe",
+    "?:\\Intel\\*.exe", "?:\\AMD\\Temp\\*.exe", "?:\\Windows\\AppReadiness\\*.exe",
+    "?:\\Windows\\ServiceState\\*.exe", "?:\\Windows\\security\\*.exe", "?:\\Windows\\IdentityCRL\\*.exe",
+    "?:\\Windows\\Branding\\*.exe", "?:\\Windows\\csc\\*.exe", "?:\\Windows\\DigitalLocker\\*.exe",
+    "?:\\Windows\\en-US\\*.exe", "?:\\Windows\\wlansvc\\*.exe", "?:\\Windows\\Prefetch\\*.exe",
+    "?:\\Windows\\Fonts\\*.exe", "?:\\Windows\\diagnostics\\*.exe", "?:\\Windows\\TAPI\\*.exe",
+    "?:\\Windows\\INF\\*.exe", "?:\\Windows\\System32\\Speech\\*.exe", "?:\\windows\\tracing\\*.exe",
+    "?:\\windows\\IME\\*.exe", "?:\\Windows\\Performance\\*.exe", "?:\\windows\\intel\\*.exe",
+    "?:\\windows\\ms\\*.exe", "?:\\Windows\\dot3svc\\*.exe", "?:\\Windows\\panther\\*.exe",
+    "?:\\Windows\\RemotePackages\\*.exe", "?:\\Windows\\OCR\\*.exe", "?:\\Windows\\appcompat\\*.exe",
+    "?:\\Windows\\apppatch\\*.exe", "?:\\Windows\\addins\\*.exe", "?:\\Windows\\Setup\\*.exe",
+    "?:\\Windows\\Help\\*.exe", "?:\\Windows\\SKB\\*.exe", "?:\\Windows\\Vss\\*.exe",
+    "?:\\Windows\\Web\\*.exe", "?:\\Windows\\servicing\\*.exe", "?:\\Windows\\CbsTemp\\*.exe",
+    "?:\\Windows\\Logs\\*.exe", "?:\\Windows\\WaaS\\*.exe", "?:\\Windows\\ShellExperiences\\*.exe",
+    "?:\\Windows\\ShellComponents\\*.exe", "?:\\Windows\\PLA\\*.exe", "?:\\Windows\\Migration\\*.exe",
+    "?:\\Windows\\debug\\*.exe", "?:\\Windows\\Cursors\\*.exe", "?:\\Windows\\Containers\\*.exe",
+    "?:\\Windows\\Boot\\*.exe", "?:\\Windows\\bcastdvr\\*.exe", "?:\\Windows\\assembly\\*.exe",
+    "?:\\Windows\\TextInput\\*.exe", "?:\\Windows\\security\\*.exe", "?:\\Windows\\schemas\\*.exe",
+    "?:\\Windows\\SchCache\\*.exe", "?:\\Windows\\Resources\\*.exe", "?:\\Windows\\rescache\\*.exe",
+    "?:\\Windows\\Provisioning\\*.exe", "?:\\Windows\\PrintDialog\\*.exe", "?:\\Windows\\PolicyDefinitions\\*.exe",
+    "?:\\Windows\\media\\*.exe", "?:\\Windows\\Globalization\\*.exe", "?:\\Windows\\L2Schemas\\*.exe",
+    "?:\\Windows\\LiveKernelReports\\*.exe", "?:\\Windows\\ModemLogs\\*.exe",
+    "?:\\Windows\\ImmersiveControlPanel\\*.exe"
+  ) and
+  
+  not process.name : (
+    "SpeechUXWiz.exe", "SystemSettings.exe", "TrustedInstaller.exe",
+    "PrintDialog.exe", "MpSigStub.exe", "LMS.exe", "mpam-*.exe"
+  ) and
+  not process.executable :
+            ("?:\\Intel\\Wireless\\WUSetupLauncher.exe",
+             "?:\\Intel\\Wireless\\Setup.exe",
+             "?:\\Intel\\Move Mouse.exe",
+             "?:\\windows\\Panther\\DiagTrackRunner.exe",
+             "?:\\Windows\\servicing\\GC64\\tzupd.exe",
+             "?:\\Users\\Public\\res\\RemoteLite.exe",
+             "?:\\Users\\Public\\IBM\\ClientSolutions\\*.exe",
+             "?:\\Users\\Public\\Documents\\syspin.exe",
+             "?:\\Users\\Public\\res\\FileWatcher.exe")
+ /* uncomment once in winlogbeat */
+ /* and not (process.code_signature.subject_name == "Microsoft Corporation" and process.code_signature.trusted == true) */
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -113,115 +190,7 @@ winlogbeat */ /* and not (process.code_signature.subject_name ==
 ** Name: Masquerading
 ** ID: T1036
 ** Reference URL: https://attack.mitre.org/techniques/T1036/
-
-[[process-execution-from-an-unusual-directory-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-/* add suspicious execution paths here */ process.executable : ("C:\\P
-erfLogs\\*.exe","C:\\Users\\Public\\*.exe","C:\\Windows\\Tasks\\*.exe"
-,"C:\\Intel\\*.exe","C:\\AMD\\Temp\\*.exe","C:\\Windows\\AppReadiness\
-\*.exe", "C:\\Windows\\ServiceState\\*.exe","C:\\Windows\\security\\*.
-exe","C:\\Windows\\IdentityCRL\\*.exe","C:\\Windows\\Branding\\*.exe",
-"C:\\Windows\\csc\\*.exe",
-"C:\\Windows\\DigitalLocker\\*.exe","C:\\Windows\\en-US\\*.exe","C:\\W
-indows\\wlansvc\\*.exe","C:\\Windows\\Prefetch\\*.exe","C:\\Windows\\F
-onts\\*.exe", "C:\\Windows\\diagnostics\\*.exe","C:\\Windows\\TAPI\\*
-.exe","C:\\Windows\\INF\\*.exe","C:\\Windows\\System32\\Speech\\*.exe"
-,"C:\\windows\\tracing\\*.exe", "c:\\windows\\IME\\*.exe","c:\\Window
-s\\Performance\\*.exe","c:\\windows\\intel\\*.exe","c:\\windows\\ms\\*
-.exe","C:\\Windows\\dot3svc\\*.exe", "C:\\Windows\\panther\\*.exe","C
-:\\Windows\\RemotePackages\\*.exe","C:\\Windows\\OCR\\*.exe","C:\\Wind
-ows\\appcompat\\*.exe","C:\\Windows\\apppatch\\*.exe","C:\\Windows\\ad
-dins\\*.exe", "C:\\Windows\\Setup\\*.exe","C:\\Windows\\Help\\*.exe",
-"C:\\Windows\\SKB\\*.exe","C:\\Windows\\Vss\\*.exe","C:\\Windows\\Web\
-\*.exe","C:\\Windows\\servicing\\*.exe","C:\\Windows\\CbsTemp\\*.exe",
-"C:\\Windows\\Logs\\*.exe","C:\\Windows\\WaaS\\*.exe","C:\\Windows\\Sh
-ellExperiences\\*.exe","C:\\Windows\\ShellComponents\\*.exe","C:\\Wind
-ows\\PLA\\*.exe", "C:\\Windows\\Migration\\*.exe","C:\\Windows\\debug
-\\*.exe","C:\\Windows\\Cursors\\*.exe","C:\\Windows\\Containers\\*.exe
-","C:\\Windows\\Boot\\*.exe","C:\\Windows\\bcastdvr\\*.exe", "C:\\Win
-dows\\assembly\\*.exe","C:\\Windows\\TextInput\\*.exe","C:\\Windows\\s
-ecurity\\*.exe","C:\\Windows\\schemas\\*.exe","C:\\Windows\\SchCache\\
-*.exe","C:\\Windows\\Resources\\*.exe", "C:\\Windows\\rescache\\*.exe
-","C:\\Windows\\Provisioning\\*.exe","C:\\Windows\\PrintDialog\\*.exe"
-,"C:\\Windows\\PolicyDefinitions\\*.exe","C:\\Windows\\media\\*.exe",
-"C:\\Windows\\Globalization\\*.exe","C:\\Windows\\L2Schemas\\*.exe","C
-:\\Windows\\LiveKernelReports\\*.exe","C:\\Windows\\ModemLogs\\*.exe",
-"C:\\Windows\\ImmersiveControlPanel\\*.exe") and not process.name : (
-"SpeechUXWiz.exe","SystemSettings.exe","TrustedInstaller.exe","PrintDi
-alog.exe","MpSigStub.exe","LMS.exe","mpam-*.exe") and not
-process.executable :
-("?:\\Intel\\Wireless\\WUSetupLauncher.exe",
-"?:\\Intel\\Wireless\\Setup.exe", "?:\\Intel\\Move
-Mouse.exe", "?:\\windows\\Panther\\DiagTrackRunner.exe",
-"?:\\Windows\\servicing\\GC64\\tzupd.exe",
-"?:\\Users\\Public\\res\\RemoteLite.exe",
-"?:\\Users\\Public\\IBM\\ClientSolutions\\*.exe",
-"?:\\Users\\Public\\Documents\\syspin.exe",
-"?:\\Users\\Public\\res\\FileWatcher.exe") /* uncomment once in
-winlogbeat */ /* and not (process.code_signature.subject_name ==
-"Microsoft Corporation" and process.code_signature.trusted == true) */
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-/* add suspicious execution paths here */ process.executable : ("C:\\P
-erfLogs\\*.exe","C:\\Users\\Public\\*.exe","C:\\Users\\Default\\*.exe"
-,"C:\\Windows\\Tasks\\*.exe","C:\\Intel\\*.exe","C:\\AMD\\Temp\\*.exe"
-,"C:\\Windows\\AppReadiness\\*.exe", "C:\\Windows\\ServiceState\\*.exe
-","C:\\Windows\\security\\*.exe","C:\\Windows\\IdentityCRL\\*.exe","C:
-\\Windows\\Branding\\*.exe","C:\\Windows\\csc\\*.exe",
-"C:\\Windows\\DigitalLocker\\*.exe","C:\\Windows\\en-US\\*.exe","C:\\W
-indows\\wlansvc\\*.exe","C:\\Windows\\Prefetch\\*.exe","C:\\Windows\\F
-onts\\*.exe", "C:\\Windows\\diagnostics\\*.exe","C:\\Windows\\TAPI\\*
-.exe","C:\\Windows\\INF\\*.exe","C:\\Windows\\System32\\Speech\\*.exe"
-,"C:\\windows\\tracing\\*.exe", "c:\\windows\\IME\\*.exe","c:\\Window
-s\\Performance\\*.exe","c:\\windows\\intel\\*.exe","c:\\windows\\ms\\*
-.exe","C:\\Windows\\dot3svc\\*.exe","C:\\Windows\\ServiceProfiles\\*.e
-xe", "C:\\Windows\\panther\\*.exe","C:\\Windows\\RemotePackages\\*.ex
-e","C:\\Windows\\OCR\\*.exe","C:\\Windows\\appcompat\\*.exe","C:\\Wind
-ows\\apppatch\\*.exe","C:\\Windows\\addins\\*.exe", "C:\\Windows\\Set
-up\\*.exe","C:\\Windows\\Help\\*.exe","C:\\Windows\\SKB\\*.exe","C:\\W
-indows\\Vss\\*.exe","C:\\Windows\\Web\\*.exe","C:\\Windows\\servicing\
-\*.exe","C:\\Windows\\CbsTemp\\*.exe", "C:\\Windows\\Logs\\*.exe","C:
-\\Windows\\WaaS\\*.exe","C:\\Windows\\twain_32\\*.exe","C:\\Windows\\S
-hellExperiences\\*.exe","C:\\Windows\\ShellComponents\\*.exe","C:\\Win
-dows\\PLA\\*.exe", "C:\\Windows\\Migration\\*.exe","C:\\Windows\\debu
-g\\*.exe","C:\\Windows\\Cursors\\*.exe","C:\\Windows\\Containers\\*.ex
-e","C:\\Windows\\Boot\\*.exe","C:\\Windows\\bcastdvr\\*.exe", "C:\\Wi
-ndows\\assembly\\*.exe","C:\\Windows\\TextInput\\*.exe","C:\\Windows\\
-security\\*.exe","C:\\Windows\\schemas\\*.exe","C:\\Windows\\SchCache\
-\*.exe","C:\\Windows\\Resources\\*.exe", "C:\\Windows\\rescache\\*.ex
-e","C:\\Windows\\Provisioning\\*.exe","C:\\Windows\\PrintDialog\\*.exe
-","C:\\Windows\\PolicyDefinitions\\*.exe","C:\\Windows\\media\\*.exe",
-"C:\\Windows\\Globalization\\*.exe","C:\\Windows\\L2Schemas\\*.exe","C
-:\\Windows\\LiveKernelReports\\*.exe","C:\\Windows\\ModemLogs\\*.exe",
-"C:\\Windows\\ImmersiveControlPanel\\*.exe") and not process.name : (
-"SpeechUXWiz.exe","SystemSettings.exe","TrustedInstaller.exe","PrintDi
-alog.exe","MpSigStub.exe","LMS.exe","mpam-*.exe") /* uncomment once
-in winlogbeat */ /* and not (process.code_signature.subject_name ==
-"Microsoft Corporation" and process.code_signature.trusted == true) */
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/process-injection-by-the-microsoft-build-engine.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-injection-by-the-microsoft-build-engine.asciidoc
index a051cba587..48c90baf51 100644
--- a/docs/detections/prebuilt-rules/rule-details/process-injection-by-the-microsoft-build-engine.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/process-injection-by-the-microsoft-build-engine.asciidoc
@@ -5,54 +5,49 @@ An instance of MSBuild, the Microsoft Build Engine, created a thread in another
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Sysmon Only
+*Tags*: 
 
-*Version*: 101 (<<process-injection-by-the-microsoft-build-engine-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Privilege Escalation
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-The Build Engine is commonly used by Windows developers but use by non-engineers is unusual.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process.name:MSBuild.exe and event.action:"CreateRemoteThread detected
-(rule: CreateRemoteThread)"
+[source, js]
 ----------------------------------
+process.name:MSBuild.exe and host.os.type:windows and event.action:"CreateRemoteThread detected (rule: CreateRemoteThread)"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,8 +59,14 @@ process.name:MSBuild.exe and event.action:"CreateRemoteThread detected
 ** Name: Process Injection
 ** ID: T1055
 ** Reference URL: https://attack.mitre.org/techniques/T1055/
-
-
+* Technique:
+** Name: Trusted Developer Utilities Proxy Execution
+** ID: T1127
+** Reference URL: https://attack.mitre.org/techniques/T1127/
+* Sub-technique:
+** Name: MSBuild
+** ID: T1127.001
+** Reference URL: https://attack.mitre.org/techniques/T1127/001/
 * Tactic:
 ** Name: Privilege Escalation
 ** ID: TA0004
@@ -74,28 +75,3 @@ process.name:MSBuild.exe and event.action:"CreateRemoteThread detected
 ** Name: Process Injection
 ** ID: T1055
 ** Reference URL: https://attack.mitre.org/techniques/T1055/
-
-[[process-injection-by-the-microsoft-build-engine-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/process-injection-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-injection-detected-elastic-endgame.asciidoc
index 01caece0c5..a4f71a3195 100644
--- a/docs/detections/prebuilt-rules/rule-details/process-injection-detected-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/process-injection-detected-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame detected Process Injection. Click the Elastic Endgame icon in th
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,41 +13,52 @@ Elastic Endgame detected Process Injection. Click the Elastic Endgame icon in th
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<process-injection-detected-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:detection and
-(event.action:kernel_shellcode_event or
-endgame.event_subtype_full:kernel_shellcode_event)
+[source, js]
 ----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:kernel_shellcode_event or endgame.event_subtype_full:kernel_shellcode_event)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -59,35 +70,3 @@ endgame.event_subtype_full:kernel_shellcode_event)
 ** Name: Process Injection
 ** ID: T1055
 ** Reference URL: https://attack.mitre.org/techniques/T1055/
-
-[[process-injection-detected-elastic-endgame-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Formatting only
-
-Version 6 (7.12.1 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Rule name changed from: Process Injection - Detected - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Process Injection - Detected - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Process Injection - Detected - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:kernel_shellcode_event and
-endgame.metadata.type:detection
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/process-injection-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-injection-prevented-elastic-endgame.asciidoc
index e425e4a10a..922190d47c 100644
--- a/docs/detections/prebuilt-rules/rule-details/process-injection-prevented-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/process-injection-prevented-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame prevented Process Injection. Click the Elastic Endgame icon in t
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,41 +13,52 @@ Elastic Endgame prevented Process Injection. Click the Elastic Endgame icon in t
 
 *Risk score*: 47
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<process-injection-prevented-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
+
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
+
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:prevention and
-(event.action:kernel_shellcode_event or
-endgame.event_subtype_full:kernel_shellcode_event)
+[source, js]
 ----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:kernel_shellcode_event or endgame.event_subtype_full:kernel_shellcode_event)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -59,35 +70,3 @@ endgame.event_subtype_full:kernel_shellcode_event)
 ** Name: Process Injection
 ** ID: T1055
 ** Reference URL: https://attack.mitre.org/techniques/T1055/
-
-[[process-injection-prevented-elastic-endgame-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.0.0 release)::
-* Formatting only
-
-Version 6 (7.12.1 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Rule name changed from: Process Injection - Prevented - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Process Injection - Prevented - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Process Injection - Prevented - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:kernel_shellcode_event and
-endgame.metadata.type:prevention
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/process-started-from-process-id-pid-file.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-started-from-process-id-pid-file.asciidoc
index 3a16e581e0..c6aac8733a 100644
--- a/docs/detections/prebuilt-rules/rule-details/process-started-from-process-id-pid-file.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/process-started-from-process-id-pid-file.asciidoc
@@ -5,75 +5,112 @@ Identifies a new process starting from a process ID (PID), lock or reboot file w
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.sandflysecurity.com/blog/linux-file-masquerading-and-malicious-pids-sandfly-1-2-6-update/
 * https://twitter.com/GossiTheDog/status/1522964028284411907
 * https://exatrack.com/public/Tricephalic_Hellkeeper.pdf
 * https://www.elastic.co/security-labs/a-peek-behind-the-bpfdoor
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Execution
-* BPFDoor
-
-*Version*: 101 (<<process-started-from-process-id-pid-file-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Threat: BPFDoor
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Auditd Manager
 
-*Added ({stack} release)*: 8.3.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-False-Positives (FP) should be at a minimum with this detection as PID files are meant to hold process IDs, not inherently be executables that spawn processes.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Process Started from Process ID (PID) File
+*Triage and analysis*
+
+
+
+*Investigating Process Started from Process ID (PID) File*
+
 Detection alerts from this rule indicate a process spawned from an executable masqueraded as a legitimate PID file which is very unusual and should not occur. Here are some possible avenues of investigation:
 - Examine parent and child process relationships of the new process to determine if other processes are running.
 - Examine the /var/run directory using Osquery to determine other potential PID files with unsually large file sizes, indicative of it being an executable: "SELECT f.size, f.uid, f.type, f.path from file f WHERE path like '/var/run/%%';"
 - Examine the reputation of the SHA256 hash from the PID file in a database like VirusTotal to identify additional pivots and artifacts for investigation.
-----------------------------------
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and user.id == "0" and
-process.executable regex~ """/var/run/\w+\.(pid|lock|reboot)"""
+[source, js]
 ----------------------------------
+process where host.os.type == "linux" and event.type == "start" and user.id == "0" and
+  process.executable regex~ """/var/run/\w+\.(pid|lock|reboot)"""
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -85,16 +122,3 @@ process.executable regex~ """/var/run/\w+\.(pid|lock|reboot)"""
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[process-started-from-process-id-pid-file-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/process-termination-followed-by-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/process-termination-followed-by-deletion.asciidoc
index 5bbbe2cc9a..75f3afc0e4 100644
--- a/docs/detections/prebuilt-rules/rule-details/process-termination-followed-by-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/process-termination-followed-by-deletion.asciidoc
@@ -5,59 +5,133 @@ Identifies a process termination event quickly followed by the deletion of its e
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.file-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 101 (<<process-termination-followed-by-deletion-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Process Termination followed by Deletion*
+
+
+This rule identifies an unsigned process termination event quickly followed by the deletion of its executable file. Attackers can delete programs after their execution in an attempt to cover their tracks in a host.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, command line and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately, as programs that exhibit this behavior, such as installers and similar utilities, should be signed. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=5s [process where event.type ==
-"end" and process.code_signature.trusted != true and not
-process.executable : ("C:\\Windows\\SoftwareDistribution\\*.exe",
-"C:\\Windows\\WinSxS\\*.exe") ] by process.executable [file
-where event.type == "deletion" and file.extension : ("exe", "scr",
-"com") and not process.executable : ("?:\\Program
-Files\\*.exe", "?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\svchost.exe",
-"?:\\Windows\\System32\\drvinst.exe") and not file.path :
-("?:\\Program Files\\*.exe", "?:\\Program Files (x86)\\*.exe") ] by
-file.path
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=5s
+   [process where host.os.type == "windows" and event.type == "end" and
+    process.code_signature.trusted != true and
+    not process.executable : ("C:\\Windows\\SoftwareDistribution\\*.exe", "C:\\Windows\\WinSxS\\*.exe")
+   ] by process.executable
+   [file where host.os.type == "windows" and event.type == "deletion" and file.extension : ("exe", "scr", "com") and
+    not process.executable :
+             ("?:\\Program Files\\*.exe",
+              "?:\\Program Files (x86)\\*.exe",
+              "?:\\Windows\\System32\\svchost.exe",
+              "?:\\Windows\\System32\\drvinst.exe") and
+    not file.path : (
+          "?:\\Program Files\\*.exe",
+          "?:\\Program Files (x86)\\*.exe",
+          "?:\\Windows\\Temp\\*\\DismHost.exe",
+          "?:\\$WINDOWS.~BT\\Work\\*\\DismHost.exe",
+          "?:\\$WinREAgent\\Scratch\\*\\DismHost.exe",
+          "?:\\Windows\\tenable_mw_scan_*.exe",
+          "?:\\Users\\*\\AppData\\Local\\Temp\\LogiUI\\Pak\\uninstall.exe"
+    )
+   ] by file.path
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,65 +140,18 @@ file.path
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
 * Technique:
-** Name: Indicator Removal on Host
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
+* Technique:
+** Name: Indicator Removal
 ** ID: T1070
 ** Reference URL: https://attack.mitre.org/techniques/T1070/
-
-[[process-termination-followed-by-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [process where event.type ==
-"end" and process.code_signature.trusted == false and not
-process.executable : ("C:\\Windows\\SoftwareDistribution\\*.exe",
-"C:\\Windows\\WinSxS\\*.exe") ] by process.executable [file
-where event.type == "deletion" and file.extension : ("exe", "scr",
-"com") and not process.executable : ("?:\\Program
-Files\\*.exe", "?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\svchost.exe",
-"?:\\Windows\\System32\\drvinst.exe") and not file.path :
-("?:\\Program Files\\*.exe", "?:\\Program Files (x86)\\*.exe") ] by
-file.path
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [process where event.type ==
-"end" and process.code_signature.trusted == false and not
-process.executable : ("C:\\Windows\\SoftwareDistribution\\*.exe",
-"C:\\Windows\\WinSxS\\*.exe") ] by process.executable [file
-where event.type == "deletion" and file.extension : ("exe", "scr",
-"com") and not process.executable : ("?:\\Program
-Files\\*.exe", "?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\svchost.exe",
-"?:\\Windows\\System32\\drvinst.exe") and not file.path :
-("?:\\Program Files\\*.exe", "?:\\Program Files (x86)\\*.exe") ] by
-file.path
-----------------------------------
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [process where event.type ==
-"end" and process.code_signature.trusted == false and not
-process.executable : ("C:\\Windows\\SoftwareDistribution\\*.exe",
-"C:\\Windows\\WinSxS\\*.exe") ] by process.executable [file
-where event.type == "deletion" and file.extension : ("exe", "scr",
-"com")] by file.path
-----------------------------------
-
-Version 3 (7.16.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: File Deletion
+** ID: T1070.004
+** Reference URL: https://attack.mitre.org/techniques/T1070/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/processes-with-trailing-spaces.asciidoc b/docs/detections/prebuilt-rules/rule-details/processes-with-trailing-spaces.asciidoc
new file mode 100644
index 0000000000..1ffee35d2f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/processes-with-trailing-spaces.asciidoc
@@ -0,0 +1,71 @@
+[[processes-with-trailing-spaces]]
+=== Processes with Trailing Spaces
+
+Identify instances where adversaries include trailing space characters to mimic regular files, disguising their activity to evade default file handling mechanisms.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started") and
+process.name : "* "
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Space after Filename
+** ID: T1036.006
+** Reference URL: https://attack.mitre.org/techniques/T1036/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/program-files-directory-masquerading.asciidoc b/docs/detections/prebuilt-rules/rule-details/program-files-directory-masquerading.asciidoc
index ed8964b57f..cdafeb8c1f 100644
--- a/docs/detections/prebuilt-rules/rule-details/program-files-directory-masquerading.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/program-files-directory-masquerading.asciidoc
@@ -5,63 +5,76 @@ Identifies execution from a directory masquerading as the Windows Program Files
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 101 (<<program-files-directory-masquerading-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.executable :
-"C:\\*Program*Files*\\*.exe" and not process.executable :
-("C:\\Program Files\\*.exe", "C:\\Program Files (x86)\\*.exe",
-"C:\\Users\\*.exe", "C:\\ProgramData\\*.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.executable : "C:\\*Program*Files*\\*.exe" and
+  not process.executable : (
+        "?:\\Program Files\\*.exe",
+        "?:\\Program Files (x86)\\*.exe",
+        "?:\\Users\\*.exe",
+        "?:\\ProgramData\\*.exe",
+        "?:\\Windows\\Downloaded Program Files\\*.exe",
+        "?:\\Windows\\Temp\\.opera\\????????????\\CProgram?FilesOpera*\\*.exe",
+        "?:\\Windows\\Temp\\.opera\\????????????\\CProgram?Files?(x86)Opera*\\*.exe"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,43 +86,7 @@ process where event.type == "start" and process.executable :
 ** Name: Masquerading
 ** ID: T1036
 ** Reference URL: https://attack.mitre.org/techniques/T1036/
-
-[[program-files-directory-masquerading-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (7.16.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-/* capture both fake program files directory in process executable as
-well as if passed in process args as a dll*/ process.args :
-("C:\\*Program*Files*\\*", "C:\\*Program*Files*\\*") and not
-process.args : ("C:\\Program Files\\*", "C:\\Program Files (x86)\\*")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/prompt-for-credentials-with-osascript.asciidoc b/docs/detections/prebuilt-rules/rule-details/prompt-for-credentials-with-osascript.asciidoc
index c7cda5ea6f..7c3086138a 100644
--- a/docs/detections/prebuilt-rules/rule-details/prompt-for-credentials-with-osascript.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/prompt-for-credentials-with-osascript.asciidoc
@@ -5,64 +5,95 @@ Identifies the use of osascript to execute scripts via standard input that may p
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/EmpireProject/EmPyre/blob/master/lib/modules/collection/osx/prompt.py
 * https://ss64.com/osx/osascript.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 207
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Credential Access
 
-*Version*: 100 (<<prompt-for-credentials-with-osascript-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This rule requires data coming in from Elastic Defend.
 
-----------------------------------
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "osascript" and process.command_line :
-"osascript*display dialog*password*"
+[source, js]
 ----------------------------------
+process where event.action == "exec" and
+ process.name : "osascript" and process.args : "-e" and process.command_line : ("*osascript*display*dialog*password*", "*osascript*display*dialog*passphrase*") and
+ not (process.parent.executable : "/usr/bin/sudo" and process.command_line : "*Encryption Key Escrow*") and
+ not (process.command_line : "*-e with timeout of 3600 seconds*" and user.id == "0" and process.parent.executable : "/bin/bash") and
+ not process.Ext.effective_parent.executable : ("/usr/local/jamf/*", 
+                                                "/Applications/Karabiner-Elements.app/Contents/MacOS/Karabiner-Elements",
+                                                "/System/Applications/Utilities/Terminal.app/Contents/MacOS/Terminal",
+                                                "/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfDaemon.app/Contents/MacOS/JamfDaemon",
+                                                "/Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfManagementService.app/Contents/MacOS/JamfManagementService")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,29 +105,7 @@ process.name : "osascript" and process.command_line :
 ** Name: Input Capture
 ** ID: T1056
 ** Reference URL: https://attack.mitre.org/techniques/T1056/
-
-[[prompt-for-credentials-with-osascript-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name:"osascript" and process.args:"-e" and
-process.args:"password"
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: GUI Input Capture
+** ID: T1056.002
+** Reference URL: https://attack.mitre.org/techniques/T1056/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/proxychains-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/proxychains-activity.asciidoc
new file mode 100644
index 0000000000..c04e2bd113
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/proxychains-activity.asciidoc
@@ -0,0 +1,146 @@
+[[proxychains-activity]]
+=== ProxyChains Activity
+
+This rule monitors for the execution of the ProxyChains utility. ProxyChains is a command-line tool that enables the routing of network connections through intermediary proxies, enhancing anonymity and enabling access to restricted resources. Attackers can exploit the ProxyChains utility to hide their true source IP address, evade detection, and perform malicious activities through a chain of proxy servers, potentially masking their identity and intentions.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.bitsadmin.com/living-off-the-foreign-land-windows-as-offensive-platform
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating ProxyChains Activity*
+
+
+Attackers can leverage `proxychains` to obfuscate their origin and bypass network defenses by routing their malicious traffic through multiple intermediary servers.
+
+This rule looks for processes spawned through `proxychains` by analyzing `proxychains` process execution.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Identify any signs of suspicious network activity or anomalies that may indicate network obfuscation. This could include unexpected traffic patterns or unusual network behavior.
+  - Investigate listening ports and open sockets to look for potential protocol tunneling, reverse shells, or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+  - !{osquery{"label":"Osquery - Retrieve Process Info","query":"SELECT name, cmdline, parent, path, uid FROM processes"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+
+
+*Related rules*
+
+
+- Suspicious Utility Launched via ProxyChains - 6ace94ba-f02c-4d55-9f53-87d99b6f9af4
+- Potential Protocol Tunneling via Chisel Client - 3f12325a-4cc6-410b-8d4c-9fbbeb744cfd
+- Potential Protocol Tunneling via Chisel Server - ac8805f6-1e08-406c-962e-3937057fa86f
+- Potential Linux Tunneling and/or Port Forwarding - 6ee947e9-de7e-4281-a55d-09289bdf947e
+- Potential Protocol Tunneling via EarthWorm - 9f1c4ca3-44b5-481d-ba42-32dc215a2769
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator or developer who uses this utility for benign purposes, consider adding exceptions for specific user accounts or hosts. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors, such as reverse shells, reverse proxies, or droppers, that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "proxychains"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Protocol Tunneling
+** ID: T1572
+** Reference URL: https://attack.mitre.org/techniques/T1572/
diff --git a/docs/detections/prebuilt-rules/rule-details/psexec-network-connection.asciidoc b/docs/detections/prebuilt-rules/rule-details/psexec-network-connection.asciidoc
index b55fa21ea2..ad8af0b646 100644
--- a/docs/detections/prebuilt-rules/rule-details/psexec-network-connection.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/psexec-network-connection.asciidoc
@@ -5,116 +5,111 @@ Identifies use of the SysInternals tool PsExec.exe making a network connection.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<psexec-network-connection-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Lateral Movement
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-PsExec is a dual-use tool that can be used for benign or malicious activity. It's important to baseline your environment to determine the amount of noise to expect from this tool.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating PsExec Network Connection
+*Triage and analysis*
+
+
 
-PsExec is a remote administration tool that enables the execution of commands with both regular and SYSTEM privileges
-on Windows systems. Microsoft develops it as part of the Sysinternals Suite. Although commonly used by administrators,
-PsExec is frequently used by attackers to enable lateral movement and execute commands as SYSTEM to disable defenses and
-bypass security protections.
+*Investigating PsExec Network Connection*
 
-This rule identifies PsExec execution by looking for the creation of `PsExec.exe`, the default name for the
-utility, followed by a network connection done by the process.
 
-#### Possible investigation steps
+PsExec is a remote administration tool that enables the execution of commands with both regular and SYSTEM privileges on Windows systems. Microsoft develops it as part of the Sysinternals Suite. Although commonly used by administrators, PsExec is frequently used by attackers to enable lateral movement and execute commands as SYSTEM to disable defenses and bypass security protections.
+
+This rule identifies PsExec execution by looking for the creation of `PsExec.exe`, the default name for the utility, followed by a network connection done by the process.
+
+
+*Possible investigation steps*
+
 
 - Check if the usage of this tool complies with the organization's administration policy.
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Identify the target computer and its role in the IT environment.
-- Investigate what commands were run, and assess whether this behavior is prevalent in the environment by looking for
-similar occurrences across hosts.
+- Investigate what commands were run, and assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+
+
+*False positive analysis*
 
-### False positive analysis
 
-- This mechanism can be used legitimately. As long as the analyst did not identify suspicious activity related to the
-user or involved hosts, and the tool is allowed by the organization's policy, such alerts can be dismissed.
+- This mechanism can be used legitimately. As long as the analyst did not identify suspicious activity related to the user or involved hosts, and the tool is allowed by the organization's policy, such alerts can be dismissed.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
-  - Prioritize accordingly with the role of the servers and users involved.
+  - Prioritize cases involving critical servers and users.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system,
-persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 - Review the privileges assigned to the user to ensure that the least privilege principle is being followed.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where process.name :
-"PsExec.exe" and event.type == "start" and /* This flag suppresses
-the display of the license dialog and may indicate that psexec
-executed for the first time in the machine */ process.args :
-"-accepteula" and not process.executable : ("?:\\ProgramData\\Docu
-snap\\Discovery\\discovery\\plugins\\17\\Bin\\psexec.exe",
-"?:\\Docusnap 11\\Bin\\psexec.exe",
-"?:\\Program Files\\Docusnap X\\Bin\\psexec.exe",
-"?:\\Program Files\\Docusnap X\\Tools\\dsDNS.exe") and not
-process.parent.executable : "?:\\Program Files (x86)\\Cynet\\Cynet
-Scanner\\CynetScanner.exe"] [network where process.name :
-"PsExec.exe"]
+[source, js]
 ----------------------------------
+sequence by process.entity_id
+  [process where host.os.type == "windows" and process.name : "PsExec.exe" and event.type == "start" and
 
-==== Threat mapping
+   /* This flag suppresses the display of the license dialog and may
+      indicate that psexec executed for the first time in the machine */
+   process.args : "-accepteula" and
+
+   not process.executable : ("?:\\ProgramData\\Docusnap\\Discovery\\discovery\\plugins\\17\\Bin\\psexec.exe",
+                             "?:\\Docusnap 11\\Bin\\psexec.exe",
+                             "?:\\Program Files\\Docusnap X\\Bin\\psexec.exe",
+                             "?:\\Program Files\\Docusnap X\\Tools\\dsDNS.exe") and
+   not process.parent.executable : "?:\\Program Files (x86)\\Cynet\\Cynet Scanner\\CynetScanner.exe"]
+  [network where host.os.type == "windows" and process.name : "PsExec.exe"]
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -126,65 +121,23 @@ Scanner\\CynetScanner.exe"] [network where process.name :
 ** Name: System Services
 ** ID: T1569
 ** Reference URL: https://attack.mitre.org/techniques/T1569/
-
-
+* Sub-technique:
+** Name: Service Execution
+** ID: T1569.002
+** Reference URL: https://attack.mitre.org/techniques/T1569/002/
 * Tactic:
 ** Name: Lateral Movement
 ** ID: TA0008
 ** Reference URL: https://attack.mitre.org/tactics/TA0008/
-
-[[psexec-network-connection-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where process.name :
-"PsExec.exe" and event.type == "start"] [network where process.name
-: "PsExec.exe"]
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:connection and
-process.name:PsExec.exe
-----------------------------------
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:PsExec.exe and event.action:"Network connection detected
-(rule: NetworkConnect)"
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:PsExec.exe and event.action:"Network connection detected
-(rule: NetworkConnect)"
-----------------------------------
-
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
+* Technique:
+** Name: Lateral Tool Transfer
+** ID: T1570
+** Reference URL: https://attack.mitre.org/techniques/T1570/
diff --git a/docs/detections/prebuilt-rules/rule-details/python-script-execution-via-command-line.asciidoc b/docs/detections/prebuilt-rules/rule-details/python-script-execution-via-command-line.asciidoc
new file mode 100644
index 0000000000..0d369b4d51
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/python-script-execution-via-command-line.asciidoc
@@ -0,0 +1,85 @@
+[[python-script-execution-via-command-line]]
+=== Python Script Execution via Command Line
+
+Identifies when a Python script is executed using command line input and imports the sys module. Attackers often use this method to execute malicious scripts and avoiding writing it to disk.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type in ("start", "process_started") and
+ process.name : "python*" and process.args : "-c" and process.args : "*import*sys*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Python
+** ID: T1059.006
+** Reference URL: https://attack.mitre.org/techniques/T1059/006/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/quarantine-attrib-removed-by-unsigned-or-untrusted-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/quarantine-attrib-removed-by-unsigned-or-untrusted-process.asciidoc
new file mode 100644
index 0000000000..4663d1f26a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/quarantine-attrib-removed-by-unsigned-or-untrusted-process.asciidoc
@@ -0,0 +1,110 @@
+[[quarantine-attrib-removed-by-unsigned-or-untrusted-process]]
+=== Quarantine Attrib Removed by Unsigned or Untrusted Process
+
+Detects deletion of the quarantine attribute by an unusual process (xattr). In macOS, when applications or programs are downloaded from the internet, there is a quarantine flag set on the file. This attribute is read by Apple's Gatekeeper defense program at execution time. An adversary may disable this attribute to evade defenses.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://nixhacker.com/security-protection-in-macos-1/
+* https://eclecticlight.co/2020/10/29/quarantine-and-the-quarantine-flag/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 108
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where event.action == "extended_attributes_delete" and process.executable != null and
+(process.code_signature.trusted == false or process.code_signature.exists == false) and not
+process.executable : ("/usr/bin/xattr", 
+                      "/System/*", 
+                      "/private/tmp/KSInstallAction.*/*/Install Google Software Update.app/Contents/Helpers/ksinstall",
+                      "/Applications/CEWE Fotoschau.app/Contents/MacOS/FotoPlus",
+                      "/Applications/.com.bomgar.scc.*/Remote Support Customer Client.app/Contents/MacOS/sdcust") and not
+file.path : "/private/var/folders/*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/query-registry-using-built-in-tools.asciidoc b/docs/detections/prebuilt-rules/rule-details/query-registry-using-built-in-tools.asciidoc
new file mode 100644
index 0000000000..8befaae1cd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/query-registry-using-built-in-tools.asciidoc
@@ -0,0 +1,77 @@
+[[query-registry-using-built-in-tools]]
+=== Query Registry using Built-in Tools
+
+This rule identifies the execution of commands that can be used to query the Windows Registry. Adversaries may query the registry to gain situational awareness about the host, like installed security software, programs and settings.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 24h
+
+*Searches indices from*: now-24h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 105
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:windows and event.category:process and event.type:start and
+  (
+    (process.name.caseless:"reg.exe" and process.args:"query") or
+    (process.name.caseless:("powershell.exe" or "powershell_ise.exe" or "pwsh.exe") and
+     process.args:(
+       ("get-childitem" or "Get-ChildItem" or "gci" or "dir" or "ls" or
+        "get-item" or "Get-Item" or "gi" or
+        "get-itemproperty" or "Get-ItemProperty" or "gp") and
+       ("hkcu" or "HKCU" or "hkey_current_user" or "HKEY_CURRENT_USER" or
+        "hkey_local_machine" or "HKEY_LOCAL_MACHINE" or
+        "hklm" or "HKLM" or registry\:\:*)
+      )
+    )
+  ) and
+  not process.command_line : (
+    "C:\\Windows\\system32\\reg.exe  query hklm\\software\\microsoft\\windows\\softwareinventorylogging /v collectionstate /reg:64" or
+    "reg  query \"HKLM\\Software\\WOW6432Node\\Npcap\" /ve  "
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Query Registry
+** ID: T1012
+** Reference URL: https://attack.mitre.org/techniques/T1012/
diff --git a/docs/detections/prebuilt-rules/rule-details/ransomware-detected-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/ransomware-detected-elastic-endgame.asciidoc
index d3d39402bd..138948c752 100644
--- a/docs/detections/prebuilt-rules/rule-details/ransomware-detected-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/ransomware-detected-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame detected ransomware. Click the Elastic Endgame icon in the event
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,65 +13,47 @@ Elastic Endgame detected ransomware. Click the Elastic Endgame icon in the event
 
 *Risk score*: 99
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 100 (<<ransomware-detected-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
+
+==== Setup
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:detection and (event.action:ransomware_event or
-endgame.event_subtype_full:ransomware_event)
-----------------------------------
 
+*Setup*
 
-[[ransomware-detected-elastic-endgame-history]]
-==== Rule version history
 
-Version 100 (8.5.0 release)::
-* Formatting only
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
 
-Version 9 (8.4.0 release)::
-* Formatting only
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
 
-Version 8 (8.0.0 release)::
-* Formatting only
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
 
-Version 6 (7.12.1 release)::
-* Formatting only
 
-Version 5 (7.12.0 release)::
-* Rule name changed from: Ransomware - Detected - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Ransomware - Detected - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Ransomware - Detected - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:ransomware_event and endgame.metadata.type:detection
-----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:detection and (event.action:ransomware_event or endgame.event_subtype_full:ransomware_event)
 
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/ransomware-prevented-elastic-endgame.asciidoc b/docs/detections/prebuilt-rules/rule-details/ransomware-prevented-elastic-endgame.asciidoc
index 483fa6bb1b..f35e70acf7 100644
--- a/docs/detections/prebuilt-rules/rule-details/ransomware-prevented-elastic-endgame.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/ransomware-prevented-elastic-endgame.asciidoc
@@ -5,7 +5,7 @@ Elastic Endgame prevented ransomware. Click the Elastic Endgame icon in the even
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * endgame-*
 
@@ -13,65 +13,47 @@ Elastic Endgame prevented ransomware. Click the Elastic Endgame icon in the even
 
 *Risk score*: 73
 
-*Runs every*: 10 minutes
+*Runs every*: 10m
 
 *Searches indices from*: now-15m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 10000
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 100 (<<ransomware-prevented-elastic-endgame-history, version history>>)
+* Data Source: Elastic Endgame
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Rule query
+
+==== Setup
 
 
-[source,js]
-----------------------------------
-event.kind:alert and event.module:endgame and
-endgame.metadata.type:prevention and (event.action:ransomware_event or
-endgame.event_subtype_full:ransomware_event)
-----------------------------------
 
+*Setup*
 
-[[ransomware-prevented-elastic-endgame-history]]
-==== Rule version history
 
-Version 100 (8.5.0 release)::
-* Formatting only
+This rule is configured to generate more **Max alerts per run** than the default 1000 alerts per run set for all rules. This is to ensure that it captures as many alerts as possible.
 
-Version 9 (8.4.0 release)::
-* Formatting only
+**IMPORTANT:** The rule's **Max alerts per run** setting can be superseded by the `xpack.alerting.rules.run.alerts.max` Kibana config setting, which determines the maximum alerts generated by _any_ rule in the Kibana alerting framework. For example, if `xpack.alerting.rules.run.alerts.max` is set to 1000, this rule will still generate no more than 1000 alerts even if its own **Max alerts per run** is set higher.
 
-Version 8 (8.0.0 release)::
-* Formatting only
+To make sure this rule can generate as many alerts as it's configured in its own **Max alerts per run** setting, increase the `xpack.alerting.rules.run.alerts.max` system setting accordingly.
+
+**NOTE:** Changing `xpack.alerting.rules.run.alerts.max` is not possible in Serverless projects.
+
+==== Rule query
 
-Version 6 (7.12.1 release)::
-* Formatting only
 
-Version 5 (7.12.0 release)::
-* Rule name changed from: Ransomware - Prevented - Endpoint Security
-Version 4 (7.10.0 release)::
-* Rule name changed from: Ransomware - Prevented - Elastic Endpoint Security
-Version 3 (7.9.0 release)::
-* Rule name changed from: Ransomware - Prevented - Elastic Endpoint
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.kind:alert and event.module:endgame and
-event.action:ransomware_event and endgame.metadata.type:prevention
-----------------------------------
+event.kind:alert and event.module:endgame and endgame.metadata.type:prevention and (event.action:ransomware_event or endgame.event_subtype_full:ransomware_event)
 
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/rare-aws-error-code.asciidoc b/docs/detections/prebuilt-rules/rule-details/rare-aws-error-code.asciidoc
index 33f1bd465a..fded439e4e 100644
--- a/docs/detections/prebuilt-rules/rule-details/rare-aws-error-code.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/rare-aws-error-code.asciidoc
@@ -5,102 +5,93 @@ A machine learning job detected an unusual error in a CloudTrail message. These
 
 *Rule type*: machine_learning
 
-*Machine learning job*: rare_error_code
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-2h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Resources: Investigation Guide
+
+*Version*: 208
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* ML
-* Investigation Guide
 
-*Version*: 102 (<<rare-aws-error-code-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Rare and unusual errors may indicate an impending service failure state. Rare and unusual user error activity can also be due to manual troubleshooting or reconfiguration attempts by insufficiently privileged users, bugs in cloud automation scripts or workflows, or changes to IAM privileges.
 
-==== Investigation guide
+
+*Investigating Rare AWS Error Code*
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+CloudTrail logging provides visibility on actions taken within an AWS environment. By monitoring these events and understanding what is considered normal behavior within an organization, you can spot suspicious or malicious activity when deviations occur.
 
-### Investigating Rare AWS Error Code
+This rule uses a machine learning job to detect an unusual error in a CloudTrail message. This can be byproducts of attempted or successful persistence, privilege escalation, defense evasion, discovery, lateral movement, or collection.
 
-CloudTrail logging provides visibility on actions taken within an AWS environment. By monitoring these events and
-understanding what is considered normal behavior within an organization, you can spot suspicious or malicious activity
-when deviations occur.
+Detection alerts from this rule indicate a rare and unusual error code that was associated with the response to an AWS API command or method call.
 
-This rule uses a machine learning job to detect an unusual error in a CloudTrail message. This can be byproducts of
-attempted or successful persistence, privilege escalation, defense evasion, discovery, lateral movement, or collection.
 
-Detection alerts from this rule indicate a rare and unusual error code that was associated with the response to an AWS
-API command or method call.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Examine the history of the error. If the error only manifested recently, it might be related to recent changes in an
-automation module or script. You can find the error in the `aws.cloudtrail.error_code field` field.
+- Examine the history of the error. If the error only manifested recently, it might be related to recent changes in an automation module or script. You can find the error in the `aws.cloudtrail.error_code field` field.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Validate the activity is not related to planned patches, updates, or network administrator activity.
-- Examine the request parameters. These may indicate the source of the program or the nature of the task being performed
-when the error occurred.
+- Examine the request parameters. These may indicate the source of the program or the nature of the task being performed when the error occurred.
     - Check whether the error is related to unsuccessful attempts to enumerate or access objects, data, or secrets.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the calling user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
-- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal
-time of day?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
+- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal time of day?
 - Contact the account owner and confirm whether they are aware of this activity if suspicious.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
 
-### False positive analysis
 
-- Examine the history of the command. If the command only manifested recently, it might be part of a new automation
-module or script. If it has a consistent cadence (for example, it appears in small numbers on a weekly or monthly cadence),
-it might be part of a housekeeping or maintenance process. You can find the command in the `event.action field` field.
+*False positive analysis*
+
+
+- Examine the history of the command. If the command only manifested recently, it might be part of a new automation module or script. If it has a consistent cadence (for example, it appears in small numbers on a weekly or monthly cadence), it might be part of a housekeeping or maintenance process. You can find the command in the `event.action field` field.
 - The adoption of new services or the addition of new functionality to scripts may generate false positives.
 
-### Related Rules
+
+*Related Rules*
+
 
 - Unusual City For an AWS Command - 809b70d3-e2c3-455e-af1b-2626a5a1a276
 - Unusual Country For an AWS Command - dca28dee-c999-400f-b640-50a081cc0fd1
 - Unusual AWS Command for a User - ac706eae-d5ec-4b14-b4fd-e8ba8086f0e1
 - Spike in AWS Error Messages - 78d3d8d9-b476-451d-a9e0-7a5addd70670
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -110,47 +101,16 @@ it might be part of a housekeeping or maintenance process. You can find the comm
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
-
-
-[[rare-aws-error-code-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (7.16.0 release)::
-* Formatting only
-
-Version 6 (7.15.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 3 (7.12.0 release)::
-* Formatting only
+==== Setup
 
-Version 2 (7.10.0 release)::
-* Formatting only
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
diff --git a/docs/detections/prebuilt-rules/rule-details/rare-smb-connection-to-the-internet.asciidoc b/docs/detections/prebuilt-rules/rule-details/rare-smb-connection-to-the-internet.asciidoc
new file mode 100644
index 0000000000..fe86f6fa54
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/rare-smb-connection-to-the-internet.asciidoc
@@ -0,0 +1,100 @@
+[[rare-smb-connection-to-the-internet]]
+=== Rare SMB Connection to the Internet
+
+This rule detects rare internet network connections via the SMB protocol. SMB is commonly used to leak NTLM credentials via rogue UNC path injection.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.network-*
+* winlogbeat-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.securify.nl/en/blog/living-off-the-land-stealing-netntlm-hashes/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Exfiltration
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:network and host.os.type:windows and process.pid:4 and 
+  network.transport:tcp and destination.port:(139 or 445) and 
+  source.ip:(
+    10.0.0.0/8 or
+    172.16.0.0/12 or
+    192.168.0.0/16
+  ) and
+  not destination.ip:(
+    10.0.0.0/8 or
+    127.0.0.0/8 or
+    169.254.0.0/16 or
+    172.16.0.0/12 or
+    192.0.0.0/24 or
+    192.0.0.0/29 or
+    192.0.0.8/32 or
+    192.0.0.9/32 or
+    192.0.0.10/32 or
+    192.0.0.170/32 or
+    192.0.0.171/32 or
+    192.0.2.0/24 or
+    192.31.196.0/24 or
+    192.52.193.0/24 or
+    192.168.0.0/16 or
+    192.88.99.0/24 or
+    224.0.0.0/4 or
+    100.64.0.0/10 or
+    192.175.48.0/24 or
+    198.18.0.0/15 or
+    198.51.100.0/24 or
+    203.0.113.0/24 or
+    240.0.0.0/4 or
+    "::1" or
+    "FE80::/10" or
+    "FF00::/8"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over Alternative Protocol
+** ID: T1048
+** Reference URL: https://attack.mitre.org/techniques/T1048/
diff --git a/docs/detections/prebuilt-rules/rule-details/rare-user-logon.asciidoc b/docs/detections/prebuilt-rules/rule-details/rare-user-logon.asciidoc
index 949e8cdf0c..33ed485149 100644
--- a/docs/detections/prebuilt-rules/rule-details/rare-user-logon.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/rare-user-logon.asciidoc
@@ -5,47 +5,76 @@ A machine learning job found an unusual user name in the authentication logs. An
 
 *Rule type*: machine_learning
 
-*Machine learning job*: auth_rare_user
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Initial Access
+* Resources: Investigation Guide
+
+*Version*: 104
+
+*Rule authors*: 
 
 * Elastic
-* Authentication
-* Threat Detection
-* ML
-* Initial Access
 
-*Version*: 100 (<<rare-user-logon-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.14.0
+==== Investigation guide
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Triage and analysis*
+
+
+
+*Investigating Rare User Logon*
+
+
+This rule uses a machine learning job to detect an unusual user name in authentication logs, which could detect new accounts created for persistence.
+
+
+*Possible investigation steps*
 
-==== Potential false positives
 
-User accounts that are rarely active, such as a site reliability engineer (SRE) or developer logging into a production server for troubleshooting, may trigger this alert. Under some conditions, a newly created user account may briefly trigger this alert while the model is learning.
-==== Threat mapping
+- Check if the user was newly created and if the company policies were followed.
+  - Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate other alerts associated with the involved users during the past 48 hours.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+
+
+*False positive analysis*
+
+
+- Accounts that are used for specific purposes — and therefore not normally active — may trigger the alert.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -57,19 +86,11 @@ User accounts that are rarely active, such as a site reliability engineer (SRE)
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[rare-user-logon-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 3 (7.16.0 release)::
-* Formatting only
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Domain Accounts
+** ID: T1078.002
+** Reference URL: https://attack.mitre.org/techniques/T1078/002/
+* Sub-technique:
+** Name: Local Accounts
+** ID: T1078.003
+** Reference URL: https://attack.mitre.org/techniques/T1078/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/rdp-enabled-via-registry.asciidoc b/docs/detections/prebuilt-rules/rule-details/rdp-enabled-via-registry.asciidoc
index 05a786c1e2..7d599eb710 100644
--- a/docs/detections/prebuilt-rules/rule-details/rdp-enabled-via-registry.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/rdp-enabled-via-registry.asciidoc
@@ -5,77 +5,85 @@ Identifies registry write modifications to enable Remote Desktop Protocol (RDP)
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<rdp-enabled-via-registry-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating RDP Enabled via Registry
+*Triage and analysis*
+
+
 
-Microsoft Remote Desktop Protocol (RDP) is a proprietary Microsoft protocol that enables remote connections to other
-computers, typically over TCP port 3389.
+*Investigating RDP Enabled via Registry*
 
-Attackers can use RDP to conduct their actions interactively. Ransomware operators frequently use RDP to access
-victim servers, often using privileged accounts.
 
-This rule detects modification of the fDenyTSConnections registry key to the value `0`, which specifies that remote
-desktop connections are enabled. Attackers can abuse remote registry, use psexec, etc., to enable RDP and move laterally.
+Microsoft Remote Desktop Protocol (RDP) is a proprietary Microsoft protocol that enables remote connections to other computers, typically over TCP port 3389.
+
+Attackers can use RDP to conduct their actions interactively. Ransomware operators frequently use RDP to access victim servers, often using privileged accounts.
+
+This rule detects modification of the fDenyTSConnections registry key to the value `0`, which specifies that remote desktop connections are enabled. Attackers can abuse remote registry, use psexec, etc., to enable RDP and move laterally.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the user to check if they are aware of the operation.
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Check whether it makes sense to enable RDP to this host, given its role in the environment.
 - Check if the host is directly exposed to the internet.
 - Check whether privileged accounts accessed the host shortly after the modification.
 - Review network events within a short timespan of this alert for incoming RDP connection attempts.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Check whether the user should be performing this kind of activity, whether
-they are aware of it, whether RDP should be open, and whether the action exposes the environment to unnecessary risks.
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Check whether the user should be performing this kind of activity, whether they are aware of it, whether RDP should be open, and whether the action exposes the environment to unnecessary risks.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - If RDP is needed, make sure to secure it using firewall rules:
@@ -84,25 +92,40 @@ they are aware of it, whether RDP should be open, and whether the action exposes
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-registry.path : "HKLM\\SYSTEM\\*ControlSet*\\Control\\Terminal
-Server\\fDenyTSConnections" and registry.data.strings : ("0",
-"0x00000000") and not (process.name : "svchost.exe" and user.domain ==
-"NT AUTHORITY") and not process.executable :
-"C:\\Windows\\System32\\SystemPropertiesRemote.exe"
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and 
+ event.type in ("creation", "change") and
+  registry.path : "HKLM\\SYSTEM\\*ControlSet*\\Control\\Terminal Server\\fDenyTSConnections" and
+  registry.data.strings : ("0", "0x00000000") and
+  not process.executable : ("?:\\Windows\\System32\\SystemPropertiesRemote.exe", 
+                            "?:\\Windows\\System32\\SystemPropertiesComputerName.exe", 
+                            "?:\\Windows\\System32\\SystemPropertiesAdvanced.exe", 
+                            "?:\\Windows\\System32\\SystemSettingsAdminFlows.exe", 
+                            "?:\\Windows\\WinSxS\\*\\TiWorker.exe", 
+                            "?:\\Windows\\system32\\svchost.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -114,44 +137,15 @@ Server\\fDenyTSConnections" and registry.data.strings : ("0",
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[rdp-enabled-via-registry-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.3.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path :
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Terminal
-Server\\fDenyTSConnections" and registry.data.strings == "0" and not
-(process.name : "svchost.exe" and user.domain == "NT AUTHORITY") and
-not process.executable :
-"C:\\Windows\\System32\\SystemPropertiesRemote.exe"
-----------------------------------
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Remote Desktop Protocol
+** ID: T1021.001
+** Reference URL: https://attack.mitre.org/techniques/T1021/001/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/rdp-remote-desktop-protocol-from-the-internet.asciidoc b/docs/detections/prebuilt-rules/rule-details/rdp-remote-desktop-protocol-from-the-internet.asciidoc
index d46854d65f..2df719f2b5 100644
--- a/docs/detections/prebuilt-rules/rule-details/rdp-remote-desktop-protocol-from-the-internet.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/rdp-remote-desktop-protocol-from-the-internet.asciidoc
@@ -5,70 +5,84 @@ This rule detects network events that may indicate the use of RDP traffic from t
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Network
-* Threat Detection
-* Command and Control
-* Host
+* Tactic: Command and Control
+* Domain: Endpoint
+* Use Case: Threat Detection
 
-*Version*: 100 (<<rdp-remote-desktop-protocol-from-the-internet-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.6.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Some network security policies allow RDP directly from the Internet but usage that is unfamiliar to server or network owners can be unexpected and suspicious. RDP services may be exposed directly to the Internet in some networks such as cloud environments. In such cases, only RDP gateways, bastions or jump servers may be expected expose RDP directly to the Internet and can be exempted from this rule. RDP may be required by some work-flows such as remote access and support for specialized software products and servers. Such work-flows are usually known and not unexpected.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:3389 or event.dataset:zeek.rdp) and not
-source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
-172.16.0.0/12 or 192.0.0.0/24 or 192.0.0.0/29 or
-192.0.0.8/32 or 192.0.0.9/32 or 192.0.0.10/32 or
-192.0.0.170/32 or 192.0.0.171/32 or 192.0.2.0/24 or
-192.31.196.0/24 or 192.52.193.0/24 or 192.168.0.0/16 or
-192.88.99.0/24 or 224.0.0.0/4 or 100.64.0.0/10 or
-192.175.48.0/24 or 198.18.0.0/15 or 198.51.100.0/24 or
-203.0.113.0/24 or 240.0.0.0/4 or "::1" or "FE80::/10" or
-"FF00::/8" ) and destination.ip:( 10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16 )
+[source, js]
 ----------------------------------
+(event.dataset: network_traffic.flow or (event.category: (network or network_traffic))) and
+  network.transport:tcp and (destination.port:3389 or event.dataset:zeek.rdp) and
+  not source.ip:(
+    10.0.0.0/8 or
+    127.0.0.0/8 or
+    169.254.0.0/16 or
+    172.16.0.0/12 or
+    192.0.0.0/24 or
+    192.0.0.0/29 or
+    192.0.0.8/32 or
+    192.0.0.9/32 or
+    192.0.0.10/32 or
+    192.0.0.170/32 or
+    192.0.0.171/32 or
+    192.0.2.0/24 or
+    192.31.196.0/24 or
+    192.52.193.0/24 or
+    192.168.0.0/16 or
+    192.88.99.0/24 or
+    224.0.0.0/4 or
+    100.64.0.0/10 or
+    192.175.48.0/24 or
+    198.18.0.0/15 or
+    198.51.100.0/24 or
+    203.0.113.0/24 or
+    240.0.0.0/4 or
+    "::1" or
+    "FE80::/10" or
+    "FF00::/8"
+  ) and
+  destination.ip:(
+    10.0.0.0/8 or
+    172.16.0.0/12 or
+    192.168.0.0/16
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,8 +90,6 @@ source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
 ** Name: Command and Control
 ** ID: TA0011
 ** Reference URL: https://attack.mitre.org/tactics/TA0011/
-
-
 * Tactic:
 ** Name: Lateral Movement
 ** ID: TA0008
@@ -86,8 +98,6 @@ source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -96,81 +106,3 @@ source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[rdp-remote-desktop-protocol-from-the-internet-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 15 (8.4.0 release)::
-* Formatting only
-
-Version 14 (8.3.0 release)::
-* Formatting only
-
-Version 12 (8.2.0 release)::
-* Formatting only
-
-Version 11 (7.15.0 release)::
-* Formatting only
-
-Version 10 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:3389 or event.dataset:zeek.rdp) and not
-source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
-172.16.0.0/12 or 192.168.0.0/16 or 224.0.0.0/4 or "::1" or "FE80::/10"
-or "FF00::/8" ) and destination.ip:( 10.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 )
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:3389 or event.dataset:zeek.rdp) and not
-source.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) and
-destination.ip:(10.0.0.0/8 or 127.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 or "::1")
-----------------------------------
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport:tcp and destination.port:3389 and not
-source.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) and
-destination.ip:(10.0.0.0/8 or 127.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 or "::1")
-----------------------------------
-
-Version 3 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport: tcp and destination.port: 3389 and (
-network.direction: inbound or ( not source.ip: (10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16) and destination.ip: (10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16) ) )
-----------------------------------
-
-Version 2 (7.6.1 release)::
-* Removed auditbeat-\*, packetbeat-*, and winlogbeat-* from the rule indices.
-
diff --git a/docs/detections/prebuilt-rules/rule-details/registry-persistence-via-appcert-dll.asciidoc b/docs/detections/prebuilt-rules/rule-details/registry-persistence-via-appcert-dll.asciidoc
index 728ad44633..b1b68ca898 100644
--- a/docs/detections/prebuilt-rules/rule-details/registry-persistence-via-appcert-dll.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/registry-persistence-via-appcert-dll.asciidoc
@@ -5,60 +5,72 @@ Detects attempts to maintain persistence by creating registry keys using AppCert
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 100 (<<registry-persistence-via-appcert-dll-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where /* uncomment once stable length(bytes_written_string) >
-0 and */ registry.path :
-"HKLM\\SYSTEM\\*ControlSet*\\Control\\Session Manager\\AppCertDLLs\\*"
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and
+/* uncomment once stable length(bytes_written_string) > 0 and */
+  registry.path : (
+    "HKLM\\SYSTEM\\*ControlSet*\\Control\\Session Manager\\AppCertDLLs\\*",
+    "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Control\\Session Manager\\AppCertDLLs\\*"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,32 +82,19 @@ registry where /* uncomment once stable length(bytes_written_string) >
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[registry-persistence-via-appcert-dll-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where /* uncomment once stable length(bytes_written_string) >
-0 and */ registry.path :
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Session Manager\\AppCertDLLs\\*"
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: AppCert DLLs
+** ID: T1546.009
+** Reference URL: https://attack.mitre.org/techniques/T1546/009/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: AppCert DLLs
+** ID: T1546.009
+** Reference URL: https://attack.mitre.org/techniques/T1546/009/
diff --git a/docs/detections/prebuilt-rules/rule-details/registry-persistence-via-appinit-dll.asciidoc b/docs/detections/prebuilt-rules/rule-details/registry-persistence-via-appinit-dll.asciidoc
index 4618f979af..25b6195543 100644
--- a/docs/detections/prebuilt-rules/rule-details/registry-persistence-via-appinit-dll.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/registry-persistence-via-appinit-dll.asciidoc
@@ -1,69 +1,155 @@
 [[registry-persistence-via-appinit-dll]]
 === Registry Persistence via AppInit DLL
 
-Attackers may maintain persistence by creating registry keys using AppInit DLLs. AppInit DLLs are loaded by every process using the common library, user32.dll.
+AppInit DLLs are dynamic-link libraries (DLLs) that are loaded into every process that creates a user interface (loads user32.dll) on Microsoft Windows operating systems. The AppInit DLL mechanism is used to load custom code into user-mode processes, allowing for the customization of the user interface and the behavior of Windows-based applications. Attackers who add those DLLs to the registry locations can execute code with elevated privileges, similar to process injection, and provide a solid and constant persistence on the machine.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 100 (<<registry-persistence-via-appinit-dll-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating Registry Persistence via AppInit DLL*
+
+
+AppInit DLLs are dynamic-link libraries (DLLs) that are loaded into every process that creates a user interface (loads `user32.dll`) on Microsoft Windows operating systems. The AppInit DLL mechanism is used to load custom code into user-mode processes, allowing for the customization of the user interface and the behavior of Windows-based applications.
+
+Attackers who add those DLLs to the registry locations can execute code with elevated privileges, similar to process injection, and provide a solid and constant persistence on the machine.
+
+This rule identifies modifications on the AppInit registry keys.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Review the source process and related DLL file tied to the Windows Registry entry.
+  - Check whether the DLL is signed, and tied to a authorized program used on your environment.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Retrieve all DLLs under the AppInit registry keys:
+  - !{osquery{"label":"Osquery - Retrieve AppInit Registry Value","query":"SELECT * FROM registry r where (r.key == 'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Windows' or\nr.key == 'HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows NT\\CurrentVersion\\Windows') and r.name ==\n'AppInit_DLLs'\n"}}
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable and the DLLs using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.path : ("HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\AppInit_Dlls",
-"HKLM\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\AppInit_Dlls") and not
-process.executable : ("C:\\Windows\\System32\\msiexec.exe",
-"C:\\Windows\\SysWOW64\\msiexec.exe",
-"C:\\Program Files\\Commvault\\ContentStore*\\Base\\cvd.exe",
-"C:\\Program Files (x86)\\Commvault\\ContentStore*\\Base\\cvd.exe")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and
+  registry.path : (
+     "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Windows\\AppInit_Dlls",
+     "HKLM\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows NT\\CurrentVersion\\Windows\\AppInit_Dlls",
+     "\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Windows\\AppInit_Dlls",
+     "\\REGISTRY\\MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows NT\\CurrentVersion\\Windows\\AppInit_Dlls"
+  ) and
+  not process.executable : (
+     "?:\\Windows\\System32\\DriverStore\\FileRepository\\*\\Display.NvContainer\\NVDisplay.Container.exe",
+     "?:\\Windows\\System32\\msiexec.exe",
+     "?:\\Windows\\SysWOW64\\msiexec.exe",
+     "?:\\Program Files\\Commvault\\Base\\cvd.exe",
+     "?:\\Program Files\\Commvault\\ContentStore*\\Base\\cvd.exe",
+     "?:\\Program Files (x86)\\Commvault\\Base\\cvd.exe",
+     "?:\\Program Files (x86)\\Commvault\\ContentStore*\\Base\\cvd.exe",
+     "?:\\Program Files\\NVIDIA Corporation\\Display.NvContainer\\NVDisplay.Container.exe"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,34 +161,15 @@ process.executable : ("C:\\Windows\\System32\\msiexec.exe",
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[registry-persistence-via-appinit-dll-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path : ("HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\AppInit_Dlls",
-"HKLM\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\AppInit_Dlls") and not
-process.executable : ("C:\\Windows\\System32\\msiexec.exe",
-"C:\\Windows\\SysWOW64\\msiexec.exe",
-"C:\\Program Files\\Commvault\\ContentStore*\\Base\\cvd.exe",
-"C:\\Program Files (x86)\\Commvault\\ContentStore*\\Base\\cvd.exe")
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: AppInit DLLs
+** ID: T1546.010
+** Reference URL: https://attack.mitre.org/techniques/T1546/010/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-computer-account-dnshostname-update.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-computer-account-dnshostname-update.asciidoc
index f35dc1fa02..d8bade8884 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-computer-account-dnshostname-update.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-computer-account-dnshostname-update.asciidoc
@@ -5,67 +5,60 @@ Identifies the remote update to a computer account's DnsHostName attribute. If t
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://research.ifcr.dk/certifried-active-directory-domain-privilege-escalation-cve-2022-26923-9e098fe298f4
 * https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2022-26923
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Active Directory
-
-*Version*: 101 (<<remote-computer-account-dnshostname-update-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Use Case: Active Directory Monitoring
+* Data Source: Active Directory
+* Use Case: Vulnerability
 
-*Added ({stack} release)*: 8.3.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=5m [authentication where
-event.action == "logged-in" and winlog.logon.type == "Network" and
-event.outcome == "success" and not user.name == "ANONYMOUS LOGON"
-and not winlog.event_data.SubjectUserName : "*$" and not
-user.domain == "NT AUTHORITY" and source.ip != "127.0.0.1" and
-source.ip !="::1"] by winlog.event_data.TargetLogonId [iam where
-event.action == "changed-computer-account" and /* if DnsHostName
-value equal a DC DNS hostname then it's highly suspicious */
-winlog.event_data.DnsHostName : "??*" and /* exclude FPs
-where DnsHostName starts with the ComputerName that was changed */
-not startswith~(winlog.event_data.DnsHostName,
-substring(winlog.event_data.TargetUserName, 0,
-length(winlog.event_data.TargetUserName) - 1)) ] by
-winlog.event_data.SubjectLogonId
+[source, js]
 ----------------------------------
+iam where event.action == "changed-computer-account" and user.id : ("S-1-5-21-*", "S-1-12-1-*") and
+
+    /* if DnsHostName value equal a DC DNS hostname then it's highly suspicious */
+    winlog.event_data.DnsHostName : "??*" and
 
-==== Threat mapping
+    /* exclude FPs where DnsHostName starts with the ComputerName that was changed */
+    not startswith~(winlog.event_data.DnsHostName, substring(winlog.event_data.TargetUserName, 0, length(winlog.event_data.TargetUserName) - 1))
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,30 +70,11 @@ winlog.event_data.SubjectLogonId
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-[[remote-computer-account-dnshostname-update-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5m [authentication where
-event.action == "logged-in" and winlog.logon.type == "Network" and
-event.outcome == "success" and not user.name == "ANONYMOUS LOGON"
-and not winlog.event_data.SubjectUserName : "*$" and not
-user.domain == "NT AUTHORITY" and source.ip != "127.0.0.1" and
-source.ip !="::1"] by winlog.event_data.TargetLogonId [iam where
-event.action == "changed-computer-account" and /* if DnsHostName
-value equal a DC DNS hostname then it's highly suspicious */
-winlog.event_data.DnsHostName : "??*"] by
-winlog.event_data.SubjectLogonId
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Domain Accounts
+** ID: T1078.002
+** Reference URL: https://attack.mitre.org/techniques/T1078/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-desktop-enabled-in-windows-firewall-by-netsh.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-desktop-enabled-in-windows-firewall-by-netsh.asciidoc
index 4169659ef0..624c6be4e1 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-desktop-enabled-in-windows-firewall-by-netsh.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-desktop-enabled-in-windows-firewall-by-netsh.asciidoc
@@ -5,79 +5,84 @@ Identifies use of the network shell utility (netsh.exe) to enable inbound Remote
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<remote-desktop-enabled-in-windows-firewall-by-netsh-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Remote Desktop Enabled in Windows Firewall by Netsh
+*Triage and analysis*
+
+
+
+*Investigating Remote Desktop Enabled in Windows Firewall by Netsh*
+
+
+Microsoft Remote Desktop Protocol (RDP) is a proprietary Microsoft protocol that enables remote connections to other computers, typically over TCP port 3389.
+
+Attackers can use RDP to conduct their actions interactively. Ransomware operators frequently use RDP to access victim servers, often using privileged accounts.
 
-Microsoft Remote Desktop Protocol (RDP) is a proprietary Microsoft protocol that enables remote connections to other
-computers, typically over TCP port 3389.
+This rule detects the creation of a Windows Firewall inbound rule that would allow inbound RDP traffic using the `netsh.exe` utility.
 
-Attackers can use RDP to conduct their actions interactively. Ransomware operators frequently use RDP to access
-victim servers, often using privileged accounts.
 
-This rule detects the creation of a Windows Firewall inbound rule that would allow inbound RDP traffic using the
-`netsh.exe` utility.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the user to check if they are aware of the operation.
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Check whether it makes sense to enable RDP to this host, given its role in the environment.
 - Check if the host is directly exposed to the internet.
 - Check whether privileged accounts accessed the host shortly after the modification.
 - Review network events within a short timespan of this alert for incoming RDP connection attempts.
 
-### False positive analysis
 
-- The `netsh.exe` utility can be used legitimately. Check whether the user should be performing this kind of activity, whether the user is aware
-of it, whether RDP should be open, and whether the action exposes the environment to unnecessary risks.
+*False positive analysis*
+
+
+- The `netsh.exe` utility can be used legitimately. Check whether the user should be performing this kind of activity, whether the user is aware of it, whether RDP should be open, and whether the action exposes the environment to unnecessary risks.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - If RDP is needed, make sure to secure it:
@@ -86,23 +91,34 @@ of it, whether RDP should be open, and whether the action exposes the environmen
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name : "netsh.exe"
-or process.pe.original_file_name == "netsh.exe") and process.args :
-("localport=3389", "RemoteDesktop", "group=\"remote desktop\"") and
-process.args : ("action=allow", "enable=Yes", "enable")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ (process.name : "netsh.exe" or ?process.pe.original_file_name == "netsh.exe") and
+ process.args : ("localport=3389", "RemoteDesktop", "group=\"remote desktop\"") and
+ process.args : ("action=allow", "enable=Yes", "enable")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -114,39 +130,7 @@ process.args : ("action=allow", "enable=Yes", "enable")
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[remote-desktop-enabled-in-windows-firewall-by-netsh-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "netsh.exe" or process.pe.original_file_name ==
-"netsh.exe") and process.args : ("localport=3389", "RemoteDesktop",
-"group=\"remote desktop\"") and process.args : ("action=allow",
-"enable=Yes", "enable")
-----------------------------------
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Rule name changed from: Remote Desktop Enabled in Windows Firewall
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify System Firewall
+** ID: T1562.004
+** Reference URL: https://attack.mitre.org/techniques/T1562/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-execution-via-file-shares.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-execution-via-file-shares.asciidoc
index 33f1fb6ada..41926e4709 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-execution-via-file-shares.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-execution-via-file-shares.asciidoc
@@ -5,88 +5,91 @@ Identifies the execution of a file that was created by the virtual system proces
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
-* winlogbeat-*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.file-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
-* https://web.archive.org/web/20230329172636/https://blog.menasec.net/2020/08/new-trick-to-detect-lateral-movement.html
+* http://web.archive.org/web/20230329172636/https://blog.menasec.net/2020/08/new-trick-to-detect-lateral-movement.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-* Investigation Guide
-
-*Version*: 102 (<<remote-execution-via-file-shares-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Remote Execution via File Shares
+*Triage and analysis*
+
+
+
+*Investigating Remote Execution via File Shares*
 
-Adversaries can use network shares to host tooling to support the compromise of other hosts in the environment. These
-tools can include discovery utilities, credential dumpers, malware, etc.
+
+Adversaries can use network shares to host tooling to support the compromise of other hosts in the environment. These tools can include discovery utilities, credential dumpers, malware, etc.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Review adjacent login events (e.g., 4624) in the alert timeframe to identify the account used to perform this action.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - This activity can happen legitimately. Consider adding exceptions if it is expected and noisy in your environment.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -94,31 +97,40 @@ for prevalence, whether they are located in expected locations, and if they are
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
 - Review the privileges needed to write to the network share and restrict write access as needed.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence with maxspan=1m [file where event.type in ("creation",
-"change") and process.pid == 4 and file.extension : "exe"] by host.id,
-file.path [process where event.type == "start"] by host.id,
-process.executable
+[source, js]
 ----------------------------------
+sequence with maxspan=1m
+  [file where host.os.type == "windows" and event.type in ("creation", "change") and 
+   process.pid == 4 and (file.extension : "exe" or file.Ext.header_bytes : "4d5a*")] by host.id, file.path
+  [process where host.os.type == "windows" and event.type == "start" and
+    not (
+      /* Veeam related processes */
+      (
+        process.name : (
+          "VeeamGuestHelper.exe", "VeeamGuestIndexer.exe", "VeeamAgent.exe", "VeeamLogShipper.exe", "Veeam.VSS.Sharepoint2010.exe"
+        ) and process.code_signature.trusted == true and process.code_signature.subject_name : "Veeam Software Group GmbH"
+      ) or
+      /* PDQ related processes */
+      (
+        process.name : (
+          "PDQInventoryScanner.exe", "PDQInventoryMonitor.exe", "PDQInventory-Scanner-?.exe", "PDQInventoryWakeCommand-?.exe"
+        ) and process.code_signature.trusted == true and process.code_signature.subject_name : "PDQ.com Corporation"
+      )
+    )
+  ] by host.id, process.executable
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -130,27 +142,7 @@ process.executable
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[remote-execution-via-file-shares-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1m [file where event.type in ("creation",
-"change") and process.pid == 4 and file.extension : "exe"] by host.id,
-file.path [process where event.type in ("start", "process_started")]
-by host.id, process.executable
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-file-copy-to-a-hidden-share.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-file-copy-to-a-hidden-share.asciidoc
index dfab4375eb..d053548140 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-file-copy-to-a-hidden-share.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-file-copy-to-a-hidden-share.asciidoc
@@ -5,60 +5,71 @@ Identifies a remote file copy attempt to a hidden network share. This may indica
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
+*Tags*: 
 
-*Version*: 101 (<<remote-file-copy-to-a-hidden-share-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : ("cmd.exe",
-"powershell.exe", "robocopy.exe", "xcopy.exe") and process.args :
-("copy*", "move*", "cp", "mv") and process.args : "*$*"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (
+    process.name : ("cmd.exe", "powershell.exe", "xcopy.exe") and
+    process.args : ("copy*", "move*", "cp", "mv") or
+    process.name : "robocopy.exe"
+  ) and process.args : "*\\\\*\\*$*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,38 +81,7 @@ process where event.type == "start" and process.name : ("cmd.exe",
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[remote-file-copy-to-a-hidden-share-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : ("cmd.exe", "powershell.exe", "robocopy.exe",
-"xcopy.exe") and process.args : ("copy*", "move*", "cp", "mv") and
-process.args : "*$*"
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : ("cmd.exe", "powershell.exe", "robocopy.exe",
-"xcopy.exe") and process.args : ("copy*", "move*", "cp", "mv") and
-process.args : "*$*"
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-file-copy-via-teamviewer.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-file-copy-via-teamviewer.asciidoc
index 802e7efca6..9462a84c88 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-file-copy-via-teamviewer.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-file-copy-via-teamviewer.asciidoc
@@ -5,97 +5,93 @@ Identifies an executable or script file remotely downloaded via a TeamViewer tra
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
-* endgame-*
+* logs-endpoint.events.file-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
-* https://web.archive.org/web/20230329160957/https://blog.menasec.net/2019/11/hunting-for-suspicious-use-of.html
+* http://web.archive.org/web/20230329160957/https://blog.menasec.net/2019/11/hunting-for-suspicious-use-of.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<remote-file-copy-via-teamviewer-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Remote File Copy via TeamViewer
+*Triage and analysis*
+
 
-Attackers commonly transfer tooling or malware from external systems into a compromised environment using the command
-and control channel. However, they can also abuse legitimate utilities to drop these files.
 
-TeamViewer is a remote access and remote control tool used by helpdesks and system administrators to perform various
-support activities. It is also frequently used by attackers and scammers to deploy malware interactively and other
-malicious activities. This rule looks for the TeamViewer process creating files with suspicious extensions.
+*Investigating Remote File Copy via TeamViewer*
+
+
+Attackers commonly transfer tooling or malware from external systems into a compromised environment using the command and control channel. However, they can also abuse legitimate utilities to drop these files.
+
+TeamViewer is a remote access and remote control tool used by helpdesks and system administrators to perform various support activities. It is also frequently used by attackers and scammers to deploy malware interactively and other malicious activities. This rule looks for the TeamViewer process creating files with suspicious extensions.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Contact the user to gather information about who and why was conducting the remote access.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Check whether the company uses TeamViewer for the support activities and if there is a support ticket related to this
-access.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Check whether the company uses TeamViewer for the support activities and if there is a support ticket related to this access.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Analysts can dismiss the alert if the company relies on TeamViewer to conduct
-remote access and the triage has not identified suspicious or malicious files.
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the company relies on TeamViewer to conduct remote access and the triage has not identified suspicious or malicious files.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -103,30 +99,44 @@ remote access and the triage has not identified suspicious or malicious files.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type == "creation" and process.name :
-"TeamViewer.exe" and file.extension : ("exe", "dll", "scr", "com",
-"bat", "ps1", "vbs", "vbe", "js", "wsh", "hta")
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and process.name : "TeamViewer.exe" and
+  file.extension : ("exe", "dll", "scr", "com", "bat", "ps1", "vbs", "vbe", "js", "wsh", "hta") and
+  not 
+  (
+    file.path : (
+      "?:\\Users\\*\\AppData\\Local\\Microsoft\\Windows\\INetCache\\*.js",
+      "?:\\Users\\*\\AppData\\Local\\Temp\\TeamViewer\\update.exe",
+      "?:\\Users\\*\\AppData\\Local\\Temp\\?\\TeamViewer\\update.exe"
+    ) and process.code_signature.trusted == true
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -138,41 +148,7 @@ file where event.type == "creation" and process.name :
 ** Name: Ingress Tool Transfer
 ** ID: T1105
 ** Reference URL: https://attack.mitre.org/techniques/T1105/
-
-[[remote-file-copy-via-teamviewer-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.3.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (7.16.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and event.type:creation and
-process.name:TeamViewer.exe and file.extension:(exe or dll or scr or
-com or bat or ps1 or vbs or vbe or js or wsh or hta)
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Technique:
+** Name: Remote Access Software
+** ID: T1219
+** Reference URL: https://attack.mitre.org/techniques/T1219/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-desktopimgdownldr-utility.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-desktopimgdownldr-utility.asciidoc
index 0a1089fc9b..4429fd7815 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-desktopimgdownldr-utility.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-desktopimgdownldr-utility.asciidoc
@@ -5,99 +5,104 @@ Identifies the desktopimgdownldr utility being used to download a remote file. A
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://labs.sentinelone.com/living-off-windows-land-a-new-native-file-downldr/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<remote-file-download-via-desktopimgdownldr-utility-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Remote File Download via Desktopimgdownldr Utility
+*Triage and analysis*
+
 
-Attackers commonly transfer tooling or malware from external systems into a compromised environment using the command
-and control channel. However, they can also abuse signed utilities to drop these files.
 
-The `Desktopimgdownldr.exe` utility is used to to configure lockscreen/desktop image, and can be abused with the
-`lockscreenurl` argument to download remote files and tools, this rule looks for this behavior.
+*Investigating Remote File Download via Desktopimgdownldr Utility*
+
+
+Attackers commonly transfer tooling or malware from external systems into a compromised environment using the command and control channel. However, they can also abuse signed utilities to drop these files.
+
+The `Desktopimgdownldr.exe` utility is used to to configure lockscreen/desktop image, and can be abused with the `lockscreenurl` argument to download remote files and tools, this rule looks for this behavior.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/interactive-investigation-guides.html[Investigate Markdown Plugin] introduced in Elastic Stack version 8.8.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
+  - !{investigate{"label":"Alerts associated with the user in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"user.id","queryType":"phrase","value":"{{user.id}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
+  - !{investigate{"label":"Alerts associated with the host in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"host.name","queryType":"phrase","value":"{{host.name}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Check the reputation of the domain or IP address used to host the downloaded file or if the user downloaded the file
-from an internal system.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Check the reputation of the domain or IP address used to host the downloaded file or if the user downloaded the file from an internal system.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+        - !{investigate{"label":"Investigate the Subject Process Network Events","providers":[[{"excluded":false,"field":"process.entity_id","queryType":"phrase","value":"{{process.entity_id}}","valueType":"string"},{"excluded":false,"field":"event.category","queryType":"phrase","value":"network","valueType":"string"}]]}}
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
 
-### False positive analysis
+*False positive analysis*
 
-- This activity is unusual but can be done by administrators. Benign true positives (B-TPs) can be added as exceptions
-if necessary.
+
+- This activity is unusual but can be done by administrators. Benign true positives (B-TPs) can be added as exceptions if necessary.
 - Analysts can dismiss the alert if the downloaded file is a legitimate image.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -105,31 +110,38 @@ if necessary.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"desktopimgdownldr.exe" or process.pe.original_file_name ==
-"desktopimgdownldr.exe") and process.args : "/lockscreenurl:http*"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "desktopimgdownldr.exe" or ?process.pe.original_file_name == "desktopimgdownldr.exe") and
+  process.args : "/lockscreenurl:http*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -141,59 +153,3 @@ process where event.type == "start" and (process.name :
 ** Name: Ingress Tool Transfer
 ** ID: T1105
 ** Reference URL: https://attack.mitre.org/techniques/T1105/
-
-[[remote-file-download-via-desktopimgdownldr-utility-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "desktopimgdownldr.exe" or
-process.pe.original_file_name == "desktopimgdownldr.exe") and
-process.args : "/lockscreenurl:http*"
-----------------------------------
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.3.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-(process.name:desktopimgdownldr.exe or
-process.pe.original_file_name:desktopimgdownldr.exe) and
-process.args:/lockscreenurl\:http*
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-(process.name:desktopimgdownldr.exe or
-process.pe.original_file_name:desktopimgdownldr.exe or
-winlog.event_data.OriginalFileName:desktopimgdownldr.exe) and
-process.args:/lockscreenurl\:http*
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-mpcmdrun.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-mpcmdrun.asciidoc
index 92ba19b86c..3354c45a7e 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-mpcmdrun.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-mpcmdrun.asciidoc
@@ -5,97 +5,103 @@ Identifies the Windows Defender configuration utility (MpCmdRun.exe) being used
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://twitter.com/mohammadaskar2/status/1301263551638761477
 * https://www.bleepingcomputer.com/news/microsoft/microsoft-defender-can-ironically-be-used-to-download-malware/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<remote-file-download-via-mpcmdrun-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Remote File Download via MpCmdRun
+*Triage and analysis*
+
 
-Attackers commonly transfer tooling or malware from external systems into a compromised environment using the command
-and control channel. However, they can also abuse signed utilities to drop these files.
 
-The `MpCmdRun.exe` is a command-line tool part of Windows Defender and is used to manage various Microsoft Windows
-Defender Antivirus settings and perform certain tasks. It can also be abused by attackers to download remote files,
-including malware and offensive tooling. This rule looks for the patterns used to perform downloads using the utility.
+*Investigating Remote File Download via MpCmdRun*
+
+
+Attackers commonly transfer tooling or malware from external systems into a compromised environment using the command and control channel. However, they can also abuse signed utilities to drop these files.
+
+The `MpCmdRun.exe` is a command-line tool part of Windows Defender and is used to manage various Microsoft Windows Defender Antivirus settings and perform certain tasks. It can also be abused by attackers to download remote files, including malware and offensive tooling. This rule looks for the patterns used to perform downloads using the utility.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/interactive-investigation-guides.html[Investigate Markdown Plugin] introduced in Elastic Stack version 8.8.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
+  - !{investigate{"label":"Alerts associated with the user in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"user.id","queryType":"phrase","value":"{{user.id}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
+  - !{investigate{"label":"Alerts associated with the host in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"host.name","queryType":"phrase","value":"{{host.name}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
 - Check the reputation of the domain or IP address used to host the downloaded file.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+        - !{investigate{"label":"Investigate the Subject Process Network Events","providers":[[{"excluded":false,"field":"process.entity_id","queryType":"phrase","value":"{{process.entity_id}}","valueType":"string"},{"excluded":false,"field":"event.category","queryType":"phrase","value":"network","valueType":"string"}]]}}
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -103,32 +109,38 @@ for prevalence, whether they are located in expected locations, and if they are
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"MpCmdRun.exe" or process.pe.original_file_name == "MpCmdRun.exe") and
-process.args : "-DownloadFile" and process.args : "-url" and
-process.args : "-path"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "MpCmdRun.exe" or ?process.pe.original_file_name == "MpCmdRun.exe") and
+   process.args : "-DownloadFile" and process.args : "-url" and process.args : "-path"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -140,53 +152,3 @@ process.args : "-path"
 ** Name: Ingress Tool Transfer
 ** ID: T1105
 ** Reference URL: https://attack.mitre.org/techniques/T1105/
-
-[[remote-file-download-via-mpcmdrun-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.3.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-(process.name:MpCmdRun.exe or
-process.pe.original_file_name:MpCmdRun.exe) and
-process.args:(("-DownloadFile" or "-downloadfile") and "-url" and
-"-path")
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-(process.name:MpCmdRun.exe or
-process.pe.original_file_name:MpCmdRun.exe or
-winlog.event_data.OriginalFileName:MpCmdRun.exe) and
-process.args:(("-DownloadFile" or "-downloadfile") and "-url" and
-"-path")
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-powershell.asciidoc
index 77f28c529d..3849f928c0 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-powershell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-powershell.asciidoc
@@ -5,92 +5,96 @@ Identifies powershell.exe being used to download an executable file from an untr
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.network-*
+* logs-endpoint.events.file-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<remote-file-download-via-powershell-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Remote File Download via PowerShell
+*Triage and analysis*
+
 
-Attackers commonly transfer tooling or malware from external systems into a compromised environment using the command
-and control channel. However, they can also abuse signed utilities to drop these files.
 
-PowerShell is one of system administrators' main tools for automation, report routines, and other tasks. This makes it
-available for use in various environments and creates an attractive way for attackers to execute code and perform
-actions. This rule correlates network and file events to detect downloads of executable and script files performed using
-PowerShell.
+*Investigating Remote File Download via PowerShell*
+
+
+Attackers commonly transfer tooling or malware from external systems into a compromised environment using the command and control channel. However, they can also abuse signed utilities to drop these files.
+
+PowerShell is one of system administrators' main tools for automation, report routines, and other tasks. This makes it available for use in various environments and creates an attractive way for attackers to execute code and perform actions. This rule correlates network and file events to detect downloads of executable and script files performed using PowerShell.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/interactive-investigation-guides.html[Investigate Markdown Plugin] introduced in Elastic Stack version 8.8.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
 - Investigate other alerts associated with the user/host during the past 48 hours.
+  - !{investigate{"label":"Alerts associated with the user in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"user.id","queryType":"phrase","value":"{{user.id}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
+  - !{investigate{"label":"Alerts associated with the host in the last 48h","providers":[[{"excluded":false,"field":"event.kind","queryType":"phrase","value":"signal","valueType":"string"},{"excluded":false,"field":"host.name","queryType":"phrase","value":"{{host.name}}","valueType":"string"}]],"relativeFrom":"now-48h/h","relativeTo":"now"}}
 - Check the reputation of the domain or IP address used to host the downloaded file.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+        - !{investigate{"label":"Investigate the Subject Process Network Events","providers":[[{"excluded":false,"field":"process.entity_id","queryType":"phrase","value":"{{process.entity_id}}","valueType":"string"},{"excluded":false,"field":"event.category","queryType":"phrase","value":"network","valueType":"string"}]]}}
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
+
+
+- Administrators can use PowerShell legitimately to download executable and script files. Analysts can dismiss the alert if the Administrator is aware of the activity and the triage has not identified suspicious or malicious files.
 
-### False positive analysis
 
-- Administrators can use PowerShell legitimately to download executable and script files. Analysts can dismiss the alert
-if the Administrator is aware of the activity and the triage has not identified suspicious or malicious files.
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -98,38 +102,34 @@ if the Administrator is aware of the activity and the triage has not identified
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=30s [network
-where process.name : ("powershell.exe", "pwsh.exe",
-"powershell_ise.exe") and network.protocol == "dns" and not
-dns.question.name : ("localhost", "*.microsoft.com",
-"*.azureedge.net", "*.powershellgallery.com", "*.windowsupdate.com",
-"metadata.google.internal") and not user.domain : "NT AUTHORITY"]
-[file where process.name : "powershell.exe" and event.type ==
-"creation" and file.extension : ("exe", "dll", "ps1", "bat") and
-not file.name : "__PSScriptPolicy*.ps1"]
+[source, js]
 ----------------------------------
+sequence by process.entity_id with maxspan=30s
+
+[network where host.os.type == "windows" and
+  process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe") and network.protocol == "dns" and
+   not dns.question.name : (
+          "localhost", "*.microsoft.com", "*.azureedge.net", "*.powershellgallery.com",
+          "*.windowsupdate.com", "metadata.google.internal", "dist.nuget.org",
+          "artifacts.elastic.co", "*.digicert.com", "packages.chocolatey.org",
+          "outlook.office365.com"
+       ) and not user.id : "S-1-5-18"]
+[file where host.os.type == "windows" and event.type == "creation" and
+  process.name : "powershell.exe" and file.extension : ("exe", "dll", "ps1", "bat") and
+  not file.name : "__PSScriptPolicy*.ps1"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -141,8 +141,6 @@ not file.name : "__PSScriptPolicy*.ps1"]
 ** Name: Ingress Tool Transfer
 ** ID: T1105
 ** Reference URL: https://attack.mitre.org/techniques/T1105/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -151,53 +149,7 @@ not file.name : "__PSScriptPolicy*.ps1"]
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[remote-file-download-via-powershell-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=30s [network
-where process.name : ("powershell.exe", "pwsh.exe",
-"powershell_ise.exe") and network.protocol == "dns" and not
-dns.question.name : ("localhost", "*.microsoft.com",
-"*.azureedge.net", "*.powershellgallery.com", "*.windowsupdate.com",
-"metadata.google.internal") and not user.domain : "NT AUTHORITY"]
-[file where process.name : "powershell.exe" and event.type ==
-"creation" and file.extension : ("exe", "dll", "ps1", "bat") and
-not file.name : "__PSScriptPolicy*.ps1"]
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=30s [network
-where process.name : "powershell.exe" and network.protocol == "dns"
-and not dns.question.name : ("localhost", "*.microsoft.com",
-"*.azureedge.net", "*.powershellgallery.com", "*.windowsupdate.com",
-"metadata.google.internal") and not user.domain : "NT AUTHORITY"]
-[file where process.name : "powershell.exe" and event.type ==
-"creation" and file.extension : ("exe", "dll", "ps1", "bat") and
-not file.name : "__PSScriptPolicy*.ps1"]
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-script-interpreter.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-script-interpreter.asciidoc
index f40d1395bb..73a590ef06 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-script-interpreter.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-file-download-via-script-interpreter.asciidoc
@@ -5,88 +5,94 @@ Identifies built-in Windows script interpreters (cscript.exe or wscript.exe) bei
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.network-*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<remote-file-download-via-script-interpreter-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Remote File Download via Script Interpreter
+*Triage and analysis*
+
 
-The Windows Script Host (WSH) is a Windows automation technology, which is ideal for non-interactive scripting needs,
-such as logon scripting, administrative scripting, and machine automation.
 
-Attackers commonly use WSH scripts as their initial access method, acting like droppers for second stage payloads, but
-can also use them to download tools and utilities needed to accomplish their goals.
+*Investigating Remote File Download via Script Interpreter*
+
+
+The Windows Script Host (WSH) is a Windows automation technology, which is ideal for non-interactive scripting needs, such as logon scripting, administrative scripting, and machine automation.
+
+Attackers commonly use WSH scripts as their initial access method, acting like droppers for second stage payloads, but can also use them to download tools and utilities needed to accomplish their goals.
 
 This rule looks for DLLs and executables downloaded using `cscript.exe` or `wscript.exe`.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Examine the host for derived artifacts that indicates suspicious activities:
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze both the script and the executable involved using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- The usage of these script engines by regular users is unlikely. In the case of authorized benign true positives (B-TPs), exceptions can be added.
 
-- The usage of these script engines by regular users is unlikely. In the case of authorized benign true positives
-(B-TPs), exceptions can be added.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -94,34 +100,26 @@ for prevalence, whether they are located in expected locations, and if they are
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, process.entity_id [network where process.name :
-("wscript.exe", "cscript.exe") and network.protocol != "dns" and
-network.direction : ("outgoing", "egress") and network.type == "ipv4"
-and destination.ip != "127.0.0.1" ] [file where event.type ==
-"creation" and file.extension : ("exe", "dll")]
+[source, js]
 ----------------------------------
+sequence by host.id, process.entity_id
+  [network where host.os.type == "windows" and process.name : ("wscript.exe", "cscript.exe") and network.protocol != "dns" and
+   network.direction : ("outgoing", "egress") and network.type == "ipv4" and destination.ip != "127.0.0.1"
+  ]
+  [file where host.os.type == "windows" and event.type == "creation" and file.extension : ("exe", "dll")]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -133,37 +131,15 @@ and destination.ip != "127.0.0.1" ] [file where event.type ==
 ** Name: Ingress Tool Transfer
 ** ID: T1105
 ** Reference URL: https://attack.mitre.org/techniques/T1105/
-
-[[remote-file-download-via-script-interpreter-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id [network where process.name :
-("wscript.exe", "cscript.exe") and network.protocol != "dns" and
-network.direction == "outgoing" and network.type == "ipv4" and
-destination.ip != "127.0.0.1" ] [file where event.type ==
-"creation" and file.extension : ("exe", "dll")]
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Visual Basic
+** ID: T1059.005
+** Reference URL: https://attack.mitre.org/techniques/T1059/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-scheduled-task-creation-via-rpc.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-scheduled-task-creation-via-rpc.asciidoc
new file mode 100644
index 0000000000..c1959fb5ea
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/remote-scheduled-task-creation-via-rpc.asciidoc
@@ -0,0 +1,118 @@
+[[remote-scheduled-task-creation-via-rpc]]
+=== Remote Scheduled Task Creation via RPC
+
+Identifies scheduled task creation from a remote source. This could be indicative of adversary lateral movement.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-system.security*
+* logs-windows.forwarded*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Remote Scheduled Task Creation*
+
+
+https://docs.microsoft.com/en-us/windows/win32/taskschd/about-the-task-scheduler[Scheduled tasks] are a great mechanism for persistence and program execution. These features can be used remotely for a variety of legitimate reasons, but at the same time used by malware and adversaries. When investigating scheduled tasks that were set up remotely, one of the first steps should be to determine the original intent behind the configuration and to verify if the activity is tied to benign behavior such as software installation or any kind of network administrator work. One objective for these alerts is to understand the configured action within the scheduled task. This is captured within the registry event data for this rule and can be base64 decoded to view the value.
+
+
+*Possible investigation steps*
+
+
+- Review the TaskContent value to investigate the task configured action.
+- Validate if the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Further examination should include review of host-based artifacts and network logs from around when the scheduled task was created, on both the source and target machines.
+
+
+*False positive analysis*
+
+
+- There is a high possibility of benign activity tied to the creation of remote scheduled tasks as it is a general feature within Windows and used for legitimate purposes for a wide range of activity. Any kind of context should be found to further understand the source of the activity and determine the intent based on the scheduled task's contents.
+
+
+*Related rules*
+
+
+- Service Command Lateral Movement - d61cbcf8-1bc1-4cff-85ba-e7b21c5beedc
+- Remotely Started Services via RPC - aa9a274d-6b53-424d-ac5e-cb8ca4251650
+- Remote Scheduled Task Creation - 954ee7c8-5437-49ae-b2d6-2960883898e9
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Remove scheduled task and any other related artifacts.
+- Review privileged account management and user account management settings. Consider implementing group policy object (GPO) policies to further restrict activity, or configuring settings that only allow administrators to create remote scheduled tasks.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+iam where event.action == "scheduled-task-created" and 
+ winlog.event_data.RpcCallClientLocality : "0" and winlog.event_data.ClientProcessId : "0"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-scheduled-task-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-scheduled-task-creation.asciidoc
index 8c0678cc44..3d27ccb59e 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-scheduled-task-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-scheduled-task-creation.asciidoc
@@ -5,104 +5,103 @@ Identifies remote scheduled task creations on a target host. This could be indic
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* logs-endpoint.events.network-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<remote-scheduled-task-creation-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Remote Scheduled Task Creation
+*Triage and analysis*
+
+
 
-[Scheduled tasks](https://docs.microsoft.com/en-us/windows/win32/taskschd/about-the-task-scheduler) are a great mechanism
-for persistence and program execution. These features can be used remotely for a variety of legitimate reasons, but at
-the same time used by malware and adversaries. When investigating scheduled tasks that were set up remotely, one of the
-first steps should be to determine the original intent behind the configuration and to verify if the activity is tied to
-benign behavior such as software installation or any kind of network administrator work. One objective for these alerts
-is to understand the configured action within the scheduled task. This is captured within the registry event data for
-this rule and can be base64 decoded to view the value.
+*Investigating Remote Scheduled Task Creation*
+
+
+https://docs.microsoft.com/en-us/windows/win32/taskschd/about-the-task-scheduler[Scheduled tasks] are a great mechanism for persistence and program execution. These features can be used remotely for a variety of legitimate reasons, but at the same time used by malware and adversaries. When investigating scheduled tasks that were set up remotely, one of the first steps should be to determine the original intent behind the configuration and to verify if the activity is tied to benign behavior such as software installation or any kind of network administrator work. One objective for these alerts is to understand the configured action within the scheduled task. This is captured within the registry event data for this rule and can be base64 decoded to view the value.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Review the base64 encoded tasks actions registry value to investigate the task configured action.
-- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software
-installations.
-- Further examination should include review of host-based artifacts and network logs from around when the scheduled task
-was created, on both the source and target machines.
+- Validate if the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Further examination should include review of host-based artifacts and network logs from around when the scheduled task was created, on both the source and target machines.
+
 
-### False positive analysis
+*False positive analysis*
 
-- There is a high possibility of benign activity tied to the creation of remote scheduled tasks as it is a general feature
-within Windows and used for legitimate purposes for a wide range of activity. Any kind of context should be found to
-further understand the source of the activity and determine the intent based on the scheduled task's contents.
 
-### Related rules
+- There is a high possibility of benign activity tied to the creation of remote scheduled tasks as it is a general feature within Windows and used for legitimate purposes for a wide range of activity. Any kind of context should be found to further understand the source of the activity and determine the intent based on the scheduled task's contents.
+
+
+*Related rules*
+
 
 - Service Command Lateral Movement - d61cbcf8-1bc1-4cff-85ba-e7b21c5beedc
 - Remotely Started Services via RPC - aa9a274d-6b53-424d-ac5e-cb8ca4251650
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
 - Remove scheduled task and any other related artifacts.
-- Review privileged account management and user account management settings. Consider implementing group policy object (GPO) policies to further
-restrict activity, or configuring settings that only allow administrators to create remote scheduled tasks.
-
-----------------------------------
+- Review privileged account management and user account management settings. Consider implementing group policy object (GPO) policies to further restrict activity, or configuring settings that only allow administrators to create remote scheduled tasks.
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-/* Task Scheduler service incoming connection followed by TaskCache
-registry modification */ sequence by host.id, process.entity_id with
-maxspan = 1m [network where process.name : "svchost.exe" and
-network.direction : ("incoming", "ingress") and source.port >= 49152
-and destination.port >= 49152 and source.ip != "127.0.0.1" and
-source.ip != "::1" ] [registry where registry.path :
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions"]
+[source, js]
 ----------------------------------
+/* Task Scheduler service incoming connection followed by TaskCache registry modification  */
 
-==== Threat mapping
+sequence by host.id, process.entity_id with maxspan = 1m
+   [network where host.os.type == "windows" and process.name : "svchost.exe" and
+   network.direction : ("incoming", "ingress") and source.port >= 49152 and destination.port >= 49152 and
+   source.ip != "127.0.0.1" and source.ip != "::1"
+   ]
+   [registry where host.os.type == "windows" and registry.path : "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions"]
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -114,8 +113,6 @@ NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions"]
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -124,58 +121,7 @@ NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions"]
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[remote-scheduled-task-creation-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 8 (8.2.0 release)::
-* Formatting only
-
-Version 7 (8.1.0 release)::
-* Formatting only
-
-Version 6 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* Task Scheduler service incoming connection followed by TaskCache
-registry modification */ sequence by host.id, process.entity_id with
-maxspan = 1m [network where process.name : "svchost.exe" and
-network.direction : ("incoming", "ingress") and source.port >= 49152
-and destination.port >= 49152 and source.address != "127.0.0.1" and
-source.address != "::1" ] [registry where registry.path :
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions"]
-----------------------------------
-
-Version 5 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* Task Scheduler service incoming connection followed by TaskCache
-registry modification */ sequence by host.id, process.entity_id with
-maxspan = 1m [network where process.name : "svchost.exe" and
-network.direction == "incoming" and source.port >= 49152 and
-destination.port >= 49152 and source.address != "127.0.0.1" and
-source.address != "::1" ] [registry where registry.path :
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions"]
-----------------------------------
-
-Version 3 (7.13.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-ssh-login-enabled-via-systemsetup-command.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-ssh-login-enabled-via-systemsetup-command.asciidoc
index 338820c9ab..48424403da 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-ssh-login-enabled-via-systemsetup-command.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-ssh-login-enabled-via-systemsetup-command.asciidoc
@@ -5,56 +5,91 @@ Detects use of the systemsetup command to enable remote SSH Login.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://documents.trendmicro.com/assets/pdf/XCSSET_Technical_Brief.pdf
 * https://ss64.com/osx/systemsetup.html
 * https://support.apple.com/guide/remote-desktop/about-systemsetup-apd95406b8d/mac
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Lateral Movement
 
-*Version*: 100 (<<remote-ssh-login-enabled-via-systemsetup-command-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.10.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:systemsetup and process.args:("-setremotelogin" and on)
-and not process.parent.executable : /usr/local/jamf/bin/jamf
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+ process.name:systemsetup and
+ process.args:("-setremotelogin" and on) and
+ not process.parent.executable : /usr/local/jamf/bin/jamf
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,32 +101,7 @@ and not process.parent.executable : /usr/local/jamf/bin/jamf
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[remote-ssh-login-enabled-via-systemsetup-command-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:systemsetup and process.args:("-setremotelogin" and on)
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:systemsetup and process.args:("-f" and "-setremotelogin"
-and on)
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: SSH
+** ID: T1021.004
+** Reference URL: https://attack.mitre.org/techniques/T1021/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-system-discovery-commands.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-system-discovery-commands.asciidoc
index 656842571d..0658c03cf7 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-system-discovery-commands.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-system-discovery-commands.asciidoc
@@ -5,9 +5,9 @@ Discovery of remote system information using built-in commands, which may be use
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
@@ -16,88 +16,118 @@ Discovery of remote system information using built-in commands, which may be use
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<remote-system-discovery-commands-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Rule Type: BBR
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Remote System Discovery Commands
+*Triage and analysis*
+
+
 
-After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps.
-This can happen by running commands to enumerate network resources, users, connections, files, and installed security
-software.
+*Investigating Remote System Discovery Commands*
 
-This rule looks for the execution of the `arp` or `nbstat` utilities to enumerate remote systems in the environment,
-which is useful for attackers to identify lateral movement targets.
 
-#### Possible investigation steps
+After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+This rule looks for the execution of the `arp` or `nbstat` utilities to enumerate remote systems in the environment, which is useful for attackers to identify lateral movement targets.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+
 
-### False positive analysis
+*False positive analysis*
 
-- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify
-suspicious activity related to the user or host, such alerts can be dismissed.
 
-### Response and remediation
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
+
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and ((process.name :
-"nbtstat.exe" and process.args : ("-n", "-s")) or (process.name :
-"arp.exe" and process.args : "-a"))
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  ((process.name : "nbtstat.exe" and process.args : ("-n", "-s")) or
+  (process.name : "arp.exe" and process.args : "-a") or
+  (process.name : "nltest.exe" and process.args : ("/dclist", "/dsgetdc")) or
+  (process.name : "nslookup.exe" and process.args : "*_ldap._tcp.dc.*") or
+  (process.name: ("dsquery.exe", "dsget.exe") and process.args: "subnet") or
+  ((((process.name : "net.exe" or process.pe.original_file_name == "net.exe") or
+    ((process.name : "net1.exe" or process.pe.original_file_name == "net1.exe") and not 
+       process.parent.name : "net.exe")) and 
+       process.args : "group" and process.args : "/domain" and not process.args : "/add"))) and
+  not
+  (
+    (
+      process.name : "arp.exe" and
+      process.parent.executable : (
+        "?:\\ProgramData\\CentraStage\\AEMAgent\\AEMAgent.exe",
+        "?:\\Program Files (x86)\\Citrix\\Workspace Environment Management Agent\\Citrix.Wem.Agent.Service.exe",
+        "?:\\Program Files (x86)\\Lansweeper\\Service\\LansweeperService.exe"
+      )
+    )
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -109,42 +139,7 @@ process where event.type == "start" and ((process.name :
 ** Name: System Network Configuration Discovery
 ** ID: T1016
 ** Reference URL: https://attack.mitre.org/techniques/T1016/
-
-[[remote-system-discovery-commands-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-((process.name : "nbtstat.exe" and process.args : ("-n", "-s")) or
-(process.name : "arp.exe" and process.args : "-a"))
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "nbtstat.exe" and process.args : ("-n", "-s")) or
-(process.name : "arp.exe" and process.args : "-a")
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Technique:
+** Name: Remote System Discovery
+** ID: T1018
+** Reference URL: https://attack.mitre.org/techniques/T1018/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-windows-service-installed.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-windows-service-installed.asciidoc
index 9cf7f704b5..9530359e38 100644
--- a/docs/detections/prebuilt-rules/rule-details/remote-windows-service-installed.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remote-windows-service-installed.asciidoc
@@ -5,76 +5,79 @@ Identifies a network logon followed by Windows service creation with same LogonI
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-* Persistence
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Persistence
 
-*Version*: 1
+*Version*: 6
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by winlog.logon.id, host.id with maxspan=1m [authentication
-where event.action == "logged-in" and winlog.logon.type : "Network"
-and event.outcome=="success" and source.ip != null and source.ip !=
-"127.0.0.1" and source.ip != "::1"] [iam where event.action ==
-"service-installed" and not winlog.event_data.SubjectLogonId :
-"0x3e7" and not winlog.event_data.ServiceFileName :
-("?:\\Windows\\ADCR_Agent\\adcrsvc.exe",
-"?:\\Windows\\System32\\VSSVC.exe",
-"?:\\Windows\\servicing\\TrustedInstaller.exe",
-"?:\\Windows\\System32\\svchost.exe", "?:\\Program
-Files (x86)\\*.exe", "?:\\Program Files\\*.exe",
-"?:\\Windows\\PSEXESVC.EXE",
-"?:\\Windows\\System32\\sppsvc.exe",
-"?:\\Windows\\System32\\wbem\\WmiApSrv.exe",
-"?:\\WINDOWS\\RemoteAuditService.exe",
-"?:\\Windows\\VeeamVssSupport\\VeeamGuestHelper.exe",
-"?:\\Windows\\VeeamLogShipper\\VeeamLogShipper.exe",
-"?:\\Windows\\CAInvokerService.exe",
-"?:\\Windows\\System32\\upfc.exe",
-"?:\\Windows\\AdminArsenal\\PDQ*.exe",
-"?:\\Windows\\System32\\vds.exe",
-"?:\\Windows\\Veeam\\Backup\\VeeamDeploymentSvc.exe",
-"?:\\Windows\\ProPatches\\Scheduler\\STSchedEx.exe",
-"?:\\Windows\\System32\\certsrv.exe",
-"?:\\Windows\\eset-remote-install-service.exe",
-"?:\\Pella Corporation\\Pella Order Management\\GPAutoSvc.exe",
-"?:\\Pella Corporation\\OSCToGPAutoService\\OSCToGPAutoSvc.exe",
-"?:\\Pella Corporation\\Pella Order Management\\GPAutoSvc.exe",
-"?:\\Windows\\SysWOW64\\NwxExeSvc\\NwxExeSvc.exe",
-"?:\\Windows\\System32\\taskhostex.exe")]
+[source, js]
 ----------------------------------
+sequence by winlog.logon.id, winlog.computer_name with maxspan=1m
+[authentication where event.action == "logged-in" and winlog.logon.type : "Network" and
+event.outcome=="success" and source.ip != null and source.ip != "127.0.0.1" and source.ip != "::1"]
+[iam where event.action == "service-installed" and
+ not winlog.event_data.SubjectLogonId : "0x3e7" and
+ not winlog.event_data.ServiceFileName :
+               ("?:\\Windows\\ADCR_Agent\\adcrsvc.exe",
+                "?:\\Windows\\System32\\VSSVC.exe",
+                "?:\\Windows\\servicing\\TrustedInstaller.exe",
+                "?:\\Windows\\System32\\svchost.exe",
+                "?:\\Program Files (x86)\\*.exe",
+                "?:\\Program Files\\*.exe",
+                "?:\\Windows\\PSEXESVC.EXE",
+                "?:\\Windows\\System32\\sppsvc.exe",
+                "?:\\Windows\\System32\\wbem\\WmiApSrv.exe",
+                "?:\\WINDOWS\\RemoteAuditService.exe",
+                "?:\\Windows\\VeeamVssSupport\\VeeamGuestHelper.exe",
+                "?:\\Windows\\VeeamLogShipper\\VeeamLogShipper.exe",
+                "?:\\Windows\\CAInvokerService.exe",
+                "?:\\Windows\\System32\\upfc.exe",
+                "?:\\Windows\\AdminArsenal\\PDQ*.exe",
+                "?:\\Windows\\System32\\vds.exe",
+                "?:\\Windows\\Veeam\\Backup\\VeeamDeploymentSvc.exe",
+                "?:\\Windows\\ProPatches\\Scheduler\\STSchedEx.exe",
+                "?:\\Windows\\System32\\certsrv.exe",
+                "?:\\Windows\\eset-remote-install-service.exe",
+                "?:\\Pella Corporation\\Pella Order Management\\GPAutoSvc.exe",
+                "?:\\Pella Corporation\\OSCToGPAutoService\\OSCToGPAutoSvc.exe",
+                "?:\\Pella Corporation\\Pella Order Management\\GPAutoSvc.exe",
+                "?:\\Windows\\SysWOW64\\NwxExeSvc\\NwxExeSvc.exe",
+                "?:\\Windows\\System32\\taskhostex.exe")]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -86,8 +89,6 @@ Files (x86)\\*.exe", "?:\\Program Files\\*.exe",
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -96,3 +97,7 @@ Files (x86)\\*.exe", "?:\\Program Files\\*.exe",
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/remote-xsl-script-execution-via-com.asciidoc b/docs/detections/prebuilt-rules/rule-details/remote-xsl-script-execution-via-com.asciidoc
new file mode 100644
index 0000000000..3dd1319de7
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/remote-xsl-script-execution-via-com.asciidoc
@@ -0,0 +1,84 @@
+[[remote-xsl-script-execution-via-com]]
+=== Remote XSL Script Execution via COM
+
+Identifies the execution of a hosted XSL script using the Microsoft.XMLDOM COM interface via Microsoft Office processes. This behavior may indicate adversarial activity to execute malicious JScript or VBScript on the system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* logs-endpoint.events.library-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence with maxspan=1m
+ [library where host.os.type == "windows" and dll.name : "msxml3.dll" and
+  process.name : ("winword.exe", "excel.exe", "powerpnt.exe", "mspub.exe")] by process.entity_id
+ [process where host.os.type == "windows" and event.action == "start" and
+  process.parent.name : ("winword.exe", "excel.exe", "powerpnt.exe", "mspub.exe") and 
+  not process.executable :
+        ("?:\\Windows\\System32\\WerFault.exe",
+         "?:\\Windows\\SysWoW64\\WerFault.exe",
+         "?:\\windows\\splwow64.exe",
+         "?:\\Windows\\System32\\conhost.exe",
+         "?:\\Program Files\\*.exe",
+         "?:\\Program Files (x86)\\*exe")] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: XSL Script Processing
+** ID: T1220
+** Reference URL: https://attack.mitre.org/techniques/T1220/
diff --git a/docs/detections/prebuilt-rules/rule-details/remotely-started-services-via-rpc.asciidoc b/docs/detections/prebuilt-rules/rule-details/remotely-started-services-via-rpc.asciidoc
index 62ce906cf4..d24fb596d7 100644
--- a/docs/detections/prebuilt-rules/rule-details/remotely-started-services-via-rpc.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/remotely-started-services-via-rpc.asciidoc
@@ -1,106 +1,103 @@
 [[remotely-started-services-via-rpc]]
 === Remotely Started Services via RPC
 
-Identifies remote execution of Windows services over remote procedure call (RPC). This could be indicative of lateral movement, but will be noisy if commonly done by administrators."
+Identifies remote execution of Windows services over remote procedure call (RPC). This could be indicative of lateral movement, but will be noisy if commonly done by administrators.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-scmr/705b624a-13de-43cc-b8a2-99573da3635f
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-* Investigation Guide
-
-*Version*: 102 (<<remotely-started-services-via-rpc-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Remotely Started Services via RPC
+*Triage and analysis*
+
 
-The Service Control Manager Remote Protocol is a client/server protocol used for configuring and controlling service
-programs running on a remote computer. A remote service management session begins with the client initiating the
-connection request to the server. If the server grants the request, the connection is established. The client can then
-make multiple requests to modify, query the configuration, or start and stop services on the server by using the same
-session until the session is terminated.
 
-This rule detects the remote creation or start of a service by correlating a `services.exe` network connection and the
-spawn of a child process.
+*Investigating Remotely Started Services via RPC*
+
+
+The Service Control Manager Remote Protocol is a client/server protocol used for configuring and controlling service programs running on a remote computer. A remote service management session begins with the client initiating the connection request to the server. If the server grants the request, the connection is established. The client can then make multiple requests to modify, query the configuration, or start and stop services on the server by using the same session until the session is terminated.
+
+This rule detects the remote creation or start of a service by correlating a `services.exe` network connection and the spawn of a child process.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
-
-#### Possible investigation steps
-
-- Review login events (e.g., 4624) in the alert timeframe to identify the account used to perform this action. Use the
-`source.address` field to help identify the source system.
-- Review network events from the source system using the source port identified on the alert and try to identify the
-program used to initiate the action.
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Review login events (e.g., 4624) in the alert timeframe to identify the account used to perform this action. Use the `source.address` field to help identify the source system.
+- Review network events from the source system using the source port identified on the alert and try to identify the program used to initiate the action.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Validate if the activity is not related to planned patches, updates, network administrator activity, or legitimate
-software installations.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Validate if the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
 
 
-### False positive analysis
+*False positive analysis*
+
 
 - Remote management software like SCCM may trigger this rule. If noisy on your environment, consider adding exceptions.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
@@ -108,63 +105,58 @@ software installations.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence with maxspan=1s [network where process.name :
-"services.exe" and network.direction : ("incoming", "ingress")
-and network.transport == "tcp" and source.port >= 49152 and
-destination.port >= 49152 and source.ip != "127.0.0.1" and source.ip
-!= "::1" ] by host.id, process.entity_id [process where
-event.type == "start" and process.parent.name : "services.exe" and
-not (process.name : "svchost.exe" and process.args :
-"tiledatamodelsvc") and not (process.name : "msiexec.exe" and
-process.args : "/V") and not process.executable :
-("?:\\Windows\\ADCR_Agent\\adcrsvc.exe",
-"?:\\Windows\\System32\\VSSVC.exe",
-"?:\\Windows\\servicing\\TrustedInstaller.exe",
-"?:\\Windows\\System32\\svchost.exe", "?:\\Program
-Files (x86)\\*.exe", "?:\\Program Files\\*.exe",
-"?:\\Windows\\PSEXESVC.EXE",
-"?:\\Windows\\System32\\sppsvc.exe",
-"?:\\Windows\\System32\\wbem\\WmiApSrv.exe",
-"?:\\WINDOWS\\RemoteAuditService.exe",
-"?:\\Windows\\VeeamVssSupport\\VeeamGuestHelper.exe",
-"?:\\Windows\\VeeamLogShipper\\VeeamLogShipper.exe",
-"?:\\Windows\\CAInvokerService.exe",
-"?:\\Windows\\System32\\upfc.exe",
-"?:\\Windows\\AdminArsenal\\PDQ*.exe",
-"?:\\Windows\\System32\\vds.exe",
-"?:\\Windows\\Veeam\\Backup\\VeeamDeploymentSvc.exe",
-"?:\\Windows\\ProPatches\\Scheduler\\STSchedEx.exe",
-"?:\\Windows\\System32\\certsrv.exe",
-"?:\\Windows\\eset-remote-install-service.exe",
-"?:\\Pella Corporation\\Pella Order Management\\GPAutoSvc.exe",
-"?:\\Pella Corporation\\OSCToGPAutoService\\OSCToGPAutoSvc.exe",
-"?:\\Pella Corporation\\Pella Order Management\\GPAutoSvc.exe",
-"?:\\Windows\\SysWOW64\\NwxExeSvc\\NwxExeSvc.exe",
-"?:\\Windows\\System32\\taskhostex.exe") ] by host.id,
-process.parent.entity_id
+[source, js]
 ----------------------------------
+sequence with maxspan=1s
+   [network where host.os.type == "windows" and process.name : "services.exe" and
+      network.direction : ("incoming", "ingress") and network.transport == "tcp" and
+      source.port >= 49152 and destination.port >= 49152 and source.ip != "127.0.0.1" and source.ip != "::1"
+   ] by host.id, process.entity_id
+   [process where host.os.type == "windows" and 
+       event.type == "start" and process.parent.name : "services.exe" and
+       not (process.executable : "?:\\Windows\\System32\\msiexec.exe" and process.args : "/V") and
+       not process.executable : (
+                "?:\\Pella Corporation\\OSCToGPAutoService\\OSCToGPAutoSvc.exe",
+                "?:\\Pella Corporation\\Pella Order Management\\GPAutoSvc.exe",
+                "?:\\Pella Corporation\\Pella Order Management\\GPAutoSvc.exe",
+                "?:\\Program Files (x86)\\*.exe",
+                "?:\\Program Files\\*.exe",
+                "?:\\Windows\\ADCR_Agent\\adcrsvc.exe",
+                "?:\\Windows\\AdminArsenal\\PDQ*.exe",
+                "?:\\Windows\\CAInvokerService.exe",
+                "?:\\Windows\\ccmsetup\\ccmsetup.exe",
+                "?:\\Windows\\eset-remote-install-service.exe",
+                "?:\\Windows\\ProPatches\\Scheduler\\STSchedEx.exe",
+                "?:\\Windows\\PSEXESVC.EXE",
+                "?:\\Windows\\RemoteAuditService.exe",
+                "?:\\Windows\\servicing\\TrustedInstaller.exe",
+                "?:\\Windows\\System32\\certsrv.exe",
+                "?:\\Windows\\System32\\sppsvc.exe",
+                "?:\\Windows\\System32\\srmhost.exe",
+                "?:\\Windows\\System32\\svchost.exe",
+                "?:\\Windows\\System32\\taskhostex.exe",
+                "?:\\Windows\\System32\\upfc.exe",
+                "?:\\Windows\\System32\\vds.exe",
+                "?:\\Windows\\System32\\VSSVC.exe",
+                "?:\\Windows\\System32\\wbem\\WmiApSrv.exe",
+                "?:\\Windows\\SysWOW64\\NwxExeSvc\\NwxExeSvc.exe",
+                "?:\\Windows\\Veeam\\Backup\\VeeamDeploymentSvc.exe",
+                "?:\\Windows\\VeeamLogShipper\\VeeamLogShipper.exe",
+                "?:\\Windows\\VeeamVssSupport\\VeeamGuestHelper.exe"
+       )] by host.id, process.parent.entity_id
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -176,109 +168,3 @@ process.parent.entity_id
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[remotely-started-services-via-rpc-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1s [network where process.name :
-"services.exe" and network.direction : ("incoming", "ingress")
-and network.transport == "tcp" and source.port >= 49152 and
-destination.port >= 49152 and source.ip != "127.0.0.1" and source.ip
-!= "::1" ] by host.id, process.entity_id [process where
-event.type in ("start", "process_started") and process.parent.name :
-"services.exe" and not (process.name : "svchost.exe" and
-process.args : "tiledatamodelsvc") and not (process.name :
-"msiexec.exe" and process.args : "/V") and not
-process.executable :
-("?:\\Windows\\ADCR_Agent\\adcrsvc.exe",
-"?:\\Windows\\System32\\VSSVC.exe",
-"?:\\Windows\\servicing\\TrustedInstaller.exe",
-"?:\\Windows\\System32\\svchost.exe", "?:\\Program
-Files (x86)\\*.exe", "?:\\Program Files\\*.exe",
-"?:\\Windows\\PSEXESVC.EXE",
-"?:\\Windows\\System32\\sppsvc.exe",
-"?:\\Windows\\System32\\wbem\\WmiApSrv.exe",
-"?:\\WINDOWS\\RemoteAuditService.exe",
-"?:\\Windows\\VeeamVssSupport\\VeeamGuestHelper.exe",
-"?:\\Windows\\VeeamLogShipper\\VeeamLogShipper.exe",
-"?:\\Windows\\CAInvokerService.exe",
-"?:\\Windows\\System32\\upfc.exe",
-"?:\\Windows\\AdminArsenal\\PDQ*.exe",
-"?:\\Windows\\System32\\vds.exe",
-"?:\\Windows\\Veeam\\Backup\\VeeamDeploymentSvc.exe",
-"?:\\Windows\\ProPatches\\Scheduler\\STSchedEx.exe",
-"?:\\Windows\\System32\\certsrv.exe",
-"?:\\Windows\\eset-remote-install-service.exe",
-"?:\\Pella Corporation\\Pella Order Management\\GPAutoSvc.exe",
-"?:\\Pella Corporation\\OSCToGPAutoService\\OSCToGPAutoSvc.exe",
-"?:\\Pella Corporation\\Pella Order Management\\GPAutoSvc.exe",
-"?:\\Windows\\SysWOW64\\NwxExeSvc\\NwxExeSvc.exe",
-"?:\\Windows\\System32\\taskhostex.exe") ] by host.id,
-process.parent.entity_id
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1s [network where process.name :
-"services.exe" and network.direction : ("incoming", "ingress")
-and network.transport == "tcp" and source.port >= 49152 and
-destination.port >= 49152 and source.ip != "127.0.0.1" and source.ip
-!= "::1" ] by host.id, process.entity_id [process where
-event.type in ("start", "process_started") and process.parent.name :
-"services.exe" and not (process.name : "svchost.exe" and
-process.args : "tiledatamodelsvc") and not (process.name :
-"msiexec.exe" and process.args : "/V") /* uncomment if psexec
-is noisy in your environment */ /* and not process.name :
-"PSEXESVC.exe" */ ] by host.id, process.parent.entity_id
-----------------------------------
-
-Version 4 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1s [network where process.name :
-"services.exe" and network.direction : ("incoming", "ingress")
-and network.transport == "tcp" and source.port >= 49152 and
-destination.port >= 49152 and source.address not in ("127.0.0.1",
-"::1") ] by host.id, process.entity_id [process where
-event.type in ("start", "process_started") and process.parent.name :
-"services.exe" and not (process.name : "svchost.exe" and
-process.args : "tiledatamodelsvc") and not (process.name :
-"msiexec.exe" and process.args : "/V") /* uncomment if psexec
-is noisy in your environment */ /* and not process.name :
-"PSEXESVC.exe" */ ] by host.id, process.parent.entity_id
-----------------------------------
-
-Version 3 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1s [network where process.name :
-"services.exe" and network.direction == "incoming" and
-network.transport == "tcp" and source.port >= 49152 and
-destination.port >= 49152 and source.address not in ("127.0.0.1",
-"::1") ] by host.id, process.entity_id [process where
-event.type in ("start", "process_started") and process.parent.name :
-"services.exe" and not (process.name : "svchost.exe" and
-process.args : "tiledatamodelsvc") and not (process.name :
-"msiexec.exe" and process.args : "/V") /* uncomment if psexec
-is noisy in your environment */ /* and not process.name :
-"PSEXESVC.exe" */ ] by host.id, process.parent.entity_id
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/renamed-autoit-scripts-interpreter.asciidoc b/docs/detections/prebuilt-rules/rule-details/renamed-autoit-scripts-interpreter.asciidoc
index ca1b4fdf0e..9bceb6b00c 100644
--- a/docs/detections/prebuilt-rules/rule-details/renamed-autoit-scripts-interpreter.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/renamed-autoit-scripts-interpreter.asciidoc
@@ -5,114 +5,144 @@ Identifies a suspicious AutoIt process execution. Malware written as an AutoIt s
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<renamed-autoit-scripts-interpreter-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Renamed AutoIt Scripts Interpreter*
 
-[source,js]
-----------------------------------
-process where event.type == "start" and
-process.pe.original_file_name : "AutoIt*.exe" and not process.name :
-"AutoIt*.exe"
-----------------------------------
 
-==== Threat mapping
+The OriginalFileName attribute of a PE (Portable Executable) file is a metadata field that contains the original name of the executable file when compiled or linked. By using this attribute, analysts can identify renamed instances that attackers can use with the intent of evading detections, application allowlists, and other security protections.
 
-*Framework*: MITRE ATT&CK^TM^
+AutoIt is a scripting language and tool for automating tasks on Microsoft Windows operating systems. Due to its capabilities, malicious threat actors can abuse it to create malicious scripts and distribute malware.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Masquerading
-** ID: T1036
-** Reference URL: https://attack.mitre.org/techniques/T1036/
+This rule checks for renamed instances of AutoIt, which can indicate an attempt of evading detections, application allowlists, and other security protections.
 
-[[renamed-autoit-scripts-interpreter-history]]
-==== Rule version history
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.pe.original_file_name : "AutoIt*.exe" and not process.name :
-"AutoIt*.exe"
-----------------------------------
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
 
-Version 8 (8.4.0 release)::
-* Formatting only
 
-Version 6 (8.2.0 release)::
-* Formatting only
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-Version 5 (7.16.0 release)::
-* Formatting only
 
-Version 4 (7.12.0 release)::
-* Formatting only
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
 
-Version 3 (7.11.2 release)::
-* Formatting only
 
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.category:process AND event.type:(start OR process_started) AND (
-process.pe.original_file_name:/[aA][uU][tT][oO][iI][tT]\d\.[eE][xX][eE
-]/ OR winlog.event_data.OriginalFileName:/[aA][uU][tT][oO][iI][tT]\d\.
-[eE][xX][eE]/) AND NOT
-process.name:/[aA][uU][tT][oO][iI][tT]\d{1,3}\.[eE][xX][eE]/
+process where host.os.type == "windows" and event.type == "start" and
+  process.pe.original_file_name : "AutoIt*.exe" and not process.name : "AutoIt*.exe"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Rename System Utilities
+** ID: T1036.003
+** Reference URL: https://attack.mitre.org/techniques/T1036/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/renamed-utility-executed-with-short-program-name.asciidoc b/docs/detections/prebuilt-rules/rule-details/renamed-utility-executed-with-short-program-name.asciidoc
new file mode 100644
index 0000000000..415108beb9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/renamed-utility-executed-with-short-program-name.asciidoc
@@ -0,0 +1,132 @@
+[[renamed-utility-executed-with-short-program-name]]
+=== Renamed Utility Executed with Short Program Name
+
+Identifies the execution of a process with a single character process name, differing from the original file name. This is often done by adversaries while staging, executing temporary utilities, or trying to bypass security detections based on the process name.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 109
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Renamed Utility Executed with Short Program Name*
+
+
+Identifies the execution of a process with a single character process name, differing from the original file name. This is often done by adversaries while staging, executing temporary utilities, or trying to bypass security detections based on the process name.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, command line and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and length(process.name) > 0 and
+ length(process.name) == 5 and length(process.pe.original_file_name) > 5
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Rename System Utilities
+** ID: T1036.003
+** Reference URL: https://attack.mitre.org/techniques/T1036/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/root-network-connection-via-gdb-cap-sys-ptrace.asciidoc b/docs/detections/prebuilt-rules/rule-details/root-network-connection-via-gdb-cap-sys-ptrace.asciidoc
new file mode 100644
index 0000000000..81e96dee33
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/root-network-connection-via-gdb-cap-sys-ptrace.asciidoc
@@ -0,0 +1,132 @@
+[[root-network-connection-via-gdb-cap-sys-ptrace]]
+=== Root Network Connection via GDB CAP_SYS_PTRACE
+
+Identifies instances where GDB (granted the CAP_SYS_PTRACE capability) is executed, after which an outbound network connection is initiated by UID/GID 0 (root). In Linux, the CAP_SYS_PTRACE capability grants a process the ability to use the ptrace system call, which is typically used for debugging and allows the process to trace and control other processes. Attackers may leverage this capability to hook and inject into a process that is running with root permissions in order to execute shell code and gain a reverse shell with root privileges.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Execution
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.entry_leader.entity_id with maxspan=30s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and process.name == "gdb" and
+   (process.thread.capabilities.effective : "CAP_SYS_PTRACE" or process.thread.capabilities.permitted : "CAP_SYS_PTRACE") and
+   user.id != "0"]
+  [network where host.os.type == "linux" and event.action == "connection_attempted" and event.type == "start" and
+   process.name != null and user.id == "0"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
+* Sub-technique:
+** Name: Ptrace System Calls
+** ID: T1055.008
+** Reference URL: https://attack.mitre.org/techniques/T1055/008/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/roshal-archive-rar-or-powershell-file-downloaded-from-the-internet.asciidoc b/docs/detections/prebuilt-rules/rule-details/roshal-archive-rar-or-powershell-file-downloaded-from-the-internet.asciidoc
index a15dd3880b..d03056987a 100644
--- a/docs/detections/prebuilt-rules/rule-details/roshal-archive-rar-or-powershell-file-downloaded-from-the-internet.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/roshal-archive-rar-or-powershell-file-downloaded-from-the-internet.asciidoc
@@ -5,83 +5,96 @@ Detects a Roshal Archive (RAR) file or PowerShell script downloaded from the int
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.fireeye.com/blog/threat-research/2017/04/fin7-phishing-lnk.html
 * https://www.justice.gov/opa/press-release/file/1084361/download
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
-
-* Elastic
-* Network
-* Threat Detection
-* Command and Control
-* Host
+*Tags*: 
 
-*Version*: 100 (<<roshal-archive-rar-or-powershell-file-downloaded-from-the-internet-history, version history>>)
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Domain: Endpoint
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Downloading RAR or PowerShell files from the Internet may be expected for certain systems. This rule should be tailored to either exclude systems as sources or destinations in which this behavior is expected.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Threat intel
 
-This activity has been observed in FIN7 campaigns.
-----------------------------------
+*Threat intel*
 
 
+This activity has been observed in FIN7 campaigns.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and network.protocol:http
-and (url.extension:(ps1 or rar) or url.path:(*.ps1 or *.rar)) and
-not destination.ip:( 10.0.0.0/8 or 127.0.0.0/8 or
-169.254.0.0/16 or 172.16.0.0/12 or 192.0.0.0/24 or
-192.0.0.0/29 or 192.0.0.8/32 or 192.0.0.9/32 or
-192.0.0.10/32 or 192.0.0.170/32 or 192.0.0.171/32 or
-192.0.2.0/24 or 192.31.196.0/24 or 192.52.193.0/24 or
-192.168.0.0/16 or 192.88.99.0/24 or 224.0.0.0/4 or
-100.64.0.0/10 or 192.175.48.0/24 or 198.18.0.0/15 or
-198.51.100.0/24 or 203.0.113.0/24 or 240.0.0.0/4 or
-"::1" or "FE80::/10" or "FF00::/8" ) and
-source.ip:( 10.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 )
+[source, js]
 ----------------------------------
+(event.dataset: (network_traffic.http or network_traffic.tls) or
+  (event.category: (network or network_traffic) and network.protocol: http)) and
+  (url.extension:(ps1 or rar) or url.path:(*.ps1 or *.rar)) and
+    not destination.ip:(
+      10.0.0.0/8 or
+      127.0.0.0/8 or
+      169.254.0.0/16 or
+      172.16.0.0/12 or
+      192.0.0.0/24 or
+      192.0.0.0/29 or
+      192.0.0.8/32 or
+      192.0.0.9/32 or
+      192.0.0.10/32 or
+      192.0.0.170/32 or
+      192.0.0.171/32 or
+      192.0.2.0/24 or
+      192.31.196.0/24 or
+      192.52.193.0/24 or
+      192.168.0.0/16 or
+      192.88.99.0/24 or
+      224.0.0.0/4 or
+      100.64.0.0/10 or
+      192.175.48.0/24 or
+      198.18.0.0/15 or
+      198.51.100.0/24 or
+      203.0.113.0/24 or
+      240.0.0.0/4 or
+      "::1" or
+      "FE80::/10" or
+      "FF00::/8"
+    ) and
+    source.ip:(
+      10.0.0.0/8 or
+      172.16.0.0/12 or
+      192.168.0.0/16
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -93,41 +106,3 @@ source.ip:( 10.0.0.0/8 or 172.16.0.0/12 or
 ** Name: Ingress Tool Transfer
 ** ID: T1105
 ** Reference URL: https://attack.mitre.org/techniques/T1105/
-
-[[roshal-archive-rar-or-powershell-file-downloaded-from-the-internet-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 10 (8.4.0 release)::
-* Formatting only
-
-Version 9 (8.0.0 release)::
-* Formatting only
-
-Version 8 (7.16.0 release)::
-* Formatting only
-
-Version 7 (7.15.0 release)::
-* Formatting only
-
-Version 6 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network OR network_traffic) AND network.protocol:http
-AND url.path:/.*(rar|ps1)/ AND source.ip:(10.0.0.0\/8 OR
-172.16.0.0\/12 OR 192.168.0.0\/16)
-----------------------------------
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/route53-resolver-query-log-configuration-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/route53-resolver-query-log-configuration-deleted.asciidoc
new file mode 100644
index 0000000000..ed54a15ac8
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/route53-resolver-query-log-configuration-deleted.asciidoc
@@ -0,0 +1,123 @@
+[[route53-resolver-query-log-configuration-deleted]]
+=== Route53 Resolver Query Log Configuration Deleted
+
+Identifies when a Route53 Resolver Query Log Configuration is deleted. When a Route53 Resolver query log configuration is deleted, Resolver stops logging DNS queries and responses for the specified configuration. Adversaries may delete query log configurations to evade detection or cover their tracks.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-aws.cloudtrail*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 10m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_DeleteResolverQueryLogConfig.html
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Data Source: Amazon Route53
+* Use Case: Log Auditing
+* Resources: Investigation Guide
+* Tactic: Defense Evasion
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+*Triage and Analysis*
+
+
+
+*Investigating Route53 Resolver Query Log Configuration Deleted*
+
+
+This rule detects when a Route53 Resolver Query Log Configuration is deleted. Deleting these configurations stops the logging of DNS queries and responses, which can significantly impede network monitoring and compromise security visibility. Adversaries may delete these configurations to evade detection, remove evidence, or obscure their activities within a network.
+
+Adversaries target Route53 Resolver query log configurations because these logs can contain evidence of malicious domain queries or responses. By deleting these logs, an adversary can prevent the capture of information that could reveal unauthorized network activities, aiding in avoiding detection and thwarting incident response efforts.
+
+
+*Possible Investigation Steps*
+
+
+- **Review the Deletion Details**: Examine the CloudTrail logs to identify when and by whom the deletion was initiated.
+    - Check the `event.action` and `user_identity` elements to understand the scope and authorization of the deletion.
+- **Contextualize with User Actions**: Assess whether the deletion aligns with the user’s role and job responsibilities.
+    - Investigate if similar modifications have occurred recently that could suggest a pattern or broader campaign.
+- **Analyze Access Patterns and Permissions**: Verify whether the user had the appropriate permissions to delete log configurations.
+    - Investigate any recent permission changes that might indicate role abuse or credentials compromise.
+- **Correlate with Other Security Incidents**: Look for related security alerts or incidents that could be connected to the log deletion.
+    - This includes unusual network traffic, alerts from other AWS services, or findings from intrusion detection systems.
+- **Interview the Responsible Team**: If the deletion was initiated by an internal team member, confirm their intent and authorization to ensure it was a legitimate action.
+
+
+*False Positive Analysis*
+
+
+- **Legitimate Administrative Actions**: Confirm that the deletion was part of scheduled IT operations or network management activities, possibly linked to maintenance or infrastructure updates. Validate this action against change management records or through interviews with relevant personnel.
+
+
+*Response and Remediation*
+
+
+- **Restore Logs if Feasible**: If the deletion was unauthorized, consider restoring the configuration from backups to ensure continuous visibility into DNS queries.
+- **Review and Tighten Permissions**: Ensure that only authorized personnel have the capability to delete critical configurations.
+    - Adjust AWS IAM policies to reinforce security measures.
+- **Enhance Monitoring of Log Management**: Implement or enhance monitoring rules to detect and alert on unauthorized changes to logging configurations, focusing on critical deletions.
+- **Conduct Comprehensive Security Review**: If the deletion is verified as malicious, initiate a thorough security assessment to identify any further unauthorized changes or ongoing malicious activities.
+
+
+*Additional Information*
+
+
+For detailed instructions on managing Route53 Resolver and securing its configurations, refer to the https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_DeleteResolverQueryLogConfig.html[Amazon Route53 Resolver documentation].
+
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:aws.cloudtrail and event.provider: route53resolver.amazonaws.com
+    and event.action: DeleteResolverQueryLogConfig and event.outcome: success
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Cloud Logs
+** ID: T1562.008
+** Reference URL: https://attack.mitre.org/techniques/T1562/008/
diff --git a/docs/detections/prebuilt-rules/rule-details/rpc-remote-procedure-call-from-the-internet.asciidoc b/docs/detections/prebuilt-rules/rule-details/rpc-remote-procedure-call-from-the-internet.asciidoc
index b4c4dd8e00..f7c79e5403 100644
--- a/docs/detections/prebuilt-rules/rule-details/rpc-remote-procedure-call-from-the-internet.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/rpc-remote-procedure-call-from-the-internet.asciidoc
@@ -5,66 +5,84 @@ This rule detects network events that may indicate the use of RPC traffic from t
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Network
-* Threat Detection
-* Initial Access
-* Host
+* Tactic: Initial Access
+* Domain: Endpoint
+* Use Case: Threat Detection
 
-*Version*: 100 (<<rpc-remote-procedure-call-from-the-internet-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.6.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:135 or event.dataset:zeek.dce_rpc) and not
-source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
-172.16.0.0/12 or 192.0.0.0/24 or 192.0.0.0/29 or
-192.0.0.8/32 or 192.0.0.9/32 or 192.0.0.10/32 or
-192.0.0.170/32 or 192.0.0.171/32 or 192.0.2.0/24 or
-192.31.196.0/24 or 192.52.193.0/24 or 192.168.0.0/16 or
-192.88.99.0/24 or 224.0.0.0/4 or 100.64.0.0/10 or
-192.175.48.0/24 or 198.18.0.0/15 or 198.51.100.0/24 or
-203.0.113.0/24 or 240.0.0.0/4 or "::1" or "FE80::/10" or
-"FF00::/8" ) and destination.ip:( 10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16 )
+[source, js]
 ----------------------------------
+(event.dataset: network_traffic.flow or (event.category: (network or network_traffic))) and
+  network.transport:tcp and (destination.port:135 or event.dataset:zeek.dce_rpc) and
+  not source.ip:(
+    10.0.0.0/8 or
+    127.0.0.0/8 or
+    169.254.0.0/16 or
+    172.16.0.0/12 or
+    192.0.0.0/24 or
+    192.0.0.0/29 or
+    192.0.0.8/32 or
+    192.0.0.9/32 or
+    192.0.0.10/32 or
+    192.0.0.170/32 or
+    192.0.0.171/32 or
+    192.0.2.0/24 or
+    192.31.196.0/24 or
+    192.52.193.0/24 or
+    192.168.0.0/16 or
+    192.88.99.0/24 or
+    224.0.0.0/4 or
+    100.64.0.0/10 or
+    192.175.48.0/24 or
+    198.18.0.0/15 or
+    198.51.100.0/24 or
+    203.0.113.0/24 or
+    240.0.0.0/4 or
+    "::1" or
+    "FE80::/10" or
+    "FF00::/8"
+  ) and
+  destination.ip:(
+    10.0.0.0/8 or
+    172.16.0.0/12 or
+    192.168.0.0/16
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,75 +94,3 @@ source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[rpc-remote-procedure-call-from-the-internet-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 12 (8.4.0 release)::
-* Formatting only
-
-Version 11 (7.15.0 release)::
-* Formatting only
-
-Version 10 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:135 or event.dataset:zeek.dce_rpc) and not
-source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
-172.16.0.0/12 or 192.168.0.0/16 or 224.0.0.0/4 or "::1" or "FE80::/10"
-or "FF00::/8" ) and destination.ip:( 10.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 )
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:135 or event.dataset:zeek.dce_rpc) and not
-source.ip:(10.0.0.0/8 or 127.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 or "::1") and destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport:tcp and destination.port:135 and not
-source.ip:(10.0.0.0/8 or 127.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 or "::1") and destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
-Version 3 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport: tcp and destination.port: 135 and (
-network.direction: inbound or ( not source.ip: (10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16) and destination.ip: (10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16) ) )
-----------------------------------
-
-Version 2 (7.6.1 release)::
-* Removed auditbeat-\*, packetbeat-*, and winlogbeat-* from the rule indices.
-
diff --git a/docs/detections/prebuilt-rules/rule-details/rpc-remote-procedure-call-to-the-internet.asciidoc b/docs/detections/prebuilt-rules/rule-details/rpc-remote-procedure-call-to-the-internet.asciidoc
index 4d02fea61e..c7bc8f0e06 100644
--- a/docs/detections/prebuilt-rules/rule-details/rpc-remote-procedure-call-to-the-internet.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/rpc-remote-procedure-call-to-the-internet.asciidoc
@@ -5,66 +5,84 @@ This rule detects network events that may indicate the use of RPC traffic to the
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Network
-* Threat Detection
-* Initial Access
-* Host
+* Tactic: Initial Access
+* Domain: Endpoint
+* Use Case: Threat Detection
 
-*Version*: 100 (<<rpc-remote-procedure-call-to-the-internet-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.6.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:135 or event.dataset:zeek.dce_rpc) and
-source.ip:( 10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16
-) and not destination.ip:( 10.0.0.0/8 or 127.0.0.0/8 or
-169.254.0.0/16 or 172.16.0.0/12 or 192.0.0.0/24 or
-192.0.0.0/29 or 192.0.0.8/32 or 192.0.0.9/32 or
-192.0.0.10/32 or 192.0.0.170/32 or 192.0.0.171/32 or
-192.0.2.0/24 or 192.31.196.0/24 or 192.52.193.0/24 or
-192.168.0.0/16 or 192.88.99.0/24 or 224.0.0.0/4 or
-100.64.0.0/10 or 192.175.48.0/24 or 198.18.0.0/15 or
-198.51.100.0/24 or 203.0.113.0/24 or 240.0.0.0/4 or "::1"
-or "FE80::/10" or "FF00::/8" )
+[source, js]
 ----------------------------------
+(event.dataset: network_traffic.flow or (event.category: (network or network_traffic))) and
+  network.transport:tcp and (destination.port:135 or event.dataset:zeek.dce_rpc) and
+  source.ip:(
+    10.0.0.0/8 or
+    172.16.0.0/12 or
+    192.168.0.0/16
+  ) and
+  not destination.ip:(
+    10.0.0.0/8 or
+    127.0.0.0/8 or
+    169.254.0.0/16 or
+    172.16.0.0/12 or
+    192.0.0.0/24 or
+    192.0.0.0/29 or
+    192.0.0.8/32 or
+    192.0.0.9/32 or
+    192.0.0.10/32 or
+    192.0.0.170/32 or
+    192.0.0.171/32 or
+    192.0.2.0/24 or
+    192.31.196.0/24 or
+    192.52.193.0/24 or
+    192.168.0.0/16 or
+    192.88.99.0/24 or
+    224.0.0.0/4 or
+    100.64.0.0/10 or
+    192.175.48.0/24 or
+    198.18.0.0/15 or
+    198.51.100.0/24 or
+    203.0.113.0/24 or
+    240.0.0.0/4 or
+    "::1" or
+    "FE80::/10" or
+    "FF00::/8"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,75 +94,3 @@ or "FE80::/10" or "FF00::/8" )
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[rpc-remote-procedure-call-to-the-internet-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 12 (8.4.0 release)::
-* Formatting only
-
-Version 11 (7.15.0 release)::
-* Formatting only
-
-Version 10 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:135 or event.dataset:zeek.dce_rpc) and
-source.ip:( 10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16 ) and not
-destination.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
-172.16.0.0/12 or 192.168.0.0/16 or 224.0.0.0/4 or "::1" or "FE80::/10"
-or "FF00::/8" )
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:135 or event.dataset:zeek.dce_rpc) and
-source.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) and not
-destination.ip:(10.0.0.0/8 or 127.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 or "::1")
-----------------------------------
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport:tcp and destination.port:135 and
-source.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) and not
-destination.ip:(10.0.0.0/8 or 127.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 or "::1")
-----------------------------------
-
-Version 3 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport: tcp and destination.port: 135 and (
-network.direction: outbound or ( source.ip: (10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16) and not destination.ip: (10.0.0.0/8
-or 172.16.0.0/12 or 192.168.0.0/16) ) )
-----------------------------------
-
-Version 2 (7.6.1 release)::
-* Removed auditbeat-\*, packetbeat-*, and winlogbeat-* from the rule indices.
-
diff --git a/docs/detections/prebuilt-rules/rule-details/scheduled-task-created-by-a-windows-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/scheduled-task-created-by-a-windows-script.asciidoc
index aa5331763e..d1e76cccdf 100644
--- a/docs/detections/prebuilt-rules/rule-details/scheduled-task-created-by-a-windows-script.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/scheduled-task-created-by-a-windows-script.asciidoc
@@ -5,70 +5,70 @@ A scheduled task was created by a Windows script via cscript.exe, wscript.exe or
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-endpoint.events.library-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 100 (<<scheduled-task-created-by-a-windows-script-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Legitimate scheduled tasks may be created during installation of new software.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-Decode the base64 encoded Tasks Actions registry value to investigate the task's configured action.
-----------------------------------
+*Triage and analysis*
 
 
+Decode the base64 encoded Tasks Actions registry value to investigate the task's configured action.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan = 30s [any where (event.category ==
-"library" or (event.category == "process" and event.action : "Image
-loaded*")) and (dll.name : "taskschd.dll" or file.name :
-"taskschd.dll") and process.name : ("cscript.exe", "wscript.exe",
-"powershell.exe", "pwsh.exe", "powershell_ise.exe")] [registry where
-registry.path : "HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions"]
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan = 30s
+  [any where host.os.type == "windows" and 
+    (event.category : ("library", "driver") or (event.category == "process" and event.action : "Image loaded*")) and
+    (?dll.name : "taskschd.dll" or file.name : "taskschd.dll") and
+    process.name : ("cscript.exe", "wscript.exe", "powershell.exe", "pwsh.exe", "powershell_ise.exe")]
+  [registry where host.os.type == "windows" and registry.path : (
+    "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions",
+    "\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions")]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,49 +80,23 @@ NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions"]
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[scheduled-task-created-by-a-windows-script-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan = 30s [library where dll.name :
-"taskschd.dll" and process.name : ("cscript.exe", "wscript.exe",
-"powershell.exe", "pwsh.exe", "powershell_ise.exe")] [registry where
-registry.path : "HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions"]
-----------------------------------
-
-Version 5 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan = 30s [library where dll.name :
-"taskschd.dll" and process.name : ("cscript.exe", "wscript.exe",
-"powershell.exe")] [registry where registry.path :
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions"]
-----------------------------------
-
-Version 3 (7.13.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan = 30s [library where file.name :
-"taskschd.dll" and process.name : ("cscript.exe", "wscript.exe",
-"powershell.exe")] [registry where registry.path :
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\TaskCache\\Tasks\\*\\Actions"]
-----------------------------------
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Visual Basic
+** ID: T1059.005
+** Reference URL: https://attack.mitre.org/techniques/T1059/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/scheduled-task-execution-at-scale-via-gpo.asciidoc b/docs/detections/prebuilt-rules/rule-details/scheduled-task-execution-at-scale-via-gpo.asciidoc
index b9ef549dda..bbb86b43d9 100644
--- a/docs/detections/prebuilt-rules/rule-details/scheduled-task-execution-at-scale-via-gpo.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/scheduled-task-execution-at-scale-via-gpo.asciidoc
@@ -5,22 +5,23 @@ Detects the modification of Group Policy Object attributes to execute a schedule
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0025_windows_audit_directory_service_changes.md
 * https://github.com/atc-project/atc-data/blob/f2bbb51ecf68e2c9f488e3c70dcdd3df51d2a46b/docs/Logging_Policies/LP_0029_windows_audit_detailed_file_share.md
@@ -28,85 +29,121 @@ Detects the modification of Group Policy Object attributes to execute a schedule
 * https://twitter.com/menasec1/status/1106899890377052160
 * https://github.com/SigmaHQ/sigma/blob/master/rules/windows/builtin/security/win_gpo_scheduledtasks.yml
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Active Directory
-* Investigation Guide
-
-*Version*: 102 (<<scheduled-task-execution-at-scale-via-gpo-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Lateral Movement
+* Data Source: Active Directory
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Scheduled Task Execution at Scale via GPO
+*Triage and analysis*
+
 
-Group Policy Objects (GPOs) can be used by attackers to execute scheduled tasks at scale to compromise objects controlled
-by a given GPO. This is done by changing the contents of the `<GPOPath>\Machine\Preferences\ScheduledTasks\ScheduledTasks.xml`
-file.
 
-#### Possible investigation steps
+*Investigating Scheduled Task Execution at Scale via GPO*
 
-- This attack abuses a legitimate mechanism of Active Directory, so it is important to determine whether the activity
-is legitimate and the administrator is authorized to perform this operation.
-- Retrieve the contents of the `ScheduledTasks.xml` file, and check the `<Command>` and `<Arguments>` XML tags for any
-potentially malicious commands or binaries.
+
+Group Policy Objects (GPOs) can be used by attackers to execute scheduled tasks at scale to compromise objects controlled by a given GPO. This is done by changing the contents of the `<GPOPath>\Machine\Preferences\ScheduledTasks\ScheduledTasks.xml` file.
+
+
+*Possible investigation steps*
+
+
+- This attack abuses a legitimate mechanism of Active Directory, so it is important to determine whether the activity is legitimate and the administrator is authorized to perform this operation.
+- Retrieve the contents of the `ScheduledTasks.xml` file, and check the `<Command>` and `<Arguments>` XML tags for any potentially malicious commands or binaries.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Scope which objects may be compromised by retrieving information about which objects are controlled by the GPO.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - Verify if the execution is allowed and done under change management, and if the execution is legitimate.
 
-### Related rules
+
+*Related rules*
+
 
 - Group Policy Abuse for Privilege Addition - b9554892-5e0e-424b-83a0-5aef95aa43bf
 - Startup/Logon Script added to Group Policy Object - 16fac1a1-21ee-4ca6-b720-458e3855d046
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - The investigation and containment must be performed in every computer controlled by the GPO, where necessary.
 - Remove the script from the GPO.
 - Check if other GPOs have suspicious scheduled tasks attached.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Detailed File Share' audit policy must be configured (Success Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+Object Access >
+Audit Detailed File Share (Success,Failure)
+```
+
+The 'Audit Directory Service Changes' audit policy must be configured (Success Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Changes (Success,Failure)
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-(event.code: "5136" and
-winlog.event_data.AttributeLDAPDisplayName:("gPCMachineExtensionNames"
-or "gPCUserExtensionNames") and winlog.event_data.AttributeValue:(*
-CAB54552-DEEA-4691-817E-ED4A4D1AFC72* and
-*AADCED64-746C-4633-A97C-D61349046527*)) or (event.code: "5145" and
-winlog.event_data.ShareName: "\\\\*\\SYSVOL" and
-winlog.event_data.RelativeTargetName: *ScheduledTasks.xml and
-(message: WriteData or winlog.event_data.AccessList: *%%4417*))
+[source, js]
 ----------------------------------
+(event.code: "5136" and winlog.event_data.AttributeLDAPDisplayName:("gPCMachineExtensionNames" or "gPCUserExtensionNames") and
+   winlog.event_data.AttributeValue:(*CAB54552-DEEA-4691-817E-ED4A4D1AFC72* and *AADCED64-746C-4633-A97C-D61349046527*))
+or
+(event.code: "5145" and winlog.event_data.ShareName: "\\\\*\\SYSVOL" and winlog.event_data.RelativeTargetName: *ScheduledTasks.xml and
+  (message: WriteData or winlog.event_data.AccessList: *%%4417*))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -118,37 +155,23 @@ winlog.event_data.RelativeTargetName: *ScheduledTasks.xml and
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[scheduled-task-execution-at-scale-via-gpo-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-(event.code: "5136" and
-winlog.event_data.AttributeLDAPDisplayName:("gPCMachineExtensionNames"
-or "gPCUserExtensionNames") and winlog.event_data.AttributeValue:(
-*CAB54552-DEEA-4691-817E-ED4A4D1AFC72* and
-*AADCED64-746C-4633-A97C-D61349046527*)) or (event.code: "5145" and
-winlog.event_data.ShareName: "\\\\*\\SYSVOL" and
-winlog.event_data.RelativeTargetName: *ScheduledTasks.xml and
-(message: WriteData or winlog.event_data.AccessList: *%%4417*))
-----------------------------------
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
+* Technique:
+** Name: Domain Policy Modification
+** ID: T1484
+** Reference URL: https://attack.mitre.org/techniques/T1484/
+* Sub-technique:
+** Name: Group Policy Modification
+** ID: T1484.001
+** Reference URL: https://attack.mitre.org/techniques/T1484/001/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Lateral Tool Transfer
+** ID: T1570
+** Reference URL: https://attack.mitre.org/techniques/T1570/
diff --git a/docs/detections/prebuilt-rules/rule-details/scheduled-tasks-at-command-enabled.asciidoc b/docs/detections/prebuilt-rules/rule-details/scheduled-tasks-at-command-enabled.asciidoc
index 65ad3f08dc..7ef463e8a9 100644
--- a/docs/detections/prebuilt-rules/rule-details/scheduled-tasks-at-command-enabled.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/scheduled-tasks-at-command-enabled.asciidoc
@@ -5,69 +5,73 @@ Identifies attempts to enable the Windows scheduled tasks AT command via the reg
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows/win32/cimwin32prov/win32-scheduledjob
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
-
-*Version*: 101 (<<scheduled-tasks-at-command-enabled-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.path : (
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\Configuration\\EnableAt",
-"\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\Configuration\\EnableAt" ) and
-registry.data.strings : ("1", "0x00000001")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and
+  registry.path : (
+    "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Schedule\\Configuration\\EnableAt",
+    "\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Schedule\\Configuration\\EnableAt"
+  ) and registry.data.strings : ("1", "0x00000001")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,49 +83,19 @@ registry.data.strings : ("1", "0x00000001")
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[scheduled-tasks-at-command-enabled-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path : "HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\Configuration\\EnableAt" and
-registry.data.strings : ("1", "0x00000001")
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path : "HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\Configuration\\EnableAt" and
-registry.data.strings : ("1", "0x00000001")
-----------------------------------
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path : "HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Schedule\\Configuration\\EnableAt" and
-registry.data.strings == "1"
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: At
+** ID: T1053.002
+** Reference URL: https://attack.mitre.org/techniques/T1053/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/screenconnect-server-spawning-suspicious-processes.asciidoc b/docs/detections/prebuilt-rules/rule-details/screenconnect-server-spawning-suspicious-processes.asciidoc
new file mode 100644
index 0000000000..87e5293231
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/screenconnect-server-spawning-suspicious-processes.asciidoc
@@ -0,0 +1,87 @@
+[[screenconnect-server-spawning-suspicious-processes]]
+=== ScreenConnect Server Spawning Suspicious Processes
+
+Identifies suspicious processes being spawned by the ScreenConnect server process (ScreenConnect.Service.exe). This activity may indicate exploitation activity or access to an existing web shell backdoor.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* winlogbeat-*
+* logs-windows.sysmon_operational-*
+* logs-system.security*
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blackpointcyber.com/resources/blog/breaking-through-the-screen/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : "ScreenConnect.Service.exe" and
+  (process.name : ("cmd.exe", "powershell.exe", "pwsh.exe", "powershell_ise.exe", "csc.exe") or
+  ?process.pe.original_file_name in ("cmd.exe", "powershell.exe", "pwsh.dll", "powershell_ise.exe"))
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Exploit Public-Facing Application
+** ID: T1190
+** Reference URL: https://attack.mitre.org/techniques/T1190/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/screensaver-plist-file-modified-by-unexpected-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/screensaver-plist-file-modified-by-unexpected-process.asciidoc
index 167bb82f56..8a81ecbd07 100644
--- a/docs/detections/prebuilt-rules/rule-details/screensaver-plist-file-modified-by-unexpected-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/screensaver-plist-file-modified-by-unexpected-process.asciidoc
@@ -5,74 +5,128 @@ Identifies when a screensaver plist file is modified by an unexpected process. A
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://posts.specterops.io/saving-your-access-d562bf5bf90b
 * https://github.com/D00MFist/PersistentJXA
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
-
-*Version*: 100 (<<screensaver-plist-file-modified-by-unexpected-process-history, version history>>)
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+
+*Triage and analysis*
+
 
 - Analyze the plist file modification event to identify whether the change was expected or not
 - Investigate the process that modified the plist file for malicious code or other suspicious behavior
 - Identify if any suspicious or known malicious screensaver (.saver) files were recently written to or modified on the host
-----------------------------------
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.name:
-"com.apple.screensaver.*.plist" and file.path : (
-"/Users/*/Library/Preferences/ByHost/*", "/Library/Managed
-Preferences/*", "/System/Library/Preferences/*" ) and /*
-Filter OS processes modifying screensaver plist files */ not
-process.executable : ( "/usr/sbin/cfprefsd",
-"/usr/libexec/xpcproxy", "/System/Library/CoreServices/ManagedClie
-nt.app/Contents/Resources/MCXCompositor", "/System/Library/CoreSer
-vices/ManagedClient.app/Contents/MacOS/ManagedClient" )
+[source, js]
 ----------------------------------
+file where host.os.type == "macos" and event.type != "deletion" and
+  file.name: "com.apple.screensaver.*.plist" and
+   file.path : (
+      "/Users/*/Library/Preferences/ByHost/*",
+      "/Library/Managed Preferences/*",
+      "/System/Library/Preferences/*"
+      ) and
+  (
+    process.code_signature.trusted == false or
+    process.code_signature.exists == false or
+
+    /* common script interpreters and abused native macOS bins */
+    process.name : (
+      "curl",
+      "mktemp",
+      "tail",
+      "funzip",
+      "python*",
+      "osascript",
+      "perl"
+      )
+   ) and
+
+  /* Filter OS processes modifying screensaver plist files */
+  not process.executable : (
+    "/usr/sbin/cfprefsd",
+    "/usr/libexec/xpcproxy",
+    "/System/Library/CoreServices/ManagedClient.app/Contents/Resources/MCXCompositor",
+    "/System/Library/CoreServices/ManagedClient.app/Contents/MacOS/ManagedClient"
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,16 +138,3 @@ vices/ManagedClient.app/Contents/MacOS/ManagedClient" )
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[screensaver-plist-file-modified-by-unexpected-process-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/searching-for-saved-credentials-via-vaultcmd.asciidoc b/docs/detections/prebuilt-rules/rule-details/searching-for-saved-credentials-via-vaultcmd.asciidoc
index b272cc96f9..ec4e36b1ce 100644
--- a/docs/detections/prebuilt-rules/rule-details/searching-for-saved-credentials-via-vaultcmd.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/searching-for-saved-credentials-via-vaultcmd.asciidoc
@@ -5,68 +5,72 @@ Windows Credential Manager allows you to create, view, or delete saved credentia
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://medium.com/threatpunter/detecting-adversary-tradecraft-with-image-load-event-logging-and-eql-8de93338c16
 * https://web.archive.org/web/20201004080456/https://rastamouse.me/blog/rdp-jump-boxes/
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Elastic Endgame
-
-*Version*: 102 (<<searching-for-saved-credentials-via-vaultcmd-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and
-(process.pe.original_file_name:"vaultcmd.exe" or
-process.name:"vaultcmd.exe") and process.args:"/list*"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (?process.pe.original_file_name:"vaultcmd.exe" or process.name:"vaultcmd.exe") and
+  process.args:"/list*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,32 +82,11 @@ process.name:"vaultcmd.exe") and process.args:"/list*"
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[searching-for-saved-credentials-via-vaultcmd-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.pe.original_file_name:"vaultcmd.exe" or
-process.name:"vaultcmd.exe") and process.args:"/list*"
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Formatting only
-
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Sub-technique:
+** Name: Windows Credential Manager
+** ID: T1555.004
+** Reference URL: https://attack.mitre.org/techniques/T1555/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/security-software-discovery-using-wmic.asciidoc b/docs/detections/prebuilt-rules/rule-details/security-software-discovery-using-wmic.asciidoc
index d3a6cb3e54..6fd341c5a3 100644
--- a/docs/detections/prebuilt-rules/rule-details/security-software-discovery-using-wmic.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/security-software-discovery-using-wmic.asciidoc
@@ -5,101 +5,112 @@ Identifies the use of Windows Management Instrumentation Command (WMIC) to disco
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<security-software-discovery-using-wmic-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Rule Type: BBR
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Security Software Discovery using WMIC
+*Triage and analysis*
+
+
+
+*Investigating Security Software Discovery using WMIC*
+
+
+After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
+
+This rule looks for the execution of the `wmic` utility with arguments compatible to the enumeration of the security software installed on the host. Attackers can use this information to decide whether or not to infect a system, disable protections, use bypasses, etc.
 
-After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps.
-This can happen by running commands to enumerate network resources, users, connections, files, and installed security
-software.
 
-This rule looks for the execution of the `wmic` utility with arguments compatible to the enumeration of the security
-software installed on the host. Attackers can use this information to decide whether or not to infect a system, disable
-protections, use bypasses, etc.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
 
-### False positive analysis
 
-- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify
-suspicious activity related to the user or host, such alerts can be dismissed.
+*False positive analysis*
+
+
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name:"wmic.exe" or
-process.pe.original_file_name:"wmic.exe") and
-process.args:"/namespace:\\\\root\\SecurityCenter2" and
-process.args:"Get"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+(process.name : "wmic.exe" or ?process.pe.original_file_name : "wmic.exe") and
+process.args : "/namespace:\\\\root\\SecurityCenter2" and process.args : "Get"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -111,39 +122,15 @@ process.args:"Get"
 ** Name: Software Discovery
 ** ID: T1518
 ** Reference URL: https://attack.mitre.org/techniques/T1518/
-
-[[security-software-discovery-using-wmic-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name:"wmic.exe" or process.pe.original_file_name:"wmic.exe")
-and process.args:"/namespace:\\\\root\\SecurityCenter2" and
-process.args:"Get"
-----------------------------------
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Security Software Discovery
+** ID: T1518.001
+** Reference URL: https://attack.mitre.org/techniques/T1518/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Windows Management Instrumentation
+** ID: T1047
+** Reference URL: https://attack.mitre.org/techniques/T1047/
diff --git a/docs/detections/prebuilt-rules/rule-details/security-software-discovery-via-grep.asciidoc b/docs/detections/prebuilt-rules/rule-details/security-software-discovery-via-grep.asciidoc
index 582f1cc034..3775ae0bff 100644
--- a/docs/detections/prebuilt-rules/rule-details/security-software-discovery-via-grep.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/security-software-discovery-via-grep.asciidoc
@@ -5,7 +5,7 @@ Identifies the use of the grep command to discover known third-party macOS and L
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
 * auditbeat-*
@@ -14,108 +14,147 @@ Identifies the use of the grep command to discover known third-party macOS and L
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* macOS
-* Linux
-* Threat Detection
-* Discovery
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<security-software-discovery-via-grep-history, version history>>)
+* Domain: Endpoint
+* OS: macOS
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Endpoint Security installers, updaters and post installation verification scripts.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Security Software Discovery via Grep
+*Triage and analysis*
+
+
+
+*Investigating Security Software Discovery via Grep*
+
+
+After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
 
-After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps.
-This can happen by running commands to enumerate network resources, users, connections, files, and installed security
-software.
+This rule looks for the execution of the `grep` utility with arguments compatible to the enumeration of the security software installed on the host. Attackers can use this information to decide whether or not to infect a system, disable protections, use bypasses, etc.
 
-This rule looks for the execution of the `grep` utility with arguments compatible to the enumeration of the security
-software installed on the host. Attackers can use this information to decide whether or not to infect a system, disable
-protections, use bypasses, etc.
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence and whether they are located in expected locations.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
-- Investigate any abnormal behavior by the subject process such as network connections, file modifications, and any
-spawned child processes.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+- Investigate any abnormal behavior by the subject process such as network connections, file modifications, and any spawned child processes.
 - Inspect the host for suspicious or abnormal behavior in the alert timeframe.
-- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate
-software installations.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+
+
+*False positive analysis*
+
+
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
 
-### False positive analysis
 
-- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify
-suspicious activity related to the user or host, such alerts can be dismissed.
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "grep" and
-user.id != "0" and not process.parent.executable :
-"/Library/Application Support/*" and process.args :
-("Little Snitch*", "Avast*", "Avira*",
-"ESET*", "BlockBlock*", "360Sec*",
-"LuLu*", "KnockKnock*", "kav", "KIS",
-"RTProtectionDaemon*", "Malware*",
-"VShieldScanner*", "WebProtection*",
-"webinspectord*", "McAfee*", "isecespd*",
-"macmnsvc*", "masvc*", "kesl*",
-"avscan*", "guard*", "rtvscand*",
-"symcfgd*", "scmdaemon*", "symantec*",
-"sophos*", "osquery*", "elastic-endpoint*"
-) and not (process.args : "Avast" and process.args : "Passwords")
+[source, js]
 ----------------------------------
+process where event.type == "start" and
+process.name : "grep" and user.id != "0" and
+ not process.parent.executable : ("/Library/Application Support/*", "/opt/McAfee/agent/scripts/ma") and
+   process.args :
+         ("Little Snitch*",
+          "Avast*",
+          "Avira*",
+          "ESET*",
+          "BlockBlock*",
+          "360Sec*",
+          "LuLu*",
+          "KnockKnock*",
+          "kav",
+          "KIS",
+          "RTProtectionDaemon*",
+          "Malware*",
+          "VShieldScanner*",
+          "WebProtection*",
+          "webinspectord*",
+          "McAfee*",
+          "isecespd*",
+          "macmnsvc*",
+          "masvc*",
+          "kesl*",
+          "avscan*",
+          "guard*",
+          "rtvscand*",
+          "symcfgd*",
+          "scmdaemon*",
+          "symantec*",
+          "sophos*",
+          "osquery*",
+          "elastic-endpoint*"
+          ) and
+   not (
+     (process.args : "Avast" and process.args : "Passwords") or
+     (process.parent.args : "/opt/McAfee/agent/scripts/ma" and process.parent.args : "checkhealth") or
+     (process.command_line : (
+       "grep ESET Command-line scanner, version %s -A2",
+       "grep -i McAfee Web Gateway Core version:",
+       "grep --color=auto ESET Command-line scanner, version %s -A2"
+       )
+     ) or
+     (process.parent.command_line : (
+       """sh -c printf "command_start_%s"*; perl -pe 's/[^ -~]/\n/g' < /opt/eset/esets/sbin/esets_scan | grep 'ESET Command-line scanner, version %s' -A2 | tail -1; printf "command_done_%s*""",
+       """bash -c perl -pe 's/[^ -~]/\n/g' < /opt/eset/esets/sbin/esets_scan | grep 'ESET Command-line scanner, version %s' -A2 | tail -1"""
+       )
+     )
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -127,33 +166,7 @@ user.id != "0" and not process.parent.executable :
 ** Name: Software Discovery
 ** ID: T1518
 ** Reference URL: https://attack.mitre.org/techniques/T1518/
-
-[[security-software-discovery-via-grep-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category : process and event.type : (start or process_started)
-and process.name : grep and process.args : ("Little Snitch" or Avast*
-or Avira* or ESET* or esets_* or BlockBlock or 360* or LuLu or
-KnockKnock* or kav or KIS or RTProtectionDaemon or Malware* or
-VShieldScanner or WebProtection or webinspectord or McAfee* or
-isecespd* or macmnsvc* or masvc or kesl or avscan or guard or rtvscand
-or symcfgd or scmdaemon or symantec or elastic-endpoint )
-----------------------------------
-
+* Sub-technique:
+** Name: Security Software Discovery
+** ID: T1518.001
+** Reference URL: https://attack.mitre.org/techniques/T1518/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/sedebugprivilege-enabled-by-a-suspicious-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/sedebugprivilege-enabled-by-a-suspicious-process.asciidoc
index 8a81211d0f..fcd22c5292 100644
--- a/docs/detections/prebuilt-rules/rule-details/sedebugprivilege-enabled-by-a-suspicious-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/sedebugprivilege-enabled-by-a-suspicious-process.asciidoc
@@ -5,78 +5,96 @@ Identifies the creation of a process running as SYSTEM and impersonating a Windo
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-windows.*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4703
 * https://blog.palantir.com/windows-privilege-abuse-auditing-detection-and-defense-3078a403d74e
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
 
-*Version*: 1
+*Version*: 7
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+Windows Event 4703 logs Token Privileges changes and need to be configured (Enable).
+
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+Detailed Tracking >
+Token Right Adjusted Events (Success)
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-any where event.provider: "Microsoft-Windows-Security-Auditing" and
-event.action : "Token Right Adjusted Events" and
-winlog.event_data.EnabledPrivilegeList : "SeDebugPrivilege" and /*
-exclude processes with System Integrity */ not
-winlog.event_data.SubjectUserSid : ("S-1-5-18", "S-1-5-19",
-"S-1-5-20") and not winlog.event_data.ProcessName :
-("?:\\Windows\\System32\\msiexec.exe",
-"?:\\Windows\\SysWOW64\\msiexec.exe",
-"?:\\Windows\\System32\\lsass.exe",
-"?:\\Windows\\WinSxS\\*", "?:\\Program Files\\*",
-"?:\\Program Files (x86)\\*",
-"?:\\Windows\\System32\\MRT.exe",
-"?:\\Windows\\System32\\cleanmgr.exe",
-"?:\\Windows\\System32\\taskhostw.exe",
-"?:\\Windows\\System32\\mmc.exe",
-"?:\\Users\\*\\AppData\\Local\\Temp\\*-*\\DismHost.exe",
-"?:\\Windows\\System32\\auditpol.exe",
-"?:\\Windows\\System32\\wbem\\WmiPrvSe.exe",
-"?:\\Windows\\SysWOW64\\wbem\\WmiPrvSe.exe")
+[source, js]
 ----------------------------------
+any where host.os.type == "windows" and event.provider: "Microsoft-Windows-Security-Auditing" and
+ event.action : "Token Right Adjusted Events" and
+
+ winlog.event_data.EnabledPrivilegeList : "SeDebugPrivilege" and
+
+ /* exclude processes with System Integrity  */
+ not winlog.event_data.SubjectUserSid : ("S-1-5-18", "S-1-5-19", "S-1-5-20") and
+
+ not winlog.event_data.ProcessName :
+         ("?:\\Windows\\System32\\msiexec.exe",
+          "?:\\Windows\\SysWOW64\\msiexec.exe",
+          "?:\\Windows\\System32\\lsass.exe",
+          "?:\\Windows\\WinSxS\\*",
+          "?:\\Program Files\\*",
+          "?:\\Program Files (x86)\\*",
+          "?:\\Windows\\System32\\MRT.exe",
+          "?:\\Windows\\System32\\cleanmgr.exe",
+          "?:\\Windows\\System32\\taskhostw.exe",
+          "?:\\Windows\\System32\\mmc.exe",
+          "?:\\Users\\*\\AppData\\Local\\Temp\\*-*\\DismHost.exe",
+          "?:\\Windows\\System32\\auditpol.exe",
+          "?:\\Windows\\System32\\wbem\\WmiPrvSe.exe",
+          "?:\\Windows\\SysWOW64\\wbem\\WmiPrvSe.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
diff --git a/docs/detections/prebuilt-rules/rule-details/segfault-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/segfault-detected.asciidoc
new file mode 100644
index 0000000000..a26b42c116
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/segfault-detected.asciidoc
@@ -0,0 +1,91 @@
+[[segfault-detected]]
+=== Segfault Detected
+
+Monitors kernel logs for segfault messages. A segfault, or segmentation fault, is an error that occurs when a program tries to access a memory location that it's not allowed to access, typically leading to program termination. A segfault can be an indication of malicious behavior if it results from attempts to exploit buffer overflows or other vulnerabilities in software to execute arbitrary code or disrupt its normal operation.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-system.syslog-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Rule Type: BBR
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Filebeat
+
+
+*Filebeat Setup*
+
+
+Filebeat is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to Elasticsearch or Logstash for indexing.
+
+
+*The following steps should be executed in order to add the Filebeat for the Linux System:*
+
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html[helper guide].
+- To run Filebeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-docker.html[helper guide].
+- To run Filebeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html[helper guide].
+- For quick start information for Filebeat refer to the https://www.elastic.co/guide/en/beats/filebeat/8.11/filebeat-installation-configuration.html[helper guide].
+- For complete Setup and Run Filebeat information refer to the https://www.elastic.co/guide/en/beats/filebeat/current/setting-up-and-running.html[helper guide].
+
+
+*Rule Specific Setup Note*
+
+
+- This rule requires the Filebeat System Module to be enabled.
+- The system module collects and parses logs created by the system logging service of common Unix/Linux based distributions.
+- To run the system module of Filebeat on Linux follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-system.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.dataset:"system.syslog" and process.name:kernel and message:segfault
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
diff --git a/docs/detections/prebuilt-rules/rule-details/sensitive-files-compression-inside-a-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/sensitive-files-compression-inside-a-container.asciidoc
new file mode 100644
index 0000000000..ede4904852
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/sensitive-files-compression-inside-a-container.asciidoc
@@ -0,0 +1,107 @@
+[[sensitive-files-compression-inside-a-container]]
+=== Sensitive Files Compression Inside A Container
+
+Identifies the use of a compression utility to collect known files containing sensitive information, such as credentials and system configurations inside a container.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Collection
+* Tactic: Credential Access
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where container.id: "*" and event.type== "start" and 
+
+/*account for tools that execute utilities as a subprocess, in this case the target utility name will appear as a process arg*/  
+(process.name: ("zip", "tar", "gzip", "hdiutil", "7z") or process.args: ("zip", "tar", "gzip", "hdiutil", "7z"))
+and process.args: ( 
+"/root/.ssh/id_rsa", 
+"/root/.ssh/id_rsa.pub", 
+"/root/.ssh/id_ed25519", 
+"/root/.ssh/id_ed25519.pub", 
+"/root/.ssh/authorized_keys", 
+"/root/.ssh/authorized_keys2", 
+"/root/.ssh/known_hosts", 
+"/root/.bash_history", 
+"/etc/hosts", 
+"/home/*/.ssh/id_rsa", 
+"/home/*/.ssh/id_rsa.pub", 
+"/home/*/.ssh/id_ed25519",
+"/home/*/.ssh/id_ed25519.pub",
+"/home/*/.ssh/authorized_keys",
+"/home/*/.ssh/authorized_keys2",
+"/home/*/.ssh/known_hosts",
+"/home/*/.bash_history",
+"/root/.aws/credentials",
+"/root/.aws/config",
+"/home/*/.aws/credentials",
+"/home/*/.aws/config",
+"/root/.docker/config.json",
+"/home/*/.docker/config.json",
+"/etc/group",
+"/etc/passwd",
+"/etc/shadow",
+"/etc/gshadow")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Unsecured Credentials
+** ID: T1552
+** Reference URL: https://attack.mitre.org/techniques/T1552/
+* Sub-technique:
+** Name: Credentials In Files
+** ID: T1552.001
+** Reference URL: https://attack.mitre.org/techniques/T1552/001/
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Archive Collected Data
+** ID: T1560
+** Reference URL: https://attack.mitre.org/techniques/T1560/
+* Sub-technique:
+** Name: Archive via Utility
+** ID: T1560.001
+** Reference URL: https://attack.mitre.org/techniques/T1560/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/sensitive-files-compression.asciidoc b/docs/detections/prebuilt-rules/rule-details/sensitive-files-compression.asciidoc
index 554f763b0d..6f381f480b 100644
--- a/docs/detections/prebuilt-rules/rule-details/sensitive-files-compression.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/sensitive-files-compression.asciidoc
@@ -3,69 +3,141 @@
 
 Identifies the use of a compression utility to collect known files containing sensitive information, such as credentials and system configurations.
 
-*Rule type*: query
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.trendmicro.com/en_ca/research/20/l/teamtnt-now-deploying-ddos-capable-irc-bot-tntbotinger.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Collection
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 208
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Collection
-* Credential Access
 
-*Version*: 100 (<<sensitive-files-compression-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:start and process.name:(zip or
-tar or gzip or hdiutil or 7z) and process.args: (
-/root/.ssh/id_rsa or /root/.ssh/id_rsa.pub or
-/root/.ssh/id_ed25519 or /root/.ssh/id_ed25519.pub or
-/root/.ssh/authorized_keys or /root/.ssh/authorized_keys2 or
-/root/.ssh/known_hosts or /root/.bash_history or
-/etc/hosts or /home/*/.ssh/id_rsa or
-/home/*/.ssh/id_rsa.pub or /home/*/.ssh/id_ed25519 or
-/home/*/.ssh/id_ed25519.pub or /home/*/.ssh/authorized_keys or
-/home/*/.ssh/authorized_keys2 or /home/*/.ssh/known_hosts or
-/home/*/.bash_history or /root/.aws/credentials or
-/root/.aws/config or /home/*/.aws/credentials or
-/home/*/.aws/config or /root/.docker/config.json or
-/home/*/.docker/config.json or /etc/group or /etc/passwd
-or /etc/shadow or /etc/gshadow )
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:linux and event.type:start and
+  process.name:(zip or tar or gzip or hdiutil or 7z) and
+  process.args:
+    (
+      /root/.ssh/id_rsa or
+      /root/.ssh/id_rsa.pub or
+      /root/.ssh/id_ed25519 or
+      /root/.ssh/id_ed25519.pub or
+      /root/.ssh/authorized_keys or
+      /root/.ssh/authorized_keys2 or
+      /root/.ssh/known_hosts or
+      /root/.bash_history or
+      /etc/hosts or
+      /home/*/.ssh/id_rsa or
+      /home/*/.ssh/id_rsa.pub or
+      /home/*/.ssh/id_ed25519 or
+      /home/*/.ssh/id_ed25519.pub or
+      /home/*/.ssh/authorized_keys or
+      /home/*/.ssh/authorized_keys2 or
+      /home/*/.ssh/known_hosts or
+      /home/*/.bash_history or
+      /root/.aws/credentials or
+      /root/.aws/config or
+      /home/*/.aws/credentials or
+      /home/*/.aws/config or
+      /root/.docker/config.json or
+      /home/*/.docker/config.json or
+      /etc/group or
+      /etc/passwd or
+      /etc/shadow or
+      /etc/gshadow
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,8 +149,10 @@ or /etc/shadow or /etc/gshadow )
 ** Name: Unsecured Credentials
 ** ID: T1552
 ** Reference URL: https://attack.mitre.org/techniques/T1552/
-
-
+* Sub-technique:
+** Name: Credentials In Files
+** ID: T1552.001
+** Reference URL: https://attack.mitre.org/techniques/T1552/001/
 * Tactic:
 ** Name: Collection
 ** ID: TA0009
@@ -87,13 +161,7 @@ or /etc/shadow or /etc/gshadow )
 ** Name: Archive Collected Data
 ** ID: T1560
 ** Reference URL: https://attack.mitre.org/techniques/T1560/
-
-[[sensitive-files-compression-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Archive via Utility
+** ID: T1560.001
+** Reference URL: https://attack.mitre.org/techniques/T1560/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/sensitive-keys-or-passwords-searched-for-inside-a-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/sensitive-keys-or-passwords-searched-for-inside-a-container.asciidoc
new file mode 100644
index 0000000000..e53f511568
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/sensitive-keys-or-passwords-searched-for-inside-a-container.asciidoc
@@ -0,0 +1,77 @@
+[[sensitive-keys-or-passwords-searched-for-inside-a-container]]
+=== Sensitive Keys Or Passwords Searched For Inside A Container
+
+This rule detects the use of system search utilities like grep and find to search for private SSH keys or passwords inside a container. Unauthorized access to these sensitive files could lead to further compromise of the container environment or facilitate a container breakout to the underlying host machine.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://sysdig.com/blog/cve-2021-25741-kubelet-falco/
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Credential Access
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where container.id: "*" and event.type== "start" and
+((
+/*account for tools that execute utilities as a subprocess, in this case the target utility name will appear as a process arg*/  
+  (process.name in ("grep", "egrep", "fgrep") or process.args in ("grep", "egrep", "fgrep")) 
+    and process.args : ("*BEGIN PRIVATE*", "*BEGIN OPENSSH PRIVATE*", "*BEGIN RSA PRIVATE*", 
+"*BEGIN DSA PRIVATE*", "*BEGIN EC PRIVATE*", "*pass*", "*ssh*", "*user*")
+) 
+or 
+(
+/*account for tools that execute utilities as a subprocess, in this case the target utility name will appear as a process arg*/
+  (process.name in ("find", "locate", "mlocate") or process.args in ("find", "locate", "mlocate")) 
+    and process.args : ("*id_rsa*", "*id_dsa*")
+))
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Unsecured Credentials
+** ID: T1552
+** Reference URL: https://attack.mitre.org/techniques/T1552/
+* Sub-technique:
+** Name: Credentials In Files
+** ID: T1552.001
+** Reference URL: https://attack.mitre.org/techniques/T1552/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/sensitive-privilege-seenabledelegationprivilege-assigned-to-a-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/sensitive-privilege-seenabledelegationprivilege-assigned-to-a-user.asciidoc
index da238e8261..3fe5eb09c2 100644
--- a/docs/detections/prebuilt-rules/rule-details/sensitive-privilege-seenabledelegationprivilege-assigned-to-a-user.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/sensitive-privilege-seenabledelegationprivilege-assigned-to-a-user.asciidoc
@@ -5,22 +5,23 @@ Identifies the assignment of the SeEnableDelegationPrivilege sensitive "user rig
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.harmj0y.net/activedirectory/the-most-dangerous-user-right-you-probably-have-never-heard-of/
 * https://github.com/SigmaHQ/sigma/blob/master/rules/windows/builtin/security/win_alert_active_directory_user_control.yml
@@ -28,91 +29,106 @@ Identifies the assignment of the SeEnableDelegationPrivilege sensitive "user rig
 * https://www.thehacker.recipes/ad/movement/kerberos/delegations
 * https://github.com/atc-project/atomic-threat-coverage/blob/master/Atomic_Threat_Coverage/Logging_Policies/LP_0105_windows_audit_authorization_policy_change.md
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Active Directory
-* Investigation Guide
-
-*Version*: 102 (<<sensitive-privilege-seenabledelegationprivilege-assigned-to-a-user-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Persistence
+* Data Source: Active Directory
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Sensitive Privilege SeEnableDelegationPrivilege assigned to a User
+*Triage and analysis*
+
+
+
+*Investigating Sensitive Privilege SeEnableDelegationPrivilege assigned to a User*
+
+
+Kerberos delegation is an Active Directory feature that allows user and computer accounts to impersonate other accounts, act on their behalf, and use their privileges. Delegation (constrained and unconstrained) can be configured for user and computer objects.
 
-Kerberos delegation is an Active Directory feature that allows user and computer accounts to impersonate other accounts,
-act on their behalf, and use their privileges. Delegation (constrained and unconstrained) can be configured
-for user and computer objects.
+Enabling unconstrained delegation for a computer causes the computer to store the ticket-granting ticket (TGT) in memory at any time an account connects to the computer, so it can be used by the computer for impersonation when needed. Risk is heightened if an attacker compromises computers with unconstrained delegation enabled, as they could extract TGTs from memory and then replay them to move laterally on the domain. If the attacker coerces a privileged user to connect to the server, or if the user does so routinely, the account will be compromised and the attacker will be able to pass-the-ticket to privileged assets.
 
-Enabling unconstrained delegation for a computer causes the computer to store the ticket-granting ticket
-(TGT) in memory at any time an account connects to the computer, so it can be used by the computer for impersonation
-when needed. Risk is heightened if an attacker compromises computers with unconstrained delegation enabled, as they
-could extract TGTs from memory and then replay them to move laterally on the domain. If the attacker coerces a privileged
-user to connect to the server, or if the user does so routinely, the account will be compromised and the attacker will
-be able to pass-the-ticket to privileged assets.
+SeEnableDelegationPrivilege is a user right that is controlled within the Local Security Policy of a domain controller and is managed through Group Policy. This setting is named **Enable computer and user accounts to be trusted for delegation**.
 
-SeEnableDelegationPrivilege is a user right that is controlled within the Local Security Policy of a domain controller
-and is managed through Group Policy. This setting is named **Enable computer and user accounts to be trusted for
-delegation**.
+It is critical to control the assignment of this privilege. A user with this privilege and write access to a computer can control delegation settings, perform the attacks described above, and harvest TGTs from any user that connects to the system.
 
-It is critical to control the assignment of this privilege. A user with this privilege and write access to a computer
-can control delegation settings, perform the attacks described above, and harvest TGTs from any user that connects to
-the system.
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - Investigate how the privilege was assigned to the user and who assigned it.
-- Investigate other potentially malicious activity that was performed by the user that assigned the privileges using the
-`user.id` and `winlog.activity_id` fields as a filter during the past 48 hours.
+- Investigate other potentially malicious activity that was performed by the user that assigned the privileges using the `user.id` and `winlog.activity_id` fields as a filter during the past 48 hours.
 - Investigate other alerts associated with the users/host during the past 48 hours.
 
-### False positive analysis
 
-- The SeEnableDelegationPrivilege privilege should not be assigned to users. If this rule is triggered in your
-environment legitimately, the security team should notify the administrators about the risks of using it.
+*False positive analysis*
+
+
+- The SeEnableDelegationPrivilege privilege should not be assigned to users. If this rule is triggered in your environment legitimately, the security team should notify the administrators about the risks of using it.
+
+
+*Related rules*
 
-### Related rules
 
 - KRBTGT Delegation Backdoor - e052c845-48d0-4f46-8a13-7d0aba05df82
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Remove the privilege from the account.
 - Review the privileges of the administrator account that performed the action.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Authorization Policy Change' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Windows Settings >
+Security Settings >
+Advanced Audit Policy Configuration >
+Audit Policies >
+Policy Change >
+Audit Authorization Policy Change (Success,Failure)
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.action: "Authorization Policy Change" and event.code:4704 and
-winlog.event_data.PrivilegeList:"SeEnableDelegationPrivilege"
+[source, js]
 ----------------------------------
+event.action:"Authorization Policy Change" and event.code:4704 and
+  winlog.event_data.PrivilegeList:"SeEnableDelegationPrivilege"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -120,28 +136,15 @@ winlog.event_data.PrivilegeList:"SeEnableDelegationPrivilege"
 ** Name: Credential Access
 ** ID: TA0006
 ** Reference URL: https://attack.mitre.org/tactics/TA0006/
-
-
+* Technique:
+** Name: Steal or Forge Kerberos Tickets
+** ID: T1558
+** Reference URL: https://attack.mitre.org/techniques/T1558/
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-[[sensitive-privilege-seenabledelegationprivilege-assigned-to-a-user-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Technique:
+** Name: Account Manipulation
+** ID: T1098
+** Reference URL: https://attack.mitre.org/techniques/T1098/
diff --git a/docs/detections/prebuilt-rules/rule-details/service-command-lateral-movement.asciidoc b/docs/detections/prebuilt-rules/rule-details/service-command-lateral-movement.asciidoc
index 625324b44e..6536f95aaf 100644
--- a/docs/detections/prebuilt-rules/rule-details/service-command-lateral-movement.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/service-command-lateral-movement.asciidoc
@@ -5,54 +5,56 @@ Identifies use of sc.exe to create, modify, or start services on remote hosts. T
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
+*Tags*: 
 
-*Version*: 101 (<<service-command-lateral-movement-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id with maxspan = 1m [process where
-event.type == "start" and (process.name : "sc.exe" or
-process.pe.original_file_name : "sc.exe") and process.args :
-"\\\\*" and process.args : ("binPath=*", "binpath=*") and
-process.args : ("create", "config", "failure", "start")] [network
-where process.name : "sc.exe" and destination.ip != "127.0.0.1"]
+[source, js]
 ----------------------------------
+sequence by process.entity_id with maxspan = 1m
+  [process where host.os.type == "windows" and event.type == "start" and
+     (process.name : "sc.exe" or process.pe.original_file_name : "sc.exe") and
+      process.args : "\\\\*" and process.args : ("binPath=*", "binpath=*") and
+      process.args : ("create", "config", "failure", "start")]
+  [network where host.os.type == "windows" and process.name : "sc.exe" and destination.ip != "127.0.0.1"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,8 +66,6 @@ where process.name : "sc.exe" and destination.ip != "127.0.0.1"]
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -74,8 +74,10 @@ where process.name : "sc.exe" and destination.ip != "127.0.0.1"]
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -84,43 +86,7 @@ where process.name : "sc.exe" and destination.ip != "127.0.0.1"]
 ** Name: System Services
 ** ID: T1569
 ** Reference URL: https://attack.mitre.org/techniques/T1569/
-
-[[service-command-lateral-movement-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan = 1m [process where
-event.type in ("start", "process_started") and (process.name :
-"sc.exe" or process.pe.original_file_name : "sc.exe") and
-process.args : "\\\\*" and process.args : ("binPath=*", "binpath=*")
-and process.args : ("create", "config", "failure", "start")]
-[network where process.name : "sc.exe" and destination.ip !=
-"127.0.0.1"]
-----------------------------------
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan=1m [process where
-event.type in ("start", "process_started") and
-/* uncomment once in winlogbeat */ (process.name == "sc.exe" /*
-or process.pe.original_file_name == "sc.exe" */ ) and
-/* case insensitive */ wildcard(process.args, "\\\\*") and
-wildcard(process.args, "binPath=*", "binpath=*") and
-(process.args : "create" or process.args : "config" or
-process.args : "failure" or process.args : "start")] [network
-where process.name : "sc.exe" and destination.ip != "127.0.0.1"]
-----------------------------------
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Service Execution
+** ID: T1569.002
+** Reference URL: https://attack.mitre.org/techniques/T1569/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/service-control-spawned-via-script-interpreter.asciidoc b/docs/detections/prebuilt-rules/rule-details/service-control-spawned-via-script-interpreter.asciidoc
index 0539b16b97..03d1e25e2c 100644
--- a/docs/detections/prebuilt-rules/rule-details/service-control-spawned-via-script-interpreter.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/service-control-spawned-via-script-interpreter.asciidoc
@@ -1,151 +1,172 @@
 [[service-control-spawned-via-script-interpreter]]
 === Service Control Spawned via Script Interpreter
 
-Identifies Service Control (sc.exe) spawning from script interpreter processes to create, modify, or start services. This could be indicative of adversary lateral movement but will be noisy if commonly done by admins.
+Identifies Service Control (sc.exe) spawning from script interpreter processes to create, modify, or start services. This can potentially indicate an attempt to elevate privileges or maintain persistence.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-system.*
 * winlogbeat-*
+* logs-windows.*
+* endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
+*Tags*: 
 
-*Version*: 100 (<<service-control-spawned-via-script-interpreter-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Service Control Spawned via Script Interpreter*
 
-[source,js]
-----------------------------------
-/* This rule is not compatible with Sysmon due to user.id issues */
-process where event.type == "start" and (process.name : "sc.exe" or
-process.pe.original_file_name == "sc.exe") and process.parent.name :
-("cmd.exe", "wscript.exe", "rundll32.exe", "regsvr32.exe",
-"wmic.exe", "mshta.exe","powershell.exe", "pwsh.exe") and
-process.args:("config", "create", "start", "delete", "stop", "pause")
-and /* exclude SYSTEM SID - look for service creations by non-SYSTEM
-user */ not user.id : "S-1-5-18"
-----------------------------------
 
-==== Threat mapping
+Windows services are background processes that run with SYSTEM privileges and provide specific functionality or support to other applications and system components.
 
-*Framework*: MITRE ATT&CK^TM^
+The `sc.exe` command line utility is used to manage and control Windows services on a local or remote computer. Attackers may use `sc.exe` to create, modify, and start services to elevate their privileges from administrator to SYSTEM.
 
-* Tactic:
-** Name: Lateral Movement
-** ID: TA0008
-** Reference URL: https://attack.mitre.org/tactics/TA0008/
-* Technique:
-** Name: Remote Services
-** ID: T1021
-** Reference URL: https://attack.mitre.org/techniques/T1021/
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-[[service-control-spawned-via-script-interpreter-history]]
-==== Rule version history
 
-Version 100 (8.5.0 release)::
-* Formatting only
+*Possible investigation steps*
 
-Version 13 (8.4.0 release)::
-* Formatting only
 
-Version 11 (8.2.0 release)::
-* Formatting only
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine the command line, registry changes events, and Windows events related to service activities (for example, 4697 and/or 7045) for suspicious characteristics.
+  - Examine the created and existent services, the executables or drivers referenced, and command line arguments for suspicious entries.
+    - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+    - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+    - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the referenced files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
 
-Version 10 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and (process.name : "sc.exe" or
-process.pe.original_file_name == "sc.exe") and process.parent.name :
-("cmd.exe", "wscript.exe", "rundll32.exe", "regsvr32.exe",
-"wmic.exe", "mshta.exe","powershell.exe", "pwsh.exe") and
-process.args:("config", "create", "start", "delete", "stop", "pause")
-and /* exclude SYSTEM SID - look for service creations by non-SYSTEM
-user */ not user.id : "S-1-5-18"
-----------------------------------
 
-Version 9 (7.13.0 release)::
-* Rule name changed from: Local Service Commands
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:sc.exe and process.args:(config or create or failure or
-start)
-----------------------------------
+*False positive analysis*
 
-Version 8 (7.12.0 release)::
-* Formatting only
 
-Version 7 (7.11.2 release)::
-* Formatting only
+- This activity is not inherently malicious if it occurs in isolation. As long as the analyst did not identify suspicious activity related to the user, host, and service, such alerts can be dismissed.
 
-Version 6 (7.11.0 release)::
-* Formatting only
 
-Version 5 (7.10.0 release)::
-* Formatting only
+*Response and remediation*
 
-Version 4 (7.9.1 release)::
-* Formatting only
 
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:sc.exe and process.args:(config or create or failure or
-start)
-----------------------------------
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Delete the service or restore it to the original configuration.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
 
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:sc.exe and process.args:("create" or "config" or
-"failure" or "start")
+/* This rule is not compatible with Sysmon due to user.id issues */
+
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "sc.exe" or process.pe.original_file_name == "sc.exe") and
+  process.parent.name : ("cmd.exe", "wscript.exe", "rundll32.exe", "regsvr32.exe",
+                         "wmic.exe", "mshta.exe","powershell.exe", "pwsh.exe") and
+  process.args:("config", "create", "start", "delete", "stop", "pause") and
+  /* exclude SYSTEM SID - look for service creations by non-SYSTEM user */
+  not user.id : "S-1-5-18"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
+* Sub-technique:
+** Name: Visual Basic
+** ID: T1059.005
+** Reference URL: https://attack.mitre.org/techniques/T1059/005/
+* Technique:
+** Name: Windows Management Instrumentation
+** ID: T1047
+** Reference URL: https://attack.mitre.org/techniques/T1047/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: Regsvr32
+** ID: T1218.010
+** Reference URL: https://attack.mitre.org/techniques/T1218/010/
+* Sub-technique:
+** Name: Rundll32
+** ID: T1218.011
+** Reference URL: https://attack.mitre.org/techniques/T1218/011/
diff --git a/docs/detections/prebuilt-rules/rule-details/service-creation-via-local-kerberos-authentication.asciidoc b/docs/detections/prebuilt-rules/rule-details/service-creation-via-local-kerberos-authentication.asciidoc
index 176929fcbd..2fb132c537 100644
--- a/docs/detections/prebuilt-rules/rule-details/service-creation-via-local-kerberos-authentication.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/service-creation-via-local-kerberos-authentication.asciidoc
@@ -5,65 +5,68 @@ Identifies a suspicious local successful logon event where the Logon Package is
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/Dec0ne/KrbRelayUp
 * https://googleprojectzero.blogspot.com/2021/10/using-kerberos-for-authentication-relay.html
 * https://github.com/cube0x0/KrbRelay
 * https://gist.github.com/tyranid/c24cfd1bd141d14d4925043ee7e03c82
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Credential Access
-
-*Version*: 100 (<<service-creation-via-local-kerberos-authentication-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Credential Access
+* Use Case: Active Directory Monitoring
+* Data Source: Active Directory
 
-*Added ({stack} release)*: 8.3.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=5m [authentication where /* event
-4624 need to be logged */ event.action == "logged-in" and
-event.outcome == "success" and /* authenticate locally using
-relayed kerberos Ticket */
-winlog.event_data.AuthenticationPackageName :"Kerberos" and
-winlog.logon.type == "Network" and cidrmatch(source.ip,
-"127.0.0.0/8", "::1") and source.port > 0] by
-winlog.event_data.TargetLogonId [any where /* event 4697 need to
-be logged */ event.action : "service-installed"] by
-winlog.event_data.SubjectLogonId
+[source, js]
 ----------------------------------
+sequence by winlog.computer_name with maxspan=5m
+ [authentication where
+
+  /* event 4624 need to be logged */
+  event.action == "logged-in" and event.outcome == "success" and
 
-==== Threat mapping
+  /* authenticate locally using relayed kerberos Ticket */
+  winlog.event_data.AuthenticationPackageName :"Kerberos" and winlog.logon.type == "Network" and
+  cidrmatch(source.ip, "127.0.0.0/8", "::1") and source.port > 0] by winlog.event_data.TargetLogonId
+
+  [any where
+   /* event 4697 need to be logged */
+   event.action : "service-installed"] by winlog.event_data.SubjectLogonId
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,8 +78,10 @@ winlog.event_data.SubjectLogonId
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
 * Tactic:
 ** Name: Credential Access
 ** ID: TA0006
@@ -85,13 +90,3 @@ winlog.event_data.SubjectLogonId
 ** Name: Steal or Forge Kerberos Tickets
 ** ID: T1558
 ** Reference URL: https://attack.mitre.org/techniques/T1558/
-
-[[service-creation-via-local-kerberos-authentication-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/service-disabled-via-registry-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/service-disabled-via-registry-modification.asciidoc
new file mode 100644
index 0000000000..39026a0c17
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/service-disabled-via-registry-modification.asciidoc
@@ -0,0 +1,79 @@
+[[service-disabled-via-registry-modification]]
+=== Service Disabled via Registry Modification
+
+Identifies attempts to modify services start settings using processes other than services.exe. Attackers may attempt to modify security and monitoring services to avoid detection or delay response.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.registry-*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+registry where host.os.type == "windows" and event.type == "change" and
+  registry.path : (
+    "HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\Start",
+    "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\*\\Start"
+  ) and registry.data.strings : ("3", "4") and
+  not 
+    (
+      process.name : "services.exe" and user.id : "S-1-5-18"
+    )
+  and not registry.path : "HKLM\\SYSTEM\\ControlSet001\\Services\\MrxSmb10\\Start"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Service Stop
+** ID: T1489
+** Reference URL: https://attack.mitre.org/techniques/T1489/
diff --git a/docs/detections/prebuilt-rules/rule-details/service-path-modification-via-sc-exe.asciidoc b/docs/detections/prebuilt-rules/rule-details/service-path-modification-via-sc-exe.asciidoc
new file mode 100644
index 0000000000..87945fd1fc
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/service-path-modification-via-sc-exe.asciidoc
@@ -0,0 +1,87 @@
+[[service-path-modification-via-sc-exe]]
+=== Service Path Modification via sc.exe
+
+Identifies attempts to modify a service path setting using sc.exe. Attackers may attempt to modify existing services for persistence or privilege escalation.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and process.name : "sc.exe" and
+  process.args : "*config*" and process.args : "*binPath*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/service-path-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/service-path-modification.asciidoc
new file mode 100644
index 0000000000..cccc6885ce
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/service-path-modification.asciidoc
@@ -0,0 +1,97 @@
+[[service-path-modification]]
+=== Service Path Modification
+
+Identifies attempts to modify a service path by an unusual process. Attackers may attempt to modify existing services for persistence or privilege escalation.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.registry-*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+registry where host.os.type == "windows" and event.type == "change" and
+  registry.path : (
+    "HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\ImagePath",
+    "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\*\\ImagePath"
+  ) and not (
+    process.executable : (
+      "?:\\Program Files\\*.exe",
+      "?:\\Program Files (x86)\\*.exe",
+      "?:\\Windows\\System32\\services.exe",
+      "?:\\Windows\\WinSxS\\*"
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/setcap-setuid-setgid-capability-set.asciidoc b/docs/detections/prebuilt-rules/rule-details/setcap-setuid-setgid-capability-set.asciidoc
new file mode 100644
index 0000000000..09121daf4f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/setcap-setuid-setgid-capability-set.asciidoc
@@ -0,0 +1,181 @@
+[[setcap-setuid-setgid-capability-set]]
+=== Setcap setuid/setgid Capability Set
+
+This rule monitors for the addition of the cap_setuid+ep or cap_setgid+ep capabilities via setcap. Setuid (Set User ID) and setgid (Set Group ID) are Unix-like OS features that enable processes to run with elevated privileges, based on the file owner or group. Threat actors can exploit these attributes to achieve persistence by creating malicious binaries, allowing them to maintain control over a compromised system with elevated permissions.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Setcap setuid/setgid Capability Set*
+
+
+Setuid (Set User ID) and setgid (Set Group ID) are Unix-like OS features that enable processes to run with elevated privileges, based on the file owner or group.
+
+Threat actors can exploit these attributes to achieve persistence by creating malicious binaries, allowing them to maintain control over a compromised system with elevated permissions.
+
+This rule monitors for the addition of the cap_setuid+ep or cap_setgid+ep capabilities via setcap.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible Investigation Steps*
+
+
+- Investigate the file that was targeted by the addition of the setuid/setgid capability through OSQuery.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+    - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+    - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+
+
+*False Positive Analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator that performed these actions for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and 
+process.name == "setcap" and process.args : "cap_set?id+ep" and not process.parent.name in ("jem", "vzctl")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Setuid and Setgid
+** ID: T1548.001
+** Reference URL: https://attack.mitre.org/techniques/T1548/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/setuid-setgid-bit-set-via-chmod.asciidoc b/docs/detections/prebuilt-rules/rule-details/setuid-setgid-bit-set-via-chmod.asciidoc
index 3be9360143..649968bd22 100644
--- a/docs/detections/prebuilt-rules/rule-details/setuid-setgid-bit-set-via-chmod.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/setuid-setgid-bit-set-via-chmod.asciidoc
@@ -5,7 +5,7 @@ An adversary may add the setuid or setgid bit to a file or directory in order to
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,59 +14,64 @@ An adversary may add the setuid or setgid bit to a file or directory in order to
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 33
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* macOS
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<setuid-setgid-bit-set-via-chmod-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.8.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.category:process AND event.type:(start OR process_started) AND
-process.name:chmod AND process.args:("+s" OR "u+s" OR /4[0-9]{3}/ OR
-g+s OR /2[0-9]{3}/) AND NOT process.args: (
-/.*\/Applications\/VirtualBox.app\/.+/ OR
-/\/usr\/local\/lib\/python.+/ OR
-/\/var\/folders\/.+\/FP.*nstallHelper/ OR
-/\/Library\/Filesystems\/.+/ OR
-/\/usr\/lib\/virtualbox\/.+/ OR
-/\/Library\/Application.*/ OR "/run/postgresql" OR
-"/var/crash" OR "/var/run/postgresql" OR
-/\/usr\/bin\/.+/ OR /\/usr\/local\/share\/.+/ OR
-/\/Applications\/.+/ OR /\/usr\/libexec\/.+/ OR
-"/var/metrics" OR /\/var\/lib\/dpkg\/.+/ OR
-/\/run\/log\/journal\/.*/ OR
-\/Users\/*\/.minikube\/bin\/docker-machine-driver-hyperkit
-) AND NOT process.parent.executable: (
-/\/var\/lib\/docker\/.+/ OR "/System/Library/PrivateFrame
-works/PackageKit.framework/Versions/A/XPCServices/package_script_servi
-ce.xpc/Contents/MacOS/package_script_service" OR
-"/var/lib/dpkg/info/whoopsie.postinst" )
-----------------------------------
+ process.name:chmod AND process.args:("+s" OR "u+s" OR /4[0-9]{3}/ OR g+s OR /2[0-9]{3}/) AND
+ NOT process.args:
+           (
+             /.*\/Applications\/VirtualBox.app\/.+/ OR
+             /\/usr\/local\/lib\/python.+/ OR
+             /\/var\/folders\/.+\/FP.*nstallHelper/ OR
+             /\/Library\/Filesystems\/.+/ OR
+             /\/usr\/lib\/virtualbox\/.+/ OR
+             /\/Library\/Application.*/ OR
+             "/run/postgresql" OR
+             "/var/crash" OR
+             "/var/run/postgresql" OR
+             /\/usr\/bin\/.+/ OR /\/usr\/local\/share\/.+/ OR
+             /\/Applications\/.+/ OR /\/usr\/libexec\/.+/ OR
+             "/var/metrics" OR /\/var\/lib\/dpkg\/.+/ OR
+             /\/run\/log\/journal\/.*/ OR
+             \/Users\/*\/.minikube\/bin\/docker-machine-driver-hyperkit
+           ) AND
+ NOT process.parent.executable:
+           (
+             /\/var\/lib\/docker\/.+/ OR
+             "/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/XPCServices/package_script_service.xpc/Contents/MacOS/package_script_service" OR
+             "/var/lib/dpkg/info/whoopsie.postinst"
+           )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,59 +83,11 @@ ce.xpc/Contents/MacOS/package_script_service" OR
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-
+* Sub-technique:
+** Name: Setuid and Setgid
+** ID: T1548.001
+** Reference URL: https://attack.mitre.org/techniques/T1548/001/
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-[[setuid-setgid-bit-set-via-chmod-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process AND event.type:(start OR process_started) AND
-process.name:chmod AND process.args:("+s" OR "u+s" OR /4[0-9]{3}/ OR
-g+s OR /2[0-9]{3}/)
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Rule name changed from: Setuid Bit Set via chmod
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process AND event.type:(start or process_started) AND
-process.name:chmod AND process.args:(u+s OR /4[0-9]{3}/) AND NOT
-user.name:root
-----------------------------------
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:(executed OR process_started) AND process.name:chmod AND
-process.args:(u+s OR /4[0-9]{3}/) AND NOT user.name:root
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/shared-object-created-or-changed-by-previously-unknown-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/shared-object-created-or-changed-by-previously-unknown-process.asciidoc
new file mode 100644
index 0000000000..1addbb7581
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/shared-object-created-or-changed-by-previously-unknown-process.asciidoc
@@ -0,0 +1,185 @@
+[[shared-object-created-or-changed-by-previously-unknown-process]]
+=== Shared Object Created or Changed by Previously Unknown Process
+
+This rule monitors the creation of shared object files by previously unknown processes. The creation of a shared object file involves compiling code into a dynamically linked library that can be loaded by other programs at runtime. While this process is typically used for legitimate purposes, malicious actors can leverage shared object files to execute unauthorized code, inject malicious functionality into legitimate processes, or bypass security controls. This allows malware to persist on the system, evade detection, and potentially compromise the integrity and confidentiality of the affected system and its data.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://threatpost.com/sneaky-malware-backdoors-linux/180158/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Shared Object Created or Changed by Previously Unknown Process*
+
+
+A shared object file is a compiled library file (typically with a .so extension) that can be dynamically linked to executable programs at runtime, allowing for code reuse and efficient memory usage. The creation of a shared object file involves compiling code into a dynamically linked library that can be loaded by other programs at runtime.
+
+Malicious actors can leverage shared object files to execute unauthorized code, inject malicious functionality into legitimate processes, or bypass security controls. This allows malware to persist on the system, evade detection, and potentially compromise the integrity and confidentiality of the affected system and its data.
+
+This rule monitors the creation of shared object files by previously unknown processes through the usage of the new terms rule type.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible Investigation Steps*
+
+
+- Investigate the shared object that was created or modified through OSQuery.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE path = {{file.path}}\n"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE path = {{file.path}}\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+    - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+    - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+
+
+*False Positive Analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator that performed these actions for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.action:(creation or file_create_event or file_rename_event or rename) and 
+file.path:(/dev/shm/* or /usr/lib/*) and file.extension:so and process.name:* and not (
+  process.name:("dockerd" or "dpkg" or "rpm" or "snapd" or "yum" or "vmis-launcher" or "pacman" or
+  "apt-get" or "dnf" or "podman" or "platform-python") or 
+  (process.name:vmware-install.pl and file.path:/usr/lib/vmware-tools/*)
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: Dynamic Linker Hijacking
+** ID: T1574.006
+** Reference URL: https://attack.mitre.org/techniques/T1574/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/sharepoint-malware-file-upload.asciidoc b/docs/detections/prebuilt-rules/rule-details/sharepoint-malware-file-upload.asciidoc
index 1bee260ff2..dfaae66b25 100644
--- a/docs/detections/prebuilt-rules/rule-details/sharepoint-malware-file-upload.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/sharepoint-malware-file-upload.asciidoc
@@ -5,7 +5,7 @@ Identifies the occurence of files uploaded to SharePoint being detected as Malwa
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-o365*
@@ -14,59 +14,49 @@ Identifies the occurence of files uploaded to SharePoint being detected as Malwa
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/virus-detection-in-spo?view=o365-worldwide
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Microsoft 365
-* Continuous Monitoring
-* SecOps
-* Lateral Movement
-
-*Version*: 101 (<<sharepoint-malware-file-upload-history, version history>>)
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Tactic: Lateral Movement
 
-*Added ({stack} release)*: 8.1.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Benign files can trigger signatures in the built-in virus protection
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:o365.audit and event.provider:SharePoint and
-event.code:SharePointFileOperation and
-event.action:FileMalwareDetected
+[source, js]
 ----------------------------------
+event.dataset:o365.audit and event.provider:SharePoint and event.code:SharePointFileOperation and event.action:FileMalwareDetected
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,19 +68,3 @@ event.action:FileMalwareDetected
 ** Name: Taint Shared Content
 ** ID: T1080
 ** Reference URL: https://attack.mitre.org/techniques/T1080/
-
-[[sharepoint-malware-file-upload-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/shell-configuration-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/shell-configuration-modification.asciidoc
new file mode 100644
index 0000000000..7dac5801e7
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/shell-configuration-modification.asciidoc
@@ -0,0 +1,121 @@
+[[shell-configuration-modification]]
+=== Shell Configuration Modification
+
+This rule monitors the creation/alteration of a shell configuration by a previously unknown process executable using the new terms rule type. Unix systems use shell configuration files to set environment variables, create aliases, and customize the user's environment. Adversaries may modify or add a shell configuration file to execute malicious code and gain persistence in the system. This behavior is consistent with the Kaiji malware family.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://intezer.com/blog/research/kaiji-new-chinese-linux-malware-turning-to-golang/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:file and host.os.type:linux and
+event.action:(creation or file_create_event or rename or file_rename_event) and file.path:(
+  "/etc/profile" or "/etc/profile.local" or "/etc/bashrc" or "/etc/bash.bashrc" or "/etc/bash.bashrc.local" or
+  "/etc/zshenv" or "/etc/zprofile" or "/etc/zlogin" or "/etc/zlogout" or "/root/.profile" or "/root/.bash_logout" or
+  "/root/.bashrc" or "/root/.bash_login" or /etc/profile.d/* or /home/*/.profile or /home/*/.bash_logout or
+  /home/*/.bashrc or /home/*/.bash_login
+) and not (
+  (process.executable: (
+  "/bin/dpkg" or "/usr/bin/dpkg" or "/bin/useradd" or "/usr/sbin/useradd" or "/bin/adduser" or "/usr/sbin/adduser" or
+  "/bin/dockerd" or "/usr/bin/dockerd" or "/bin/microdnf" or "/usr/bin/microdnf" or "/bin/rpm" or "/usr/bin/rpm" or
+  "/bin/snapd" or "/usr/bin/snapd" or "/bin/yum" or "/usr/bin/yum" or "/bin/dnf" or "/usr/bin/dnf" or "/bin/podman" or
+  "/usr/bin/podman" or "/bin/dnf-automatic" or "/usr/bin/dnf-automatic" or "/bin/pacman" or "/usr/bin/pacman"
+  )
+) or
+  (file.extension:("swp" or "swpx")) or
+  (process.executable:("/bin/sed" or "/usr/bin/sed") and file.name:sed*) or
+  (process.executable:("/bin/perl" or "/usr/bin/perl") and file.name:e2scrub_all.tmp*)
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: Unix Shell Configuration Modification
+** ID: T1546.004
+** Reference URL: https://attack.mitre.org/techniques/T1546/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/shell-execution-via-apple-scripting.asciidoc b/docs/detections/prebuilt-rules/rule-details/shell-execution-via-apple-scripting.asciidoc
index ee50e096e0..c076227eb5 100644
--- a/docs/detections/prebuilt-rules/rule-details/shell-execution-via-apple-scripting.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/shell-execution-via-apple-scripting.asciidoc
@@ -5,57 +5,89 @@ Identifies the execution of the shell process (sh) via scripting (JXA or AppleSc
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.apple.com/library/archive/technotes/tn2065/_index.html
 * https://objectivebythesea.com/v2/talks/OBTS_v2_Thomas.pdf
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Execution
 
-*Version*: 100 (<<shell-execution-via-apple-scripting-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.11.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=5s [process where event.type in
-("start", "process_started", "info") and process.name == "osascript"]
-by process.pid [process where event.type in ("start",
-"process_started") and process.name == "sh" and process.args == "-c"]
-by process.parent.pid
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=5s
+ [process where host.os.type == "macos" and event.type in ("start", "process_started", "info") and process.name == "osascript" and process.args : "-e"] by process.entity_id
+ [process where host.os.type == "macos" and event.type in ("start", "process_started") and process.name : ("sh", "bash", "zsh") and process.args == "-c" and process.args : ("*curl*", "*pbcopy*", "*http*", "*chmod*")] by process.parent.entity_id
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -67,28 +99,3 @@ by process.parent.pid
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[shell-execution-via-apple-scripting-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 3 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [process where event.type in
-("start", "process_started", "info") and process.name == "osascript"]
-by process.pid [process where event.type in ("start",
-"process_started") and process.name == "sh" and process.args == "-c"]
-by process.ppid
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/shortcut-file-written-or-modified-on-startup-folder.asciidoc b/docs/detections/prebuilt-rules/rule-details/shortcut-file-written-or-modified-on-startup-folder.asciidoc
new file mode 100644
index 0000000000..016aac5c42
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/shortcut-file-written-or-modified-on-startup-folder.asciidoc
@@ -0,0 +1,78 @@
+[[shortcut-file-written-or-modified-on-startup-folder]]
+=== Shortcut File Written or Modified on Startup Folder
+
+Identifies shortcut files written to or modified in the startup folder. Adversaries may use this technique to maintain persistence.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and file.extension == "lnk" and
+  file.path : (
+    "C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\Startup\\*",
+    "C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\StartUp\\*"
+  ) and
+  not (
+    (process.name : "ONENOTE.EXE" and process.code_signature.status: "trusted" and file.name : "*OneNote.lnk") or
+    (process.name : "OktaVerifySetup.exe" and process.code_signature.status: "trusted" and file.name : "Okta Verify.lnk") or
+    (process.name : "OneLaunch.exe" and process.code_signature.status: "trusted" and file.name : "OneLaunch*.lnk") or
+    (process.name : "APPServerClient.exe" and process.code_signature.status: "trusted" and file.name : "Parallels Client.lnk")
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Sub-technique:
+** Name: Registry Run Keys / Startup Folder
+** ID: T1547.001
+** Reference URL: https://attack.mitre.org/techniques/T1547/001/
+* Sub-technique:
+** Name: Shortcut Modification
+** ID: T1547.009
+** Reference URL: https://attack.mitre.org/techniques/T1547/009/
diff --git a/docs/detections/prebuilt-rules/rule-details/signed-proxy-execution-via-ms-work-folders.asciidoc b/docs/detections/prebuilt-rules/rule-details/signed-proxy-execution-via-ms-work-folders.asciidoc
index ed42ba2465..8930fb71e7 100644
--- a/docs/detections/prebuilt-rules/rule-details/signed-proxy-execution-via-ms-work-folders.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/signed-proxy-execution-via-ms-work-folders.asciidoc
@@ -5,108 +5,117 @@ Identifies the use of Windows Work Folders to execute a potentially masqueraded
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows-server/storage/work-folders/work-folders-overview
 * https://twitter.com/ElliotKillick/status/1449812843772227588
 * https://lolbas-project.github.io/lolbas/Binaries/WorkFolders/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<signed-proxy-execution-via-ms-work-folders-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
 
-*Added ({stack} release)*: 8.2.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Signed Proxy Execution via MS Work Folders
+*Triage and analysis*
+
+
+
+*Investigating Signed Proxy Execution via MS Work Folders*
+
 
-Work Folders is a role service for file servers running Windows Server that provides a consistent way for users to access
-their work files from their PCs and devices. This allows users to store work files and access them from anywhere. When
-called, Work Folders will automatically execute any Portable Executable (PE) named control.exe as an argument before
-accessing the synced share.
+Work Folders is a role service for file servers running Windows Server that provides a consistent way for users to access their work files from their PCs and devices. This allows users to store work files and access them from anywhere. When called, Work Folders will automatically execute any Portable Executable (PE) named control.exe as an argument before accessing the synced share.
 
-Using Work Folders to execute a masqueraded control.exe could allow an adversary to bypass application controls and
-increase privileges.
+Using Work Folders to execute a masqueraded control.exe could allow an adversary to bypass application controls and increase privileges.
 
-#### Possible investigation steps
 
-- Investigate the process tree starting with parent process WorkFolders.exe and child process control.exe to determine
-if other child processes spawned during execution.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+    - Examine the location of the WorkFolders.exe binary to determine if it was copied to the location of the control.exe binary. It resides in the System32 directory by default.
 - Trace the activity related to the control.exe binary to identify any continuing intrusion activity on the host.
-- Examine the location of the WorkFolders.exe binary to determine if it was copied to the location of the control.exe
-binary. It resides in the System32 directory by default.
-- Review the control.exe binary executed with Work Folders to determine maliciousness such as additional host activity
-or network traffic.
+- Review the control.exe binary executed with Work Folders to determine maliciousness such as additional host activity or network traffic.
 - Determine if control.exe was synced to sync share, indicating potential lateral movement.
 - Review how control.exe was originally delivered on the host, such as emailed, downloaded from the web, or written to
 disk from a separate binary.
 
-### False positive analysis
 
-- Windows Work Folders are used legitimately by end users and administrators for file sharing and syncing but not in the
-instance where a suspicious control.exe is passed as an argument.
+*False positive analysis*
+
+
+- Windows Work Folders are used legitimately by end users and administrators for file sharing and syncing but not in the instance where a suspicious control.exe is passed as an argument.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
 - Review the Work Folders synced share to determine if the control.exe was shared and if so remove it.
-- If no lateral movement was identified during investigation, take the affected host offline if possible and remove the
-control.exe binary as well as any additional artifacts identified during investigation.
-- Review integrating Windows Information Protection (WIP) to enforce data protection by encrypting the data on PCs using
-Work Folders.
+- If no lateral movement was identified during investigation, take the affected host offline if possible and remove the control.exe binary as well as any additional artifacts identified during investigation.
+- Review integrating Windows Information Protection (WIP) to enforce data protection by encrypting the data on PCs using Work Folders.
 - Confirm with the user whether this was expected or not, and reset their password.
-----------------------------------
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name :
-"control.exe" and process.parent.name : "WorkFolders.exe" and not
-process.executable : ("?:\\Windows\\System32\\control.exe",
-"?:\\Windows\\SysWOW64\\control.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start"
+    and process.name : "control.exe" and process.parent.name : "WorkFolders.exe"
+    and not process.executable : ("?:\\Windows\\System32\\control.exe", "?:\\Windows\\SysWOW64\\control.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -118,27 +127,3 @@ process.executable : ("?:\\Windows\\System32\\control.exe",
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[signed-proxy-execution-via-ms-work-folders-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start","process_started") and
-process.name : "control.exe" and process.parent.name :
-"WorkFolders.exe" and not process.executable :
-("?:\\Windows\\System32\\control.exe",
-"?:\\Windows\\SysWOW64\\control.exe")
-----------------------------------
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.3.0 release)::
-* Rule name changed from: Signed Proxy Execution via MS WorkFolders
diff --git a/docs/detections/prebuilt-rules/rule-details/sip-provider-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/sip-provider-modification.asciidoc
index 3229198a3a..505ec1f878 100644
--- a/docs/detections/prebuilt-rules/rule-details/sip-provider-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/sip-provider-modification.asciidoc
@@ -5,60 +5,60 @@ Identifies modifications to the registered Subject Interface Package (SIP) provi
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
 * endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/mattifestation/PoCSubjectInterfacePackage
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
-
-*Version*: 101 (<<sip-provider-modification-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type:"change" and registry.path: (
-"*\\SOFTWARE\\Microsoft\\Cryptography\\OID\\EncodingType
-0\\CryptSIPDllPutSignedDataMsg\\{*}\\Dll",
-"*\\SOFTWARE\\WOW6432Node\\Microsoft\\Cryptography\\OID\\EncodingType
-0\\CryptSIPDllPutSignedDataMsg\\{*}\\Dll", "*\\SOFTWARE\\Microsoft
-\\Cryptography\\Providers\\Trust\\FinalPolicy\\{*}\\$Dll", "*\\SOF
-TWARE\\WOW6432Node\\Microsoft\\Cryptography\\Providers\\Trust\\FinalPo
-licy\\{*}\\$Dll" ) and registry.data.strings:"*.dll"
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type:"change" and
+  registry.path: (
+    "*\\SOFTWARE\\Microsoft\\Cryptography\\OID\\EncodingType 0\\CryptSIPDllPutSignedDataMsg\\{*}\\Dll",
+    "*\\SOFTWARE\\WOW6432Node\\Microsoft\\Cryptography\\OID\\EncodingType 0\\CryptSIPDllPutSignedDataMsg\\{*}\\Dll",
+    "*\\SOFTWARE\\Microsoft\\Cryptography\\Providers\\Trust\\FinalPolicy\\{*}\\$Dll",
+    "*\\SOFTWARE\\WOW6432Node\\Microsoft\\Cryptography\\Providers\\Trust\\FinalPolicy\\{*}\\$Dll"
+    ) and
+  registry.data.strings:"*.dll"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,31 +70,7 @@ licy\\{*}\\$Dll" ) and registry.data.strings:"*.dll"
 ** Name: Subvert Trust Controls
 ** ID: T1553
 ** Reference URL: https://attack.mitre.org/techniques/T1553/
-
-[[sip-provider-modification-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type:"change" and registry.path: (
-"HKLM\\SOFTWARE\\Microsoft\\Cryptography\\OID\\EncodingType
-0\\CryptSIPDllPutSignedDataMsg\\{*}\\Dll", "HKLM\\SOFTWARE\\WOW643
-2Node\\Microsoft\\Cryptography\\OID\\EncodingType
-0\\CryptSIPDllPutSignedDataMsg\\{*}\\Dll", "HKLM\\SOFTWARE\\Micros
-oft\\Cryptography\\Providers\\Trust\\FinalPolicy\\{*}\\$Dll", "HKL
-M\\SOFTWARE\\WOW6432Node\\Microsoft\\Cryptography\\Providers\\Trust\\F
-inalPolicy\\{*}\\$Dll" ) and registry.data.strings:"*.dll"
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: SIP and Trust Provider Hijacking
+** ID: T1553.003
+** Reference URL: https://attack.mitre.org/techniques/T1553/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/smb-windows-file-sharing-activity-to-the-internet.asciidoc b/docs/detections/prebuilt-rules/rule-details/smb-windows-file-sharing-activity-to-the-internet.asciidoc
index 18f20bdfe5..17bee9f099 100644
--- a/docs/detections/prebuilt-rules/rule-details/smb-windows-file-sharing-activity-to-the-internet.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/smb-windows-file-sharing-activity-to-the-internet.asciidoc
@@ -5,66 +5,84 @@ This rule detects network events that may indicate the use of Windows file shari
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Network
-* Threat Detection
-* Initial Access
-* Host
+* Tactic: Initial Access
+* Domain: Endpoint
+* Use Case: Threat Detection
 
-*Version*: 100 (<<smb-windows-file-sharing-activity-to-the-internet-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.6.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:(139 or 445) or event.dataset:zeek.smb) and
-source.ip:( 10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16
-) and not destination.ip:( 10.0.0.0/8 or 127.0.0.0/8 or
-169.254.0.0/16 or 172.16.0.0/12 or 192.0.0.0/24 or
-192.0.0.0/29 or 192.0.0.8/32 or 192.0.0.9/32 or
-192.0.0.10/32 or 192.0.0.170/32 or 192.0.0.171/32 or
-192.0.2.0/24 or 192.31.196.0/24 or 192.52.193.0/24 or
-192.168.0.0/16 or 192.88.99.0/24 or 224.0.0.0/4 or
-100.64.0.0/10 or 192.175.48.0/24 or 198.18.0.0/15 or
-198.51.100.0/24 or 203.0.113.0/24 or 240.0.0.0/4 or "::1"
-or "FE80::/10" or "FF00::/8" )
+[source, js]
 ----------------------------------
+(event.dataset: network_traffic.flow or (event.category: (network or network_traffic))) and
+  network.transport:tcp and (destination.port:(139 or 445) or event.dataset:zeek.smb) and
+  source.ip:(
+    10.0.0.0/8 or
+    172.16.0.0/12 or
+    192.168.0.0/16
+  ) and
+  not destination.ip:(
+    10.0.0.0/8 or
+    127.0.0.0/8 or
+    169.254.0.0/16 or
+    172.16.0.0/12 or
+    192.0.0.0/24 or
+    192.0.0.0/29 or
+    192.0.0.8/32 or
+    192.0.0.9/32 or
+    192.0.0.10/32 or
+    192.0.0.170/32 or
+    192.0.0.171/32 or
+    192.0.2.0/24 or
+    192.31.196.0/24 or
+    192.52.193.0/24 or
+    192.168.0.0/16 or
+    192.88.99.0/24 or
+    224.0.0.0/4 or
+    100.64.0.0/10 or
+    192.175.48.0/24 or
+    198.18.0.0/15 or
+    198.51.100.0/24 or
+    203.0.113.0/24 or
+    240.0.0.0/4 or
+    "::1" or
+    "FE80::/10" or
+    "FF00::/8"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,8 +94,6 @@ or "FE80::/10" or "FF00::/8" )
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-
 * Tactic:
 ** Name: Exfiltration
 ** ID: TA0010
@@ -86,75 +102,3 @@ or "FE80::/10" or "FF00::/8" )
 ** Name: Exfiltration Over Alternative Protocol
 ** ID: T1048
 ** Reference URL: https://attack.mitre.org/techniques/T1048/
-
-[[smb-windows-file-sharing-activity-to-the-internet-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 12 (8.4.0 release)::
-* Formatting only
-
-Version 11 (7.15.0 release)::
-* Formatting only
-
-Version 10 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:(139 or 445) or event.dataset:zeek.smb) and
-source.ip:( 10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16 ) and not
-destination.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
-172.16.0.0/12 or 192.168.0.0/16 or 224.0.0.0/4 or "::1" or "FE80::/10"
-or "FF00::/8" )
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:(139 or 445) or event.dataset:zeek.smb) and
-source.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) and not
-destination.ip:(10.0.0.0/8 or 127.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 or "::1")
-----------------------------------
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport:tcp and destination.port:(139 or 445) and
-source.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) and not
-destination.ip:(10.0.0.0/8 or 127.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 or "::1")
-----------------------------------
-
-Version 3 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport: tcp and destination.port: (139 or 445) and (
-network.direction: outbound or ( source.ip: (10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16) and not destination.ip: (10.0.0.0/8
-or 172.16.0.0/12 or 192.168.0.0/16) ) )
-----------------------------------
-
-Version 2 (7.6.1 release)::
-* Removed auditbeat-\*, packetbeat-*, and winlogbeat-* from the rule indices.
-
diff --git a/docs/detections/prebuilt-rules/rule-details/smtp-on-port-26-tcp.asciidoc b/docs/detections/prebuilt-rules/rule-details/smtp-on-port-26-tcp.asciidoc
index 72bfb54ff9..1c2924239e 100644
--- a/docs/detections/prebuilt-rules/rule-details/smtp-on-port-26-tcp.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/smtp-on-port-26-tcp.asciidoc
@@ -5,62 +5,51 @@ This rule detects events that may indicate use of SMTP on TCP port 26. This port
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://unit42.paloaltonetworks.com/unit42-badpatch/
 * https://isc.sans.edu/forums/diary/Next+up+whats+up+with+TCP+port+26/25564/
 
-*Tags*:
-
-* Elastic
-* Host
-* Network
-* Threat Detection
-* Command and Control
-* Host
+*Tags*: 
 
-*Version*: 100 (<<smtp-on-port-26-tcp-history, version history>>)
+* Tactic: Command and Control
+* Domain: Endpoint
+* Use Case: Threat Detection
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Servers that process email traffic may cause false positives and should be excluded from this rule as this is expected behavior.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:26 or (event.dataset:zeek.smtp and
-destination.port:26))
+[source, js]
 ----------------------------------
+(event.dataset: (network_traffic.flow or zeek.smtp) or event.category:(network or network_traffic)) and network.transport:tcp and destination.port:26
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -68,8 +57,6 @@ destination.port:26))
 ** Name: Command and Control
 ** ID: TA0011
 ** Reference URL: https://attack.mitre.org/tactics/TA0011/
-
-
 * Tactic:
 ** Name: Exfiltration
 ** ID: TA0010
@@ -78,46 +65,3 @@ destination.port:26))
 ** Name: Exfiltration Over Alternative Protocol
 ** ID: T1048
 ** Reference URL: https://attack.mitre.org/techniques/T1048/
-
-[[smtp-on-port-26-tcp-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 8 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and (destination.port:26 or (event.dataset:zeek.smtp and
-destination.port:26))
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport:tcp and destination.port:26
-----------------------------------
-
-Version 2 (7.6.1 release)::
-* Removed auditbeat-\*, packetbeat-*, and winlogbeat-* from the rule indices.
-
diff --git a/docs/detections/prebuilt-rules/rule-details/softwareupdate-preferences-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/softwareupdate-preferences-modification.asciidoc
index 04b72795d9..5d01b9e728 100644
--- a/docs/detections/prebuilt-rules/rule-details/softwareupdate-preferences-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/softwareupdate-preferences-modification.asciidoc
@@ -5,60 +5,88 @@ Identifies changes to the SoftwareUpdate preferences using the built-in defaults
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.checkpoint.com/2017/07/13/osxdok-refuses-go-away-money/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Defense Evasion
 
-*Version*: 100 (<<softwareupdate-preferences-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Authorized SoftwareUpdate Settings Changes
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:defaults and process.args:(write and "-bool" and
-(com.apple.SoftwareUpdate or
-/Library/Preferences/com.apple.SoftwareUpdate.plist) and not (TRUE or
-true))
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+ process.name:defaults and
+ process.args:(write and "-bool" and (com.apple.SoftwareUpdate or /Library/Preferences/com.apple.SoftwareUpdate.plist) and not (TRUE or true))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,22 +98,7 @@ true))
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[softwareupdate-preferences-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:defaults and process.args:(write and "-bool" and
-(com.apple.SoftwareUpdate or
-/Library/Preferences/com.apple.SoftwareUpdate.plist) and not (TRUE or
-true))
-----------------------------------
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/solarwinds-process-disabling-services-via-registry.asciidoc b/docs/detections/prebuilt-rules/rule-details/solarwinds-process-disabling-services-via-registry.asciidoc
index a08a234723..5ae40204cc 100644
--- a/docs/detections/prebuilt-rules/rule-details/solarwinds-process-disabling-services-via-registry.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/solarwinds-process-disabling-services-via-registry.asciidoc
@@ -5,72 +5,81 @@ Identifies a SolarWinds binary modifying the start type of a service to be disab
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.fireeye.com/blog/threat-research/2020/12/evasive-attacker-leverages-solarwinds-supply-chain-compromises-with-sunburst-backdoor.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
-
-*Version*: 101 (<<solarwinds-process-disabling-services-via-registry-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Initial Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.path : (
-"HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\Start",
-"\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\*\\Start" )
-and registry.data.strings : ("4", "0x00000004") and process.name :
-( "SolarWinds.BusinessLayerHost*.exe",
-"ConfigurationWizard*.exe", "NetflowDatabaseMaintenance*.exe",
-"NetFlowService*.exe", "SolarWinds.Administration*.exe",
-"SolarWinds.Collector.Service*.exe",
-"SolarwindsDiagnostics*.exe")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and registry.path : (
+    "HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\Start",
+    "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\*\\Start"
+  ) and
+  registry.data.strings : ("4", "0x00000004") and
+  process.name : (
+      "SolarWinds.BusinessLayerHost*.exe",
+      "ConfigurationWizard*.exe",
+      "NetflowDatabaseMaintenance*.exe",
+      "NetFlowService*.exe",
+      "SolarWinds.Administration*.exe",
+      "SolarWinds.Collector.Service*.exe",
+      "SolarwindsDiagnostics*.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -82,8 +91,14 @@ and registry.data.strings : ("4", "0x00000004") and process.name :
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -92,64 +107,7 @@ and registry.data.strings : ("4", "0x00000004") and process.name :
 ** Name: Supply Chain Compromise
 ** ID: T1195
 ** Reference URL: https://attack.mitre.org/techniques/T1195/
-
-[[solarwinds-process-disabling-services-via-registry-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path :
-"HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\Start" and
-registry.data.strings : ("4", "0x00000004") and process.name : (
-"SolarWinds.BusinessLayerHost*.exe", "ConfigurationWizard*.exe",
-"NetflowDatabaseMaintenance*.exe", "NetFlowService*.exe",
-"SolarWinds.Administration*.exe",
-"SolarWinds.Collector.Service*.exe" ,
-"SolarwindsDiagnostics*.exe")
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path :
-"HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\Start" and
-registry.data.strings : ("4", "0x00000004") and process.name : (
-"SolarWinds.BusinessLayerHost*.exe",
-"ConfigurationWizard*.exe", "NetflowDatabaseMaintenance*.exe",
-"NetFlowService*.exe", "SolarWinds.Administration*.exe",
-"SolarWinds.Collector.Service*.exe" ,
-"SolarwindsDiagnostics*.exe")
-----------------------------------
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path :
-"HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\Start" and
-registry.data.strings == "4" and process.name : (
-"SolarWinds.BusinessLayerHost*.exe", "ConfigurationWizard*.exe",
-"NetflowDatabaseMaintenance*.exe", "NetFlowService*.exe",
-"SolarWinds.Administration*.exe",
-"SolarWinds.Collector.Service*.exe" ,
-"SolarwindsDiagnostics*.exe")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Compromise Software Supply Chain
+** ID: T1195.002
+** Reference URL: https://attack.mitre.org/techniques/T1195/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-aws-error-messages.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-aws-error-messages.asciidoc
index 56a5c78cfa..74407e3825 100644
--- a/docs/detections/prebuilt-rules/rule-details/spike-in-aws-error-messages.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-aws-error-messages.asciidoc
@@ -5,99 +5,91 @@ A machine learning job detected a significant spike in the rate of a particular
 
 *Rule type*: machine_learning
 
-*Machine learning job*: high_distinct_count_error_message
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Resources: Investigation Guide
+
+*Version*: 208
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* ML
-* Investigation Guide
 
-*Version*: 102 (<<spike-in-aws-error-messages-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.9.0
+==== Investigation guide
 
-*Last modified ({stack} release)*: 8.6.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Triage and analysis*
 
-==== Potential false positives
 
-Spikes in error message activity can also be due to bugs in cloud automation scripts or workflows; changes to cloud automation scripts or workflows; adoption of new services; changes in the way services are used; or changes to IAM privileges.
 
-==== Investigation guide
+*Investigating Spike in AWS Error Messages*
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+CloudTrail logging provides visibility on actions taken within an AWS environment. By monitoring these events and understanding what is considered normal behavior within an organization, you can spot suspicious or malicious activity when deviations occur.
 
-### Investigating Spike in AWS Error Messages
+This rule uses a machine learning job to detect a significant spike in the rate of a particular error in the CloudTrail messages. Spikes in error messages may accompany attempts at privilege escalation, lateral movement, or discovery.
 
-CloudTrail logging provides visibility on actions taken within an AWS environment. By monitoring these events and
-understanding what is considered normal behavior within an organization, you can spot suspicious or malicious activity
-when deviations occur.
 
-This rule uses a machine learning job to detect a significant spike in the rate of a particular error in the CloudTrail
-messages. Spikes in error messages may accompany attempts at privilege escalation, lateral movement, or discovery.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Examine the history of the error. If the error only manifested recently, it might be related to recent changes in an
-automation module or script. You can find the error in the `aws.cloudtrail.error_code field` field.
+- Examine the history of the error. If the error only manifested recently, it might be related to recent changes in an automation module or script. You can find the error in the `aws.cloudtrail.error_code field` field.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Validate the activity is not related to planned patches, updates, or network administrator activity.
-- Examine the request parameters. These may indicate the source of the program or the nature of the task being performed
-when the error occurred.
+- Examine the request parameters. These may indicate the source of the program or the nature of the task being performed when the error occurred.
     - Check whether the error is related to unsuccessful attempts to enumerate or access objects, data, or secrets.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the calling user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
-- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal
-time of day?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
+- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal time of day?
 - Contact the account owner and confirm whether they are aware of this activity if suspicious.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
 
-### False positive analysis
+*False positive analysis*
 
-- Examine the history of the command. If the command only manifested recently, it might be part of a new automation
-module or script. If it has a consistent cadence (for example, it appears in small numbers on a weekly or monthly cadence),
-it might be part of a housekeeping or maintenance process. You can find the command in the `event.action field` field.
+
+- Examine the history of the command. If the command only manifested recently, it might be part of a new automation module or script. If it has a consistent cadence (for example, it appears in small numbers on a weekly or monthly cadence), it might be part of a housekeeping or maintenance process. You can find the command in the `event.action field` field.
 - The adoption of new services or the addition of new functionality to scripts may generate false positives.
 
-### Related Rules
+
+*Related Rules*
+
 
 - Unusual City For an AWS Command - 809b70d3-e2c3-455e-af1b-2626a5a1a276
 - Unusual Country For an AWS Command - dca28dee-c999-400f-b640-50a081cc0fd1
 - Unusual AWS Command for a User - ac706eae-d5ec-4b14-b4fd-e8ba8086f0e1
 - Rare AWS Error Code - 19de8096-e2b0-4bd8-80c9-34a820813fff
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -107,53 +99,16 @@ it might be part of a housekeeping or maintenance process. You can find the comm
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
-
-
-[[spike-in-aws-error-messages-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 11 (8.4.0 release)::
-* Formatting only
-
-Version 9 (8.2.0 release)::
-* Formatting only
-
-Version 8 (8.1.0 release)::
-* Formatting only
-
-Version 7 (7.16.0 release)::
-* Formatting only
-
-Version 6 (7.15.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 3 (7.12.0 release)::
-* Formatting only
+==== Setup
 
-Version 2 (7.10.0 release)::
-* Formatting only
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-bytes-sent-to-an-external-device-via-airdrop.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-bytes-sent-to-an-external-device-via-airdrop.asciidoc
new file mode 100644
index 0000000000..d79c85149c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-bytes-sent-to-an-external-device-via-airdrop.asciidoc
@@ -0,0 +1,90 @@
+[[spike-in-bytes-sent-to-an-external-device-via-airdrop]]
+=== Spike in Bytes Sent to an External Device via Airdrop
+
+A machine learning job has detected high bytes of data written to an external device via Airdrop. In a typical operational setting, there is usually a predictable pattern or a certain range of data that is written to external devices. An unusually large amount of data being written is anomalous and can signal illicit data copying or transfer activities.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-2h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/ded
+* https://www.elastic.co/blog/detect-data-exfiltration-activity-with-kibanas-new-integration
+
+*Tags*: 
+
+* Use Case: Data Exfiltration Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Exfiltration
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Data Exfiltration Detection integration assets to be installed, as well as network and file events collected by integrations such as Elastic Defend and Network Packet Capture (for network events only).  
+
+
+*Data Exfiltration Detection Setup*
+
+The Data Exfiltration Detection integration detects data exfiltration activity by identifying abnormalities in network and file events. Anomalies are detected using Elastic's Anomaly Detection feature. 
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Data Exfiltration Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- File events collected by the Elastic Defend integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Data Exfiltration Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Data Exfiltration Detection and select the integration to see more details about it.
+- Under Settings, click Install Data Exfiltration Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Data Exfiltration Detection, you'll need to enable the corresponding Anomaly Detection jobs. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your file events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/ded/kibana/ml_module/ded-ml.json[this] configuration file, you will see a card for Data Exfiltration Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over Other Network Medium
+** ID: T1011
+** Reference URL: https://attack.mitre.org/techniques/T1011/
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-bytes-sent-to-an-external-device.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-bytes-sent-to-an-external-device.asciidoc
new file mode 100644
index 0000000000..1f3e4dd10b
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-bytes-sent-to-an-external-device.asciidoc
@@ -0,0 +1,90 @@
+[[spike-in-bytes-sent-to-an-external-device]]
+=== Spike in Bytes Sent to an External Device
+
+A machine learning job has detected high bytes of data written to an external device. In a typical operational setting, there is usually a predictable pattern or a certain range of data that is written to external devices. An unusually large amount of data being written is anomalous and can signal illicit data copying or transfer activities.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-2h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/ded
+* https://www.elastic.co/blog/detect-data-exfiltration-activity-with-kibanas-new-integration
+
+*Tags*: 
+
+* Use Case: Data Exfiltration Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Exfiltration
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Data Exfiltration Detection integration assets to be installed, as well as network and file events collected by integrations such as Elastic Defend and Network Packet Capture (for network events only).  
+
+
+*Data Exfiltration Detection Setup*
+
+The Data Exfiltration Detection integration detects data exfiltration activity by identifying abnormalities in network and file events. Anomalies are detected using Elastic's Anomaly Detection feature. 
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Data Exfiltration Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- File events collected by the Elastic Defend integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Data Exfiltration Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Data Exfiltration Detection and select the integration to see more details about it.
+- Under Settings, click Install Data Exfiltration Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Data Exfiltration Detection, you'll need to enable the corresponding Anomaly Detection jobs. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your file events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/ded/kibana/ml_module/ded-ml.json[this] configuration file, you will see a card for Data Exfiltration Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over Physical Medium
+** ID: T1052
+** Reference URL: https://attack.mitre.org/techniques/T1052/
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-failed-logon-events.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-failed-logon-events.asciidoc
index b1ebb8da73..a486334a42 100644
--- a/docs/detections/prebuilt-rules/rule-details/spike-in-failed-logon-events.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-failed-logon-events.asciidoc
@@ -5,47 +5,84 @@ A machine learning job found an unusually large spike in authentication failure
 
 *Rule type*: machine_learning
 
-*Machine learning job*: auth_high_count_logon_fails
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Credential Access
+* Resources: Investigation Guide
+
+*Version*: 104
+
+*Rule authors*: 
 
 * Elastic
-* Authentication
-* Threat Detection
-* ML
-* Credential Access
 
-*Version*: 100 (<<spike-in-failed-logon-events-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.14.0
+==== Investigation guide
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Triage and analysis*
+
+
+
+*Investigating Spike in Failed Logon Events*
+
+
+This rule uses a machine learning job to detect a substantial spike in failed authentication events. This could indicate attempts to enumerate users, password spraying, brute force, etc.
+
+
+*Possible investigation steps*
 
-==== Potential false positives
 
-A misconfigured service account can trigger this alert. A password change on an account used by an email client can trigger this alert. Security test cycles that include brute force or password spraying activities may trigger this alert.
-==== Threat mapping
+- Identify the users involved and if the activity targets a specific user or a set of users.
+- Check if the authentication comes from different sources.
+- Investigate if the host where the failed authentication events occur is exposed to the internet.
+  - If the host is exposed to the internet, and the source of these attempts is external, the activity can be related to bot activity and possibly not directed at your organization.
+  - If the host is not exposed to the internet, investigate the hosts where the authentication attempts are coming from, as this can indicate that they are compromised and the attacker is trying to move laterally.
+- Investigate other alerts associated with the involved users and hosts during the past 48 hours.
+- Check whether the involved credentials are used in automation or scheduled tasks.
+- If this activity is suspicious, contact the account owner and confirm whether they are aware of it.
+- Investigate whether there are successful authentication events from the involved sources. This could indicate a successful brute force or password spraying attack.
+
+
+*False positive analysis*
+
+
+- If the account is used in automation tasks, it is possible that they are using expired credentials, causing a spike in authentication failures.
+- Authentication failures can be related to permission issues.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Assess whether the asset should be exposed to the internet, and take action to reduce your attack surface.
+  - If the asset needs to be exposed to the internet, restrict access to remote login services to specific IPs.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -57,16 +94,3 @@ A misconfigured service account can trigger this alert. A password change on an
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
-
-[[spike-in-failed-logon-events-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-firewall-denies.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-firewall-denies.asciidoc
index 3caab81be3..91b366b21c 100644
--- a/docs/detections/prebuilt-rules/rule-details/spike-in-firewall-denies.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-firewall-denies.asciidoc
@@ -5,52 +5,33 @@ A machine learning job detected an unusually large spike in network traffic that
 
 *Rule type*: machine_learning
 
-*Machine learning job*: high_count_network_denies
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Network
-* Threat Detection
-* ML
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
 
-*Version*: 100 (<<spike-in-firewall-denies-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.13.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A misconfgured network application or firewall may trigger this alert. Security scans or test cycles may trigger this alert.
-
-[[spike-in-firewall-denies-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (7.14.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-logon-events.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-logon-events.asciidoc
index 4974592e40..9bc3bedd3d 100644
--- a/docs/detections/prebuilt-rules/rule-details/spike-in-logon-events.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-logon-events.asciidoc
@@ -5,47 +5,38 @@ A machine learning job found an unusually large spike in successful authenticati
 
 *Rule type*: machine_learning
 
-*Machine learning job*: auth_high_count_logon_events
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Authentication
-* Threat Detection
-* ML
-* Credential Access
+* Use Case: Identity and Access Audit
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Credential Access
 
-*Version*: 100 (<<spike-in-logon-events-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.14.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Build servers and CI systems can sometimes trigger this alert. Security test cycles that include brute force or password spraying activities may trigger this alert.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -57,13 +48,3 @@ Build servers and CI systems can sometimes trigger this alert. Security test cyc
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
-
-[[spike-in-logon-events-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-network-traffic-to-a-country.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-network-traffic-to-a-country.asciidoc
index da5570f108..3f3c06f315 100644
--- a/docs/detections/prebuilt-rules/rule-details/spike-in-network-traffic-to-a-country.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-network-traffic-to-a-country.asciidoc
@@ -1,56 +1,88 @@
 [[spike-in-network-traffic-to-a-country]]
 === Spike in Network Traffic To a Country
 
-A machine learning job detected an unusually large spike in network activity to one destination country in the network logs. This could be due to unusually large amounts of reconnaissance or enumeration traffic. Data exfiltration activity may also produce such a surge in traffic to a destination country which does not normally appear in network traffic or business work-flows. Malware instances and persistence mechanisms may communicate with command-and-control (C2) infrastructure in their country of origin, which may be an unusual destination country for the source network.
+A machine learning job detected an unusually large spike in network activity to one destination country in the network logs. This could be due to unusually large amounts of reconnaissance or enumeration traffic. Data exfiltration activity may also produce such a surge in traffic to a destination country that does not normally appear in network traffic or business workflows. Malware instances and persistence mechanisms may communicate with command-and-control (C2) infrastructure in their country of origin, which may be an unusual destination country for the source network.
 
 *Rule type*: machine_learning
 
-*Machine learning job*: high_count_by_destination_country
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+
+*Version*: 104
+
+*Rule authors*: 
 
 * Elastic
-* Network
-* Threat Detection
-* ML
 
-*Version*: 100 (<<spike-in-network-traffic-to-a-country-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.13.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
+
+
+
+*Investigating Spike in Network Traffic To a Country*
+
+
+Monitoring network traffic for anomalies is a good methodology for uncovering various potentially suspicious activities. For example, data exfiltration or infected machines may communicate with a command-and-control (C2) server in another country your company doesn't have business with.
+
+This rule uses a machine learning job to detect a significant spike in the network traffic to a country, which can indicate reconnaissance or enumeration activities, an infected machine being used as a bot in a DDoS attack, or potentially data exfiltration.
+
+
+*Possible investigation steps*
+
+
+- Identify the specifics of the involved assets, such as role, criticality, and associated users.
+- Investigate other alerts associated with the involved assets during the past 48 hours.
+- Examine the data available and determine the exact users and processes involved in those connections.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Consider the time of day. If the user is a human (not a program or script), did the activity occurs during working hours?
+- If this activity is suspicious, contact the account owner and confirm whether they are aware of it.
+
+
+*False positive analysis*
+
+
+- Understand the context of the connections by contacting the asset owners. If this activity is related to a new business process or newly implemented (approved) technology, consider adding exceptions — preferably with a combination of user and source conditions.
 
-Business workflows that occur very occasionally, and involve an unusual surge in network traffic to one destination country, can trigger this alert. A new business workflow or a surge in business activity in a particular country may trigger this alert. Business travelers who roam to many countries for brief periods may trigger this alert if they engage in volumetric network activity.
 
-[[spike-in-network-traffic-to-a-country-history]]
-==== Rule version history
+*Response and remediation*
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 2 (7.14.0 release)::
-* Formatting only
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+  - Remove and block malicious artifacts identified during triage.
+- Consider implementing temporary network border rules to block or alert connections to the target country, if relevant.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-network-traffic.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-network-traffic.asciidoc
index c462f101d3..64c640a676 100644
--- a/docs/detections/prebuilt-rules/rule-details/spike-in-network-traffic.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-network-traffic.asciidoc
@@ -5,55 +5,33 @@ A machine learning job detected an unusually large spike in network traffic. Suc
 
 *Rule type*: machine_learning
 
-*Machine learning job*: high_count_network_events
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Network
-* Threat Detection
-* ML
+*Tags*: 
 
-*Version*: 100 (<<spike-in-network-traffic-history, version history>>)
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
 
-*Added ({stack} release)*: 7.13.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Business workflows that occur very occasionally, and involve an unusual surge in network traffic, can trigger this alert. A new business workflow or a surge in business activity may trigger this alert. A misconfigured network application or firewall may trigger this alert.
-
-[[spike-in-network-traffic-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (7.15.0 release)::
-* Formatting only
-
-Version 2 (7.14.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-number-of-connections-made-from-a-source-ip.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-number-of-connections-made-from-a-source-ip.asciidoc
new file mode 100644
index 0000000000..0551be606d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-number-of-connections-made-from-a-source-ip.asciidoc
@@ -0,0 +1,92 @@
+[[spike-in-number-of-connections-made-from-a-source-ip]]
+=== Spike in Number of Connections Made from a Source IP
+
+A machine learning job has detected a high count of destination IPs establishing an RDP connection with a single source IP. Once an attacker has gained access to one system, they might attempt to access more in the network in search of valuable assets, data, or further access points.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-12h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/lmd
+* https://www.elastic.co/blog/detecting-lateral-movement-activity-a-new-kibana-integration
+* https://www.elastic.co/blog/remote-desktop-protocol-connections-elastic-security
+
+*Tags*: 
+
+* Use Case: Lateral Movement Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Lateral Movement Detection integration assets to be installed, as well as file and Windows RDP process events collected by the Elastic Defend integration.  
+
+
+*Lateral Movement Detection Setup*
+
+The Lateral Movement Detection integration detects lateral movement activity by identifying abnormalities in file and Windows RDP events. Anomalies are detected using Elastic's Anomaly Detection feature.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Lateral Movement Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows RDP process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Lateral Movement Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Lateral Movement Detection and select the integration to see more details about it.
+- Under Settings, click Install Lateral Movement Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Lateral Movement Detection, you'll need to enable the corresponding Anomaly Detection jobs.
+- Before enabling the Anomaly Detection jobs, confirm that the Pivot Transform asset is installed and actively gathering data in the destination index `ml-rdp-lmd`.
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your transformed RDP process data i.e.`ml-rdp-lmd`.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/lmd/kibana/ml_module/lmd-ml.json[this] configuration file, you will see a card for Lateral Movement Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-number-of-connections-made-to-a-destination-ip.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-number-of-connections-made-to-a-destination-ip.asciidoc
new file mode 100644
index 0000000000..b19128f359
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-number-of-connections-made-to-a-destination-ip.asciidoc
@@ -0,0 +1,92 @@
+[[spike-in-number-of-connections-made-to-a-destination-ip]]
+=== Spike in Number of Connections Made to a Destination IP
+
+A machine learning job has detected a high count of source IPs establishing an RDP connection with a single destination IP. Attackers might use multiple compromised systems to attack a target to ensure redundancy in case a source IP gets detected and blocked.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-12h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/lmd
+* https://www.elastic.co/blog/detecting-lateral-movement-activity-a-new-kibana-integration
+* https://www.elastic.co/blog/remote-desktop-protocol-connections-elastic-security
+
+*Tags*: 
+
+* Use Case: Lateral Movement Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Lateral Movement Detection integration assets to be installed, as well as file and Windows RDP process events collected by the Elastic Defend integration.  
+
+
+*Lateral Movement Detection Setup*
+
+The Lateral Movement Detection integration detects lateral movement activity by identifying abnormalities in file and Windows RDP events. Anomalies are detected using Elastic's Anomaly Detection feature.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Lateral Movement Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows RDP process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Lateral Movement Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Lateral Movement Detection and select the integration to see more details about it.
+- Under Settings, click Install Lateral Movement Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Lateral Movement Detection, you'll need to enable the corresponding Anomaly Detection jobs.
+- Before enabling the Anomaly Detection jobs, confirm that the Pivot Transform asset is installed and actively gathering data in the destination index `ml-rdp-lmd`.
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your transformed RDP process data i.e.`ml-rdp-lmd`.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/lmd/kibana/ml_module/lmd-ml.json[this] configuration file, you will see a card for Lateral Movement Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-number-of-processes-in-an-rdp-session.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-number-of-processes-in-an-rdp-session.asciidoc
new file mode 100644
index 0000000000..70c5fcd663
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-number-of-processes-in-an-rdp-session.asciidoc
@@ -0,0 +1,92 @@
+[[spike-in-number-of-processes-in-an-rdp-session]]
+=== Spike in Number of Processes in an RDP Session
+
+A machine learning job has detected unusually high number of processes started in a single RDP session. Executing a large number of processes remotely on other machines can be an indicator of lateral movement activity.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-12h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/lmd
+* https://www.elastic.co/blog/detecting-lateral-movement-activity-a-new-kibana-integration
+* https://www.elastic.co/blog/remote-desktop-protocol-connections-elastic-security
+
+*Tags*: 
+
+* Use Case: Lateral Movement Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Lateral Movement Detection integration assets to be installed, as well as file and Windows RDP process events collected by the Elastic Defend integration.  
+
+
+*Lateral Movement Detection Setup*
+
+The Lateral Movement Detection integration detects lateral movement activity by identifying abnormalities in file and Windows RDP events. Anomalies are detected using Elastic's Anomaly Detection feature.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Lateral Movement Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows RDP process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Lateral Movement Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Lateral Movement Detection and select the integration to see more details about it.
+- Under Settings, click Install Lateral Movement Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Lateral Movement Detection, you'll need to enable the corresponding Anomaly Detection jobs.
+- Before enabling the Anomaly Detection jobs, confirm that the Pivot Transform asset is installed and actively gathering data in the destination index `ml-rdp-lmd`.
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your transformed RDP process data i.e.`ml-rdp-lmd`.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/lmd/kibana/ml_module/lmd-ml.json[this] configuration file, you will see a card for Lateral Movement Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-remote-file-transfers.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-remote-file-transfers.asciidoc
new file mode 100644
index 0000000000..a5e75dd495
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-remote-file-transfers.asciidoc
@@ -0,0 +1,91 @@
+[[spike-in-remote-file-transfers]]
+=== Spike in Remote File Transfers
+
+A machine learning job has detected an abnormal volume of remote files shared on the host indicating potential lateral movement activity. One of the primary goals of attackers after gaining access to a network is to locate and exfiltrate valuable information. Attackers might perform multiple small transfers to match normal egress activity in the network, to evade detection.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-90m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/lmd
+* https://www.elastic.co/blog/detecting-lateral-movement-activity-a-new-kibana-integration
+* https://www.elastic.co/blog/remote-desktop-protocol-connections-elastic-security
+
+*Tags*: 
+
+* Use Case: Lateral Movement Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Lateral Movement Detection integration assets to be installed, as well as file and Windows RDP process events collected by the Elastic Defend integration.  
+
+
+*Lateral Movement Detection Setup*
+
+The Lateral Movement Detection integration detects lateral movement activity by identifying abnormalities in file and Windows RDP events. Anomalies are detected using Elastic's Anomaly Detection feature.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Lateral Movement Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- File events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Lateral Movement Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Lateral Movement Detection and select the integration to see more details about it.
+- Under Settings, click Install Lateral Movement Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Lateral Movement Detection, you'll need to enable the corresponding Anomaly Detection jobs.
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your file events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/lmd/kibana/ml_module/lmd-ml.json[this] configuration file, you will see a card for Lateral Movement Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/spike-in-successful-logon-events-from-a-source-ip.asciidoc b/docs/detections/prebuilt-rules/rule-details/spike-in-successful-logon-events-from-a-source-ip.asciidoc
new file mode 100644
index 0000000000..50ab860ea3
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/spike-in-successful-logon-events-from-a-source-ip.asciidoc
@@ -0,0 +1,107 @@
+[[spike-in-successful-logon-events-from-a-source-ip]]
+=== Spike in Successful Logon Events from a Source IP
+
+A machine learning job found an unusually large spike in successful authentication events from a particular source IP address. This can be due to password spraying, user enumeration or brute force activity.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Credential Access
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+
+*Version*: 104
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Spike in Successful Logon Events from a Source IP*
+
+
+This rule uses a machine learning job to detect a substantial spike in successful authentication events. This could indicate post-exploitation activities that aim to test which hosts, services, and other resources the attacker can access with the compromised credentials.
+
+
+*Possible investigation steps*
+
+
+- Identify the specifics of the involved assets, such as role, criticality, and associated users.
+- Check if the authentication comes from different sources.
+- Use the historical data available to determine if the same behavior happened in the past.
+- Investigate other alerts associated with the involved users during the past 48 hours.
+- Check whether the involved credentials are used in automation or scheduled tasks.
+- If this activity is suspicious, contact the account owner and confirm whether they are aware of it.
+
+
+*False positive analysis*
+
+
+- Understand the context of the authentications by contacting the asset owners. If this activity is related to a new business process or newly implemented (approved) technology, consider adding exceptions — preferably with a combination of user and source conditions.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Brute Force
+** ID: T1110
+** Reference URL: https://attack.mitre.org/techniques/T1110/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
+* Sub-technique:
+** Name: Domain Accounts
+** ID: T1078.002
+** Reference URL: https://attack.mitre.org/techniques/T1078/002/
+* Sub-technique:
+** Name: Local Accounts
+** ID: T1078.003
+** Reference URL: https://attack.mitre.org/techniques/T1078/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/ssh-authorized-keys-file-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/ssh-authorized-keys-file-modification.asciidoc
index 1832dd4ebb..7fef6c953a 100644
--- a/docs/detections/prebuilt-rules/rule-details/ssh-authorized-keys-file-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/ssh-authorized-keys-file-modification.asciidoc
@@ -3,9 +3,9 @@
 
 The Secure Shell (SSH) authorized_keys file specifies which users are allowed to log into a server using public key authentication. Adversaries may modify it to maintain persistence on a victim host by adding their own public key(s).
 
-*Rule type*: query
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,49 +14,58 @@ The Secure Shell (SSH) authorized_keys file specifies which users are allowed to
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* macOS
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 100 (<<ssh-authorized-keys-file-modification-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Persistence
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 205
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.category:file and event.type:(change or creation) and
-file.name:("authorized_keys" or "authorized_keys2") and not
-process.executable:
-(/Library/Developer/CommandLineTools/usr/bin/git or
-/usr/local/Cellar/maven/*/libexec/bin/mvn or
-/Library/Java/JavaVirtualMachines/jdk*.jdk/Contents/Home/bin/java or
-/usr/bin/vim or /usr/local/Cellar/coreutils/*/bin/gcat
-or /usr/bin/bsdtar or /usr/bin/nautilus or
-/usr/bin/scp or /usr/bin/touch or
-/var/lib/docker/* or /usr/bin/google_guest_agent)
-----------------------------------
+ file.name:("authorized_keys" or "authorized_keys2" or "/etc/ssh/sshd_config" or "/root/.ssh") and
+ not process.executable:
+             (/Library/Developer/CommandLineTools/usr/bin/git or
+              /usr/local/Cellar/maven/*/libexec/bin/mvn or
+              /Library/Java/JavaVirtualMachines/jdk*.jdk/Contents/Home/bin/java or
+              /usr/bin/vim or
+              /usr/local/Cellar/coreutils/*/bin/gcat or
+              /usr/bin/bsdtar or
+              /usr/bin/nautilus or
+              /usr/bin/scp or
+              /usr/bin/touch or
+              /var/lib/docker/* or
+              /usr/bin/google_guest_agent or 
+              /opt/jc/bin/jumpcloud-agent or 
+              /opt/puppetlabs/puppet/bin/puppet or
+              /usr/bin/chef-client
+)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -68,44 +77,27 @@ or /usr/bin/bsdtar or /usr/bin/nautilus or
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[ssh-authorized-keys-file-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and event.type:(change or creation) and
-file.name:("authorized_keys" or "authorized_keys2") and not
-process.executable:
-(/Library/Developer/CommandLineTools/usr/bin/git or
-/usr/local/Cellar/maven/*/libexec/bin/mvn or
-/Library/Java/JavaVirtualMachines/jdk*.jdk/Contents/Home/bin/java or
-/usr/bin/vim or /usr/local/Cellar/coreutils/*/bin/gcat
-or /usr/bin/bsdtar or /usr/bin/nautilus
-or /usr/bin/scp or /usr/bin/touch or
-/var/lib/docker/* or /usr/bin/google_guest_agent)
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.3.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and event.type:(change or creation) and
-file.name:("authorized_keys" or "authorized_keys2") and not
-process.executable:
-(/Library/Developer/CommandLineTools/usr/bin/git or
-/usr/local/Cellar/maven/*/libexec/bin/mvn or
-/Library/Java/JavaVirtualMachines/jdk*.jdk/Contents/Home/bin/java or
-/usr/bin/vim or /usr/local/Cellar/coreutils/*/bin/gcat
-or /usr/bin/bsdtar or /usr/bin/nautilus
-or /usr/bin/scp or /usr/bin/touch or
-/var/lib/docker/*)
-----------------------------------
-
+* Sub-technique:
+** Name: SSH Authorized Keys
+** ID: T1098.004
+** Reference URL: https://attack.mitre.org/techniques/T1098/004/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Service Session Hijacking
+** ID: T1563
+** Reference URL: https://attack.mitre.org/techniques/T1563/
+* Sub-technique:
+** Name: SSH Hijacking
+** ID: T1563.001
+** Reference URL: https://attack.mitre.org/techniques/T1563/001/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SSH
+** ID: T1021.004
+** Reference URL: https://attack.mitre.org/techniques/T1021/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/ssh-authorized-keys-file-modified-inside-a-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/ssh-authorized-keys-file-modified-inside-a-container.asciidoc
new file mode 100644
index 0000000000..c3aa161a67
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/ssh-authorized-keys-file-modified-inside-a-container.asciidoc
@@ -0,0 +1,85 @@
+[[ssh-authorized-keys-file-modified-inside-a-container]]
+=== SSH Authorized Keys File Modified Inside a Container
+
+This rule detects the creation or modification of an authorized_keys or sshd_config file inside a container. The Secure Shell (SSH) authorized_keys file specifies which users are allowed to log into a server using public key authentication. Adversaries may modify it to maintain persistence on a victim host by adding their own public key(s). Unexpected and unauthorized SSH usage inside a container can be an indicator of compromise and should be investigated.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Lateral Movement
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where container.id:"*" and
+  event.type in ("change", "creation") and file.name: ("authorized_keys", "authorized_keys2", "sshd_config")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Account Manipulation
+** ID: T1098
+** Reference URL: https://attack.mitre.org/techniques/T1098/
+* Sub-technique:
+** Name: SSH Authorized Keys
+** ID: T1098.004
+** Reference URL: https://attack.mitre.org/techniques/T1098/004/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Service Session Hijacking
+** ID: T1563
+** Reference URL: https://attack.mitre.org/techniques/T1563/
+* Sub-technique:
+** Name: SSH Hijacking
+** ID: T1563.001
+** Reference URL: https://attack.mitre.org/techniques/T1563/001/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SSH
+** ID: T1021.004
+** Reference URL: https://attack.mitre.org/techniques/T1021/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/ssh-connection-established-inside-a-running-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/ssh-connection-established-inside-a-running-container.asciidoc
new file mode 100644
index 0000000000..4f871d9fb7
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/ssh-connection-established-inside-a-running-container.asciidoc
@@ -0,0 +1,83 @@
+[[ssh-connection-established-inside-a-running-container]]
+=== SSH Connection Established Inside A Running Container
+
+This rule detects an incoming SSH connection established inside a running container. Running an ssh daemon inside a container should be avoided and monitored closely if necessary. If an attacker gains valid credentials they can use it to gain initial access or establish persistence within a compromised environment.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://microsoft.github.io/Threat-Matrix-for-Kubernetes/techniques/SSH%20server%20running%20inside%20container/
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Lateral Movement
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where container.id: "*" and event.type == "start" and 
+
+/* use of sshd to enter a container*/
+process.entry_leader.entry_meta.type: "sshd"  and 
+
+/* process is the initial process run in a container or start of a new session*/
+(process.entry_leader.same_as_process== true or process.session_leader.same_as_process== true) and 
+
+/* interactive process*/
+process.interactive== true
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: External Remote Services
+** ID: T1133
+** Reference URL: https://attack.mitre.org/techniques/T1133/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SSH
+** ID: T1021.004
+** Reference URL: https://attack.mitre.org/techniques/T1021/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/ssh-process-launched-from-inside-a-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/ssh-process-launched-from-inside-a-container.asciidoc
new file mode 100644
index 0000000000..0d6ea8466d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/ssh-process-launched-from-inside-a-container.asciidoc
@@ -0,0 +1,77 @@
+[[ssh-process-launched-from-inside-a-container]]
+=== SSH Process Launched From Inside A Container
+
+This rule detects an SSH or SSHD process executed from inside a container. This includes both the client ssh binary and server ssh daemon process. SSH usage inside a container should be avoided and monitored closely when necessary. With valid credentials an attacker may move laterally to other containers or to the underlying host through container breakout. They may also use valid SSH credentials as a persistence mechanism.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://microsoft.github.io/Threat-Matrix-for-Kubernetes/techniques/SSH%20server%20running%20inside%20container/
+* https://www.blackhillsinfosec.com/sshazam-hide-your-c2-inside-of-ssh/
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Persistence
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where container.id: "*" and event.type== "start" and
+event.action in ("fork", "exec") and event.action != "end" and 
+process.name: ("sshd", "ssh", "autossh")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SSH
+** ID: T1021.004
+** Reference URL: https://attack.mitre.org/techniques/T1021/004/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: External Remote Services
+** ID: T1133
+** Reference URL: https://attack.mitre.org/techniques/T1133/
diff --git a/docs/detections/prebuilt-rules/rule-details/startup-folder-persistence-via-unsigned-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/startup-folder-persistence-via-unsigned-process.asciidoc
index cd20dced90..e881b6f301 100644
--- a/docs/detections/prebuilt-rules/rule-details/startup-folder-persistence-via-unsigned-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/startup-folder-persistence-via-unsigned-process.asciidoc
@@ -5,93 +5,99 @@ Identifies files written or modified in the startup folder by unsigned processes
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.file-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<startup-folder-persistence-via-unsigned-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Startup Folder Persistence via Unsigned Process
+*Triage and analysis*
+
 
-The Windows Startup folder is a special folder in Windows. Programs added to this folder are executed during account
-logon, without user interaction, providing an excellent way for attackers to maintain persistence.
+
+*Investigating Startup Folder Persistence via Unsigned Process*
+
+
+The Windows Startup folder is a special folder in Windows. Programs added to this folder are executed during account logon, without user interaction, providing an excellent way for attackers to maintain persistence.
 
 This rule looks for unsigned processes writing to the Startup folder locations.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate
-software installations.
+- Validate if the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- There is a high possibility of benign legitimate programs being added to Startup folders. This activity could be based on new software installations, patches, or any kind of network administrator related activity. Before undertaking further investigation, verify that this activity is not benign.
 
-- There is a high possibility of benign legitimate programs being added to Startup folders. This activity could be based
-on new software installations, patches, or any kind of network administrator related activity. Before undertaking further
-investigation, verify that this activity is not benign.
 
-### Related rules
+*Related rules*
+
 
 - Suspicious Startup Shell Folder Modification - c8b150f0-0164-475b-a75e-74b47800a9ff
 - Persistent Scripts in the Startup Directory - f7c4dc5a-a58d-491d-9f14-9b66507121c0
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -99,43 +105,35 @@ investigation, verify that this activity is not benign.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=5s [process
-where event.type == "start" and process.code_signature.trusted ==
-false and /* suspicious paths can be added here */
-process.executable : ("C:\\Users\\*.exe",
-"C:\\ProgramData\\*.exe",
-"C:\\Windows\\Temp\\*.exe",
-"C:\\Windows\\Tasks\\*.exe",
-"C:\\Intel\\*.exe", "C:\\PerfLogs\\*.exe")
-] [file where event.type != "deletion" and user.domain != "NT
-AUTHORITY" and file.path :
-("C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start
-Menu\\Programs\\Startup\\*",
-"C:\\ProgramData\\Microsoft\\Windows\\Start
-Menu\\Programs\\StartUp\\*") ]
+[source, js]
 ----------------------------------
+sequence by host.id, process.entity_id with maxspan=5s
+  [process where host.os.type == "windows" and event.type == "start" and process.code_signature.trusted == false and
+  /* suspicious paths can be added here  */
+   process.executable : ("C:\\Users\\*.exe",
+                         "C:\\ProgramData\\*.exe",
+                         "C:\\Windows\\Temp\\*.exe",
+                         "C:\\Windows\\Tasks\\*.exe",
+                         "C:\\Intel\\*.exe",
+                         "C:\\PerfLogs\\*.exe")
+   ]
+   [file where host.os.type == "windows" and event.type != "deletion" and user.domain != "NT AUTHORITY" and
+    file.path : ("C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\Startup\\*",
+                 "C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\StartUp\\*")
+   ]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -147,43 +145,19 @@ Menu\\Programs\\StartUp\\*") ]
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[startup-folder-persistence-via-unsigned-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=5s [process
-where event.type in ("start", "process_started") and
-process.code_signature.trusted == false and /* suspicious paths can
-be added here */ process.executable : ("C:\\Users\\*.exe",
-"C:\\ProgramData\\*.exe",
-"C:\\Windows\\Temp\\*.exe",
-"C:\\Windows\\Tasks\\*.exe",
-"C:\\Intel\\*.exe", "C:\\PerfLogs\\*.exe")
-] [file where event.type != "deletion" and user.domain != "NT
-AUTHORITY" and file.path :
-("C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start
-Menu\\Programs\\Startup\\*",
-"C:\\ProgramData\\Microsoft\\Windows\\Start
-Menu\\Programs\\StartUp\\*") ]
-----------------------------------
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Registry Run Keys / Startup Folder
+** ID: T1547.001
+** Reference URL: https://attack.mitre.org/techniques/T1547/001/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/startup-logon-script-added-to-group-policy-object.asciidoc b/docs/detections/prebuilt-rules/rule-details/startup-logon-script-added-to-group-policy-object.asciidoc
index a7e189305a..2867d3cafe 100644
--- a/docs/detections/prebuilt-rules/rule-details/startup-logon-script-added-to-group-policy-object.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/startup-logon-script-added-to-group-policy-object.asciidoc
@@ -5,113 +5,150 @@ Detects the modification of Group Policy Objects (GPO) to add a startup/logon sc
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0025_windows_audit_directory_service_changes.md
 * https://github.com/atc-project/atc-data/blob/f2bbb51ecf68e2c9f488e3c70dcdd3df51d2a46b/docs/Logging_Policies/LP_0029_windows_audit_detailed_file_share.md
 * https://labs.f-secure.com/tools/sharpgpoabuse
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Active Directory
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
+
+*Version*: 109
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Active Directory
-* Investigation Guide
 
-*Version*: 102 (<<startup-logon-script-added-to-group-policy-object-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 8.0.0
+==== Investigation guide
 
-*Last modified ({stack} release)*: 8.6.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Triage and analysis*
 
-==== Potential false positives
 
-Legitimate Administrative Activity
 
-==== Investigation guide
+*Investigating Startup/Logon Script added to Group Policy Object*
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+Group Policy Objects (GPOs) can be used by attackers to instruct arbitrarily large groups of clients to execute specified commands at startup, logon, shutdown, and logoff. This is done by creating or modifying the `scripts.ini` or `psscripts.ini` files. The scripts are stored in the following paths:
+  - `<GPOPath>\Machine\Scripts\`
+  - `<GPOPath>\User\Scripts\`
 
-### Investigating Scheduled Task Execution at Scale via GPO
 
-Group Policy Objects (GPOs) can be used by attackers to instruct arbitrarily large groups of
-clients to execute specified commands at startup, logon, shutdown, and logoff. This is done by creating or modifying the
-`scripts.ini` or `psscripts.ini` files. The scripts are stored in the following path: `<GPOPath>\Machine\Scripts\`,
-`<GPOPath>\User\Scripts\`
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- This attack abuses a legitimate mechanism of Active Directory, so it is important to determine whether the activity
-is legitimate and the administrator is authorized to perform this operation.
-- Retrieve the contents of the `ScheduledTasks.xml` file, and check the `<Command>` and `<Arguments>` XML tags for any
-potentially malicious commands or binaries.
+- This attack abuses a legitimate mechanism of Active Directory, so it is important to determine whether the activity is legitimate and the administrator is authorized to perform this operation.
+- Retrieve the contents of the `ScheduledTasks.xml` file, and check the `<Command>` and `<Arguments>` XML tags for any potentially malicious commands or binaries.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Scope which objects may be compromised by retrieving information about which objects are controlled by the GPO.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - Verify if the execution is legitimately authorized and executed under a change management process.
 
-### Related rules
+
+*Related rules*
+
 
 - Group Policy Abuse for Privilege Addition - b9554892-5e0e-424b-83a0-5aef95aa43bf
 - Scheduled Task Execution at Scale via GPO - 15a8ba77-1c13-4274-88fe-6bd14133861e
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - The investigation and containment must be performed in every computer controlled by the GPO, where necessary.
 - Remove the script from the GPO.
 - Check if other GPOs have suspicious scripts attached.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Detailed File Share' audit policy must be configured (Success Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+Object Access >
+Audit Detailed File Share (Success,Failure)
+```
+
+The 'Audit Directory Service Changes' audit policy must be configured (Success Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Changes (Success,Failure)
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-( event.code:5136 and
-winlog.event_data.AttributeLDAPDisplayName:(gPCMachineExtensionNames
-or gPCUserExtensionNames) and winlog.event_data.AttributeValue:(*42
-B5FAAE-6536-11D2-AE5A-0000F87571E3* and
-(*40B66650-4972-11D1-A7CA-0000F87571E3* or
-*40B6664F-4972-11D1-A7CA-0000F87571E3*)) ) or ( event.code:5145 and
-winlog.event_data.ShareName:\\\\*\\SYSVOL and
-winlog.event_data.RelativeTargetName:(*\\scripts.ini or
-*\\psscripts.ini) and (message:WriteData or
-winlog.event_data.AccessList:*%%4417*) )
+[source, js]
 ----------------------------------
+(
+ event.code:5136 and winlog.event_data.AttributeLDAPDisplayName:(gPCMachineExtensionNames or gPCUserExtensionNames) and
+   winlog.event_data.AttributeValue:(*42B5FAAE-6536-11D2-AE5A-0000F87571E3* and
+                                      (*40B66650-4972-11D1-A7CA-0000F87571E3* or *40B6664F-4972-11D1-A7CA-0000F87571E3*))
+)
+or
+(
+ event.code:5145 and winlog.event_data.ShareName:\\\\*\\SYSVOL and
+   winlog.event_data.RelativeTargetName:(*\\scripts.ini or *\\psscripts.ini) and
+   (message:WriteData or winlog.event_data.AccessList:*%%4417*)
+)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -120,28 +157,14 @@ winlog.event_data.AccessList:*%%4417*) )
 ** ID: TA0004
 ** Reference URL: https://attack.mitre.org/tactics/TA0004/
 * Technique:
+** Name: Domain Policy Modification
+** ID: T1484
+** Reference URL: https://attack.mitre.org/techniques/T1484/
+* Sub-technique:
+** Name: Group Policy Modification
+** ID: T1484.001
+** Reference URL: https://attack.mitre.org/techniques/T1484/001/
+* Technique:
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[startup-logon-script-added-to-group-policy-object-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/startup-or-run-key-registry-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/startup-or-run-key-registry-modification.asciidoc
index f0b1df5ede..c95f526618 100644
--- a/docs/detections/prebuilt-rules/rule-details/startup-or-run-key-registry-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/startup-or-run-key-registry-modification.asciidoc
@@ -5,96 +5,99 @@ Identifies run key or startup key registry modifications. In order to survive re
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<startup-or-run-key-registry-modification-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Startup or Run Key Registry Modification
+*Triage and analysis*
+
 
-Adversaries may achieve persistence by referencing a program with a registry run key. Adding an entry to the run keys
-in the registry will cause the program referenced to be executed when a user logs in. These programs will executed
-under the context of the user and will have the account's permissions. This rule looks for this behavior by monitoring
-a range of registry run keys.
+
+*Investigating Startup or Run Key Registry Modification*
+
+
+Adversaries may achieve persistence by referencing a program with a registry run key. Adding an entry to the run keys in the registry will cause the program referenced to be executed when a user logs in. These programs will executed under the context of the user and will have the account's permissions. This rule looks for this behavior by monitoring a range of registry run keys.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate
-software installations.
+- Validate if the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
 
 
-### False positive analysis
 
-- There is a high possibility of benign legitimate programs being added to registry run keys. This activity could be
-based on new software installations, patches, or any kind of network administrator related activity. Before undertaking
-further investigation, verify that this activity is not benign.
+*False positive analysis*
+
+
+- There is a high possibility of benign legitimate programs being added to registry run keys. This activity could be based on new software installations, patches, or any kind of network administrator related activity. Before undertaking further investigation, verify that this activity is not benign.
+
+
+*Related rules*
 
-### Related rules
 
 - Suspicious Startup Shell Folder Modification - c8b150f0-0164-475b-a75e-74b47800a9ff
 - Persistent Scripts in the Startup Directory - f7c4dc5a-a58d-491d-9f14-9b66507121c0
 - Startup Folder Persistence via Unsigned Process - 2fba96c0-ade5-4bce-b92f-a5df2509da3f
 - Startup Persistence by a Suspicious Process - 440e2db4-bc7f-4c96-a068-65b78da59bde
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -102,57 +105,208 @@ further investigation, verify that this activity is not benign.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.data.strings != null and registry.path : (
-/* Machine Hive */
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explore
-r\\Run\\*", "HKLM\\Software\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell\\*", /* Users Hive */
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\
-\*", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion
-\\RunOnceEx\\*", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\Cu
-rrentVersion\\Policies\\Explorer\\Run\\*",
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell\\*" ) and /* add common
-legitimate changes without being too restrictive as this is one of the
-most abused AESPs */ not registry.data.strings : "ctfmon.exe /n" and
-not (registry.value : "Application Restart #*" and process.name :
-"csrss.exe") and user.id not in ("S-1-5-18", "S-1-5-19", "S-1-5-20")
-and not registry.data.strings : ("?:\\Program Files\\*.exe",
-"?:\\Program Files (x86)\\*.exe") and not process.executable :
-("?:\\Windows\\System32\\msiexec.exe",
-"?:\\Windows\\SysWOW64\\msiexec.exe") and not (process.name :
-"OneDriveSetup.exe" and registry.value : ("Delete Cached
-Standalone Update Binary", "Delete Cached Update Binary", "amd64",
-"Uninstall *") and registry.data.strings :
-"?:\\Windows\\system32\\cmd.exe /q /c *
-\"?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\*\"")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and registry.data.strings != null and
+ registry.path : (
+     /* Machine Hive */
+     "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
+     "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\\*",
+     "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\*",
+     "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\*",
+     "HKLM\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Shell\\*",
+     /* Users Hive */
+     "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
+     "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\\*",
+     "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\*",
+     "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\*",
+     "HKEY_USERS\\*\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Shell\\*"
+     ) and
+  /* add common legitimate changes without being too restrictive as this is one of the most abused AESPs */
+  not registry.data.strings : "ctfmon.exe /n" and
+  not (registry.value : "Application Restart #*" and process.name : "csrss.exe") and
+  not user.id : ("S-1-5-18", "S-1-5-19", "S-1-5-20") and
+  not registry.data.strings : ("?:\\Program Files\\*.exe", "?:\\Program Files (x86)\\*.exe") and
+  not process.executable : ("?:\\Windows\\System32\\msiexec.exe", "?:\\Windows\\SysWOW64\\msiexec.exe") and
+  not (
+    /* Logitech G Hub */
+    (
+      process.code_signature.trusted == true and process.code_signature.subject_name == "Logitech Inc" and
+      (
+        process.name : "lghub_agent.exe" and registry.data.strings : (
+          "\"?:\\Program Files\\LGHUB\\lghub.exe\" --background",
+          "\"?:\\Program Files\\LGHUB\\system_tray\\lghub_system_tray.exe\" --minimized"
+        )
+      ) or
+      (
+        process.name : "LogiBolt.exe" and registry.data.strings : (
+          "?:\\Program Files\\Logi\\LogiBolt\\LogiBolt.exe --startup",
+          "?:\\Users\\*\\AppData\\Local\\Logi\\LogiBolt\\LogiBolt.exe --startup"
+        )
+      )
+    ) or
+
+    /* Google Drive File Stream, Chrome, and Google Update */
+    (
+      process.code_signature.trusted == true and process.code_signature.subject_name == "Google LLC" and
+      (
+        process.name : "GoogleDriveFS.exe" and registry.data.strings : (
+        "\"?:\\Program Files\\Google\\Drive File Stream\\*\\GoogleDriveFS.exe\" --startup_mode"
+        ) or
+
+        process.name : "chrome.exe" and registry.data.strings : (
+          "\"?:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\" --no-startup-window /prefetch:5",
+          "\"?:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe\" --no-startup-window /prefetch:5"
+        ) or
+
+        process.name : "GoogleUpdate.exe" and registry.data.strings : (
+          "\"?:\\Users\\*\\AppData\\Local\\Google\\Update\\*\\GoogleUpdateCore.exe\""
+        )
+      )
+    ) or
+
+    /* MS Programs */
+    (
+      process.code_signature.trusted == true and process.code_signature.subject_name in ("Microsoft Windows", "Microsoft Corporation") and
+      (
+        process.name : "msedge.exe" and registry.data.strings : (
+          "\"?:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe\" --no-startup-window --win-session-start /prefetch:5",
+          "\"C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe\" --win-session-start",
+          "\"C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe\" --no-startup-window --win-session-start"
+        ) or
+
+        process.name : ("Update.exe", "Teams.exe") and registry.data.strings : (
+          "?:\\Users\\*\\AppData\\Local\\Microsoft\\Teams\\Update.exe --processStart \"Teams.exe\" --process-start-args \"--system-initiated\"",
+          "?:\\ProgramData\\*\\Microsoft\\Teams\\Update.exe --processStart \"Teams.exe\" --process-start-args \"--system-initiated\""
+        ) or
+
+        process.name : "OneDriveStandaloneUpdater.exe" and registry.data.strings : (
+          "?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\*\\Microsoft.SharePoint.exe"
+        ) or
+
+        process.name : "OneDriveSetup.exe" and
+          registry.data.strings : (
+            "?:\\Windows\\system32\\cmd.exe /q /c * \"?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\*\"",
+            "?:\\Program Files (x86)\\Microsoft OneDrive\\OneDrive.exe /background*",
+            "\"?:\\Program Files (x86)\\Microsoft OneDrive\\OneDrive.exe\" /background*",
+            "?:\\Program Files\\Microsoft OneDrive\\OneDrive.exe /background *",
+            "?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\??.???.????.????\\Microsoft.SharePoint.exe"
+          ) or
+        
+        process.name : "OneDrive.exe" and registry.data.strings : (
+          "\"?:\\Program Files\\Microsoft OneDrive\\OneDrive.exe\" /background",
+          "\"?:\\Program Files (x86)\\Microsoft OneDrive\\OneDrive.exe\" /background",
+          "\"?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\OneDrive.exe\" /background"
+        ) or
+        
+        process.name : "Microsoft.SharePoint.exe" and registry.data.strings : (
+          "?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\??.???.????.????\\Microsoft.SharePoint.exe"
+        ) or
+        
+        process.name : "MicrosoftEdgeUpdate.exe" and registry.data.strings : (
+          "\"?:\\Users\\Expedient\\AppData\\Local\\Microsoft\\EdgeUpdate\\*\\MicrosoftEdgeUpdateCore.exe\""
+        ) or
+        
+        process.executable : "?:\\Program Files (x86)\\Microsoft\\EdgeWebView\\Application\\*\\Installer\\setup.exe" and
+        registry.data.strings : (
+          "\"?:\\Program Files (x86)\\Microsoft\\EdgeWebView\\Application\\*\\Installer\\setup.exe\" --msedgewebview --delete-old-versions --system-level --verbose-logging --on-logon"
+        )
+      )
+    ) or
+
+    /* Slack */
+    (
+      process.code_signature.trusted == true and process.code_signature.subject_name in (
+       "Slack Technologies, Inc.", "Slack Technologies, LLC"
+      ) and process.name : "slack.exe" and registry.data.strings : (
+        "\"?:\\Users\\*\\AppData\\Local\\slack\\slack.exe\" --process-start-args --startup",
+        "\"?:\\ProgramData\\*\\slack\\slack.exe\" --process-start-args --startup",
+        "\"?:\\Program Files\\Slack\\slack.exe\" --process-start-args --startup"
+      )
+    ) or
+
+    /* Cisco */
+    (
+      process.code_signature.trusted == true and process.code_signature.subject_name in ("Cisco WebEx LLC", "Cisco Systems, Inc.") and
+      (
+        process.name : "WebexHost.exe" and registry.data.strings : (
+          "\"?:\\Users\\*\\AppData\\Local\\WebEx\\WebexHost.exe\" /daemon /runFrom=autorun"
+        )
+      ) or
+      (
+        process.name : "CiscoJabber.exe" and registry.data.strings : (
+          "\"?:\\Program Files (x86)\\Cisco Systems\\Cisco Jabber\\CiscoJabber.exe\" /min"
+        )
+      )
+    ) or
+
+    /* Loom */
+    (
+      process.code_signature.trusted == true and process.code_signature.subject_name == "Loom, Inc." and
+      process.name : "Loom.exe" and registry.data.strings : (
+        "?:\\Users\\*\\AppData\\Local\\Programs\\Loom\\Loom.exe --process-start-args \"--loomHidden\""
+      )
+    ) or
+
+    /* Adobe */
+    (
+      process.code_signature.trusted == true and process.code_signature.subject_name == "Adobe Inc." and
+      process.name : ("Acrobat.exe", "FlashUtil32_*_Plugin.exe") and registry.data.strings : (
+        "\"?:\\Program Files\\Adobe\\Acrobat DC\\Acrobat\\AdobeCollabSync.exe\"",
+        "\"?:\\Program Files (x86)\\Adobe\\Acrobat DC\\Acrobat\\AdobeCollabSync.exe\"",
+        "?:\\WINDOWS\\SysWOW64\\Macromed\\Flash\\FlashUtil32_*_Plugin.exe -update plugin"
+      )
+    ) or
+
+    /* CCleaner */
+    (
+      process.code_signature.trusted == true and process.code_signature.subject_name == "PIRIFORM SOFTWARE LIMITED" and
+      process.name : ("CCleanerBrowser.exe", "CCleaner64.exe") and registry.data.strings : (
+        "\"C:\\Program Files (x86)\\CCleaner Browser\\Application\\CCleanerBrowser.exe\" --check-run=src=logon --auto-launch-at-startup --profile-directory=\"Default\"",
+        "\"C:\\Program Files\\CCleaner\\CCleaner64.exe\" /MONITOR"
+      )
+    ) or
+
+    /* Opera */
+    (
+      process.code_signature.trusted == true and process.code_signature.subject_name == "Opera Norway AS" and
+      process.name : "opera.exe" and registry.data.strings : (
+        "?:\\Users\\*\\AppData\\Local\\Programs\\Opera\\launcher.exe",
+        "?:\\Users\\*\\AppData\\Local\\Programs\\Opera GX\\launcher.exe"
+      )
+    ) or
+
+    /* Avast */
+    (
+      process.code_signature.trusted == true and process.code_signature.subject_name == "Avast Software s.r.o." and
+      process.name : "AvastBrowser.exe" and registry.data.strings : (
+        "\"?:\\Users\\*\\AppData\\Local\\AVAST Software\\Browser\\Application\\AvastBrowser.exe\" --check-run=src=logon --auto-launch-at-startup*",
+        "\"?:\\Program Files (x86)\\AVAST Software\\Browser\\Application\\AvastBrowser.exe\" --check-run=src=logon --auto-launch-at-startup*",
+        ""
+      )
+    ) or
+
+    /* Grammarly */
+    (
+      process.code_signature.trusted == true and process.code_signature.subject_name == "Grammarly, Inc." and
+      process.name : "GrammarlyInstaller.exe" and registry.data.strings : (
+        "?:\\Users\\*\\AppData\\Local\\Grammarly\\DesktopIntegrations\\Grammarly.Desktop.exe"
+      )
+    )
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -164,101 +318,7 @@ Standalone Update Binary", "Delete Cached Update Binary", "amd64",
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[startup-or-run-key-registry-modification-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.data.strings != null and registry.path : (
-/* Machine Hive */
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explore
-r\\Run\\*", "HKLM\\Software\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell\\*", /* Users Hive */
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\
-\*", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersio
-n\\RunOnceEx\\*", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\C
-urrentVersion\\Policies\\Explorer\\Run\\*",
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell\\*" ) and /* add common
-legitimate changes without being too restrictive as this is one of the
-most abused AESPs */ not registry.data.strings : "ctfmon.exe /n" and
-not (registry.value : "Application Restart #*" and process.name :
-"csrss.exe") and user.id not in ("S-1-5-18", "S-1-5-19", "S-1-5-20")
-and not registry.data.strings : ("?:\\Program Files\\*.exe",
-"?:\\Program Files (x86)\\*.exe") and not process.executable :
-("?:\\Windows\\System32\\msiexec.exe",
-"?:\\Windows\\SysWOW64\\msiexec.exe") and not (process.name :
-"OneDriveSetup.exe" and registry.value : ("Delete Cached
-Standalone Update Binary", "Delete Cached Update Binary", "amd64",
-"Uninstall *") and registry.data.strings :
-"?:\\Windows\\system32\\cmd.exe /q /c *
-\"?:\\Users\\*\\AppData\\Local\\Microsoft\\OneDrive\\*\"")
-----------------------------------
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 8 (8.3.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* uncomment length once stable */ registry where /*
-length(registry.data.strings) > 0 and */ registry.path : ( /*
-Machine Hive */
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User
-Shell Folders\\*",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell
-Folders\\*", "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion
-\\Policies\\Explorer\\Run\\*",
-"HKLM\\Software\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell\\*", /* Users Hive */
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce\
-\*", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersio
-n\\RunOnceEx\\*", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\
-CurrentVersion\\Explorer\\User Shell Folders\\*", "HKEY_USERS\\*
-\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell
-Folders\\*", "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\Curre
-ntVersion\\Policies\\Explorer\\Run\\*",
-"HKEY_USERS\\*\\Software\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell\\*" ) and /* add here
-common legit changes without making too restrictive as this is one of
-the most abused AESPs */ not registry.data.strings : "ctfmon.exe /n"
-and not (registry.value : "Application Restart #*" and process.name
-: "csrss.exe") and user.domain != "NT AUTHORITY" and not
-registry.data.strings : ("C:\\Program Files\\*.exe", "C:\\Program
-Files (x86)\\*.exe") and not process.executable :
-("C:\\Windows\\System32\\msiexec.exe",
-"C:\\Windows\\SysWOW64\\msiexec.exe")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Registry Run Keys / Startup Folder
+** ID: T1547.001
+** Reference URL: https://attack.mitre.org/techniques/T1547/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/startup-persistence-by-a-suspicious-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/startup-persistence-by-a-suspicious-process.asciidoc
index 89f609a908..260c3e51ad 100644
--- a/docs/detections/prebuilt-rules/rule-details/startup-persistence-by-a-suspicious-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/startup-persistence-by-a-suspicious-process.asciidoc
@@ -5,98 +5,104 @@ Identifies files written to or modified in the startup folder by commonly abused
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/security-labs/hunting-for-persistence-using-elastic-security-part-1
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
-
-*Version*: 102 (<<startup-persistence-by-a-suspicious-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Startup Persistence by a Suspicious Process
+*Triage and analysis*
 
-The Windows Startup folder is a special folder in Windows. Programs added to this folder are executed during account
-logon, without user interaction, providing an excellent way for attackers to maintain persistence.
+
+
+*Investigating Startup Persistence by a Suspicious Process*
+
+
+The Windows Startup folder is a special folder in Windows. Programs added to this folder are executed during account logon, without user interaction, providing an excellent way for attackers to maintain persistence.
 
 This rule monitors for commonly abused processes writing to the Startup folder locations.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate
-software installations.
+- Validate if the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
+
+
+- Administrators may add programs to this mechanism via command-line shells. Before the further investigation, verify that this activity is not benign.
 
-### False positive analysis
 
-- Administrators may add programs to this mechanism via command-line shells. Before the further investigation,
-verify that this activity is not benign.
+*Related rules*
 
-### Related rules
 
 - Suspicious Startup Shell Folder Modification - c8b150f0-0164-475b-a75e-74b47800a9ff
 - Persistent Scripts in the Startup Directory - f7c4dc5a-a58d-491d-9f14-9b66507121c0
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -104,43 +110,57 @@ verify that this activity is not benign.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and user.domain != "NT
-AUTHORITY" and file.path :
-("C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start
-Menu\\Programs\\Startup\\*",
-"C:\\ProgramData\\Microsoft\\Windows\\Start
-Menu\\Programs\\StartUp\\*") and process.name : ("cmd.exe",
-"powershell.exe", "wmic.exe",
-"mshta.exe", "pwsh.exe",
-"cscript.exe", "wscript.exe",
-"regsvr32.exe", "RegAsm.exe",
-"rundll32.exe", "EQNEDT32.EXE",
-"WINWORD.EXE", "EXCEL.EXE",
-"POWERPNT.EXE", "MSPUB.EXE",
-"MSACCESS.EXE", "iexplore.exe",
-"InstallUtil.exe")
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and
+  user.domain != "NT AUTHORITY" and
+  file.path : ("C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\Startup\\*",
+               "C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\StartUp\\*") and
+  process.name : ("cmd.exe",
+                  "powershell.exe",
+                  "wmic.exe",
+                  "mshta.exe",
+                  "pwsh.exe",
+                  "cscript.exe",
+                  "wscript.exe",
+                  "regsvr32.exe",
+                  "RegAsm.exe",
+                  "rundll32.exe",
+                  "EQNEDT32.EXE",
+                  "WINWORD.EXE",
+                  "EXCEL.EXE",
+                  "POWERPNT.EXE",
+                  "MSPUB.EXE",
+                  "MSACCESS.EXE",
+                  "iexplore.exe",
+                  "InstallUtil.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -152,46 +172,7 @@ Menu\\Programs\\StartUp\\*") and process.name : ("cmd.exe",
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[startup-persistence-by-a-suspicious-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type != "deletion" and user.domain != "NT
-AUTHORITY" and file.path :
-("C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start
-Menu\\Programs\\Startup\\*",
-"C:\\ProgramData\\Microsoft\\Windows\\Start
-Menu\\Programs\\StartUp\\*") and process.name : ("cmd.exe",
-"powershell.exe", "wmic.exe",
-"mshta.exe", "pwsh.exe",
-"cscript.exe", "wscript.exe",
-"regsvr32.exe", "RegAsm.exe",
-"rundll32.exe", "EQNEDT32.EXE",
-"WINWORD.EXE", "EXCEL.EXE",
-"POWERPNT.EXE", "MSPUB.EXE",
-"MSACCESS.EXE", "iexplore.exe",
-"InstallUtil.exe")
-----------------------------------
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Rule name changed from: Shortcut File Written or Modified for Persistence
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Registry Run Keys / Startup Folder
+** ID: T1547.001
+** Reference URL: https://attack.mitre.org/techniques/T1547/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/statistical-model-detected-c2-beaconing-activity-with-high-confidence.asciidoc b/docs/detections/prebuilt-rules/rule-details/statistical-model-detected-c2-beaconing-activity-with-high-confidence.asciidoc
new file mode 100644
index 0000000000..d362d9d70d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/statistical-model-detected-c2-beaconing-activity-with-high-confidence.asciidoc
@@ -0,0 +1,96 @@
+[[statistical-model-detected-c2-beaconing-activity-with-high-confidence]]
+=== Statistical Model Detected C2 Beaconing Activity with High Confidence
+
+A statistical model has identified command-and-control (C2) beaconing activity with high confidence. Beaconing can help attackers maintain stealthy communication with their C2 servers, receive instructions and payloads, exfiltrate data and maintain persistence in a network.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* ml_beaconing.all
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-1h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/beaconing
+* https://www.elastic.co/security-labs/identifying-beaconing-malware-using-elastic
+
+*Tags*: 
+
+* Domain: Network
+* Use Case: C2 Beaconing Detection
+* Tactic: Command and Control
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Network Beaconing Identification integration assets to be installed, as well as network logs collected by the Elastic Defend or Network Packet Capture integrations.
+
+
+*Network Beaconing Identification Setup*
+
+The Network Beaconing Identification integration consists of a statistical framework to identify C2 beaconing activity in network logs.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Network Beaconing Identification.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Network events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] or https://docs.elastic.co/integrations/network_traffic[Network Packet Capture] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To add the Network Packet Capture integration to an Elastic Agent policy, refer to https://www.elastic.co/guide/en/fleet/current/add-integration-to-policy.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the Network Beaconing Identification integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Network Beaconing Identification and select the integration to see more details about it.
+- Under Settings, click "Install Network Beaconing Identification assets" and follow the prompts to install the assets.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+beacon_stats.beaconing_score: 3
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Web Service
+** ID: T1102
+** Reference URL: https://attack.mitre.org/techniques/T1102/
+* Sub-technique:
+** Name: Bidirectional Communication
+** ID: T1102.002
+** Reference URL: https://attack.mitre.org/techniques/T1102/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/statistical-model-detected-c2-beaconing-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/statistical-model-detected-c2-beaconing-activity.asciidoc
new file mode 100644
index 0000000000..9b67032125
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/statistical-model-detected-c2-beaconing-activity.asciidoc
@@ -0,0 +1,97 @@
+[[statistical-model-detected-c2-beaconing-activity]]
+=== Statistical Model Detected C2 Beaconing Activity
+
+A statistical model has identified command-and-control (C2) beaconing activity. Beaconing can help attackers maintain stealthy communication with their C2 servers, receive instructions and payloads, exfiltrate data and maintain persistence in a network.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* ml_beaconing.all
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-1h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/beaconing
+* https://www.elastic.co/security-labs/identifying-beaconing-malware-using-elastic
+
+*Tags*: 
+
+* Domain: Network
+* Use Case: C2 Beaconing Detection
+* Tactic: Command and Control
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Network Beaconing Identification integration assets to be installed, as well as network logs collected by the Elastic Defend or Network Packet Capture integrations.
+
+
+*Network Beaconing Identification Setup*
+
+The Network Beaconing Identification integration consists of a statistical framework to identify C2 beaconing activity in network logs.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Network Beaconing Identification.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Network events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] or https://docs.elastic.co/integrations/network_traffic[Network Packet Capture] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To add the Network Packet Capture integration to an Elastic Agent policy, refer to https://www.elastic.co/guide/en/fleet/current/add-integration-to-policy.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the Network Beaconing Identification integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Network Beaconing Identification and select the integration to see more details about it.
+- Under Settings, click "Install Network Beaconing Identification assets" and follow the prompts to install the assets.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+beacon_stats.is_beaconing: true and
+not process.name: ("WaAppAgent.exe" or "metricbeat.exe" or "packetbeat.exe" or "WindowsAzureGuestAgent.exe" or "HealthService.exe" or "Widgets.exe" or "lsass.exe" or "msedgewebview2.exe" or "MsMpEng.exe" or "OUTLOOK.EXE" or "msteams.exe" or "FileSyncHelper.exe" or "SearchProtocolHost.exe" or "Creative Cloud.exe" or "ms-teams.exe" or "ms-teamsupdate.exe" or "curl.exe" or "rundll32.exe" or "MsSense.exe" or "wermgr.exe" or "java" or "olk.exe" or "iexplore.exe" or "NetworkManager" or "packetbeat" or "Ssms.exe" or "NisSrv.exe" or "gamingservices.exe" or "appidcertstorecheck.exe" or "POWERPNT.EXE" or "miiserver.exe" or "Grammarly.Desktop.exe" or "SnagitEditor.exe" or "CRWindowsClientService.exe")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Web Service
+** ID: T1102
+** Reference URL: https://attack.mitre.org/techniques/T1102/
+* Sub-technique:
+** Name: Bidirectional Communication
+** ID: T1102.002
+** Reference URL: https://attack.mitre.org/techniques/T1102/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/stolen-credentials-used-to-login-to-okta-account-after-mfa-reset.asciidoc b/docs/detections/prebuilt-rules/rule-details/stolen-credentials-used-to-login-to-okta-account-after-mfa-reset.asciidoc
new file mode 100644
index 0000000000..93049b3cc9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/stolen-credentials-used-to-login-to-okta-account-after-mfa-reset.asciidoc
@@ -0,0 +1,125 @@
+[[stolen-credentials-used-to-login-to-okta-account-after-mfa-reset]]
+=== Stolen Credentials Used to Login to Okta Account After MFA Reset
+
+Detects a sequence of suspicious activities on Windows hosts indicative of credential compromise, followed by efforts to undermine multi-factor authentication (MFA) and single sign-on (SSO) mechanisms for an Okta user account.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-okta*
+* .alerts-security.*
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 6h
+
+*Searches indices from*: now-12h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://developer.okta.com/docs/reference/api/system-log/
+* https://developer.okta.com/docs/reference/api/event-types/
+* https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
+* https://sec.okta.com/articles/2023/08/cross-tenant-impersonation-prevention-and-detection
+
+*Tags*: 
+
+* Tactic: Persistence
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Data Source: Elastic Defend
+* Rule Type: Higher-Order Rule
+* Domain: Endpoint
+* Domain: Cloud
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Stolen Credentials Used to Login to Okta Account After MFA Reset*
+
+
+This rule detects a sequence of suspicious activities on Windows hosts indicative of credential compromise, followed by efforts to undermine multi-factor authentication (MFA) and single sign-on (SSO) mechanisms for an Okta user account.
+
+Typically, adversaries initially extract credentials from targeted endpoints through various means. Subsequently, leveraging social engineering, they may seek to reset the MFA credentials associated with an Okta account, especially in scenarios where Active Directory (AD) services are integrated with Okta. Successfully resetting MFA allows the unauthorized use of stolen credentials to gain access to the compromised Okta account. The attacker can then register their own device for MFA, paving the way for unfettered access to the user's Okta account and any associated SaaS applications. This is particularly alarming if the compromised account has administrative rights, as it could lead to widespread access to organizational resources and configurations.
+
+
+*Possible investigation steps:*
+
+- Identify the user account associated with the Okta login attempt by examining the `user.name` field.
+- Identify the endpoint for the Credential Access alert for this user by examining the `host.name` and `host.id` fields from the alert document.
+- Cross-examine the Okta user and endpoint user to confirm that they are the same person.
+- Reach out to the user to confirm if they have intentionally reset their MFA credentials recently or asked for help in doing so.
+- If the user is unaware of the MFA reset, incident response may be required immediately to prevent further compromise.
+
+
+*False positive analysis:*
+
+- A Windows administrator may have triggered a low-fidelity credential access alert during a legitimate administrative action. Following this, the administrator may have reset the MFA credentials for themselves and then logged into the Okta console for AD directory services integration management.
+
+
+*Response and remediation:*
+
+- If confirmed that the user did not intentionally have their MFA factor reset, deactivate the user account.
+- After deactivation, reset the user's password and MFA factor to regain control of the account.
+    - Ensure that all user sessions are stopped during this process.
+- Immediately reset the user's AD password as well if Okta does not sync back to AD.
+- Forensic analysis on the user's endpoint may be required to determine the root cause of the compromise and identify the scope of the compromise.
+- Review Okta system logs to identify any other suspicious activity associated with the user account, such as creation of a backup account.
+- With the device ID captured from the MFA factor reset, search across all Okta logs for any other activity associated with the device ID.
+
+
+*Setup*
+
+
+==== Setup
+
+
+The Okta and Elastic Defend fleet integration structured data is required to be compatible with this rule. Directory services integration in Okta with AD synced is also required for this rule to be effective as it relies on triaging `user.name` from Okta and Elastic Defend events.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by user.name with maxspan=12h
+    [any where host.os.type == "windows" and signal.rule.threat.tactic.name == "Credential Access"]
+    [any where event.dataset == "okta.system" and okta.event_type == "user.mfa.factor.update"]
+    [any where event.dataset == "okta.system" and okta.event_type: ("user.session.start", "user.authentication*")]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Modify Authentication Process
+** ID: T1556
+** Reference URL: https://attack.mitre.org/techniques/T1556/
+* Sub-technique:
+** Name: Multi-Factor Authentication
+** ID: T1556.006
+** Reference URL: https://attack.mitre.org/techniques/T1556/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/sublime-plugin-or-application-script-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/sublime-plugin-or-application-script-modification.asciidoc
index daa415dbfd..1d80712edf 100644
--- a/docs/detections/prebuilt-rules/rule-details/sublime-plugin-or-application-script-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/sublime-plugin-or-application-script-modification.asciidoc
@@ -5,70 +5,99 @@ Adversaries may create or modify the Sublime application plugins or scripts to e
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://posts.specterops.io/persistent-jxa-66e1c3cd1cf5
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<sublime-plugin-or-application-script-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-----------------------------------
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type in ("change", "creation") and file.extension :
-"py" and file.path : ( "/Users/*/Library/Application
-Support/Sublime Text*/Packages/*.py", "/Applications/Sublime
-Text.app/Contents/MacOS/sublime.py" ) and not process.executable
-: ( "/Applications/Sublime Text*.app/Contents/*",
-"/usr/local/Cellar/git/*/bin/git",
-"/Library/Developer/CommandLineTools/usr/bin/git",
-"/usr/libexec/xpcproxy", "/System/Library/PrivateFrameworks/Desk
-topServicesPriv.framework/Versions/A/Resources/DesktopServicesHelper"
-)
+[source, js]
 ----------------------------------
+file where host.os.type == "macos" and event.type in ("change", "creation") and file.extension : "py" and
+  file.path :
+    (
+      "/Users/*/Library/Application Support/Sublime Text*/Packages/*.py",
+      "/Applications/Sublime Text.app/Contents/MacOS/sublime.py"
+    ) and
+  not process.executable :
+    (
+      "/Applications/Sublime Text*.app/Contents/*",
+      "/usr/local/Cellar/git/*/bin/git",
+      "/Library/Developer/CommandLineTools/usr/bin/git",
+      "/usr/libexec/xpcproxy",
+      "/System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Resources/DesktopServicesHelper"
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,30 +109,3 @@ topServicesPriv.framework/Versions/A/Resources/DesktopServicesHelper"
 ** Name: Compromise Client Software Binary
 ** ID: T1554
 ** Reference URL: https://attack.mitre.org/techniques/T1554/
-
-[[sublime-plugin-or-application-script-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type in ("change", "creation") and file.extension :
-"py" and file.path : ( "/Users/*/Library/Application
-Support/Sublime Text*/Packages/*.py", "/Applications/Sublime
-Text.app/Contents/MacOS/sublime.py" ) and not process.executable
-: ( "/Applications/Sublime Text*.app/Contents/MacOS/Sublime
-Text*", "/usr/local/Cellar/git/*/bin/git",
-"/usr/libexec/xpcproxy", "/System/Library/PrivateFrameworks/Des
-ktopServicesPriv.framework/Versions/A/Resources/DesktopServicesHelper"
-, "/Applications/Sublime Text.app/Contents/MacOS/plugin_host"
-)
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/sudo-command-enumeration-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/sudo-command-enumeration-detected.asciidoc
new file mode 100644
index 0000000000..80c77b2939
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/sudo-command-enumeration-detected.asciidoc
@@ -0,0 +1,99 @@
+[[sudo-command-enumeration-detected]]
+=== Sudo Command Enumeration Detected
+
+This rule monitors for the usage of the sudo -l command, which is used to list the allowed and forbidden commands for the invoking user. Attackers may execute this command to enumerate commands allowed to be executed with sudo permissions, potentially allowing to escalate privileges to root.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+process.name == "sudo" and process.args == "-l" and process.args_count == 2 and
+process.parent.name in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") and 
+not group.Ext.real.id : "0" and not user.Ext.real.id : "0" and not process.args == "dpkg"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Owner/User Discovery
+** ID: T1033
+** Reference URL: https://attack.mitre.org/techniques/T1033/
diff --git a/docs/detections/prebuilt-rules/rule-details/sudo-heap-based-buffer-overflow-attempt.asciidoc b/docs/detections/prebuilt-rules/rule-details/sudo-heap-based-buffer-overflow-attempt.asciidoc
index d58ec7af65..cdca5bdb55 100644
--- a/docs/detections/prebuilt-rules/rule-details/sudo-heap-based-buffer-overflow-attempt.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/sudo-heap-based-buffer-overflow-attempt.asciidoc
@@ -5,7 +5,7 @@ Identifies the attempted use of a heap-based buffer overflow vulnerability for t
 
 *Rule type*: threshold
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,52 +14,48 @@ Identifies the attempted use of a heap-based buffer overflow vulnerability for t
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3156
 * https://blog.qualys.com/vulnerabilities-research/2021/01/26/cve-2021-3156-heap-based-buffer-overflow-in-sudo-baron-samedit
 * https://www.bleepingcomputer.com/news/security/latest-macos-big-sur-also-has-sudo-root-privilege-escalation-flaw
 * https://www.sudo.ws/alerts/unescape_overflow.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* macOS
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 100 (<<sudo-heap-based-buffer-overflow-attempt-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-This rule could generate false positives if the process arguments leveraged by the exploit are shared by custom scripts using the Sudo or Sudoedit binaries. Only Sudo versions 1.8.2 through 1.8.31p2 and 1.9.0 through 1.9.5p1 are affected; if those versions are not present on the endpoint, this could be a false positive.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:start and process.name:(sudo
-or sudoedit) and process.args:(*\\ and ("-i" or "-s"))
+[source, js]
 ----------------------------------
+event.category:process and event.type:start and
+  process.name:(sudo or sudoedit) and
+  process.args:(*\\ and ("-i" or "-s"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -71,13 +67,3 @@ or sudoedit) and process.args:(*\\ and ("-i" or "-s"))
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-[[sudo-heap-based-buffer-overflow-attempt-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/sudoers-file-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/sudoers-file-modification.asciidoc
index 38386f12ce..007e26fb0b 100644
--- a/docs/detections/prebuilt-rules/rule-details/sudoers-file-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/sudoers-file-modification.asciidoc
@@ -3,9 +3,9 @@
 
 A sudoers file specifies the commands that users or groups can run and from which terminals. Adversaries can take advantage of these configurations to execute commands as other users or spawn processes with higher privileges.
 
-*Rule type*: query
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,41 +14,42 @@ A sudoers file specifies the commands that users or groups can run and from whic
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* macOS
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<sudoers-file-modification-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.8.0
+*Version*: 204
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:file and event.type:change and file.path:(/etc/sudoers*
-or /private/etc/sudoers*)
+[source, js]
 ----------------------------------
+event.category:file and event.type:change and file.path:(/etc/sudoers* or /private/etc/sudoers*) and
+not process.name:(dpkg or platform-python or puppet or yum or dnf) and 
+not process.executable:(/opt/chef/embedded/bin/ruby or /opt/puppetlabs/puppet/bin/ruby or /usr/bin/dockerd)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -60,42 +61,7 @@ or /private/etc/sudoers*)
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[sudoers-file-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 7 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and event.type:change and file.path:/etc/sudoers
-----------------------------------
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.11.0 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.1 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:file_integrity and event.action:updated and
-file.path:/etc/sudoers
-----------------------------------
-
+* Sub-technique:
+** Name: Sudo and Sudo Caching
+** ID: T1548.003
+** Reference URL: https://attack.mitre.org/techniques/T1548/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suid-sguid-enumeration-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/suid-sguid-enumeration-detected.asciidoc
new file mode 100644
index 0000000000..4ad5bacdb2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suid-sguid-enumeration-detected.asciidoc
@@ -0,0 +1,119 @@
+[[suid-sguid-enumeration-detected]]
+=== SUID/SGUID Enumeration Detected
+
+This rule monitors for the usage of the "find" command in conjunction with SUID and SGUID permission arguments. SUID (Set User ID) and SGID (Set Group ID) are special permissions in Linux that allow a program to execute with the privileges of the file owner or group, respectively, rather than the privileges of the user running the program. In case an attacker is able to enumerate and find a binary that is misconfigured, they might be able to leverage this misconfiguration to escalate privileges by exploiting vulnerabilities or built-in features in the privileged program.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+process.name == "find" and process.args : "-perm" and process.args : (
+  "/6000", "-6000", "/4000", "-4000", "/2000", "-2000", "/u=s", "-u=s", "/g=s", "-g=s", "/u=s,g=s", "/g=s,u=s"
+) and not (
+  user.Ext.real.id == "0" or group.Ext.real.id == "0" or process.args_count >= 12 or 
+  (process.args : "/usr/bin/pkexec" and process.args : "-xdev" and process.args_count == 7)
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: File and Directory Discovery
+** ID: T1083
+** Reference URL: https://attack.mitre.org/techniques/T1083/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Setuid and Setgid
+** ID: T1548.001
+** Reference URL: https://attack.mitre.org/techniques/T1548/001/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
diff --git a/docs/detections/prebuilt-rules/rule-details/sunburst-command-and-control-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/sunburst-command-and-control-activity.asciidoc
index 4496a9a265..2be7b0aeba 100644
--- a/docs/detections/prebuilt-rules/rule-details/sunburst-command-and-control-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/sunburst-command-and-control-activity.asciidoc
@@ -5,96 +5,91 @@ The malware known as SUNBURST targets the SolarWind's Orion business software fo
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.network-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.fireeye.com/blog/threat-research/2020/12/evasive-attacker-leverages-solarwinds-supply-chain-compromises-with-sunburst-backdoor.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Command and Control
-* Investigation Guide
-
-*Version*: 102 (<<sunburst-command-and-control-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating SUNBURST Command and Control Activity
+*Triage and analysis*
 
-SUNBURST is a trojanized version of a digitally signed SolarWinds Orion plugin called
-SolarWinds.Orion.Core.BusinessLayer.dll. The plugin contains a backdoor that communicates via HTTP to third-party
-servers. After an initial dormant period of up to two weeks, SUNBURST may retrieve and execute commands that instruct
-the backdoor to transfer files, execute files, profile the system, reboot the system, and disable system services.
-The malware's network traffic attempts to blend in with legitimate SolarWinds activity by imitating the Orion
-Improvement Program (OIP) protocol, and the malware stores persistent state data within legitimate plugin configuration files. The
-backdoor uses multiple obfuscated blocklists to identify processes, services, and drivers associated with forensic and
-anti-virus tools.
 
-More details on SUNBURST can be found on the [Mandiant Report](https://www.mandiant.com/resources/sunburst-additional-technical-details).
 
-This rule identifies suspicious network connections that attempt to blend in with legitimate SolarWinds activity
-by imitating the Orion Improvement Program (OIP) protocol behavior.
+*Investigating SUNBURST Command and Control Activity*
+
+
+SUNBURST is a trojanized version of a digitally signed SolarWinds Orion plugin called SolarWinds.Orion.Core.BusinessLayer.dll. The plugin contains a backdoor that communicates via HTTP to third-party servers. After an initial dormant period of up to two weeks, SUNBURST may retrieve and execute commands that instruct the backdoor to transfer files, execute files, profile the system, reboot the system, and disable system services. The malware's network traffic attempts to blend in with legitimate SolarWinds activity by imitating the Orion Improvement Program (OIP) protocol, and the malware stores persistent state data within legitimate plugin configuration files. The backdoor uses multiple obfuscated blocklists to identify processes, services, and drivers associated with forensic and anti-virus tools.
+
+More details on SUNBURST can be found on the https://www.mandiant.com/resources/sunburst-additional-technical-details[Mandiant Report].
+
+This rule identifies suspicious network connections that attempt to blend in with legitimate SolarWinds activity by imitating the Orion Improvement Program (OIP) protocol behavior.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Examine the host for derived artifacts that indicates suspicious activities:
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the executable involved using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
+
+
+- This activity should not happen legitimately. The security team should address any potential benign true positive (B-TP), as this configuration can put the environment at risk.
 
-### False positive analysis
 
-- This activity should not happen legitimately. The security team should address any potential benign true positive
-(B-TP), as this configuration can put the environment at risk.
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -102,41 +97,37 @@ for prevalence, whether they are located in expected locations, and if they are
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Reimage the host operating system and restore compromised files to clean versions.
 - Upgrade SolarWinds systems to the latest version to eradicate the chance of reinfection by abusing the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-network where event.type == "protocol" and network.protocol == "http"
-and process.name : ("ConfigurationWizard.exe",
-"NetFlowService.exe",
-"NetflowDatabaseMaintenance.exe",
-"SolarWinds.Administration.exe",
-"SolarWinds.BusinessLayerHost.exe",
-"SolarWinds.BusinessLayerHostx64.exe",
-"SolarWinds.Collector.Service.exe",
-"SolarwindsDiagnostics.exe") and ( (
-(http.request.body.content : "*/swip/Upload.ashx*" and
-http.request.body.content : ("POST*", "PUT*")) or
-(http.request.body.content : ("*/swip/SystemDescription*",
-"*/swip/Events*") and http.request.body.content : ("GET*", "HEAD*"))
-) and not http.request.body.content : "*solarwinds.com*" )
+[source, js]
 ----------------------------------
+network where host.os.type == "windows" and event.type == "protocol" and network.protocol == "http" and
+  process.name : ("ConfigurationWizard.exe",
+                  "NetFlowService.exe",
+                  "NetflowDatabaseMaintenance.exe",
+                  "SolarWinds.Administration.exe",
+                  "SolarWinds.BusinessLayerHost.exe",
+                  "SolarWinds.BusinessLayerHostx64.exe",
+                  "SolarWinds.Collector.Service.exe",
+                  "SolarwindsDiagnostics.exe") and
+  (
+    (
+      (http.request.body.content : "*/swip/Upload.ashx*" and http.request.body.content : ("POST*", "PUT*")) or
+      (http.request.body.content : ("*/swip/SystemDescription*", "*/swip/Events*") and http.request.body.content : ("GET*", "HEAD*"))
+    ) and
+    not http.request.body.content : "*solarwinds.com*"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -148,8 +139,10 @@ http.request.body.content : ("POST*", "PUT*")) or
 ** Name: Application Layer Protocol
 ** ID: T1071
 ** Reference URL: https://attack.mitre.org/techniques/T1071/
-
-
+* Sub-technique:
+** Name: Web Protocols
+** ID: T1071.001
+** Reference URL: https://attack.mitre.org/techniques/T1071/001/
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -158,62 +151,7 @@ http.request.body.content : ("POST*", "PUT*")) or
 ** Name: Supply Chain Compromise
 ** ID: T1195
 ** Reference URL: https://attack.mitre.org/techniques/T1195/
-
-[[sunburst-command-and-control-activity-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network where event.type == "protocol" and network.protocol == "http"
-and process.name : ("ConfigurationWizard.exe",
-"NetFlowService.exe",
-"NetflowDatabaseMaintenance.exe",
-"SolarWinds.Administration.exe",
-"SolarWinds.BusinessLayerHost.exe",
-"SolarWinds.BusinessLayerHostx64.exe",
-"SolarWinds.Collector.Service.exe",
-"SolarwindsDiagnostics.exe") and (http.request.body.content :
-"*/swip/Upload.ashx*" and http.request.body.content : ("POST*",
-"PUT*")) or (http.request.body.content :
-("*/swip/SystemDescription*", "*/swip/Events*") and
-http.request.body.content : ("GET*", "HEAD*")) and not
-http.request.body.content : "*solarwinds.com*"
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:protocol and
-network.protocol:http and process.name:( ConfigurationWizard.exe or
-NetFlowService.exe or NetflowDatabaseMaintenance.exe or
-SolarWinds.Administration.exe or SolarWinds.BusinessLayerHost.exe or
-SolarWinds.BusinessLayerHostx64.exe or
-SolarWinds.Collector.Service.exe or SolarwindsDiagnostics.exe) and
-http.request.body.content:(( (*/swip/Upload.ashx* and (POST* or PUT*))
-or (*/swip/SystemDescription* and (GET* or HEAD*)) or (*/swip/Events*
-and (GET* or HEAD*))) and not *solarwinds.com*)
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Compromise Software Supply Chain
+** ID: T1195.002
+** Reference URL: https://attack.mitre.org/techniques/T1195/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-access-to-ldap-attributes.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-access-to-ldap-attributes.asciidoc
new file mode 100644
index 0000000000..411579ec5d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-access-to-ldap-attributes.asciidoc
@@ -0,0 +1,81 @@
+[[suspicious-access-to-ldap-attributes]]
+=== Suspicious Access to LDAP Attributes
+
+Identify read access to a high number of Active Directory object attributes. The knowledge of objects properties can help adversaries find vulnerabilities, elevate privileges or collect sensitive information.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-system.security*
+* logs-windows.forwarded*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: System
+* Data Source: Active Directory
+* Data Source: Windows
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+The 'Audit Directory Service Changes' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Changes (Success,Failure)
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+any where event.action == "Directory Service Access" and
+ event.code == "4662" and not winlog.event_data.SubjectUserSid : "S-1-5-18" and
+ winlog.event_data.AccessMaskDescription == "Read Property" and length(winlog.event_data.Properties) >= 2000
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Permission Groups Discovery
+** ID: T1069
+** Reference URL: https://attack.mitre.org/techniques/T1069/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-activity-reported-by-okta-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-activity-reported-by-okta-user.asciidoc
index 7317b427d5..53e29aa944 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-activity-reported-by-okta-user.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-activity-reported-by-okta-user.asciidoc
@@ -5,7 +5,7 @@ Detects when a user reports suspicious activity for their Okta account. These ev
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,60 +14,51 @@ Detects when a user reports suspicious activity for their Okta account. These ev
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Monitoring
-
-*Version*: 102 (<<suspicious-activity-reported-by-okta-user-history, version history>>)
+* Use Case: Identity and Access Audit
+* Data Source: Okta
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.9.0
+*Version*: 205
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A user may report suspicious activity on their Okta account in error.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and
-event.action:user.account.report_suspicious_activity_by_enduser
+[source, js]
 ----------------------------------
+event.dataset:okta.system and event.action:user.account.report_suspicious_activity_by_enduser
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -79,8 +70,6 @@ event.action:user.account.report_suspicious_activity_by_enduser
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -89,8 +78,6 @@ event.action:user.account.report_suspicious_activity_by_enduser
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Privilege Escalation
 ** ID: TA0004
@@ -99,8 +86,6 @@ event.action:user.account.report_suspicious_activity_by_enduser
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -109,37 +94,3 @@ event.action:user.account.report_suspicious_activity_by_enduser
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[suspicious-activity-reported-by-okta-user-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.13.0 release)::
-* Formatting only
-
-Version 5 (7.12.0 release)::
-* Formatting only
-
-Version 4 (7.11.2 release)::
-* Formatting only
-
-Version 3 (7.11.0 release)::
-* Formatting only
-
-Version 2 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.module:okta and event.dataset:okta.system and
-event.action:user.account.report_suspicious_activity_by_enduser
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-antimalware-scan-interface-dll.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-antimalware-scan-interface-dll.asciidoc
new file mode 100644
index 0000000000..98bfa9736c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-antimalware-scan-interface-dll.asciidoc
@@ -0,0 +1,142 @@
+[[suspicious-antimalware-scan-interface-dll]]
+=== Suspicious Antimalware Scan Interface DLL
+
+Identifies the creation of the Antimalware Scan Interface (AMSI) DLL in an unusual location. This may indicate an attempt to bypass AMSI by loading a rogue AMSI module instead of the legit one.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/S3cur3Th1sSh1t/Amsi-Bypass-Powershell
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 9
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Suspicious Antimalware Scan Interface DLL*
+
+
+The Windows Antimalware Scan Interface (AMSI) is a versatile interface standard that allows your applications and services to integrate with any antimalware product on a machine. AMSI integrates with multiple Windows components, ranging from User Account Control (UAC) to VBA macros and PowerShell.
+
+Attackers might copy a rogue AMSI DLL to an unusual location to prevent the process from loading the legitimate module, achieving a bypass to execute malicious code.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Identify the process that created the DLL and which account was used.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate the execution of scripts and macros after the registry modification.
+- Investigate other processes launched from the directory that the DLL was created.
+- Inspect the host for suspicious or abnormal behavior in the alert timeframe:
+  - Observe and collect information about the following activities in the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+
+
+*False positive analysis*
+
+
+- This modification should not happen legitimately. Any potential benign true positive (B-TP) should be mapped and monitored by the security team as these modifications expose the host to malware infections.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and file.path != null and
+ file.name : ("amsi.dll", "amsi") and not file.path : ("?:\\Windows\\system32\\amsi.dll", "?:\\Windows\\Syswow64\\amsi.dll", "?:\\$WINDOWS.~BT\\NewOS\\Windows\\WinSXS\\*", "?:\\$WINDOWS.~BT\\NewOS\\Windows\\servicing\\LCU\\*", "?:\\$WINDOWS.~BT\\Work\\*\\*", "?:\\Windows\\SoftwareDistribution\\Download\\*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Impair Defenses
+** ID: T1562
+** Reference URL: https://attack.mitre.org/techniques/T1562/
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: DLL Search Order Hijacking
+** ID: T1574.001
+** Reference URL: https://attack.mitre.org/techniques/T1574/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-apt-package-manager-execution.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-apt-package-manager-execution.asciidoc
new file mode 100644
index 0000000000..be7750e04d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-apt-package-manager-execution.asciidoc
@@ -0,0 +1,129 @@
+[[suspicious-apt-package-manager-execution]]
+=== Suspicious APT Package Manager Execution
+
+Detects suspicious process events executed by the APT package manager, potentially indicating persistence through an APT backdoor. In Linux, APT (Advanced Package Tool) is a command-line utility used for handling packages on Debian-based systems, providing functions for installing, updating, upgrading, and removing software along with managing package repositories. Attackers can backdoor APT to gain persistence by injecting malicious code into scripts that APT runs, thereby ensuring continued unauthorized access or control each time APT is used for package management.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Execution
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=5s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+   process.parent.name == "apt" and process.args == "-c" and process.name in (
+     "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish"
+   )
+  ] by process.entity_id
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and process.name : (
+     "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "python*", "php*",
+     "perl", "ruby", "lua*", "openssl", "nc", "netcat", "ncat", "telnet", "awk"
+   )
+  ] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-apt-package-manager-network-connection.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-apt-package-manager-network-connection.asciidoc
new file mode 100644
index 0000000000..10e175ebaf
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-apt-package-manager-network-connection.asciidoc
@@ -0,0 +1,118 @@
+[[suspicious-apt-package-manager-network-connection]]
+=== Suspicious APT Package Manager Network Connection
+
+Detects suspicious network events executed by the APT package manager, potentially indicating persistence through an APT backdoor. In Linux, APT (Advanced Package Tool) is a command-line utility used for handling packages on Debian-based systems, providing functions for installing, updating, upgrading, and removing software along with managing package repositories. Attackers can backdoor APT to gain persistence by injecting malicious code into scripts that APT runs, thereby ensuring continued unauthorized access or control each time APT is used for package management.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Command and Control
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=5s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+   process.parent.name == "apt" and process.args == "-c" and process.name in (
+     "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish"
+    )
+  ] by process.entity_id
+  [network where host.os.type == "linux" and event.action == "connection_attempted" and event.type == "start"
+  ] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-automator-workflows-execution.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-automator-workflows-execution.asciidoc
index d3f3fc23d8..c71c32b2f3 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-automator-workflows-execution.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-automator-workflows-execution.asciidoc
@@ -5,54 +5,88 @@ Identifies the execution of the Automator Workflows process followed by a networ
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://posts.specterops.io/persistent-jxa-66e1c3cd1cf5
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Execution
 
-*Version*: 100 (<<suspicious-automator-workflows-execution-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=30s [process where event.type in
-("start", "process_started") and process.name == "automator"]
-[network where process.name:"com.apple.automator.runner"]
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=30s
+ [process where host.os.type == "macos" and event.type in ("start", "process_started") and process.name == "automator"]
+ [network where host.os.type == "macos" and process.name:"com.apple.automator.runner"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,13 +98,3 @@ sequence by host.id with maxspan=30s [process where event.type in
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[suspicious-automator-workflows-execution-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-browser-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-browser-child-process.asciidoc
index e997390937..da337d6082 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-browser-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-browser-child-process.asciidoc
@@ -5,7 +5,7 @@ Identifies the execution of a suspicious browser child process. Adversaries may
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
 
@@ -13,62 +13,100 @@ Identifies the execution of a suspicious browser child process. Adversaries may
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://objective-see.com/blog/blog_0x43.html
 * https://fr.slideshare.net/codeblue_jp/cb19-recent-apt-attack-on-crypto-exchange-employees-by-heungsoo-kang
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Initial Access
-* Execution
 
-*Version*: 100 (<<suspicious-browser-child-process-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.12.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : ("Google Chrome", "Google Chrome Helper*",
-"firefox", "Opera", "Safari", "com.apple.WebKit.WebContent",
-"Microsoft Edge") and process.name : ("sh", "bash", "dash", "ksh",
-"tcsh", "zsh", "curl", "wget", "python*", "perl*", "php*",
-"osascript", "pwsh") and process.command_line != null and not
-process.command_line : "*/Library/Application
-Support/Microsoft/MAU*/Microsoft
-AutoUpdate.app/Contents/MacOS/msupdate*" and not process.args :
-( "hw.model", "IOPlatformExpertDevice",
-"/Volumes/Google Chrome/Google
-Chrome.app/Contents/Frameworks/*/Resources/install.sh", "--
-defaults-torrc", "*Chrome.app", "Framework.framework/Versi
-ons/*/Resources/keystone_promote_preflight.sh",
-"/Users/*/Library/Application
-Support/Google/Chrome/recovery/*/ChromeRecovery", "$DISPLAY",
-"*GIO_LAUNCHED_DESKTOP_FILE_PID=$$*", "/opt/homebrew/*",
-"/usr/local/*brew*" )
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and
+  process.parent.name : ("Google Chrome", "Google Chrome Helper*", "firefox", "Opera", "Safari", "com.apple.WebKit.WebContent", "Microsoft Edge") and
+  process.name : ("sh", "bash", "dash", "ksh", "tcsh", "zsh", "curl", "wget", "python*", "perl*", "php*", "osascript", "pwsh") and
+  process.command_line != null and
+  not process.command_line : "*/Library/Application Support/Microsoft/MAU*/Microsoft AutoUpdate.app/Contents/MacOS/msupdate*" and
+  not process.args :
+    (
+      "hw.model",
+      "IOPlatformExpertDevice",
+      "/Volumes/Google Chrome/Google Chrome.app/Contents/Frameworks/*/Resources/install.sh",
+      "/Applications/Google Chrome.app/Contents/Frameworks/Google Chrome Framework.framework/Versions/*/Helpers/Google Chrome Helper (Renderer).app/Contents/MacOS/Google Chrome Helper (Renderer)",
+      "/Applications/Firefox.app/Contents/MacOS/plugin-container.app/Contents/MacOS/plugin-container",
+      "--defaults-torrc",
+      "*Chrome.app",
+      "Framework.framework/Versions/*/Resources/keystone_promote_preflight.sh",
+      "/Users/*/Library/Application Support/Google/Chrome/recovery/*/ChromeRecovery",
+      "$DISPLAY",
+      "*GIO_LAUNCHED_DESKTOP_FILE_PID=$$*",
+      "/opt/homebrew/*",
+      "/usr/local/*brew*"
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,8 +118,6 @@ Support/Google/Chrome/recovery/*/ChromeRecovery", "$DISPLAY",
 ** Name: Exploitation for Client Execution
 ** ID: T1203
 ** Reference URL: https://attack.mitre.org/techniques/T1203/
-
-
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -90,33 +126,3 @@ Support/Google/Chrome/recovery/*/ChromeRecovery", "$DISPLAY",
 ** Name: Drive-by Compromise
 ** ID: T1189
 ** Reference URL: https://attack.mitre.org/techniques/T1189/
-
-[[suspicious-browser-child-process-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : ("Google Chrome", "Google Chrome Helper*",
-"firefox", "Opera", "Safari", "com.apple.WebKit.WebContent",
-"Microsoft Edge") and process.name : ("sh", "bash", "dash", "ksh",
-"tcsh", "zsh", "curl", "wget", "python*", "perl*", "php*",
-"osascript", "pwsh") and process.command_line != null and not
-process.args : ( "/Library/Application
-Support/Microsoft/MAU*/Microsoft
-AutoUpdate.app/Contents/MacOS/msupdate", "hw.model",
-"IOPlatformExpertDevice", "/Volumes/Google Chrome/Google
-Chrome.app/Contents/Frameworks/*/Resources/install.sh", "--
-defaults-torrc", "Chrome.app", "Framework.framework/Vers
-ions/*/Resources/keystone_promote_preflight.sh",
-"/Users/*/Library/Application
-Support/Google/Chrome/recovery/*/ChromeRecovery", "$DISPLAY",
-"GIO_LAUNCHED_DESKTOP_FILE_PID=$$" )
-----------------------------------
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-calendar-file-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-calendar-file-modification.asciidoc
index 3a44708f98..fc5ba88684 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-calendar-file-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-calendar-file-modification.asciidoc
@@ -5,64 +5,100 @@ Identifies suspicious modifications of the calendar file by an unusual process.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
-* auditbeat-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://labs.f-secure.com/blog/operationalising-calendar-alerts-persistence-on-macos
 * https://github.com/FSecureLABS/CalendarPersist
 * https://github.com/D00MFist/PersistentJXA/blob/master/CalendarPersist.js
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<suspicious-calendar-file-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Trusted applications for managing calendars and reminders.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:file and event.action:modification and
-file.path:/Users/*/Library/Calendars/*.calendar/Events/*.ics and
-process.executable: (* and not ( /System/Library/* or
-/System/Applications/Calendar.app/Contents/MacOS/* or
-/System/Applications/Mail.app/Contents/MacOS/Mail or
-/usr/libexec/xpcproxy or /sbin/launchd or /Applications/*
-) )
+[source, js]
 ----------------------------------
+event.category:file and host.os.type:macos and event.action:modification and
+  file.path:/Users/*/Library/Calendars/*.calendar/Events/*.ics and
+  process.executable:
+  (* and not
+    (
+      /System/Library/* or
+      /System/Applications/Calendar.app/Contents/MacOS/* or
+      /System/Applications/Mail.app/Contents/MacOS/Mail or
+      /usr/libexec/xpcproxy or
+      /sbin/launchd or
+      /Applications/*
+    )
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,23 +110,3 @@ process.executable: (* and not ( /System/Library/* or
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[suspicious-calendar-file-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and event.action:modification and
-file.path:/Users/*/Library/Calendars/*.calendar/Events/*.ics and
-process.executable: (* and not ( /System/Library/* or
-/System/Applications/Calendar.app/Contents/MacOS/* or
-/usr/libexec/xpcproxy or /sbin/launchd or
-/Applications/* ) )
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-certutil-commands.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-certutil-commands.asciidoc
index 5f3f81f3ee..5e0d0bac67 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-certutil-commands.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-certutil-commands.asciidoc
@@ -5,170 +5,133 @@ Identifies suspicious commands being used with certutil.exe. CertUtil is a nativ
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://twitter.com/Moriarty_Meng/status/984380793383370752
 * https://twitter.com/egre55/status/1087685529016193025
 * https://www.sysadmins.lv/blog-en/certutil-tips-and-tricks-working-with-x509-file-format.aspx
 * https://docs.microsoft.com/en-us/archive/blogs/pki/basic-crl-checking-with-certutil
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
-
-*Version*: 101 (<<suspicious-certutil-commands-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Suspicious CertUtil Commands*
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"certutil.exe" or process.pe.original_file_name == "CertUtil.exe") and
-process.args : ("?decode", "?encode", "?urlcache", "?verifyctl",
-"?encodehex", "?decodehex", "?exportPFX")
-----------------------------------
 
-==== Threat mapping
+`certutil.exe` is a command line utility program that is included with Microsoft Windows operating systems. It is used to manage and manipulate digital certificates and certificate services on computers running Windows.
 
-*Framework*: MITRE ATT&CK^TM^
+Attackers can abuse `certutil.exe` utility to download and/or deobfuscate malware, offensive security tools, and certificates from external sources to take the next steps in a compromised environment. This rule identifies command line arguments used to accomplish these behaviors.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Deobfuscate/Decode Files or Information
-** ID: T1140
-** Reference URL: https://attack.mitre.org/techniques/T1140/
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-[[suspicious-certutil-commands-history]]
-==== Rule version history
 
-Version 101 (8.6.0 release)::
-* Formatting only
+*Possible investigation steps*
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 16 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"certutil.exe" or process.pe.original_file_name == "CertUtil.exe") and
-process.args : ("?decode", "?encode", "?urlcache", "?verifyctl",
-"?encodehex", "?decodehex", "?exportPFX")
-----------------------------------
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Examine the command line to determine the nature of the execution.
+  - If files were downloaded, retrieve them and check whether they were run, and under which security context.
+  - If files were obfuscated or deobfuscated, retrieve them.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the involved files using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-Version 14 (8.3.0 release)::
-* Formatting only
 
-Version 12 (8.2.0 release)::
-* Formatting only
+*False positive analysis*
 
-Version 10 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"certutil.exe" or process.pe.original_file_name == "CertUtil.exe") and
-process.args : ("?decode", "?encode", "?urlcache", "?verifyctl",
-"?encodehex", "?decodehex")
-----------------------------------
 
-Version 9 (7.14.0 release)::
-* Rule name changed from: Encoding or Decoding Files via CertUtil
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"certutil.exe" or process.pe.original_file_name == "CertUtil.exe") and
-process.args : ("?decode", "?encode")
-----------------------------------
+- If this rule is noisy in your environment due to expected activity, consider adding exceptions — preferably with a combination of user and command line conditions.
 
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:certutil.exe and process.args:(-decode or -encode or
-/decode or /encode)
-----------------------------------
 
-Version 7 (7.12.0 release)::
-* Formatting only
+*Response and remediation*
 
-Version 6 (7.11.2 release)::
-* Formatting only
 
-Version 5 (7.10.0 release)::
-* Formatting only
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 4 (7.9.1 release)::
-* Formatting only
 
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:certutil.exe and process.args:(-decode or -encode or
-/decode or /encode)
-----------------------------------
+==== Rule query
+
 
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:"certutil.exe" and process.args:("-encode" or "/encode"
-or "-decode" or "/decode")
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "certutil.exe" or ?process.pe.original_file_name == "CertUtil.exe") and
+  process.args : ("?decode", "?encode", "?urlcache", "?verifyctl", "?encodehex", "?decodehex", "?exportPFX")
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Deobfuscate/Decode Files or Information
+** ID: T1140
+** Reference URL: https://attack.mitre.org/techniques/T1140/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-child-process-of-adobe-acrobat-reader-update-service.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-child-process-of-adobe-acrobat-reader-update-service.asciidoc
index c52896f20d..df15323b0c 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-child-process-of-adobe-acrobat-reader-update-service.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-child-process-of-adobe-acrobat-reader-update-service.asciidoc
@@ -5,67 +5,98 @@ Detects attempts to exploit privilege escalation vulnerabilities related to the
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://rekken.github.io/2020/05/14/Security-Flaws-in-Adobe-Acrobat-Reader-Allow-Malicious-Program-to-Gain-Root-on-macOS-Silently/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Privilege Escalation
-* CVE-2020-9615
-* CVE-2020-9614
-* CVE-2020-9613
 
-*Version*: 100 (<<suspicious-child-process-of-adobe-acrobat-reader-update-service-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Trusted system or Adobe Acrobat Related processes.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:com.adobe.ARMDC.SMJobBlessHelper and
-user.name:root and not process.executable:
-(/Library/PrivilegedHelperTools/com.adobe.ARMDC.SMJobBlessHelper or
-/usr/bin/codesign or
-/private/var/folders/zz/*/T/download/ARMDCHammer or
-/usr/sbin/pkgutil or /usr/bin/shasum or
-/usr/bin/perl* or /usr/sbin/spctl or
-/usr/sbin/installer or /usr/bin/csrutil)
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+  process.parent.name:com.adobe.ARMDC.SMJobBlessHelper and
+  user.name:root and
+  not process.executable: (/Library/PrivilegedHelperTools/com.adobe.ARMDC.SMJobBlessHelper or
+                           /usr/bin/codesign or
+                           /private/var/folders/zz/*/T/download/ARMDCHammer or
+                           /usr/sbin/pkgutil or
+                           /usr/bin/shasum or
+                           /usr/bin/perl* or
+                           /usr/sbin/spctl or
+                           /usr/sbin/installer or
+                           /usr/bin/csrutil)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,26 +108,3 @@ user.name:root and not process.executable:
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-[[suspicious-child-process-of-adobe-acrobat-reader-update-service-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:com.adobe.ARMDC.SMJobBlessHelper and
-user.name:root and not process.executable:
-(/Library/PrivilegedHelperTools/com.adobe.ARMDC.SMJobBlessHelper or
-/usr/bin/codesign or
-/private/var/folders/zz/*/T/download/ARMDCHammer or
-/usr/sbin/pkgutil or /usr/bin/shasum or
-/usr/bin/perl* or /usr/sbin/spctl or
-/usr/sbin/installer)
-----------------------------------
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-cmd-execution-via-wmi.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-cmd-execution-via-wmi.asciidoc
index 96e8ae6db3..9d2f73d1a7 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-cmd-execution-via-wmi.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-cmd-execution-via-wmi.asciidoc
@@ -5,62 +5,68 @@ Identifies suspicious command execution (cmd) via Windows Management Instrumenta
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<suspicious-cmd-execution-via-wmi-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"WmiPrvSE.exe" and process.name : "cmd.exe" and process.args :
-"\\\\127.0.0.1\\*" and process.args : ("2>&1", "1>")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.parent.name : "WmiPrvSE.exe" and process.name : "cmd.exe" and
+ process.args : "\\\\127.0.0.1\\*" and process.args : ("2>&1", "1>")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,40 +78,11 @@ process where event.type == "start" and process.parent.name :
 ** Name: Windows Management Instrumentation
 ** ID: T1047
 ** Reference URL: https://attack.mitre.org/techniques/T1047/
-
-[[suspicious-cmd-execution-via-wmi-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "WmiPrvSE.exe" and process.name : "cmd.exe" and
-process.args : "\\\\127.0.0.1\\*" and process.args : ("2>&1", "1>")
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name == "WmiPrvSE.exe" and process.name == "cmd.exe"
-and wildcard(process.args, "\\\\127.0.0.1\\*") and process.args in
-("2>&1", "1>")
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-communication-app-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-communication-app-child-process.asciidoc
new file mode 100644
index 0000000000..838d628170
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-communication-app-child-process.asciidoc
@@ -0,0 +1,299 @@
+[[suspicious-communication-app-child-process]]
+=== Suspicious Communication App Child Process
+
+Identifies suspicious child processes of communications apps, which can indicate a potential masquerading as the communication app or the exploitation of a vulnerability on the application causing it to execute code.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Persistence
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (
+    /* Slack */
+    (process.parent.name : "slack.exe" and not
+      (
+        (
+          process.executable : (
+            "?:\\Program Files\\*",
+            "?:\\Program Files (x86)\\*",
+            "?:\\Users\\*\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe",
+            "?:\\Users\\*\\AppData\\Local\\Island\\Island\\Application\\Island.exe",
+            "?:\\Users\\*\\AppData\\Roaming\\Zoom\\bin*\\Zoom.exe",
+            "?:\\Windows\\System32\\rundll32.exe",
+            "?:\\Users\\*\\AppData\\Local\\Mozilla Firefox\\firefox.exe",
+            "?:\\Windows\\System32\\notepad.exe",
+            "?:\\Windows\\System32\\WerFault.exe",
+            "?:\\Windows\\SysWOW64\\WerFault.exe",
+            "?:\\Users\\*\\AppData\\Local\\Programs\\Opera\\opera.exe"
+          ) and process.code_signature.trusted == true  
+        ) or
+        (
+          process.code_signature.subject_name : (
+            "Slack Technologies, Inc.",
+            "Slack Technologies, LLC"
+          ) and process.code_signature.trusted == true
+        ) or
+        (
+          (process.name : "powershell.exe" and process.command_line : "powershell.exe -c Invoke-WebRequest -Uri https://slackb.com/*") or
+          (process.name : "cmd.exe" and process.command_line : "C:\\WINDOWS\\system32\\cmd.exe /d /s /c \"%windir%\\System32\\rundll32.exe User32.dll,SetFocus 0\"")
+        )
+      )
+    ) or
+
+    /* WebEx */
+    (process.parent.name : ("CiscoCollabHost.exe", "WebexHost.exe") and not
+      (
+        (
+          process.executable : (
+            "?:\\Program Files\\*",
+            "?:\\Program Files (x86)\\*",
+            "?:\\Windows\\System32\\WerFault.exe",
+            "?:\\Users\\*\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe",
+            "?:\\Users\\*\\AppData\\Local\\Mozilla Firefox\\firefox.exe",
+            "?:\\Users\\*\\AppData\\Local\\Programs\\Opera\\opera.exe"
+          ) and process.code_signature.trusted == true  
+        ) or
+        (
+          process.code_signature.subject_name : (
+            "Cisco Systems, Inc.",
+            "Cisco WebEx LLC",
+            "Cisco Systems Inc."
+          ) and process.code_signature.trusted == true
+        )
+      )
+    ) or
+
+    /* Teams */
+    (process.parent.name : "Teams.exe" and not
+      (
+        (
+          process.executable : (
+            "?:\\Program Files\\*",
+            "?:\\Program Files (x86)\\*",
+            "?:\\Windows\\System32\\WerFault.exe",
+            "?:\\Windows\\SysWOW64\\WerFault.exe",
+            "?:\\Windows\\BrowserCore\\BrowserCore.exe",
+            "?:\\Users\\*\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe",
+            "?:\\Users\\*\\AppData\\Local\\Mozilla Firefox\\firefox.exe"
+          ) and process.code_signature.trusted == true  
+        ) or
+        (
+          process.code_signature.subject_name : (
+            "Microsoft Corporation",
+            "Microsoft 3rd Party Application Component"
+          ) and process.code_signature.trusted == true
+        ) or
+        (
+          (process.name : "taskkill.exe" and process.args : "Teams.exe")
+        )
+      )
+    ) or
+
+    /* Discord */
+    (process.parent.name : "Discord.exe" and not
+      (
+        (
+          process.executable : (
+            "?:\\Program Files\\*",
+            "?:\\Program Files (x86)\\*",
+            "?:\\Users\\*\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe",
+            "?:\\Windows\\System32\\reg.exe",
+            "?:\\Windows\\SysWOW64\\reg.exe",
+            "?:\\Windows\\System32\\WerFault.exe",
+            "?:\\Windows\\SysWOW64\\WerFault.exe"
+          ) and process.code_signature.trusted == true  
+        ) or
+        (
+          process.code_signature.subject_name : (
+            "Discord Inc."
+          ) and process.code_signature.trusted == true
+        ) or
+        (
+          process.name : "cmd.exe" and 
+          (
+            process.command_line : (
+              "C:\\WINDOWS\\system32\\cmd.exe /d /s /c \"chcp\"",
+              "C:\\WINDOWS\\system32\\cmd.exe /q /d /s /c \"C:\\Program^ Files\\NVIDIA^ Corporation\\NVSMI\\nvidia-smi.exe\""
+            ) or
+            process.args : (
+              "C:\\WINDOWS/System32/nvidia-smi.exe",
+              "C:\\WINDOWS\\System32\\nvidia-smi.exe",
+              "C:\\Windows\\System32\\DriverStore\\FileRepository/*/nvidia-smi.exe*"
+            )
+          )
+        )
+      )
+    ) or
+
+    /* WhatsApp */
+    (process.parent.name : "Whatsapp.exe" and not
+      (
+        (
+          process.executable : (
+            "?:\\Program Files\\*",
+            "?:\\Program Files (x86)\\*",
+            "?:\\Windows\\System32\\WerFault.exe",
+            "?:\\Windows\\System32\\reg.exe",
+            "?:\\Windows\\SysWOW64\\reg.exe"
+          ) and process.code_signature.trusted == true  
+        ) or
+        (
+          process.code_signature.subject_name : (
+            "WhatsApp LLC",
+            "WhatsApp, Inc",
+            "24803D75-212C-471A-BC57-9EF86AB91435"
+          ) and process.code_signature.trusted == true
+        ) or
+        (
+          (process.name : "cmd.exe" and process.command_line : "C:\\Windows\\system32\\cmd.exe /d /s /c \"C:\\Windows\\system32\\wbem\\wmic.exe*")
+        )
+      )
+    ) or
+
+    /* Zoom */
+    (process.parent.name : "Zoom.exe" and not
+      (
+        (
+          process.executable : (
+            "?:\\Program Files\\*",
+            "?:\\Program Files (x86)\\*",
+            "?:\\Users\\*\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe",
+            "?:\\Users\\*\\AppData\\Local\\Island\\Island\\Application\\Island.exe",
+            "?:\\Users\\*\\AppData\\Local\\Mozilla Firefox\\firefox.exe",
+            "?:\\Windows\\System32\\WerFault.exe"
+          ) and process.code_signature.trusted == true  
+        ) or
+        (
+          process.code_signature.subject_name : (
+            "Zoom Video Communications, Inc."
+          ) and process.code_signature.trusted == true
+        )
+      )
+    ) or
+
+    /* Outlook */
+    (process.parent.name : "outlook.exe" and not
+      (
+        (
+          process.executable : (
+            "?:\\Program Files\\*",
+            "?:\\Program Files (x86)\\*",
+            "?:\\Windows\\System32\\WerFault.exe",
+            "?:\\Windows\\SysWOW64\\WerFault.exe",
+            "?:\\Windows\\system32\\wermgr.exe",
+            "?:\\Users\\*\\AppData\\Local\\Microsoft\\Teams\\current\\Teams.exe",
+            "?:\\Users\\*\\AppData\\Local\\Temp\\NewOutlookInstall\\NewOutlookInstaller.exe",
+            "?:\\Users\\*\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe",
+            "?:\\Users\\*\\AppData\\Local\\Island\\Island\\Application\\Island.exe",
+            "?:\\Users\\*\\AppData\\Local\\Mozilla Firefox\\firefox.exe",
+            "?:\\Users\\*\\AppData\\Roaming\\Zoom\\bin\\Zoom.exe",
+            "?:\\Windows\\System32\\IME\\SHARED\\IMEWDBLD.EXE",
+            "?:\\Windows\\System32\\spool\\drivers\\x64\\*",
+            "?:\\Windows\\System32\\prevhost.exe",
+            "?:\\Windows\\System32\\dwwin.exe",
+            "?:\\Windows\\System32\\mspaint.exe",
+            "?:\\Windows\\SysWOW64\\mspaint.exe",
+            "?:\\Windows\\System32\\notepad.exe",
+            "?:\\Windows\\SysWOW64\\notepad.exe",
+            "?:\\Windows\\System32\\smartscreen.exe",
+            "?:\\Windows\\explorer.exe",
+            "?:\\Windows\\splwow64.exe"
+          ) and process.code_signature.trusted == true  
+        ) or
+        (
+          process.name : "rundll32.exe" and
+          process.args : "*hpmsn???.dll,MonitorPrintJobStatus*"
+        )
+      )
+    ) or
+
+    /* Thunderbird */
+    (process.parent.name : "thunderbird.exe" and not
+      (
+        (
+          process.executable : (
+            "?:\\Program Files\\*",
+            "?:\\Program Files (x86)\\*",
+            "?:\\Windows\\System32\\WerFault.exe",
+            "?:\\Windows\\splwow64.exe"
+          ) and process.code_signature.trusted == true  
+        ) or
+        (
+          process.code_signature.subject_name : (
+            "Mozilla Corporation"
+          ) and process.code_signature.trusted == true
+        )
+      )
+    )
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Compromise Client Software Binary
+** ID: T1554
+** Reference URL: https://attack.mitre.org/techniques/T1554/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-content-extracted-or-decompressed-via-funzip.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-content-extracted-or-decompressed-via-funzip.asciidoc
new file mode 100644
index 0000000000..d707d45de8
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-content-extracted-or-decompressed-via-funzip.asciidoc
@@ -0,0 +1,120 @@
+[[suspicious-content-extracted-or-decompressed-via-funzip]]
+=== Suspicious Content Extracted or Decompressed via Funzip
+
+Identifies when suspicious content is extracted from a file and subsequently decompressed using the funzip utility. Malware may execute the tail utility using the "-c" option to read a sequence of bytes from the end of a file. The output from tail can be piped to funzip in order to decompress malicious code before it is executed. This behavior is consistent with malware families such as Bundlore.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://attack.mitre.org/software/S0482/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.action in ("exec", "exec_event") and
+((process.args == "tail" and process.args == "-c" and process.args == "funzip")) and
+not process.args : "/var/log/messages" and 
+not process.parent.executable : ("/usr/bin/dracut", "/sbin/dracut", "/usr/bin/xargs") and
+not (process.parent.name in ("sh", "sudo") and process.parent.command_line : "*nessus_su*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Obfuscated Files or Information
+** ID: T1027
+** Reference URL: https://attack.mitre.org/techniques/T1027/
+* Technique:
+** Name: Deobfuscate/Decode Files or Information
+** ID: T1140
+** Reference URL: https://attack.mitre.org/techniques/T1140/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-crontab-creation-or-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-crontab-creation-or-modification.asciidoc
index 6ceaa5573a..fd8bfff188 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-crontab-creation-or-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-crontab-creation-or-modification.asciidoc
@@ -5,7 +5,7 @@ Identifies attempts to create or modify a crontab via a process that is not cron
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
 
@@ -13,46 +13,80 @@ Identifies attempts to create or modify a crontab via a process that is not cron
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://taomm.org/PDFs/vol1/CH%200x02%20Persistence.pdf
 * https://theevilbit.github.io/beyond/beyond_0004/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<suspicious-crontab-creation-or-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.3.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and process.name != null and
-file.path : "/private/var/at/tabs/*" and not process.executable ==
-"/usr/bin/crontab"
+[source, js]
 ----------------------------------
+file where host.os.type == "macos" and event.type != "deletion" and process.name != null and
+  file.path : "/private/var/at/tabs/*" and not process.executable == "/usr/bin/crontab"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -64,20 +98,7 @@ file.path : "/private/var/at/tabs/*" and not process.executable ==
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[suspicious-crontab-creation-or-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type != "deletion" and process.name != null and
-file.path : "/private/var/at/tabs/*" and not process.executable ==
-"/usr/bin/crontab"
-----------------------------------
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Cron
+** ID: T1053.003
+** Reference URL: https://attack.mitre.org/techniques/T1053/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-data-encryption-via-openssl-utility.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-data-encryption-via-openssl-utility.asciidoc
new file mode 100644
index 0000000000..e6656d04fa
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-data-encryption-via-openssl-utility.asciidoc
@@ -0,0 +1,105 @@
+[[suspicious-data-encryption-via-openssl-utility]]
+=== Suspicious Data Encryption via OpenSSL Utility
+
+Identifies when the openssl command-line utility is used to encrypt multiple files on a host within a short time window. Adversaries may encrypt data on a single or multiple systems in order to disrupt the availability of their target's data and may attempt to hold the organization's data to ransom for the purposes of extortion.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.welivesecurity.com/2017/06/30/telebots-back-supply-chain-attacks-against-ukraine/
+* https://www.trendmicro.com/en_us/research/21/f/bash-ransomware-darkradiation-targets-red-hat--and-debian-based-linux-distributions.html
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Impact
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, user.name, process.parent.entity_id with maxspan=5s
+  [ process where host.os.type == "linux" and event.action == "exec" and 
+    process.name == "openssl" and process.parent.name : ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "perl*", "php*", "python*", "xargs") and
+    process.args == "-in" and process.args == "-out" and
+    process.args in ("-k", "-K", "-kfile", "-pass", "-iv", "-md") and
+    /* excluding base64 encoding options and including encryption password or key params */
+    not process.args in ("-d", "-a", "-A", "-base64", "-none", "-nosalt") ] with runs=10
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Data Encrypted for Impact
+** ID: T1486
+** Reference URL: https://attack.mitre.org/techniques/T1486/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-dll-loaded-for-persistence-or-privilege-escalation.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-dll-loaded-for-persistence-or-privilege-escalation.asciidoc
index 89668e8278..5b21ca60dc 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-dll-loaded-for-persistence-or-privilege-escalation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-dll-loaded-for-persistence-or-privilege-escalation.asciidoc
@@ -5,23 +5,24 @@ Identifies the loading of a non Microsoft signed DLL that is missing on a defaul
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.library*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://itm4n.github.io/windows-dll-hijacking-clarified/
 * http://remoteawesomethoughts.blogspot.com/2019/05/windows-10-task-schedulerservice.html
@@ -30,44 +31,47 @@ Identifies the loading of a non Microsoft signed DLL that is missing on a defaul
 * https://windows-internals.com/faxing-your-way-to-system/
 * http://waleedassar.blogspot.com/2013/01/wow64logdll.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Privilege Escalation
-* Investigation Guide
-
-*Version*: 102 (<<suspicious-dll-loaded-for-persistence-or-privilege-escalation-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious DLL Loaded for Persistence or Privilege Escalation
+*Triage and analysis*
+
+
+
+*Investigating Suspicious DLL Loaded for Persistence or Privilege Escalation*
+
+
+Attackers can execute malicious code by abusing missing modules that processes try to load, enabling them to escalate privileges or gain persistence. This rule identifies the loading of a non-Microsoft-signed DLL that is missing on a default Windows installation or one that can be loaded from a different location by a native Windows process.
+
 
-Attackers can execute malicious code by abusing missing modules that processes try to load, enabling them to escalate
-privileges or gain persistence. This rule identifies the loading of a non-Microsoft-signed DLL that is missing on a
-default Windows installation or one that can be loaded from a different location by a native Windows process.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Examine the DLL signature and identify the process that created it.
-  - Investigate any abnormal behaviors by the process such as network connections, registry or file modifications, and
-  any spawned child processes.
+  - Investigate any abnormal behaviors by the process such as network connections, registry or file modifications, and any spawned child processes.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Retrieve the DLL and determine if it is malicious:
   - Use a private sandboxed malware analysis system to perform analysis.
@@ -79,12 +83,15 @@ default Windows installation or one that can be loaded from a different location
   - Use the PowerShell Get-FileHash cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
 
-- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently
-malicious must be monitored by the security team.
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -92,45 +99,57 @@ malicious must be monitored by the security team.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-any where (event.category == "library" or (event.category ==
-"process" and event.action : "Image loaded*")) and ( /* compatible
-with Elastic Endpoint Library Events */ (dll.name : ("wlbsctrl.dll",
-"wbemcomn.dll", "WptsExtensions.dll", "Tsmsisrv.dll", "TSVIPSrv.dll",
-"Msfte.dll", "wow64log.dll",
-"WindowsCoreDeviceInfo.dll", "Ualapi.dll", "wlanhlp.dll",
-"phoneinfo.dll", "EdgeGdi.dll", "cdpsgshims.dll",
-"windowsperformancerecordercontrol.dll", "diagtrack_win.dll") and
-(dll.code_signature.trusted == false or dll.code_signature.exists ==
-false)) or /* compatible with Sysmon EventID 7 - Image Load */
-(file.name : ("wlbsctrl.dll", "wbemcomn.dll", "WptsExtensions.dll",
-"Tsmsisrv.dll", "TSVIPSrv.dll", "Msfte.dll",
-"wow64log.dll", "WindowsCoreDeviceInfo.dll", "Ualapi.dll",
-"wlanhlp.dll", "phoneinfo.dll", "EdgeGdi.dll",
-"cdpsgshims.dll", "windowsperformancerecordercontrol.dll",
-"diagtrack_win.dll") and not file.code_signature.status == "Valid")
-)
+[source, js]
 ----------------------------------
+any where host.os.type == "windows" and
+ (event.category : ("driver", "library") or (event.category == "process" and event.action : "Image loaded*")) and
+ (
+  /* compatible with Elastic Endpoint Library Events */
+  (?dll.name : ("wlbsctrl.dll", "wbemcomn.dll", "WptsExtensions.dll", "Tsmsisrv.dll", "TSVIPSrv.dll", "Msfte.dll",
+               "wow64log.dll", "WindowsCoreDeviceInfo.dll", "Ualapi.dll", "wlanhlp.dll", "phoneinfo.dll", "EdgeGdi.dll",
+               "cdpsgshims.dll", "windowsperformancerecordercontrol.dll", "diagtrack_win.dll", "oci.dll", "TPPCOIPW32.dll", 
+               "tpgenlic.dll", "thinmon.dll", "fxsst.dll", "msTracer.dll")
+   and (?dll.code_signature.trusted != true or ?dll.code_signature.exists != true)) or
+
+  /* compatible with Sysmon EventID 7 - Image Load */
+  (file.name : ("wlbsctrl.dll", "wbemcomn.dll", "WptsExtensions.dll", "Tsmsisrv.dll", "TSVIPSrv.dll", "Msfte.dll",
+               "wow64log.dll", "WindowsCoreDeviceInfo.dll", "Ualapi.dll", "wlanhlp.dll", "phoneinfo.dll", "EdgeGdi.dll",
+               "cdpsgshims.dll", "windowsperformancerecordercontrol.dll", "diagtrack_win.dll", "oci.dll", "TPPCOIPW32.dll", 
+               "tpgenlic.dll", "thinmon.dll", "fxsst.dll", "msTracer.dll") and 
+   not file.path : ("?:\\Windows\\System32\\wbemcomn.dll", "?:\\Windows\\SysWOW64\\wbemcomn.dll") and 
+   not file.hash.sha256 : 
+            ("6e837794fc282446906c36d681958f2f6212043fc117c716936920be166a700f", 
+             "b14e4954e8cca060ffeb57f2458b6a3a39c7d2f27e94391cbcea5387652f21a4", 
+             "c258d90acd006fa109dc6b748008edbb196d6168bc75ace0de0de54a4db46662") and 
+   not file.code_signature.status == "Valid")
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -142,8 +161,10 @@ false)) or /* compatible with Sysmon EventID 7 - Image Load */
 ** Name: Hijack Execution Flow
 ** ID: T1574
 ** Reference URL: https://attack.mitre.org/techniques/T1574/
-
-
+* Sub-technique:
+** Name: DLL Side-Loading
+** ID: T1574.002
+** Reference URL: https://attack.mitre.org/techniques/T1574/002/
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -152,48 +173,19 @@ false)) or /* compatible with Sysmon EventID 7 - Image Load */
 ** Name: Hijack Execution Flow
 ** ID: T1574
 ** Reference URL: https://attack.mitre.org/techniques/T1574/
-
-[[suspicious-dll-loaded-for-persistence-or-privilege-escalation-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-library where dll.name : ( "wlbsctrl.dll", "wbemcomn.dll",
-"WptsExtensions.dll", "Tsmsisrv.dll", "TSVIPSrv.dll",
-"Msfte.dll", "wow64log.dll", "WindowsCoreDeviceInfo.dll",
-"Ualapi.dll", "wlanhlp.dll", "phoneinfo.dll", "EdgeGdi.dll",
-"cdpsgshims.dll", "windowsperformancerecordercontrol.dll",
-"diagtrack_win.dll" ) and not (dll.code_signature.subject_name :
-("Microsoft Windows", "Microsoft Corporation") and
-dll.code_signature.status : "trusted")
-----------------------------------
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-library where dll.name : ( "wlbsctrl.dll", "wbemcomn.dll",
-"WptsExtensions.dll", "Tsmsisrv.dll", "TSVIPSrv.dll",
-"Msfte.dll", "wow64log.dll", "WindowsCoreDeviceInfo.dll",
-"Ualapi.dll", "wlanhlp.dll", "phoneinfo.dll", "EdgeGdi.dll",
-"cdpsgshims.dll", "windowsperformancerecordercontrol.dll",
-"diagtrack_win.dll" ) and not (dll.code_signature.subject_name :
-"Microsoft Windows" and dll.code_signature.status : "trusted")
-----------------------------------
-
+* Sub-technique:
+** Name: DLL Search Order Hijacking
+** ID: T1574.001
+** Reference URL: https://attack.mitre.org/techniques/T1574/001/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-dynamic-linker-discovery-via-od.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-dynamic-linker-discovery-via-od.asciidoc
new file mode 100644
index 0000000000..05a3d94707
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-dynamic-linker-discovery-via-od.asciidoc
@@ -0,0 +1,108 @@
+[[suspicious-dynamic-linker-discovery-via-od]]
+=== Suspicious Dynamic Linker Discovery via od
+
+Monitors for dynamic linker discovery via the od utility. od (octal dump) is a command-line utility in Unix operating systems used for displaying data in various formats, including octal, hexadecimal, decimal, and ASCII, primarily used for examining and debugging binary files or data streams. Attackers can leverage od to analyze the dynamic linker by identifying injection points and craft exploits based on the observed behaviors and structures within these files.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/arget13/DDexec
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "od" and process.args in (
+  "/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2", "/etc/ld.so.preload", "/lib64/ld-linux-x86-64.so.2",
+  "/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2", "/usr/lib64/ld-linux-x86-64.so.2"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Process Discovery
+** ID: T1057
+** Reference URL: https://attack.mitre.org/techniques/T1057/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-emond-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-emond-child-process.asciidoc
index e796616516..0cdf98c41b 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-emond-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-emond-child-process.asciidoc
@@ -5,7 +5,7 @@ Identifies the execution of a suspicious child process of the Event Monitor Daem
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
 
@@ -13,48 +13,102 @@ Identifies the execution of a suspicious child process of the Event Monitor Daem
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.xorrior.com/emond-persistence/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
 
-*Version*: 100 (<<suspicious-emond-child-process-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "emond" and process.name : ( "bash",
-"dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish",
-"Python", "python*", "perl*", "php*", "osascript",
-"pwsh", "curl", "wget", "cp", "mv", "touch", "echo",
-"base64", "launchctl")
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and
+ process.parent.name : "emond" and
+ process.name : (
+   "bash",
+   "dash",
+   "sh",
+   "tcsh",
+   "csh",
+   "zsh",
+   "ksh",
+   "fish",
+   "Python",
+   "python*",
+   "perl*",
+   "php*",
+   "osascript",
+   "pwsh",
+   "curl",
+   "wget",
+   "cp",
+   "mv",
+   "touch",
+   "echo",
+   "base64",
+   "launchctl")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,13 +120,7 @@ process.parent.name : "emond" and process.name : ( "bash",
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[suspicious-emond-child-process-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Emond
+** ID: T1546.014
+** Reference URL: https://attack.mitre.org/techniques/T1546/014/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-endpoint-security-parent-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-endpoint-security-parent-process.asciidoc
index e1539ebc6f..4e48e658f3 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-endpoint-security-parent-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-endpoint-security-parent-process.asciidoc
@@ -5,66 +5,91 @@ A suspicious Endpoint Security parent process was detected. This may indicate a
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<suspicious-endpoint-security-parent-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name :
-("esensor.exe", "elastic-endpoint.exe") and process.parent.executable
-!= null and /* add FPs here */ not process.parent.executable :
-("C:\\Program Files\\Elastic\\*",
-"C:\\Windows\\System32\\services.exe",
-"C:\\Windows\\System32\\WerFault*.exe",
-"C:\\Windows\\System32\\wermgr.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : ("esensor.exe", "elastic-endpoint.exe") and
+  process.parent.executable != null and
+  /* add FPs here */
+  not process.parent.executable : (
+        "?:\\Program Files\\Elastic\\*",
+        "?:\\Windows\\System32\\services.exe",
+        "?:\\Windows\\System32\\WerFault*.exe",
+        "?:\\Windows\\System32\\wermgr.exe",
+        "?:\\Windows\\explorer.exe"
+  ) and
+  not (
+    process.parent.executable : (
+        "?:\\Windows\\System32\\cmd.exe",
+        "?:\\Windows\\System32\\SecurityHealthHost.exe",
+        "?:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
+    ) and
+    process.args : (
+        "test", "version",
+        "top", "run",
+        "*help", "status",
+        "upgrade", "/launch",
+        "/enable"
+    )
+  )
+  
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,58 +101,7 @@ process where event.type == "start" and process.name :
 ** Name: Masquerading
 ** ID: T1036
 ** Reference URL: https://attack.mitre.org/techniques/T1036/
-
-[[suspicious-endpoint-security-parent-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.name : ("esensor.exe", "elastic-endpoint.exe") and
-process.parent.executable != null and /* add FPs here */ not
-process.parent.executable : ("C:\\Program Files\\Elastic\\*",
-"C:\\Windows\\System32\\services.exe",
-"C:\\Windows\\System32\\WerFault*.exe",
-"C:\\Windows\\System32\\wermgr.exe")
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.name : ("esensor.exe", "elastic-endpoint.exe") and
-process.parent.executable != null and /* add FPs here */ not
-process.parent.executable : ("C:\\Program Files\\Elastic\\*",
-"C:\\Windows\\System32\\services.exe",
-"C:\\Windows\\System32\\WerFault*.exe",
-"C:\\Windows\\System32\\wermgr.exe")
-----------------------------------
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:(esensor.exe or "elastic-endpoint.exe" or "elastic-
-agent.exe") and not
-process.parent.executable:"C:\Windows\System32\services.exe"
-----------------------------------
-
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-execution-from-a-mounted-device.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-from-a-mounted-device.asciidoc
index ecd2e14e47..2b1cacd613 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-execution-from-a-mounted-device.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-from-a-mounted-device.asciidoc
@@ -5,68 +5,72 @@ Identifies when a script interpreter or signed binary is launched via a non-stan
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.microsoft.com/security/blog/2021/05/27/new-sophisticated-email-based-attack-from-nobelium/
 * https://www.volexity.com/blog/2021/05/27/suspected-apt29-operation-launches-election-fraud-themed-phishing-campaigns/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-
-*Version*: 100 (<<suspicious-execution-from-a-mounted-device-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.executable : "C:\\*"
-and (process.working_directory : "?:\\" and not
-process.working_directory: "C:\\") and process.parent.name :
-"explorer.exe" and process.name : ("rundll32.exe", "mshta.exe",
-"powershell.exe", "pwsh.exe", "cmd.exe", "regsvr32.exe",
-"cscript.exe", "wscript.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.executable : "C:\\*" and
+  (process.working_directory : "?:\\" and not process.working_directory: "C:\\") and
+  process.parent.name : "explorer.exe" and
+  process.name : ("rundll32.exe", "mshta.exe", "powershell.exe", "pwsh.exe", "cmd.exe", "regsvr32.exe",
+                  "cscript.exe", "wscript.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,8 +82,18 @@ process.working_directory: "C:\\") and process.parent.name :
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-
+* Sub-technique:
+** Name: Mshta
+** ID: T1218.005
+** Reference URL: https://attack.mitre.org/techniques/T1218/005/
+* Sub-technique:
+** Name: Regsvr32
+** ID: T1218.010
+** Reference URL: https://attack.mitre.org/techniques/T1218/010/
+* Sub-technique:
+** Name: Rundll32
+** ID: T1218.011
+** Reference URL: https://attack.mitre.org/techniques/T1218/011/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -88,16 +102,11 @@ process.working_directory: "C:\\") and process.parent.name :
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[suspicious-execution-from-a-mounted-device-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-execution-from-inet-cache.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-from-inet-cache.asciidoc
new file mode 100644
index 0000000000..ee70a2e2f2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-from-inet-cache.asciidoc
@@ -0,0 +1,82 @@
+[[suspicious-execution-from-inet-cache]]
+=== Suspicious Execution from INET Cache
+
+Identifies the execution of a process with arguments pointing to the INetCache Folder. Adversaries may deliver malicious content via WININET during initial access.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.trendmicro.com/en_us/research/24/b/cve202421412-water-hydra-targets-traders-with-windows-defender-s.html
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Command and Control
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and  
+ process.parent.name : ("explorer.exe", "winrar.exe", "7zFM.exe", "Bandizip.exe") and
+  (process.args : "?:\\Users\\*\\AppData\\Local\\Microsoft\\Windows\\INetCache\\IE\\*" or
+   process.executable : "?:\\Users\\*\\AppData\\Local\\Microsoft\\Windows\\INetCache\\IE\\*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Ingress Tool Transfer
+** ID: T1105
+** Reference URL: https://attack.mitre.org/techniques/T1105/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-microsoft-office-add-ins.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-microsoft-office-add-ins.asciidoc
new file mode 100644
index 0000000000..8241e56d79
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-microsoft-office-add-ins.asciidoc
@@ -0,0 +1,123 @@
+[[suspicious-execution-via-microsoft-office-add-ins]]
+=== Suspicious Execution via Microsoft Office Add-Ins
+
+Identifies execution of common Microsoft Office applications to launch an Office Add-In from a suspicious path or with an unusual parent process. This may indicate an attempt to get initial access via a malicious phishing MS Office Add-In.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/Octoberfest7/XLL_Phishing
+* https://labs.f-secure.com/archive/add-in-opportunities-for-office-persistence/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where 
+    
+    host.os.type == "windows" and event.type == "start" and  
+    
+    process.name : ("WINWORD.EXE", "EXCEL.EXE", "POWERPNT.EXE", "MSACCESS.EXE", "VSTOInstaller.exe") and 
+    
+    process.args regex~ """.+\.(wll|xll|ppa|ppam|xla|xlam|vsto)""" and 
+    
+    /* Office Add-In from suspicious paths */
+    (process.args :
+             ("?:\\Users\\*\\Temp\\7z*",
+              "?:\\Users\\*\\Temp\\Rar$*",
+              "?:\\Users\\*\\Temp\\Temp?_*",
+              "?:\\Users\\*\\Temp\\BNZ.*",
+              "?:\\Users\\*\\Downloads\\*",
+              "?:\\Users\\*\\AppData\\Roaming\\*",
+              "?:\\Users\\Public\\*",
+              "?:\\ProgramData\\*",
+              "?:\\Windows\\Temp\\*",
+              "\\Device\\*",
+              "http*") or
+	      
+    process.parent.name : ("explorer.exe", "OpenWith.exe") or 
+    
+    /* Office Add-In from suspicious parent */
+    process.parent.name : ("cmd.exe", "powershell.exe")) and
+	  
+    /* False Positives */
+    not (process.args : "*.vsto" and
+         process.parent.executable :
+                   ("?:\\Program Files\\Logitech\\LogiOptions\\PlugInInstallerUtility*.exe",
+                    "?:\\ProgramData\\Logishrd\\LogiOptions\\Plugins\\VSTO\\*\\VSTOInstaller.exe",
+                    "?:\\Program Files\\Logitech\\LogiOptions\\PlugInInstallerUtility.exe",
+                    "?:\\Program Files\\LogiOptionsPlus\\PlugInInstallerUtility*.exe",
+                    "?:\\ProgramData\\Logishrd\\LogiOptionsPlus\\Plugins\\VSTO\\*\\VSTOInstaller.exe",
+                    "?:\\Program Files\\Common Files\\microsoft shared\\VSTO\\*\\VSTOInstaller.exe")) and
+    not (process.args : "/Uninstall" and process.name : "VSTOInstaller.exe") and
+    not (process.parent.name : "rundll32.exe" and
+         process.parent.args : "?:\\WINDOWS\\Installer\\MSI*.tmp,zzzzInvokeManagedCustomActionOutOfProc") and
+    not (process.name : "VSTOInstaller.exe" and process.args : "https://dl.getsidekick.com/outlook/vsto/Sidekick.vsto")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Office Application Startup
+** ID: T1137
+** Reference URL: https://attack.mitre.org/techniques/T1137/
+* Sub-technique:
+** Name: Add-ins
+** ID: T1137.006
+** Reference URL: https://attack.mitre.org/techniques/T1137/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-msiexec.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-msiexec.asciidoc
new file mode 100644
index 0000000000..ab9a5e7882
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-msiexec.asciidoc
@@ -0,0 +1,98 @@
+[[suspicious-execution-via-msiexec]]
+=== Suspicious Execution via MSIEXEC
+
+Identifies suspicious execution of the built-in Windows Installer, msiexec.exe, to install a package from usual paths or parent process. Adversaries may abuse msiexec.exe to launch malicious local MSI files.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* winlogbeat-*
+* logs-windows.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://lolbas-project.github.io/lolbas/Binaries/Msiexec/
+* https://www.guardicore.com/labs/purple-fox-rootkit-now-propagates-as-a-worm/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.action == "start" and
+  process.name : "msiexec.exe" and user.id : ("S-1-5-21*", "S-1-12-*") and process.parent.executable != null and
+  (
+    (process.args : "/i" and process.args : ("/q", "/quiet") and process.args_count == 4 and
+     process.args : ("?:\\Users\\*", "?:\\ProgramData\\*") and
+     not process.parent.executable : ("?:\\Program Files (x86)\\*.exe",
+                                      "?:\\Program Files\\*.exe",
+                                      "?:\\Windows\\explorer.exe",
+                                      "?:\\Users\\*\\Desktop\\*",
+                                      "?:\\Users\\*\\Downloads\\*",
+                                      "?:\\programdata\\*")) or
+
+    (process.args_count == 1 and not process.parent.executable : ("?:\\Windows\\explorer.exe", "?:\\Windows\\SysWOW64\\explorer.exe")) or
+
+    (process.args : "/i" and process.args : ("/q", "/quiet") and process.args_count == 4 and
+     (process.parent.args : "Schedule" or process.parent.name : "wmiprvse.exe" or
+     process.parent.executable : "?:\\Users\\*\\AppData\\*" or
+     (process.parent.name : ("powershell.exe", "cmd.exe") and length(process.parent.command_line) >= 200))) or
+
+    (process.args : "/i" and process.args : ("/q", "/quiet") and process.args_count == 4 and
+     ?process.working_directory : "?:\\" and process.parent.name : ("cmd.exe", "powershell.exe"))
+  ) and
+
+  /* noisy pattern */
+  not (process.parent.executable : "?:\\Users\\*\\AppData\\Local\\Temp\\*" and ?process.parent.args_count >= 2 and
+       process.args : "?:\\Users\\*\\AppData\\Local\\Temp\\*\\*.msi") and
+
+  not process.args : ("?:\\Program Files (x86)\\*", "?:\\Program Files\\*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: Msiexec
+** ID: T1218.007
+** Reference URL: https://attack.mitre.org/techniques/T1218/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-scheduled-task.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-scheduled-task.asciidoc
index 270f25b72b..bacf2ddaba 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-scheduled-task.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-scheduled-task.asciidoc
@@ -5,86 +5,101 @@ Identifies execution of a suspicious program via scheduled tasks by looking at p
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 100 (<<suspicious-execution-via-scheduled-task-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Execution
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Legitimate scheduled tasks running third party software.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and /* Schedule service
-cmdline on Win10+ */ process.parent.name : "svchost.exe" and
-process.parent.args : "Schedule" and /* add suspicious programs
-here */ process.pe.original_file_name in
-( "cscript.exe",
-"wscript.exe", "PowerShell.EXE",
-"Cmd.Exe", "MSHTA.EXE",
-"RUNDLL32.EXE", "REGSVR32.EXE",
-"MSBuild.exe", "InstallUtil.exe",
-"RegAsm.exe", "RegSvcs.exe",
-"msxsl.exe", "CONTROL.EXE",
-"EXPLORER.EXE",
-"Microsoft.Workflow.Compiler.exe",
-"msiexec.exe" ) and /* add
-suspicious paths here */ process.args : ( "C:\\Users\\*",
-"C:\\ProgramData\\*", "C:\\Windows\\Temp\\*",
-"C:\\Windows\\Tasks\\*", "C:\\PerfLogs\\*",
-"C:\\Intel\\*", "C:\\Windows\\Debug\\*", "C:\\HP\\*")
-and not (process.name : "cmd.exe" and process.args : "?:\\*.bat"
-and process.working_directory : "?:\\Windows\\System32\\") and
-not (process.name : "cscript.exe" and process.args :
-"?:\\Windows\\system32\\calluxxprovider.vbs") and not
-(process.name : "powershell.exe" and process.args : ("-File",
-"-PSConsoleFile") and user.id : "S-1-5-18") and not (process.name
-: "msiexec.exe" and user.id : "S-1-5-18")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+    /* Schedule service cmdline on Win10+ */
+    process.parent.name : "svchost.exe" and process.parent.args : "Schedule" and
+    /* add suspicious programs here */
+    process.pe.original_file_name in
+                                (
+                                  "cscript.exe",
+                                  "wscript.exe",
+                                  "PowerShell.EXE",
+                                  "Cmd.Exe",
+                                  "MSHTA.EXE",
+                                  "RUNDLL32.EXE",
+                                  "REGSVR32.EXE",
+                                  "MSBuild.exe",
+                                  "InstallUtil.exe",
+                                  "RegAsm.exe",
+                                  "RegSvcs.exe",
+                                  "msxsl.exe",
+                                  "CONTROL.EXE",
+                                  "EXPLORER.EXE",
+                                  "Microsoft.Workflow.Compiler.exe",
+                                  "msiexec.exe"
+                                  ) and
+    /* add suspicious paths here */
+    process.args : (
+       "C:\\Users\\*",
+       "C:\\ProgramData\\*",
+       "C:\\Windows\\Temp\\*",
+       "C:\\Windows\\Tasks\\*",
+       "C:\\PerfLogs\\*",
+       "C:\\Intel\\*",
+       "C:\\Windows\\Debug\\*",
+       "C:\\HP\\*") and
+
+     not (process.name : "cmd.exe" and process.args : "?:\\*.bat" and process.working_directory : "?:\\Windows\\System32\\") and
+     not (process.name : "cscript.exe" and process.args : "?:\\Windows\\system32\\calluxxprovider.vbs") and
+     not (process.name : "powershell.exe" and process.args : ("-File", "-PSConsoleFile") and user.id : "S-1-5-18") and
+     not (process.name : "msiexec.exe" and user.id : "S-1-5-18")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -96,69 +111,19 @@ not (process.name : "cscript.exe" and process.args :
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[suspicious-execution-via-scheduled-task-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and /* Schedule service
-cmdline on Win10+ */ process.parent.name : "svchost.exe" and
-process.parent.args : "Schedule" and /* add suspicious programs
-here */ process.pe.original_file_name in
-( "cscript.exe",
-"wscript.exe", "PowerShell.EXE",
-"Cmd.Exe", "MSHTA.EXE",
-"RUNDLL32.EXE", "REGSVR32.EXE",
-"MSBuild.exe", "InstallUtil.exe",
-"RegAsm.exe", "RegSvcs.exe",
-"msxsl.exe", "CONTROL.EXE",
-"EXPLORER.EXE",
-"Microsoft.Workflow.Compiler.exe",
-"msiexec.exe" ) and /* add
-suspicious paths here */ process.args : ( "C:\\Users\\*",
-"C:\\ProgramData\\*", "C:\\Windows\\Temp\\*",
-"C:\\Windows\\Tasks\\*", "C:\\PerfLogs\\*",
-"C:\\Intel\\*", "C:\\Windows\\Debug\\*", "C:\\HP\\*")
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and /* Schedule service
-cmdline on Win10+ */ process.parent.name : "svchost.exe" and
-process.parent.args : "Schedule" and /* add suspicious programs
-here */ process.pe.original_file_name in
-( "cscript.exe",
-"wscript.exe", "PowerShell.EXE",
-"Cmd.Exe", "MSHTA.EXE",
-"RUNDLL32.EXE", "REGSVR32.EXE",
-"MSBuild.exe", "InstallUtil.exe",
-"RegAsm.exe", "RegSvcs.exe",
-"msxsl.exe", "CONTROL.EXE",
-"EXPLORER.EXE",
-"Microsoft.Workflow.Compiler.exe",
-"msiexec.exe" ) and /* add
-suspicious paths here */ process.args : ( "C:\\Users\\*",
-"C:\\ProgramData\\*", "C:\\Windows\\Temp\\*",
-"C:\\Windows\\Tasks\\*", "C:\\PerfLogs\\*",
-"C:\\Intel\\*", "C:\\Windows\\Debug\\*", "C:\\HP\\*")
-----------------------------------
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-windows-subsystem-for-linux.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-windows-subsystem-for-linux.asciidoc
new file mode 100644
index 0000000000..00d005d52b
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-execution-via-windows-subsystem-for-linux.asciidoc
@@ -0,0 +1,97 @@
+[[suspicious-execution-via-windows-subsystem-for-linux]]
+=== Suspicious Execution via Windows Subsystem for Linux
+
+Detects Linux Bash commands from the the Windows Subsystem for Linux. Adversaries may enable and use WSL for Linux to avoid detection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.f-secure.com/hunting-for-windows-subsystem-for-linux/
+* https://lolbas-project.github.io/lolbas/OtherMSBinaries/Wsl/
+* https://blog.qualys.com/vulnerabilities-threat-research/2022/03/22/implications-of-windows-subsystem-for-linux-for-adversaries-defenders-part-1
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type : "start" and
+  (
+    (
+      (process.executable : "?:\\Windows\\System32\\bash.exe" or ?process.pe.original_file_name == "Bash.exe") and 
+      not process.command_line : ("bash", "bash.exe")
+    ) or 
+    process.executable : "?:\\Users\\*\\AppData\\Local\\Packages\\*\\rootfs\\usr\\bin\\bash" or 
+    (
+      process.parent.name : "wsl.exe" and ?process.parent.command_line : "bash*" and not process.name : "wslhost.exe"
+    ) or 
+    (
+      process.name : "wsl.exe" and process.args : (
+        "curl", "/etc/shadow", "/etc/passwd", "cat", "--system", "root", "-e", "--exec", "bash", "/mnt/c/*"
+      ) and not process.args : ("wsl-bootstrap", "docker-desktop-data", "*.vscode-server*")
+    )
+  ) and 
+    not process.parent.executable : ("?:\\Program Files\\Docker\\*.exe", "?:\\Program Files (x86)\\Docker\\*.exe")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indirect Command Execution
+** ID: T1202
+** Reference URL: https://attack.mitre.org/techniques/T1202/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-explorer-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-explorer-child-process.asciidoc
index f8b5db26b3..b0a47b1feb 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-explorer-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-explorer-child-process.asciidoc
@@ -5,68 +5,80 @@ Identifies a suspicious Windows explorer child process. Explorer.exe can be abus
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Initial Access
+*Tags*: 
 
-*Version*: 101 (<<suspicious-explorer-child-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and ( process.name :
-("cscript.exe", "wscript.exe", "powershell.exe", "rundll32.exe",
-"cmd.exe", "mshta.exe", "regsvr32.exe") or
-process.pe.original_file_name in ("cscript.exe", "wscript.exe",
-"PowerShell.EXE", "RUNDLL32.EXE", "Cmd.Exe", "MSHTA.EXE",
-"REGSVR32.EXE") ) and /* Explorer started via DCOM */
-process.parent.name : "explorer.exe" and process.parent.args :
-"-Embedding" and not process.parent.args: ( /*
-Noisy CLSID_SeparateSingleProcessExplorerHost Explorer COM Class IDs
-*/ "/factory,{5BD95610-9434-43C2-886C-57852CC8A120}",
-"/factory,{ceff45ee-c862-41de-aee2-a022c81eda92}" )
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (
+   process.name : ("cscript.exe", "wscript.exe", "powershell.exe", "rundll32.exe", "cmd.exe", "mshta.exe", "regsvr32.exe") or
+   process.pe.original_file_name in ("cscript.exe", "wscript.exe", "PowerShell.EXE", "RUNDLL32.EXE", "Cmd.Exe", "MSHTA.EXE", "REGSVR32.EXE")
+  ) and
+  /* Explorer started via DCOM */
+  process.parent.name : "explorer.exe" and process.parent.args : "-Embedding" and
+  not process.parent.args:
+          (
+            /* Noisy CLSID_SeparateSingleProcessExplorerHost Explorer COM Class IDs   */
+            "/factory,{5BD95610-9434-43C2-886C-57852CC8A120}",
+            "/factory,{ceff45ee-c862-41de-aee2-a022c81eda92}"
+          )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,49 +90,39 @@ Noisy CLSID_SeparateSingleProcessExplorerHost Explorer COM Class IDs
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[suspicious-explorer-child-process-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and (
-process.name : ("cscript.exe", "wscript.exe", "powershell.exe",
-"rundll32.exe", "cmd.exe", "mshta.exe", "regsvr32.exe") or
-process.pe.original_file_name in ("cscript.exe", "wscript.exe",
-"PowerShell.EXE", "RUNDLL32.EXE", "Cmd.Exe", "MSHTA.EXE",
-"REGSVR32.EXE") ) and /* Explorer started via DCOM */
-process.parent.name : "explorer.exe" and process.parent.args :
-"-Embedding" and not process.parent.args: ( /*
-Noisy CLSID_SeparateSingleProcessExplorerHost Explorer COM Class IDs
-*/ "/factory,{5BD95610-9434-43C2-886C-57852CC8A120}",
-"/factory,{ceff45ee-c862-41de-aee2-a022c81eda92}" )
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : ("cscript.exe", "wscript.exe", "powershell.exe",
-"rundll32.exe", "cmd.exe", "mshta.exe", "regsvr32.exe") and /*
-Explorer started via DCOM */ process.parent.name : "explorer.exe"
-and process.parent.args : "-Embedding"
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
+* Sub-technique:
+** Name: Visual Basic
+** ID: T1059.005
+** Reference URL: https://attack.mitre.org/techniques/T1059/005/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-file-changes-activity-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-file-changes-activity-detected.asciidoc
new file mode 100644
index 0000000000..451cc7371f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-file-changes-activity-detected.asciidoc
@@ -0,0 +1,108 @@
+[[suspicious-file-changes-activity-detected]]
+=== Suspicious File Changes Activity Detected
+
+This rule identifies a sequence of 100 file extension rename events within a set of common file paths by the same process in a timespan of 1 second. Ransomware is a type of malware that encrypts a victim's files or systems and demands payment (usually in cryptocurrency) in exchange for the decryption key. One important indicator of a ransomware attack is the mass encryption of the file system, after which a new file extension is added to the file.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Impact
+* Data Source: Elastic Defend
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by process.entity_id, host.id with maxspan=1s
+  [file where host.os.type == "linux" and event.type == "change" and event.action == "rename" and file.extension : "?*" 
+   and process.executable : ("./*", "/tmp/*", "/var/tmp/*", "/dev/shm/*", "/var/run/*", "/boot/*", "/srv/*", "/run/*") and
+   file.path : (
+     "/home/*/Downloads/*", "/home/*/Documents/*", "/root/*", "/bin/*", "/usr/bin/*", "/var/log/*", "/var/lib/log/*",
+     "/var/backup/*", "/var/www/*"
+   ) and
+   not process.name : (
+     "dpkg", "yum", "dnf", "rpm", "dockerd", "go", "java", "pip*", "python*", "node", "containerd", "php", "p4d",
+     "conda", "chrome", "imap", "cmake", "firefox", "semanage", "semodule", "ansible-galaxy", "fc-cache", "jammy", "git",
+     "systemsettings", "vmis-launcher", "bundle", "kudu-tserver", "suldownloader"
+    )
+   ] with runs=25
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Data Encrypted for Impact
+** ID: T1486
+** Reference URL: https://attack.mitre.org/techniques/T1486/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-file-creation-in-etc-for-persistence.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-file-creation-in-etc-for-persistence.asciidoc
index dc91f4f3ae..4e93a58f17 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-file-creation-in-etc-for-persistence.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-file-creation-in-etc-for-persistence.asciidoc
@@ -1,63 +1,193 @@
 [[suspicious-file-creation-in-etc-for-persistence]]
 === Suspicious File Creation in /etc for Persistence
 
-Detects the manual creation of files in specific etc directories, via user root, used by Linux malware to persist and elevate privileges on compromised systems. File creation in these directories should not be entirely common and could indicate a malicious binary or script installing persistence for long term access.
+Detects the manual creation of files in specific etc directories, via user root, used by Linux malware to persist and elevate privileges on compromised systems. File creation in these directories should not be entirely common and could indicate a malicious binary or script installing persistence mechanisms for long term access.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-*
+* logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.intezer.com/blog/incident-response/orbit-new-undetected-linux-threat/
 * https://www.intezer.com/blog/research/lightning-framework-new-linux-threat/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Threat: Orbit
+* Threat: Lightning Framework
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 113
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Persistence
-* Orbit
-* Lightning Framework
 
-*Version*: 101 (<<suspicious-file-creation-in-etc-for-persistence-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 8.4.0
+==== Investigation guide
 
-*Last modified ({stack} release)*: 8.6.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Triage and analysis*
+
+
+
+*Investigating Suspicious File Creation in /etc for Persistence*
+
+
+The /etc/ directory in Linux is used to store system-wide configuration files and scripts.
+
+By creating or modifying specific system-wide configuration files, attackers can leverage system services to execute malicious commands or scripts at predefined intervals, ensuring their continued presence and enabling unauthorized activities.
+
+This rule monitors for the creation of the most common system-wide configuration files and scripts abused by attackers for persistence. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible Investigation Steps*
+
+
+- Investigate the file that was created or modified.
+- Investigate whether any other files in any of the commonly abused directories have been altered through OSQuery.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE (\n  path LIKE '/etc/ld.so.conf.d/%' OR\n  path LIKE '/etc/cron.d/%' OR\n  path LIKE '/etc/sudoers.d/%' OR\n  path LIKE '/etc/rc%.d/%' OR\n  path LIKE '/etc/init.d/%' OR\n  path LIKE '/etc/systemd/system/%' OR\n  path LIKE '/usr/lib/systemd/system/%'\n)\n"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE (\n  path LIKE '/etc/ld.so.conf.d/%' OR\n  path LIKE '/etc/cron.d/%' OR\n  path LIKE '/etc/sudoers.d/%' OR\n  path LIKE '/etc/rc%.d/%' OR\n  path LIKE '/etc/init.d/%' OR\n  path LIKE '/etc/systemd/system/%' OR\n  path LIKE '/usr/lib/systemd/system/%'\n)\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+    - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+    - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+
+
+*False Positive Analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator that performed these actions for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Related Rules*
+
+
+- Cron Job Created or Changed by Previously Unknown Process - ff10d4d8-fea7-422d-afb1-e5a2702369a9
+- Potential Persistence Through Run Control Detected - 0f4d35e4-925e-4959-ab24-911be207ee6f
+- Potential Persistence Through init.d Detected - 474fd20e-14cc-49c5-8160-d9ab4ba16c8b
+- New Systemd Timer Created - 7fb500fa-8e24-4bd1-9480-2a819352602c
+- New Systemd Service Created by Previously Unknown Process - 17b0a495-4d9f-414c-8ad0-92f018b8e001
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Delete the service/timer or restore its original configuration.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.action == "creation" and user.name == "root" and
-file.path : ("/etc/ld.so.conf.d/*", "/etc/cron.d/*",
-"/etc/sudoers.d/*", "/etc/rc.d/init.d/*", "/etc/systemd/system/*") and
-not process.executable : ("*/dpkg", "*/yum", "*/apt", "*/dnf",
-"*/systemd", "*/snapd", "*/dnf-automatic", "*/yum-cron", "*/elastic-
-agent", "*/dnfdaemon-system")
+[source, js]
 ----------------------------------
+file where host.os.type == "linux" and event.type in ("creation", "file_create_event") and user.id == "0" and
+file.path : ("/etc/ld.so.conf.d/*", "/etc/cron.d/*", "/etc/sudoers.d/*", "/etc/rc.d/init.d/*", "/etc/systemd/system/*",
+"/usr/lib/systemd/system/*") and not (
+  (process.name : (
+    "chef-client", "ruby", "pacman", "packagekitd", "python*", "platform-python", "dpkg", "yum", "apt", "dnf", "rpm",
+    "systemd", "snapd", "dnf-automatic", "yum-cron", "elastic-agent", "dnfdaemon-system", "dockerd", "executor",
+    "rhn_check"
+    )
+  ) or 
+  (file.extension in ("swp", "swpx", "tmp"))
+)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -69,8 +199,26 @@ agent", "*/dnfdaemon-system")
 ** Name: Boot or Logon Initialization Scripts
 ** ID: T1037
 ** Reference URL: https://attack.mitre.org/techniques/T1037/
-
-
+* Sub-technique:
+** Name: RC Scripts
+** ID: T1037.004
+** Reference URL: https://attack.mitre.org/techniques/T1037/004/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: Dynamic Linker Hijacking
+** ID: T1574.006
+** Reference URL: https://attack.mitre.org/techniques/T1574/006/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Systemd Service
+** ID: T1543.002
+** Reference URL: https://attack.mitre.org/techniques/T1543/002/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -79,8 +227,10 @@ agent", "*/dnfdaemon-system")
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-
+* Sub-technique:
+** Name: Cron
+** ID: T1053.003
+** Reference URL: https://attack.mitre.org/techniques/T1053/003/
 * Tactic:
 ** Name: Privilege Escalation
 ** ID: TA0004
@@ -89,22 +239,7 @@ agent", "*/dnfdaemon-system")
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[suspicious-file-creation-in-etc-for-persistence-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.action == "creation" and user.name == "root" and
-file.path : ("/etc/ld.so.conf.d/*", "/etc/cron.d/*",
-"/etc/sudoers.d/*", "/etc/rc.d/init.d/*", "/etc/systemd/system/*") and
-not process.executable : ("*/dpkg", "*/yum", "*/apt", "*/dnf",
-"*/systemd")
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Sudo and Sudo Caching
+** ID: T1548.003
+** Reference URL: https://attack.mitre.org/techniques/T1548/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-file-creation-via-kworker.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-file-creation-via-kworker.asciidoc
new file mode 100644
index 0000000000..997877ed70
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-file-creation-via-kworker.asciidoc
@@ -0,0 +1,192 @@
+[[suspicious-file-creation-via-kworker]]
+=== Suspicious File Creation via Kworker
+
+This rule monitors for a file creation event originating from a kworker parent process. kworker, or kernel worker, processes are part of the kernel's workqueue mechanism. They are responsible for executing work that has been scheduled to be done in kernel space, which might include tasks like handling interrupts, background activities, and other kernel-related tasks. Attackers may attempt to evade detection by masquerading as a kernel worker process.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Suspicious File Creation via Kworker*
+
+
+Kworker, or kernel worker, processes are part of the kernel's workqueue mechanism. They are responsible for executing work that has been scheduled to be done in kernel space, which might include tasks like handling interrupts, background activities, and other kernel-related tasks.
+
+Attackers may attempt to evade detection by masquerading as a kernel worker process.
+
+This rule monitors for suspicious file creation events through the kworker process. This is not common, and could indicate malicious behaviour.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible Investigation Steps*
+
+
+- Investigate the file that was created or modified through OSQuery.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE path = {{file.path}}\n"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE path = {{file.path}}\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
+  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+    - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+    - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+
+
+*False Positive Analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator that performed these actions for administrative purposes, consider adding exceptions for this specific administrator user account. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Related Rules*
+
+
+- Suspicious Kworker UID Elevation - 7dfaaa17-425c-4fe7-bd36-83705fde7c2b
+- Network Activity Detected via Kworker - 25d917c4-aa3c-4111-974c-286c0312ff95
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click Add integrations.
+- In the query bar, search for Elastic Defend and select the integration to see more details about it.
+- Click Add Elastic Defend.
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either Traditional Endpoints or Cloud Workloads.
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in New agent policy name. If other agent policies already exist, you can click the Existing hosts tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click Save and Continue.
+- To complete the integration, select Add Elastic Agent to your hosts and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where event.action in ("creation", "file_create_event") and process.name : "kworker*" and not (
+  (process.name : "kworker*kcryptd*") or 
+  (file.path : ("/var/log/*", "/var/crash/*", "/var/run/*", "/var/lib/systemd/coredump/*", "/var/spool/*"))
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Rootkit
+** ID: T1014
+** Reference URL: https://attack.mitre.org/techniques/T1014/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-file-downloaded-from-google-drive.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-file-downloaded-from-google-drive.asciidoc
new file mode 100644
index 0000000000..bb6b44e3bd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-file-downloaded-from-google-drive.asciidoc
@@ -0,0 +1,75 @@
+[[suspicious-file-downloaded-from-google-drive]]
+=== Suspicious File Downloaded from Google Drive
+
+Identifies suspicious file download activity from a Google Drive URL. This could indicate an attempt to deliver phishing payloads via a trusted webservice.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-endpoint*
+* logs-system.security*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://intelligence.abnormalsecurity.com/blog/google-drive-matanbuchus-malware
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* OS: Windows
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Command and Control
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where
+
+    /* common browser processes  */
+    event.action in ("exec", "fork", "start") and 
+
+    process.name : ("Microsoft Edge", "chrome.exe", "Google Chrome", "google-chrome-stable", 
+                    "google-chrome-beta", "google-chrome", "msedge.exe", "firefox.exe", "brave.exe", 
+                    "whale.exe", "browser.exe", "dragon.exe", "vivaldi.exe", "opera.exe", "firefox", 
+                    "powershell.exe", "curl", "curl.exe", "wget", "wget.exe") and 
+
+    /* Look for Google Drive download URL with AV flag skipping */
+    (process.command_line : "*drive.google.com*" and process.command_line : "*export=download*" and process.command_line : "*confirm=no_antivirus*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Ingress Tool Transfer
+** ID: T1105
+** Reference URL: https://attack.mitre.org/techniques/T1105/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-file-renamed-via-smb.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-file-renamed-via-smb.asciidoc
new file mode 100644
index 0000000000..1823af63b6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-file-renamed-via-smb.asciidoc
@@ -0,0 +1,138 @@
+[[suspicious-file-renamed-via-smb]]
+=== Suspicious File Renamed via SMB
+
+Identifies an incoming SMB connection followed by a suspicious file rename operation. This may indicate a remote ransomware attack via the SMB protocol.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://news.sophos.com/en-us/2023/12/21/akira-again-the-ransomware-that-keeps-on-taking/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Performance*
+
+
+- This rule may cause medium to high performance impact due to logic scoping all icoming SMB network events.
+
+
+*Possible investigation steps*
+
+
+- Investigate the source.ip address connecting to port 445 on this host.
+- Identify the user account that performed the file creation via SMB.
+- If the number of files is too high and source.ip connecting over SMB is unusual isolate the host and block the used credentials.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Remote file rename over SMB.
+
+
+*Related rules*
+
+
+- Third-party Backup Files Deleted via Unexpected Process - 11ea6bec-ebde-4d71-a8e9-784948f8e3e9
+- Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
+- Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
+- Volume Shadow Copy Deletion via WMIC - dc9c1f74-dac3-48e3-b47f-eb79db358f57
+- Potential Ransomware Note File Dropped via SMB - 02bab13d-fb14-4d7c-b6fe-4a28874d37c5
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If any other destructive action was identified on the host, it is recommended to prioritize the investigation and look for ransomware preparation and execution activities.
+- If any backups were affected:
+  - Perform data recovery locally or restore the backups from replicated copies (cloud, other servers, etc.).
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=1s
+ [network where host.os.type == "windows" and
+  event.action == "connection_accepted" and destination.port == 445 and source.port >= 49152 and process.pid == 4 and
+  source.ip != "127.0.0.1" and source.ip != "::1"]
+ [file where host.os.type == "windows" and
+  event.action == "rename" and process.pid == 4 and user.id : ("S-1-5-21*", "S-1-12-*") and
+  file.extension != null and file.Ext.entropy >= 6 and
+  file.Ext.original.name : ("*.jpg", "*.bmp", "*.png", "*.pdf", "*.doc", "*.docx", "*.xls", "*.xlsx", "*.ppt", "*.pptx", "*.lnk") and
+  not file.extension : ("jpg", "bmp", "png", "pdf", "doc", "docx", "xls", "xlsx", "ppt", "pptx", "*.lnk")] with runs=3
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Inhibit System Recovery
+** ID: T1490
+** Reference URL: https://attack.mitre.org/techniques/T1490/
+* Technique:
+** Name: Data Destruction
+** ID: T1485
+** Reference URL: https://attack.mitre.org/techniques/T1485/
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-hidden-child-process-of-launchd.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-hidden-child-process-of-launchd.asciidoc
index 6488bac384..3c60df9739 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-hidden-child-process-of-launchd.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-hidden-child-process-of-launchd.asciidoc
@@ -5,56 +5,90 @@ Identifies the execution of a launchd child process with a hidden file. An adver
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://objective-see.com/blog/blog_0x61.html
 * https://www.intezer.com/blog/research/operation-electrorat-attacker-creates-fake-companies-to-drain-your-crypto-wallets/
 * https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
-* Defense Evasion
 
-*Version*: 100 (<<suspicious-hidden-child-process-of-launchd-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:.* and process.parent.executable:/sbin/launchd
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+ process.name:.* and process.parent.executable:/sbin/launchd
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,8 +100,10 @@ process.name:.* and process.parent.executable:/sbin/launchd
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-
+* Sub-technique:
+** Name: Launch Agent
+** ID: T1543.001
+** Reference URL: https://attack.mitre.org/techniques/T1543/001/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -76,13 +112,7 @@ process.name:.* and process.parent.executable:/sbin/launchd
 ** Name: Hide Artifacts
 ** ID: T1564
 ** Reference URL: https://attack.mitre.org/techniques/T1564/
-
-[[suspicious-hidden-child-process-of-launchd-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Hidden Files and Directories
+** ID: T1564.001
+** Reference URL: https://attack.mitre.org/techniques/T1564/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-html-file-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-html-file-creation.asciidoc
index 00a584d6c5..de740c52d6 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-html-file-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-html-file-creation.asciidoc
@@ -5,74 +5,82 @@ Identifies the execution of a browser process to open an HTML file with high ent
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.file-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Initial Access
+*Tags*: 
 
-*Version*: 100 (<<suspicious-html-file-creation-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by user.id with maxspan=5m [file where event.action in
-("creation", "rename") and file.extension : ("htm", "html") and
-file.path : ("?:\\Users\\*\\Downloads\\*",
-"?:\\Users\\*\\Content.Outlook\\*",
-"?:\\Users\\*\\AppData\\Local\\Temp\\Temp?_*",
-"?:\\Users\\*\\AppData\\Local\\Temp\\7z*",
-"?:\\Users\\*\\AppData\\Local\\Temp\\Rar$*") and ((file.Ext.entropy
->= 5 and file.size >= 150000) or file.size >= 1000000)] [process
-where event.action == "start" and ( (process.name in
-("chrome.exe", "msedge.exe", "brave.exe", "whale.exe", "browser.exe",
-"dragon.exe", "vivaldi.exe", "opera.exe") and process.args == "--
-single-argument") or (process.name == "iexplore.exe" and
-process.args_count == 2) or (process.name in ("firefox.exe",
-"waterfox.exe") and process.args == "-url") ) and process.args :
-("?:\\Users\\*\\Downloads\\*.htm*",
-"?:\\Users\\*\\Content.Outlook\\*.htm*",
-"?:\\Users\\*\\AppData\\Local\\Temp\\Temp?_*.htm*",
-"?:\\Users\\*\\AppData\\Local\\Temp\\7z*.htm*",
-"?:\\Users\\*\\AppData\\Local\\Temp\\Rar$*.htm*")]
+[source, js]
 ----------------------------------
+sequence by user.id with maxspan=5m
+ [file where host.os.type == "windows" and event.action in ("creation", "rename") and
+  file.extension : ("htm", "html") and
+   file.path : ("?:\\Users\\*\\Downloads\\*",
+                "?:\\Users\\*\\Content.Outlook\\*",
+                "?:\\Users\\*\\AppData\\Local\\Temp\\Temp?_*",
+                "?:\\Users\\*\\AppData\\Local\\Temp\\7z*",
+                "?:\\Users\\*\\AppData\\Local\\Temp\\Rar$*") and
+   ((file.Ext.entropy >= 5 and file.size >= 150000) or file.size >= 1000000)]
+ [process where host.os.type == "windows" and event.action == "start" and
+  (
+   (process.name in ("chrome.exe", "msedge.exe", "brave.exe", "whale.exe", "browser.exe", "dragon.exe", "vivaldi.exe", "opera.exe")
+    and process.args == "--single-argument") or
+   (process.name == "iexplore.exe" and process.args_count == 2) or
+   (process.name in ("firefox.exe", "waterfox.exe") and process.args == "-url")
+  )
+  and process.args : ("?:\\Users\\*\\Downloads\\*.htm*",
+                      "?:\\Users\\*\\Content.Outlook\\*.htm*",
+                      "?:\\Users\\*\\AppData\\Local\\Temp\\Temp?_*.htm*",
+                      "?:\\Users\\*\\AppData\\Local\\Temp\\7z*.htm*",
+                      "?:\\Users\\*\\AppData\\Local\\Temp\\Rar$*.htm*")]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,8 +92,14 @@ process.args_count == 2) or (process.name in ("firefox.exe",
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -94,10 +108,7 @@ process.args_count == 2) or (process.name in ("firefox.exe",
 ** Name: Obfuscated Files or Information
 ** ID: T1027
 ** Reference URL: https://attack.mitre.org/techniques/T1027/
-
-[[suspicious-html-file-creation-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: HTML Smuggling
+** ID: T1027.006
+** Reference URL: https://attack.mitre.org/techniques/T1027/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-image-load-taskschd-dll-from-ms-office.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-image-load-taskschd-dll-from-ms-office.asciidoc
new file mode 100644
index 0000000000..3b2e5dc397
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-image-load-taskschd-dll-from-ms-office.asciidoc
@@ -0,0 +1,182 @@
+[[suspicious-image-load-taskschd-dll-from-ms-office]]
+=== Suspicious Image Load (taskschd.dll) from MS Office
+
+Identifies a suspicious image load (taskschd.dll) from Microsoft Office processes. This behavior may indicate adversarial activity where a scheduled task is configured via Windows Component Object Model (COM). This technique can be used to configure persistence and evade monitoring by avoiding the usage of the traditional Windows binary (schtasks.exe) used to manage scheduled tasks.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.library-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://medium.com/threatpunter/detecting-adversary-tradecraft-with-image-load-event-logging-and-eql-8de93338c16
+* https://www.clearskysec.com/wp-content/uploads/2020/10/Operation-Quicksand.pdf
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 109
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Suspicious Image Load (taskschd.dll) from MS Office*
+
+
+Microsoft Office, a widely used suite of productivity applications, is frequently targeted by attackers due to its popularity in corporate environments. These attackers exploit its extensive capabilities, like macro scripts in Word and Excel, to gain initial access to systems. They often use Office documents as delivery mechanisms for malware or phishing attempts, taking advantage of their trusted status in professional settings.
+
+`taskschd.dll` provides Command Object Model (COM) interfaces for the Windows Task Scheduler service, allowing developers to programmatically manage scheduled tasks.
+
+This rule looks for an MS Office process loading `taskschd.dll`, which may indicate an adversary abusing COM to configure a scheduled task. This can happen as part of a phishing attack, when a malicious office document registers the scheduled task to download the malware "stage 2" or to establish persistent access.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Analyze the host's scheduled tasks and explore the related Windows events to determine if tasks were created or deleted (Event IDs 4698 and 4699).
+- Investigate any abnormal behavior by the subject process, such as network connections, registry or file modifications, and spawned child processes.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Inspect the host for suspicious or abnormal behavior in the alert timeframe.
+- Examine the files downloaded during the past 24 hours.
+  - Identify files that are related or can be executed in MS Office.
+  - Identify and analyze macros that these documents contain.
+    - Identify suspicious traits in the office macros, such as encoded or encrypted sections.
+- Retrieve the suspicious files identified in the previous step and determine if they are malicious:
+  - Analyze the file using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+
+
+*Related Rules*
+
+
+- Suspicious WMI Image Load from MS Office - 891cb88e-441a-4c3e-be2d-120d99fe7b0d
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+  - If the malicious file was delivered via phishing:
+    - Block the email sender from sending future emails.
+    - Block the malicious web pages.
+    - Remove emails from the sender from mailboxes.
+    - Consider improvements to the security awareness program.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+any where host.os.type == "windows" and
+ (event.category : ("library", "driver") or (event.category == "process" and event.action : "Image loaded*")) and
+  process.name : ("WINWORD.EXE", "EXCEL.EXE", "POWERPNT.EXE", "MSPUB.EXE", "MSACCESS.EXE") and
+  (?dll.name : "taskschd.dll" or file.name : "taskschd.dll")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-imagepath-service-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-imagepath-service-creation.asciidoc
index 1a16ee3cfc..d1d7c02b29 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-imagepath-service-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-imagepath-service-creation.asciidoc
@@ -5,50 +5,57 @@ Identifies the creation of a suspicious ImagePath value. This could be an indica
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 100 (<<suspicious-imagepath-service-creation-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.path :
-"HKLM\\SYSTEM\\ControlSet*\\Services\\*\\ImagePath" and /* add
-suspicious registry ImagePath values here */ registry.data.strings :
-("%COMSPEC%*", "*\\.\\pipe\\*")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and registry.path : (
+    "HKLM\\SYSTEM\\ControlSet*\\Services\\*\\ImagePath",
+    "\\REGISTRY\\MACHINE\\SYSTEM\\ControlSet*\\Services\\*\\ImagePath"
+    ) and
+ /* add suspicious registry ImagePath values here */
+    registry.data.strings : ("%COMSPEC%*", "*\\.\\pipe\\*")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -60,22 +67,15 @@ suspicious registry ImagePath values here */ registry.data.strings :
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[suspicious-imagepath-service-creation-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.1.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-inter-process-communication-via-outlook.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-inter-process-communication-via-outlook.asciidoc
new file mode 100644
index 0000000000..629d7ff1a4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-inter-process-communication-via-outlook.asciidoc
@@ -0,0 +1,91 @@
+[[suspicious-inter-process-communication-via-outlook]]
+=== Suspicious Inter-Process Communication via Outlook
+
+Detects Inter-Process Communication with Outlook via Component Object Model from an unusual process. Adversaries may target user email to collect sensitive information or send email on their behalf via API.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/center-for-threat-informed-defense/adversary_emulation_library/blob/master/apt29/Archive/CALDERA_DIY/evals/payloads/stepSeventeen_email.ps1
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Collection
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence with maxspan=1m
+[process where host.os.type == "windows" and event.action == "start" and
+  (
+    process.name : (
+      "rundll32.exe", "mshta.exe", "powershell.exe", "pwsh.exe",
+      "cmd.exe", "regsvr32.exe", "cscript.exe", "wscript.exe"
+    ) or
+    (
+      (process.code_signature.trusted == false or process.code_signature.exists == false) and 
+      (process.Ext.relative_file_creation_time <= 500 or process.Ext.relative_file_name_modify_time <= 500)
+    )
+  )
+] by process.executable
+[process where host.os.type == "windows" and event.action == "start" and process.name : "OUTLOOK.EXE" and
+  process.Ext.effective_parent.name != null] by process.Ext.effective_parent.executable
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Email Collection
+** ID: T1114
+** Reference URL: https://attack.mitre.org/techniques/T1114/
+* Sub-technique:
+** Name: Local Email Collection
+** ID: T1114.001
+** Reference URL: https://attack.mitre.org/techniques/T1114/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Inter-Process Communication
+** ID: T1559
+** Reference URL: https://attack.mitre.org/techniques/T1559/
+* Sub-technique:
+** Name: Component Object Model
+** ID: T1559.001
+** Reference URL: https://attack.mitre.org/techniques/T1559/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-interactive-shell-spawned-from-inside-a-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-interactive-shell-spawned-from-inside-a-container.asciidoc
new file mode 100644
index 0000000000..1f240d21ef
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-interactive-shell-spawned-from-inside-a-container.asciidoc
@@ -0,0 +1,72 @@
+[[suspicious-interactive-shell-spawned-from-inside-a-container]]
+=== Suspicious Interactive Shell Spawned From Inside A Container
+
+This rule detects when an interactive shell is spawned inside a running container. This could indicate a potential container breakout attempt or an attacker's attempt to gain unauthorized access to the underlying host.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where container.id: "*" and
+event.type== "start" and 
+
+/*D4C consolidates closely spawned event.actions, this excludes end actions to only capture ongoing processes*/
+event.action in ("fork", "exec") and event.action != "end"
+ and process.entry_leader.same_as_process== false and
+(
+(process.executable: "*/*sh" and process.args: ("-i", "-it")) or
+process.args: "*/*sh"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-java-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-java-child-process.asciidoc
index b76ab6c248..6e7f143658 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-java-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-java-child-process.asciidoc
@@ -3,9 +3,9 @@
 
 Identifies suspicious child processes of the Java interpreter process. This may indicate an attempt to execute a malicious JAR file or an exploitation attempt via a JAVA specific vulnerability.
 
-*Rule type*: eql
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,13 +14,13 @@ Identifies suspicious child processes of the Java interpreter process. This may
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.lunasec.io/docs/blog/log4j-zero-day/
 * https://github.com/christophetd/log4shell-vulnerable-app
@@ -28,82 +28,97 @@ Identifies suspicious child processes of the Java interpreter process. This may
 * https://www.elastic.co/security-labs/detecting-log4j2-with-elastic-security
 * https://www.elastic.co/security-labs/analysis-of-log4shell-cve-2021-45046
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* macOS
-* Threat Detection
-* Execution
-* Investigation Guide
-
-*Version*: 102 (<<suspicious-java-child-process-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 208
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious Java Child Process
+*Triage and analysis*
+
+
+
+*Investigating Suspicious Java Child Process*
+
+
+This rule identifies a suspicious child process of the Java interpreter process. It may indicate an attempt to execute a malicious JAR file or an exploitation attempt via a Java specific vulnerability.
 
-This rule identifies a suspicious child process of the Java interpreter process. It may indicate an attempt to execute
-a malicious JAR file or an exploitation attempt via a Java specific vulnerability.
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence and whether they are located in expected locations.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
-- Investigate any abnormal behavior by the subject process such as network connections, file modifications, and any
-spawned child processes.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+- Investigate any abnormal behavior by the subject process such as network connections, file modifications, and any spawned child processes.
 - Examine the command line to determine if the command executed is potentially harmful or malicious.
 - Inspect the host for suspicious or abnormal behavior in the alert timeframe.
 
-### False positive analysis
 
-- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination
-of process and command line conditions.
+*False positive analysis*
+
+
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of process and command line conditions.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "java" and process.name : ("sh", "bash",
-"dash", "ksh", "tcsh", "zsh", "curl", "wget")
+[source, js]
 ----------------------------------
+event.category:process and event.type:("start" or "process_started") and process.parent.name:"java" and process.name:(
+  bash or dash or sh or tcsh or csh or zsh or ksh or fish or python* or php* or perl or ruby or lua* or openssl or
+  nc or netcat or ncat or telnet or awk or socat or wget or curl
+) and process.args :(
+  whoami or id or uname or cat or hostname or ip or curl or wget or pwd or ls or cd or python* or php* or perl or
+  ruby or lua* or openssl or nc or netcat or ncat or telnet or awk or socat
+)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -115,38 +130,7 @@ process.parent.name : "java" and process.name : ("sh", "bash",
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[suspicious-java-child-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (8.0.0 release)::
-* Rule name changed from: Suspicious JAR Child Process
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "java" and process.name : ("sh", "bash",
-"dash", "ksh", "tcsh", "zsh", "curl", "wget") and process.args :
-"-jar" and process.args : "*.jar" and /* Add any FP's here */ not
-process.executable : ("/Users/*/.sdkman/*",
-"/Library/Java/JavaVirtualMachines/*") and not process.args :
-("/usr/local/*", "/Users/*/github.com/*", "/Users/*/src/*")
-----------------------------------
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: JavaScript
+** ID: T1059.007
+** Reference URL: https://attack.mitre.org/techniques/T1059/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-jetbrains-teamcity-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-jetbrains-teamcity-child-process.asciidoc
new file mode 100644
index 0000000000..4f8cbf744c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-jetbrains-teamcity-child-process.asciidoc
@@ -0,0 +1,98 @@
+[[suspicious-jetbrains-teamcity-child-process]]
+=== Suspicious JetBrains TeamCity Child Process
+
+Identifies suspicious processes being spawned by the JetBrain TeamCity process. This activity could be related to JetBrains remote code execution vulnerabilities.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* winlogbeat-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.trendmicro.com/en_us/research/24/c/teamcity-vulnerability-exploits-lead-to-jasmin-ransomware.html
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Data Source: Elastic Endgame
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.executable :
+                 ("?:\\TeamCity\\jre\\bin\\java.exe",
+                  "?:\\Program Files\\TeamCity\\jre\\bin\\java.exe",
+                  "?:\\Program Files (x86)\\TeamCity\\jre\\bin\\java.exe",
+                  "?:\\TeamCity\\BuildAgent\\jre\\bin\\java.exe") and
+  process.name : ("cmd.exe", "powershell.exe", "msiexec.exe", "certutil.exe", "bitsadmin.exe", "wmic.exe", "curl.exe", "ssh.exe",
+                   "rundll32.exe", "regsvr32.exe", "mshta.exe", "certreq.exe", "net.exe", "nltest.exe", "whoami.exe", "hostname.exe",
+                   "tasklist.exe", "arp.exe", "nbtstat.exe", "netstat.exe", "reg.exe", "tasklist.exe", "Microsoft.Workflow.Compiler.exe",
+                   "arp.exe", "atbroker.exe", "bginfo.exe", "bitsadmin.exe", "cdb.exe", "cmstp.exe", "control.exe", "cscript.exe", "csi.exe",
+                   "dnx.exe", "dsget.exe", "dsquery.exe", "forfiles.exe", "fsi.exe", "ftp.exe", "gpresult.exe", "ieexec.exe", "iexpress.exe",
+                   "installutil.exe", "ipconfig.exe","msxsl.exe", "netsh.exe", "odbcconf.exe", "ping.exe", "pwsh.exe", "qprocess.exe",
+                   "quser.exe", "qwinsta.exe", "rcsi.exe", "regasm.exe", "regsvcs.exe", "regsvr32.exe", "sc.exe", "schtasks.exe",
+                   "systeminfo.exe", "tracert.exe", "wmic.exe", "wscript.exe","xwizard.exe", "explorer.exe", "msdt.exe") and
+ not (process.name : "powershell.exe" and process.args : "-ExecutionPolicy" and process.args : "?:\\TeamCity\\buildAgent\\work\\*.ps1") and
+ not (process.name : "cmd.exe" and process.args : "dir" and process.args : "/-c")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Exploit Public-Facing Application
+** ID: T1190
+** Reference URL: https://attack.mitre.org/techniques/T1190/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-kworker-uid-elevation.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-kworker-uid-elevation.asciidoc
new file mode 100644
index 0000000000..cc0bfc527d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-kworker-uid-elevation.asciidoc
@@ -0,0 +1,113 @@
+[[suspicious-kworker-uid-elevation]]
+=== Suspicious Kworker UID Elevation
+
+Monitors for the elevation of regular user permissions to root permissions through the kworker process. kworker, or kernel worker, processes are part of the kernel's workqueue mechanism. They are responsible for executing work that has been scheduled to be done in kernel space, which might include tasks like handling interrupts, background activities, and other kernel-related tasks. Attackers may attempt to evade detection by masquerading as a kernel worker process, and hijack the execution flow by hooking certain functions/syscalls through a rootkit in order to provide easy access to root via a special modified command.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click Add integrations.
+- In the query bar, search for Elastic Defend and select the integration to see more details about it.
+- Click Add Elastic Defend.
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either Traditional Endpoints or Cloud Workloads.
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in New agent policy name. If other agent policies already exist, you can click the Existing hosts tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click Save and Continue.
+- To complete the integration, select Add Elastic Agent to your hosts and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.action == "session_id_change" and process.name : "kworker*" and
+user.id == "0"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: KernelCallbackTable
+** ID: T1574.013
+** Reference URL: https://attack.mitre.org/techniques/T1574/013/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Rootkit
+** ID: T1014
+** Reference URL: https://attack.mitre.org/techniques/T1014/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-lsass-access-via-malseclogon.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-lsass-access-via-malseclogon.asciidoc
index 0405d46719..57bbc5d5ae 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-lsass-access-via-malseclogon.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-lsass-access-via-malseclogon.asciidoc
@@ -5,67 +5,71 @@ Identifies suspicious access to LSASS handle from a call trace pointing to seclo
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://splintercod3.blogspot.com/p/the-hidden-side-of-seclogon-part-3.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Sysmon Only
-
-*Version*: 101 (<<suspicious-lsass-access-via-malseclogon-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 8.4.0
+*Version*: 208
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.code == "10" and winlog.event_data.TargetImage :
-"?:\\WINDOWS\\system32\\lsass.exe" and /* seclogon service
-accessing lsass */ winlog.event_data.CallTrace : "*seclogon.dll*"
-and process.name : "svchost.exe" and /* PROCESS_CREATE_PROCESS &
-PROCESS_DUP_HANDLE & PROCESS_QUERY_INFORMATION */
-winlog.event_data.GrantedAccess == "0x14c0"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.code == "10" and
+  winlog.event_data.TargetImage : "?:\\WINDOWS\\system32\\lsass.exe" and
+
+   /* seclogon service accessing lsass */
+  winlog.event_data.CallTrace : "*seclogon.dll*" and process.name : "svchost.exe" and
 
-==== Threat mapping
+   /* PROCESS_CREATE_PROCESS & PROCESS_DUP_HANDLE & PROCESS_QUERY_INFORMATION */
+  winlog.event_data.GrantedAccess == "0x14c0"
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,13 +81,7 @@ winlog.event_data.GrantedAccess == "0x14c0"
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[suspicious-lsass-access-via-malseclogon-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-lsass-process-access.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-lsass-process-access.asciidoc
new file mode 100644
index 0000000000..53270c291a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-lsass-process-access.asciidoc
@@ -0,0 +1,103 @@
+[[suspicious-lsass-process-access]]
+=== Suspicious Lsass Process Access
+
+Identifies access attempts to LSASS handle, this may indicate an attempt to dump credentials from Lsass memory.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.sysmon_operational-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1003.001/T1003.001.md
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Sysmon
+
+*Version*: 107
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.code == "10" and
+  winlog.event_data.TargetImage : "?:\\WINDOWS\\system32\\lsass.exe" and
+  not winlog.event_data.GrantedAccess :
+                ("0x1000", "0x1400", "0x101400", "0x101000", "0x101001", "0x100000", "0x100040", "0x3200", "0x40", "0x3200") and
+  not process.name : ("procexp64.exe", "procmon.exe", "procexp.exe", "Microsoft.Identity.AadConnect.Health.AadSync.Host.ex") and
+  not process.executable : (
+        "?:\\ProgramData\\Microsoft\\Windows Defender\\platform\\*",
+        "?:\\ProgramData\\WebEx\\webex\\*",
+        "?:\\Program Files (x86)\\*",
+        "?:\\Program Files\\*",
+        "?:\\Windows\\CCM\\CcmExec.exe",
+        "?:\\Windows\\LTSvc\\LTSVC.exe",
+        "?:\\Windows\\Sysmon.exe",
+        "?:\\Windows\\Sysmon64.exe",
+        "?:\\Windows\\system32\\csrss.exe",
+        "?:\\Windows\\System32\\lsm.exe",
+        "?:\\Windows\\system32\\MRT.exe",
+        "?:\\Windows\\System32\\msiexec.exe",
+        "?:\\Windows\\system32\\wbem\\wmiprvse.exe",
+        "?:\\Windows\\system32\\wininit.exe",
+        "?:\\Windows\\SystemTemp\\GUM*.tmp\\GoogleUpdate.exe",
+        "?:\\Windows\\sysWOW64\\wbem\\wmiprvse.exe"
+  ) and
+  not winlog.event_data.CallTrace : ("*mpengine.dll*", "*appresolver.dll*", "*sysmain.dll*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-macos-ms-office-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-macos-ms-office-child-process.asciidoc
index e54233a6d8..1c72f39bb8 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-macos-ms-office-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-macos-ms-office-child-process.asciidoc
@@ -5,7 +5,7 @@ Identifies suspicious child processes of frequently targeted Microsoft Office ap
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * logs-endpoint.events.*
 
@@ -13,55 +13,144 @@ Identifies suspicious child processes of frequently targeted Microsoft Office ap
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.malwarebytes.com/cybercrime/2017/02/microsoft-office-macro-malware-targets-macs/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Initial Access
 
-*Version*: 100 (<<suspicious-macos-ms-office-child-process-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.12.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name:("Microsoft Word", "Microsoft PowerPoint",
-"Microsoft Excel") and process.name: ( "bash", "dash",
-"sh", "tcsh", "csh", "zsh", "ksh", "fish",
-"python*", "perl*", "php*", "osascript", "pwsh",
-"curl", "wget", "cp", "mv", "base64", "launchctl" )
-and /* noisy false positives related to product version discovery
-and office errors reporting */ not process.args: (
-"ProductVersion", "hw.model", "ioreg",
-"ProductName", "ProductUserVisibleVersion",
-"ProductBuildVersion", "/Library/Application
-Support/Microsoft/MERP*/Microsoft Error
-Reporting.app/Contents/MacOS/Microsoft Error Reporting" )
+[source, js]
 ----------------------------------
+process where event.action == "exec" and
+    process.parent.name: (
+      "Microsoft Word",
+      "Microsoft Outlook",
+      "Microsoft Excel",
+      "Microsoft PowerPoint",
+      "Microsoft OneNote"
+    ) and
+  process.name : (
+    "curl",
+    "nscurl",
+    "bash",
+    "sh",
+    "osascript",
+    "python*",
+    "perl*",
+    "mktemp",
+    "chmod",
+    "php",
+    "nohup",
+    "openssl",
+    "plutil",
+    "PlistBuddy",
+    "xattr",
+    "mktemp",
+    "sqlite3",
+    "funzip",
+    "popen"
+  ) and
+
+  // Filter FPs related to product version discovery and Office error reporting behavior
+  not process.args:
+    (
+      "ProductVersion",
+      "hw.model",
+      "ioreg",
+      "ProductName",
+      "ProductUserVisibleVersion",
+      "ProductBuildVersion",
+      "/Library/Application Support/Microsoft/MERP*/Microsoft Error Reporting.app/Contents/MacOS/Microsoft Error Reporting",
+      "open -a Safari *",
+      "defaults read *",
+      "sysctl hw.model*",
+      "ioreg -d2 -c IOPlatformExpertDevice *",
+      "ps aux | grep 'ToDesk_Desktop' | grep -v grep",
+      "PIPE=\"$CFFIXED_USER_HOME/.zoteroIntegrationPipe*"
+    ) and
+
+   not process.parent.executable :
+        (
+          "/Applications/ToDesk.app/Contents/MacOS/ToDesk_Service",
+          "/usr/local/Privacy-i/PISupervisor",
+          "/Library/Addigy/lan-cache",
+          "/Library/Elastic/Agent/*",
+          "/opt/jc/bin/jumpcloud-agent",
+          "/usr/sbin/networksetup"
+        ) and
+   not (process.name : "sh" and process.command_line : "*$CFFIXED_USER_HOME/.zoteroIntegrationPipe*") and
+
+   not process.Ext.effective_parent.executable : (
+        "/Applications/ToDesk.app/Contents/MacOS/ToDesk_Service",
+        "/usr/local/Privacy-i/PISupervisor",
+        "/Library/Addigy/auditor",
+        "/Library/Elastic/Agent/*",
+        "/opt/jc/bin/jumpcloud-agent",
+        "/usr/sbin/networksetup"
+      )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,44 +162,7 @@ Reporting.app/Contents/MacOS/Microsoft Error Reporting" )
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[suspicious-macos-ms-office-child-process-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name:("Microsoft Word", "Microsoft PowerPoint",
-"Microsoft Excel") and process.name: ( "bash", "dash",
-"sh", "tcsh", "csh", "zsh", "ksh", "fish",
-"python*", "perl*", "php*", "osascript", "pwsh",
-"curl", "wget", "cp", "mv", "base64", "launchctl"
-) and /* noisy false positives related to product version discovery
-and office errors reporting */ not process.args: (
-"ProductVersion", "hw.model", "ioreg",
-"ProductName", "ProductUserVisibleVersion",
-"ProductBuildVersion", "/Library/Application
-Support/Microsoft/MERP*/Microsoft Error
-Reporting.app/Contents/MacOS/Microsoft Error Reporting" )
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name:("Microsoft Word", "Microsoft PowerPoint",
-"Microsoft Excel") and process.name: ( "bash", "dash",
-"sh", "tcsh", "csh", "zsh", "ksh", "fish",
-"python*", "perl*", "php*", "osascript", "pwsh",
-"curl", "wget", "cp", "mv", "base64", "launchctl"
-)
-----------------------------------
-
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-managed-code-hosting-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-managed-code-hosting-process.asciidoc
index 2bf1088ef3..6e9933b893 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-managed-code-hosting-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-managed-code-hosting-process.asciidoc
@@ -5,60 +5,60 @@ Identifies a suspicious managed code hosting process which could indicate code i
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
-* https://web.archive.org/web/20230329154538/https://blog.menasec.net/2019/07/interesting-difr-traces-of-net-clr.html
+* http://web.archive.org/web/20230329154538/https://blog.menasec.net/2019/07/interesting-difr-traces-of-net-clr.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-
-*Version*: 100 (<<suspicious-managed-code-hosting-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id with maxspan=5m [process where
-event.type == "start" and process.name : ("wscript.exe",
-"cscript.exe", "mshta.exe", "wmic.exe", "regsvr32.exe", "svchost.exe",
-"dllhost.exe", "cmstp.exe")] [file where event.type != "deletion" and
-file.name : ("wscript.exe.log", "cscript.exe",
-"mshta.exe.log", "wmic.exe.log",
-"svchost.exe.log", "dllhost.exe.log",
-"cmstp.exe.log", "regsvr32.exe.log")]
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and
+  file.name : ("wscript.exe.log",
+               "cscript.exe.log",
+               "mshta.exe.log",
+               "wmic.exe.log",
+               "svchost.exe.log",
+               "dllhost.exe.log",
+               "cmstp.exe.log",
+               "regsvr32.exe.log")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -70,45 +70,3 @@ file.name : ("wscript.exe.log", "cscript.exe",
 ** Name: Process Injection
 ** ID: T1055
 ** Reference URL: https://attack.mitre.org/techniques/T1055/
-
-[[suspicious-managed-code-hosting-process-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan=5m [process where
-event.type == "start" and process.name : ("wscript.exe",
-"cscript.exe", "mshta.exe", "wmic.exe", "regsvr32.exe", "svchost.exe",
-"dllhost.exe", "cmstp.exe")] [file where event.type != "deletion" and
-file.name : ("wscript.exe.log", "cscript.exe",
-"mshta.exe.log", "wmic.exe.log",
-"svchost.exe.log", "dllhost.exe.log",
-"cmstp.exe.log", "regsvr32.exe.log")]
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and not event.type:deletion and
-file.name:(wscript.exe.log or mshta.exe.log or wscript.exe.log or
-wmic.exe.log or svchost.exe.log or dllhost.exe.log or cmstp.exe.log or
-regsvr32.exe.log)
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-memory-grep-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-memory-grep-activity.asciidoc
new file mode 100644
index 0000000000..b5b3811461
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-memory-grep-activity.asciidoc
@@ -0,0 +1,65 @@
+[[suspicious-memory-grep-activity]]
+=== Suspicious Memory grep Activity
+
+Monitors for grep activity related to memory mapping. The /proc/*/maps file in Linux provides a memory map for a specific process, detailing the memory segments, permissions, and what files are mapped to these segments. Attackers may read a process's memory map to identify memory addresses for code injection or process hijacking.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/arget13/DDexec
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
+process.name in ("grep", "egrep", "fgrep", "rgrep") and process.args in ("[stack]", "[vdso]", "[heap]")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Process Discovery
+** ID: T1057
+** Reference URL: https://attack.mitre.org/techniques/T1057/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-microsoft-365-mail-access-by-clientappid.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-microsoft-365-mail-access-by-clientappid.asciidoc
new file mode 100644
index 0000000000..6338c69f63
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-microsoft-365-mail-access-by-clientappid.asciidoc
@@ -0,0 +1,71 @@
+[[suspicious-microsoft-365-mail-access-by-clientappid]]
+=== Suspicious Microsoft 365 Mail Access by ClientAppId
+
+Identifies when a Microsoft 365 Mailbox is accessed by a ClientAppId that was observed for the fist time during the last 10 days.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* filebeat-*
+* logs-o365*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-193a
+
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: Microsoft 365
+* Use Case: Configuration Audit
+* Tactic: Initial Access
+
+*Version*: 105
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+
+==== Setup
+
+
+The Office 365 Logs Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.dataset:o365.audit and event.provider:Exchange and event.category:web and event.action:MailItemsAccessed and event.outcome:success
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Valid Accounts
+** ID: T1078
+** Reference URL: https://attack.mitre.org/techniques/T1078/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-microsoft-diagnostics-wizard-execution.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-microsoft-diagnostics-wizard-execution.asciidoc
index 1b6c4b4f89..b8c45959fe 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-microsoft-diagnostics-wizard-execution.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-microsoft-diagnostics-wizard-execution.asciidoc
@@ -5,9 +5,9 @@ Identifies potential abuse of the Microsoft Diagnostics Troubleshooting Wizard (
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
@@ -16,67 +16,69 @@ Identifies potential abuse of the Microsoft Diagnostics Troubleshooting Wizard (
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://twitter.com/nao_sec/status/1530196847679401984
 * https://lolbas-project.github.io/lolbas/Binaries/Msdt/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
-
-*Version*: 102 (<<suspicious-microsoft-diagnostics-wizard-execution-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 8.3.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and
-(process.pe.original_file_name == "msdt.exe" or process.name :
-"msdt.exe") and ( process.args : ("IT_RebrowseForFile=*", "ms-
-msdt:/id", "ms-msdt:-id", "*FromBase64*") or (process.args :
-"-af" and process.args : "/skip" and process.parent.name :
-("explorer.exe", "cmd.exe", "powershell.exe", "cscript.exe",
-"wscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe") and
-process.args : ("?:\\WINDOWS\\diagnostics\\index\\PCWDiagnostic.xml",
-"PCWDiagnostic.xml", "?:\\Users\\Public\\*", "?:\\Windows\\Temp\\*"))
-or (process.pe.original_file_name == "msdt.exe" and not
-process.name : "msdt.exe" and process.name != null) or
-(process.pe.original_file_name == "msdt.exe" and not
-process.executable : ("?:\\Windows\\system32\\msdt.exe",
-"?:\\Windows\\SysWOW64\\msdt.exe")) )
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+   (process.pe.original_file_name == "msdt.exe" or process.name : "msdt.exe") and
+   (
+    process.args : ("IT_RebrowseForFile=*", "ms-msdt:/id", "ms-msdt:-id", "*FromBase64*") or
 
-==== Threat mapping
+    (process.args : "-af" and process.args : "/skip" and
+     process.parent.name : ("explorer.exe", "cmd.exe", "powershell.exe", "cscript.exe", "wscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe") and
+     process.args : ("?:\\WINDOWS\\diagnostics\\index\\PCWDiagnostic.xml", "PCWDiagnostic.xml", "?:\\Users\\Public\\*", "?:\\Windows\\Temp\\*")) or
+
+    (process.pe.original_file_name == "msdt.exe" and not process.name : "msdt.exe" and process.name != null) or
+
+    (process.pe.original_file_name == "msdt.exe" and not process.executable : ("?:\\Windows\\system32\\msdt.exe", "?:\\Windows\\SysWOW64\\msdt.exe"))
+    )
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -88,52 +90,3 @@ process.executable : ("?:\\Windows\\system32\\msdt.exe",
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[suspicious-microsoft-diagnostics-wizard-execution-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.pe.original_file_name == "msdt.exe" or process.name :
-"msdt.exe") and ( process.args : ("IT_RebrowseForFile=*", "ms-
-msdt:/id", "ms-msdt:-id", "*FromBase64*") or (process.args :
-"-af" and process.args : "/skip" and process.parent.name :
-("explorer.exe", "cmd.exe", "powershell.exe", "cscript.exe",
-"wscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe") and
-process.args : ("?:\\WINDOWS\\diagnostics\\index\\PCWDiagnostic.xml",
-"PCWDiagnostic.xml", "?:\\Users\\Public\\*", "?:\\Windows\\Temp\\*"))
-or (process.pe.original_file_name == "msdt.exe" and not
-process.name : "msdt.exe" and process.name != null) or
-(process.pe.original_file_name == "msdt.exe" and not
-process.executable : ("?:\\Windows\\system32\\msdt.exe",
-"?:\\Windows\\SysWOW64\\msdt.exe")) )
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.pe.original_file_name == "msdt.exe" or process.name :
-"msdt.exe") and ( process.args : ("IT_RebrowseForFile=*", "ms-
-msdt:/id", "ms-msdt:-id", "*FromBase64*") or (process.args :
-"-af" and process.args : "/skip" and process.parent.name :
-("explorer.exe", "cmd.exe", "powershell.exe", "cscript.exe",
-"wscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe") and
-process.args : ("?:\\WINDOWS\\diagnostics\\index\\PCWDiagnostic.xml",
-"PCWDiagnostic.xml", "?:\\Users\\Public\\*", "?:\\Windows\\Temp\\*"))
-or (process.pe.original_file_name == "msdt.exe" and not
-process.name : "msdt.exe" and process.name != null) or
-(process.pe.original_file_name == "msdt.exe" and not
-process.executable : ("?:\\Windows\\system32\\msdt.exe",
-"?:\\Windows\\SysWOW64\\msdt.exe")) )
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-mining-process-creation-event.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-mining-process-creation-event.asciidoc
new file mode 100644
index 0000000000..988742890f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-mining-process-creation-event.asciidoc
@@ -0,0 +1,103 @@
+[[suspicious-mining-process-creation-event]]
+=== Suspicious Mining Process Creation Event
+
+Identifies service creation events of common mining services, possibly indicating the infection of a system with a cryptominer.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "linux" and event.type == "creation" and event.action : ("creation", "file_create_event") and 
+file.name : ("aliyun.service", "moneroocean_miner.service", "c3pool_miner.service", "pnsd.service", "apache4.service", "pastebin.service", "xvf.service")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-modprobe-file-event.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-modprobe-file-event.asciidoc
new file mode 100644
index 0000000000..0b4dbd6037
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-modprobe-file-event.asciidoc
@@ -0,0 +1,92 @@
+[[suspicious-modprobe-file-event]]
+=== Suspicious Modprobe File Event
+
+Detects file events involving kernel modules in modprobe configuration files, which may indicate unauthorized access or manipulation of critical kernel modules. Attackers may tamper with the modprobe files to load malicious or unauthorized kernel modules, potentially bypassing security measures, escalating privileges, or hiding their activities within the system.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+
+*Version*: 107
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires the use of the `auditd_manager` integration. `Auditd_manager` is a tool designed to simplify and enhance the management of the audit subsystem in Linux systems. It provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system. The following steps should be executed in order to install and deploy `auditd_manager` on a Linux system.
+
+```
+Kibana -->
+Management -->
+Integrations -->
+Auditd Manager -->
+Add Auditd Manager
+```
+
+`Auditd_manager` subscribes to the kernel and receives events as they occur without any additional configuration. However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+
+For this detection rule to trigger, the following additional audit rules are required to be added to the integration:
+```
+-w /etc/modprobe.conf -p wa -k modprobe
+-w /etc/modprobe.d -p wa -k modprobe
+```
+
+Add the newly installed `auditd manager` to an agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.category:file and event.action:"opened-file" and
+file.path : ("/etc/modprobe.conf" or "/etc/modprobe.d" or /etc/modprobe.d/*) and not process.name:(
+  cp or dpkg or dockerd or lynis or mkinitramfs or snapd or systemd-udevd or grep or borg or auditbeat or lspci or
+  aide or modprobe or python*
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-module-loaded-by-lsass.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-module-loaded-by-lsass.asciidoc
new file mode 100644
index 0000000000..8cbf34f688
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-module-loaded-by-lsass.asciidoc
@@ -0,0 +1,147 @@
+[[suspicious-module-loaded-by-lsass]]
+=== Suspicious Module Loaded by LSASS
+
+Identifies LSASS loading an unsigned or untrusted DLL. Windows Security Support Provider (SSP) DLLs are loaded into LSSAS process at system start. Once loaded into the LSA, SSP DLLs have access to encrypted and plaintext passwords that are stored in Windows, such as any logged-on user's Domain password or smart card PINs.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.xpnsec.com/exploring-mimikatz-part-2/
+* https://github.com/jas502n/mimikat_ssp
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+library where host.os.type == "windows" and process.executable : "?:\\Windows\\System32\\lsass.exe" and
+  not (dll.code_signature.subject_name :
+               ("Microsoft Windows",
+                "Microsoft Corporation",
+                "Microsoft Windows Publisher",
+                "Microsoft Windows Software Compatibility Publisher",
+                "Microsoft Windows Hardware Compatibility Publisher",
+                "McAfee, Inc.",
+                "SecMaker AB",
+                "HID Global Corporation",
+                "HID Global",
+                "Apple Inc.",
+                "Citrix Systems, Inc.",
+                "Dell Inc",
+                "Hewlett-Packard Company",
+                "Symantec Corporation",
+                "National Instruments Corporation",
+                "DigitalPersona, Inc.",
+                "Novell, Inc.",
+                "gemalto",
+                "EasyAntiCheat Oy",
+                "Entrust Datacard Corporation",
+                "AuriStor, Inc.",
+                "LogMeIn, Inc.",
+                "VMware, Inc.",
+                "Istituto Poligrafico e Zecca dello Stato S.p.A.",
+                "Nubeva Technologies Ltd",
+                "Micro Focus (US), Inc.",
+                "Yubico AB",
+                "GEMALTO SA",
+                "Secure Endpoints, Inc.",
+                "Sophos Ltd",
+                "Morphisec Information Security 2014 Ltd",
+                "Entrust, Inc.",
+                "Nubeva Technologies Ltd",
+                "Micro Focus (US), Inc.",
+                "F5 Networks Inc",
+                "Bit4id",
+                "Thales DIS CPL USA, Inc.",
+                "Micro Focus International plc",
+                "HYPR Corp",
+                "Intel(R) Software Development Products",
+                "PGP Corporation",
+                "Parallels International GmbH",
+                "FrontRange Solutions Deutschland GmbH",
+                "SecureLink, Inc.",
+                "Tidexa OU",
+                "Amazon Web Services, Inc.",
+                "SentryBay Limited",
+                "Audinate Pty Ltd",
+                "CyberArk Software Ltd.",
+                "McAfeeSysPrep",
+                "NVIDIA Corporation PE Sign v2016",
+                "Trend Micro, Inc.",
+                "Fortinet Technologies (Canada) Inc.",
+                "Carbon Black, Inc.") and
+       dll.code_signature.status : ("trusted", "errorExpired", "errorCode_endpoint*", "errorChaining")) and
+
+     not dll.hash.sha256 :
+                ("811a03a5d7c03802676d2613d741be690b3461022ea925eb6b2651a5be740a4c",
+                 "1181542d9cfd63fb00c76242567446513e6773ea37db6211545629ba2ecf26a1",
+                 "ed6e735aa6233ed262f50f67585949712f1622751035db256811b4088c214ce3",
+                 "26be2e4383728eebe191c0ab19706188f0e9592add2e0bf86b37442083ae5e12",
+                 "9367e78b84ef30cf38ab27776605f2645e52e3f6e93369c674972b668a444faa",
+                 "d46cc934765c5ecd53867070f540e8d6f7701e834831c51c2b0552aba871921b",
+                 "0f77a3826d7a5cd0533990be0269d951a88a5c277bc47cff94553330b715ec61",
+                 "4aca034d3d85a9e9127b5d7a10882c2ef4c3e0daa3329ae2ac1d0797398695fb",
+                 "86031e69914d9d33c34c2f4ac4ae523cef855254d411f88ac26684265c981d95")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: LSASS Memory
+** ID: T1003.001
+** Reference URL: https://attack.mitre.org/techniques/T1003/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-ms-office-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-ms-office-child-process.asciidoc
index a4a37859c2..4445b310d8 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-ms-office-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-ms-office-child-process.asciidoc
@@ -5,69 +5,71 @@ Identifies suspicious child processes of frequently targeted Microsoft Office ap
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/blog/vulnerability-summary-follina
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Initial Access
-* Investigation Guide
-
-*Version*: 102 (<<suspicious-ms-office-child-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious MS Office Child Process
+*Triage and analysis*
+
+
+
+*Investigating Suspicious MS Office Child Process*
+
 
-Microsoft Office (MS Office) is a suite of applications designed to help with productivity and completing common tasks on a computer.
-You can create and edit documents containing text and images, work with data in spreadsheets and databases, and create
-presentations and posters. As it is some of the most-used software across companies, MS Office is frequently targeted
-for initial access. It also has a wide variety of capabilities that attackers can take advantage of.
+Microsoft Office (MS Office) is a suite of applications designed to help with productivity and completing common tasks on a computer. You can create and edit documents containing text and images, work with data in spreadsheets and databases, and create presentations and posters. As it is some of the most-used software across companies, MS Office is frequently targeted for initial access. It also has a wide variety of capabilities that attackers can take advantage of.
 
-This rule looks for suspicious processes spawned by MS Office programs. This is generally the result of the execution of
-malicious documents.
+This rule looks for suspicious processes spawned by MS Office programs. This is generally the result of the execution of malicious documents.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Retrieve MS Office documents received and opened by the user that could cause this behavior. Common locations include,
-but are not limited to, the Downloads and Document folders and the folder configured at the email client.
+- Retrieve MS Office documents received and opened by the user that could cause this behavior. Common locations include, but are not limited to, the Downloads and Document folders and the folder configured at the email client.
 - Determine if the collected files are malicious:
   - Use a private sandboxed malware analysis system to perform analysis.
     - Observe and collect information about the following activities:
@@ -78,63 +80,77 @@ but are not limited to, the Downloads and Document folders and the folder config
   - Use the PowerShell Get-FileHash cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - If the triage identified malware, search the environment for additional compromised hosts.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system,
-persistence mechanisms, and malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
   - If the malicious file was delivered via phishing:
     - Block the email sender from sending future emails.
     - Block the malicious web pages.
     - Remove emails from the sender from mailboxes.
     - Consider improvements to the security awareness program.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-("eqnedt32.exe", "excel.exe", "fltldr.exe", "msaccess.exe",
-"mspub.exe", "powerpnt.exe", "winword.exe", "outlook.exe") and
-process.name : ("Microsoft.Workflow.Compiler.exe", "arp.exe",
-"atbroker.exe", "bginfo.exe", "bitsadmin.exe", "cdb.exe",
-"certutil.exe", "cmd.exe", "cmstp.exe", "control.exe",
-"cscript.exe", "csi.exe", "dnx.exe", "dsget.exe", "dsquery.exe",
-"forfiles.exe", "fsi.exe", "ftp.exe", "gpresult.exe",
-"hostname.exe", "ieexec.exe", "iexpress.exe", "installutil.exe",
-"ipconfig.exe", "mshta.exe", "msxsl.exe",
-"nbtstat.exe", "net.exe", "net1.exe", "netsh.exe", "netstat.exe",
-"nltest.exe", "odbcconf.exe", "ping.exe",
-"powershell.exe", "pwsh.exe", "qprocess.exe", "quser.exe",
-"qwinsta.exe", "rcsi.exe", "reg.exe", "regasm.exe",
-"regsvcs.exe", "regsvr32.exe", "sc.exe", "schtasks.exe",
-"systeminfo.exe", "tasklist.exe", "tracert.exe", "whoami.exe",
-"wmic.exe", "wscript.exe", "xwizard.exe", "explorer.exe",
-"rundll32.exe", "hh.exe", "msdt.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : (
+      "eqnedt32.exe", "excel.exe", "fltldr.exe", "msaccess.exe",
+      "mspub.exe", "powerpnt.exe", "winword.exe", "outlook.exe"
+  ) and
+  process.name : (
+      "Microsoft.Workflow.Compiler.exe", "arp.exe", "atbroker.exe", "bginfo.exe", "bitsadmin.exe", "cdb.exe",
+      "certutil.exe", "cmd.exe", "cmstp.exe", "control.exe", "cscript.exe", "csi.exe", "dnx.exe", "dsget.exe",
+      "dsquery.exe", "forfiles.exe", "fsi.exe", "ftp.exe", "gpresult.exe", "hostname.exe", "ieexec.exe", "iexpress.exe",
+      "installutil.exe", "ipconfig.exe", "mshta.exe", "msxsl.exe", "nbtstat.exe", "net.exe", "net1.exe", "netsh.exe",
+      "netstat.exe", "nltest.exe", "odbcconf.exe", "ping.exe", "powershell.exe", "pwsh.exe", "qprocess.exe",
+      "quser.exe", "qwinsta.exe", "rcsi.exe", "reg.exe", "regasm.exe", "regsvcs.exe", "regsvr32.exe", "sc.exe",
+      "schtasks.exe", "systeminfo.exe", "tasklist.exe", "tracert.exe", "whoami.exe", "wmic.exe", "wscript.exe",
+      "xwizard.exe", "explorer.exe", "rundll32.exe", "hh.exe", "msdt.exe"
+  ) and
+  not (
+    process.parent.name : "outlook.exe" and
+    process.name : "rundll32.exe" and
+    process.args : "shell32.dll,Control_RunDLL" and
+    process.args : "srchadmin.dll"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -146,192 +162,31 @@ process.name : ("Microsoft.Workflow.Compiler.exe", "arp.exe",
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[suspicious-ms-office-child-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : ("eqnedt32.exe", "excel.exe", "fltldr.exe",
-"msaccess.exe", "mspub.exe", "powerpnt.exe", "winword.exe",
-"outlook.exe") and process.name :
-("Microsoft.Workflow.Compiler.exe", "arp.exe", "atbroker.exe",
-"bginfo.exe", "bitsadmin.exe", "cdb.exe", "certutil.exe",
-"cmd.exe", "cmstp.exe", "control.exe", "cscript.exe", "csi.exe",
-"dnx.exe", "dsget.exe", "dsquery.exe", "forfiles.exe",
-"fsi.exe", "ftp.exe", "gpresult.exe", "hostname.exe", "ieexec.exe",
-"iexpress.exe", "installutil.exe", "ipconfig.exe",
-"mshta.exe", "msxsl.exe", "nbtstat.exe", "net.exe", "net1.exe",
-"netsh.exe", "netstat.exe", "nltest.exe", "odbcconf.exe",
-"ping.exe", "powershell.exe", "pwsh.exe", "qprocess.exe", "quser.exe",
-"qwinsta.exe", "rcsi.exe", "reg.exe", "regasm.exe",
-"regsvcs.exe", "regsvr32.exe", "sc.exe", "schtasks.exe",
-"systeminfo.exe", "tasklist.exe", "tracert.exe", "whoami.exe",
-"wmic.exe", "wscript.exe", "xwizard.exe", "explorer.exe",
-"rundll32.exe", "hh.exe", "msdt.exe")
-----------------------------------
-
-Version 13 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : ("eqnedt32.exe", "excel.exe", "fltldr.exe",
-"msaccess.exe", "mspub.exe", "powerpnt.exe", "winword.exe",
-"outlook.exe") and process.name :
-("Microsoft.Workflow.Compiler.exe", "arp.exe", "atbroker.exe",
-"bginfo.exe", "bitsadmin.exe", "cdb.exe", "certutil.exe",
-"cmd.exe", "cmstp.exe", "control.exe", "cscript.exe", "csi.exe",
-"dnx.exe", "dsget.exe", "dsquery.exe", "forfiles.exe",
-"fsi.exe", "ftp.exe", "gpresult.exe", "hostname.exe", "ieexec.exe",
-"iexpress.exe", "installutil.exe", "ipconfig.exe",
-"mshta.exe", "msxsl.exe", "nbtstat.exe", "net.exe", "net1.exe",
-"netsh.exe", "netstat.exe", "nltest.exe", "odbcconf.exe",
-"ping.exe", "powershell.exe", "pwsh.exe", "qprocess.exe", "quser.exe",
-"qwinsta.exe", "rcsi.exe", "reg.exe", "regasm.exe",
-"regsvcs.exe", "regsvr32.exe", "sc.exe", "schtasks.exe",
-"systeminfo.exe", "tasklist.exe", "tracert.exe", "whoami.exe",
-"wmic.exe", "wscript.exe", "xwizard.exe", "explorer.exe",
-"rundll32.exe", "hh.exe", "msdt.exe")
-----------------------------------
-
-Version 11 (8.3.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : ("eqnedt32.exe", "excel.exe", "fltldr.exe",
-"msaccess.exe", "mspub.exe", "powerpnt.exe", "winword.exe") and
-process.name : ("Microsoft.Workflow.Compiler.exe", "arp.exe",
-"atbroker.exe", "bginfo.exe", "bitsadmin.exe", "cdb.exe",
-"certutil.exe", "cmd.exe", "cmstp.exe", "control.exe",
-"cscript.exe", "csi.exe", "dnx.exe", "dsget.exe", "dsquery.exe",
-"forfiles.exe", "fsi.exe", "ftp.exe", "gpresult.exe",
-"hostname.exe", "ieexec.exe", "iexpress.exe", "installutil.exe",
-"ipconfig.exe", "mshta.exe", "msxsl.exe",
-"nbtstat.exe", "net.exe", "net1.exe", "netsh.exe", "netstat.exe",
-"nltest.exe", "odbcconf.exe", "ping.exe",
-"powershell.exe", "pwsh.exe", "qprocess.exe", "quser.exe",
-"qwinsta.exe", "rcsi.exe", "reg.exe", "regasm.exe",
-"regsvcs.exe", "regsvr32.exe", "sc.exe", "schtasks.exe",
-"systeminfo.exe", "tasklist.exe", "tracert.exe", "whoami.exe",
-"wmic.exe", "wscript.exe", "xwizard.exe", "explorer.exe",
-"rundll32.exe", "hh.exe")
-----------------------------------
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 9 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : ("eqnedt32.exe", "excel.exe", "fltldr.exe",
-"msaccess.exe", "mspub.exe", "powerpnt.exe", "winword.exe") and
-process.name : ("Microsoft.Workflow.Compiler.exe", "arp.exe",
-"atbroker.exe", "bginfo.exe", "bitsadmin.exe", "cdb.exe",
-"certutil.exe", "cmd.exe", "cmstp.exe", "cscript.exe",
-"csi.exe", "dnx.exe", "dsget.exe", "dsquery.exe", "forfiles.exe",
-"fsi.exe", "ftp.exe", "gpresult.exe", "hostname.exe",
-"ieexec.exe", "iexpress.exe", "installutil.exe", "ipconfig.exe",
-"mshta.exe", "msxsl.exe", "nbtstat.exe", "net.exe",
-"net1.exe", "netsh.exe", "netstat.exe", "nltest.exe", "odbcconf.exe",
-"ping.exe", "powershell.exe", "pwsh.exe",
-"qprocess.exe", "quser.exe", "qwinsta.exe", "rcsi.exe", "reg.exe",
-"regasm.exe", "regsvcs.exe", "regsvr32.exe", "sc.exe",
-"schtasks.exe", "systeminfo.exe", "tasklist.exe", "tracert.exe",
-"whoami.exe", "wmic.exe", "wscript.exe",
-"xwizard.exe", "explorer.exe", "rundll32.exe", "hh.exe")
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:(eqnedt32.exe or excel.exe or fltldr.exe or
-msaccess.exe or mspub.exe or powerpnt.exe or winword.exe) and
-process.name:(Microsoft.Workflow.Compiler.exe or arp.exe or
-atbroker.exe or bginfo.exe or bitsadmin.exe or cdb.exe or certutil.exe
-or cmd.exe or cmstp.exe or cscript.exe or csi.exe or dnx.exe or
-dsget.exe or dsquery.exe or forfiles.exe or fsi.exe or ftp.exe or
-gpresult.exe or hostname.exe or ieexec.exe or iexpress.exe or
-installutil.exe or ipconfig.exe or mshta.exe or msxsl.exe or
-nbtstat.exe or net.exe or net1.exe or netsh.exe or netstat.exe or
-nltest.exe or odbcconf.exe or ping.exe or powershell.exe or pwsh.exe
-or qprocess.exe or quser.exe or qwinsta.exe or rcsi.exe or reg.exe or
-regasm.exe or regsvcs.exe or regsvr32.exe or sc.exe or schtasks.exe or
-systeminfo.exe or tasklist.exe or tracert.exe or whoami.exe or
-wmic.exe or wscript.exe or xwizard.exe)
-----------------------------------
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.parent.name:(eqnedt32.exe or excel.exe or fltldr.exe or
-msaccess.exe or mspub.exe or powerpnt.exe or winword.exe) and
-process.name:(Microsoft.Workflow.Compiler.exe or arp.exe or
-atbroker.exe or bginfo.exe or bitsadmin.exe or cdb.exe or certutil.exe
-or cmd.exe or cmstp.exe or cscript.exe or csi.exe or dnx.exe or
-dsget.exe or dsquery.exe or forfiles.exe or fsi.exe or ftp.exe or
-gpresult.exe or hostname.exe or ieexec.exe or iexpress.exe or
-installutil.exe or ipconfig.exe or mshta.exe or msxsl.exe or
-nbtstat.exe or net.exe or net1.exe or netsh.exe or netstat.exe or
-nltest.exe or odbcconf.exe or ping.exe or powershell.exe or pwsh.exe
-or qprocess.exe or quser.exe or qwinsta.exe or rcsi.exe or reg.exe or
-regasm.exe or regsvcs.exe or regsvr32.exe or sc.exe or schtasks.exe or
-systeminfo.exe or tasklist.exe or tracert.exe or whoami.exe or
-wmic.exe or wscript.exe or xwizard.exe)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.parent.name:("winword.exe" or "excel.exe" or "powerpnt.exe" or
-"eqnedt32.exe" or "fltldr.exe" or "mspub.exe" or "msaccess.exe") and
-process.name:("arp.exe" or "dsquery.exe" or "dsget.exe" or
-"gpresult.exe" or "hostname.exe" or "ipconfig.exe" or "nbtstat.exe" or
-"net.exe" or "net1.exe" or "netsh.exe" or "netstat.exe" or
-"nltest.exe" or "ping.exe" or "qprocess.exe" or "quser.exe" or
-"qwinsta.exe" or "reg.exe" or "sc.exe" or "systeminfo.exe" or
-"tasklist.exe" or "tracert.exe" or "whoami.exe" or "bginfo.exe" or
-"cdb.exe" or "cmstp.exe" or "csi.exe" or "dnx.exe" or "fsi.exe" or
-"ieexec.exe" or "iexpress.exe" or "installutil.exe" or
-"Microsoft.Workflow.Compiler.exe" or "msbuild.exe" or "mshta.exe" or
-"msxsl.exe" or "odbcconf.exe" or "rcsi.exe" or "regsvr32.exe" or
-"xwizard.exe" or "atbroker.exe" or "forfiles.exe" or "schtasks.exe" or
-"regasm.exe" or "regsvcs.exe" or "cmd.exe" or "cscript.exe" or
-"powershell.exe" or "pwsh.exe" or "wmic.exe" or "wscript.exe" or
-"bitsadmin.exe" or "certutil.exe" or "ftp.exe")
-----------------------------------
-
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-ms-outlook-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-ms-outlook-child-process.asciidoc
index 23a9d5a0ad..a3400b7a8b 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-ms-outlook-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-ms-outlook-child-process.asciidoc
@@ -5,63 +5,69 @@ Identifies suspicious child processes of Microsoft Outlook. These child processe
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Initial Access
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<suspicious-ms-outlook-child-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious MS Outlook Child Process
+*Triage and analysis*
+
+
+
+*Investigating Suspicious MS Outlook Child Process*
 
-Microsoft Outlook is an email client that provides contact, email calendar, and task management features. Outlook is
-widely used, either standalone or as part of the Office suite.
 
-This rule looks for suspicious processes spawned by MS Outlook, which can be the result of the execution of malicious
-documents and/or exploitation for initial access.
+Microsoft Outlook is an email client that provides contact, email calendar, and task management features. Outlook is widely used, either standalone or as part of the Office suite.
 
-#### Possible investigation steps
+This rule looks for suspicious processes spawned by MS Outlook, which can be the result of the execution of malicious documents and/or exploitation for initial access.
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Retrieve recently opened files received via email and opened by the user that could cause this behavior. Common
-locations include but are not limited to, the Downloads and Document folders and the folder configured at the email client.
+- Retrieve recently opened files received via email and opened by the user that could cause this behavior. Common locations include but are not limited to, the Downloads and Document folders and the folder configured at the email client.
 - Determine if the collected files are malicious:
   - Use a private sandboxed malware analysis system to perform analysis.
     - Observe and collect information about the following activities:
@@ -72,59 +78,66 @@ locations include but are not limited to, the Downloads and Document folders and
   - Use the PowerShell Get-FileHash cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - If the triage identified malware, search the environment for additional compromised hosts.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system,
-persistence mechanisms, and malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
   - If the malicious file was delivered via phishing:
     - Block the email sender from sending future emails.
     - Block the malicious web pages.
     - Remove emails from the sender from mailboxes.
     - Consider improvements to the security awareness program.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"outlook.exe" and process.name : ("Microsoft.Workflow.Compiler.exe",
-"arp.exe", "atbroker.exe", "bginfo.exe", "bitsadmin.exe",
-"cdb.exe", "certutil.exe", "cmd.exe", "cmstp.exe", "cscript.exe",
-"csi.exe", "dnx.exe", "dsget.exe", "dsquery.exe",
-"forfiles.exe", "fsi.exe", "ftp.exe", "gpresult.exe", "hostname.exe",
-"ieexec.exe", "iexpress.exe", "installutil.exe",
-"ipconfig.exe", "mshta.exe", "msxsl.exe", "nbtstat.exe", "net.exe",
-"net1.exe", "netsh.exe", "netstat.exe", "nltest.exe", "odbcconf.exe",
-"ping.exe", "powershell.exe", "pwsh.exe",
-"qprocess.exe", "quser.exe", "qwinsta.exe", "rcsi.exe", "reg.exe",
-"regasm.exe", "regsvcs.exe", "regsvr32.exe",
-"sc.exe", "schtasks.exe", "systeminfo.exe", "tasklist.exe",
-"tracert.exe", "whoami.exe", "wmic.exe", "wscript.exe", "xwizard.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : "outlook.exe" and
+  process.name : ("Microsoft.Workflow.Compiler.exe", "arp.exe", "atbroker.exe", "bginfo.exe", "bitsadmin.exe",
+                  "cdb.exe", "certutil.exe", "cmd.exe", "cmstp.exe", "cscript.exe", "csi.exe", "dnx.exe", "dsget.exe",
+                  "dsquery.exe", "forfiles.exe", "fsi.exe", "ftp.exe", "gpresult.exe", "hostname.exe", "ieexec.exe",
+                  "iexpress.exe", "installutil.exe", "ipconfig.exe", "mshta.exe", "msxsl.exe", "nbtstat.exe", "net.exe",
+                  "net1.exe", "netsh.exe", "netstat.exe", "nltest.exe", "odbcconf.exe", "ping.exe", "powershell.exe",
+                  "pwsh.exe", "qprocess.exe", "quser.exe", "qwinsta.exe", "rcsi.exe", "reg.exe", "regasm.exe",
+                  "regsvcs.exe", "regsvr32.exe", "sc.exe", "schtasks.exe", "systeminfo.exe", "tasklist.exe",
+                  "tracert.exe", "whoami.exe", "wmic.exe", "wscript.exe", "xwizard.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -136,118 +149,31 @@ process where event.type == "start" and process.parent.name :
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[suspicious-ms-outlook-child-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "outlook.exe" and process.name :
-("Microsoft.Workflow.Compiler.exe", "arp.exe", "atbroker.exe",
-"bginfo.exe", "bitsadmin.exe", "cdb.exe",
-"certutil.exe", "cmd.exe", "cmstp.exe", "cscript.exe", "csi.exe",
-"dnx.exe", "dsget.exe", "dsquery.exe",
-"forfiles.exe", "fsi.exe", "ftp.exe", "gpresult.exe", "hostname.exe",
-"ieexec.exe", "iexpress.exe", "installutil.exe",
-"ipconfig.exe", "mshta.exe", "msxsl.exe", "nbtstat.exe", "net.exe",
-"net1.exe", "netsh.exe", "netstat.exe", "nltest.exe", "odbcconf.exe",
-"ping.exe", "powershell.exe", "pwsh.exe",
-"qprocess.exe", "quser.exe", "qwinsta.exe", "rcsi.exe", "reg.exe",
-"regasm.exe", "regsvcs.exe", "regsvr32.exe",
-"sc.exe", "schtasks.exe", "systeminfo.exe", "tasklist.exe",
-"tracert.exe", "whoami.exe", "wmic.exe", "wscript.exe", "xwizard.exe")
-----------------------------------
-
-Version 12 (8.4.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:outlook.exe and
-process.name:(Microsoft.Workflow.Compiler.exe or arp.exe or
-atbroker.exe or bginfo.exe or bitsadmin.exe or cdb.exe or
-certutil.exe or cmd.exe or cmstp.exe or cscript.exe or csi.exe or
-dnx.exe or dsget.exe or dsquery.exe or forfiles.exe or fsi.exe or
-ftp.exe or gpresult.exe or hostname.exe or ieexec.exe or iexpress.exe
-or installutil.exe or ipconfig.exe or mshta.exe or msxsl.exe or
-nbtstat.exe or net.exe or net1.exe or netsh.exe or netstat.exe or
-nltest.exe or odbcconf.exe or ping.exe or powershell.exe or pwsh.exe
-or qprocess.exe or quser.exe or qwinsta.exe or rcsi.exe or reg.exe or
-regasm.exe or regsvcs.exe or regsvr32.exe or sc.exe or schtasks.exe or
-systeminfo.exe or tasklist.exe or tracert.exe or whoami.exe or
-wmic.exe or wscript.exe or xwizard.exe)
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.parent.name:outlook.exe and
-process.name:(Microsoft.Workflow.Compiler.exe or arp.exe or
-atbroker.exe or bginfo.exe or bitsadmin.exe or cdb.exe or certutil.exe
-or cmd.exe or cmstp.exe or cscript.exe or csi.exe or dnx.exe or
-dsget.exe or dsquery.exe or forfiles.exe or fsi.exe or ftp.exe or
-gpresult.exe or hostname.exe or ieexec.exe or iexpress.exe or
-installutil.exe or ipconfig.exe or mshta.exe or msxsl.exe or
-nbtstat.exe or net.exe or net1.exe or netsh.exe or netstat.exe or
-nltest.exe or odbcconf.exe or ping.exe or powershell.exe or pwsh.exe
-or qprocess.exe or quser.exe or qwinsta.exe or rcsi.exe or reg.exe or
-regasm.exe or regsvcs.exe or regsvr32.exe or sc.exe or schtasks.exe or
-systeminfo.exe or tasklist.exe or tracert.exe or whoami.exe or
-wmic.exe or wscript.exe or xwizard.exe)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.parent.name:"outlook.exe" and process.name:("arp.exe" or
-"dsquery.exe" or "dsget.exe" or "gpresult.exe" or "hostname.exe" or
-"ipconfig.exe" or "nbtstat.exe" or "net.exe" or "net1.exe" or
-"netsh.exe" or "netstat.exe" or "nltest.exe" or "ping.exe" or
-"qprocess.exe" or "quser.exe" or "qwinsta.exe" or "reg.exe" or
-"sc.exe" or "systeminfo.exe" or "tasklist.exe" or "tracert.exe" or
-"whoami.exe" or "bginfo.exe" or "cdb.exe" or "cmstp.exe" or "csi.exe"
-or "dnx.exe" or "fsi.exe" or "ieexec.exe" or "iexpress.exe" or
-"installutil.exe" or "Microsoft.Workflow.Compiler.exe" or
-"msbuild.exe" or "mshta.exe" or "msxsl.exe" or "odbcconf.exe" or
-"rcsi.exe" or "regsvr32.exe" or "xwizard.exe" or "atbroker.exe" or
-"forfiles.exe" or "schtasks.exe" or "regasm.exe" or "regsvcs.exe" or
-"cmd.exe" or "cscript.exe" or "powershell.exe" or "pwsh.exe" or
-"wmic.exe" or "wscript.exe" or "bitsadmin.exe" or "certutil.exe" or
-"ftp.exe")
-----------------------------------
-
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-net-code-compilation.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-net-code-compilation.asciidoc
new file mode 100644
index 0000000000..c950fcbffc
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-net-code-compilation.asciidoc
@@ -0,0 +1,97 @@
+[[suspicious-net-code-compilation]]
+=== Suspicious .NET Code Compilation
+
+Identifies executions of .NET compilers with suspicious parent processes, which can indicate an attacker's attempt to compile code after delivery in order to bypass security mechanisms.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 110
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : ("csc.exe", "vbc.exe") and
+  process.parent.name : ("wscript.exe", "mshta.exe", "cscript.exe", "wmic.exe", "svchost.exe", "rundll32.exe", "cmstp.exe", "regsvr32.exe")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Obfuscated Files or Information
+** ID: T1027
+** Reference URL: https://attack.mitre.org/techniques/T1027/
+* Sub-technique:
+** Name: Compile After Delivery
+** ID: T1027.004
+** Reference URL: https://attack.mitre.org/techniques/T1027/004/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Visual Basic
+** ID: T1059.005
+** Reference URL: https://attack.mitre.org/techniques/T1059/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-net-reflection-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-net-reflection-via-powershell.asciidoc
new file mode 100644
index 0000000000..2ed0bf8046
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-net-reflection-via-powershell.asciidoc
@@ -0,0 +1,200 @@
+[[suspicious-net-reflection-via-powershell]]
+=== Suspicious .NET Reflection via PowerShell
+
+Detects the use of Reflection.Assembly to load PEs and DLLs in memory in PowerShell scripts. Attackers use this method to load executables and DLLs without writing to the disk, bypassing security solutions.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.powershell*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.microsoft.com/en-us/dotnet/api/system.reflection.assembly.load
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
+
+*Version*: 212
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Suspicious .NET Reflection via PowerShell*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+Attackers can use .NET reflection to load PEs and DLLs in memory. These payloads are commonly embedded in the script, which can circumvent file-based security protections.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Examine file or network events from the involved PowerShell process for suspicious behavior.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Evaluate whether the user needs to use PowerShell to complete tasks.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the script using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately outside engineering or IT business units. As long as the analyst did not identify malware or suspicious activity related to the user or host, this alert can be dismissed.
+
+
+*Related rules*
+
+
+- PowerShell PSReflect Script - 56f2e9b5-4803-4e44-a0a4-a52dc79d57fe
+- Potential Process Injection via PowerShell - 2e29e96a-b67c-455a-afe4-de6183431d0d
+- PowerShell Suspicious Payload Encoded and Compressed - 81fe9dc6-a2d7-4192-a2d8-eed98afc766a
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
+
+Steps to implement the logging policy via registry:
+
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    "[System.Reflection.Assembly]::Load" or
+    "[Reflection.Assembly]::Load"
+  ) and
+  not powershell.file.script_block_text : (
+        ("CommonWorkflowParameters" or "RelatedLinksHelpInfo") and
+        "HelpDisplayStrings"
+  ) and
+  not (powershell.file.script_block_text :
+        ("Get-SolutionFiles" or "Get-VisualStudio" or "Select-MSBuildPath") and
+        file.name : "PathFunctions.ps1"
+  ) and
+  not user.id : "S-1-5-18"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Reflective Code Loading
+** ID: T1620
+** Reference URL: https://attack.mitre.org/techniques/T1620/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
+* Sub-technique:
+** Name: Dynamic-link Library Injection
+** ID: T1055.001
+** Reference URL: https://attack.mitre.org/techniques/T1055/001/
+* Sub-technique:
+** Name: Portable Executable Injection
+** ID: T1055.002
+** Reference URL: https://attack.mitre.org/techniques/T1055/002/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-network-activity-to-the-internet-by-previously-unknown-executable.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-network-activity-to-the-internet-by-previously-unknown-executable.asciidoc
new file mode 100644
index 0000000000..698cb84d56
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-network-activity-to-the-internet-by-previously-unknown-executable.asciidoc
@@ -0,0 +1,241 @@
+[[suspicious-network-activity-to-the-internet-by-previously-unknown-executable]]
+=== Suspicious Network Activity to the Internet by Previously Unknown Executable
+
+This rule monitors for network connectivity to the internet from a previously unknown executable located in a suspicious directory to a previously unknown destination ip. An alert from this rule can indicate the presence of potentially malicious activity, such as the execution of unauthorized or suspicious processes attempting to establish connections to unknown or suspicious destinations such as a command and control server. Detecting and investigating such behavior can help identify and mitigate potential security threats, protecting the system and its data from potential compromise.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* auditbeat-*
+* filebeat-*
+* packetbeat-*
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-59m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Suspicious Network Activity to the Internet by Previously Unknown Executable*
+
+
+After being installed, malware will often call out to its command and control server to receive further instructions by its operators.
+
+This rule leverages the new terms rule type to detect previously unknown processes, initiating network connections to external IP-addresses. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Identify any signs of suspicious network activity or anomalies that may indicate malicious behavior. This could include unexpected traffic patterns or unusual network behavior.
+  - Investigate listening ports and open sockets to look for potential malicious processes, reverse shells or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+  - !{osquery{"label":"Osquery - Retrieve Process Info","query":"SELECT name, cmdline, parent, path, uid FROM processes"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+
+
+*Related rules*
+
+
+- Network Activity Detected via cat - afd04601-12fc-4149-9b78-9c3f8fe45d39
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors, such as reverse shells, reverse proxies, or droppers, that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
+- Filebeat
+- Packetbeat
+
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Filebeat Setup*
+
+Filebeat is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to Elasticsearch or Logstash for indexing.
+
+
+*The following steps should be executed in order to add the Filebeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html[helper guide].
+- To run Filebeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-docker.html[helper guide].
+- To run Filebeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html[helper guide].
+- For quick start information for Filebeat refer to the https://www.elastic.co/guide/en/beats/filebeat/8.11/filebeat-installation-configuration.html[helper guide].
+- For complete “Setup and Run Filebeat” information refer to the https://www.elastic.co/guide/en/beats/filebeat/current/setting-up-and-running.html[helper guide].
+
+
+*Packetbeat Setup*
+
+Packetbeat is a real-time network packet analyzer that you can use for application monitoring, performance analytics, and threat detection. Packetbeat works by capturing the network traffic between your application servers, decoding the application layer protocols (HTTP, MySQL, Redis, and so on), correlating the requests with the responses, and recording the interesting fields for each transaction.
+
+
+*The following steps should be executed in order to add the Packetbeat on a  Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/packetbeat/current/setup-repositories.html[helper guide].
+- To run Packetbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/packetbeat/current/running-on-docker.html[helper guide].
+- For quick start information for Packetbeat refer to the https://www.elastic.co/guide/en/beats/packetbeat/current/packetbeat-installation-configuration.html[helper guide].
+- For complete “Setup and Run Packetbeat” information refer to the https://www.elastic.co/guide/en/beats/packetbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.category:network and event.action:(connection_attempted or ipv4_connection_attempt_event) and 
+process.executable:(
+  (/etc/crontab or /etc/rc.local or ./* or /boot/* or /dev/shm/* or /etc/cron.*/* or /etc/init.d/* or /etc/rc*.d/* or 
+   /etc/update-motd.d/* or /home/*/.* or /run/* or /srv/* or /tmp/* or /usr/lib/update-notifier/* or /var/tmp/*
+  ) and not (/tmp/newroot/* or /tmp/snap.rootfs*)
+ ) and 
+source.ip:(10.0.0.0/8 or 127.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) and 
+not process.name:(
+ apt or chrome or curl or dnf or dockerd or dpkg or firefox-bin or java or kite-update or kited or node or rpm or
+ saml2aws or wget or yum or ansible* or aws* or php* or pip* or python* or steam* or terraform*
+) and 
+not destination.ip:(
+   10.0.0.0/8 or 100.64.0.0/10 or 127.0.0.0/8 or 169.254.0.0/16 or 172.16.0.0/12 or 192.0.0.0/24 or 192.0.0.0/29 or 
+   192.0.0.10/32 or 192.0.0.170/32 or 192.0.0.171/32 or 192.0.0.8/32 or 192.0.0.9/32 or 192.0.2.0/24 or 
+   192.168.0.0/16 or 192.175.48.0/24 or 192.31.196.0/24 or 192.52.193.0/24 or 192.88.99.0/24 or 198.18.0.0/15 or 
+   198.51.100.0/24 or 203.0.113.0/24 or 224.0.0.0/4 or 240.0.0.0/4 or "::1" or "FE80::/10" or "FF00::/8" or 0.0.0.0
+) and
+not destination.port:(22 or 80 or 443)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-network-connection-via-sudo-binary.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-network-connection-via-sudo-binary.asciidoc
new file mode 100644
index 0000000000..23fcc9f85c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-network-connection-via-sudo-binary.asciidoc
@@ -0,0 +1,112 @@
+[[suspicious-network-connection-via-sudo-binary]]
+=== Suspicious Network Connection via Sudo Binary
+
+Detects network connections initiated by the "sudo" binary. This behavior is uncommon and may occur in instances where reverse shell shellcode is injected into a process run with elevated permissions via "sudo". Attackers may attempt to inject shellcode into processes running as root, to escalate privileges.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+network where host.os.type == "linux" and event.type == "start" and
+event.action in ("connection_attempted", "ipv4_connection_attempt_event") and process.name == "sudo"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
+* Sub-technique:
+** Name: Ptrace System Calls
+** ID: T1055.008
+** Reference URL: https://attack.mitre.org/techniques/T1055/008/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Sudo and Sudo Caching
+** ID: T1548.003
+** Reference URL: https://attack.mitre.org/techniques/T1548/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-network-connection-via-systemd.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-network-connection-via-systemd.asciidoc
new file mode 100644
index 0000000000..f869a21e87
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-network-connection-via-systemd.asciidoc
@@ -0,0 +1,122 @@
+[[suspicious-network-connection-via-systemd]]
+=== Suspicious Network Connection via systemd
+
+Detects suspicious network events executed by systemd, potentially indicating persistence through a systemd backdoor. Systemd is a system and service manager for Linux operating systems, used to initialize and manage system processes. Attackers can backdoor systemd for persistence by creating or modifying systemd unit files to execute malicious scripts or commands, or by replacing legitimate systemd binaries with compromised ones, ensuring that their malicious code is automatically executed at system startup or during certain system events.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Command and Control
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id with maxspan=5s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+   process.parent.name == "systemd" and process.name in (
+     "python*", "php*", "perl", "ruby", "lua*", "openssl", "nc", "netcat", "ncat", "telnet", "awk"
+   )
+  ] by process.entity_id
+  [network where host.os.type == "linux" and event.action == "connection_attempted" and event.type == "start"
+  ] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Systemd Service
+** ID: T1543.002
+** Reference URL: https://attack.mitre.org/techniques/T1543/002/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-network-tool-launched-inside-a-container.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-network-tool-launched-inside-a-container.asciidoc
new file mode 100644
index 0000000000..e5503226b0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-network-tool-launched-inside-a-container.asciidoc
@@ -0,0 +1,82 @@
+[[suspicious-network-tool-launched-inside-a-container]]
+=== Suspicious Network Tool Launched Inside A Container
+
+This rule detects commonly abused network utilities running inside a container. Network utilities like nc, nmap, dig, tcpdump, ngrep, telnet, mitmproxy, zmap can be used for malicious purposes such as network reconnaissance, monitoring, or exploitation, and should be monitored closely within a container.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-cloud_defend*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Elastic Defend for Containers
+* Domain: Container
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Tactic: Command and Control
+* Tactic: Reconnaissance
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where container.id: "*" and event.type== "start" and 
+(
+(process.name: ("nc", "ncat", "nmap", "dig", "nslookup", "tcpdump", "tshark", "ngrep", "telnet", "mitmproxy", "socat", "zmap", "masscan", "zgrab")) or 
+/*account for tools that execute utilities as a subprocess, in this case the target utility name will appear as a process arg*/
+(process.args: ("nc", "ncat", "nmap", "dig", "nslookup", "tcpdump", "tshark", "ngrep", "telnet", "mitmproxy", "socat", "zmap", "masscan", "zgrab"))
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Network Service Discovery
+** ID: T1046
+** Reference URL: https://attack.mitre.org/techniques/T1046/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Ingress Tool Transfer
+** ID: T1105
+** Reference URL: https://attack.mitre.org/techniques/T1105/
+* Tactic:
+** Name: Reconnaissance
+** ID: TA0043
+** Reference URL: https://attack.mitre.org/tactics/TA0043/
+* Technique:
+** Name: Active Scanning
+** ID: T1595
+** Reference URL: https://attack.mitre.org/techniques/T1595/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-passwd-file-event-action.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-passwd-file-event-action.asciidoc
new file mode 100644
index 0000000000..28bf7edca0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-passwd-file-event-action.asciidoc
@@ -0,0 +1,130 @@
+[[suspicious-passwd-file-event-action]]
+=== Suspicious Passwd File Event Action
+
+Monitors for the generation of a passwd password entry via openssl, followed by a file write activity on the "/etc/passwd" file. The "/etc/passwd" file in Linux stores user account information, including usernames, user IDs, group IDs, home directories, and default shell paths. Attackers may exploit a misconfiguration in the "/etc/passwd" file permissions or other privileges to add a new entry to the "/etc/passwd" file with root permissions, and leverage this new user account to login as root.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend and Auditd Manager.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditd Manager Integration Setup*
+
+The Auditd Manager Integration receives audit events from the Linux Audit Framework which is a part of the Linux kernel.
+Auditd Manager provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system.
+
+
+*The following steps should be executed in order to add the Elastic Agent System integration "auditd_manager" on a Linux System:*
+
+- Go to the Kibana home page and click “Add integrations”.
+- In the query bar, search for “Auditd Manager” and select the integration to see more details about it.
+- Click “Add Auditd Manager”.
+- Configure the integration name and optionally add a description.
+- Review optional and advanced settings accordingly.
+- Add the newly installed “auditd manager” to an existing or a new agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+- Click “Save and Continue”.
+- For more details on the integration refer to the https://docs.elastic.co/integrations/auditd_manager[helper guide].
+
+
+*Rule Specific Setup Note*
+
+Auditd Manager subscribes to the kernel and receives events as they occur without any additional configuration.
+However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+- For this detection rule the following additional audit rules are required to be added to the integration:
+  -- "-w /etc/passwd -p wa -k etcpasswd"
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.parent.pid with maxspan=1m
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+   process.name == "openssl" and process.args == "passwd" and user.id != "0"]
+  [file where host.os.type == "linux" and file.path == "/etc/passwd" and process.parent.pid != 1 and
+   not auditd.data.a2 == "80000" and event.outcome == "success" and user.id != "0"]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-pdf-reader-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-pdf-reader-child-process.asciidoc
index fb544daf6e..8c73d91d12 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-pdf-reader-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-pdf-reader-child-process.asciidoc
@@ -5,65 +5,68 @@ Identifies suspicious child processes of PDF reader applications. These child pr
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<suspicious-pdf-reader-child-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Initial Access
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious PDF Reader Child Process
+*Triage and analysis*
+
+
 
-PDF is a common file type used in corporate environments and most machines have software to handle these files. This
-creates a vector where attackers can exploit the engines and technology behind this class of software for initial access
-or privilege escalation.
+*Investigating Suspicious PDF Reader Child Process*
+
+
+PDF is a common file type used in corporate environments and most machines have software to handle these files. This creates a vector where attackers can exploit the engines and technology behind this class of software for initial access or privilege escalation.
 
 This rule looks for commonly abused built-in utilities spawned by a PDF reader process, which is likely a malicious behavior.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Retrieve PDF documents received and opened by the user that could cause this behavior. Common locations include, but
-are not limited to, the Downloads and Document folders and the folder configured at the email client.
+- Retrieve PDF documents received and opened by the user that could cause this behavior. Common locations include, but are not limited to, the Downloads and Document folders and the folder configured at the email client.
 - Determine if the collected files are malicious:
   - Use a private sandboxed malware analysis system to perform analysis.
     - Observe and collect information about the following activities:
@@ -75,166 +78,89 @@ are not limited to, the Downloads and Document folders and the folder configured
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - If the triage identified malware, search the environment for additional compromised hosts.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system,
-persistence mechanisms, and malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
   - If the malicious file was delivered via phishing:
     - Block the email sender from sending future emails.
     - Block the malicious web pages.
     - Remove emails from the sender from mailboxes.
     - Consider improvements to the security awareness program.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
-==== Rule query
+==== Setup
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-("AcroRd32.exe", "Acrobat.exe",
-"FoxitPhantomPDF.exe", "FoxitReader.exe") and
-process.name : ("arp.exe", "dsquery.exe", "dsget.exe", "gpresult.exe",
-"hostname.exe", "ipconfig.exe", "nbtstat.exe",
-"net.exe", "net1.exe", "netsh.exe", "netstat.exe", "nltest.exe",
-"ping.exe", "qprocess.exe", "quser.exe",
-"qwinsta.exe", "reg.exe", "sc.exe", "systeminfo.exe", "tasklist.exe",
-"tracert.exe", "whoami.exe", "bginfo.exe",
-"cdb.exe", "cmstp.exe", "csi.exe", "dnx.exe", "fsi.exe", "ieexec.exe",
-"iexpress.exe", "installutil.exe", "Microsoft.Workflow.Compiler.exe",
-"msbuild.exe", "mshta.exe", "msxsl.exe",
-"odbcconf.exe", "rcsi.exe", "regsvr32.exe", "xwizard.exe",
-"atbroker.exe", "forfiles.exe", "schtasks.exe",
-"regasm.exe", "regsvcs.exe", "cmd.exe", "cscript.exe",
-"powershell.exe", "pwsh.exe", "wmic.exe", "wscript.exe",
-"bitsadmin.exe", "certutil.exe", "ftp.exe")
-----------------------------------
 
-==== Threat mapping
+*Setup*
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Execution
-** ID: TA0002
-** Reference URL: https://attack.mitre.org/tactics/TA0002/
-* Technique:
-** Name: User Execution
-** ID: T1204
-** Reference URL: https://attack.mitre.org/techniques/T1204/
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
-[[suspicious-pdf-reader-child-process-history]]
-==== Rule version history
 
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : ("AcroRd32.exe",
-"Acrobat.exe", "FoxitPhantomPDF.exe",
-"FoxitReader.exe") and process.name : ("arp.exe", "dsquery.exe",
-"dsget.exe", "gpresult.exe", "hostname.exe", "ipconfig.exe",
-"nbtstat.exe", "net.exe", "net1.exe", "netsh.exe",
-"netstat.exe", "nltest.exe", "ping.exe", "qprocess.exe",
-"quser.exe", "qwinsta.exe", "reg.exe", "sc.exe", "systeminfo.exe",
-"tasklist.exe", "tracert.exe", "whoami.exe",
-"bginfo.exe", "cdb.exe", "cmstp.exe", "csi.exe", "dnx.exe", "fsi.exe",
-"ieexec.exe", "iexpress.exe", "installutil.exe",
-"Microsoft.Workflow.Compiler.exe", "msbuild.exe", "mshta.exe",
-"msxsl.exe", "odbcconf.exe", "rcsi.exe", "regsvr32.exe",
-"xwizard.exe", "atbroker.exe", "forfiles.exe",
-"schtasks.exe", "regasm.exe", "regsvcs.exe", "cmd.exe", "cscript.exe",
-"powershell.exe", "pwsh.exe", "wmic.exe", "wscript.exe",
-"bitsadmin.exe", "certutil.exe", "ftp.exe")
-----------------------------------
-
-Version 11 (8.4.0 release)::
-* Formatting only
-
-Version 9 (8.3.0 release)::
-* Formatting only
+==== Rule query
 
-Version 8 (8.2.0 release)::
-* Formatting only
 
-Version 7 (7.13.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:(AcroRd32.exe or Acrobat.exe or
-FoxitPhantomPDF.exe or FoxitReader.exe) and process.name:(arp.exe or
-dsquery.exe or dsget.exe or gpresult.exe or hostname.exe or
-ipconfig.exe or nbtstat.exe or net.exe or net1.exe or netsh.exe or
-netstat.exe or nltest.exe or ping.exe or qprocess.exe or quser.exe or
-qwinsta.exe or reg.exe or sc.exe or systeminfo.exe or tasklist.exe or
-tracert.exe or whoami.exe or bginfo.exe or cdb.exe or cmstp.exe or
-csi.exe or dnx.exe or fsi.exe or ieexec.exe or iexpress.exe or
-installutil.exe or Microsoft.Workflow.Compiler.exe or msbuild.exe or
-mshta.exe or msxsl.exe or odbcconf.exe or rcsi.exe or regsvr32.exe or
-xwizard.exe or atbroker.exe or forfiles.exe or schtasks.exe or
-regasm.exe or regsvcs.exe or cmd.exe or cscript.exe or powershell.exe
-or pwsh.exe or wmic.exe or wscript.exe or bitsadmin.exe or
-certutil.exe or ftp.exe)
-----------------------------------
-
-Version 6 (7.12.0 release)::
-* Formatting only
-
-Version 5 (7.11.2 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.1 release)::
-* Formatting only
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : ("AcroRd32.exe",
+                         "Acrobat.exe",
+                         "FoxitPhantomPDF.exe",
+                         "FoxitReader.exe") and
+  process.name : ("arp.exe", "dsquery.exe", "dsget.exe", "gpresult.exe", "hostname.exe", "ipconfig.exe", "nbtstat.exe",
+                  "net.exe", "net1.exe", "netsh.exe", "netstat.exe", "nltest.exe", "ping.exe", "qprocess.exe",
+                  "quser.exe", "qwinsta.exe", "reg.exe", "sc.exe", "systeminfo.exe", "tasklist.exe", "tracert.exe",
+                  "whoami.exe", "bginfo.exe", "cdb.exe", "cmstp.exe", "csi.exe", "dnx.exe", "fsi.exe", "ieexec.exe",
+                  "iexpress.exe", "installutil.exe", "Microsoft.Workflow.Compiler.exe", "msbuild.exe", "mshta.exe",
+                  "msxsl.exe", "odbcconf.exe", "rcsi.exe", "regsvr32.exe", "xwizard.exe", "atbroker.exe",
+                  "forfiles.exe", "schtasks.exe", "regasm.exe", "regsvcs.exe", "cmd.exe", "cscript.exe",
+                  "powershell.exe", "pwsh.exe", "wmic.exe", "wscript.exe", "bitsadmin.exe", "certutil.exe", "ftp.exe")
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.parent.name:(AcroRd32.exe or Acrobat.exe or
-FoxitPhantomPDF.exe or FoxitReader.exe) and process.name:(arp.exe or
-dsquery.exe or dsget.exe or gpresult.exe or hostname.exe or
-ipconfig.exe or nbtstat.exe or net.exe or net1.exe or netsh.exe or
-netstat.exe or nltest.exe or ping.exe or qprocess.exe or quser.exe or
-qwinsta.exe or reg.exe or sc.exe or systeminfo.exe or tasklist.exe or
-tracert.exe or whoami.exe or bginfo.exe or cdb.exe or cmstp.exe or
-csi.exe or dnx.exe or fsi.exe or ieexec.exe or iexpress.exe or
-installutil.exe or Microsoft.Workflow.Compiler.exe or msbuild.exe or
-mshta.exe or msxsl.exe or odbcconf.exe or rcsi.exe or regsvr32.exe or
-xwizard.exe or atbroker.exe or forfiles.exe or schtasks.exe or
-regasm.exe or regsvcs.exe or cmd.exe or cscript.exe or powershell.exe
-or pwsh.exe or wmic.exe or wscript.exe or bitsadmin.exe or
-certutil.exe or ftp.exe)
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Exploitation for Client Execution
+** ID: T1203
+** Reference URL: https://attack.mitre.org/techniques/T1203/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-portable-executable-encoded-in-powershell-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-portable-executable-encoded-in-powershell-script.asciidoc
index 28840343c8..e8413713c3 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-portable-executable-encoded-in-powershell-script.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-portable-executable-encoded-in-powershell-script.asciidoc
@@ -5,98 +5,102 @@ Detects the presence of a portable executable (PE) in a PowerShell script by loo
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.powershell*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/atc-project/atc-data/blob/master/docs/Logging_Policies/LP_0109_windows_powershell_script_block_log.md
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Investigation Guide
-
-*Version*: 102 (<<suspicious-portable-executable-encoded-in-powershell-script-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: PowerShell Logs
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious Portable Executable Encoded in Powershell Script
+*Triage and analysis*
+
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This
-makes it available for use in various environments, and creates an attractive way for attackers to execute code.
 
-Attackers can abuse PowerShell in-memory capabilities to inject executables into memory without touching the disk,
-bypassing file-based security protections. These executables are generally base64 encoded.
+*Investigating Suspicious Portable Executable Encoded in Powershell Script*
+
+
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+
+Attackers can abuse PowerShell in-memory capabilities to inject executables into memory without touching the disk, bypassing file-based security protections. These executables are generally base64 encoded.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-#### Possible investigation steps
 
-- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration
-capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
-- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for
-prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Examine the script content that triggered the detection; look for suspicious DLL imports, collection or exfiltration capabilities, suspicious functions, encoded or compressed data, and other potentially malicious characteristics.
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Evaluate whether the user needs to use PowerShell to complete tasks.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the script using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Related rules
+
+*Related rules*
+
 
 - Suspicious .NET Reflection via PowerShell - e26f042e-c590-4e82-8e05-41e81bd822ad
 - PowerShell Suspicious Payload Encoded and Compressed - 81fe9dc6-a2d7-4192-a2d8-eed98afc766a
 - PowerShell PSReflect Script - 56f2e9b5-4803-4e44-a0a4-a52dc79d57fe
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
@@ -104,74 +108,70 @@ prevalence, whether they are located in expected locations, and if they are sign
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
 - Reimage the host operating system or restore the compromised files to clean versions.
 - Restrict PowerShell usage outside of IT and engineering business units using GPOs, AppLocker, Intune, or similar software.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
-==== Rule query
-
+==== Setup
 
-[source,js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-TVqQAAMAAAAEAAAA )
-----------------------------------
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+*Setup*
 
-* Tactic:
-** Name: Execution
-** ID: TA0002
-** Reference URL: https://attack.mitre.org/tactics/TA0002/
-* Technique:
-** Name: Command and Scripting Interpreter
-** ID: T1059
-** Reference URL: https://attack.mitre.org/techniques/T1059/
 
-[[suspicious-portable-executable-encoded-in-powershell-script-history]]
-==== Rule version history
+The 'PowerShell Script Block Logging' logging policy must be enabled.
+Steps to implement the logging policy with Advanced Audit Configuration:
 
-Version 102 (8.6.0 release)::
-* Formatting only
+```
+Computer Configuration >
+Administrative Templates >
+Windows PowerShell >
+Turn on PowerShell Script Block Logging (Enable)
+```
 
-Version 101 (8.5.0 release)::
-* Formatting only
+Steps to implement the logging policy via registry:
 
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and powershell.file.script_block_text : (
-TVqQAAMAAAAEAAAA )
-----------------------------------
+```
+reg add "hklm\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging" /v EnableScriptBlockLogging /t REG_DWORD /d 1
+```
 
-Version 6 (8.3.0 release)::
-* Formatting only
 
-Version 5 (8.2.0 release)::
-* Formatting only
+==== Rule query
 
-Version 4 (8.1.0 release)::
-* Formatting only
 
-Version 3 (8.0.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.code:"4104" and powershell.file.script_block_text : (
-TVqQAAMAAAAEAAAA )
+event.category:process and host.os.type:windows and
+  powershell.file.script_block_text : (
+    TVqQAAMAAAAEAAAA
+  ) and not user.id : "S-1-5-18"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-powershell-engine-imageload.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-powershell-engine-imageload.asciidoc
index d1c3c0c64d..6002abc7c6 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-powershell-engine-imageload.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-powershell-engine-imageload.asciidoc
@@ -3,67 +3,63 @@
 
 Identifies the PowerShell engine being invoked by unexpected processes. Rather than executing PowerShell functionality with powershell.exe, some attackers do this to operate more stealthily.
 
-*Rule type*: eql
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
-* winlogbeat-*
-* logs-windows.*
-* endgame-*
+* logs-endpoint.events.library-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<suspicious-powershell-engine-imageload-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 210
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious PowerShell Engine ImageLoad
+*Triage and analysis*
+
+
 
-PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This
-makes it available for use in various environments, and creates an attractive way for attackers to execute code.
+*Investigating Suspicious PowerShell Engine ImageLoad*
 
-Attackers can use PowerShell without having to execute `PowerShell.exe` directly. This technique, often called
-"PowerShell without PowerShell," works by using the underlying System.Management.Automation namespace and can bypass
-application allowlisting and PowerShell security features.
 
-#### Possible investigation steps
+PowerShell is one of the main tools system administrators use for automation, report routines, and other tasks. This makes it available for use in various environments, and creates an attractive way for attackers to execute code.
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file
-modifications, and any spawned child processes.
+Attackers can use PowerShell without having to execute `PowerShell.exe` directly. This technique, often called "PowerShell without PowerShell," works by using the underlying System.Management.Automation namespace and can bypass application allowlisting and PowerShell security features.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Inspect the host for suspicious or abnormal behavior in the alert timeframe.
 - Retrieve the implementation (DLL, executable, etc.) and determine if it is malicious:
@@ -76,12 +72,15 @@ modifications, and any spawned child processes.
   - Use the PowerShell `Get-FileHash` cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
 
-- This activity can happen legitimately. Some vendors have their own PowerShell implementations that are shipped with
-some products. These benign true positives (B-TPs) can be added as exceptions if necessary after analysis.
+*False positive analysis*
+
+
+- This activity can happen legitimately. Some vendors have their own PowerShell implementations that are shipped with some products. These benign true positives (B-TPs) can be added as exceptions if necessary after analysis.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
@@ -89,62 +88,38 @@ some products. These benign true positives (B-TPs) can be added as exceptions if
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-
-
-If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define `event.ingested` and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate `event.ingested` to @timestamp for this rule to work.
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-any where (event.category : ("library", "driver") or (event.category
-== "process" and event.action : "Image loaded*")) and (dll.name :
-("System.Management.Automation.ni.dll",
-"System.Management.Automation.dll") or file.name :
-("System.Management.Automation.ni.dll",
-"System.Management.Automation.dll")) and /* add false positives
-relevant to your environment here */ not process.executable :
-("C:\\Windows\\System32\\RemoteFXvGPUDisablement.exe",
-"C:\\Windows\\System32\\sdiagnhost.exe") and not process.executable
-regex~ """C:\\Program Files( \(x86\))?\\*\.exe""" and not
-process.name : ( "Altaro.SubAgent.exe", "AppV_Manage.exe",
-"azureadconnect.exe", "CcmExec.exe", "configsyncrun.exe",
-"choco.exe", "ctxappvservice.exe", "DVLS.Console.exe",
-"edgetransport.exe", "exsetup.exe",
-"forefrontactivedirectoryconnector.exe", "InstallUtil.exe",
-"JenkinsOnDesktop.exe",
-"Microsoft.EnterpriseManagement.ServiceManager.UI.Console.exe",
-"mmc.exe", "mscorsvw.exe", "msexchangedelivery.exe",
-"msexchangefrontendtransport.exe", "msexchangehmworker.exe",
-"msexchangesubmission.exe", "msiexec.exe", "MsiExec.exe",
-"noderunner.exe", "NServiceBus.Host.exe",
-"NServiceBus.Host32.exe",
-"NServiceBus.Hosting.Azure.HostProcess.exe", "OuiGui.WPF.exe",
-"powershell.exe", "powershell_ise.exe", "pwsh.exe",
-"SCCMCliCtrWPF.exe", "ScriptEditor.exe", "ScriptRunner.exe",
-"sdiagnhost.exe", "servermanager.exe", "setup100.exe",
-"ServiceHub.VSDetouredHost.exe", "SPCAF.Client.exe",
-"SPCAF.SettingsEditor.exe", "SQLPS.exe",
-"telemetryservice.exe", "UMWorkerProcess.exe", "w3wp.exe",
-"wsmprovhost.exe" )
+[source, js]
 ----------------------------------
+host.os.type:windows and event.category:library and 
+  dll.name:("System.Management.Automation.dll" or "System.Management.Automation.ni.dll") and 
+  not (
+    process.code_signature.subject_name:("Microsoft Corporation" or "Microsoft Dynamic Code Publisher" or "Microsoft Windows") and process.code_signature.trusted:true and not process.name.caseless:("regsvr32.exe" or "rundll32.exe")
+  ) and 
+  not (
+    process.executable.caseless:(C\:\\Program*Files*\(x86\)\\*.exe or C\:\\Program*Files\\*.exe) and
+    process.code_signature.trusted:true
+  ) and 
+  not (
+    process.executable.caseless: C\:\\Windows\\Lenovo\\*.exe and process.code_signature.subject_name:"Lenovo" and 
+    process.code_signature.trusted:true
+  ) and 
+  not (
+    process.executable.caseless: "C:\\ProgramData\\chocolatey\\choco.exe" and
+    process.code_signature.subject_name:"Chocolatey Software, Inc." and process.code_signature.trusted:true
+  ) and not process.executable.caseless : "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -156,152 +131,7 @@ process.name : ( "Altaro.SubAgent.exe", "AppV_Manage.exe",
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[suspicious-powershell-engine-imageload-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-any where (event.category == "library" or (event.category == "process"
-and event.action : "Image loaded*")) and (dll.name :
-("System.Management.Automation.ni.dll",
-"System.Management.Automation.dll") or file.name :
-("System.Management.Automation.ni.dll",
-"System.Management.Automation.dll")) and /* add false positives
-relevant to your environment here */ not process.executable :
-("C:\\Windows\\System32\\RemoteFXvGPUDisablement.exe",
-"C:\\Windows\\System32\\sdiagnhost.exe") and not process.executable
-regex~ """C:\\Program Files( \(x86\))?\\*\.exe""" and not
-process.name : ( "Altaro.SubAgent.exe", "AppV_Manage.exe",
-"azureadconnect.exe", "CcmExec.exe", "configsyncrun.exe",
-"choco.exe", "ctxappvservice.exe", "DVLS.Console.exe",
-"edgetransport.exe", "exsetup.exe",
-"forefrontactivedirectoryconnector.exe", "InstallUtil.exe",
-"JenkinsOnDesktop.exe",
-"Microsoft.EnterpriseManagement.ServiceManager.UI.Console.exe",
-"mmc.exe", "mscorsvw.exe", "msexchangedelivery.exe",
-"msexchangefrontendtransport.exe", "msexchangehmworker.exe",
-"msexchangesubmission.exe", "msiexec.exe", "MsiExec.exe",
-"noderunner.exe", "NServiceBus.Host.exe",
-"NServiceBus.Host32.exe",
-"NServiceBus.Hosting.Azure.HostProcess.exe", "OuiGui.WPF.exe",
-"powershell.exe", "powershell_ise.exe", "pwsh.exe",
-"SCCMCliCtrWPF.exe", "ScriptEditor.exe", "ScriptRunner.exe",
-"sdiagnhost.exe", "servermanager.exe", "setup100.exe",
-"ServiceHub.VSDetouredHost.exe", "SPCAF.Client.exe",
-"SPCAF.SettingsEditor.exe", "SQLPS.exe",
-"telemetryservice.exe", "UMWorkerProcess.exe", "w3wp.exe",
-"wsmprovhost.exe" )
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-library where dll.name : ("System.Management.Automation.ni.dll",
-"System.Management.Automation.dll") and /* add false positives
-relevant to your environment here */ not process.executable :
-("C:\\Windows\\System32\\RemoteFXvGPUDisablement.exe",
-"C:\\Windows\\System32\\sdiagnhost.exe") and not process.executable
-regex~ """C:\\Program Files( \(x86\))?\\*\.exe""" and not
-process.name : ( "Altaro.SubAgent.exe", "AppV_Manage.exe",
-"azureadconnect.exe", "CcmExec.exe", "configsyncrun.exe",
-"choco.exe", "ctxappvservice.exe", "DVLS.Console.exe",
-"edgetransport.exe", "exsetup.exe",
-"forefrontactivedirectoryconnector.exe", "InstallUtil.exe",
-"JenkinsOnDesktop.exe",
-"Microsoft.EnterpriseManagement.ServiceManager.UI.Console.exe",
-"mmc.exe", "mscorsvw.exe", "msexchangedelivery.exe",
-"msexchangefrontendtransport.exe", "msexchangehmworker.exe",
-"msexchangesubmission.exe", "msiexec.exe", "MsiExec.exe",
-"noderunner.exe", "NServiceBus.Host.exe",
-"NServiceBus.Host32.exe",
-"NServiceBus.Hosting.Azure.HostProcess.exe", "OuiGui.WPF.exe",
-"powershell.exe", "powershell_ise.exe", "pwsh.exe",
-"SCCMCliCtrWPF.exe", "ScriptEditor.exe", "ScriptRunner.exe",
-"sdiagnhost.exe", "servermanager.exe", "setup100.exe",
-"ServiceHub.VSDetouredHost.exe", "SPCAF.Client.exe",
-"SPCAF.SettingsEditor.exe", "SQLPS.exe",
-"telemetryservice.exe", "UMWorkerProcess.exe", "w3wp.exe",
-"wsmprovhost.exe" )
-----------------------------------
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-library where dll.name : ("System.Management.Automation.ni.dll",
-"System.Management.Automation.dll") and /* add false positives
-relevant to your environment here */ not process.executable :
-("C:\\Windows\\System32\\RemoteFXvGPUDisablement.exe",
-"C:\\Windows\\System32\\sdiagnhost.exe", "C:\\Program Files*\\*.exe")
-and not process.name : ( "Altaro.SubAgent.exe",
-"AppV_Manage.exe", "azureadconnect.exe", "CcmExec.exe",
-"configsyncrun.exe", "choco.exe", "ctxappvservice.exe",
-"DVLS.Console.exe", "edgetransport.exe", "exsetup.exe",
-"forefrontactivedirectoryconnector.exe", "InstallUtil.exe",
-"JenkinsOnDesktop.exe",
-"Microsoft.EnterpriseManagement.ServiceManager.UI.Console.exe",
-"mmc.exe", "mscorsvw.exe", "msexchangedelivery.exe",
-"msexchangefrontendtransport.exe", "msexchangehmworker.exe",
-"msexchangesubmission.exe", "msiexec.exe", "MsiExec.exe",
-"noderunner.exe", "NServiceBus.Host.exe",
-"NServiceBus.Host32.exe",
-"NServiceBus.Hosting.Azure.HostProcess.exe", "OuiGui.WPF.exe",
-"powershell.exe", "powershell_ise.exe", "pwsh.exe",
-"SCCMCliCtrWPF.exe", "ScriptEditor.exe", "ScriptRunner.exe",
-"sdiagnhost.exe", "servermanager.exe", "setup100.exe",
-"ServiceHub.VSDetouredHost.exe", "SPCAF.Client.exe",
-"SPCAF.SettingsEditor.exe", "SQLPS.exe",
-"telemetryservice.exe", "UMWorkerProcess.exe", "w3wp.exe",
-"wsmprovhost.exe" )
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-library where file.name : ("System.Management.Automation.ni.dll",
-"System.Management.Automation.dll") and /* add false positives
-relevant to your environment here */ not process.executable :
-("C:\\Windows\\System32\\RemoteFXvGPUDisablement.exe",
-"C:\\Windows\\System32\\sdiagnhost.exe", "C:\\Program Files*\\*.exe")
-and not process.name : ( "Altaro.SubAgent.exe",
-"AppV_Manage.exe", "azureadconnect.exe", "CcmExec.exe",
-"configsyncrun.exe", "choco.exe", "ctxappvservice.exe",
-"DVLS.Console.exe", "edgetransport.exe", "exsetup.exe",
-"forefrontactivedirectoryconnector.exe", "InstallUtil.exe",
-"JenkinsOnDesktop.exe",
-"Microsoft.EnterpriseManagement.ServiceManager.UI.Console.exe",
-"mmc.exe", "mscorsvw.exe", "msexchangedelivery.exe",
-"msexchangefrontendtransport.exe", "msexchangehmworker.exe",
-"msexchangesubmission.exe", "msiexec.exe", "MsiExec.exe",
-"noderunner.exe", "NServiceBus.Host.exe",
-"NServiceBus.Host32.exe",
-"NServiceBus.Hosting.Azure.HostProcess.exe", "OuiGui.WPF.exe",
-"powershell.exe", "powershell_ise.exe", "pwsh.exe",
-"SCCMCliCtrWPF.exe", "ScriptEditor.exe", "ScriptRunner.exe",
-"sdiagnhost.exe", "servermanager.exe", "setup100.exe",
-"ServiceHub.VSDetouredHost.exe", "SPCAF.Client.exe",
-"SPCAF.SettingsEditor.exe", "SQLPS.exe", "telemetryservice.exe",
-"UMWorkerProcess.exe", "w3wp.exe", "wsmprovhost.exe" )
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-powershell-script.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-powershell-script.asciidoc
index fcc20de521..c06d6a8c8b 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-powershell-script.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-powershell-script.asciidoc
@@ -5,49 +5,40 @@ A machine learning job detected a PowerShell script with unusual data characteri
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_windows_anomalous_script
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 * https://www.elastic.co/security-labs/detecting-living-off-the-land-attacks-with-new-elastic-integration
 
-*Tags*:
-
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
-* Execution
+*Tags*: 
 
-*Version*: 101 (<<suspicious-powershell-script-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Execution
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Certain kinds of security testing may trigger this alert. PowerShell scripts that use high levels of obfuscation or have unusual script block payloads may trigger this alert.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -59,28 +50,7 @@ Certain kinds of security testing may trigger this alert. PowerShell scripts tha
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[suspicious-powershell-script-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-file-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-file-deletion.asciidoc
index 8c88f21186..f464e74a3c 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-file-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-file-deletion.asciidoc
@@ -5,68 +5,71 @@ Detects deletion of print driver files by an unusual process. This may indicate
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-34527
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 100 (<<suspicious-print-spooler-file-deletion-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Uninstall or manual deletion of a legitimate printing driver files. Verify the printer file metadata such as manufacturer and signature information.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type : "deletion" and not process.name :
-("spoolsv.exe", "dllhost.exe", "explorer.exe") and file.path :
-"?:\\Windows\\System32\\spool\\drivers\\x64\\3\\*.dll"
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type : "deletion" and
+ not process.name : ("spoolsv.exe", "dllhost.exe", "explorer.exe") and
+ file.path : "?:\\Windows\\System32\\spool\\drivers\\x64\\3\\*.dll"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,19 +81,3 @@ file where event.type : "deletion" and not process.name :
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-[[suspicious-print-spooler-file-deletion-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-point-and-print-dll.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-point-and-print-dll.asciidoc
index 082f5ddbe1..4f031b53ae 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-point-and-print-dll.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-point-and-print-dll.asciidoc
@@ -5,61 +5,68 @@ Detects attempts to exploit a privilege escalation vulnerability (CVE-2020-1030)
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.accenture.com/us-en/blogs/cyber-defense/discovering-exploiting-shutting-down-dangerous-windows-print-spooler-vulnerability
 * https://github.com/sbousseaden/EVTX-ATTACK-SAMPLES/blob/master/Privilege%20Escalation/privesc_sysmon_cve_20201030_spooler.evtx
 * https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2020-1030
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 100 (<<suspicious-print-spooler-point-and-print-dll-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=30s [registry where registry.path :
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Print\\Printers\\*\\SpoolDirectory" and
-registry.data.strings :
-"C:\\Windows\\System32\\spool\\drivers\\x64\\4"] [registry where
-registry.path : "HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Print\\Printers\\*\\CopyFiles\\Payload\\Module"
-and registry.data.strings :
-"C:\\Windows\\System32\\spool\\drivers\\x64\\4\\*"]
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=30s
+[registry where host.os.type == "windows" and
+ registry.path : (
+    "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Print\\Printers\\*\\SpoolDirectory",
+    "\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Print\\Printers\\*\\SpoolDirectory"
+    ) and
+ registry.data.strings : "C:\\Windows\\System32\\spool\\drivers\\x64\\4"]
+[registry where host.os.type == "windows" and
+ registry.path : (
+    "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Print\\Printers\\*\\CopyFiles\\Payload\\Module",
+    "\\REGISTRY\\MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Print\\Printers\\*\\CopyFiles\\Payload\\Module"
+    ) and
+ registry.data.strings : "C:\\Windows\\System32\\spool\\drivers\\x64\\4\\*"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -71,19 +78,3 @@ and registry.data.strings :
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-[[suspicious-print-spooler-point-and-print-dll-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-spl-file-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-spl-file-created.asciidoc
index 87f311cf91..19ba68b588 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-spl-file-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-print-spooler-spl-file-created.asciidoc
@@ -5,96 +5,96 @@ Detects attempts to exploit privilege escalation vulnerabilities related to the
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* endgame-*
 
-*Severity*: high
+*Severity*: medium
 
-*Risk score*: 73
+*Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://safebreach.com/Post/How-we-bypassed-CVE-2020-1048-Patch-and-got-CVE-2020-1337
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Investigation Guide
-
-*Version*: 102 (<<suspicious-print-spooler-spl-file-created-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious Print Spooler SPL File Created
+*Triage and analysis*
 
-Print Spooler is a Windows service enabled by default in all Windows clients and servers. The service manages print jobs
-by loading printer drivers, receiving files to be printed, queuing them, scheduling, etc.
 
-The Print Spooler service has some known vulnerabilities that attackers can abuse to escalate privileges to SYSTEM, like
-CVE-2020-1048 and CVE-2020-1337. This rule looks for unusual processes writing SPL files to the location
-`?:\Windows\System32\spool\PRINTERS\`, which is an essential step in exploiting these vulnerabilities.
+
+*Investigating Suspicious Print Spooler SPL File Created*
+
+
+Print Spooler is a Windows service enabled by default in all Windows clients and servers. The service manages print jobs by loading printer drivers, receiving files to be printed, queuing them, scheduling, etc.
+
+The Print Spooler service has some known vulnerabilities that attackers can abuse to escalate privileges to SYSTEM, like CVE-2020-1048 and CVE-2020-1337. This rule looks for unusual processes writing SPL files to the location `?:\Windows\System32\spool\PRINTERS\`, which is an essential step in exploiting these vulnerabilities.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Inspect the host for suspicious or abnormal behavior in the alert timeframe.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+
+*False positive analysis*
+
 
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of process executable and file conditions.
 
-### False positive analysis
 
-- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination
-of process executable and file conditions.
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -102,35 +102,60 @@ of process executable and file conditions.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Ensure that the machine has the latest security updates and is not running legacy Windows versions.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.extension : "spl" and
-file.path : "?:\\Windows\\System32\\spool\\PRINTERS\\*" and not
-process.name : ("spoolsv.exe",
-"printfilterpipelinesvc.exe",
-"PrintIsolationHost.exe", "splwow64.exe",
-"msiexec.exe", "poqexec.exe")
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and
+  file.extension : "spl" and
+  file.path : "?:\\Windows\\System32\\spool\\PRINTERS\\*" and
+  not process.name : ("spoolsv.exe",
+                      "printfilterpipelinesvc.exe",
+                      "PrintIsolationHost.exe",
+                      "splwow64.exe",
+                      "msiexec.exe",
+                      "poqexec.exe",
+                      "System") and
+  not user.id : "S-1-5-18" and
+  not process.executable :
+            ("?:\\Windows\\System32\\mmc.exe",
+             "\\Device\\Mup\\*.exe",
+             "?:\\Windows\\System32\\svchost.exe",
+             "?:\\Windows\\System32\\mmc.exe",
+             "?:\\Windows\\System32\\printui.exe",
+             "?:\\Windows\\System32\\mstsc.exe",
+             "?:\\Windows\\System32\\spool\\*.exe",
+             "?:\\Program Files\\*.exe",
+             "?:\\Program Files (x86)\\*.exe",
+             "?:\\PROGRA~1\\*.exe",
+             "?:\\PROGRA~2\\*.exe",
+             "?:\\Windows\\System32\\rundll32.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -142,36 +167,3 @@ process.name : ("spoolsv.exe",
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-[[suspicious-print-spooler-spl-file-created-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Rule name changed from: Suspicious PrintSpooler SPL File Created
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and not event.type:deletion and
-file.extension:(spl or SPL) and
-file.path:C\:\\Windows\\System32\\spool\\PRINTERS\\* and not
-process.name:(spoolsv.exe or printfilterpipelinesvc.exe or
-PrintIsolationHost.exe or splwow64.exe or msiexec.exe or poqexec.exe)
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-printspooler-service-executable-file-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-printspooler-service-executable-file-creation.asciidoc
index 0397ffbff9..b5f2fa085f 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-printspooler-service-executable-file-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-printspooler-service-executable-file-creation.asciidoc
@@ -5,66 +5,82 @@ Detects attempts to exploit privilege escalation vulnerabilities related to the
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://voidsec.com/cve-2020-1337-printdemon-is-dead-long-live-printdemon/
 * https://www.thezdi.com/blog/2020/7/8/cve-2020-1300-remote-code-execution-through-microsoft-windows-cab-files
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 100 (<<suspicious-printspooler-service-executable-file-creation-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and process.name : "spoolsv.exe"
-and file.extension : ("exe", "dll") and not file.path :
-("?:\\Windows\\System32\\spool\\*", "?:\\Windows\\Temp\\*",
-"?:\\Users\\*")
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and
+  process.name : "spoolsv.exe" and file.extension : "dll" and
+  file.path : ("?:\\Windows\\System32\\*", "?:\\Windows\\SysWOW64\\*") and
+  not file.path : (
+    "?:\\WINDOWS\\SysWOW64\\PrintConfig.dll",
+    "?:\\WINDOWS\\system32\\x5lrs.dll",
+    "?:\\WINDOWS\\sysWOW64\\x5lrs.dll",
+    "?:\\WINDOWS\\system32\\PrintConfig.dll",
+    "?:\\WINDOWS\\system32\\spool\\DRIVERS\\x64\\*.dll",
+    "?:\\WINDOWS\\system32\\spool\\DRIVERS\\W32X86\\*.dll",
+    "?:\\WINDOWS\\system32\\spool\\PRTPROCS\\x64\\*.dll",
+    "?:\\WINDOWS\\system32\\spool\\{????????-????-????-????-????????????}\\*.dll"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,33 +92,3 @@ and file.extension : ("exe", "dll") and not file.path :
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-[[suspicious-printspooler-service-executable-file-creation-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and not event.type:deletion and
-process.name:spoolsv.exe and file.extension:(exe or dll) and not
-file.path:(C\:\\Windows\\System32\\spool\\* or C\:\\Windows\\Temp\\*
-or C\:\\Users\\*)
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-proc-maps-discovery.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-proc-maps-discovery.asciidoc
new file mode 100644
index 0000000000..8d4e8846fc
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-proc-maps-discovery.asciidoc
@@ -0,0 +1,102 @@
+[[suspicious-proc-maps-discovery]]
+=== Suspicious /proc/maps Discovery
+
+Monitors for /proc/*/maps file reads. The /proc/*/maps file in Linux provides a memory map for a specific process, detailing the memory segments, permissions, and what files are mapped to these segments. Attackers may read a process's memory map to identify memory addresses for code injection or process hijacking.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/arget13/DDexec
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
+process.name in ("cat", "grep") and process.args : "/proc/*/maps" and process.entry_leader.name in (
+  "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Process Discovery
+** ID: T1057
+** Reference URL: https://attack.mitre.org/techniques/T1057/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-proc-pseudo-file-system-enumeration.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-proc-pseudo-file-system-enumeration.asciidoc
new file mode 100644
index 0000000000..35d9a7fbb1
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-proc-pseudo-file-system-enumeration.asciidoc
@@ -0,0 +1,94 @@
+[[suspicious-proc-pseudo-file-system-enumeration]]
+=== Suspicious Proc Pseudo File System Enumeration
+
+This rule monitors for a rapid enumeration of 25 different proc cmd, stat, and exe files, which suggests an abnormal activity pattern. Such behavior could be an indicator of a malicious process scanning or gathering information about running processes, potentially for reconnaissance, privilege escalation, or identifying vulnerable targets.
+
+*Rule type*: threshold
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires the use of the `auditd_manager` integration. `Auditd_manager` is a tool designed to simplify and enhance the management of the audit subsystem in Linux systems. It provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system. The following steps should be executed in order to install and deploy `auditd_manager` on a Linux system.
+
+```
+Kibana -->
+Management -->
+Integrations -->
+Auditd Manager -->
+Add Auditd Manager
+```
+
+`Auditd_manager` subscribes to the kernel and receives events as they occur without any additional configuration. However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+
+For this detection rule to trigger, the following additional audit rules are required to be added to the integration:
+```
+-w /proc/ -p r -k audit_proc
+```
+
+Add the newly installed `auditd manager` to an agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.category:file and event.action:"opened-file" and 
+file.path : (/proc/*/cmdline or /proc/*/stat or /proc/*/exe) and not process.name : (
+  ps or netstat or landscape-sysin or w or pgrep or pidof or needrestart or apparmor_status
+) and not process.parent.pid : 1
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Process Discovery
+** ID: T1057
+** Reference URL: https://attack.mitre.org/techniques/T1057/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-process-access-via-direct-system-call.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-process-access-via-direct-system-call.asciidoc
index b0241f2f5a..4fc3bd5001 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-process-access-via-direct-system-call.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-process-access-via-direct-system-call.asciidoc
@@ -5,97 +5,97 @@ Identifies suspicious process access events from an unknown memory region. Endpo
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://twitter.com/SBousseaden/status/1278013896440324096
 * https://www.ired.team/offensive-security/defense-evasion/using-syscalls-directly-from-visual-studio-to-bypass-avs-edrs
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Sysmon Only
-
-*Version*: 102 (<<suspicious-process-access-via-direct-system-call-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 211
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious Process Access via Direct System Call
+*Triage and analysis*
 
-Endpoint security solutions usually hook userland Windows APIs in order to decide if the code that is being executed is
-malicious or not. It's possible to bypass hooked functions by writing malicious functions that call syscalls directly.
 
-More context and technical details can be found in this [research blog](https://outflank.nl/blog/2019/06/19/red-team-tactics-combining-direct-system-calls-and-srdi-to-bypass-av-edr/).
 
-This rule identifies suspicious process access events from an unknown memory region. Attackers can use direct system
-calls to bypass security solutions that rely on hooks.
+*Investigating Suspicious Process Access via Direct System Call*
+
+
+Endpoint security solutions usually hook userland Windows APIs in order to decide if the code that is being executed is malicious or not. It's possible to bypass hooked functions by writing malicious functions that call syscalls directly.
+
+More context and technical details can be found in this https://outflank.nl/blog/2019/06/19/red-team-tactics-combining-direct-system-calls-and-srdi-to-bypass-av-edr/[research blog].
+
+This rule identifies suspicious process access events from an unknown memory region. Attackers can use direct system calls to bypass security solutions that rely on hooks.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+
+*False positive analysis*
+
 
+- This detection may be triggered by certain applications that install root certificates for the purpose of inspecting SSL traffic. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### False positive analysis
 
-- This detection may be triggered by certain applications that install root certificates for the purpose of inspecting
-SSL traffic. Benign true positives (B-TPs) can be added as exceptions if necessary.
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -103,49 +103,56 @@ SSL traffic. Benign true positives (B-TPs) can be added as exceptions if necessa
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove the malicious certificate from the root certificate store.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.code == "10" and
-length(winlog.event_data.CallTrace) > 0 and /* Sysmon CallTrace
-starting with unknown memory module instead of ntdll which host
-Windows NT Syscalls */ not winlog.event_data.CallTrace :
-("?:\\WINDOWS\\SYSTEM32\\ntdll.dll*",
-"?:\\WINDOWS\\SysWOW64\\ntdll.dll*",
-"?:\\Windows\\System32\\wow64cpu.dll*",
-"?:\\WINDOWS\\System32\\wow64win.dll*",
-"?:\\Windows\\System32\\win32u.dll*") and not
-winlog.event_data.TargetImage : ("?:\\Program Files
-(x86)\\Malwarebytes Anti-Exploit\\mbae-svc.exe",
-"?:\\Program Files\\Cisco\\AMP\\*\\sfc.exe", "?:\\Program
-Files
-(x86)\\Microsoft\\EdgeWebView\\Application\\*\\msedgewebview2.exe",
-"?:\\Program Files\\Adobe\\Acrobat DC\\Acrobat\\*\\AcroCEF.exe") and
-not (process.executable : ("?:\\Program Files\\Adobe\\Acrobat
-DC\\Acrobat\\Acrobat.exe", "?:\\Program
-Files (x86)\\World of Warcraft\\_classic_\\WowClassic.exe") and
-not winlog.event_data.TargetImage :
-"?:\\WINDOWS\\system32\\lsass.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.code == "10" and
+ length(winlog.event_data.CallTrace) > 0 and
+
+ /* Sysmon CallTrace starting with unknown memory module instead of ntdll which host Windows NT Syscalls */
+ not winlog.event_data.CallTrace :
+            ("?:\\WINDOWS\\SYSTEM32\\ntdll.dll*",
+             "?:\\WINDOWS\\SysWOW64\\ntdll.dll*",
+             "?:\\Windows\\System32\\wow64cpu.dll*",
+             "?:\\WINDOWS\\System32\\wow64win.dll*",
+             "?:\\Windows\\System32\\win32u.dll*") and
+
+ not winlog.event_data.TargetImage :
+            ("?:\\Program Files (x86)\\Malwarebytes Anti-Exploit\\mbae-svc.exe",
+             "?:\\Program Files\\Cisco\\AMP\\*\\sfc.exe",
+             "?:\\Program Files (x86)\\Microsoft\\EdgeWebView\\Application\\*\\msedgewebview2.exe",
+             "?:\\Program Files\\Adobe\\Acrobat DC\\Acrobat\\*\\AcroCEF.exe") and
+
+ not (process.executable : ("?:\\Program Files\\Adobe\\Acrobat DC\\Acrobat\\Acrobat.exe",
+                            "?:\\Program Files (x86)\\World of Warcraft\\_classic_\\WowClassic.exe") and
+      not winlog.event_data.TargetImage : "?:\\WINDOWS\\system32\\lsass.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -157,32 +164,11 @@ not winlog.event_data.TargetImage :
 ** Name: Process Injection
 ** ID: T1055
 ** Reference URL: https://attack.mitre.org/techniques/T1055/
-
-[[suspicious-process-access-via-direct-system-call-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.code == "10" and
-length(winlog.event_data.CallTrace) > 0 and /* Sysmon CallTrace
-starting with unknown memory module instead of ntdll which host
-Windows NT Syscalls */ not winlog.event_data.CallTrace :
-("?:\\WINDOWS\\SYSTEM32\\ntdll.dll*",
-"?:\\WINDOWS\\SysWOW64\\ntdll.dll*")
-----------------------------------
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.0.0 release)::
-* Formatting only
-
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Native API
+** ID: T1106
+** Reference URL: https://attack.mitre.org/techniques/T1106/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-process-creation-calltrace.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-process-creation-calltrace.asciidoc
index cb49a7cc44..a7d2ec42dd 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-process-creation-calltrace.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-process-creation-calltrace.asciidoc
@@ -5,120 +5,111 @@ Identifies when a process is created and immediately accessed from an unknown me
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Sysmon Only
+*Tags*: 
 
-*Version*: 102 (<<suspicious-process-creation-calltrace-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 8.0.0
+*Version*: 208
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious Process Creation CallTrace
+*Triage and analysis*
+
+
+
+*Investigating Suspicious Process Creation CallTrace*
 
-Attackers may inject code into child processes' memory to hide their actual activity, evade detection mechanisms, and
-decrease discoverability during forensics. This rule looks for a spawned process by Microsoft Office, scripting, and
-command line applications, followed by a process access event for an unknown memory region by the parent process, which
-can indicate a code injection attempt.
 
-#### Possible investigation steps
+Attackers may inject code into child processes' memory to hide their actual activity, evade detection mechanisms, and decrease discoverability during forensics. This rule looks for a spawned process by Microsoft Office, scripting, and command line applications, followed by a process access event for an unknown memory region by the parent process, which can indicate a code injection attempt.
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Investigate abnormal behavior observed by the subject process such as network connections, registry or file
-modifications, and any spawned child processes.
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Inspect the host for suspicious or abnormal behavior in the alert timeframe.
 - Create a memory dump of the child process for analysis.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan=1m [process where event.code == "1"
-and /* sysmon process creation */ process.parent.name :
-("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe",
-"eqnedt32.exe", "fltldr.exe", "mspub.exe",
-"msaccess.exe","cscript.exe", "wscript.exe", "rundll32.exe",
-"regsvr32.exe", "mshta.exe", "wmic.exe",
-"cmstp.exe", "msxsl.exe") and /* noisy FP patterns */ not
-(process.parent.name : "EXCEL.EXE" and process.executable :
-"?:\\Program Files\\Microsoft Office\\root\\Office*\\ADDINS\\*.exe")
-and not (process.executable : "?:\\Windows\\splwow64.exe" and
-process.args in ("8192", "12288") and process.parent.name :
-("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe")) and
-not (process.parent.name : "rundll32.exe" and process.parent.args : ("
-?:\\WINDOWS\\Installer\\MSI*.tmp,zzzzInvokeManagedCustomActionOutOfPro
-c", "--no-sandbox")) and not (process.executable :
-("?:\\Program Files
-(x86)\\Microsoft\\EdgeWebView\\Application\\*\\msedgewebview2.exe",
-"?:\\Program Files\\Adobe\\Acrobat DC\\Acrobat\\Acrobat.exe",
-"?:\\Windows\\SysWOW64\\DWWIN.EXE") and process.parent.name :
-("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe")) and
-not (process.parent.name : "regsvr32.exe" and process.parent.args :
-("?:\\Program Files\\*", "?:\\Program Files (x86)\\*")) ] by
-process.parent.entity_id, process.entity_id [process where
-event.code == "10" and /* Sysmon process access event from unknown
-module */ winlog.event_data.CallTrace : "*UNKNOWN*"] by
-process.entity_id, winlog.event_data.TargetProcessGUID
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan=1m
+  [process where host.os.type == "windows" and event.code == "1" and
+   /* sysmon process creation */
+   process.parent.name : ("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe", "eqnedt32.exe", "fltldr.exe",
+                          "mspub.exe", "msaccess.exe","cscript.exe", "wscript.exe", "rundll32.exe", "regsvr32.exe",
+                          "mshta.exe", "wmic.exe", "cmstp.exe", "msxsl.exe") and
+
+   /* noisy FP patterns */
+   not (process.parent.name : "EXCEL.EXE" and process.executable : "?:\\Program Files\\Microsoft Office\\root\\Office*\\ADDINS\\*.exe") and
+   not (process.executable : "?:\\Windows\\splwow64.exe" and process.args in ("8192", "12288") and process.parent.name : ("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe")) and
+   not (process.parent.name : "rundll32.exe" and process.parent.args : ("?:\\WINDOWS\\Installer\\MSI*.tmp,zzzzInvokeManagedCustomActionOutOfProc", "--no-sandbox")) and
+   not (process.executable :
+            ("?:\\Program Files (x86)\\Microsoft\\EdgeWebView\\Application\\*\\msedgewebview2.exe",
+             "?:\\Program Files\\Adobe\\Acrobat DC\\Acrobat\\Acrobat.exe",
+             "?:\\Windows\\SysWOW64\\DWWIN.EXE") and
+        process.parent.name : ("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe")) and
+   not (process.parent.name : "regsvr32.exe" and process.parent.args : ("?:\\Program Files\\*", "?:\\Program Files (x86)\\*"))
+   ] by process.parent.entity_id, process.entity_id
+  [process where host.os.type == "windows" and event.code == "10" and
+   /* Sysmon process access event from unknown module */
+   winlog.event_data.CallTrace : "*UNKNOWN*"] by process.entity_id, winlog.event_data.TargetProcessGUID
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -130,34 +121,3 @@ process.entity_id, winlog.event_data.TargetProcessGUID
 ** Name: Process Injection
 ** ID: T1055
 ** Reference URL: https://attack.mitre.org/techniques/T1055/
-
-[[suspicious-process-creation-calltrace-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=1m [process where event.code == "1"
-and /* sysmon process creation */ process.parent.name :
-("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe",
-"eqnedt32.exe", "fltldr.exe", "mspub.exe",
-"msaccess.exe", "powershell.exe", "pwsh.exe",
-"cscript.exe", "wscript.exe", "rundll32.exe", "regsvr32.exe",
-"mshta.exe", "wmic.exe", "cmstp.exe",
-"msxsl.exe")] by process.parent.entity_id, process.entity_id
-[process where event.code == "10" and /* Sysmon process access
-event from unknown module */ winlog.event_data.CallTrace :
-"*UNKNOWN*"] by process.entity_id, winlog.event_data.TargetProcessGUID
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-process-execution-via-renamed-psexec-executable.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-process-execution-via-renamed-psexec-executable.asciidoc
index ae91c5b8d5..12dfb1b615 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-process-execution-via-renamed-psexec-executable.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-process-execution-via-renamed-psexec-executable.asciidoc
@@ -5,111 +5,138 @@ Identifies suspicious psexec activity which is executing from the psexec service
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<suspicious-process-execution-via-renamed-psexec-executable-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Suspicious Process Execution via Renamed PsExec Executable*
 
-[source,js]
-----------------------------------
-process where event.type == "start" and
-process.pe.original_file_name : "psexesvc.exe" and not process.name :
-"PSEXESVC.exe"
-----------------------------------
 
-==== Threat mapping
+PsExec is a remote administration tool that enables the execution of commands with both regular and SYSTEM privileges on Windows systems. It operates by executing a service component `Psexecsvc` on a remote system, which then runs a specified process and returns the results to the local system. Microsoft develops PsExec as part of the Sysinternals Suite. Although commonly used by administrators, PsExec is frequently used by attackers to enable lateral movement and execute commands as SYSTEM to disable defenses and bypass security protections.
 
-*Framework*: MITRE ATT&CK^TM^
+This rule identifies instances where the PsExec service component is executed using a custom name. This behavior can indicate an attempt to bypass security controls or detections that look for the default PsExec service component name.
 
-* Tactic:
-** Name: Execution
-** ID: TA0002
-** Reference URL: https://attack.mitre.org/tactics/TA0002/
-* Technique:
-** Name: System Services
-** ID: T1569
-** Reference URL: https://attack.mitre.org/techniques/T1569/
 
-[[suspicious-process-execution-via-renamed-psexec-executable-history]]
-==== Rule version history
+*Possible investigation steps*
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.pe.original_file_name : "psexesvc.exe" and not process.name :
-"PSEXESVC.exe"
-----------------------------------
+- Check if the usage of this tool complies with the organization's administration policy.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Identify the target computer and its role in the IT environment.
+- Investigate what commands were run, and assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+
+
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. As long as the analyst did not identify suspicious activity related to the user or involved hosts, and the tool is allowed by the organization's policy, such alerts can be dismissed.
 
-Version 7 (8.4.0 release)::
-* Formatting only
 
-Version 5 (8.2.0 release)::
-* Formatting only
+*Response and remediation*
 
-Version 4 (7.12.0 release)::
-* Formatting only
 
-Version 3 (7.11.2 release)::
-* Formatting only
+- Initiate the incident response process based on the outcome of the triage.
+  - Prioritize cases involving critical servers and users.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Review the privileges assigned to the user to ensure that the least privilege principle is being followed.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
 
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.category:process and event.type:(start or process_started) and
-(process.pe.original_file_name:(psexesvc.exe or PSEXESVC.exe) or
-winlog.event_data.OriginalFileName:(psexesvc.exe or PSEXESVC.exe)) and
-process.parent.name:services.exe and not process.name:(psexesvc.exe or
-PSEXESVC.exe)
+process where host.os.type == "windows" and event.type == "start" and
+  process.pe.original_file_name : "psexesvc.exe" and not process.name : "PSEXESVC.exe"
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: System Services
+** ID: T1569
+** Reference URL: https://attack.mitre.org/techniques/T1569/
+* Sub-technique:
+** Name: Service Execution
+** ID: T1569.002
+** Reference URL: https://attack.mitre.org/techniques/T1569/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Rename System Utilities
+** ID: T1036.003
+** Reference URL: https://attack.mitre.org/techniques/T1036/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-process-spawned-from-motd-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-process-spawned-from-motd-detected.asciidoc
new file mode 100644
index 0000000000..b07d3e30e6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-process-spawned-from-motd-detected.asciidoc
@@ -0,0 +1,201 @@
+[[suspicious-process-spawned-from-motd-detected]]
+=== Suspicious Process Spawned from MOTD Detected
+
+Message of the day (MOTD) is the message that is presented to the user when a user connects to a Linux server via SSH or a serial connection. Linux systems contain several default MOTD files located in the "/etc/update-motd.d/" and "/usr/lib/update-notifier/" directories. These scripts run as the root user every time a user connects over SSH or a serial connection. Adversaries may create malicious MOTD files that grant them persistence onto the target every time a user connects to the system by executing a backdoor script or command. This rule detects the execution of potentially malicious processes through the MOTD utility.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://pberba.github.io/security/2022/02/06/linux-threat-hunting-for-persistence-initialization-scripts-and-shell-configuration/#10-boot-or-logon-initialization-scripts-motd
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Suspicious Process Spawned from MOTD Detected*
+
+
+The message-of-the-day (MOTD) is used to display a customizable system-wide message or information to users upon login in Linux.
+
+Attackers can abuse message-of-the-day (motd) files to run scripts, commands or malicious software every time a user connects to a system over SSH or a serial connection, by creating a new file within the `/etc/update-motd.d/` or `/usr/lib/update-notifier/` directory. Files in these directories will automatically run with root privileges when they are made executable.
+
+This rule identifies the execution of potentially malicious processes from a MOTD script, which is not likely to occur as default benign behavior. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible Investigation Steps*
+
+
+- Investigate the file that was created or modified from which the suspicious process was executed.
+  - !{osquery{"label":"Osquery - Retrieve File Information","query":"SELECT * FROM file WHERE path = {{file.path}}"}}
+- Investigate whether any other files in the `/etc/update-motd.d/` or `/usr/lib/update-notifier/` directories have been altered.
+  - !{osquery{"label":"Osquery - Retrieve File Listing Information","query":"SELECT * FROM file WHERE (path LIKE '/etc/update-motd.d/%' OR path LIKE '/usr/lib/update-notifier/%')"}}
+  - !{osquery{"label":"Osquery - Retrieve Additional File Listing Information","query":"SELECT\n  f.path,\n  u.username AS file_owner,\n  g.groupname AS group_owner,\n  datetime(f.atime, 'unixepoch') AS file_last_access_time,\n  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,\n  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,\n  datetime(f.btime, 'unixepoch') AS file_created_time,\n  f.size AS size_bytes\nFROM\n  file f\n  LEFT JOIN users u ON f.uid = u.uid\n  LEFT JOIN groups g ON f.gid = g.gid\nWHERE (path LIKE '/etc/update-motd.d/%' OR path LIKE '/usr/lib/update-notifier/%')\n"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+        - Cron jobs, services, and other persistence mechanisms.
+            - !{osquery{"label":"Osquery - Retrieve Crontab Information","query":"SELECT * FROM crontab"}}
+
+
+*Related Rules*
+
+
+- Potential Persistence Through MOTD File Creation Detected - 96d11d31-9a79-480f-8401-da28b194608f
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Delete the MOTD files or restore them to the original configuration.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and event.action : ("exec", "exec_event") and
+process.parent.executable : ("/etc/update-motd.d/*", "/usr/lib/update-notifier/*") and (
+  (process.name in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") and (
+    (process.args : ("-i", "-l")) or (process.parent.name == "socat" and process.parent.args : "*exec*"))) or
+  (process.name : ("nc", "ncat", "netcat", "nc.openbsd") and process.args_count >= 3 and 
+    not process.args : ("-*z*", "-*l*")) or
+  (process.name : "python*" and process.args : "-c" and process.args : (
+     "*import*pty*spawn*", "*import*subprocess*call*"
+  )) or
+  (process.name : "perl*" and process.args : "-e" and process.args : "*socket*" and process.args : (
+     "*exec*", "*system*"
+  )) or
+  (process.name : "ruby*" and process.args : ("-e", "-rsocket") and process.args : (
+     "*TCPSocket.new*", "*TCPSocket.open*"
+  )) or
+  (process.name : "lua*" and process.args : "-e" and process.args : "*socket.tcp*" and process.args : (
+     "*io.popen*", "*os.execute*"
+  )) or
+  (process.name : "php*" and process.args : "-r" and process.args : "*fsockopen*" and process.args : "*/bin/*sh*") or 
+  (process.name : ("awk", "gawk", "mawk", "nawk") and process.args : "*/inet/tcp/*") or 
+  (process.name in ("openssl", "telnet"))
+) and 
+not (
+  (process.parent.args : "--force") or
+  (process.args : ("/usr/games/lolcat", "/usr/bin/screenfetch")) or
+  (process.parent.name == "system-crash-notification")
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Initialization Scripts
+** ID: T1037
+** Reference URL: https://attack.mitre.org/techniques/T1037/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-rdp-activex-client-loaded.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-rdp-activex-client-loaded.asciidoc
index a60b21fbdf..924fecd808 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-rdp-activex-client-loaded.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-rdp-activex-client-loaded.asciidoc
@@ -5,71 +5,89 @@ Identifies suspicious Image Loading of the Remote Desktop Services ActiveX Clien
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.library-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://posts.specterops.io/revisiting-remote-desktop-lateral-movement-8fb905cb46c3
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-
-*Version*: 100 (<<suspicious-rdp-activex-client-loaded-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-any where (event.category == "library" or (event.category == "process"
-and event.action : "Image loaded*")) and (dll.name : "mstscax.dll" or
-file.name : "mstscax.dll") and /* depending on noise in your env
-add here extra paths */ process.executable : (
-"C:\\Windows\\*", "C:\\Users\\Public\\*",
-"C:\\Users\\Default\\*", "C:\\Intel\\*", "C:\\PerfLogs\\*",
-"C:\\ProgramData\\*", "\\Device\\Mup\\*", "\\\\*" ) and
-/* add here FPs */ not process.executable :
-("C:\\Windows\\System32\\mstsc.exe",
-"C:\\Windows\\SysWOW64\\mstsc.exe")
+[source, js]
 ----------------------------------
+any where host.os.type == "windows" and
+ (event.category : ("library", "driver") or (event.category == "process" and event.action : "Image loaded*")) and
+ (?dll.name : "mstscax.dll" or file.name : "mstscax.dll") and
+   /* depending on noise in your env add here extra paths  */
+  process.executable : (
+    "C:\\Windows\\*",
+    "C:\\Users\\Public\\*",
+    "C:\\Users\\Default\\*",
+    "C:\\Intel\\*",
+    "C:\\PerfLogs\\*",
+    "C:\\ProgramData\\*",
+    "\\Device\\Mup\\*",
+    "\\\\*"
+  ) and
+  /* add here FPs */
+  not process.executable : (
+    "?:\\Windows\\System32\\mstsc.exe",
+    "?:\\Windows\\SysWOW64\\mstsc.exe",
+    "?:\\Windows\\System32\\vmconnect.exe",
+    "?:\\Windows\\System32\\WindowsSandboxClient.exe",
+    "?:\\Windows\\System32\\hvsirdpclient.exe"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,49 +99,7 @@ add here extra paths */ process.executable : (
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[suspicious-rdp-activex-client-loaded-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-library where dll.name : "mstscax.dll" and /* depending on noise in
-your env add here extra paths */ process.executable : (
-"C:\\Windows\\*", "C:\\Users\\Public\\*",
-"C:\\Users\\Default\\*", "C:\\Intel\\*", "C:\\PerfLogs\\*",
-"C:\\ProgramData\\*", "\\Device\\Mup\\*", "\\\\*" ) and
-/* add here FPs */ not process.executable :
-("C:\\Windows\\System32\\mstsc.exe",
-"C:\\Windows\\SysWOW64\\mstsc.exe")
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-library where file.name == "mstscax.dll" and /* depending on noise
-in your env add here extra paths */ wildcard(process.executable,
-"C:\\Windows\\*",
-"C:\\Users\\Public\\*",
-"C:\\Users\\Default\\*",
-"C:\\Intel\\*", "C:\\PerfLogs\\*",
-"C:\\ProgramData\\*",
-"\\Device\\Mup\\*", "\\\\*") and
-/* add here FPs */ not process.executable in
-("C:\\Windows\\System32\\mstsc.exe",
-"C:\\Windows\\SysWOW64\\mstsc.exe")
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Remote Desktop Protocol
+** ID: T1021.001
+** Reference URL: https://attack.mitre.org/techniques/T1021/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-remote-registry-access-via-sebackupprivilege.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-remote-registry-access-via-sebackupprivilege.asciidoc
index 17a83d821a..dc8ba9c1ac 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-remote-registry-access-via-sebackupprivilege.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-remote-registry-access-via-sebackupprivilege.asciidoc
@@ -5,110 +5,140 @@ Identifies remote access to the registry using an account with Backup Operators
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/mpgn/BackupOperatorToDA
 * https://raw.githubusercontent.com/Wh04m1001/Random/main/BackupOperators.cpp
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-* Credential Access
-* Investigation Guide
-
-*Version*: 102 (<<suspicious-remote-registry-access-via-sebackupprivilege-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
+* Data Source: Active Directory
 
-*Added ({stack} release)*: 8.2.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious Remote Registry Access via SeBackupPrivilege
+*Triage and analysis*
+
+
+
+*Investigating Suspicious Remote Registry Access via SeBackupPrivilege*
+
+
+SeBackupPrivilege is a privilege that allows file content retrieval, designed to enable users to create backup copies of the system. Since it is impossible to make a backup of something you cannot read, this privilege comes at the cost of providing the user with full read access to the file system. This privilege must bypass any access control list (ACL) placed in the system.
 
-SeBackupPrivilege is a privilege that allows file content retrieval, designed to enable users to create backup copies of
-the system. Since it is impossible to make a backup of something you cannot read, this privilege comes at the cost of
-providing the user with full read access to the file system. This privilege must bypass any access control list (ACL) placed in the system.
+This rule identifies remote access to the registry using an account with Backup Operators group membership. This may indicate an attempt to exfiltrate credentials by dumping the Security Account Manager (SAM) registry hive in preparation for credential access and privileges elevation.
 
-This rule identifies remote access to the registry using an account with Backup Operators group membership. This may
-indicate an attempt to exfiltrate credentials by dumping the Security Account Manager (SAM) registry hive in preparation
-for credential access and privileges elevation.
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
-- Investigate the activities done by the subject user the login session. The field `winlog.event_data.SubjectLogonId`
-can be used to get this data.
+- Investigate the activities done by the subject user the login session. The field `winlog.event_data.SubjectLogonId` can be used to get this data.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Contact the account owner and confirm whether they are aware of this activity.
-- Investigate abnormal behaviors observed by the subject user such as network connections, registry or file
-modifications, and processes created.
+- Investigate abnormal behaviors observed by the subject user such as network connections, registry or file modifications, and processes created.
 - Investigate if the registry file was retrieved or exfiltrated.
 
-### False positive analysis
 
-- If this activity is expected and noisy in your environment, benign true positives (B-TPs) can be added as exceptions
-if necessary.
+*False positive analysis*
+
+
+- If this activity is expected and noisy in your environment, benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Limit or disable the involved user account to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Detailed File Share' audit policy is required be configured (Success) on Domain Controllers and Sensitive Windows Servers.
+Steps to implement the logging policy with Advanced Audit Configuration:
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+Object Access >
+Audit Detailed File Share (Success)
+```
+
+The 'Special Logon' audit policy must be configured (Success).
+Steps to implement the logging policy with Advanced Audit Configuration:
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+Logon/Logoff >
+Special Logon (Success)
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, winlog.event_data.SubjectLogonId with maxspan=1m
-[iam where event.action == "logged-in-special" and
-winlog.event_data.PrivilegeList : "SeBackupPrivilege" and /*
-excluding accounts with existing privileged access */ not
-winlog.event_data.PrivilegeList : "SeDebugPrivilege"] [any where
-event.action == "Detailed File Share" and
-winlog.event_data.RelativeTargetName : "winreg"]
+[source, js]
 ----------------------------------
+sequence by winlog.computer_name, winlog.event_data.SubjectLogonId with maxspan=1m
+ [iam where event.action == "logged-in-special"  and
+  winlog.event_data.PrivilegeList : "SeBackupPrivilege" and
+
+  /* excluding accounts with existing privileged access */
+  not winlog.event_data.PrivilegeList : "SeDebugPrivilege"]
+ [any where event.action == "Detailed File Share" and winlog.event_data.RelativeTargetName : "winreg"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -120,8 +150,14 @@ winlog.event_data.RelativeTargetName : "winreg"]
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-
+* Sub-technique:
+** Name: Security Account Manager
+** ID: T1003.002
+** Reference URL: https://attack.mitre.org/techniques/T1003/002/
+* Sub-technique:
+** Name: LSA Secrets
+** ID: T1003.004
+** Reference URL: https://attack.mitre.org/techniques/T1003/004/
 * Tactic:
 ** Name: Lateral Movement
 ** ID: TA0008
@@ -130,28 +166,3 @@ winlog.event_data.RelativeTargetName : "winreg"]
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[suspicious-remote-registry-access-via-sebackupprivilege-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, winlog.event_data.SubjectLogonId with maxspan=1m
-[iam where event.action == "logged-in-special" and
-winlog.event_data.PrivilegeList : "SeBackupPrivilege"] [any where
-event.action == "Detailed File Share" and
-winlog.event_data.RelativeTargetName : "winreg"]
-----------------------------------
-
-Version 2 (8.3.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-renaming-of-esxi-files.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-renaming-of-esxi-files.asciidoc
new file mode 100644
index 0000000000..f6261063db
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-renaming-of-esxi-files.asciidoc
@@ -0,0 +1,104 @@
+[[suspicious-renaming-of-esxi-files]]
+=== Suspicious Renaming of ESXI Files
+
+Identifies instances where VMware-related files, such as those with extensions like ".vmdk", ".vmx", ".vmxf", ".vmsd", ".vmsn", ".vswp", ".vmss", ".nvram", and ".vmem", are renamed on a Linux system. The rule monitors for the "rename" event action associated with these file types, which could indicate malicious activity.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.bleepingcomputer.com/news/security/massive-esxiargs-ransomware-attack-targets-vmware-esxi-servers-worldwide/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "linux" and event.action == "rename" and
+file.Ext.original.name : ("*.vmdk", "*.vmx", "*.vmxf", "*.vmsd", "*.vmsn", "*.vswp", "*.vmss", "*.nvram", "*.vmem")
+and not file.name : ("*.vmdk", "*.vmx", "*.vmxf", "*.vmsd", "*.vmsn", "*.vswp", "*.vmss", "*.nvram", "*.vmem")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Rename System Utilities
+** ID: T1036.003
+** Reference URL: https://attack.mitre.org/techniques/T1036/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-renaming-of-esxi-index-html-file.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-renaming-of-esxi-index-html-file.asciidoc
new file mode 100644
index 0000000000..baf1776ad8
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-renaming-of-esxi-index-html-file.asciidoc
@@ -0,0 +1,103 @@
+[[suspicious-renaming-of-esxi-index-html-file]]
+=== Suspicious Renaming of ESXI index.html File
+
+Identifies instances where the "index.html" file within the "/usr/lib/vmware/*" directory is renamed on a Linux system. The rule monitors for the "rename" event action associated with this specific file and path, which could indicate malicious activity.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.bleepingcomputer.com/news/security/massive-esxiargs-ransomware-attack-targets-vmware-esxi-servers-worldwide/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "linux" and event.action == "rename" and file.name : "index.html" and
+file.Ext.original.path : "/usr/lib/vmware/*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Rename System Utilities
+** ID: T1036.003
+** Reference URL: https://attack.mitre.org/techniques/T1036/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-screenconnect-client-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-screenconnect-client-child-process.asciidoc
new file mode 100644
index 0000000000..9672f8383f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-screenconnect-client-child-process.asciidoc
@@ -0,0 +1,86 @@
+[[suspicious-screenconnect-client-child-process]]
+=== Suspicious ScreenConnect Client Child Process
+
+Identifies suspicious processes being spawned by the ScreenConnect client processes. This activity may indicate execution abusing unauthorized access to the ScreenConnect remote access software.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* winlogbeat-*
+* logs-windows.sysmon_operational-*
+* logs-system.security*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.huntress.com/blog/slashandgrab-screen-connect-post-exploitation-in-the-wild-cve-2024-1709-cve-2024-1708
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name :
+                ("ScreenConnect.ClientService.exe",
+                 "ScreenConnect.WindowsClient.exe",
+                 "ScreenConnect.WindowsBackstageShell.exe",
+                 "ScreenConnect.WindowsFileManager.exe") and
+  (
+   (process.name : "powershell.exe" and
+    process.args : ("-enc", "-ec", "-e", "*downloadstring*", "*Reflection.Assembly*", "*http*")) or
+   (process.name : "cmd.exe" and process.args : "/c") or
+   (process.name : "net.exe" and process.args : "/add") or
+   (process.name : "schtasks.exe" and process.args : ("/create", "-create")) or
+   (process.name : "sc.exe" and process.args : "create") or
+   (process.name : "rundll32.exe" and not process.args : "url.dll,FileProtocolHandler") or
+   (process.name : "msiexec.exe" and process.args : ("/i", "-i") and
+    process.args : ("/q", "/quiet", "/qn", "-q", "-quiet", "-qn", "-Q+")) or
+   process.name : ("mshta.exe", "certutil.exe", "bistadmin.exe", "certreq.exe", "wscript.exe", "cscript.exe", "curl.exe", 
+                   "ssh.exe", "scp.exe", "wevtutil.exe", "wget.exe", "wmic.exe")
+   )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Remote Access Software
+** ID: T1219
+** Reference URL: https://attack.mitre.org/techniques/T1219/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-script-object-execution.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-script-object-execution.asciidoc
index f6dd3cb612..86363c7e94 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-script-object-execution.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-script-object-execution.asciidoc
@@ -5,68 +5,71 @@ Identifies scrobj.dll loaded into unusual Microsoft processes. This usually mean
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.library-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<suspicious-script-object-execution-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id with maxspan=2m [process where
-event.type == "start" and (process.code_signature.subject_name in
-("Microsoft Corporation", "Microsoft Windows") and
-process.code_signature.trusted == true) and not
-process.executable : ( "?:\\Windows\\System32\\cscript.exe",
-"?:\\Windows\\SysWOW64\\cscript.exe", "?:\\Program Files
-(x86)\\Internet Explorer\\iexplore.exe", "?:\\Program
-Files\\Internet Explorer\\iexplore.exe", "?:\\Windows\\SystemAp
-ps\\Microsoft.MicrosoftEdge_*\\MicrosoftEdge.exe",
-"?:\\Windows\\system32\\msiexec.exe",
-"?:\\Windows\\SysWOW64\\msiexec.exe",
-"?:\\Windows\\System32\\smartscreen.exe",
-"?:\\Windows\\system32\\taskhostw.exe",
-"?:\\windows\\system32\\inetsrv\\w3wp.exe",
-"?:\\windows\\SysWOW64\\inetsrv\\w3wp.exe",
-"?:\\Windows\\system32\\wscript.exe",
-"?:\\Windows\\SysWOW64\\wscript.exe",
-"?:\\Windows\\system32\\mobsync.exe",
-"?:\\Windows\\SysWOW64\\mobsync.exe",
-"?:\\Windows\\System32\\cmd.exe",
-"?:\\Windows\\SysWOW64\\cmd.exe")] [library where event.type ==
-"start" and dll.name : "scrobj.dll"]
+[source, js]
 ----------------------------------
+any where host.os.type == "windows" and 
+ (event.category == "library" or (event.category == "process" and event.action : "Image loaded*")) and 
+ (?dll.name : "scrobj.dll" or ?file.name : "scrobj.dll") and 
+ process.executable : ("?:\\Windows\\System32\\*.exe", "?:\\Windows\\SysWOW64\\*.exe") and 
+ not process.executable : (
+       "?:\\Windows\\System32\\cscript.exe",
+       "?:\\Windows\\SysWOW64\\cscript.exe",
+       "?:\\Windows\\system32\\msiexec.exe",
+       "?:\\Windows\\SysWOW64\\msiexec.exe",
+       "?:\\Windows\\System32\\smartscreen.exe",
+       "?:\\Windows\\system32\\taskhostw.exe",
+       "?:\\windows\\system32\\inetsrv\\w3wp.exe",
+       "?:\\windows\\SysWOW64\\inetsrv\\w3wp.exe",
+       "?:\\Windows\\system32\\wscript.exe",
+       "?:\\Windows\\SysWOW64\\wscript.exe",
+       "?:\\Windows\\System32\\mshta.exe",
+       "?:\\Windows\\system32\\mobsync.exe",
+       "?:\\Windows\\SysWOW64\\mobsync.exe",
+       "?:\\Windows\\System32\\cmd.exe",
+       "?:\\Windows\\SysWOW64\\cmd.exe", 
+       "?:\\Windows\\System32\\OpenWith.exe",
+       "?:\\Windows\\System32\\wbem\\WMIADAP.exe",
+       "?:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,79 +81,7 @@ ps\\Microsoft.MicrosoftEdge_*\\MicrosoftEdge.exe",
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[suspicious-script-object-execution-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan=2m [process where
-event.type == "start" and (process.code_signature.subject_name in
-("Microsoft Corporation", "Microsoft Windows") and
-process.code_signature.trusted == true) and not
-process.executable : ( "?:\\Windows\\System32\\cscript.exe",
-"?:\\Windows\\SysWOW64\\cscript.exe", "?:\\Program Files
-(x86)\\Internet Explorer\\iexplore.exe", "?:\\Program
-Files\\Internet Explorer\\iexplore.exe", "?:\\Windows\\SystemAp
-ps\\Microsoft.MicrosoftEdge_*\\MicrosoftEdge.exe",
-"?:\\Windows\\system32\\msiexec.exe",
-"?:\\Windows\\SysWOW64\\msiexec.exe",
-"?:\\Windows\\System32\\smartscreen.exe",
-"?:\\Windows\\system32\\taskhostw.exe",
-"?:\\windows\\system32\\inetsrv\\w3wp.exe",
-"?:\\windows\\SysWOW64\\inetsrv\\w3wp.exe",
-"?:\\Windows\\system32\\wscript.exe",
-"?:\\Windows\\SysWOW64\\wscript.exe",
-"?:\\Windows\\system32\\mobsync.exe",
-"?:\\Windows\\SysWOW64\\mobsync.exe",
-"?:\\Windows\\System32\\cmd.exe",
-"?:\\Windows\\SysWOW64\\cmd.exe")] [library where event.type ==
-"start" and dll.name : "scrobj.dll"]
-----------------------------------
-
-Version 4 (7.13.0 release)::
-* Rule name changed from: Windows Suspicious Script Object Execution
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* add winlogbeat-* when process.code_signature.* fields are populated
-*/ sequence by process.entity_id with maxspan = 2m [process where
-event.type in ("start", "process_started") and /* uncomment once
-in winlogbeat */ /* process.code_signature.subject_name :
-"Microsoft Corporation" and process.code_signature.trusted : true and
-*/ not process.name : ( "cscript.exe",
-"iexplore.exe", "MicrosoftEdge.exe", "msiexec.exe",
-"smartscreen.exe", "taskhostw.exe", "w3wp.exe",
-"wscript.exe")] [library where event.type == "start" and dll.name :
-"scrobj.dll"]
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-/* add winlogbeat-* when process.code_signature.* fields are populated
-*/ sequence by process.entity_id with maxspan=2m [process where
-event.type in ("start", "process_started") and /* uncomment once
-in winlogbeat */ /* process.code_signature.subject_name ==
-"Microsoft Corporation" and process.code_signature.trusted == true and
-*/ not (process.name : "cscript.exe" or process.name :
-"iexplore.exe" or process.name : "MicrosoftEdge.exe" or
-process.name : "msiexec.exe" or process.name :
-"smartscreen.exe" or process.name : "taskhostw.exe" or
-process.name : "w3wp.exe" or process.name : "wscript.exe")]
-[library where event.type == "start" and file.name : "scrobj.dll"]
-----------------------------------
-
-Version 2 (7.11.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Regsvr32
+** ID: T1218.010
+** Reference URL: https://attack.mitre.org/techniques/T1218/010/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-service-was-installed-in-the-system.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-service-was-installed-in-the-system.asciidoc
index 32c723563c..7d5ebfb03b 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-service-was-installed-in-the-system.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-service-was-installed-in-the-system.asciidoc
@@ -1,97 +1,122 @@
 [[suspicious-service-was-installed-in-the-system]]
-=== Suspicious service was installed in the system
+=== Suspicious Service was Installed in the System
 
 Identifies the creation of a new Windows service with suspicious Service command values. Windows services typically run as SYSTEM and can be used for privilege escalation and persistence.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
 
-*Version*: 1
+*Version*: 8
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-#### Possible investigation steps
+*Triage and analysis*
+
+
+
+*Investigating Suspicious Service was Installed in the System*
+
+
+Attackers may create new services to execute system shells and other command execution utilities to elevate their privileges from administrator to SYSTEM. They can also configure services to execute these utilities with persistence payloads.
+
+This rule looks for suspicious services being created with suspicious traits compatible with the above behavior.
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Identify how the service was created or modified. Look for registry changes events or Windows events related to
-service activities (for example, 4697 and/or 7045).
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Identify how the service was created or modified. Look for registry changes events or Windows events related to service activities (for example, 4697 and/or 7045).
+  - Examine the created and existent services, the executables or drivers referenced, and command line arguments for suspicious entries.
+    - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+    - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+    - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+    - !{osquery{"label":"Osquery - Retrieve All Non-Microsoft Drivers with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, class, description, directory, image, issuer_name, manufacturer, service, signed, subject_name FROM drivers JOIN authenticode ON drivers.image = authenticode.path JOIN hash ON drivers.image = hash.path WHERE NOT (provider == \"Microsoft\" AND signed == \"1\")\n"}}
+    - !{osquery{"label":"Osquery - Retrieve All Unsigned Drivers with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, class, description, directory, image, issuer_name, manufacturer, service, signed, subject_name FROM drivers JOIN authenticode ON drivers.image = authenticode.path JOIN hash ON drivers.image = hash.path WHERE signed == \"0\"\n"}}
+  - Retrieve the referenced files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
 
 
-### False positive analysis
 
-- Certain services such as PSEXECSVC may happen legitimately. The security team should address any potential benign true
-positive (B-TP) by excluding the relevant FP by pattern.
+*False positive analysis*
+
+
+- Certain services such as PSEXECSVC may happen legitimately. The security team should address any potential benign true positive (B-TP) by excluding the relevant FP by pattern.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Delete the service or restore it to the original configuration.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Delete the service.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-any where (event.code : "4697" and
-(winlog.event_data.ServiceFileName : ("*COMSPEC*", "*\\172.0.0.1*",
-"*Admin$*", "*powershell*", "*rundll32*", "*cmd.exe*", "*PSEXESVC*",
-"*echo*", "*RemComSvc*") or winlog.event_data.ServiceFileName
-regex~ """%systemroot%\\[a-z0-9]+\.exe""")) or (event.code : "7045"
-and winlog.event_data.ImagePath : ("*COMSPEC*", "*\\172.0.0.1*",
-"*Admin$*", "*powershell*", "*rundll32*", "*cmd.exe*", "*PSEXESVC*",
-"*echo*", "*RemComSvc*"))
+[source, js]
 ----------------------------------
+any where
+  (event.code : "4697" and
+   (winlog.event_data.ServiceFileName : 
+           ("*COMSPEC*", "*\\127.0.0.1*", "*Admin$*", "*powershell*", "*rundll32*", "*cmd.exe*", "*PSEXESVC*", 
+            "*echo*", "*RemComSvc*", "*.bat*", "*.cmd*", "*certutil*", "*vssadmin*", "*certmgr*", "*bitsadmin*", 
+            "*\\Users\\*", "*\\Windows\\Temp\\*", "*\\Windows\\Tasks\\*", "*\\PerfLogs\\*", "*\\Windows\\Debug\\*",
+            "*regsvr32*", "*msbuild*") or
+   winlog.event_data.ServiceFileName regex~ """%systemroot%\\[a-z0-9]+\.exe""")) or
+
+  (event.code : "7045" and
+   winlog.event_data.ImagePath : (
+       "*COMSPEC*", "*\\127.0.0.1*", "*Admin$*", "*powershell*", "*rundll32*", "*cmd.exe*", "*PSEXESVC*",
+       "*echo*", "*RemComSvc*", "*.bat*", "*.cmd*", "*certutil*", "*vssadmin*", "*certmgr*", "*bitsadmin*",
+       "*\\Users\\*", "*\\Windows\\Temp\\*", "*\\Windows\\Tasks\\*", "*\\PerfLogs\\*", "*\\Windows\\Debug\\*",
+       "*regsvr32*", "*msbuild*"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -103,3 +128,7 @@ and winlog.event_data.ImagePath : ("*COMSPEC*", "*\\172.0.0.1*",
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-solarwinds-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-solarwinds-child-process.asciidoc
index 72915648db..b050a7d5fd 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-solarwinds-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-solarwinds-child-process.asciidoc
@@ -5,81 +5,85 @@ A suspicious SolarWinds child process was detected, which may indicate an attemp
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.fireeye.com/blog/threat-research/2020/12/evasive-attacker-leverages-solarwinds-supply-chain-compromises-with-sunburst-backdoor.html
 * https://github.com/mandiant/sunburst_countermeasures/blob/main/rules/SUNBURST/hxioc/SUNBURST%20SUSPICIOUS%20CHILD%20PROCESSES%20(METHODOLOGY).ioc
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Elastic Endgame
-
-*Version*: 102 (<<suspicious-solarwinds-child-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Trusted SolarWinds child processes, verify process details such as network connections and file writes.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name:
-("SolarWinds.BusinessLayerHost.exe",
-"SolarWinds.BusinessLayerHostx64.exe") and not process.name : (
-"APMServiceControl*.exe", "ExportToPDFCmd*.Exe",
-"SolarWinds.Credentials.Orion.WebApi*.exe",
-"SolarWinds.Orion.Topology.Calculator*.exe", "Database-
-Maint.exe", "SolarWinds.Orion.ApiPoller.Service.exe",
-"WerFault.exe", "WerMgr.exe",
-"SolarWinds.BusinessLayerHost.exe",
-"SolarWinds.BusinessLayerHostx64.exe") and not process.executable :
-("?:\\Windows\\SysWOW64\\ARP.EXE",
-"?:\\Windows\\SysWOW64\\lodctr.exe",
-"?:\\Windows\\SysWOW64\\unlodctr.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.parent.name: ("SolarWinds.BusinessLayerHost.exe", "SolarWinds.BusinessLayerHostx64.exe") and
+ not (
+    process.name : (
+        "APMServiceControl*.exe",
+        "ExportToPDFCmd*.Exe",
+        "SolarWinds.Credentials.Orion.WebApi*.exe",
+        "SolarWinds.Orion.Topology.Calculator*.exe",
+        "Database-Maint.exe",
+        "SolarWinds.Orion.ApiPoller.Service.exe",
+        "WerFault.exe",
+        "WerMgr.exe",
+        "SolarWinds.BusinessLayerHost.exe",
+        "SolarWinds.BusinessLayerHostx64.exe",
+        "SolarWinds.Topology.Calculator.exe",
+        "SolarWinds.Topology.Calculatorx64.exe",
+        "SolarWinds.APM.RealTimeProcessPoller.exe") and
+    process.code_signature.trusted == true
+ ) and
+ not process.executable : ("?:\\Windows\\SysWOW64\\ARP.EXE", "?:\\Windows\\SysWOW64\\lodctr.exe", "?:\\Windows\\SysWOW64\\unlodctr.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -91,8 +95,6 @@ Maint.exe", "SolarWinds.Orion.ApiPoller.Service.exe",
 ** Name: Native API
 ** ID: T1106
 ** Reference URL: https://attack.mitre.org/techniques/T1106/
-
-
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -101,40 +103,7 @@ Maint.exe", "SolarWinds.Orion.ApiPoller.Service.exe",
 ** Name: Supply Chain Compromise
 ** ID: T1195
 ** Reference URL: https://attack.mitre.org/techniques/T1195/
-
-[[suspicious-solarwinds-child-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name: ("SolarWinds.BusinessLayerHost.exe",
-"SolarWinds.BusinessLayerHostx64.exe") and not process.name : (
-"APMServiceControl*.exe", "ExportToPDFCmd*.Exe",
-"SolarWinds.Credentials.Orion.WebApi*.exe",
-"SolarWinds.Orion.Topology.Calculator*.exe", "Database-
-Maint.exe", "SolarWinds.Orion.ApiPoller.Service.exe",
-"WerFault.exe", "WerMgr.exe")
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Compromise Software Supply Chain
+** ID: T1195.002
+** Reference URL: https://attack.mitre.org/techniques/T1195/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-startup-shell-folder-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-startup-shell-folder-modification.asciidoc
index 51221df814..da4c2dd6a9 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-startup-shell-folder-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-startup-shell-folder-modification.asciidoc
@@ -5,93 +5,100 @@ Identifies suspicious startup shell folder modifications to change the default S
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<suspicious-startup-shell-folder-modification-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.13.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Suspicious Startup Shell Folder Modification
+*Triage and analysis*
+
+
+
+*Investigating Suspicious Startup Shell Folder Modification*
+
 
-Techniques used within malware and by adversaries often leverage the Windows registry to store malicious programs for
-persistence. Startup shell folders are often targeted as they are not as prevalent as normal Startup folder paths so this
-behavior may evade existing AV/EDR solutions. These programs may also run with higher privileges which can be ideal for
-an attacker.
+Techniques used within malware and by adversaries often leverage the Windows registry to store malicious programs for persistence. Startup shell folders are often targeted as they are not as prevalent as normal Startup folder paths so this behavior may evade existing AV/EDR solutions. These programs may also run with higher privileges which can be ideal for an attacker.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Review the source process and related file tied to the Windows Registry entry.
-- Validate the activity is not related to planned patches, updates, network administrator activity or legitimate software
-installations.
+- Validate if the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the file using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
-- There is a high possibility of benign legitimate programs being added to shell folders. This activity could be based
-on new software installations, patches, or other network administrator activity. Before undertaking further investigation,
-it should be verified that this activity is not benign.
+- There is a high possibility of benign legitimate programs being added to shell folders. This activity could be based on new software installations, patches, or other network administrator activity. Before undertaking further investigation, it should be verified that this activity is not benign.
+
+
+*Related rules*
 
-### Related rules
 
 - Startup or Run Key Registry Modification - 97fc44d3-8dae-4019-ae83-298c3015600f
 - Persistent Scripts in the Startup Directory - f7c4dc5a-a58d-491d-9f14-9b66507121c0
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -101,37 +108,38 @@ it should be verified that this activity is not benign.
   - Block the malicious web pages.
   - Remove emails from the sender from mailboxes.
   - Consider improvements to the security awareness program.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.path : (
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User
-Shell Folders\\Common Startup",
-"HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell
-Folders\\Common Startup", "HKEY_USERS\\*\\Software\\Microsoft\\Wi
-ndows\\CurrentVersion\\Explorer\\User Shell Folders\\Startup", "H
-KEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\
-Shell Folders\\Startup" ) and registry.data.strings != null and
-/* Normal Startup Folder Paths */ not registry.data.strings : (
-"C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\Startup",
-"%ProgramData%\\Microsoft\\Windows\\Start Menu\\Programs\\Startup",
-"%USERPROFILE%\\AppData\\Roaming\\Microsoft\\Windows\\Start
-Menu\\Programs\\Startup",
-"C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start
-Menu\\Programs\\Startup" )
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and
+ registry.path : (
+     "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User Shell Folders\\Common Startup",
+     "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell Folders\\Common Startup",
+     "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User Shell Folders\\Startup",
+     "HKEY_USERS\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell Folders\\Startup",
+     "HKU\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User Shell Folders\\Startup",
+     "HKU\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell Folders\\Startup",
+     "\\REGISTRY\\MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User Shell Folders\\Common Startup",
+     "\\REGISTRY\\MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell Folders\\Common Startup",
+     "\\REGISTRY\\USER\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User Shell Folders\\Startup",
+     "\\REGISTRY\\USER\\*\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell Folders\\Startup"
+     ) and
+  registry.data.strings != null and
+  /* Normal Startup Folder Paths */
+  not registry.data.strings : (
+           "C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\Startup",
+           "%ProgramData%\\Microsoft\\Windows\\Start Menu\\Programs\\Startup",
+           "%USERPROFILE%\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\Startup",
+           "C:\\Users\\*\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\Startup"
+           )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -143,28 +151,15 @@ Menu\\Programs\\Startup" )
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-[[suspicious-startup-shell-folder-modification-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (8.1.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Registry Run Keys / Startup Folder
+** ID: T1547.001
+** Reference URL: https://attack.mitre.org/techniques/T1547/001/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-symbolic-link-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-symbolic-link-created.asciidoc
new file mode 100644
index 0000000000..f377b5f267
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-symbolic-link-created.asciidoc
@@ -0,0 +1,129 @@
+[[suspicious-symbolic-link-created]]
+=== Suspicious Symbolic Link Created
+
+Identifies the creation of a symbolic link to a suspicious file or location. A symbolic link is a reference to a file or directory that acts as a pointer or shortcut, allowing users to access the target file or directory from a different location in the file system. An attacker can potentially leverage symbolic links for privilege escalation by tricking a privileged process into following the symbolic link to a sensitive file, giving the attacker access to data or capabilities they would not normally have.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Credential Access
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
+process.name == "ln" and process.args in ("-s", "-sf") and 
+  (
+    /* suspicious files */
+    (process.args in ("/etc/shadow", "/etc/shadow-", "/etc/shadow~", "/etc/gshadow", "/etc/gshadow-") or 
+    (process.working_directory == "/etc" and process.args in ("shadow", "shadow-", "shadow~", "gshadow", "gshadow-"))) or 
+    
+    /* suspicious bins */
+    (process.args in ("/bin/bash", "/bin/dash", "/bin/sh", "/bin/tcsh", "/bin/csh", "/bin/zsh", "/bin/ksh", "/bin/fish") or 
+    (process.working_directory == "/bin" and process.args : ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish"))) or 
+    (process.args in ("/usr/bin/bash", "/usr/bin/dash", "/usr/bin/sh", "/usr/bin/tcsh", "/usr/bin/csh", "/usr/bin/zsh", "/usr/bin/ksh", "/usr/bin/fish") or 
+    (process.working_directory == "/usr/bin" and process.args in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish"))) or
+    
+    /* suspicious locations */
+    (process.args : ("/etc/cron.d/*", "/etc/cron.daily/*", "/etc/cron.hourly/*", "/etc/cron.weekly/*", "/etc/cron.monthly/*")) or
+    (process.args : ("/home/*/.ssh/*", "/root/.ssh/*","/etc/sudoers.d/*", "/dev/shm/*"))
+  ) and 
+  process.parent.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") and 
+  not user.Ext.real.id == "0" and not group.Ext.real.id == "0"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Sub-technique:
+** Name: /etc/passwd and /etc/shadow
+** ID: T1003.008
+** Reference URL: https://attack.mitre.org/techniques/T1003/008/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-sysctl-file-event.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-sysctl-file-event.asciidoc
new file mode 100644
index 0000000000..f4d8cc0858
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-sysctl-file-event.asciidoc
@@ -0,0 +1,92 @@
+[[suspicious-sysctl-file-event]]
+=== Suspicious Sysctl File Event
+
+Monitors file events on sysctl configuration files (e.g., /etc/sysctl.conf, /etc/sysctl.d/*.conf) to identify potential unauthorized access or manipulation of system-level configuration settings. Attackers may tamper with the sysctl configuration files to modify kernel parameters, potentially compromising system stability, performance, or security.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Data Source: Auditd Manager
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+
+*Version*: 107
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires the use of the `auditd_manager` integration. `Auditd_manager` is a tool designed to simplify and enhance the management of the audit subsystem in Linux systems. It provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system. The following steps should be executed in order to install and deploy `auditd_manager` on a Linux system.
+
+```
+Kibana -->
+Management -->
+Integrations -->
+Auditd Manager -->
+Add Auditd Manager
+```
+
+`Auditd_manager` subscribes to the kernel and receives events as they occur without any additional configuration. However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+
+For this detection rule to trigger, the following additional audit rules are required to be added to the integration:
+
+```
+-w /etc/sysctl.conf -p wa -k sysctl
+-w /etc/sysctl.d -p wa -k sysctl
+```
+
+Add the newly installed `auditd manager` to an agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.category:file and event.action:("opened-file" or "read-file" or "wrote-to-file") and
+file.path : ("/etc/sysctl.conf" or "/etc/sysctl.d" or /etc/sysctl.d/*) and not process.name:(
+  dpkg or dockerd or unattended-upg or systemd-sysctl or python* or auditbeat or dpkg or grep or pool*
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-system-commands-executed-by-previously-unknown-executable.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-system-commands-executed-by-previously-unknown-executable.asciidoc
new file mode 100644
index 0000000000..cf74d58061
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-system-commands-executed-by-previously-unknown-executable.asciidoc
@@ -0,0 +1,110 @@
+[[suspicious-system-commands-executed-by-previously-unknown-executable]]
+=== Suspicious System Commands Executed by Previously Unknown Executable
+
+This rule monitors for the execution of several commonly used system commands executed by a previously unknown executable located in commonly abused directories. An alert from this rule can indicate the presence of potentially malicious activity, such as the execution of unauthorized or suspicious processes attempting to run malicious code. Detecting and investigating such behavior can help identify and mitigate potential security threats, protecting the system and its data from potential compromise.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 105
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.category:process and event.action:(exec or exec_event or fork or fork_event) and 
+process.executable:(
+  /bin/* or /usr/bin/* or /usr/share/* or /tmp/* or /var/tmp/* or /dev/shm/* or
+  /etc/init.d/* or /etc/rc*.d/* or /etc/crontab or /etc/cron.*/* or /etc/update-motd.d/* or 
+  /usr/lib/update-notifier/* or /home/*/.* or /boot/* or /srv/* or /run/*) 
+  and process.args:(whoami or id or hostname or uptime or top or ifconfig or netstat or route or ps or pwd or ls) and 
+  not process.name:(sudo or which or whoami or id or hostname or uptime or top or netstat or ps or pwd or ls or apt or 
+  dpkg or yum or rpm or dnf or dockerd or docker or snapd or snap) and
+  not process.parent.executable:(/bin/* or /usr/bin/* or /run/k3s/* or /etc/network/* or /opt/Elastic/*)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-termination-of-esxi-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-termination-of-esxi-process.asciidoc
new file mode 100644
index 0000000000..c7428169e9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-termination-of-esxi-process.asciidoc
@@ -0,0 +1,101 @@
+[[suspicious-termination-of-esxi-process]]
+=== Suspicious Termination of ESXI Process
+
+Identifies instances where VMware processes, such as "vmware-vmx" or "vmx," are terminated on a Linux system by a "kill" command. The rule monitors for the "end" event type, which signifies the termination of a process. The presence of a "kill" command as the parent process for terminating VMware processes may indicate that a threat actor is attempting to interfere with the virtualized environment on the targeted system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.bleepingcomputer.com/news/security/massive-esxiargs-ransomware-attack-targets-vmware-esxi-servers-worldwide/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Impact
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "end" and process.name in ("vmware-vmx", "vmx")
+and process.parent.name == "kill"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Impact
+** ID: TA0040
+** Reference URL: https://attack.mitre.org/tactics/TA0040/
+* Technique:
+** Name: Service Stop
+** ID: T1489
+** Reference URL: https://attack.mitre.org/techniques/T1489/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-troubleshooting-pack-cabinet-execution.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-troubleshooting-pack-cabinet-execution.asciidoc
new file mode 100644
index 0000000000..08038657ab
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-troubleshooting-pack-cabinet-execution.asciidoc
@@ -0,0 +1,79 @@
+[[suspicious-troubleshooting-pack-cabinet-execution]]
+=== Suspicious Troubleshooting Pack Cabinet Execution
+
+Identifies the execution of the Microsoft Diagnostic Wizard to open a diagcab file from a suspicious path and with an unusual parent process. This may indicate an attempt to execute malicious Troubleshooting Pack Cabinet files.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* logs-system.security*
+* winlogbeat-*
+* logs-windows.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://irsl.medium.com/the-trouble-with-microsofts-troubleshooters-6e32fc80b8bd
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.action == "start" and
+  (process.name : "msdt.exe" or ?process.pe.original_file_name == "msdt.exe") and process.args : "/cab" and
+  process.parent.name : (
+    "firefox.exe", "chrome.exe", "msedge.exe", "explorer.exe", "brave.exe", "whale.exe", "browser.exe",
+    "dragon.exe", "vivaldi.exe", "opera.exe", "iexplore", "firefox.exe", "waterfox.exe", "iexplore.exe",
+    "winrar.exe", "winrar.exe", "7zFM.exe", "outlook.exe", "winword.exe", "excel.exe"
+  ) and
+  process.args : (
+    "?:\\Users\\*",
+    "\\\\*",
+    "http*",
+    "ftp://*"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-utility-launched-via-proxychains.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-utility-launched-via-proxychains.asciidoc
new file mode 100644
index 0000000000..fab74fcfeb
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-utility-launched-via-proxychains.asciidoc
@@ -0,0 +1,187 @@
+[[suspicious-utility-launched-via-proxychains]]
+=== Suspicious Utility Launched via ProxyChains
+
+This rule monitors for the execution of suspicious linux tools through ProxyChains. ProxyChains is a command-line tool that enables the routing of network connections through intermediary proxies, enhancing anonymity and enabling access to restricted resources. Attackers can exploit the ProxyChains utility to hide their true source IP address, evade detection, and perform malicious activities through a chain of proxy servers, potentially masking their identity and intentions.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.bitsadmin.com/living-off-the-foreign-land-windows-as-offensive-platform
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Command and Control
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Suspicious Utility Launched via ProxyChains*
+
+
+Attackers can leverage `proxychains` to obfuscate their origin and bypass network defenses by routing their malicious traffic through multiple intermediary servers.
+
+This rule looks for a list of suspicious processes spawned through `proxychains` by analyzing process command line arguments. 
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+> This investigation guide uses https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html[placeholder fields] to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
+
+
+*Possible investigation steps*
+
+
+- Identify any signs of suspicious network activity or anomalies that may indicate network obfuscation. This could include unexpected traffic patterns or unusual network behavior.
+  - Investigate listening ports and open sockets to look for potential protocol tunneling, reverse shells, or data exfiltration.
+    - !{osquery{"label":"Osquery - Retrieve Listening Ports","query":"SELECT pid, address, port, socket, protocol, path FROM listening_ports"}}
+    - !{osquery{"label":"Osquery - Retrieve Open Sockets","query":"SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"}}
+- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
+  - !{osquery{"label":"Osquery - Retrieve Information for a Specific User","query":"SELECT * FROM users WHERE username = {{user.name}}"}}
+- Investigate whether the user is currently logged in and active.
+  - !{osquery{"label":"Osquery - Investigate the Account Authentication Status","query":"SELECT * FROM logged_in_users WHERE user = {{user.name}}"}}
+- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
+  - !{osquery{"label":"Osquery - Retrieve Running Processes by User","query":"SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"}}
+  - !{osquery{"label":"Osquery - Retrieve Process Info","query":"SELECT name, cmdline, parent, path, uid FROM processes"}}
+- Investigate other alerts associated with the user/host during the past 48 hours.
+  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
+    - Use a private sandboxed malware analysis system to perform analysis.
+      - Observe and collect information about the following activities:
+        - Attempts to contact external domains and addresses.
+          - Check if the domain is newly registered or unexpected.
+          - Check the reputation of the domain or IP address.
+        - File access, modification, and creation activities.
+
+
+*Related rules*
+
+
+- ProxyChains Activity - 4b868f1f-15ff-4ba3-8c11-d5a7a6356d37
+- Potential Protocol Tunneling via Chisel Client - 3f12325a-4cc6-410b-8d4c-9fbbeb744cfd
+- Potential Protocol Tunneling via Chisel Server - ac8805f6-1e08-406c-962e-3937057fa86f
+- Potential Linux Tunneling and/or Port Forwarding - 6ee947e9-de7e-4281-a55d-09289bdf947e
+- Potential Protocol Tunneling via EarthWorm - 9f1c4ca3-44b5-481d-ba42-32dc215a2769
+
+
+*False positive analysis*
+
+
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- If this activity is related to a system administrator or developer who uses this utility for benign purposes, consider adding exceptions for specific user accounts or hosts. 
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors, such as reverse shells, reverse proxies, or droppers, that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and process.name == "proxychains" and process.args : (
+  "ssh", "sshd", "sshuttle", "socat", "iodine", "iodined", "dnscat", "hans", "hans-ubuntu", "ptunnel-ng",
+  "ssf", "3proxy", "ngrok", "gost", "pivotnacci", "chisel*", "nmap", "ping", "python*", "php*", "perl", "ruby",
+  "lua*", "openssl", "nc", "netcat", "ncat", "telnet", "awk", "java", "telnet", "ftp", "curl", "wget"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Protocol Tunneling
+** ID: T1572
+** Reference URL: https://attack.mitre.org/techniques/T1572/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-web-browser-sensitive-file-access.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-web-browser-sensitive-file-access.asciidoc
new file mode 100644
index 0000000000..ebd52984fa
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-web-browser-sensitive-file-access.asciidoc
@@ -0,0 +1,115 @@
+[[suspicious-web-browser-sensitive-file-access]]
+=== Suspicious Web Browser Sensitive File Access
+
+Identifies the access or file open of web browser sensitive files by an untrusted/unsigned process or osascript. Adversaries may acquire credentials from web browsers by reading files specific to the target browser.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.file.*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://securelist.com/calisto-trojan-for-macos/86543/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 207
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where event.action == "open" and process.executable != null and 
+ file.name : ("cookies.sqlite", 
+              "key?.db", 
+              "logins.json", 
+              "Cookies", 
+              "Cookies.binarycookies", 
+              "Login Data") and 
+ ((process.code_signature.trusted == false or process.code_signature.exists == false) or process.name : "osascript") and 
+ not process.code_signature.signing_id : "org.mozilla.firefox" and
+ not process.Ext.effective_parent.executable : "/Library/Elastic/Endpoint/elastic-endpoint.app/Contents/MacOS/elastic-endpoint"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: Steal Web Session Cookie
+** ID: T1539
+** Reference URL: https://attack.mitre.org/techniques/T1539/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Sub-technique:
+** Name: Credentials from Web Browsers
+** ID: T1555.003
+** Reference URL: https://attack.mitre.org/techniques/T1555/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-werfault-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-werfault-child-process.asciidoc
index 3c85da1734..fab2e0ddc2 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-werfault-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-werfault-child-process.asciidoc
@@ -1,14 +1,14 @@
 [[suspicious-werfault-child-process]]
 === Suspicious WerFault Child Process
 
-A suspicious WerFault child process was detected, which may indicate an attempt to run unnoticed. Verify process details such as command line, network connections, file writes and parent process details as well.
+A suspicious WerFault child process was detected, which may indicate an attempt to run via the SilentProcessExit registry key manipulation. Verify process details such as command line, network connections and file writes.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
 
@@ -16,66 +16,68 @@ A suspicious WerFault child process was detected, which may indicate an attempt
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.hexacorn.com/blog/2019/09/19/silentprocessexit-quick-look-under-the-hood/
+* https://www.hexacorn.com/blog/2019/09/20/werfault-command-line-switches-v0-1/
 * https://github.com/sbousseaden/EVTX-ATTACK-SAMPLES/blob/master/Persistence/persistence_SilentProcessExit_ImageHijack_sysmon_13_1.evtx
-* https://web.archive.org/web/20230530011556/https://blog.menasec.net/2021/01/
+* http://web.archive.org/web/20230530011556/https://blog.menasec.net/2021/01/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
-
-*Version*: 102 (<<suspicious-werfault-child-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Persistence
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Custom Windows error reporting debugger or applications restarted by WerFault after a crash.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"WerFault.exe" and not process.name : ("cofire.exe",
-"psr.exe", "VsJITDebugger.exe",
-"TTTracer.exe", "rundll32.exe",
-"LogiOptionsMgr.exe") and not process.args : ("/LOADSAVEDWINDOWS",
-"/restore", "RestartByRestartManager*",
-"--restarted", "createdump",
-"dontsend", "/watson")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
 
-==== Threat mapping
+  process.parent.name : "WerFault.exe" and 
+  
+  /* args -s and -t used to execute a process via SilentProcessExit mechanism */
+  (process.parent.args : "-s" and process.parent.args : "-t" and process.parent.args : "-c") and 
+  
+  not process.executable : ("?:\\Windows\\SysWOW64\\Initcrypt.exe", "?:\\Program Files (x86)\\Heimdal\\Heimdal.Guard.exe")
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -87,48 +89,27 @@ process where event.type == "start" and process.parent.name :
 ** Name: Masquerading
 ** ID: T1036
 ** Reference URL: https://attack.mitre.org/techniques/T1036/
-
-[[suspicious-werfault-child-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "WerFault.exe" and not process.name :
-("cofire.exe", "psr.exe",
-"VsJITDebugger.exe", "TTTracer.exe",
-"rundll32.exe", "LogiOptionsMgr.exe") and not
-process.args : ("/LOADSAVEDWINDOWS", "/restore",
-"RestartByRestartManager*", "--restarted",
-"createdump", "dontsend",
-"/watson")
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:WerFault.exe and not process.name:(cofire.exe or
-psr.exe or VsJITDebugger.exe or TTTracer.exe or rundll32.exe)
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: Image File Execution Options Injection
+** ID: T1546.012
+** Reference URL: https://attack.mitre.org/techniques/T1546/012/
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: Image File Execution Options Injection
+** ID: T1546.012
+** Reference URL: https://attack.mitre.org/techniques/T1546/012/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-which-enumeration.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-which-enumeration.asciidoc
new file mode 100644
index 0000000000..ca489c1a49
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-which-enumeration.asciidoc
@@ -0,0 +1,68 @@
+[[suspicious-which-enumeration]]
+=== Suspicious which Enumeration
+
+This rule monitors for the usage of the which command with an unusual amount of process arguments. Attackers may leverage the which command to enumerate the system for useful installed utilities that may be used after compromising a system to escalate privileges or move latteraly across the network.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 5
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and 
+process.name == "which" and process.args_count >= 10 and not process.parent.name == "jem" and 
+not process.args == "--tty-only"
+
+/* potential tuning if rule would turn out to be noisy
+and process.args in ("nmap", "nc", "ncat", "netcat", nc.traditional", "gcc", "g++", "socat") and 
+process.parent.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")
+*/ 
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-host.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-host.asciidoc
new file mode 100644
index 0000000000..0db42c7da2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-host.asciidoc
@@ -0,0 +1,124 @@
+[[suspicious-windows-process-cluster-spawned-by-a-host]]
+=== Suspicious Windows Process Cluster Spawned by a Host
+
+A machine learning job combination has detected a set of one or more suspicious Windows processes with unusually high scores for malicious probability. These process(es) have been classified as malicious in several ways. The process(es) were predicted to be malicious by the ProblemChild supervised ML model. If the anomaly contains a cluster of suspicious processes, each process has the same host name, and the aggregate score of the event cluster was calculated to be unusually high by an unsupervised ML model. Such a cluster often contains suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/problemchild
+* https://www.elastic.co/security-labs/detecting-living-off-the-land-attacks-with-new-elastic-integration
+
+*Tags*: 
+
+* Use Case: Living off the Land Attack Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Defense Evasion
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Living off the Land (LotL) Attack Detection integration assets to be installed, as well as Windows process events collected by integrations such as Elastic Defend or Winlogbeat.  
+
+
+*LotL Attack Detection Setup*
+
+The LotL Attack Detection integration detects living-off-the-land activity in Windows process events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for LotL Attack Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration or Winlogbeat(https://www.elastic.co/guide/en/beats/winlogbeat/current/_winlogbeat_overview.html).
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To set up and run Winlogbeat, follow https://www.elastic.co/guide/en/beats/winlogbeat/current/winlogbeat-installation-configuration.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the LotL Attack Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Living off the Land Attack Detection and select the integration to see more details about it.
+- Under Settings, click Install Living off the Land Attack Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+**Before you can enable this rule**, you'll need to enrich Windows process events with predictions from the Supervised LotL Attack Detection model. This is done via the ingest pipeline named `<package_version>-problem_child_ingest_pipeline` installed with the LotL Attack Detection package.
+- If using an Elastic Beat such as Winlogbeat, add the LotL ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `winlogbeat.yml`.
+- If adding the LotL ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor]. For example, you can check if your winlogbeat or Elastic Defend (the https://docs.elastic.co/en/integrations/endpoint#logs[default index pattern] being `logs-endpoint*`) already has an ingest pipeline by navigating to `Data > Index Management`, finding the index (sometimes you need to toggle "Include hidden indices"), and checking the index's settings for a default or final https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#set-default-pipeline[pipeline].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the LotL ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "problemchild": {
+      "properties": {
+        "prediction": {
+          "type": "long"
+        },
+        "prediction_probability": {
+          "type": "float"
+        }
+      }
+    },
+    "blocklist_label": {
+      "type": "long"
+    }
+  }
+}
+```
+
+
+*Anomaly Detection Setup*
+
+**Before you can enable this rule**, you'll need to enable the corresponding Anomaly Detection job. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your enriched Windows process events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events, or `winlogbeat-*` if you used Winlogbeat.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/problemchild/kibana/ml_module/problemchild-ml.json[this] configuration file, you will see a card for "Living off the Land Attack Detection" under "Use preconfigured jobs". Warning: if the ingest pipeline hasn't run for some reason, such as no eligible data in winlogbeat has come in yet, _you won't be able to see this card yet_. If that is the case, try troubleshooting the ingest pipeline, and if any ProblemChild predictions have been populated yet.
+- Keep the default settings and click "Create jobs" to start the anomaly detection job and datafeed.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-parent-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-parent-process.asciidoc
new file mode 100644
index 0000000000..13bbf33559
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-parent-process.asciidoc
@@ -0,0 +1,126 @@
+[[suspicious-windows-process-cluster-spawned-by-a-parent-process]]
+=== Suspicious Windows Process Cluster Spawned by a Parent Process
+
+A machine learning job combination has detected a set of one or more suspicious Windows processes with unusually high scores for malicious probability. These process(es) have been classified as malicious in several ways. The process(es) were predicted to be malicious by the ProblemChild supervised ML model. If the anomaly contains a cluster of suspicious processes, each process has the same parent process name, and the aggregate score of the event cluster was calculated to be unusually high by an unsupervised ML model. Such a cluster often contains suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/problemchild
+* https://www.elastic.co/security-labs/detecting-living-off-the-land-attacks-with-new-elastic-integration
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Living off the Land Attack Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Defense Evasion
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Living off the Land (LotL) Attack Detection integration assets to be installed, as well as Windows process events collected by integrations such as Elastic Defend or Winlogbeat.  
+
+
+*LotL Attack Detection Setup*
+
+The LotL Attack Detection integration detects living-off-the-land activity in Windows process events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for LotL Attack Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration or Winlogbeat(https://www.elastic.co/guide/en/beats/winlogbeat/current/_winlogbeat_overview.html).
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To set up and run Winlogbeat, follow https://www.elastic.co/guide/en/beats/winlogbeat/current/winlogbeat-installation-configuration.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the LotL Attack Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Living off the Land Attack Detection and select the integration to see more details about it.
+- Under Settings, click Install Living off the Land Attack Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+**Before you can enable this rule**, you'll need to enrich Windows process events with predictions from the Supervised LotL Attack Detection model. This is done via the ingest pipeline named `<package_version>-problem_child_ingest_pipeline` installed with the LotL Attack Detection package.
+- If using an Elastic Beat such as Winlogbeat, add the LotL ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `winlogbeat.yml`.
+- If adding the LotL ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor]. For example, you can check if your winlogbeat or Elastic Defend (the https://docs.elastic.co/en/integrations/endpoint#logs[default index pattern] being `logs-endpoint*`) already has an ingest pipeline by navigating to `Data > Index Management`, finding the index (sometimes you need to toggle "Include hidden indices"), and checking the index's settings for a default or final https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#set-default-pipeline[pipeline].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the LotL ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "problemchild": {
+      "properties": {
+        "prediction": {
+          "type": "long"
+        },
+        "prediction_probability": {
+          "type": "float"
+        }
+      }
+    },
+    "blocklist_label": {
+      "type": "long"
+    }
+  }
+}
+```
+
+
+*Anomaly Detection Setup*
+
+**Before you can enable this rule**, you'll need to enable the corresponding Anomaly Detection job. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your enriched Windows process events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events, or `winlogbeat-*` if you used Winlogbeat.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/problemchild/kibana/ml_module/problemchild-ml.json[this] configuration file, you will see a card for "Living off the Land Attack Detection" under "Use preconfigured jobs". Warning: if the ingest pipeline hasn't run for some reason, such as no eligible data in winlogbeat has come in yet, _you won't be able to see this card yet_. If that is the case, try troubleshooting the ingest pipeline, and if any ProblemChild predictions have been populated yet.
+- Keep the default settings and click "Create jobs" to start the anomaly detection job and datafeed.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-user.asciidoc
new file mode 100644
index 0000000000..1bf58264d6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-windows-process-cluster-spawned-by-a-user.asciidoc
@@ -0,0 +1,126 @@
+[[suspicious-windows-process-cluster-spawned-by-a-user]]
+=== Suspicious Windows Process Cluster Spawned by a User
+
+A machine learning job combination has detected a set of one or more suspicious Windows processes with unusually high scores for malicious probability. These process(es) have been classified as malicious in several ways. The process(es) were predicted to be malicious by the ProblemChild supervised ML model. If the anomaly contains a cluster of suspicious processes, each process has the same user name, and the aggregate score of the event cluster was calculated to be unusually high by an unsupervised ML model. Such a cluster often contains suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/problemchild
+* https://www.elastic.co/security-labs/detecting-living-off-the-land-attacks-with-new-elastic-integration
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Living off the Land Attack Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Defense Evasion
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Living off the Land (LotL) Attack Detection integration assets to be installed, as well as Windows process events collected by integrations such as Elastic Defend or Winlogbeat.  
+
+
+*LotL Attack Detection Setup*
+
+The LotL Attack Detection integration detects living-off-the-land activity in Windows process events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for LotL Attack Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration or Winlogbeat(https://www.elastic.co/guide/en/beats/winlogbeat/current/_winlogbeat_overview.html).
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To set up and run Winlogbeat, follow https://www.elastic.co/guide/en/beats/winlogbeat/current/winlogbeat-installation-configuration.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the LotL Attack Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Living off the Land Attack Detection and select the integration to see more details about it.
+- Under Settings, click Install Living off the Land Attack Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+**Before you can enable this rule**, you'll need to enrich Windows process events with predictions from the Supervised LotL Attack Detection model. This is done via the ingest pipeline named `<package_version>-problem_child_ingest_pipeline` installed with the LotL Attack Detection package.
+- If using an Elastic Beat such as Winlogbeat, add the LotL ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `winlogbeat.yml`.
+- If adding the LotL ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor]. For example, you can check if your winlogbeat or Elastic Defend (the https://docs.elastic.co/en/integrations/endpoint#logs[default index pattern] being `logs-endpoint*`) already has an ingest pipeline by navigating to `Data > Index Management`, finding the index (sometimes you need to toggle "Include hidden indices"), and checking the index's settings for a default or final https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#set-default-pipeline[pipeline].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the LotL ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "problemchild": {
+      "properties": {
+        "prediction": {
+          "type": "long"
+        },
+        "prediction_probability": {
+          "type": "float"
+        }
+      }
+    },
+    "blocklist_label": {
+      "type": "long"
+    }
+  }
+}
+```
+
+
+*Anomaly Detection Setup*
+
+**Before you can enable this rule**, you'll need to enable the corresponding Anomaly Detection job. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your enriched Windows process events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events, or `winlogbeat-*` if you used Winlogbeat.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/problemchild/kibana/ml_module/problemchild-ml.json[this] configuration file, you will see a card for "Living off the Land Attack Detection" under "Use preconfigured jobs". Warning: if the ingest pipeline hasn't run for some reason, such as no eligible data in winlogbeat has come in yet, _you won't be able to see this card yet_. If that is the case, try troubleshooting the ingest pipeline, and if any ProblemChild predictions have been populated yet.
+- Keep the default settings and click "Create jobs" to start the anomaly detection job and datafeed.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-wmi-event-subscription-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-wmi-event-subscription-created.asciidoc
new file mode 100644
index 0000000000..fe42a700df
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-wmi-event-subscription-created.asciidoc
@@ -0,0 +1,68 @@
+[[suspicious-wmi-event-subscription-created]]
+=== Suspicious WMI Event Subscription Created
+
+Detects the creation of a WMI Event Subscription. Attackers can abuse this mechanism for persistence or to elevate to SYSTEM privileges.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-windows.sysmon_operational-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.blackhat.com/docs/us-15/materials/us-15-Graeber-Abusing-Windows-Management-Instrumentation-WMI-To-Build-A-Persistent%20Asynchronous-And-Fileless-Backdoor-wp.pdf
+* https://medium.com/threatpunter/detecting-removing-wmi-persistence-60ccbb7dff96
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Sysmon
+
+*Version*: 106
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+any where event.dataset == "windows.sysmon_operational" and event.code == "21" and
+    winlog.event_data.Operation : "Created" and winlog.event_data.Consumer : ("*subscription:CommandLineEventConsumer*", "*subscription:ActiveScriptEventConsumer*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: Windows Management Instrumentation Event Subscription
+** ID: T1546.003
+** Reference URL: https://attack.mitre.org/techniques/T1546/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-wmi-image-load-from-ms-office.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-wmi-image-load-from-ms-office.asciidoc
index 9d7f1f900c..33343fce67 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-wmi-image-load-from-ms-office.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-wmi-image-load-from-ms-office.asciidoc
@@ -5,68 +5,71 @@ Identifies a suspicious image load (wmiutils.dll) from Microsoft Office processe
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.library-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://medium.com/threatpunter/detecting-adversary-tradecraft-with-image-load-event-logging-and-eql-8de93338c16
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Elastic Endgame
-
-*Version*: 101 (<<suspicious-wmi-image-load-from-ms-office-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-any where (event.category : ("library", "driver") or (event.category
-== "process" and event.action : "Image loaded*")) and process.name :
-("WINWORD.EXE", "EXCEL.EXE", "POWERPNT.EXE", "MSPUB.EXE",
-"MSACCESS.EXE") and (dll.name : "wmiutils.dll" or file.name :
-"wmiutils.dll")
+[source, js]
 ----------------------------------
+any where host.os.type == "windows" and
+ (event.category : ("library", "driver") or (event.category == "process" and event.action : "Image loaded*")) and
+  process.name : ("WINWORD.EXE", "EXCEL.EXE", "POWERPNT.EXE", "MSPUB.EXE", "MSACCESS.EXE") and
+  (?dll.name : "wmiutils.dll" or file.name : "wmiutils.dll")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,53 +81,3 @@ any where (event.category : ("library", "driver") or (event.category
 ** Name: Windows Management Instrumentation
 ** ID: T1047
 ** Reference URL: https://attack.mitre.org/techniques/T1047/
-
-[[suspicious-wmi-image-load-from-ms-office-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-any where (event.category == "library" or (event.category ==
-"process" and event.action : "Image loaded*")) and process.name :
-("WINWORD.EXE", "EXCEL.EXE", "POWERPNT.EXE", "MSPUB.EXE",
-"MSACCESS.EXE") and (dll.name : "wmiutils.dll" or file.name :
-"wmiutils.dll")
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-library where process.name : ("WINWORD.EXE", "EXCEL.EXE",
-"POWERPNT.EXE", "MSPUB.EXE", "MSACCESS.EXE") and event.action :
-"load" and event.category : "library" and dll.name :
-"wmiutils.dll"
-----------------------------------
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.15.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-library where process.name in ("WINWORD.EXE", "EXCEL.EXE",
-"POWERPNT.EXE", "MSPUB.EXE", "MSACCESS.EXE") and event.action ==
-"load" and event.category == "library" and file.name ==
-"wmiutils.dll"
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-wmic-xsl-script-execution.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-wmic-xsl-script-execution.asciidoc
index 8c5c245286..b93afda91d 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-wmic-xsl-script-execution.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-wmic-xsl-script-execution.asciidoc
@@ -5,56 +5,58 @@ Identifies WMIC allowlist bypass techniques by alerting on suspicious execution
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.library-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 101 (<<suspicious-wmic-xsl-script-execution-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id with maxspan = 2m [process where
-event.type == "start" and (process.name : "WMIC.exe" or
-process.pe.original_file_name : "wmic.exe") and process.args :
-("format*:*", "/format*:*", "*-format*:*") and not
-process.command_line : "* /format:table *"] [any where (event.category
-== "library" or (event.category == "process" and event.action : "Image
-loaded*")) and (dll.name : ("jscript.dll", "vbscript.dll") or
-file.name : ("jscript.dll", "vbscript.dll"))]
+[source, js]
 ----------------------------------
+sequence by process.entity_id with maxspan = 2m
+[process where host.os.type == "windows" and event.type == "start" and
+   (process.name : "WMIC.exe" or process.pe.original_file_name : "wmic.exe") and
+   process.args : ("format*:*", "/format*:*", "*-format*:*") and
+   not process.command_line : ("* /format:table *", "* /format:table")]
+[any where host.os.type == "windows" and (event.category == "library" or (event.category == "process" and event.action : "Image loaded*")) and
+ (?dll.name : ("jscript.dll", "vbscript.dll") or file.name : ("jscript.dll", "vbscript.dll"))]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,52 +68,11 @@ file.name : ("jscript.dll", "vbscript.dll"))]
 ** Name: XSL Script Processing
 ** ID: T1220
 ** Reference URL: https://attack.mitre.org/techniques/T1220/
-
-[[suspicious-wmic-xsl-script-execution-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan = 2m [process where
-event.type in ("start", "process_started") and (process.name :
-"WMIC.exe" or process.pe.original_file_name : "wmic.exe") and
-process.args : ("format*:*", "/format*:*", "*-format*:*") and not
-process.command_line : "* /format:table *"] [any where (event.category
-== "library" or (event.category == "process" and event.action : "Image
-loaded*")) and (dll.name : ("jscript.dll", "vbscript.dll") or
-file.name : ("jscript.dll", "vbscript.dll"))]
-----------------------------------
-
-Version 5 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan = 2m [process where
-event.type in ("start", "process_started") and (process.name :
-"WMIC.exe" or process.pe.original_file_name : "wmic.exe") and
-process.args : ("format*:*", "/format*:*", "*-format*:*") and not
-process.command_line : "* /format:table *"] [library where event.type
-== "start" and dll.name : ("jscript.dll", "vbscript.dll")]
-----------------------------------
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan=2m [process where
-event.type in ("start", "process_started") and (process.name :
-"WMIC.exe" or process.pe.original_file_name == "wmic.exe") and
-wildcard(process.args, "format*:*", "/format*:*", "*-format*:*") and
-not wildcard(process.command_line, "* /format:table *")] [library
-where event.type == "start" and file.name in ("jscript.dll",
-"vbscript.dll")]
-----------------------------------
-
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Windows Management Instrumentation
+** ID: T1047
+** Reference URL: https://attack.mitre.org/techniques/T1047/
diff --git a/docs/detections/prebuilt-rules/rule-details/suspicious-zoom-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/suspicious-zoom-child-process.asciidoc
index 32f5f65049..a845f6af75 100644
--- a/docs/detections/prebuilt-rules/rule-details/suspicious-zoom-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/suspicious-zoom-child-process.asciidoc
@@ -5,133 +5,140 @@ A suspicious Zoom child process was detected, which may indicate an attempt to r
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<suspicious-zoom-child-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
 
 
-==== Rule query
 
+*Investigating Suspicious Zoom Child Process*
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"Zoom.exe" and process.name : ("cmd.exe", "powershell.exe",
-"pwsh.exe", "powershell_ise.exe")
-----------------------------------
 
-==== Threat mapping
+By examining the specific traits of Windows binaries -- such as process trees, command lines, network connections, registry modifications, and so on -- it's possible to establish a baseline of normal activity. Deviations from this baseline can indicate malicious activity, such as masquerading, and deserve further investigation.
 
-*Framework*: MITRE ATT&CK^TM^
+This rule identifies a potential malicious process masquerading as `Zoom.exe` or exploiting a vulnerability in the application causing it to execute code.
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Masquerading
-** ID: T1036
-** Reference URL: https://attack.mitre.org/techniques/T1036/
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-[[suspicious-zoom-child-process-history]]
-==== Rule version history
 
-Version 102 (8.6.0 release)::
-* Formatting only
+*Possible investigation steps*
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.parent.name : "Zoom.exe" and process.name : ("cmd.exe",
-"powershell.exe", "pwsh.exe", "powershell_ise.exe")
-----------------------------------
 
-Version 8 (8.4.0 release)::
-* Formatting only
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the command line of the child process to determine which commands or scripts were executed.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
 
-Version 6 (8.2.0 release)::
-* Formatting only
 
-Version 5 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.parent.name : "Zoom.exe" and process.name : ("cmd.exe",
-"powershell.exe", "pwsh.exe")
-----------------------------------
 
-Version 4 (7.12.0 release)::
-* Formatting only
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
 
-Version 3 (7.11.2 release)::
-* Formatting only
 
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:Zoom.exe and not process.name:(Zoom.exe or
-WerFault.exe or airhost.exe or CptControl.exe or CptHost.exe or
-cpthost.exe or CptInstall.exe or CptService.exe or Installer.exe or
-zCrashReport.exe or Zoom_launcher.exe or zTscoder.exe or
-plugin_Launcher.exe or mDNSResponder.exe or zDevHelper.exe or
-APcptControl.exe or CrashSender*.exe or aomhost64.exe or Magnify.exe
-or m_plugin_launcher.exe or com.zoom.us.zTranscode.exe or
-RoomConnector.exe or tabtip.exe or Explorer.exe or chrome.exe or
-firefox.exe or iexplore.exe or outlook.exe or lync.exe or
-ApplicationFrameHost.exe or ZoomAirhostInstaller.exe or narrator.exe
-or NVDA.exe or Magnify.exe or Outlook.exe or m_plugin_launcher.exe or
-mphost.exe or APcptControl.exe or winword.exe or excel.exe or
-powerpnt.exe or ONENOTE.EXE or wpp.exe or debug_message.exe or
-zAssistant.exe or msiexec.exe or msedge.exe or dwm.exe or
-vcredist_x86.exe or Controller.exe or Installer.exe or CptInstall.exe
-or Zoom_launcher.exe or ShellExperienceHost.exe or wps.exe)
+process where host.os.type == "windows" and event.type == "start" and
+ process.parent.name : "Zoom.exe" and process.name : ("cmd.exe", "powershell.exe", "pwsh.exe", "powershell_ise.exe")
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Technique:
+** Name: Process Injection
+** ID: T1055
+** Reference URL: https://attack.mitre.org/techniques/T1055/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Exploitation for Client Execution
+** ID: T1203
+** Reference URL: https://attack.mitre.org/techniques/T1203/
diff --git a/docs/detections/prebuilt-rules/rule-details/svchost-spawning-cmd.asciidoc b/docs/detections/prebuilt-rules/rule-details/svchost-spawning-cmd.asciidoc
index 512b34c76c..6d89a9c15b 100644
--- a/docs/detections/prebuilt-rules/rule-details/svchost-spawning-cmd.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/svchost-spawning-cmd.asciidoc
@@ -3,99 +3,97 @@
 
 Identifies a suspicious parent child process relationship with cmd.exe descending from svchost.exe
 
-*Rule type*: eql
+*Rule type*: new_terms
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
-* endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://nasbench.medium.com/demystifying-the-svchost-exe-process-and-its-command-line-options-508e9114e747
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Execution
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<svchost-spawning-cmd-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 212
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Svchost spawning Cmd
+*Triage and analysis*
+
+
 
-The Service Host process (SvcHost) is a system process that can host one, or multiple, Windows services in the Windows
-NT family of operating systems. Note that `Svchost.exe` is reserved for use by the operating system and should not be
-used by non-Windows services.
+*Investigating Svchost spawning Cmd*
 
-This rule looks for the creation of the `cmd.exe` process with `svchost.exe` as its parent process. This is an unusual
-behavior that can indicate the masquerading of a malicious process as `svchost.exe` or exploitation for privilege
-escalation.
+
+The Service Host process (SvcHost) is a system process that can host one, or multiple, Windows services in the Windows NT family of operating systems. Note that `Svchost.exe` is reserved for use by the operating system and should not be used by non-Windows services.
+
+This rule looks for the creation of the `cmd.exe` process with `svchost.exe` as its parent process. This is an unusual behavior that can indicate the masquerading of a malicious process as `svchost.exe` or exploitation for privilege escalation.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
 
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -103,40 +101,37 @@ and any spawned child processes.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"svchost.exe" and process.name : "cmd.exe" and not process.args :
-("??:\\Program Files\\Npcap\\CheckStatus.bat?", "?:\\Program
-Files\\Npcap\\CheckStatus.bat", "\\system32\\cleanmgr.exe",
-"?:\\Windows\\system32\\silcollector.cmd",
-"\\system32\\AppHostRegistrationVerifier.exe",
-"\\system32\\ServerManagerLauncher.exe", "dir",
-"?:\\Program Files\\*", "?:\\Program Files (x86)\\*",
-"?:\\Windows\\LSDeployment\\Lspush.exe",
-"(x86)\\FMAuditOnsite\\watchdog.bat",
-"?:\\ProgramData\\chocolatey\\bin\\choco-upgrade-all.bat",
-"Files\\Npcap\\CheckStatus.bat") and /* very noisy pattern - bat
-or cmd script executed via scheduled tasks */ not
-(process.parent.args : "netsvcs" and process.args : ("?:\\*.bat",
-"?:\\*.cmd"))
+[source, js]
 ----------------------------------
+host.os.type:windows and event.category:process and event.type:start and process.parent.name:"svchost.exe" and
+process.name:("cmd.exe" or "Cmd.exe" or "CMD.EXE") and
+not process.command_line : "\"cmd.exe\" /C sc control hptpsmarthealthservice 211"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -148,86 +143,3 @@ or cmd script executed via scheduled tasks */ not
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[svchost-spawning-cmd-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"svchost.exe" and process.name : "cmd.exe" and not
-(process.pe.original_file_name : "cmd.exe" and process.args : (
-"??:\\Program Files\\Npcap\\CheckStatus.bat?", "?:\\Program
-Files\\Npcap\\CheckStatus.bat", "\\system32\\cleanmgr.exe",
-"?:\\Windows\\system32\\silcollector.cmd",
-"\\system32\\AppHostRegistrationVerifier.exe",
-"\\system32\\ServerManagerLauncher.exe"))
-----------------------------------
-
-Version 14 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"svchost.exe" and process.name : "cmd.exe" and not
-(process.pe.original_file_name : "cmd.exe" and process.args : (
-"??:\\Program Files\\Npcap\\CheckStatus.bat?", "?:\\Program
-Files\\Npcap\\CheckStatus.bat", "\\system32\\cleanmgr.exe",
-"?:\\Windows\\system32\\silcollector.cmd",
-"\\system32\\AppHostRegistrationVerifier.exe",
-"\\system32\\ServerManagerLauncher.exe"))
-----------------------------------
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "svchost.exe" and process.name : "cmd.exe" and
-not (process.pe.original_file_name == "Cmd.Exe" and process.args :
-"?:\\Program Files\\Npcap\\CheckStatus.bat??")
-----------------------------------
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:svchost.exe and process.name:cmd.exe
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.parent.name:svchost.exe and process.name:cmd.exe
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/symbolic-link-to-shadow-copy-created.asciidoc b/docs/detections/prebuilt-rules/rule-details/symbolic-link-to-shadow-copy-created.asciidoc
index bd9aa1002f..766e8f39b4 100644
--- a/docs/detections/prebuilt-rules/rule-details/symbolic-link-to-shadow-copy-created.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/symbolic-link-to-shadow-copy-created.asciidoc
@@ -5,73 +5,70 @@ Identifies the creation of symbolic links to a shadow copy. Symbolic links can b
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/mklink
 * https://2017.zeronights.org/wp-content/uploads/materials/ZN17_Kheirkhabarov_Hunting_for_Credentials_Dumping_in_Windows_Environment.pdf
 * https://blog.netwrix.com/2021/11/30/extracting-password-hashes-from-the-ntds-dit-file/
 * https://www.hackingarticles.in/credential-dumping-ntds-dit/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 111
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Investigation Guide
-* Elastic Endgame
+* Austin Songer
+
+*Rule license*: Elastic License v2
 
-*Version*: 102 (<<symbolic-link-to-shadow-copy-created-history, version history>>)
 
-*Added ({stack} release)*: 8.0.0
+==== Investigation guide
 
-*Last modified ({stack} release)*: 8.6.0
 
-*Rule authors*: Elastic, Austin Songer
 
-*Rule license*: Elastic License v2
+*Triage and analysis*
 
-==== Potential false positives
 
-Legitimate administrative activity related to shadow copies.
 
-==== Investigation guide
+*Investigating Symbolic Link to Shadow Copy Created*
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+Shadow copies are backups or snapshots of an endpoint's files or volumes while they are in use. Adversaries may attempt to discover and create symbolic links to these shadow copies in order to copy sensitive information offline. If Active Directory (AD) is in use, often the ntds.dit file is a target as it contains password hashes, but an offline copy is needed to extract these hashes and potentially conduct lateral movement.
 
-### Investigating Symbolic Link to Shadow Copy Created
 
-Shadow copies are backups or snapshots of an endpoint's files or volumes while they are in use. Adversaries may attempt
-to discover and create symbolic links to these shadow copies in order to copy sensitive information offline. If Active
-Directory (AD) is in use, often the ntds.dit file is a target as it contains password hashes, but an offline copy is
-needed to extract these hashes and potentially conduct lateral movement.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Determine if a volume shadow copy was recently created on this endpoint.
 - Review privileges of the end user as this requires administrative access.
@@ -80,33 +77,42 @@ for prevalence, whether they are located in expected locations, and if they are
 - Investigate recent deletions of volume shadow copies.
 - Identify other files potentially copied from volume shadow copy paths directly.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This rule should cause very few false positives. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Related rules
+
+*Related rules*
+
 
 - NTDS or SAM Database File Copied - 3bc6deaa-fbd4-433a-ae21-3e892f95624f
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - If the entire domain or the `krbtgt` user was compromised:
-  - Activate your incident response plan for total Active Directory compromise which should include, but not be limited
-  to, a password reset (twice) of the `krbtgt` user.
+  - Activate your incident response plan for total Active Directory compromise which should include, but not be limited to, a password reset (twice) of the `krbtgt` user.
 - Locate and remove static files copied from volume shadow copies.
 - Command-Line tool mklink should require administrative access by default unless in developer mode.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
 
 Ensure advanced audit policies for Windows are enabled, specifically:
-Object Access policies [Event ID 4656](https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4656) (Handle to an Object was Requested)
+Object Access policies https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4656[Event ID 4656] (Handle to an Object was Requested)
 
 ```
 Computer Configuration >
@@ -123,23 +129,28 @@ Audit Handle Manipulation (Success,Failure)
 This event will only trigger if symbolic links are created from a new process spawning cmd.exe or powershell.exe with the correct arguments.
 Direct access to a shell and calling symbolic link creation tools will not generate an event matching this rule.
 
-If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define `event.ingested` and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate `event.ingested` to @timestamp for this rule to work.
-----------------------------------
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start","process_created") and
-process.pe.original_file_name in ("Cmd.Exe","PowerShell.EXE") and /*
-Create Symbolic Link to Shadow Copies */ process.args : ("*mklink*",
-"*SymbolicLink*") and process.command_line :
-("*HarddiskVolumeShadowCopy*")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ (
+    (?process.pe.original_file_name in ("Cmd.Exe","PowerShell.EXE")) or
+    (process.name : ("cmd.exe", "powershell.exe"))
+ ) and
+
+ /* Create Symbolic Link to Shadow Copies */
+ process.args : ("*mklink*", "*SymbolicLink*") and process.command_line : ("*HarddiskVolumeShadowCopy*")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -151,42 +162,11 @@ Create Symbolic Link to Shadow Copies */ process.args : ("*mklink*",
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-[[symbolic-link-to-shadow-copy-created-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start","process_created") and
-process.pe.original_file_name in ("Cmd.Exe","PowerShell.EXE") and
-/* Create Symbolic Link to Shadow Copies */ process.args :
-("*mklink*", "*SymbolicLink*") and process.command_line :
-("*HarddiskVolumeShadowCopy*")
-----------------------------------
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.pe.original_file_name == "Cmd.Exe" and process.args :
-"*mklink*" and process.args :
-"*\\GLOBALROOT\\Device\\HarddiskVolumeShadowCopy*"
-----------------------------------
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Security Account Manager
+** ID: T1003.002
+** Reference URL: https://attack.mitre.org/techniques/T1003/002/
+* Sub-technique:
+** Name: NTDS
+** ID: T1003.003
+** Reference URL: https://attack.mitre.org/techniques/T1003/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/system-binary-copied-and-or-moved-to-suspicious-directory.asciidoc b/docs/detections/prebuilt-rules/rule-details/system-binary-copied-and-or-moved-to-suspicious-directory.asciidoc
new file mode 100644
index 0000000000..ded457a309
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/system-binary-copied-and-or-moved-to-suspicious-directory.asciidoc
@@ -0,0 +1,130 @@
+[[system-binary-copied-and-or-moved-to-suspicious-directory]]
+=== System Binary Copied and/or Moved to Suspicious Directory
+
+This rule monitors for the copying or moving of a system binary to a suspicious directory. Adversaries may copy/move and rename system binaries to evade detection. Copying a system binary to a different location should not occur often, so if it does, the activity should be investigated.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.entity_id with maxspan=1s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+   process.name in ("cp", "mv") and process.args : (
+   // Shells
+   "/bin/*sh", "/usr/bin/*sh", 
+
+   // Interpreters
+   "/bin/python*", "/usr/bin/python*", "/bin/php*", "/usr/bin/php*", "/bin/ruby*", "/usr/bin/ruby*", "/bin/perl*",
+   "/usr/bin/perl*", "/bin/lua*", "/usr/bin/lua*", "/bin/java*", "/usr/bin/java*", 
+
+   // Compilers
+   "/bin/gcc*", "/usr/bin/gcc*", "/bin/g++*", "/usr/bin/g++*", "/bin/cc", "/usr/bin/cc",
+
+   // Suspicious utilities
+   "/bin/nc", "/usr/bin/nc", "/bin/ncat", "/usr/bin/ncat", "/bin/netcat", "/usr/bin/netcat", "/bin/nc.openbsd",
+   "/usr/bin/nc.openbsd", "/bin/*awk", "/usr/bin/*awk", "/bin/socat", "/usr/bin/socat", "/bin/openssl",
+   "/usr/bin/openssl", "/bin/telnet", "/usr/bin/telnet", "/bin/mkfifo", "/usr/bin/mkfifo", "/bin/mknod",
+   "/usr/bin/mknod", "/bin/ping*", "/usr/bin/ping*", "/bin/nmap", "/usr/bin/nmap",
+
+   // System utilities
+   "/bin/ls", "/usr/bin/ls", "/bin/cat", "/usr/bin/cat", "/bin/sudo", "/usr/bin/sudo", "/bin/curl", "/usr/bin/curl",
+   "/bin/wget", "/usr/bin/wget", "/bin/tmux", "/usr/bin/tmux", "/bin/screen", "/usr/bin/screen", "/bin/ssh",
+   "/usr/bin/ssh", "/bin/ftp", "/usr/bin/ftp"
+  ) and not process.parent.name in ("dracut-install", "apticron", "generate-from-dir", "platform-python")]
+  [file where host.os.type == "linux" and event.action == "creation" and file.path : (
+    "/dev/shm/*", "/run/shm/*", "/tmp/*", "/var/tmp/*", "/run/*", "/var/run/*", "/var/www/*", "/proc/*/fd/*"
+  ) and not file.path : ("/tmp/rear*", "/var/tmp/rear*", "/var/tmp/dracut*", "/var/tmp/mkinitramfs*")]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hide Artifacts
+** ID: T1564
+** Reference URL: https://attack.mitre.org/techniques/T1564/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Rename System Utilities
+** ID: T1036.003
+** Reference URL: https://attack.mitre.org/techniques/T1036/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/system-hosts-file-access.asciidoc b/docs/detections/prebuilt-rules/rule-details/system-hosts-file-access.asciidoc
new file mode 100644
index 0000000000..2e9547095a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/system-hosts-file-access.asciidoc
@@ -0,0 +1,67 @@
+[[system-hosts-file-access]]
+=== System Hosts File Access
+
+Identifies the use of built-in tools to read the contents of \etc\hosts on a local machine. Attackers may use this data to discover remote machines in an environment that may be used for Lateral Movement from the current system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started") and
+process.name in ("vi", "nano", "cat", "more", "less") and process.args == "/etc/hosts"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Remote System Discovery
+** ID: T1018
+** Reference URL: https://attack.mitre.org/techniques/T1018/
diff --git a/docs/detections/prebuilt-rules/rule-details/system-information-discovery-via-windows-command-shell.asciidoc b/docs/detections/prebuilt-rules/rule-details/system-information-discovery-via-windows-command-shell.asciidoc
index 83c1564490..5196d8eae0 100644
--- a/docs/detections/prebuilt-rules/rule-details/system-information-discovery-via-windows-command-shell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/system-information-discovery-via-windows-command-shell.asciidoc
@@ -1,62 +1,113 @@
 [[system-information-discovery-via-windows-command-shell]]
 === System Information Discovery via Windows Command Shell
 
-Identifies the execution of discovery commands to enumerate system info or files and folders using the Windows Command Shell.
+Identifies the execution of discovery commands to enumerate system information, files, and folders using the Windows Command Shell.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-windows.*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Execution
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Rule Type: BBR
 
-*Version*: 1
+*Version*: 10
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating System Information Discovery via Windows Command Shell*
+
+
+After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
+
+This rule identifies commands to enumerate system information, files, and folders using the Windows Command Shell.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+
+
+*False positive analysis*
+
+
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "cmd.exe" and
-process.args : "/c" and process.args : ("set", "dir")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "cmd.exe" and process.args : "/c" and process.args : ("set", "dir") and
+  not process.parent.executable : ("?:\\Program Files\\*", "?:\\Program Files (x86)\\*", "?:\\PROGRA~1\\*")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -68,8 +119,10 @@ process.args : "/c" and process.args : ("set", "dir")
 ** Name: System Information Discovery
 ** ID: T1082
 ** Reference URL: https://attack.mitre.org/techniques/T1082/
-
-
+* Technique:
+** Name: File and Directory Discovery
+** ID: T1083
+** Reference URL: https://attack.mitre.org/techniques/T1083/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -78,3 +131,7 @@ process.args : "/c" and process.args : ("set", "dir")
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/system-log-file-deletion.asciidoc b/docs/detections/prebuilt-rules/rule-details/system-log-file-deletion.asciidoc
index 8cd5d19e0f..f15fb76d3d 100644
--- a/docs/detections/prebuilt-rules/rule-details/system-log-file-deletion.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/system-log-file-deletion.asciidoc
@@ -5,66 +5,125 @@ Identifies the deletion of sensitive Linux system logs. This may indicate an att
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.fireeye.com/blog/threat-research/2020/11/live-off-the-land-an-overview-of-unc1945.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 110
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* Defense Evasion
 
-*Version*: 101 (<<system-log-file-deletion-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.11.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
 
-----------------------------------
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+*Custom Ingest Pipeline*
+
+For versions <8.2, you need to add a custom ingest pipeline to populate `event.ingested` with @timestamp for non-elastic-agent indexes, like auditbeats/filebeat/winlogbeat etc. For more details to add a custom ingest pipeline refer to the https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html[guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type == "deletion" and file.path : (
-"/var/run/utmp", "/var/log/wtmp", "/var/log/btmp",
-"/var/log/lastlog", "/var/log/faillog", "/var/log/syslog",
-"/var/log/messages", "/var/log/secure", "/var/log/auth.log",
-"/var/log/boot.log", "/var/log/kern.log" ) and not
-process.name : ("gzip")
+[source, js]
 ----------------------------------
+file where host.os.type == "linux" and event.type == "deletion" and
+  file.path :
+    (
+    "/var/run/utmp",
+    "/var/log/wtmp",
+    "/var/log/btmp",
+    "/var/log/lastlog",
+    "/var/log/faillog",
+    "/var/log/syslog",
+    "/var/log/messages",
+    "/var/log/secure",
+    "/var/log/auth.log",
+    "/var/log/boot.log",
+    "/var/log/kern.log"
+    ) and
+    not process.name in ("gzip", "executor", "dockerd")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,46 +132,10 @@ process.name : ("gzip")
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
 * Technique:
-** Name: Indicator Removal on Host
+** Name: Indicator Removal
 ** ID: T1070
 ** Reference URL: https://attack.mitre.org/techniques/T1070/
-
-[[system-log-file-deletion-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type == "deletion" and file.path : (
-"/var/run/utmp", "/var/log/wtmp", "/var/log/btmp",
-"/var/log/lastlog", "/var/log/faillog", "/var/log/syslog",
-"/var/log/messages", "/var/log/secure", "/var/log/auth.log"
-) and not process.name : ("gzip")
-----------------------------------
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type == "deletion" and file.path : (
-"/var/run/utmp", "/var/log/wtmp", "/var/log/btmp",
-"/var/log/lastlog", "/var/log/faillog", "/var/log/syslog",
-"/var/log/messages", "/var/log/secure", "/var/log/auth.log"
-)
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Clear Linux or Mac System Logs
+** ID: T1070.002
+** Reference URL: https://attack.mitre.org/techniques/T1070/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/system-network-connections-discovery.asciidoc b/docs/detections/prebuilt-rules/rule-details/system-network-connections-discovery.asciidoc
new file mode 100644
index 0000000000..54c9ba6b2a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/system-network-connections-discovery.asciidoc
@@ -0,0 +1,67 @@
+[[system-network-connections-discovery]]
+=== System Network Connections Discovery
+
+Adversaries may attempt to get a listing of network connections to or from a compromised system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started") and
+process.name in ("netstat", "lsof", "who", "w")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Network Connections Discovery
+** ID: T1049
+** Reference URL: https://attack.mitre.org/techniques/T1049/
diff --git a/docs/detections/prebuilt-rules/rule-details/system-owner-user-discovery-linux.asciidoc b/docs/detections/prebuilt-rules/rule-details/system-owner-user-discovery-linux.asciidoc
new file mode 100644
index 0000000000..7e9567ed3d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/system-owner-user-discovery-linux.asciidoc
@@ -0,0 +1,70 @@
+[[system-owner-user-discovery-linux]]
+=== System Owner/User Discovery Linux
+
+Identifies the use of built-in tools which adversaries may use to enumerate the system owner/user of a compromised system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started") and 
+process.name : ("whoami", "w", "who", "users", "id")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Owner/User Discovery
+** ID: T1033
+** Reference URL: https://attack.mitre.org/techniques/T1033/
+* Technique:
+** Name: Permission Groups Discovery
+** ID: T1069
+** Reference URL: https://attack.mitre.org/techniques/T1069/
diff --git a/docs/detections/prebuilt-rules/rule-details/system-service-discovery-through-built-in-windows-utilities.asciidoc b/docs/detections/prebuilt-rules/rule-details/system-service-discovery-through-built-in-windows-utilities.asciidoc
new file mode 100644
index 0000000000..7bef293b15
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/system-service-discovery-through-built-in-windows-utilities.asciidoc
@@ -0,0 +1,72 @@
+[[system-service-discovery-through-built-in-windows-utilities]]
+=== System Service Discovery through built-in Windows Utilities
+
+Detects the usage of commonly used system service discovery techniques, which attackers may use during the reconnaissance phase after compromising a system in order to gain a better understanding of the environment and/or escalate privileges.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Rule Type: BBR
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (
+  ((process.name: "net.exe" or process.pe.original_file_name == "net.exe" or (process.name : "net1.exe" and 
+    not process.parent.name : "net.exe")) and process.args : ("start", "use") and process.args_count == 2) or
+  ((process.name: "sc.exe" or process.pe.original_file_name == "sc.exe") and process.args: ("query", "q*")) or
+  ((process.name: "tasklist.exe" or process.pe.original_file_name == "tasklist.exe") and process.args: "/svc") or
+  (process.name : "psservice.exe" or process.pe.original_file_name == "psservice.exe")
+  ) and not user.id : "S-1-5-18"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Service Discovery
+** ID: T1007
+** Reference URL: https://attack.mitre.org/techniques/T1007/
diff --git a/docs/detections/prebuilt-rules/rule-details/system-shells-via-services.asciidoc b/docs/detections/prebuilt-rules/rule-details/system-shells-via-services.asciidoc
index 1957cf34fe..79f8947f3c 100644
--- a/docs/detections/prebuilt-rules/rule-details/system-shells-via-services.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/system-shells-via-services.asciidoc
@@ -5,100 +5,113 @@ Windows services typically run as SYSTEM and can be used as a privilege escalati
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<system-shells-via-services-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating System Shells via Services
+*Triage and analysis*
+
+
+
+*Investigating System Shells via Services*
 
-Attackers may configure existing services or create new ones to execute system shells to elevate their privileges from
-administrator to SYSTEM. They can also configure services to execute these shells with persistence payloads.
+
+Attackers may configure existing services or create new ones to execute system shells to elevate their privileges from administrator to SYSTEM. They can also configure services to execute these shells with persistence payloads.
 
 This rule looks for system shells being spawned by `services.exe`, which is compatible with the above behavior.
 
-#### Possible investigation steps
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Identify how the service was created or modified. Look for registry changes events or Windows events related to
-service activities (for example, 4697 and/or 7045).
-  - Identify the user account that performed the action and whether it should perform this kind of action.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Identify how the service was created or modified. Look for registry changes events or Windows events related to service activities (for example, 4697 and/or 7045).
+  - Examine the created and existent services, the executables or drivers referenced, and command line arguments for suspicious entries.
+    - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+    - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+    - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the referenced files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
 - Check for commands executed under the spawned shell.
 
-### False positive analysis
 
-- This activity should not happen legitimately. The security team should address any potential benign true positive
-(B-TP), as this configuration can put the user and the domain at risk.
+*False positive analysis*
+
+
+- This activity should not happen legitimately. The security team should address any potential benign true positive (B-TP), as this configuration can put the user and the domain at risk.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Delete the service or restore it to the original configuration.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"services.exe" and process.name : ("cmd.exe", "powershell.exe",
-"pwsh.exe", "powershell_ise.exe") and /* Third party FP's */ not
-process.args : "NVDisplay.ContainerLocalSystem"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : "services.exe" and
+  process.name : ("cmd.exe", "powershell.exe", "pwsh.exe", "powershell_ise.exe") and
 
-==== Threat mapping
+  /* Third party FP's */
+  not process.args : "NVDisplay.ContainerLocalSystem"
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -110,94 +123,23 @@ process.args : "NVDisplay.ContainerLocalSystem"
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[system-shells-via-services-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "services.exe" and process.name : ("cmd.exe",
-"powershell.exe", "pwsh.exe", "powershell_ise.exe") and /* Third
-party FP's */ not process.args : "NVDisplay.ContainerLocalSystem"
-----------------------------------
-
-Version 14 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "services.exe" and process.name : ("cmd.exe",
-"powershell.exe", "pwsh.exe", "powershell_ise.exe") and /* Third
-party FP's */ not process.args : "NVDisplay.ContainerLocalSystem"
-----------------------------------
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 11 (8.2.0 release)::
-* Formatting only
-
-Version 10 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "services.exe" and process.name : ("cmd.exe",
-"powershell.exe") and /* Third party FP's */ not process.args :
-"NVDisplay.ContainerLocalSystem"
-----------------------------------
-
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:services.exe and process.name:(cmd.exe or
-powershell.exe)
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.parent.name:services.exe and process.name:(cmd.exe or
-powershell.exe)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.parent.name:"services.exe" and process.name:("cmd.exe" or
-"powershell.exe")
-----------------------------------
-
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/system-time-discovery.asciidoc b/docs/detections/prebuilt-rules/rule-details/system-time-discovery.asciidoc
new file mode 100644
index 0000000000..4de422ecbd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/system-time-discovery.asciidoc
@@ -0,0 +1,73 @@
+[[system-time-discovery]]
+=== System Time Discovery
+
+Detects the usage of commonly used system time discovery techniques, which attackers may use during the reconnaissance phase after compromising a system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Rule Type: BBR
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+(
+ (
+    (process.name: "net.exe" or (process.name : "net1.exe" and not process.parent.name : "net.exe")) and 
+    process.args : "time" and not process.args : "/set"
+ ) or 
+ (process.name: "w32tm.exe" and process.args: "/tz") or 
+ (process.name: "tzutil.exe" and process.args: "/g")
+) and not user.id : ("S-1-5-18", "S-1-5-19", "S-1-5-20")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Time Discovery
+** ID: T1124
+** Reference URL: https://attack.mitre.org/techniques/T1124/
diff --git a/docs/detections/prebuilt-rules/rule-details/systemkey-access-via-command-line.asciidoc b/docs/detections/prebuilt-rules/rule-details/systemkey-access-via-command-line.asciidoc
index 223c8ce9d4..2a04fce7f0 100644
--- a/docs/detections/prebuilt-rules/rule-details/systemkey-access-via-command-line.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/systemkey-access-via-command-line.asciidoc
@@ -5,53 +5,88 @@ Keychains are the built-in way for macOS to keep track of users' passwords and c
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/AlessandroZ/LaZagne/blob/master/Mac/lazagne/softwares/system/chainbreaker.py
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Credential Access
 
-*Version*: 100 (<<systemkey-access-via-command-line-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.12.0
+==== Setup
 
-*Last modified ({stack} release)*: 8.5.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.args:("/private/var/db/SystemKey" or "/var/db/SystemKey")
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and
+  process.args:("/private/var/db/SystemKey" or "/var/db/SystemKey") and
+  not process.Ext.effective_parent.executable : "/Library/Elastic/Endpoint/elastic-endpoint.app/Contents/MacOS/elastic-endpoint"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -63,22 +98,7 @@ process.args:("/private/var/db/SystemKey" or "/var/db/SystemKey")
 ** Name: Credentials from Password Stores
 ** ID: T1555
 ** Reference URL: https://attack.mitre.org/techniques/T1555/
-
-[[systemkey-access-via-command-line-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.args:"/private/var/db/SystemKey"
-----------------------------------
-
+* Sub-technique:
+** Name: Keychain
+** ID: T1555.001
+** Reference URL: https://attack.mitre.org/techniques/T1555/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/tainted-kernel-module-load.asciidoc b/docs/detections/prebuilt-rules/rule-details/tainted-kernel-module-load.asciidoc
new file mode 100644
index 0000000000..5fadef1dca
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/tainted-kernel-module-load.asciidoc
@@ -0,0 +1,105 @@
+[[tainted-kernel-module-load]]
+=== Tainted Kernel Module Load
+
+This rule monitors the syslog log file for messages related to instances of a tainted kernel module load. Rootkits often leverage kernel modules as their main defense evasion technique. Detecting tainted kernel module loads is crucial for ensuring system security and integrity, as malicious or unauthorized modules can compromise the kernel and lead to system vulnerabilities or unauthorized access.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-system.syslog-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Filebeat
+
+
+*Filebeat Setup*
+
+Filebeat is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to Elasticsearch or Logstash for indexing.
+
+
+*The following steps should be executed in order to add the Filebeat for the Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html[helper guide].
+- To run Filebeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-docker.html[helper guide].
+- To run Filebeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html[helper guide].
+- For quick start information for Filebeat refer to the https://www.elastic.co/guide/en/beats/filebeat/8.11/filebeat-installation-configuration.html[helper guide].
+- For complete Setup and Run Filebeat information refer to the https://www.elastic.co/guide/en/beats/filebeat/current/setting-up-and-running.html[helper guide].
+
+
+*Rule Specific Setup Note*
+
+- This rule requires the Filebeat System Module to be enabled.
+- The system module collects and parses logs created by the system logging service of common Unix/Linux based distributions.
+- To run the system module of Filebeat on Linux follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-system.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.dataset:"system.syslog" and process.name:kernel and 
+message:"module verification failed: signature and/or required key missing - tainting kernel"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Sub-technique:
+** Name: Kernel Modules and Extensions
+** ID: T1547.006
+** Reference URL: https://attack.mitre.org/techniques/T1547/006/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Rootkit
+** ID: T1014
+** Reference URL: https://attack.mitre.org/techniques/T1014/
diff --git a/docs/detections/prebuilt-rules/rule-details/tainted-out-of-tree-kernel-module-load.asciidoc b/docs/detections/prebuilt-rules/rule-details/tainted-out-of-tree-kernel-module-load.asciidoc
new file mode 100644
index 0000000000..a7e2070b17
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/tainted-out-of-tree-kernel-module-load.asciidoc
@@ -0,0 +1,105 @@
+[[tainted-out-of-tree-kernel-module-load]]
+=== Tainted Out-Of-Tree Kernel Module Load
+
+This rule monitors the syslog log file for messages related to instances of a out-of-tree kernel module load, indicating the taining of the kernel. Rootkits often leverage kernel modules as their main defense evasion technique. Detecting tainted kernel module loads is crucial for ensuring system security and integrity, as malicious or unauthorized modules can compromise the kernel and lead to system vulnerabilities or unauthorized access.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-system.syslog-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from one of the following integrations:
+- Filebeat
+
+
+*Filebeat Setup*
+
+Filebeat is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to Elasticsearch or Logstash for indexing.
+
+
+*The following steps should be executed in order to add the Filebeat for the Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html[helper guide].
+- To run Filebeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-docker.html[helper guide].
+- To run Filebeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html[helper guide].
+- For quick start information for Filebeat refer to the https://www.elastic.co/guide/en/beats/filebeat/8.11/filebeat-installation-configuration.html[helper guide].
+- For complete Setup and Run Filebeat information refer to the https://www.elastic.co/guide/en/beats/filebeat/current/setting-up-and-running.html[helper guide].
+
+
+*Rule Specific Setup Note*
+
+- This rule requires the Filebeat System Module to be enabled.
+- The system module collects and parses logs created by the system logging service of common Unix/Linux based distributions.
+- To run the system module of Filebeat on Linux follow the setup instructions in the https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-system.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:linux and event.dataset:"system.syslog" and process.name:kernel and 
+message:"loading out-of-tree module taints kernel."
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Boot or Logon Autostart Execution
+** ID: T1547
+** Reference URL: https://attack.mitre.org/techniques/T1547/
+* Sub-technique:
+** Name: Kernel Modules and Extensions
+** ID: T1547.006
+** Reference URL: https://attack.mitre.org/techniques/T1547/006/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Rootkit
+** ID: T1014
+** Reference URL: https://attack.mitre.org/techniques/T1014/
diff --git a/docs/detections/prebuilt-rules/rule-details/tampering-of-shell-command-line-history.asciidoc b/docs/detections/prebuilt-rules/rule-details/tampering-of-shell-command-line-history.asciidoc
new file mode 100644
index 0000000000..3f53ba270f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/tampering-of-shell-command-line-history.asciidoc
@@ -0,0 +1,94 @@
+[[tampering-of-shell-command-line-history]]
+=== Tampering of Shell Command-Line History
+
+Adversaries may attempt to clear or disable the Bash command-line history in an attempt to evade detection or forensic investigations.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 105
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.action in ("exec", "exec_event", "executed", "process_started") and event.type == "start" and
+ (
+  ((process.args : ("rm", "echo") or
+    (process.args : "ln" and process.args : "-sf" and process.args : "/dev/null") or
+    (process.args : "truncate" and process.args : "-s0"))
+    and process.args : (".bash_history", "/root/.bash_history", "/home/*/.bash_history","/Users/.bash_history", "/Users/*/.bash_history",
+                        ".zsh_history", "/root/.zsh_history", "/home/*/.zsh_history", "/Users/.zsh_history", "/Users/*/.zsh_history")) or
+  (process.name : "history" and process.args : "-c") or
+  (process.args : "export" and process.args : ("HISTFILE=/dev/null", "HISTFILESIZE=0")) or
+  (process.args : "unset" and process.args : "HISTFILE") or
+  (process.args : "set" and process.args : "history" and process.args : "+o")
+ )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indicator Removal
+** ID: T1070
+** Reference URL: https://attack.mitre.org/techniques/T1070/
+* Sub-technique:
+** Name: Clear Command History
+** ID: T1070.003
+** Reference URL: https://attack.mitre.org/techniques/T1070/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/tcc-bypass-via-mounted-apfs-snapshot-access.asciidoc b/docs/detections/prebuilt-rules/rule-details/tcc-bypass-via-mounted-apfs-snapshot-access.asciidoc
index d2f85256e6..3a4a4c5f89 100644
--- a/docs/detections/prebuilt-rules/rule-details/tcc-bypass-via-mounted-apfs-snapshot-access.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/tcc-bypass-via-mounted-apfs-snapshot-access.asciidoc
@@ -5,55 +5,88 @@ Identifies the use of the mount_apfs command to mount the entire file system thr
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://theevilbit.github.io/posts/cve_2020_9771/
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+
+*Version*: 106
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Defense Evasion
-* CVE_2020_9771
 
-*Version*: 100 (<<tcc-bypass-via-mounted-apfs-snapshot-access-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category : process and event.type : (start or process_started)
-and process.name : mount_apfs and process.args :
-(/System/Volumes/Data and noowners)
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:(start or process_started) and process.name:mount_apfs and
+  process.args:(/System/Volumes/Data and noowners)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -65,13 +98,3 @@ and process.name : mount_apfs and process.args :
 ** Name: Direct Volume Access
 ** ID: T1006
 ** Reference URL: https://attack.mitre.org/techniques/T1006/
-
-[[tcc-bypass-via-mounted-apfs-snapshot-access-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/temporarily-scheduled-task-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/temporarily-scheduled-task-creation.asciidoc
index 1f159bf244..39c08b7f89 100644
--- a/docs/detections/prebuilt-rules/rule-details/temporarily-scheduled-task-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/temporarily-scheduled-task-creation.asciidoc
@@ -5,73 +5,56 @@ Indicates the creation and deletion of a scheduled task within a short time inte
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4698
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Persistence
-
-*Version*: 2 (<<temporarily-scheduled-task-creation-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Execution
 
-*Added ({stack} release)*: 8.5.0
+*Version*: 7
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Legitimate scheduled tasks may be created during installation of new software.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, winlog.event_data.TaskName with maxspan=5m
-[iam where event.action == "scheduled-task-created" and not user.name
-: "*$"] [iam where event.action == "scheduled-task-deleted" and not
-user.name : "*$"]
+[source, js]
 ----------------------------------
+sequence by winlog.computer_name, winlog.event_data.TaskName with maxspan=5m
+   [iam where event.action == "scheduled-task-created" and not user.name : "*$"]
+   [iam where event.action == "scheduled-task-deleted" and not user.name : "*$"]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Defense Evasion
-** ID: TA0005
-** Reference URL: https://attack.mitre.org/tactics/TA0005/
-* Technique:
-** Name: Indicator Removal on Host
-** ID: T1070
-** Reference URL: https://attack.mitre.org/techniques/T1070/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
@@ -80,17 +63,19 @@ user.name : "*$"]
 ** Name: Scheduled Task/Job
 ** ID: T1053
 ** Reference URL: https://attack.mitre.org/techniques/T1053/
-
-[[temporarily-scheduled-task-creation-history]]
-==== Rule version history
-
-Version 2 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, winlog.event_data.TaskName with maxspan=5m
-[iam where event.action == "scheduled-task-created"] [iam where
-event.action == "scheduled-task-deleted"]
-----------------------------------
-
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/third-party-backup-files-deleted-via-unexpected-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/third-party-backup-files-deleted-via-unexpected-process.asciidoc
index 352946124c..2c61e00cf4 100644
--- a/docs/detections/prebuilt-rules/rule-details/third-party-backup-files-deleted-via-unexpected-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/third-party-backup-files-deleted-via-unexpected-process.asciidoc
@@ -5,123 +5,148 @@ Identifies the deletion of backup files, saved using third-party software, by a
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.advintel.io/post/backup-removal-solutions-from-conti-ransomware-with-love
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 112
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Impact
-* Investigation Guide
-* Elastic Endgame
 
-*Version*: 102 (<<third-party-backup-files-deleted-via-unexpected-process-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.16.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Certain utilities that delete files for disk cleanup or Administrators manually removing backup files.
 
-==== Investigation guide
 
+*Investigating Third-party Backup Files Deleted via Unexpected Process*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Third-party Backup Files Deleted via Unexpected Process
+Backups are a significant obstacle for any ransomware operation. They allow the victim to resume business by performing data recovery, making them a valuable target.
+
+Attackers can delete backups from the host and gain access to backup servers to remove centralized backups for the environment, ensuring that victims have no alternatives to paying the ransom.
 
-Backups are a significant obstacle for any ransomware operation. They allow the victim to resume business by performing
-data recovery, making them a valuable target.
+This rule identifies file deletions performed by a process that does not belong to the backup suite and aims to delete Veritas or Veeam backups.
 
-Attackers can delete backups from the host and gain access to backup servers to remove centralized backups for the
-environment, ensuring that victims have no alternatives to paying the ransom.
 
-This rule identifies file deletions performed by a process that does not belong to the backup suite and aims to delete
-Veritas or Veeam backups.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Check if any files on the host machine have been encrypted.
 
-### False positive analysis
 
-- This rule can be triggered by the manual removal of backup files and by removal using other third-party tools that are
-not from the backup suite. Exceptions can be added for specific accounts and executables, preferably tied together.
+*False positive analysis*
+
+
+- This rule can be triggered by the manual removal of backup files and by removal using other third-party tools that are not from the backup suite. Exceptions can be added for specific accounts and executables, preferably tied together.
+
+
+*Related rules*
 
-### Related rules
 
 - Deleting Backup Catalogs with Wbadmin - 581add16-df76-42bb-af8e-c979bfb39a59
 - Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
 - Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
 - Volume Shadow Copy Deletion via WMIC - dc9c1f74-dac3-48e3-b47f-eb79db358f57
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
 - Perform data recovery locally or restore the backups from replicated copies (Cloud, other servers, etc.).
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type == "deletion" and ( /* Veeam Related Backup
-Files */ (file.extension : ("VBK", "VIB", "VBM") and not
-process.executable : ("?:\\Windows\\Veeam\\Backup\\*",
-"?:\\Program Files\\Veeam\\Backup and Replication\\*",
-"?:\\Program Files (x86)\\Veeam\\Backup and Replication\\*")) or /*
-Veritas Backup Exec Related Backup File */ (file.extension : "BKF"
-and not process.executable : ("?:\\Program Files\\Veritas\\Backup
-Exec\\*", "?:\\Program Files
-(x86)\\Veritas\\Backup Exec\\*")) )
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type == "deletion" and
+  (
+    /* Veeam Related Backup Files */
+    (
+      file.extension : ("VBK", "VIB", "VBM") and
+      not (
+        process.executable : ("?:\\Windows\\*", "?:\\Program Files\\*", "?:\\Program Files (x86)\\*") and
+        (process.code_signature.trusted == true and process.code_signature.subject_name : ("Veeam Software Group GmbH", "Veeam Software AG"))
+      )
+    ) or
+    /* Veritas Backup Exec Related Backup File */
+    (
+      file.extension : "BKF" and
+        not process.executable : (
+          "?:\\Program Files\\Veritas\\Backup Exec\\*",
+          "?:\\Program Files (x86)\\Veritas\\Backup Exec\\*"
+        )
+    )
+  ) and
+  not (
+    process.name : ("MSExchangeMailboxAssistants.exe", "Microsoft.PowerBI.EnterpriseGateway.exe") and
+      (process.code_signature.subject_name : "Microsoft Corporation" and process.code_signature.trusted == true)
+  ) and
+  not file.path : (
+    "?:\\ProgramData\\Trend Micro\\*",
+    "?:\\Program Files (x86)\\Trend Micro\\*",
+    "?:\\$RECYCLE.BIN\\*"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -133,25 +158,7 @@ Exec\\*", "?:\\Program Files
 ** Name: Inhibit System Recovery
 ** ID: T1490
 ** Reference URL: https://attack.mitre.org/techniques/T1490/
-
-[[third-party-backup-files-deleted-via-unexpected-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.0.0 release)::
-* Formatting only
-
+* Technique:
+** Name: Data Destruction
+** ID: T1485
+** Reference URL: https://attack.mitre.org/techniques/T1485/
diff --git a/docs/detections/prebuilt-rules/rule-details/threat-intel-hash-indicator-match.asciidoc b/docs/detections/prebuilt-rules/rule-details/threat-intel-hash-indicator-match.asciidoc
new file mode 100644
index 0000000000..d1acbc48a8
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/threat-intel-hash-indicator-match.asciidoc
@@ -0,0 +1,137 @@
+[[threat-intel-hash-indicator-match]]
+=== Threat Intel Hash Indicator Match
+
+This rule is triggered when a hash indicator from the Threat Intel Filebeat module or integrations has a match against an event that contains file hashes, such as antivirus alerts, process creation, library load, and file operation events.
+
+*Rule type*: threat_match
+
+*Rule indices*: 
+
+* auditbeat-*
+* endgame-*
+* filebeat-*
+* logs-*
+* winlogbeat-*
+
+*Severity*: critical
+
+*Risk score*: 99
+
+*Runs every*: 1h
+
+*Searches indices from*: now-65m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-threatintel.html
+* https://www.elastic.co/guide/en/security/master/es-threat-intel-integrations.html
+* https://www.elastic.co/security/tip
+
+*Tags*: 
+
+* OS: Windows
+* Data Source: Elastic Endgame
+* Rule Type: Indicator Match
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and Analysis*
+
+
+
+*Investigating Threat Intel Hash Indicator Match*
+
+
+Threat Intel indicator match rules allow matching from a local observation, such as an endpoint event that records a file hash with an entry of a file hash stored within the Threat Intel integrations index.
+
+Matches are based on threat intelligence data that's been ingested during the last 30 days. Some integrations don't place expiration dates on their threat indicators, so we strongly recommend validating ingested threat indicators and reviewing match results. When reviewing match results, check associated activity to determine whether the event requires additional investigation.
+
+This rule is triggered when a hash indicator from the Threat Intel Filebeat module or an indicator ingested from a threat intelligence integration matches against an event that contains file hashes, such as antivirus alerts, file operation events, etc.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Gain context about the field that matched the local observation. This information can be found in the `threat.indicator.matched.field` field.
+- Investigate the hash , which can be found in the `threat.indicator.matched.atomic` field:
+  - Search for the existence and reputation of the hash in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+  - Scope other potentially compromised hosts in your environment by mapping hosts with file operations involving the same hash.
+- Identify the process that created the file.
+  - Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - Enrich the information that you have right now by determining how the file was dropped, where it was downloaded from, etc. This can help you determine if the event is part of an ongoing campaign against the organization.
+- Retrieve the involved file and examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+- Using the data collected through the analysis, scope users targeted and other machines infected in the environment.
+
+
+*False Positive Analysis*
+
+
+- Adversaries often use legitimate tools as network administrators, such as `PsExec` or `AdFind`. These tools are often included in indicator lists, which creates the potential for false positives.
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule needs threat intelligence indicators to work.
+Threat intelligence indicators can be collected using an https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#agent-ti-integration[Elastic Agent integration],
+the https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#ti-mod-integration[Threat Intel module],
+or a https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#custom-ti-integration[custom integration].
+
+More information can be found https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html[here].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file.hash.*:* or process.hash.*:* or dll.hash.*:*
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/threat-intel-ip-address-indicator-match.asciidoc b/docs/detections/prebuilt-rules/rule-details/threat-intel-ip-address-indicator-match.asciidoc
new file mode 100644
index 0000000000..43e3dce2a0
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/threat-intel-ip-address-indicator-match.asciidoc
@@ -0,0 +1,139 @@
+[[threat-intel-ip-address-indicator-match]]
+=== Threat Intel IP Address Indicator Match
+
+This rule is triggered when an IP address indicator from the Threat Intel Filebeat module or integrations has a match against a network event.
+
+*Rule type*: threat_match
+
+*Rule indices*: 
+
+* auditbeat-*
+* endgame-*
+* filebeat-*
+* logs-*
+* packetbeat-*
+* winlogbeat-*
+
+*Severity*: critical
+
+*Risk score*: 99
+
+*Runs every*: 1h
+
+*Searches indices from*: now-65m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-threatintel.html
+* https://www.elastic.co/guide/en/security/master/es-threat-intel-integrations.html
+* https://www.elastic.co/security/tip
+
+*Tags*: 
+
+* OS: Windows
+* Data Source: Elastic Endgame
+* Rule Type: Indicator Match
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and Analysis*
+
+
+
+*Investigating Threat Intel IP Address Indicator Match*
+
+
+Threat Intel indicator match rules allow matching from a local observation, such as an endpoint event that records a file hash with an entry of a file hash stored within the Threat Intel integrations index.
+
+Matches are based on threat intelligence data that's been ingested during the last 30 days. Some integrations don't place expiration dates on their threat indicators, so we strongly recommend validating ingested threat indicators and reviewing match results. When reviewing match results, check associated activity to determine whether the event requires additional investigation.
+
+This rule is triggered when an IP address indicator from the Threat Intel Filebeat module or a threat intelligence integration matches against a network event.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Gain context about the field that matched the local observation so you can understand the nature of the connection. This information can be found in the `threat.indicator.matched.field` field.
+- Investigate the IP address, which can be found in the `threat.indicator.matched.atomic` field:
+  - Check the reputation of the IP address in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+  - Execute a reverse DNS lookup to retrieve hostnames associated with the given IP address.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Identify the process responsible for the connection, and investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Retrieve the involved process executable and examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+- Using the data collected through the analysis, scope users targeted and other machines infected in the environment.
+
+
+*False Positive Analysis*
+
+
+- When a match is found, it's important to consider the indicator's initial release date. Threat intelligence is useful for augmenting existing security processes but can quickly become outdated. In other words, some threat intelligence only represents a specific set of activity observed at a specific time. For example, an IP address may have hosted malware observed in a Dridex campaign months ago, but it's possible that IP has been remediated and no longer represents any threat.
+- False positives might occur after large and publicly written campaigns if curious employees interact with attacker infrastructure.
+- Some feeds may include internal or known benign addresses by mistake (e.g., 8.8.8.8, google.com, 127.0.0.1, etc.). Make sure you understand how blocking a specific domain or address might impact the organization or normal system functioning.
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule needs threat intelligence indicators to work.
+Threat intelligence indicators can be collected using an https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#agent-ti-integration[Elastic Agent integration],
+the https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#ti-mod-integration[Threat Intel module],
+or a https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#custom-ti-integration[custom integration].
+
+More information can be found https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html[here].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+source.ip:* or destination.ip:*
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/threat-intel-url-indicator-match.asciidoc b/docs/detections/prebuilt-rules/rule-details/threat-intel-url-indicator-match.asciidoc
new file mode 100644
index 0000000000..342a52c68c
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/threat-intel-url-indicator-match.asciidoc
@@ -0,0 +1,142 @@
+[[threat-intel-url-indicator-match]]
+=== Threat Intel URL Indicator Match
+
+This rule is triggered when a URL indicator from the Threat Intel Filebeat module or integrations has a match against an event that contains URL data, like DNS events, network logs, etc.
+
+*Rule type*: threat_match
+
+*Rule indices*: 
+
+* auditbeat-*
+* endgame-*
+* filebeat-*
+* logs-*
+* packetbeat-*
+* winlogbeat-*
+
+*Severity*: critical
+
+*Risk score*: 99
+
+*Runs every*: 1h
+
+*Searches indices from*: now-65m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-threatintel.html
+* https://www.elastic.co/guide/en/security/master/es-threat-intel-integrations.html
+* https://www.elastic.co/security/tip
+
+*Tags*: 
+
+* OS: Windows
+* Data Source: Elastic Endgame
+* Rule Type: Indicator Match
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and Analysis*
+
+
+
+*Investigating Threat Intel URL Indicator Match*
+
+
+Threat Intel indicator match rules allow matching from a local observation, such as an endpoint event that records a file hash with an entry of a file hash stored within the Threat Intel integrations index.
+
+Matches are based on threat intelligence data that's been ingested during the last 30 days. Some integrations don't place expiration dates on their threat indicators, so we strongly recommend validating ingested threat indicators and reviewing match results. When reviewing match results, check associated activity to determine whether the event requires additional investigation.
+
+This rule is triggered when a URL indicator from the Threat Intel Filebeat module or a threat intelligence integration matches against an event that contains URL data, like DNS events, network logs, etc.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the URL, which can be found in the `threat.indicator.matched.atomic` field:
+  - Identify the type of malicious activity related to the URL (phishing, malware, etc.).
+  - Check the reputation of the IP address in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+  - Execute a WHOIS lookup to retrieve information about the domain registration and contacts to report abuse.
+  - If dealing with a phishing incident:
+    - Contact the user to gain more information around the delivery method, information sent, etc.
+    - Analyze whether the URL is trying to impersonate a legitimate address. Look for typosquatting, extra or unusual subdomains, or other anomalies that could lure the user.
+    - Investigate the phishing page to identify which information may have been sent to the attacker by the user.
+- Identify the process responsible for the connection, and investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Retrieve the involved process executable and examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+- Using the data collected through the analysis, scope users targeted and other machines infected in the environment.
+
+
+*False Positive Analysis*
+
+
+- False positives might occur after large and publicly written campaigns if curious employees interact with attacker infrastructure.
+- Some feeds may include internal or known benign addresses by mistake (e.g., 8.8.8.8, google.com, 127.0.0.1, etc.). Make sure you understand how blocking a specific domain or address might impact the organization or normal system functioning.
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Consider reporting the address for abuse using the provided contact information.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule needs threat intelligence indicators to work.
+Threat intelligence indicators can be collected using an https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#agent-ti-integration[Elastic Agent integration],
+the https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#ti-mod-integration[Threat Intel module],
+or a https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#custom-ti-integration[custom integration].
+
+More information can be found https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html[here].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+url.full:*
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/threat-intel-windows-registry-indicator-match.asciidoc b/docs/detections/prebuilt-rules/rule-details/threat-intel-windows-registry-indicator-match.asciidoc
new file mode 100644
index 0000000000..6da1eecf2f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/threat-intel-windows-registry-indicator-match.asciidoc
@@ -0,0 +1,132 @@
+[[threat-intel-windows-registry-indicator-match]]
+=== Threat Intel Windows Registry Indicator Match
+
+This rule is triggered when a Windows registry indicator from the Threat Intel Filebeat module or integrations has a match against an event that contains registry data.
+
+*Rule type*: threat_match
+
+*Rule indices*: 
+
+* auditbeat-*
+* endgame-*
+* filebeat-*
+* logs-*
+* winlogbeat-*
+
+*Severity*: critical
+
+*Risk score*: 99
+
+*Runs every*: 1h
+
+*Searches indices from*: now-65m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-threatintel.html
+* https://www.elastic.co/guide/en/security/master/es-threat-intel-integrations.html
+* https://www.elastic.co/security/tip
+
+*Tags*: 
+
+* OS: Windows
+* Data Source: Elastic Endgame
+* Rule Type: Indicator Match
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and Analysis*
+
+
+
+*Investigating Threat Intel Windows Registry Indicator Match*
+
+
+Threat Intel indicator match rules allow matching from a local observation, such as an endpoint event that records a file hash with an entry of a file hash stored within the Threat Intel integrations index.
+
+Matches are based on threat intelligence data that's been ingested during the last 30 days. Some integrations don't place expiration dates on their threat indicators, so we strongly recommend validating ingested threat indicators and reviewing match results. When reviewing match results, check associated activity to determine whether the event requires additional investigation.
+
+This rule is triggered when a Windows registry indicator from the Threat Intel Filebeat module or a threat intelligence integration matches against an event that contains registry data.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Check related threat reports to gain context about the registry indicator of compromise (IoC) and to understand if it's a system-native mechanism abused for persistence, to store data, to disable security mechanisms, etc. Use this information to define the appropriate triage and respond steps.
+- Identify the process responsible for the registry operation and investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Retrieve the involved process executable and examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+- Using the data collected through the analysis, scope users targeted and other machines infected in the environment.
+
+
+*False Positive Analysis*
+
+
+- Adversaries can leverage dual-use registry mechanisms that are commonly used by normal applications. These registry keys can be added into indicator lists creating the potential for false positives.
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule needs threat intelligence indicators to work.
+Threat intelligence indicators can be collected using an https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#agent-ti-integration[Elastic Agent integration],
+the https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#ti-mod-integration[Threat Intel module],
+or a https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#custom-ti-integration[custom integration].
+
+More information can be found https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html[here].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+registry.path:*
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/timestomping-using-touch-command.asciidoc b/docs/detections/prebuilt-rules/rule-details/timestomping-using-touch-command.asciidoc
index 51d0a3532f..975ab0867c 100644
--- a/docs/detections/prebuilt-rules/rule-details/timestomping-using-touch-command.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/timestomping-using-touch-command.asciidoc
@@ -5,7 +5,7 @@ Timestomping is an anti-forensics technique which is used to modify the timestam
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,52 +14,59 @@ Timestomping is an anti-forensics technique which is used to modify the timestam
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 33
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* macOS
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<timestomping-using-touch-command-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 106
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "touch" and
-user.id != "0" and process.args : ("-r", "-t", "-a*","-m*") and not
-process.args : ("/usr/lib/go-*/bin/go", "/usr/lib/dracut/dracut-
-functions.sh", "/tmp/KSInstallAction.*/m/.patch/*")
+[source, js]
 ----------------------------------
+process where event.type == "start" and
+ process.name : "touch" and user.id != "0" and
+ process.args : ("-r", "-t", "-a*","-m*") and
+ not process.args : (
+   "/usr/lib/go-*/bin/go", "/usr/lib/dracut/dracut-functions.sh", "/tmp/KSInstallAction.*/m/.patch/*"
+) and not process.parent.name in ("pmlogger_daily", "pmlogger_janitor", "systemd")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -68,41 +75,10 @@ functions.sh", "/tmp/KSInstallAction.*/m/.patch/*")
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
 * Technique:
-** Name: Indicator Removal on Host
+** Name: Indicator Removal
 ** ID: T1070
 ** Reference URL: https://attack.mitre.org/techniques/T1070/
-
-[[timestomping-using-touch-command-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "touch" and process.args : ("-r", "-t", "-a*","-m*")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name == "touch" and wildcard(process.args, "-r", "-t",
-"-a*","-m*")
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Timestomp
+** ID: T1070.006
+** Reference URL: https://attack.mitre.org/techniques/T1070/006/
diff --git a/docs/detections/prebuilt-rules/rule-details/trap-signals-execution.asciidoc b/docs/detections/prebuilt-rules/rule-details/trap-signals-execution.asciidoc
new file mode 100644
index 0000000000..3c8f55dddf
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/trap-signals-execution.asciidoc
@@ -0,0 +1,71 @@
+[[trap-signals-execution]]
+=== Trap Signals Execution
+
+Identify activity related where adversaries can include a trap command which then allows programs and shells to specify commands that will be executed upon receiving interrupt signals.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started") and
+process.name == "trap" and process.args : "SIG*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: Trap
+** ID: T1546.005
+** Reference URL: https://attack.mitre.org/techniques/T1546/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-elevated-com-internet-explorer-add-on-installer.asciidoc b/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-elevated-com-internet-explorer-add-on-installer.asciidoc
index 1728d49cc3..8abadaf46e 100644
--- a/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-elevated-com-internet-explorer-add-on-installer.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-elevated-com-internet-explorer-add-on-installer.asciidoc
@@ -5,67 +5,75 @@ Identifies User Account Control (UAC) bypass attempts by abusing an elevated COM
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://swapcontext.blogspot.com/2020/11/uac-bypasses-from-comautoapprovallist.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 101 (<<uac-bypass-attempt-via-elevated-com-internet-explorer-add-on-installer-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.executable :
-"C:\\*\\AppData\\*\\Temp\\IDC*.tmp\\*.exe" and process.parent.name :
-"ieinstal.exe" and process.parent.args : "-Embedding" /* uncomment
-once in winlogbeat */ /* and not (process.code_signature.subject_name
-== "Microsoft Corporation" and process.code_signature.trusted == true)
-*/
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.executable : "C:\\*\\AppData\\*\\Temp\\IDC*.tmp\\*.exe" and
+ process.parent.name : "ieinstal.exe" and process.parent.args : "-Embedding"
+
+ /* uncomment once in winlogbeat */
+ /* and not (process.code_signature.subject_name == "Microsoft Corporation" and process.code_signature.trusted == true) */
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -77,46 +85,31 @@ once in winlogbeat */ /* and not (process.code_signature.subject_name
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[uac-bypass-attempt-via-elevated-com-internet-explorer-add-on-installer-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.executable : "C:\\*\\AppData\\*\\Temp\\IDC*.tmp\\*.exe" and
-process.parent.name : "ieinstal.exe" and process.parent.args :
-"-Embedding" /* uncomment once in winlogbeat */ /* and not
-(process.code_signature.subject_name == "Microsoft Corporation" and
-process.code_signature.trusted == true) */
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.15.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-wildcard(process.executable,
-"C:\\*\\AppData\\*\\Temp\\IDC*.tmp\\*.exe") and process.parent.name
-== "ieinstal.exe" and process.parent.args == "-Embedding" /*
-uncomment once in winlogbeat */ /* and not
-(process.code_signature.subject_name == "Microsoft Corporation" and
-process.code_signature.trusted == true) */
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Inter-Process Communication
+** ID: T1559
+** Reference URL: https://attack.mitre.org/techniques/T1559/
+* Sub-technique:
+** Name: Component Object Model
+** ID: T1559.001
+** Reference URL: https://attack.mitre.org/techniques/T1559/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-privileged-ifileoperation-com-interface.asciidoc b/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-privileged-ifileoperation-com-interface.asciidoc
index 293fc34781..d3bd8813c1 100644
--- a/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-privileged-ifileoperation-com-interface.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-privileged-ifileoperation-com-interface.asciidoc
@@ -5,70 +5,74 @@ Identifies attempts to bypass User Account Control (UAC) via DLL side-loading. A
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/hfiref0x/UACME
 * https://www.elastic.co/security-labs/exploring-windows-uac-bypasses-techniques-and-detection-strategies
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 101 (<<uac-bypass-attempt-via-privileged-ifileoperation-com-interface-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type : "change" and process.name : "dllhost.exe" and
-/* Known modules names side loaded into process running with high or
-system integrity level for UAC Bypass, update here for new modules */
-file.name : ("wow64log.dll", "comctl32.dll", "DismCore.dll",
-"OskSupport.dll", "duser.dll", "Accessibility.ni.dll") and /* has no
-impact on rule logic just to avoid OS install related FPs */ not
-file.path : ("C:\\Windows\\SoftwareDistribution\\*",
-"C:\\Windows\\WinSxS\\*")
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type : "change" and process.name : "dllhost.exe" and
+  /* Known modules names side loaded into process running with high or system integrity level for UAC Bypass, update here for new modules */
+  file.name : ("wow64log.dll", "comctl32.dll", "DismCore.dll", "OskSupport.dll", "duser.dll", "Accessibility.ni.dll") and
+  /* has no impact on rule logic just to avoid OS install related FPs */
+  not file.path : ("C:\\Windows\\SoftwareDistribution\\*", "C:\\Windows\\WinSxS\\*")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,28 +84,27 @@ file.path : ("C:\\Windows\\SoftwareDistribution\\*",
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[uac-bypass-attempt-via-privileged-ifileoperation-com-interface-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.15.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: DLL Side-Loading
+** ID: T1574.002
+** Reference URL: https://attack.mitre.org/techniques/T1574/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-windows-directory-masquerading.asciidoc b/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-windows-directory-masquerading.asciidoc
index 20dd3107b5..78e817415f 100644
--- a/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-windows-directory-masquerading.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-via-windows-directory-masquerading.asciidoc
@@ -5,97 +5,100 @@ Identifies an attempt to bypass User Account Control (UAC) by masquerading as a
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://medium.com/tenable-techblog/uac-bypass-by-mocking-trusted-directories-24a96675f6e
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Investigation Guide
-
-*Version*: 102 (<<uac-bypass-attempt-via-windows-directory-masquerading-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 112
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating UAC Bypass Attempt via Windows Directory Masquerading
+*Triage and analysis*
+
 
-Windows User Account Control (UAC) allows a program to elevate its privileges (tracked as low to high integrity levels)
-to perform a task under administrator-level permissions, possibly by prompting the user for confirmation.
-UAC can deny an operation under high-integrity enforcement, or allow the user to perform the action if they are in the
-local administrators group and enter an administrator password when prompted.
 
-For more information about the UAC and how it works, check the [official Microsoft docs page](https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/how-user-account-control-works).
+*Investigating UAC Bypass Attempt via Windows Directory Masquerading*
 
-This rule identifies an attempt to bypass User Account Control (UAC) by masquerading as a Microsoft trusted Windows
-directory. Attackers may bypass UAC to stealthily execute code with elevated permissions.
+
+Windows User Account Control (UAC) allows a program to elevate its privileges (tracked as low to high integrity levels) to perform a task under administrator-level permissions, possibly by prompting the user for confirmation. UAC can deny an operation under high-integrity enforcement, or allow the user to perform the action if they are in the local administrators group and enter an administrator password when prompted.
+
+For more information about the UAC and how it works, check the https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/how-user-account-control-works[official Microsoft docs page].
+
+This rule identifies an attempt to bypass User Account Control (UAC) by masquerading as a Microsoft trusted Windows directory. Attackers may bypass UAC to stealthily execute code with elevated permissions.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Inspect the host for suspicious or abnormal behavior in the alert timeframe.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze any suspicious spawned processes using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -103,30 +106,37 @@ and any spawned child processes.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.args : ("C:\\Windows
-\\system32\\*.exe", "C:\\Windows \\SysWOW64\\*.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.args : ("C:\\Windows \\system32\\*.exe", "C:\\Windows \\SysWOW64\\*.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -138,35 +148,27 @@ process where event.type == "start" and process.args : ("C:\\Windows
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[uac-bypass-attempt-via-windows-directory-masquerading-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.args : ("C:\\Windows \\system32\\*.exe", "C:\\Windows
-\\SysWOW64\\*.exe")
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.15.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-with-ieditionupgrademanager-elevated-com-interface.asciidoc b/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-with-ieditionupgrademanager-elevated-com-interface.asciidoc
index f3fa20fe92..b14e3ec173 100644
--- a/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-with-ieditionupgrademanager-elevated-com-interface.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/uac-bypass-attempt-with-ieditionupgrademanager-elevated-com-interface.asciidoc
@@ -5,66 +5,73 @@ Identifies attempts to bypass User Account Control (UAC) by abusing an elevated
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/hfiref0x/UACME
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 101 (<<uac-bypass-attempt-with-ieditionupgrademanager-elevated-com-interface-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "Clipup.exe"
-and not process.executable : "C:\\Windows\\System32\\ClipUp.exe" and
-process.parent.name : "dllhost.exe" and /* CLSID of the Elevated COM
-Interface IEditionUpgradeManager */ process.parent.args :
-"/Processid:{BD54C901-076B-434E-B6C7-17C531F4AB41}"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.name : "Clipup.exe" and
+  not process.executable : "C:\\Windows\\System32\\ClipUp.exe" and process.parent.name : "dllhost.exe" and
+  /* CLSID of the Elevated COM Interface IEditionUpgradeManager */
+  process.parent.args : "/Processid:{BD54C901-076B-434E-B6C7-17C531F4AB41}"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,45 +83,31 @@ Interface IEditionUpgradeManager */ process.parent.args :
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[uac-bypass-attempt-with-ieditionupgrademanager-elevated-com-interface-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "Clipup.exe" and not process.executable :
-"C:\\Windows\\System32\\ClipUp.exe" and process.parent.name :
-"dllhost.exe" and /* CLSID of the Elevated COM Interface
-IEditionUpgradeManager */ process.parent.args :
-"/Processid:{BD54C901-076B-434E-B6C7-17C531F4AB41}"
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.15.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started", "info") and
-process.name == "Clipup.exe" and process.executable !=
-"C:\\Windows\\System32\\ClipUp.exe" and process.parent.name ==
-"dllhost.exe" and /* CLSID of the Elevated COM Interface
-IEditionUpgradeManager */ wildcard(process.parent.args,"/Processid:{B
-D54C901-076B-434E-B6C7-17C531F4AB41}")
-----------------------------------
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Inter-Process Communication
+** ID: T1559
+** Reference URL: https://attack.mitre.org/techniques/T1559/
+* Sub-technique:
+** Name: Component Object Model
+** ID: T1559.001
+** Reference URL: https://attack.mitre.org/techniques/T1559/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-diskcleanup-scheduled-task-hijack.asciidoc b/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-diskcleanup-scheduled-task-hijack.asciidoc
index e06e211ee8..4c6850a1f6 100644
--- a/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-diskcleanup-scheduled-task-hijack.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-diskcleanup-scheduled-task-hijack.asciidoc
@@ -5,62 +5,72 @@ Identifies User Account Control (UAC) bypass via hijacking DiskCleanup Scheduled
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<uac-bypass-via-diskcleanup-scheduled-task-hijack-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.args : "/autoclean"
-and process.args : "/d" and not process.executable :
-("C:\\Windows\\System32\\cleanmgr.exe",
-"C:\\Windows\\SysWOW64\\cleanmgr.exe",
-"C:\\Windows\\System32\\taskhostw.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.args : "/autoclean" and process.args : "/d" and process.executable != null and 
+ not process.executable : ("C:\\Windows\\System32\\cleanmgr.exe",
+                           "C:\\Windows\\SysWOW64\\cleanmgr.exe",
+                           "C:\\Windows\\System32\\taskhostw.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,48 +82,31 @@ and process.args : "/d" and not process.executable :
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[uac-bypass-via-diskcleanup-scheduled-task-hijack-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (7.15.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.args:"/autoclean" and process.args:"/d" and not
-process.executable : ("C:\\Windows\\System32\\cleanmgr.exe",
-"C:\\Windows\\SysWOW64\\cleanmgr.exe")
-----------------------------------
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.args:(/autoclean or /AUTOCLEAN) and
-process.parent.name:svchost.exe and not
-process.executable:("C:\Windows\System32\cleanmgr.exe" or
-"C:\Windows\SysWOW64\cleanmgr.exe")
-----------------------------------
-
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Scheduled Task/Job
+** ID: T1053
+** Reference URL: https://attack.mitre.org/techniques/T1053/
+* Sub-technique:
+** Name: Scheduled Task
+** ID: T1053.005
+** Reference URL: https://attack.mitre.org/techniques/T1053/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-icmluautil-elevated-com-interface.asciidoc b/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-icmluautil-elevated-com-interface.asciidoc
index 2c9bec1c90..b4aa4f6f1b 100644
--- a/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-icmluautil-elevated-com-interface.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-icmluautil-elevated-com-interface.asciidoc
@@ -5,62 +5,71 @@ Identifies User Account Control (UAC) bypass attempts via the ICMLuaUtil Elevate
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 101 (<<uac-bypass-via-icmluautil-elevated-com-interface-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name ==
-"dllhost.exe" and process.parent.args in
-("/Processid:{3E5FC7F9-9A51-4367-9063-A120244FBEC7}",
-"/Processid:{D2E7041B-2927-42FB-8E9F-7CE93B6DC937}") and
-process.pe.original_file_name != "WerFault.exe"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.parent.name == "dllhost.exe" and
+ process.parent.args in ("/Processid:{3E5FC7F9-9A51-4367-9063-A120244FBEC7}", "/Processid:{D2E7041B-2927-42FB-8E9F-7CE93B6DC937}") and
+ process.pe.original_file_name != "WerFault.exe"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,34 +81,31 @@ process.pe.original_file_name != "WerFault.exe"
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[uac-bypass-via-icmluautil-elevated-com-interface-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name == "dllhost.exe" and process.parent.args in
-("/Processid:{3E5FC7F9-9A51-4367-9063-A120244FBEC7}",
-"/Processid:{D2E7041B-2927-42FB-8E9F-7CE93B6DC937}") and
-process.pe.original_file_name != "WerFault.exe"
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.15.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Inter-Process Communication
+** ID: T1559
+** Reference URL: https://attack.mitre.org/techniques/T1559/
+* Sub-technique:
+** Name: Component Object Model
+** ID: T1559.001
+** Reference URL: https://attack.mitre.org/techniques/T1559/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-windows-firewall-snap-in-hijack.asciidoc b/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-windows-firewall-snap-in-hijack.asciidoc
index 9fca862dd4..eef22f61fd 100644
--- a/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-windows-firewall-snap-in-hijack.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/uac-bypass-via-windows-firewall-snap-in-hijack.asciidoc
@@ -5,97 +5,100 @@ Identifies attempts to bypass User Account Control (UAC) by hijacking the Micros
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/AzAgarampur/byeintegrity-uac
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Investigation Guide
-
-*Version*: 102 (<<uac-bypass-via-windows-firewall-snap-in-hijack-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating UAC Bypass via Windows Firewall Snap-In Hijack
+*Triage and analysis*
+
 
-Windows User Account Control (UAC) allows a program to elevate its privileges (tracked as low to high integrity levels)
-to perform a task under administrator-level permissions, possibly by prompting the user for confirmation.
-UAC can deny an operation under high-integrity enforcement, or allow the user to perform the action if they are in the
-local administrators group and enter an administrator password when prompted.
 
-For more information about the UAC and how it works, check the [official Microsoft docs page](https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/how-user-account-control-works).
+*Investigating UAC Bypass via Windows Firewall Snap-In Hijack*
 
-This rule identifies attempts to bypass User Account Control (UAC) by hijacking the Microsoft Management Console (MMC)
-Windows Firewall snap-in. Attackers bypass UAC to stealthily execute code with elevated permissions.
+
+Windows User Account Control (UAC) allows a program to elevate its privileges (tracked as low to high integrity levels) to perform a task under administrator-level permissions, possibly by prompting the user for confirmation. UAC can deny an operation under high-integrity enforcement, or allow the user to perform the action if they are in the local administrators group and enter an administrator password when prompted.
+
+For more information about the UAC and how it works, check the https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/how-user-account-control-works[official Microsoft docs page].
+
+This rule identifies attempts to bypass User Account Control (UAC) by hijacking the Microsoft Management Console (MMC) Windows Firewall snap-in. Attackers bypass UAC to stealthily execute code with elevated permissions.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Inspect the host for suspicious or abnormal behavior in the alert timeframe.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze any suspicious spawned processes using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -103,33 +106,40 @@ and any spawned child processes.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name ==
-"mmc.exe" and /* process.Ext.token.integrity_level_name == "high" can
-be added in future for tuning */ /* args of the Windows Firewall
-SnapIn */ process.parent.args == "WF.msc" and process.name !=
-"WerFault.exe"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.parent.name == "mmc.exe" and
+ /* process.Ext.token.integrity_level_name == "high" can be added in future for tuning */
+ /* args of the Windows Firewall SnapIn */
+  process.parent.args == "WF.msc" and process.name != "WerFault.exe"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -141,37 +151,27 @@ SnapIn */ process.parent.args == "WF.msc" and process.name !=
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[uac-bypass-via-windows-firewall-snap-in-hijack-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name == "mmc.exe" and /*
-process.Ext.token.integrity_level_name == "high" can be added in
-future for tuning */ /* args of the Windows Firewall SnapIn */
-process.parent.args == "WF.msc" and process.name != "WerFault.exe"
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.15.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Abuse Elevation Control Mechanism
+** ID: T1548
+** Reference URL: https://attack.mitre.org/techniques/T1548/
+* Sub-technique:
+** Name: Bypass User Account Control
+** ID: T1548.002
+** Reference URL: https://attack.mitre.org/techniques/T1548/002/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: MMC
+** ID: T1218.014
+** Reference URL: https://attack.mitre.org/techniques/T1218/014/
diff --git a/docs/detections/prebuilt-rules/rule-details/uid-elevation-from-previously-unknown-executable.asciidoc b/docs/detections/prebuilt-rules/rule-details/uid-elevation-from-previously-unknown-executable.asciidoc
new file mode 100644
index 0000000000..860e0cfabd
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/uid-elevation-from-previously-unknown-executable.asciidoc
@@ -0,0 +1,121 @@
+[[uid-elevation-from-previously-unknown-executable]]
+=== UID Elevation from Previously Unknown Executable
+
+Monitors for the elevation of regular user permissions to root permissions through a previously unknown executable. Attackers may attempt to evade detection by hijacking the execution flow and hooking certain functions/syscalls through a rootkit in order to provide easy access to root via a special modified command.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
+the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click Add integrations.
+- In the query bar, search for Elastic Defend and select the integration to see more details about it.
+- Click Add Elastic Defend.
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either Traditional Endpoints or Cloud Workloads.
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in New agent policy name. If other agent policies already exist, you can click the Existing hosts tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click Save and Continue.
+- To complete the integration, select Add Elastic Agent to your hosts and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:"linux" and event.category:"process" and event.action:"uid_change" and event.type:"change" and user.id:"0"
+and process.parent.name:("bash" or "dash" or "sh" or "tcsh" or "csh" or "zsh" or "ksh" or "fish") and not (
+  process.executable:(
+    /bin/* or /usr/bin/* or /sbin/* or /usr/sbin/* or /snap/* or /tmp/newroot/* or /var/lib/docker/* or /usr/local/*
+  ) or
+  process.name:(
+    "bash" or "dash" or "sh" or "tcsh" or "csh" or "zsh" or "ksh" or "fish" or "sudo" or "su" or "apt" or "apt-get" or
+    "aptitude" or "squid" or "snap" or "fusermount" or "pkexec" or "umount" or "master" or "omsbaseline" or "dzdo" or
+    "sandfly" or "logrotate"
+  ) or
+  process.args:/usr/bin/python*
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: KernelCallbackTable
+** ID: T1574.013
+** Reference URL: https://attack.mitre.org/techniques/T1574/013/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Rootkit
+** ID: T1014
+** Reference URL: https://attack.mitre.org/techniques/T1014/
diff --git a/docs/detections/prebuilt-rules/rule-details/unauthorized-access-to-an-okta-application.asciidoc b/docs/detections/prebuilt-rules/rule-details/unauthorized-access-to-an-okta-application.asciidoc
index 4b3d4248e0..7d4b2ff7ee 100644
--- a/docs/detections/prebuilt-rules/rule-details/unauthorized-access-to-an-okta-application.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unauthorized-access-to-an-okta-application.asciidoc
@@ -5,7 +5,7 @@ Identifies unauthorized access attempts to Okta applications.
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-okta*
@@ -14,56 +14,52 @@ Identifies unauthorized access attempts to Okta applications.
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://developer.okta.com/docs/reference/api/system-log/
 * https://developer.okta.com/docs/reference/api/event-types/
 * https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Identity
-* Okta
-* Continuous Monitoring
-* SecOps
-* Identity and Access
-
-*Version*: 102 (<<unauthorized-access-to-an-okta-application-history, version history>>)
+* Tactic: Initial Access
+* Use Case: Identity and Access Audit
+* Data Source: Okta
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 206
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:okta.system and
-event.action:app.generic.unauth_app_access_attempt
+[source, js]
 ----------------------------------
+event.dataset:okta.system and event.action:app.generic.unauth_app_access_attempt
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,37 +71,15 @@ event.action:app.generic.unauth_app_access_attempt
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
-
-
 * Tactic:
 ** Name: Persistence
 ** ID: TA0003
 ** Reference URL: https://attack.mitre.org/tactics/TA0003/
-
-
 * Tactic:
 ** Name: Privilege Escalation
 ** ID: TA0004
 ** Reference URL: https://attack.mitre.org/tactics/TA0004/
-
-[[unauthorized-access-to-an-okta-application-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/uncommon-registry-persistence-change.asciidoc b/docs/detections/prebuilt-rules/rule-details/uncommon-registry-persistence-change.asciidoc
index a89d48f4a4..6591ffc040 100644
--- a/docs/detections/prebuilt-rules/rule-details/uncommon-registry-persistence-change.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/uncommon-registry-persistence-change.asciidoc
@@ -5,134 +5,110 @@ Detects changes to registry persistence keys that are not commonly used or modif
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.microsoftpressstore.com/articles/article.aspx?p=2762082&seqNum=2
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-
-*Version*: 100 (<<uncommon-registry-persistence-change-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where /* uncomment once stable
-length(registry.data.strings) > 0 and */ registry.path : (
-"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Terminal Serve
-r\\Install\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Terminal Serve
-r\\Install\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Runonce\\*",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\Load",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\Run",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\IconServiceLib",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\AppSetup",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Taskman",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Userinit",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\VmApplet", "HKLM\\SOFTWARE\\Micros
-oft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\*", "HKLM
-\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Shel
-l", "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scrip
-ts\\Logoff\\Script", "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windo
-ws\\System\\Scripts\\Logon\\Script", "HKLM\\SOFTWARE\\Policies\\
-Microsoft\\Windows\\System\\Scripts\\Shutdown\\Script", "HKLM\\S
-OFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Startup\\Scrip
-t", "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion
-\\Policies\\Explorer\\Run\\*", "HKEY_USERS\\*\\SOFTWARE\\Microso
-ft\\Windows\\CurrentVersion\\Policies\\System\\Shell", "HKEY_USE
-RS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logoff
-\\Script", "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Window
-s\\System\\Scripts\\Logon\\Script", "HKEY_USERS\\*\\SOFTWARE\\Po
-licies\\Microsoft\\Windows\\System\\Scripts\\Shutdown\\Script", 
-"HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Script
-s\\Startup\\Script", "HKLM\\SOFTWARE\\Microsoft\\Active
-Setup\\Installed Components\\*\\ShellComponent",
-"HKLM\\SOFTWARE\\Microsoft\\Windows CE
-Services\\AutoStartOnConnect\\MicrosoftActiveSync",
-"HKLM\\SOFTWARE\\Microsoft\\Windows CE
-Services\\AutoStartOnDisconnect\\MicrosoftActiveSync",
-"HKLM\\SOFTWARE\\Microsoft\\Ctf\\LangBarAddin\\*\\FilePath",
-"HKLM\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Exec",
-"HKLM\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Script",
-"HKLM\\SOFTWARE\\Microsoft\\Command Processor\\Autorun",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Ctf\\LangBarAddin\\*\\FilePath",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet
-Explorer\\Extensions\\*\\Exec",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet
-Explorer\\Extensions\\*\\Script",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Command Processor\\Autorun",
-"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Image File
-Execution Options\\*\\VerifierDlls",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\GpExtensions\\*\\DllName",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\SafeBoot\\AlternateShell",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Terminal
-Server\\Wds\\rdpwd\\StartupPrograms",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Terminal
-Server\\WinStations\\RDP-Tcp\\InitialProgram",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Session Manager\\BootExecute",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Session Manager\\SetupExecute",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Session Manager\\Execute",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Session
-Manager\\S0InitialCommand",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\ServiceControlManagerExtension",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\BootVerificationProgram\\ImagePat
-h", "HKLM\\SYSTEM\\Setup\\CmdLine",
-"HKEY_USERS\\*\\Environment\\UserInitMprLogonScript") and not
-registry.data.strings : ("C:\\Windows\\system32\\userinit.exe",
-"cmd.exe", "C:\\Program Files (x86)\\*.exe",
-"C:\\Program Files\\*.exe") and not (process.name : "rundll32.exe"
-and registry.path : "*\\Software\\Microsoft\\Internet
-Explorer\\Extensions\\*\\Script") and not process.executable :
-("C:\\Windows\\System32\\msiexec.exe",
-"C:\\Windows\\SysWOW64\\msiexec.exe",
-"C:\\ProgramData\\Microsoft\\Windows
-Defender\\Platform\\*\\MsMpEng.exe",
-"C:\\Program Files\\*.exe", "C:\\Program
-Files (x86)\\*.exe")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type in ("creation", "change") and
+ length(registry.data.strings) > 0 and
+ registry.path : (
+      "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Terminal Server\\Install\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Terminal Server\\Install\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Runonce\\*",
+      "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Windows\\Load",
+      "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Windows\\Run",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Windows\\IconServiceLib",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Shell",
+      "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Shell",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\AppSetup",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Taskman",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\Userinit",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\VmApplet",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\*",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Shell",
+      "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logoff\\Script",
+      "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logon\\Script",
+      "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Shutdown\\Script",
+      "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Startup\\Script",
+      "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\*",
+      "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Shell",
+      "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logoff\\Script",
+      "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logon\\Script",
+      "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Shutdown\\Script",
+      "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Startup\\Script",
+      "HKLM\\SOFTWARE\\Microsoft\\Active Setup\\Installed Components\\*\\ShellComponent",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows CE Services\\AutoStartOnConnect\\MicrosoftActiveSync",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows CE Services\\AutoStartOnDisconnect\\MicrosoftActiveSync",
+      "HKLM\\SOFTWARE\\Microsoft\\Ctf\\LangBarAddin\\*\\FilePath",
+      "HKLM\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Exec",
+      "HKLM\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Script",
+      "HKLM\\SOFTWARE\\Microsoft\\Command Processor\\Autorun",
+      "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Ctf\\LangBarAddin\\*\\FilePath",
+      "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Exec",
+      "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Script",
+      "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Command Processor\\Autorun",
+      "HKEY_USERS\\*\\Control Panel\\Desktop\\scrnsave.exe",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Image File Execution Options\\*\\VerifierDlls",
+      "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\GpExtensions\\*\\DllName",
+      "HKLM\\SYSTEM\\ControlSet*\\Control\\SafeBoot\\AlternateShell",
+      "HKLM\\SYSTEM\\ControlSet*\\Control\\Terminal Server\\Wds\\rdpwd\\StartupPrograms",
+      "HKLM\\SYSTEM\\ControlSet*\\Control\\Terminal Server\\WinStations\\RDP-Tcp\\InitialProgram",
+      "HKLM\\SYSTEM\\ControlSet*\\Control\\Session Manager\\BootExecute",
+      "HKLM\\SYSTEM\\ControlSet*\\Control\\Session Manager\\SetupExecute",
+      "HKLM\\SYSTEM\\ControlSet*\\Control\\Session Manager\\Execute",
+      "HKLM\\SYSTEM\\ControlSet*\\Control\\Session Manager\\S0InitialCommand",
+      "HKLM\\SYSTEM\\ControlSet*\\Control\\ServiceControlManagerExtension",
+      "HKLM\\SYSTEM\\ControlSet*\\Control\\BootVerificationProgram\\ImagePath",
+      "HKLM\\SYSTEM\\Setup\\CmdLine",
+      "HKEY_USERS\\*\\Environment\\UserInitMprLogonScript") and
+
+ not registry.data.strings : ("C:\\Windows\\system32\\userinit.exe", "cmd.exe", "C:\\Program Files (x86)\\*.exe",
+                              "C:\\Program Files\\*.exe") and
+ not (process.name : "rundll32.exe" and registry.path : "*\\Software\\Microsoft\\Internet Explorer\\Extensions\\*\\Script") and
+ not process.executable : ("C:\\Windows\\System32\\msiexec.exe",
+                           "C:\\Windows\\SysWOW64\\msiexec.exe",
+                           "C:\\ProgramData\\Microsoft\\Windows Defender\\Platform\\*\\MsMpEng.exe",
+                           "C:\\Program Files\\*.exe",
+                           "C:\\Program Files (x86)\\*.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -144,8 +120,18 @@ Files (x86)\\*.exe")
 ** Name: Boot or Logon Autostart Execution
 ** ID: T1547
 ** Reference URL: https://attack.mitre.org/techniques/T1547/
-
-
+* Sub-technique:
+** Name: Registry Run Keys / Startup Folder
+** ID: T1547.001
+** Reference URL: https://attack.mitre.org/techniques/T1547/001/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Sub-technique:
+** Name: Screensaver
+** ID: T1546.002
+** Reference URL: https://attack.mitre.org/techniques/T1546/002/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -154,119 +140,3 @@ Files (x86)\\*.exe")
 ** Name: Modify Registry
 ** ID: T1112
 ** Reference URL: https://attack.mitre.org/techniques/T1112/
-
-[[uncommon-registry-persistence-change-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where /* uncomment once stable
-length(registry.data.strings) > 0 and */ registry.path : (
-"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Terminal Serve
-r\\Install\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Run\\*",
-"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Terminal Serve
-r\\Install\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Runonce\\*",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\Load",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\Run",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Windows\\IconServiceLib",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Shell",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\AppSetup",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Taskman",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\Userinit",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\VmApplet", "HKLM\\SOFTWARE\\Micros
-oft\\Windows\\CurrentVersion\\Policies\\Explorer\\Run\\*", "HKLM
-\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Shel
-l", "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scrip
-ts\\Logoff\\Script", "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windo
-ws\\System\\Scripts\\Logon\\Script", "HKLM\\SOFTWARE\\Policies\\
-Microsoft\\Windows\\System\\Scripts\\Shutdown\\Script", "HKLM\\S
-OFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Startup\\Scrip
-t", "HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion
-\\Policies\\Explorer\\Run\\*", "HKEY_USERS\\*\\SOFTWARE\\Microso
-ft\\Windows\\CurrentVersion\\Policies\\System\\Shell", "HKEY_USE
-RS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Scripts\\Logoff
-\\Script", "HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Window
-s\\System\\Scripts\\Logon\\Script", "HKEY_USERS\\*\\SOFTWARE\\Po
-licies\\Microsoft\\Windows\\System\\Scripts\\Shutdown\\Script", 
-"HKEY_USERS\\*\\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\Script
-s\\Startup\\Script", "HKLM\\SOFTWARE\\Microsoft\\Active
-Setup\\Installed Components\\*\\ShellComponent",
-"HKLM\\SOFTWARE\\Microsoft\\Windows CE
-Services\\AutoStartOnConnect\\MicrosoftActiveSync",
-"HKLM\\SOFTWARE\\Microsoft\\Windows CE
-Services\\AutoStartOnDisconnect\\MicrosoftActiveSync",
-"HKLM\\SOFTWARE\\Microsoft\\Ctf\\LangBarAddin\\*\\FilePath",
-"HKLM\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Exec",
-"HKLM\\SOFTWARE\\Microsoft\\Internet Explorer\\Extensions\\*\\Script",
-"HKLM\\SOFTWARE\\Microsoft\\Command Processor\\Autorun",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Ctf\\LangBarAddin\\*\\FilePath",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet
-Explorer\\Extensions\\*\\Exec",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Internet
-Explorer\\Extensions\\*\\Script",
-"HKEY_USERS\\*\\SOFTWARE\\Microsoft\\Command Processor\\Autorun",
-"HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Image File
-Execution Options\\*\\VerifierDlls",
-"HKLM\\SOFTWARE\\Microsoft\\Windows
-NT\\CurrentVersion\\Winlogon\\GpExtensions\\*\\DllName",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\SafeBoot\\AlternateShell",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Terminal
-Server\\Wds\\rdpwd\\StartupPrograms",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Terminal
-Server\\WinStations\\RDP-Tcp\\InitialProgram",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Session Manager\\BootExecute",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Session Manager\\SetupExecute",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Session Manager\\Execute",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\Session
-Manager\\S0InitialCommand",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\ServiceControlManagerExtension",
-"HKLM\\SYSTEM\\ControlSet*\\Control\\BootVerificationProgram\\ImagePat
-h", "HKLM\\SYSTEM\\Setup\\CmdLine",
-"HKEY_USERS\\*\\Environment\\UserInitMprLogonScript") and not
-registry.data.strings : ("C:\\Windows\\system32\\userinit.exe",
-"cmd.exe", "C:\\Program Files (x86)\\*.exe",
-"C:\\Program Files\\*.exe") and not (process.name : "rundll32.exe"
-and registry.path : "*\\Software\\Microsoft\\Internet
-Explorer\\Extensions\\*\\Script") and not process.executable :
-("C:\\Windows\\System32\\msiexec.exe",
-"C:\\Windows\\SysWOW64\\msiexec.exe",
-"C:\\ProgramData\\Microsoft\\Windows
-Defender\\Platform\\*\\MsMpEng.exe",
-"C:\\Program Files\\*.exe", "C:\\Program
-Files (x86)\\*.exe")
-----------------------------------
-
-Version 10 (8.4.0 release)::
-* Formatting only
-
-Version 9 (8.3.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.16.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unexpected-child-process-of-macos-screensaver-engine.asciidoc b/docs/detections/prebuilt-rules/rule-details/unexpected-child-process-of-macos-screensaver-engine.asciidoc
index 0ca5c69b97..4bdc872bb4 100644
--- a/docs/detections/prebuilt-rules/rule-details/unexpected-child-process-of-macos-screensaver-engine.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unexpected-child-process-of-macos-screensaver-engine.asciidoc
@@ -5,68 +5,100 @@ Identifies when a child process is spawned by the screensaver engine process, wh
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://posts.specterops.io/saving-your-access-d562bf5bf90b
 * https://github.com/D00MFist/PersistentJXA
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* macOS
-* Threat Detection
-* Persistence
-
-*Version*: 100 (<<unexpected-child-process-of-macos-screensaver-engine-history, version history>>)
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+
+*Triage and analysis*
+
 
 - Analyze the descendant processes of the ScreenSaverEngine process for malicious code and suspicious behavior such
 as a download of a payload from a server.
 - Review the installed and activated screensaver on the host. Triage the screensaver (.saver) file that was triggered to
 identify whether the file is malicious or not.
-----------------------------------
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name ==
-"ScreenSaverEngine"
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type == "start" and process.parent.name == "ScreenSaverEngine"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,19 +110,7 @@ process where event.type == "start" and process.parent.name ==
 ** Name: Event Triggered Execution
 ** ID: T1546
 ** Reference URL: https://attack.mitre.org/techniques/T1546/
-
-[[unexpected-child-process-of-macos-screensaver-engine-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Screensaver
+** ID: T1546.002
+** Reference URL: https://attack.mitre.org/techniques/T1546/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/unix-socket-connection.asciidoc b/docs/detections/prebuilt-rules/rule-details/unix-socket-connection.asciidoc
new file mode 100644
index 0000000000..2c2410219f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unix-socket-connection.asciidoc
@@ -0,0 +1,71 @@
+[[unix-socket-connection]]
+=== Unix Socket Connection
+
+This rule monitors for inter-process communication via Unix sockets. Adversaries may attempt to communicate with local Unix sockets to enumerate application details, find vulnerabilities/configuration mistakes and potentially escalate privileges or set up malicious communication channels via Unix sockets for inter-process communication to attempt to evade detection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+* endgame-*
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Rule Type: BBR
+* Data Source: Elastic Endgame
+* Data Source: Auditd Manager
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
+ and (
+  (process.name in ("nc", "ncat", "netcat", "nc.openbsd") and 
+   process.args == "-U" and process.args : ("/usr/local/*", "/run/*", "/var/run/*")) or
+  (process.name == "socat" and 
+   process.args == "-" and process.args : ("UNIX-CLIENT:/usr/local/*", "UNIX-CLIENT:/run/*", "UNIX-CLIENT:/var/run/*"))
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Inter-Process Communication
+** ID: T1559
+** Reference URL: https://attack.mitre.org/techniques/T1559/
diff --git a/docs/detections/prebuilt-rules/rule-details/unknown-execution-of-binary-with-rwx-memory-region.asciidoc b/docs/detections/prebuilt-rules/rule-details/unknown-execution-of-binary-with-rwx-memory-region.asciidoc
new file mode 100644
index 0000000000..fca9dc59ee
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unknown-execution-of-binary-with-rwx-memory-region.asciidoc
@@ -0,0 +1,89 @@
+[[unknown-execution-of-binary-with-rwx-memory-region]]
+=== Unknown Execution of Binary with RWX Memory Region
+
+Monitors for the execution of a previously unknown unix binary with read, write and execute memory region permissions. The mprotect() system call is used to change the access protections on a region of memory that has already been allocated. This syscall allows a process to modify the permissions of pages in its virtual address space, enabling or disabling permissions such as read, write, and execute for those pages. RWX permissions on memory is in many cases overly permissive, and should be analyzed thoroughly.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* auditbeat-*
+* logs-auditd_manager.auditd-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://man7.org/linux/man-pages/man2/mprotect.2.html
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Auditd Manager
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires the use of the `auditd_manager` integration. `Auditd_manager` is a tool designed to simplify and enhance the management of the audit subsystem in Linux systems. It provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system. The following steps should be executed in order to install and deploy `auditd_manager` on a Linux system.
+```
+Kibana -->
+Management -->
+Integrations -->
+Auditd Manager -->
+Add Auditd Manager
+```
+`Auditd_manager` subscribes to the kernel and receives events as they occur without any additional configuration. However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
+For this detection rule to trigger, the following additional audit rules are required to be added to the integration:
+```
+-a always,exit -F arch=b64 -S mprotect
+```
+Add the newly installed `auditd manager` to an agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.category:process and host.os.type:linux and auditd.data.syscall:mprotect and auditd.data.a2:7
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Unix Shell
+** ID: T1059.004
+** Reference URL: https://attack.mitre.org/techniques/T1059/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/unsigned-bits-service-client-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/unsigned-bits-service-client-process.asciidoc
new file mode 100644
index 0000000000..d003a3224a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unsigned-bits-service-client-process.asciidoc
@@ -0,0 +1,73 @@
+[[unsigned-bits-service-client-process]]
+=== Unsigned BITS Service Client Process
+
+Identifies an unsigned Windows Background Intelligent Transfer Service (BITS) client process. Attackers may abuse BITS functionality to download or upload data using the BITS service.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://web.archive.org/web/20230531215706/https://blog.menasec.net/2021/05/hunting-for-suspicious-usage-of.html
+* https://www.elastic.co/blog/hunting-for-persistence-using-elastic-security-part-2
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+library where dll.name : "Bitsproxy.dll" and process.executable != null and
+not process.code_signature.trusted == true and
+not process.code_signature.status : ("errorExpired", "errorCode_endpoint*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: BITS Jobs
+** ID: T1197
+** Reference URL: https://attack.mitre.org/techniques/T1197/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/unsigned-dll-loaded-by-a-trusted-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/unsigned-dll-loaded-by-a-trusted-process.asciidoc
new file mode 100644
index 0000000000..53f7680f9a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unsigned-dll-loaded-by-a-trusted-process.asciidoc
@@ -0,0 +1,112 @@
+[[unsigned-dll-loaded-by-a-trusted-process]]
+=== Unsigned DLL Loaded by a Trusted Process
+
+Identifies digitally signed (trusted) processes loading unsigned DLLs. Attackers may plant their payloads into the application folder and invoke the legitimate application to execute the payload, masking actions they perform under a legitimate, trusted, and potentially elevated system or software process.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 102
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+library where host.os.type == "windows" and
+   (dll.Ext.relative_file_creation_time <= 500 or
+    dll.Ext.relative_file_name_modify_time <= 500 or
+    dll.Ext.device.product_id : ("Virtual DVD-ROM", "Virtual Disk")) and dll.hash.sha256 != null and
+    process.code_signature.status :"trusted" and not dll.code_signature.status : ("trusted", "errorExpired", "errorCode_endpoint*") and
+    /* DLL loaded from the process.executable current directory */
+    endswith~(substring(dll.path, 0, length(dll.path) - (length(dll.name) + 1)), substring(process.executable, 0, length(process.executable) - (length(process.name) + 1)))
+    and not user.id : "S-1-5-18" and
+    not dll.hash.sha256 : (
+        "19588e6a318894abe8094374bee233e666f319de909c69f12a6047b14473e299",
+        "6e8bee250c8cc1b65150522f33794759f5c65f58fff17c5cbf6422ad68b421d2",
+        "55de11531dc0e566cb91f26e48d1301a161a4b8b24abed42304d711412368760",
+        "56a5148d00c2d9e58415be2d64eca922a58063fe26d9af1c87084aa383c9058e",
+        "83ee0ff920144edb2c2f4ea10130f55443493290886985a63233fa2431e450f9",
+        "0d0d8f2eaff6b5f75e63d9721d5a0480b30e70792fe0d3a24d76fd3e61b05982",
+        "8b6ce3a640e2d6f36b0001be2a1abb765ae51e62c314a15911e75138cbb544bb",
+        "ea02a19dd824cb7d611b8821d1b9e6a076714a195d027d1ff918128a64ac5220",
+        "02a6d001e6dd944738e09b720e49dcb1272cb782b870e5ae319d4600bc192225",
+        "e7714a1d6ac3f4c4ae22564b9ca301e486f5f42691859c0a687246c47b5cf5c9",
+        "17f0f709fb7f6190c03b19b6198fd863b6f0d79f46ccfebac6064be747a4cb3e",
+        "cb7ab3788d10940df874acd97b1821bbb5ee4a91f3eec11982bb5bf7a3c96443",
+        "c944ee510721a1d30d42227cc3061dfdcbc144c952381afcfe4f6e82c5435ffc",
+        "967189adfbc889fde89aafc867f7a1f02731f8592cf6fd5a4ace1929213e2e13",
+        "4a824526749790603eb66777f79787128dd282162a3904a4c1135de43b14d029",
+        "620a7e658af05cc848091b8a639854b9b15700a9061b4a3d078523653133a4af",
+        "cb220267fb0116b298bab6a09a764420d630c52026f7d750f8ffca4818389327",
+        "0da1f856d92d6b95f10ed8c3f629cd15468c906de9352fb4ae629139d1412eed",
+        "e1646c7778c24407a17881908037a49ecfcb5a980d155212d544302653a3ef62",
+        "e102c9c5b22ceb60dc516ab4124bea8ec8e808b08eec48ea7ac674d13fca82ef",
+        "c7544e1f9927afdf6e8cd7063020b572e60fe8f00af39227eb831d331df38225",
+        "3668c6749db59a6cbc5293d0a4f904f76d6fb5048704449dd53894916f408a57",
+        "7705851ba047a8154402aca92621b60be0e0e9d9b52b19bf8be540305bd53dba",
+        "b5acf358ff97127eac9ef4c664a980b937376b5295ef23d77ee338225de10d60",
+        "394d2d862f2ddce71f28d9b933b21a7d6c621c80ef28652574f758f77f01f716",
+        "e958d03db79e9f1d2770c70a5bc24904aa3e2d27a8d5637684cf8166b38908f2",
+        "284701380f33a30b25e8eb9822e7f47179238e91d08bd3fb5a117145de7e0d8d",
+        "497471497886f18ca16f7facab7d76dc9bfadd69deb9c6e4ea9bdc0869a15628",
+        "739bedcfc8eb860927eb2057474be5b39518aaaa6703f9f85307a432fa1f236e",
+        "8f4c72e3c7de1ab5d894ec7813f65c5298ecafc183f31924b44a427433ffca42",
+        "1ac4753056179b358132c55ca3086d550849ae30259ba94f334826c2fbf6c57e",
+        "53e8fecd7d4b1b74064eba9bfa6a361d52929f440954931b4ba65615148bf0ea",
+        "e9088afd8871dbad5eda47a9d8abf3b08dd2e17c423ba8a05f9b6ad6751f9b7c",
+        "ab27eb05130db2f92499234b69ff97ee6429c7824efcb7324ae3e404e2b405bf",
+        "553451008520a5f0110d84192cba40208fb001c27454f946e85e6fb2e6553292"
+    )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: DLL Search Order Hijacking
+** ID: T1574.001
+** Reference URL: https://attack.mitre.org/techniques/T1574/001/
+* Sub-technique:
+** Name: DLL Side-Loading
+** ID: T1574.002
+** Reference URL: https://attack.mitre.org/techniques/T1574/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/unsigned-dll-loaded-by-svchost.asciidoc b/docs/detections/prebuilt-rules/rule-details/unsigned-dll-loaded-by-svchost.asciidoc
new file mode 100644
index 0000000000..591b2665b3
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unsigned-dll-loaded-by-svchost.asciidoc
@@ -0,0 +1,179 @@
+[[unsigned-dll-loaded-by-svchost]]
+=== Unsigned DLL Loaded by Svchost
+
+Identifies an unsigned library created in the last 5 minutes and subsequently loaded by a shared windows service (svchost). Adversaries may use this technique to maintain persistence or run with System privileges.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Data Source: Elastic Defend
+
+*Version*: 6
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+library where host.os.type == "windows" and
+
+ process.executable : 
+     ("?:\\Windows\\System32\\svchost.exe", "?:\\Windows\\Syswow64\\svchost.exe") and 
+     
+ dll.code_signature.trusted != true and 
+ 
+ not dll.code_signature.status : ("trusted", "errorExpired", "errorCode_endpoint*") and 
+ 
+ dll.hash.sha256 != null and 
+ 
+ (
+       /* DLL created within 5 minutes of the library load event - compatible with Elastic Endpoint 8.4+ */
+       dll.Ext.relative_file_creation_time <= 300 or 
+   
+       /* unusual paths */
+       dll.path :("?:\\ProgramData\\*",
+                  "?:\\Users\\*",
+                  "?:\\PerfLogs\\*",
+                  "?:\\Windows\\Tasks\\*",
+                  "?:\\Intel\\*",
+                  "?:\\AMD\\Temp\\*",
+                  "?:\\Windows\\AppReadiness\\*",
+                  "?:\\Windows\\ServiceState\\*",
+                  "?:\\Windows\\security\\*",
+                  "?:\\Windows\\IdentityCRL\\*",
+                  "?:\\Windows\\Branding\\*",
+                  "?:\\Windows\\csc\\*",
+                  "?:\\Windows\\DigitalLocker\\*",
+                  "?:\\Windows\\en-US\\*",
+                  "?:\\Windows\\wlansvc\\*",
+                  "?:\\Windows\\Prefetch\\*",
+                  "?:\\Windows\\Fonts\\*",
+                  "?:\\Windows\\diagnostics\\*",
+                  "?:\\Windows\\TAPI\\*",
+                  "?:\\Windows\\INF\\*",
+                  "?:\\Windows\\System32\\Speech\\*",
+                  "?:\\windows\\tracing\\*",
+                  "?:\\windows\\IME\\*",
+                  "?:\\Windows\\Performance\\*",
+                  "?:\\windows\\intel\\*",
+                  "?:\\windows\\ms\\*",
+                  "?:\\Windows\\dot3svc\\*",
+                  "?:\\Windows\\panther\\*",
+                  "?:\\Windows\\RemotePackages\\*",
+                  "?:\\Windows\\OCR\\*",
+                  "?:\\Windows\\appcompat\\*",
+                  "?:\\Windows\\apppatch\\*",
+                  "?:\\Windows\\addins\\*",
+                  "?:\\Windows\\Setup\\*",
+                  "?:\\Windows\\Help\\*",
+                  "?:\\Windows\\SKB\\*",
+                  "?:\\Windows\\Vss\\*",
+                  "?:\\Windows\\servicing\\*",
+                  "?:\\Windows\\CbsTemp\\*",
+                  "?:\\Windows\\Logs\\*",
+                  "?:\\Windows\\WaaS\\*",
+                  "?:\\Windows\\twain_32\\*",
+                  "?:\\Windows\\ShellExperiences\\*",
+                  "?:\\Windows\\ShellComponents\\*",
+                  "?:\\Windows\\PLA\\*",
+                  "?:\\Windows\\Migration\\*",
+                  "?:\\Windows\\debug\\*",
+                  "?:\\Windows\\Cursors\\*",
+                  "?:\\Windows\\Containers\\*",
+                  "?:\\Windows\\Boot\\*",
+                  "?:\\Windows\\bcastdvr\\*",
+                  "?:\\Windows\\TextInput\\*",
+                  "?:\\Windows\\security\\*",
+                  "?:\\Windows\\schemas\\*",
+                  "?:\\Windows\\SchCache\\*",
+                  "?:\\Windows\\Resources\\*",
+                  "?:\\Windows\\rescache\\*",
+                  "?:\\Windows\\Provisioning\\*",
+                  "?:\\Windows\\PrintDialog\\*",
+                  "?:\\Windows\\PolicyDefinitions\\*",
+                  "?:\\Windows\\media\\*",
+                  "?:\\Windows\\Globalization\\*",
+                  "?:\\Windows\\L2Schemas\\*",
+                  "?:\\Windows\\LiveKernelReports\\*",
+                  "?:\\Windows\\ModemLogs\\*",
+                  "?:\\Windows\\ImmersiveControlPanel\\*",
+                  "?:\\$Recycle.Bin\\*")
+  ) and 
+  
+  not dll.hash.sha256 : 
+            ("3ed33e71641645367442e65dca6dab0d326b22b48ef9a4c2a2488e67383aa9a6", 
+             "b4db053f6032964df1b254ac44cb995ffaeb4f3ade09597670aba4f172cf65e4", 
+             "214c75f678bc596bbe667a3b520aaaf09a0e50c364a28ac738a02f867a085eba", 
+             "23aa95b637a1bf6188b386c21c4e87967ede80242327c55447a5bb70d9439244", 
+             "5050b025909e81ae5481db37beb807a80c52fc6dd30c8aa47c9f7841e2a31be7")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: System Services
+** ID: T1569
+** Reference URL: https://attack.mitre.org/techniques/T1569/
+* Sub-technique:
+** Name: Service Execution
+** ID: T1569.002
+** Reference URL: https://attack.mitre.org/techniques/T1569/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/unsigned-dll-side-loading-from-a-suspicious-folder.asciidoc b/docs/detections/prebuilt-rules/rule-details/unsigned-dll-side-loading-from-a-suspicious-folder.asciidoc
new file mode 100644
index 0000000000..269d37ee04
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unsigned-dll-side-loading-from-a-suspicious-folder.asciidoc
@@ -0,0 +1,167 @@
+[[unsigned-dll-side-loading-from-a-suspicious-folder]]
+=== Unsigned DLL Side-Loading from a Suspicious Folder
+
+Identifies a Windows trusted program running from locations often abused by adversaries to masquerade as a trusted program and loading a recently dropped DLL. This behavior may indicate an attempt to evade defenses via side-loading a malicious DLL within the memory space of a signed processes.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+library where host.os.type == "windows" and
+
+ process.code_signature.trusted == true and 
+ 
+ (dll.Ext.relative_file_creation_time <= 500 or dll.Ext.relative_file_name_modify_time <= 500) and 
+ 
+  not dll.code_signature.status : ("trusted", "errorExpired", "errorCode_endpoint*", "errorChaining") and 
+  
+      /* Suspicious Paths */
+      dll.path : ("?:\\PerfLogs\\*.dll",
+                  "?:\\Users\\*\\Pictures\\*.dll",
+                  "?:\\Users\\*\\Music\\*.dll",
+                  "?:\\Users\\Public\\*.dll",
+                  "?:\\Users\\*\\Documents\\*.dll",
+                  "?:\\Windows\\Tasks\\*.dll",
+                  "?:\\Windows\\System32\\Tasks\\*.dll",
+                  "?:\\Intel\\*.dll",
+                  "?:\\AMD\\Temp\\*.dll",
+                  "?:\\Windows\\AppReadiness\\*.dll",
+                  "?:\\Windows\\ServiceState\\*.dll",
+                  "?:\\Windows\\security\\*.dll",
+		  "?:\\Windows\\System\\*.dll",
+                  "?:\\Windows\\IdentityCRL\\*.dll",
+                  "?:\\Windows\\Branding\\*.dll",
+                  "?:\\Windows\\csc\\*.dll",
+                  "?:\\Windows\\DigitalLocker\\*.dll",
+                  "?:\\Windows\\en-US\\*.dll",
+                  "?:\\Windows\\wlansvc\\*.dll",
+                  "?:\\Windows\\Prefetch\\*.dll",
+                  "?:\\Windows\\Fonts\\*.dll",
+                  "?:\\Windows\\diagnostics\\*.dll",
+                  "?:\\Windows\\TAPI\\*.dll",
+                  "?:\\Windows\\INF\\*.dll",
+                  "?:\\windows\\tracing\\*.dll",
+                  "?:\\windows\\IME\\*.dll",
+                  "?:\\Windows\\Performance\\*.dll",
+                  "?:\\windows\\intel\\*.dll",
+                  "?:\\windows\\ms\\*.dll",
+                  "?:\\Windows\\dot3svc\\*.dll",
+                  "?:\\Windows\\ServiceProfiles\\*.dll",
+                  "?:\\Windows\\panther\\*.dll",
+                  "?:\\Windows\\RemotePackages\\*.dll",
+                  "?:\\Windows\\OCR\\*.dll",
+                  "?:\\Windows\\appcompat\\*.dll",
+                  "?:\\Windows\\apppatch\\*.dll",
+                  "?:\\Windows\\addins\\*.dll",
+                  "?:\\Windows\\Setup\\*.dll",
+                  "?:\\Windows\\Help\\*.dll",
+                  "?:\\Windows\\SKB\\*.dll",
+                  "?:\\Windows\\Vss\\*.dll",
+                  "?:\\Windows\\Web\\*.dll",
+                  "?:\\Windows\\servicing\\*.dll",
+                  "?:\\Windows\\CbsTemp\\*.dll",
+                  "?:\\Windows\\Logs\\*.dll",
+                  "?:\\Windows\\WaaS\\*.dll",
+                  "?:\\Windows\\twain_32\\*.dll",
+                  "?:\\Windows\\ShellExperiences\\*.dll",
+                  "?:\\Windows\\ShellComponents\\*.dll",
+                  "?:\\Windows\\PLA\\*.dll",
+                  "?:\\Windows\\Migration\\*.dll",
+                  "?:\\Windows\\debug\\*.dll",
+                  "?:\\Windows\\Cursors\\*.dll",
+                  "?:\\Windows\\Containers\\*.dll",
+                  "?:\\Windows\\Boot\\*.dll",
+                  "?:\\Windows\\bcastdvr\\*.dll",
+                  "?:\\Windows\\TextInput\\*.dll",
+                  "?:\\Windows\\schemas\\*.dll",
+                  "?:\\Windows\\SchCache\\*.dll",
+                  "?:\\Windows\\Resources\\*.dll",
+                  "?:\\Windows\\rescache\\*.dll",
+                  "?:\\Windows\\Provisioning\\*.dll",
+                  "?:\\Windows\\PrintDialog\\*.dll",
+                  "?:\\Windows\\PolicyDefinitions\\*.dll",
+                  "?:\\Windows\\media\\*.dll",
+                  "?:\\Windows\\Globalization\\*.dll",
+                  "?:\\Windows\\L2Schemas\\*.dll",
+                  "?:\\Windows\\LiveKernelReports\\*.dll",
+                  "?:\\Windows\\ModemLogs\\*.dll",
+                  "?:\\Windows\\ImmersiveControlPanel\\*.dll",
+                  "?:\\$Recycle.Bin\\*.dll") and 
+	 
+	 /* DLL loaded from the process.executable current directory */
+	 endswith~(substring(dll.path, 0, length(dll.path) - (length(dll.name) + 1)), substring(process.executable, 0, length(process.executable) - (length(process.name) + 1)))
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
+* Technique:
+** Name: Hijack Execution Flow
+** ID: T1574
+** Reference URL: https://attack.mitre.org/techniques/T1574/
+* Sub-technique:
+** Name: DLL Side-Loading
+** ID: T1574.002
+** Reference URL: https://attack.mitre.org/techniques/T1574/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/untrusted-driver-loaded.asciidoc b/docs/detections/prebuilt-rules/rule-details/untrusted-driver-loaded.asciidoc
new file mode 100644
index 0000000000..004c4a4e1d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/untrusted-driver-loaded.asciidoc
@@ -0,0 +1,144 @@
+[[untrusted-driver-loaded]]
+=== Untrusted Driver Loaded
+
+Identifies attempt to load an untrusted driver. Adversaries may modify code signing policies to enable execution of unsigned or self-signed code.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://github.com/hfiref0x/TDL
+* https://docs.microsoft.com/en-us/previous-versions/windows/hardware/design/dn653559(v=vs.85)?redirectedfrom=MSDN
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+
+*Version*: 8
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Untrusted Driver Loaded*
+
+
+Microsoft created the Windows Driver Signature Enforcement (DSE) security feature to prevent drivers with invalid signatures from loading and executing into the kernel (ring 0). DSE aims to protect systems by blocking attackers from loading malicious drivers on targets. 
+
+This protection is essential for maintaining system security. However, attackers or administrators can disable DSE and load untrusted drivers, which can put the system at risk. Therefore, it's important to keep this feature enabled and only load drivers from trusted sources to ensure system integrity and security.
+
+This rule identifies an attempt to load an untrusted driver, which effectively means that DSE was disabled or bypassed. This can indicate that the system was compromised.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Examine the driver loaded to identify potentially suspicious characteristics. The following actions can help you gain context:
+  - Identify the path that the driver was loaded from. If you're using Elastic Defend, path information can be found in the `dll.path` field.
+  - Examine the file creation and modification timestamps:
+    - On Elastic Defend, those can be found in the `dll.Ext.relative_file_creation_time` and `dll.Ext.relative_file_name_modify_time` fields. The values are in seconds.
+    - Search for file creation events sharing the same file name as the `dll.name` field and identify the process responsible for the operation.
+      - Investigate any other abnormal behavior by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
+  - Use the driver SHA-256 (`dll.hash.sha256` field) hash value to search for the existence and reputation in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Use Osquery to investigate the drivers loaded into the system.
+  - !{osquery{"label":"Osquery - Retrieve All Non-Microsoft Drivers with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, class, description, directory, image, issuer_name, manufacturer, service, signed, subject_name FROM drivers JOIN authenticode ON drivers.image = authenticode.path JOIN hash ON drivers.image = hash.path WHERE NOT (provider == \"Microsoft\" AND signed == \"1\")\n"}}
+  - !{osquery{"label":"Osquery - Retrieve All Unsigned Drivers with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, class, description, directory, image, issuer_name, manufacturer, service, signed, subject_name FROM drivers JOIN authenticode ON drivers.image = authenticode.path JOIN hash ON drivers.image = hash.path WHERE signed == \"0\"\n"}}
+- Identify the driver's `Device Name` and `Service Name`.
+- Check for alerts from the rules specified in the `Related Rules` section.
+
+
+*False positive analysis*
+
+
+- This activity should not happen legitimately. The security team should address any potential benign true positive (B-TP), as this configuration can put the user and the domain at risk.
+
+
+*Related Rules*
+
+
+- First Time Seen Driver Loaded - df0fd41e-5590-4965-ad5e-cd079ec22fa9
+- Code Signing Policy Modification Through Registry - da7733b1-fe08-487e-b536-0a04c6d8b0cd
+- Code Signing Policy Modification Through Built-in tools - b43570de-a908-4f7f-8bdb-b2df6ffd8c80
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Disable and uninstall all suspicious drivers found in the system. This can be done via Device Manager. (Note that this step may require you to boot the system into Safe Mode.)
+- Remove the related services and registry keys found in the system. Note that the service will probably not stop if the driver is still installed.
+  - This can be done via PowerShell `Remove-Service` cmdlet.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Ensure that the Driver Signature Enforcement is enabled on the system.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+driver where host.os.type == "windows" and process.pid == 4 and
+  dll.code_signature.trusted != true and 
+  not dll.code_signature.status : ("errorExpired", "errorRevoked", "errorCode_endpoint:*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Invalid Code Signature
+** ID: T1036.001
+** Reference URL: https://attack.mitre.org/techniques/T1036/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-aws-command-for-a-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-aws-command-for-a-user.asciidoc
index 8936f4b2d5..888e7fae81 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-aws-command-for-a-user.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-aws-command-for-a-user.asciidoc
@@ -5,102 +5,93 @@ A machine learning job detected an AWS API command that, while not inherently su
 
 *Rule type*: machine_learning
 
-*Machine learning job*: rare_method_for_a_username
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-2h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Resources: Investigation Guide
+
+*Version*: 208
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* ML
-* Investigation Guide
 
-*Version*: 102 (<<unusual-aws-command-for-a-user-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-New or unusual user command activity can be due to manual troubleshooting or reconfiguration; changes in cloud automation scripts or workflows; adoption of new services; or changes in the way services are used.
 
-==== Investigation guide
+
+*Investigating Unusual AWS Command for a User*
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+CloudTrail logging provides visibility on actions taken within an AWS environment. By monitoring these events and understanding what is considered normal behavior within an organization, you can spot suspicious or malicious activity when deviations occur.
 
-### Investigating Unusual AWS Command for a User
+This rule uses a machine learning job to detect an AWS API command that while not inherently suspicious or abnormal, is being made by a user context that does not normally use the command. This can be the result of compromised credentials or keys as someone uses a valid account to persist, move laterally, or exfiltrate data.
 
-CloudTrail logging provides visibility on actions taken within an AWS environment. By monitoring these events and
-understanding what is considered normal behavior within an organization, you can spot suspicious or malicious activity
-when deviations occur.
+Detection alerts from this rule indicate an AWS API command or method call that is rare and unusual for the calling IAM user.
 
-This rule uses a machine learning job to detect an AWS API command that while not inherently suspicious or abnormal, is
-being made by a user context that does not normally use the command. This can be the result of compromised credentials or
-keys as someone uses a valid account to persist, move laterally, or exfiltrate data.
 
-Detection alerts from this rule indicate an AWS API command or method call that is rare and unusual for the calling IAM
-user.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account involved and the action performed. Verify whether it should perform this kind of action.
-    - Examine the user identity in the `aws.cloudtrail.user_identity.arn` field and the access key ID in the
-    `aws.cloudtrail.user_identity.access_key_id` field, which can help identify the precise user context.
+    - Examine the user identity in the `aws.cloudtrail.user_identity.arn` field and the access key ID in the `aws.cloudtrail.user_identity.access_key_id` field, which can help identify the precise user context.
     - The user agent details in the `user_agent.original` field may also indicate what kind of a client made the request.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Validate the activity is not related to planned patches, updates, or network administrator activity.
 - Examine the request parameters. These might indicate the source of the program or the nature of its tasks.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the calling user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
-- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal
-time of day?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
+- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal time of day?
 - Contact the account owner and confirm whether they are aware of this activity if suspicious.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
+
 
-### False positive analysis
+- Examine the history of the command. If the command only manifested recently, it might be part of a new automation module or script. If it has a consistent cadence (for example, it appears in small numbers on a weekly or monthly cadence), it might be part of a housekeeping or maintenance process. You can find the command in the `event.action field` field.
 
-- Examine the history of the command. If the command only manifested recently, it might be part of a new automation
-module or script. If it has a consistent cadence (for example, it appears in small numbers on a weekly or monthly cadence),
-it might be part of a housekeeping or maintenance process. You can find the command in the `event.action field` field.
 
-### Related Rules
+*Related Rules*
+
 
 - Unusual City For an AWS Command - 809b70d3-e2c3-455e-af1b-2626a5a1a276
 - Unusual Country For an AWS Command - dca28dee-c999-400f-b640-50a081cc0fd1
 - Rare AWS Error Code - 19de8096-e2b0-4bd8-80c9-34a820813fff
 - Spike in AWS Error Messages - 78d3d8d9-b476-451d-a9e0-7a5addd70670
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -110,47 +101,16 @@ it might be part of a housekeeping or maintenance process. You can find the comm
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
-
-
-[[unusual-aws-command-for-a-user-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (7.16.0 release)::
-* Formatting only
-
-Version 6 (7.15.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 3 (7.12.0 release)::
-* Formatting only
+==== Setup
 
-Version 2 (7.10.0 release)::
-* Formatting only
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-child-process-from-a-system-virtual-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-child-process-from-a-system-virtual-process.asciidoc
index 7a0daa5258..58aedf5c5c 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-child-process-from-a-system-virtual-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-child-process-from-a-system-virtual-process.asciidoc
@@ -5,62 +5,68 @@ Identifies a suspicious child process of the Windows virtual system process, whi
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<unusual-child-process-from-a-system-virtual-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.pid == 4 and
-not process.executable : ("Registry", "MemCompression",
-"?:\\Windows\\System32\\smss.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.pid == 4 and process.executable : "?*" and
+  not process.executable : ("Registry", "MemCompression", "?:\\Windows\\System32\\smss.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,42 +78,3 @@ not process.executable : ("Registry", "MemCompression",
 ** Name: Process Injection
 ** ID: T1055
 ** Reference URL: https://attack.mitre.org/techniques/T1055/
-
-[[unusual-child-process-from-a-system-virtual-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.pid == 4 and not process.executable : ("Registry",
-"MemCompression", "?:\\Windows\\System32\\smss.exe")
-----------------------------------
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.pid:4 and not process.executable:(Registry or
-MemCompression or "C:\Windows\System32\smss.exe")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-child-process-of-dns-exe.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-child-process-of-dns-exe.asciidoc
new file mode 100644
index 0000000000..e7d2aaa57a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-child-process-of-dns-exe.asciidoc
@@ -0,0 +1,136 @@
+[[unusual-child-process-of-dns-exe]]
+=== Unusual Child Process of dns.exe
+
+Identifies an unexpected process spawning from dns.exe, the process responsible for Windows DNS server services, which may indicate activity related to remote code execution or other forms of exploitation.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://research.checkpoint.com/2020/resolving-your-way-into-domain-admin-exploiting-a-17-year-old-bug-in-windows-dns-servers/
+* https://msrc-blog.microsoft.com/2020/07/14/july-2020-security-update-cve-2020-1350-vulnerability-in-windows-domain-name-system-dns-server/
+* https://github.com/maxpl0it/CVE-2020-1350-DoS
+* https://www.elastic.co/security-labs/detection-rules-for-sigred-vulnerability
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+
+*Version*: 110
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Unusual Child Process of dns.exe*
+
+
+SIGRed (CVE-2020-1350) is a wormable, critical vulnerability in the Windows DNS server that affects Windows Server versions 2003 to 2019 and can be triggered by a malicious DNS response. Because the service is running in elevated privileges (SYSTEM), an attacker that successfully exploits it is granted Domain Administrator rights. This can effectively compromise the entire corporate infrastructure.
+
+This rule looks for unusual children of the `dns.exe` process, which can indicate the exploitation of the SIGRed or a similar remote code execution vulnerability in the DNS server.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes.
+  - Any suspicious or abnormal child process spawned from dns.exe should be carefully reviewed and investigated. It's impossible to predict what an adversary may deploy as the follow-on process after the exploit, but built-in discovery/enumeration utilities should be top of mind (`whoami.exe`, `netstat.exe`, `systeminfo.exe`, `tasklist.exe`).
+  - Built-in Windows programs that contain capabilities used to download and execute additional payloads should also be considered. This is not an exhaustive list, but ideal candidates to start out would be: `mshta.exe`, `powershell.exe`, `regsvr32.exe`, `rundll32.exe`, `wscript.exe`, `wmic.exe`.
+  - If a denial-of-service (DoS) exploit is successful and DNS Server service crashes, be mindful of potential child processes related to `werfault.exe` occurring.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Investigate other alerts associated with the host during the past 48 hours.
+- Check whether the server is vulnerable to CVE-2020-1350.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Reimage the host operating system or restore the compromised server to a clean state.
+- Install the latest patches on systems that run Microsoft DNS Server.
+- Consider the implementation of a patch management system, such as the Windows Server Update Services (WSUS).
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Review the privileges assigned to the user to ensure that the least privilege principle is being followed.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.parent.name : "dns.exe" and
+  not process.name : "conhost.exe"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-child-processes-of-rundll32.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-child-processes-of-rundll32.asciidoc
index 3a8ae4092b..5e98078ca6 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-child-processes-of-rundll32.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-child-processes-of-rundll32.asciidoc
@@ -5,53 +5,128 @@ Identifies child processes of unusual instances of RunDLL32 where the command li
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 30 minutes
+*Runs every*: 30m
 
 *Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 101 (<<unusual-child-processes-of-rundll32-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Unusual Child Processes of RunDLL32*
+
+
+By examining the specific traits of Windows binaries -- such as process trees, command lines, network connections, registry modifications, and so on -- it's possible to establish a baseline of normal activity. Deviations from this baseline can indicate malicious activity, such as masquerading and deserve further investigation.
+
+RunDLL32 is a legitimate Windows utility used to load and execute functions within dynamic-link libraries (DLLs). However, adversaries may abuse RunDLL32 to execute malicious code, bypassing security measures and evading detection. This rule identifies potential abuse by looking for an unusual process creation with no arguments followed by the creation of a child process.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Investigate any abnormal behavior by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
+- Investigate the behavior of child processes, such as network connections, registry or file modifications, and any spawned processes.
+- Inspect the host for suspicious or abnormal behavior in the alert timeframe.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Related Rules*
+
+
+- Unusual Network Connection via RunDLL32 - 52aaab7b-b51c-441a-89ce-4387b3aea886
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence with maxspan=1h [process where event.type == "start" and
-(process.name : "rundll32.exe" or process.pe.original_file_name ==
-"RUNDLL32.EXE") and process.args_count == 1 ] by
-process.entity_id [process where event.type == "start" and
-process.parent.name : "rundll32.exe" ] by process.parent.entity_id
+[source, js]
 ----------------------------------
+sequence with maxspan=1h
+  [process where host.os.type == "windows" and event.type == "start" and
+     (process.name : "rundll32.exe" or process.pe.original_file_name == "RUNDLL32.EXE") and
+      process.args_count == 1
+  ] by process.entity_id
+  [process where host.os.type == "windows" and event.type == "start" and process.parent.name : "rundll32.exe"
+  ] by process.parent.entity_id
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -63,43 +138,7 @@ process.parent.name : "rundll32.exe" ] by process.parent.entity_id
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[unusual-child-processes-of-rundll32-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1h [process where event.type in ("start",
-"process_started") and (process.name : "rundll32.exe" or
-process.pe.original_file_name == "RUNDLL32.EXE") and
-process.args_count == 1 ] by process.entity_id [process where
-event.type in ("start", "process_started") and process.parent.name :
-"rundll32.exe" ] by process.parent.entity_id
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.14.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence with maxspan=1h [process where event.type in ("start",
-"process_started") and /*
-uncomment once in winlogbeat */ (process.name : "rundll32.exe" /*
-or process.pe.original_file_name == "RUNDLL32.EXE" */ ) and
-process.args_count < 2 ] by process.entity_id [process where
-event.type in ("start", "process_started") and process.parent.name :
-"rundll32.exe" ] by process.parent.entity_id
-----------------------------------
-
+* Sub-technique:
+** Name: Rundll32
+** ID: T1218.011
+** Reference URL: https://attack.mitre.org/techniques/T1218/011/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-city-for-an-aws-command.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-city-for-an-aws-command.asciidoc
index a209b33444..905e0fa53c 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-city-for-an-aws-command.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-city-for-an-aws-command.asciidoc
@@ -5,103 +5,94 @@ A machine learning job detected AWS command activity that, while not inherently
 
 *Rule type*: machine_learning
 
-*Machine learning job*: rare_method_for_a_city
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-2h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Resources: Investigation Guide
+
+*Version*: 208
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* ML
-* Investigation Guide
 
-*Version*: 102 (<<unusual-city-for-an-aws-command-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.9.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-New or unusual command and user geolocation activity can be due to manual troubleshooting or reconfiguration; changes in cloud automation scripts or workflows; adoption of new services; expansion into new regions; increased adoption of work from home policies; or users who travel frequently.
 
-==== Investigation guide
+
+*Investigating Unusual City For an AWS Command*
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+CloudTrail logging provides visibility on actions taken within an AWS environment. By monitoring these events and understanding what is considered normal behavior within an organization, you can spot suspicious or malicious activity when deviations occur.
 
-### Investigating Unusual City For an AWS Command
+This rule uses a machine learning job to detect an AWS API command that while not inherently suspicious or abnormal, is sourcing from a geolocation (city) that is unusual for the command. This can be the result of compromised credentials or keys used by a threat actor in a different geography than the authorized user(s).
 
-CloudTrail logging provides visibility on actions taken within an AWS environment. By monitoring these events and
-understanding what is considered normal behavior within an organization, you can spot suspicious or malicious activity
-when deviations occur.
+Detection alerts from this rule indicate an AWS API command or method call that is rare and unusual for the geolocation of the source IP address.
 
-This rule uses a machine learning job to detect an AWS API command that while not inherently suspicious or abnormal, is
-sourcing from a geolocation (city) that is unusual for the command. This can be the result of compromised credentials or
-keys used by a threat actor in a different geography than the authorized user(s).
 
-Detection alerts from this rule indicate an AWS API command or method call that is rare and unusual for the geolocation
-of the source IP address.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account involved and the action performed. Verify whether it should perform this kind of action.
-    - Examine the user identity in the `aws.cloudtrail.user_identity.arn` field and the access key ID in the
-    `aws.cloudtrail.user_identity.access_key_id` field, which can help identify the precise user context.
+    - Examine the user identity in the `aws.cloudtrail.user_identity.arn` field and the access key ID in the `aws.cloudtrail.user_identity.access_key_id` field, which can help identify the precise user context.
     - The user agent details in the `user_agent.original` field may also indicate what kind of a client made the request.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Validate the activity is not related to planned patches, updates, or network administrator activity.
 - Examine the request parameters. These might indicate the source of the program or the nature of its tasks.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the calling user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
-- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal
-time of day?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
+- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal time of day?
 - Contact the account owner and confirm whether they are aware of this activity if suspicious.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False positive analysis*
 
-### False positive analysis
 
 - False positives can occur if activity is coming from new employees based in a city with no previous history in AWS.
-- Examine the history of the command. If the command only manifested recently, it might be part of a new automation
-module or script. If it has a consistent cadence (for example, it appears in small numbers on a weekly or monthly cadence),
-it might be part of a housekeeping or maintenance process. You can find the command in the `event.action field` field.
+- Examine the history of the command. If the command only manifested recently, it might be part of a new automation module or script. If it has a consistent cadence (for example, it appears in small numbers on a weekly or monthly cadence), it might be part of a housekeeping or maintenance process. You can find the command in the `event.action field` field.
+
+
+*Related Rules*
 
-### Related Rules
 
 - Unusual Country For an AWS Command - dca28dee-c999-400f-b640-50a081cc0fd1
 - Unusual AWS Command for a User - ac706eae-d5ec-4b14-b4fd-e8ba8086f0e1
 - Rare AWS Error Code - 19de8096-e2b0-4bd8-80c9-34a820813fff
 - Spike in AWS Error Messages - 78d3d8d9-b476-451d-a9e0-7a5addd70670
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -111,47 +102,16 @@ it might be part of a housekeeping or maintenance process. You can find the comm
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
-
-
-[[unusual-city-for-an-aws-command-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (7.16.0 release)::
-* Formatting only
-
-Version 6 (7.15.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 3 (7.12.0 release)::
-* Formatting only
+==== Setup
 
-Version 2 (7.10.0 release)::
-* Formatting only
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-country-for-an-aws-command.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-country-for-an-aws-command.asciidoc
index 954a35a9f5..7012cce44d 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-country-for-an-aws-command.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-country-for-an-aws-command.asciidoc
@@ -5,103 +5,94 @@ A machine learning job detected AWS command activity that, while not inherently
 
 *Rule type*: machine_learning
 
-*Machine learning job*: rare_method_for_a_country
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-2h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Cloud
+* Data Source: AWS
+* Data Source: Amazon Web Services
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Resources: Investigation Guide
+
+*Version*: 208
+
+*Rule authors*: 
 
 * Elastic
-* Cloud
-* AWS
-* ML
-* Investigation Guide
 
-*Version*: 102 (<<unusual-country-for-an-aws-command-history, version history>>)
+*Rule license*: Elastic License v2
+
 
-*Added ({stack} release)*: 7.9.0
+==== Investigation guide
 
-*Last modified ({stack} release)*: 8.6.0
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
+*Triage and analysis*
 
-==== Potential false positives
 
-New or unusual command and user geolocation activity can be due to manual troubleshooting or reconfiguration; changes in cloud automation scripts or workflows; adoption of new services; expansion into new regions; increased adoption of work from home policies; or users who travel frequently.
 
-==== Investigation guide
+*Investigating Unusual Country For an AWS Command*
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
+CloudTrail logging provides visibility on actions taken within an AWS environment. By monitoring these events and understanding what is considered normal behavior within an organization, you can spot suspicious or malicious activity when deviations occur.
 
-### Investigating Unusual Country For an AWS Command
+This rule uses a machine learning job to detect an AWS API command that while not inherently suspicious or abnormal, is sourcing from a geolocation (country) that is unusual for the command. This can be the result of compromised credentials or keys used by a threat actor in a different geography than the authorized user(s).
 
-CloudTrail logging provides visibility on actions taken within an AWS environment. By monitoring these events and
-understanding what is considered normal behavior within an organization, you can spot suspicious or malicious activity
-when deviations occur.
+Detection alerts from this rule indicate an AWS API command or method call that is rare and unusual for the geolocation of the source IP address.
 
-This rule uses a machine learning job to detect an AWS API command that while not inherently suspicious or abnormal, is
-sourcing from a geolocation (country) that is unusual for the command. This can be the result of compromised credentials
-or keys used by a threat actor in a different geography than the authorized user(s).
 
-Detection alerts from this rule indicate an AWS API command or method call that is rare and unusual for the geolocation
-of the source IP address.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Identify the user account involved and the action performed. Verify whether it should perform this kind of action.
-    - Examine the user identity in the `aws.cloudtrail.user_identity.arn` field and the access key ID in the
-    `aws.cloudtrail.user_identity.access_key_id` field, which can help identify the precise user context.
+    - Examine the user identity in the `aws.cloudtrail.user_identity.arn` field and the access key ID in the `aws.cloudtrail.user_identity.access_key_id` field, which can help identify the precise user context.
     - The user agent details in the `user_agent.original` field may also indicate what kind of a client made the request.
 - Investigate other alerts associated with the user account during the past 48 hours.
 - Validate the activity is not related to planned patches, updates, or network administrator activity.
 - Examine the request parameters. These might indicate the source of the program or the nature of its tasks.
 - Considering the source IP address and geolocation of the user who issued the command:
     - Do they look normal for the calling user?
-    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source
-    IP from an EC2 instance that's not under your control?
-    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles?
-    Are there any other alerts or signs of suspicious activity involving this instance?
-- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal
-time of day?
+    - If the source is an EC2 IP address, is it associated with an EC2 instance in one of your accounts or is the source IP from an EC2 instance that's not under your control?
+    - If it is an authorized EC2 instance, is the activity associated with normal behavior for the instance role or roles? Are there any other alerts or signs of suspicious activity involving this instance?
+- Consider the time of day. If the user is a human (not a program or script), did the activity take place during a normal time of day?
 - Contact the account owner and confirm whether they are aware of this activity if suspicious.
-- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services,
-and data accessed by the account in the last 24 hours.
+- If you suspect the account has been compromised, scope potentially compromised assets by tracking servers, services, and data accessed by the account in the last 24 hours.
+
+
+*False Positive Analysis*
 
-### False Positive Analysis
 
 - False positives can occur if activity is coming from new employees based in a country with no previous history in AWS.
-- Examine the history of the command. If the command only manifested recently, it might be part of a new automation
-module or script. If it has a consistent cadence (for example, it appears in small numbers on a weekly or monthly cadence),
-it might be part of a housekeeping or maintenance process. You can find the command in the `event.action field` field.
+- Examine the history of the command. If the command only manifested recently, it might be part of a new automation module or script. If it has a consistent cadence (for example, it appears in small numbers on a weekly or monthly cadence), it might be part of a housekeeping or maintenance process. You can find the command in the `event.action field` field.
+
+
+*Related Rules*
 
-### Related Rules
 
 - Unusual City For an AWS Command - 809b70d3-e2c3-455e-af1b-2626a5a1a276
 - Unusual AWS Command for a User - ac706eae-d5ec-4b14-b4fd-e8ba8086f0e1
 - Rare AWS Error Code - 19de8096-e2b0-4bd8-80c9-34a820813fff
 - Spike in AWS Error Messages - 78d3d8d9-b476-451d-a9e0-7a5addd70670
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Disable or limit the account during the investigation and response.
@@ -111,53 +102,16 @@ it might be part of a housekeeping or maintenance process. You can find the comm
     - Work with your IT team to identify and minimize the impact on users.
     - Identify if the attacker is moving laterally and compromising other accounts, servers, or services.
     - Identify any regulatory or legal ramifications related to this activity.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with
-your IT teams to minimize the impact on business operations during these actions.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords or delete API keys as needed to revoke the attacker's access to the environment. Work with your IT teams to minimize the impact on business operations during these actions.
 - Check if unauthorized new users were created, remove unauthorized new accounts, and request password resets for other IAM users.
 - Consider enabling multi-factor authentication for users.
 - Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.
-- Implement security best practices [outlined](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/) by AWS.
+- Implement security best practices https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/[outlined] by AWS.
 - Take the actions needed to return affected systems, data, or services to their normal operational levels.
 - Identify the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
-
-
-[[unusual-country-for-an-aws-command-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 11 (8.4.0 release)::
-* Formatting only
-
-Version 9 (8.2.0 release)::
-* Formatting only
-
-Version 8 (8.1.0 release)::
-* Formatting only
-
-Version 7 (7.16.0 release)::
-* Formatting only
-
-Version 6 (7.15.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 3 (7.12.0 release)::
-* Formatting only
+==== Setup
 
-Version 2 (7.10.0 release)::
-* Formatting only
 
+The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-discovery-activity-by-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-discovery-activity-by-user.asciidoc
new file mode 100644
index 0000000000..bdbe322dc2
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-discovery-activity-by-user.asciidoc
@@ -0,0 +1,61 @@
+[[unusual-discovery-activity-by-user]]
+=== Unusual Discovery Activity by User
+
+This rule leverages alert data from various Discovery building block rules to alert on signals with unusual unique host.id and user.id entries.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* .alerts-security.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: Higher-Order Rule
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:windows and event.kind:signal and kibana.alert.rule.rule_id:(
+  "d68e95ad-1c82-4074-a12a-125fe10ac8ba" or "7b8bfc26-81d2-435e-965c-d722ee397ef1" or
+  "0635c542-1b96-4335-9b47-126582d2c19a" or "6ea55c81-e2ba-42f2-a134-bccf857ba922" or
+  "e0881d20-54ac-457f-8733-fe0bc5d44c55" or "06568a02-af29-4f20-929c-f3af281e41aa" or
+  "c4e9ed3e-55a2-4309-a012-bc3c78dad10a" or "51176ed2-2d90-49f2-9f3d-17196428b169" or
+  "1d72d014-e2ab-4707-b056-9b96abe7b511"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-discovery-signal-alert-with-unusual-process-command-line.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-discovery-signal-alert-with-unusual-process-command-line.asciidoc
new file mode 100644
index 0000000000..7af44d5891
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-discovery-signal-alert-with-unusual-process-command-line.asciidoc
@@ -0,0 +1,60 @@
+[[unusual-discovery-signal-alert-with-unusual-process-command-line]]
+=== Unusual Discovery Signal Alert with Unusual Process Command Line
+
+This rule leverages alert data from various Discovery building block rules to alert on signals with unusual unique host.id, user.id and process.command_line entries.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* .alerts-security.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: Higher-Order Rule
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:windows and event.kind:signal and kibana.alert.rule.rule_id:(
+  "d68e95ad-1c82-4074-a12a-125fe10ac8ba" or "7b8bfc26-81d2-435e-965c-d722ee397ef1" or
+  "0635c542-1b96-4335-9b47-126582d2c19a" or "6ea55c81-e2ba-42f2-a134-bccf857ba922" or
+  "e0881d20-54ac-457f-8733-fe0bc5d44c55" or "06568a02-af29-4f20-929c-f3af281e41aa" or
+  "c4e9ed3e-55a2-4309-a012-bc3c78dad10a" or "51176ed2-2d90-49f2-9f3d-17196428b169"
+)
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-discovery-signal-alert-with-unusual-process-executable.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-discovery-signal-alert-with-unusual-process-executable.asciidoc
new file mode 100644
index 0000000000..d6807644df
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-discovery-signal-alert-with-unusual-process-executable.asciidoc
@@ -0,0 +1,55 @@
+[[unusual-discovery-signal-alert-with-unusual-process-executable]]
+=== Unusual Discovery Signal Alert with Unusual Process Executable
+
+This rule leverages Discovery building block rule alert data to alert on signals with unusual unique host.id, user.id and process.executable entries.
+
+*Rule type*: new_terms
+
+*Rule indices*: 
+
+* .alerts-security.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: Higher-Order Rule
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type:windows and event.kind:signal and kibana.alert.rule.rule_id:"1d72d014-e2ab-4707-b056-9b96abe7b511"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-dns-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-dns-activity.asciidoc
index fdd51dd054..4b6b00f11e 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-dns-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-dns-activity.asciidoc
@@ -5,47 +5,37 @@ A machine learning job detected a rare and unusual DNS query that indicate netwo
 
 *Rule type*: machine_learning
 
-*Machine learning job*: packetbeat_rare_dns_question
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Network
-* Threat Detection
-* ML
-* Command and Control
+*Tags*: 
 
-*Version*: 100 (<<unusual-dns-activity-history, version history>>)
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Command and Control
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A newly installed program or one that runs rarely as part of a monthly or quarterly workflow could trigger this alert. Network activity that occurs rarely, in small quantities, can trigger this alert. Possible examples are browsing technical support or vendor networks sparsely. A user who visits a new or unique web destination may trigger this alert.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -57,22 +47,7 @@ A newly installed program or one that runs rarely as part of a monthly or quarte
 ** Name: Application Layer Protocol
 ** ID: T1071
 ** Reference URL: https://attack.mitre.org/techniques/T1071/
-
-[[unusual-dns-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: DNS
+** ID: T1071.004
+** Reference URL: https://attack.mitre.org/techniques/T1071/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-executable-file-creation-by-a-system-critical-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-executable-file-creation-by-a-system-critical-process.asciidoc
index ebe38b6ebf..52dadf20b8 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-executable-file-creation-by-a-system-critical-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-executable-file-creation-by-a-system-critical-process.asciidoc
@@ -5,91 +5,96 @@ Identifies an unexpected executable file being created or modified by a Windows
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<unusual-executable-file-creation-by-a-system-critical-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Unusual Executable File Creation by a System Critical Process
+*Triage and analysis*
+
 
-Windows internal/system processes have some characteristics that can be used to spot suspicious activities. One of these
-characteristics is file operations.
 
-This rule looks for the creation of executable files done by system-critical processes. This can indicate the exploitation
-of a vulnerability or a malicious process masquerading as a system-critical process.
+*Investigating Unusual Executable File Creation by a System Critical Process*
+
+
+Windows internal/system processes have some characteristics that can be used to spot suspicious activities. One of these characteristics is file operations.
+
+This rule looks for the creation of executable files done by system-critical processes. This can indicate the exploitation of a vulnerability or a malicious process masquerading as a system-critical process.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
 
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -97,31 +102,45 @@ and any spawned child processes.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type != "deletion" and file.extension : ("exe",
-"dll") and process.name : ("smss.exe",
-"autochk.exe", "csrss.exe",
-"wininit.exe", "services.exe",
-"lsass.exe", "winlogon.exe",
-"userinit.exe", "LogonUI.exe")
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type != "deletion" and
+  file.extension : ("exe", "dll") and
+  process.name : ("smss.exe",
+                  "autochk.exe",
+                  "csrss.exe",
+                  "wininit.exe",
+                  "services.exe",
+                  "lsass.exe",
+                  "winlogon.exe",
+                  "userinit.exe",
+                  "LogonUI.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -133,36 +152,11 @@ file where event.type != "deletion" and file.extension : ("exe",
 ** Name: Exploitation for Defense Evasion
 ** ID: T1211
 ** Reference URL: https://attack.mitre.org/techniques/T1211/
-
-[[unusual-executable-file-creation-by-a-system-critical-process-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:file and not event.type:deletion and
-file.extension:(exe or dll) and process.name:(smss.exe or autochk.exe
-or csrss.exe or wininit.exe or services.exe or lsass.exe or
-winlogon.exe or userinit.exe or LogonUI.exe)
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Exploitation for Client Execution
+** ID: T1203
+** Reference URL: https://attack.mitre.org/techniques/T1203/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-execution-via-microsoft-common-console-file.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-execution-via-microsoft-common-console-file.asciidoc
new file mode 100644
index 0000000000..a551254716
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-execution-via-microsoft-common-console-file.asciidoc
@@ -0,0 +1,124 @@
+[[unusual-execution-via-microsoft-common-console-file]]
+=== Unusual Execution via Microsoft Common Console File
+
+Identifies the execution of a child process from a Microsoft Common Console file. Adversaries may embed a malicious command in an MSC file in order to trick victims into executing malicious commands.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.genians.co.kr/blog/threat_intelligence/facebook
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Tactic: Initial Access
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Execution via Microsoft Common Console File*
+
+
+- Investigate the source of the MSC file.
+- Investigate the process execution chain (all spawned child processes and their descendants).
+- Investigate the process and it's descendants network and file events.
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+
+
+*Response and remediation*
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.parent.executable : "?:\\Windows\\System32\\mmc.exe" and endswith~(process.parent.args, ".msc") and
+ not process.parent.args : ("?:\\Windows\\System32\\*.msc", "?:\\Windows\\SysWOW64\\*.msc", "?:\\Program files\\*.msc", "?:\\Program Files (x86)\\*.msc")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: User Execution
+** ID: T1204
+** Reference URL: https://attack.mitre.org/techniques/T1204/
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
+* Tactic:
+** Name: Initial Access
+** ID: TA0001
+** Reference URL: https://attack.mitre.org/tactics/TA0001/
+* Technique:
+** Name: Phishing
+** ID: T1566
+** Reference URL: https://attack.mitre.org/techniques/T1566/
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Sub-technique:
+** Name: Spearphishing Link
+** ID: T1566.002
+** Reference URL: https://attack.mitre.org/techniques/T1566/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-file-creation-alternate-data-stream.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-file-creation-alternate-data-stream.asciidoc
index 4eedf4bda9..119e9c3bf8 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-file-creation-alternate-data-stream.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-file-creation-alternate-data-stream.asciidoc
@@ -5,97 +5,98 @@ Identifies suspicious creation of Alternate Data Streams on highly targeted file
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<unusual-file-creation-alternate-data-stream-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 114
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Unusual File Creation - Alternate Data Stream
+*Triage and analysis*
+
 
-Alternate Data Streams (ADS) are file attributes only found on the NTFS file system. In this file system, files are
-built up from a couple of attributes; one of them is $Data, also known as the data attribute.
 
-The regular data stream, also referred to as the unnamed data stream since the name string of this attribute is empty,
-contains the data inside the file. So any data stream that has a name is considered an alternate data stream.
+*Investigating Unusual File Creation - Alternate Data Stream*
 
-Attackers can abuse these alternate data streams to hide malicious files, string payloads, etc. This rule detects the
-creation of alternate data streams on highly targeted file types.
+
+Alternate Data Streams (ADS) are file attributes only found on the NTFS file system. In this file system, files are built up from a couple of attributes; one of them is $Data, also known as the data attribute.
+
+The regular data stream, also referred to as the unnamed data stream since the name string of this attribute is empty, contains the data inside the file. So any data stream that has a name is considered an alternate data stream.
+
+Attackers can abuse these alternate data streams to hide malicious files, string payloads, etc. This rule detects the creation of alternate data streams on highly targeted file types.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
 
-#### Possible investigation steps
+*Possible investigation steps*
 
-- Retrieve the contents of the alternate data stream, and analyze it for potential maliciousness. Analysts can use the
-following PowerShell cmdlet to accomplish this:
-  - `Get-Content -file C:\Path\To\file.exe -stream ADSname`
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
+
+- Retrieve the contents of the alternate data stream, and analyze it for potential maliciousness. Analysts can use the following PowerShell cmdlet to accomplish this:
+  - `Get-Content C:\Path\To\file.exe -stream SampleAlternateDataStreamName`
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
+
+
+
+*False positive analysis*
 
 
-### False positive analysis
+- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of process executable and file conditions.
 
-- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination
-of process executable and file conditions.
 
-### Response and remediation
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -103,51 +104,97 @@ of process executable and file conditions.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type == "creation" and file.path : "C:\\*:*" and
-not file.path : "C:\\*:zone.identifier*" and not process.executable
-: ("?:\\windows\\System32\\svchost.exe",
-"?:\\Windows\\System32\\inetsrv\\w3wp.exe",
-"?:\\Windows\\explorer.exe",
-"?:\\Windows\\System32\\sihost.exe",
-"?:\\Windows\\System32\\PickerHost.exe",
-"?:\\Windows\\System32\\SearchProtocolHost.exe",
-"?:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe",
-"?:\\Program Files\\Rivet
-Networks\\SmartByte\\SmartByteNetworkService.exe",
-"?:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe",
-"?:\\Program Files\\ExpressConnect\\ExpressConnectNetworkService.exe",
-"?:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe",
-"?:\\Program Files\\Google\\Chrome\\Application\\chrome.exe",
-"?:\\Program Files\\Mozilla Firefox\\firefox.exe") and
-file.extension : ( "pdf", "dll", "png",
-"exe", "dat", "com", "bat", "cmd",
-"sys", "vbs", "ps1", "hta", "txt",
-"vbe", "js", "wsh", "docx", "doc",
-"xlsx", "xls", "pptx", "ppt", "rtf",
-"gif", "jpg", "png", "bmp", "img", "iso"
-)
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and
+
+  file.path : "C:\\*:*" and
+  not file.path : 
+          ("C:\\*:zone.identifier*",
+           "C:\\users\\*\\appdata\\roaming\\microsoft\\teams\\old_weblogs_*:$DATA") and
+
+  not process.executable :
+          ("?:\\windows\\System32\\svchost.exe",
+           "?:\\Windows\\System32\\inetsrv\\w3wp.exe",
+           "?:\\Windows\\explorer.exe",
+           "?:\\Windows\\System32\\sihost.exe",
+           "?:\\Windows\\System32\\PickerHost.exe",
+           "?:\\Windows\\System32\\SearchProtocolHost.exe",
+           "?:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe",
+           "?:\\Program Files\\Rivet Networks\\SmartByte\\SmartByteNetworkService.exe",
+           "?:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe",
+           "?:\\Program Files\\ExpressConnect\\ExpressConnectNetworkService.exe",
+           "?:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe",
+           "?:\\Program Files\\Google\\Chrome\\Application\\chrome.exe",
+           "?:\\Program Files\\Mozilla Firefox\\firefox.exe",
+           "?:\\Program Files(x86)\\Microsoft Office\\root\\*\\EXCEL.EXE",
+           "?:\\Program Files\\Microsoft Office\\root\\*\\EXCEL.EXE",
+           "?:\\Program Files (x86)\\Microsoft Office\\root\\*\\OUTLOOK.EXE",
+           "?:\\Program Files\\Microsoft Office\\root\\*\\OUTLOOK.EXE",
+           "?:\\Program Files (x86)\\Microsoft Office\\root\\*\\POWERPNT.EXE",
+           "?:\\Program Files\\Microsoft Office\\root\\*\\POWERPNT.EXE",
+           "?:\\Program Files (x86)\\Microsoft Office\\root\\*\\WINWORD.EXE",
+           "?:\\Program Files\\Microsoft Office\\root\\*\\WINWORD.EXE") and
+
+  file.extension :
+    (
+      "pdf",
+      "dll",
+      "png",
+      "exe",
+      "dat",
+      "com",
+      "bat",
+      "cmd",
+      "sys",
+      "vbs",
+      "ps1",
+      "hta",
+      "txt",
+      "vbe",
+      "js",
+      "wsh",
+      "docx",
+      "doc",
+      "xlsx",
+      "xls",
+      "pptx",
+      "ppt",
+      "rtf",
+      "gif",
+      "jpg",
+      "png",
+      "bmp",
+      "img",
+      "iso"
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -159,31 +206,7 @@ file.extension : ( "pdf", "dll", "png",
 ** Name: Hide Artifacts
 ** ID: T1564
 ** Reference URL: https://attack.mitre.org/techniques/T1564/
-
-[[unusual-file-creation-alternate-data-stream-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type == "creation" and file.path : "C:\\*:*" and
-not file.path : "C:\\*:zone.identifier*" and file.extension : (
-"pdf", "dll", "png", "exe", "dat",
-"com", "bat", "cmd", "sys", "vbs",
-"ps1", "hta", "txt", "vbe", "js", "wsh",
-"docx", "doc", "xlsx", "xls", "pptx",
-"ppt", "rtf", "gif", "jpg", "png",
-"bmp", "img", "iso" )
-----------------------------------
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: NTFS File Attributes
+** ID: T1564.004
+** Reference URL: https://attack.mitre.org/techniques/T1564/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-file-modification-by-dns-exe.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-file-modification-by-dns-exe.asciidoc
new file mode 100644
index 0000000000..0ebd7fa287
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-file-modification-by-dns-exe.asciidoc
@@ -0,0 +1,100 @@
+[[unusual-file-modification-by-dns-exe]]
+=== Unusual File Modification by dns.exe
+
+Identifies an unexpected file being modified by dns.exe, the process responsible for Windows DNS Server services, which may indicate activity related to remote code execution or other forms of exploitation.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.file-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://research.checkpoint.com/2020/resolving-your-way-into-domain-admin-exploiting-a-17-year-old-bug-in-windows-dns-servers/
+* https://msrc-blog.microsoft.com/2020/07/14/july-2020-security-update-cve-2020-1350-vulnerability-in-windows-domain-name-system-dns-server/
+* https://www.elastic.co/security-labs/detection-rules-for-sigred-vulnerability
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Endgame
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 110
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Unusual File Write*
+
+Detection alerts from this rule indicate potential unusual/abnormal file writes from the DNS Server service process (`dns.exe`) after exploitation from CVE-2020-1350 (SigRed) has occurred. Here are some possible avenues of investigation:
+- Post-exploitation, adversaries may write additional files or payloads to the system as additional discovery/exploitation/persistence mechanisms.
+- Any suspicious or abnormal files written from `dns.exe` should be reviewed and investigated with care.
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+file where host.os.type == "windows" and process.name : "dns.exe" and event.type in ("creation", "deletion", "change") and
+  not file.name : "dns.log" and not
+  (file.extension : ("old", "temp", "bak", "dns", "arpa") and file.path : "C:\\Windows\\System32\\dns\\*")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-high-confidence-misconduct-blocks-detected.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-high-confidence-misconduct-blocks-detected.asciidoc
new file mode 100644
index 0000000000..b1f8303724
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-high-confidence-misconduct-blocks-detected.asciidoc
@@ -0,0 +1,68 @@
+[[unusual-high-confidence-misconduct-blocks-detected]]
+=== Unusual High Confidence Misconduct Blocks Detected
+
+Detects repeated high-confidence 'BLOCKED' actions coupled with specific violation codes such as 'MISCONDUCT', indicating persistent misuse or attempts to probe the model's ethical boundaries.
+
+*Rule type*: esql
+
+*Rule indices*: None
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 10m
+
+*Searches indices from*: now-60m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-components.html
+* https://atlas.mitre.org/techniques/AML.T0051
+* https://atlas.mitre.org/techniques/AML.T0054
+* https://www.elastic.co/security-labs/elastic-advances-llm-security
+
+*Tags*: 
+
+* Domain: LLM
+* Data Source: AWS Bedrock
+* Data Source: AWS S3
+* Use Case: Policy Violation
+* Mitre Atlas: T0051
+* Mitre Atlas: T0054
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires that guardrails are configured in AWS Bedrock. For more information, see the AWS Bedrock documentation:
+
+https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-create.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+from logs-aws_bedrock.invocation-*
+| where gen_ai.policy.confidence == "HIGH" and gen_ai.policy.action == "BLOCKED" and gen_ai.compliance.violation_code == "MISCONDUCT"
+| stats high_confidence_blocks = count() by user.id
+| where high_confidence_blocks > 5
+| sort high_confidence_blocks desc
+
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-hour-for-a-user-to-logon.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-hour-for-a-user-to-logon.asciidoc
index 1b3e3f7a3f..50d11e77a5 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-hour-for-a-user-to-logon.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-hour-for-a-user-to-logon.asciidoc
@@ -5,47 +5,76 @@ A machine learning job detected a user logging in at a time of day that is unusu
 
 *Rule type*: machine_learning
 
-*Machine learning job*: auth_rare_hour_for_a_user
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Use Case: Identity and Access Audit
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Initial Access
+* Resources: Investigation Guide
+
+*Version*: 104
+
+*Rule authors*: 
 
 * Elastic
-* Authentication
-* Threat Detection
-* ML
-* Initial Access
 
-*Version*: 100 (<<unusual-hour-for-a-user-to-logon-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.14.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
+
+
+
+*Investigating Unusual Hour for a User to Logon*
+
+
+This rule uses a machine learning job to detect a user logging in at a time of day that is unusual for the user. This can be due to credentialed access via a compromised account when the user and the threat actor are in different time zones. It can also indicate unauthorized user activity, as it often occurs during non-business hours.
+
+
+*Possible investigation steps*
+
+
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, network connections, data access, and logon events.
+- Investigate other alerts associated with the involved users during the past 48 hours.
+
+
+*False positive analysis*
+
+
+- Users may need to log in during non-business hours to perform work-related tasks. Examine whether the company policies authorize this or if the activity is done under change management.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Users working late, or logging in from unusual time zones while traveling, may trigger this rule.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -57,13 +86,3 @@ Users working late, or logging in from unusual time zones while traveling, may t
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[unusual-hour-for-a-user-to-logon-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-activity.asciidoc
index 42c39cefbf..9a141caad8 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-activity.asciidoc
@@ -5,81 +5,52 @@ Identifies Linux processes that do not usually use the network but have unexpect
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_linux_anomalous_network_activity
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
 
-*Version*: 100 (<<unusual-linux-network-activity-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.7.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Unusual Network Activity
+*Triage and analysis*
+
+
+
+*Investigating Unusual Network Activity*
+
 Detection alerts from this rule indicate the presence of network activity from a Linux process for which network activity is rare and unusual.  Here are some possible avenues of investigation:
 - Consider the IP addresses and ports. Are these used by normal but infrequent network workflows? Are they expected or unexpected?
 - If the destination IP address is remote or external, does it associate with an expected domain, organization or geography? Note: avoid interacting directly with suspected malicious IP addresses.
 - Consider the user as identified by the username field. Is this network activity part of an expected workflow for the user who ran the program?
 - Examine the history of execution. If this process only manifested recently, it might be part of a new software package. If it has a consistent cadence (for example if it runs monthly or quarterly), it might be part of a monthly or quarterly business or maintenance process.
 - Examine the process arguments, title and working directory. These may provide indications as to the source of the program or the nature of the tasks it is performing.
-----------------------------------
-
-
-[[unusual-linux-network-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.3.0 release)::
-* Formatting only
-
-Version 6 (7.15.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-configuration-discovery.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-configuration-discovery.asciidoc
new file mode 100644
index 0000000000..5e9228bafb
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-configuration-discovery.asciidoc
@@ -0,0 +1,49 @@
+[[unusual-linux-network-configuration-discovery]]
+=== Unusual Linux Network Configuration Discovery
+
+Looks for commands related to system network configuration discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used by a threat actor to engage in system network configuration discovery in order to increase their understanding of connected networks and hosts. This information may be used to shape follow-up behaviors such as lateral movement or additional discovery.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Discovery
+
+*Version*: 104
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Network Configuration Discovery
+** ID: T1016
+** Reference URL: https://attack.mitre.org/techniques/T1016/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-connection-discovery.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-connection-discovery.asciidoc
index ea74288113..f8cab62e2a 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-connection-discovery.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-connection-discovery.asciidoc
@@ -5,43 +5,37 @@ Looks for commands related to system network connection discovery from an unusua
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_linux_network_connection_discovery
-
-*Machine learning anomaly threshold*: 25
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
+*Tags*: 
 
-*Version*: 100 (<<unusual-linux-network-connection-discovery-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Discovery
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Uncommon user command activity can be due to an engineer logging onto a server instance in order to perform manual troubleshooting or reconfiguration.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -53,16 +47,3 @@ Uncommon user command activity can be due to an engineer logging onto a server i
 ** Name: System Network Connections Discovery
 ** ID: T1049
 ** Reference URL: https://attack.mitre.org/techniques/T1049/
-
-[[unusual-linux-network-connection-discovery-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-port-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-port-activity.asciidoc
index 526cdd6204..ef998afa40 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-port-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-linux-network-port-activity.asciidoc
@@ -5,65 +5,35 @@ Identifies unusual destination port activity that can indicate command-and-contr
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_linux_anomalous_network_port_activity
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
+*Tags*: 
 
-*Version*: 100 (<<unusual-linux-network-port-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A newly installed program or one that rarely uses the network could trigger this alert.
-
-[[unusual-linux-network-port-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-linux-process-calling-the-metadata-service.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-linux-process-calling-the-metadata-service.asciidoc
index 01978c35ef..93f8c231f1 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-linux-process-calling-the-metadata-service.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-linux-process-calling-the-metadata-service.asciidoc
@@ -5,44 +5,37 @@ Looks for anomalous access to the metadata service by an unusual process. The me
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_linux_rare_metadata_process
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
-* Credential Access
+*Tags*: 
 
-*Version*: 100 (<<unusual-linux-process-calling-the-metadata-service-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A newly installed program or one that runs very rarely as part of a monthly or quarterly workflow could trigger this detection rule.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -54,22 +47,7 @@ A newly installed program or one that runs very rarely as part of a monthly or q
 ** Name: Unsecured Credentials
 ** ID: T1552
 ** Reference URL: https://attack.mitre.org/techniques/T1552/
-
-[[unusual-linux-process-calling-the-metadata-service-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (7.14.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Cloud Instance Metadata API
+** ID: T1552.005
+** Reference URL: https://attack.mitre.org/techniques/T1552/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-linux-process-discovery-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-linux-process-discovery-activity.asciidoc
index a336620445..2dd7956e27 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-linux-process-discovery-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-linux-process-discovery-activity.asciidoc
@@ -5,43 +5,37 @@ Looks for commands related to system process discovery from an unusual user cont
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_linux_system_process_discovery
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
+*Tags*: 
 
-*Version*: 100 (<<unusual-linux-process-discovery-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Discovery
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Uncommon user command activity can be due to an engineer logging onto a server instance in order to perform manual troubleshooting or reconfiguration.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -53,16 +47,3 @@ Uncommon user command activity can be due to an engineer logging onto a server i
 ** Name: Process Discovery
 ** ID: T1057
 ** Reference URL: https://attack.mitre.org/techniques/T1057/
-
-[[unusual-linux-process-discovery-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-linux-system-information-discovery-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-linux-system-information-discovery-activity.asciidoc
index 7265d972c8..e0e3f8fe7f 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-linux-system-information-discovery-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-linux-system-information-discovery-activity.asciidoc
@@ -5,43 +5,37 @@ Looks for commands related to system information discovery from an unusual user
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_linux_system_information_discovery
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
+*Tags*: 
 
-*Version*: 100 (<<unusual-linux-system-information-discovery-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Discovery
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Uncommon user command activity can be due to an engineer logging onto a server instance in order to perform manual troubleshooting or reconfiguration.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -53,16 +47,3 @@ Uncommon user command activity can be due to an engineer logging onto a server i
 ** Name: System Information Discovery
 ** ID: T1082
 ** Reference URL: https://attack.mitre.org/techniques/T1082/
-
-[[unusual-linux-system-information-discovery-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-linux-user-calling-the-metadata-service.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-linux-user-calling-the-metadata-service.asciidoc
index 2a9c36eb3f..79639c36b8 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-linux-user-calling-the-metadata-service.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-linux-user-calling-the-metadata-service.asciidoc
@@ -5,44 +5,37 @@ Looks for anomalous access to the cloud platform metadata service by an unusual
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_linux_rare_metadata_user
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
-* Credential Access
+*Tags*: 
 
-*Version*: 100 (<<unusual-linux-user-calling-the-metadata-service-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A newly installed program, or one that runs under a new or rarely used user context, could trigger this detection rule. Manual interrogation of the metadata service during debugging or troubleshooting could trigger this rule.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -54,22 +47,7 @@ A newly installed program, or one that runs under a new or rarely used user cont
 ** Name: Unsecured Credentials
 ** ID: T1552
 ** Reference URL: https://attack.mitre.org/techniques/T1552/
-
-[[unusual-linux-user-calling-the-metadata-service-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (7.14.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Cloud Instance Metadata API
+** ID: T1552.005
+** Reference URL: https://attack.mitre.org/techniques/T1552/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-linux-user-discovery-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-linux-user-discovery-activity.asciidoc
new file mode 100644
index 0000000000..9df9d4cba7
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-linux-user-discovery-activity.asciidoc
@@ -0,0 +1,49 @@
+[[unusual-linux-user-discovery-activity]]
+=== Unusual Linux User Discovery Activity
+
+Looks for commands related to system user or owner discovery from an unusual user context. This can be due to uncommon troubleshooting activity or due to a compromised account. A compromised account may be used to engage in system owner or user discovery in order to identify currently active or primary users of a system. This may be a precursor to additional discovery, credential dumping or privilege elevation activity.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Discovery
+
+*Version*: 104
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Owner/User Discovery
+** ID: T1033
+** Reference URL: https://attack.mitre.org/techniques/T1033/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-linux-username.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-linux-username.asciidoc
index b6edb1735a..c0d065d500 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-linux-username.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-linux-username.asciidoc
@@ -5,63 +5,54 @@ A machine learning job detected activity for a username that is not normally act
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_linux_anomalous_user_name
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
-* Initial Access
+*Tags*: 
 
-*Version*: 100 (<<unusual-linux-username-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Uncommon user activity can be due to an engineer logging onto a server instance in order to perform manual troubleshooting or reconfiguration.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating an Unusual Linux User
+*Triage and analysis*
+
+
+
+*Investigating an Unusual Linux User*
+
 Detection alerts from this rule indicate activity for a Linux user name that is rare and unusual. Here are some possible avenues of investigation:
 - Consider the user as identified by the username field. Is this program part of an expected workflow for the user who ran this program on this host? Could this be related to troubleshooting or debugging activity by a developer or site reliability engineer?
 - Examine the history of user activity. If this user only manifested recently, it might be a service account for a new software package. If it has a consistent cadence (for example if it runs monthly or quarterly), it might be part of a monthly or quarterly business process.
 - Examine the process arguments, title and working directory. These may provide indications as to the source of the program or the nature of the tasks that the user is performing.
-----------------------------------
-
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,34 +64,3 @@ Detection alerts from this rule indicate activity for a Linux user name that is
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[unusual-linux-username-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 8 (8.3.0 release)::
-* Formatting only
-
-Version 7 (7.15.0 release)::
-* Formatting only
-
-Version 6 (7.14.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-login-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-login-activity.asciidoc
index d9240e028a..a6513138cb 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-login-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-login-activity.asciidoc
@@ -5,47 +5,38 @@ Identifies an unusually high number of authentication attempts.
 
 *Rule type*: machine_learning
 
-*Machine learning job*: suspicious_login_activity
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Authentication
-* Threat Detection
-* ML
-* Credential Access
+*Tags*: 
 
-*Version*: 100 (<<unusual-login-activity-history, version history>>)
+* Use Case: Identity and Access Audit
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Security audits may trigger this alert. Conditions that generate bursts of failed logins, such as misconfigured applications or account lockouts could trigger this alert.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -57,25 +48,3 @@ Security audits may trigger this alert. Conditions that generate bursts of faile
 ** Name: Brute Force
 ** ID: T1110
 ** Reference URL: https://attack.mitre.org/techniques/T1110/
-
-[[unusual-login-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-network-activity-from-a-windows-system-binary.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-network-activity-from-a-windows-system-binary.asciidoc
index 2ca6554ee2..8db3083bb2 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-network-activity-from-a-windows-system-binary.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-network-activity-from-a-windows-system-binary.asciidoc
@@ -5,74 +5,176 @@ Identifies network activity from unexpected system applications. This may indica
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 101 (<<unusual-network-activity-from-a-windows-system-binary-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Unusual Network Activity from a Windows System Binary*
+
+
+Attackers can abuse certain trusted developer utilities to proxy the execution of malicious payloads. Since these utilities are usually signed, they can bypass the security controls that were put in place to prevent or detect direct execution.
+
+This rule identifies network connections established by trusted developer utilities, which can indicate abuse to execute payloads or process masquerading.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate abnormal behaviors observed by the subject process, such as registry or file modifications, and any spawned child processes.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+
+
+*False positive analysis*
+
+
+- As trusted developer utilities have dual-use purposes, alerts derived from this rule are not essentially malicious. If these utilities are contacting internal or known trusted domains, review their security and consider creating exceptions if the domain is safe.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+  - If the malicious file was delivered via phishing:
+    - Block the email sender from sending future emails.
+    - Block the malicious web pages.
+    - Remove emails from the sender from mailboxes.
+    - Consider improvements to the security awareness program.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id with maxspan=5m [process where
-event.type == "start" and /* known applocker bypasses */
-(process.name : "bginfo.exe" or process.name : "cdb.exe" or
-process.name : "control.exe" or process.name : "cmstp.exe" or
-process.name : "csi.exe" or process.name : "dnx.exe" or
-process.name : "fsi.exe" or process.name : "ieexec.exe" or
-process.name : "iexpress.exe" or process.name :
-"installutil.exe" or process.name :
-"Microsoft.Workflow.Compiler.exe" or process.name :
-"MSBuild.exe" or process.name : "msdt.exe" or process.name
-: "mshta.exe" or process.name : "msiexec.exe" or
-process.name : "msxsl.exe" or process.name : "odbcconf.exe" or
-process.name : "rcsi.exe" or process.name : "regsvr32.exe" or
-process.name : "xwizard.exe")] [network where (process.name :
-"bginfo.exe" or process.name : "cdb.exe" or process.name :
-"control.exe" or process.name : "cmstp.exe" or
-process.name : "csi.exe" or process.name : "dnx.exe" or
-process.name : "fsi.exe" or process.name : "ieexec.exe" or
-process.name : "iexpress.exe" or process.name :
-"installutil.exe" or process.name :
-"Microsoft.Workflow.Compiler.exe" or process.name :
-"MSBuild.exe" or process.name : "msdt.exe" or process.name
-: "mshta.exe" or process.name : "msiexec.exe" or
-process.name : "msxsl.exe" or process.name : "odbcconf.exe" or
-process.name : "rcsi.exe" or process.name : "regsvr32.exe" or
-process.name : "xwizard.exe")]
+[source, js]
 ----------------------------------
+sequence by process.entity_id with maxspan=5m
+  [process where host.os.type == "windows" and event.type == "start" and
+
+     /* known applocker bypasses */
+     (process.name : "bginfo.exe" or
+      process.name : "cdb.exe" or
+      process.name : "control.exe" or
+      process.name : "cmstp.exe" or
+      process.name : "csi.exe" or
+      process.name : "dnx.exe" or
+      process.name : "fsi.exe" or
+      process.name : "ieexec.exe" or
+      process.name : "iexpress.exe" or
+      process.name : "installutil.exe" or
+      process.name : "Microsoft.Workflow.Compiler.exe" or
+      process.name : "MSBuild.exe" or
+      process.name : "msdt.exe" or
+      process.name : "mshta.exe" or
+      process.name : "msiexec.exe" or
+      process.name : "msxsl.exe" or
+      process.name : "odbcconf.exe" or
+      process.name : "rcsi.exe" or
+      process.name : "regsvr32.exe" or
+      process.name : "xwizard.exe")]
+  [network where
+     (process.name : "bginfo.exe" or
+      process.name : "cdb.exe" or
+      process.name : "control.exe" or
+      process.name : "cmstp.exe" or
+      process.name : "csi.exe" or
+      process.name : "dnx.exe" or
+      process.name : "fsi.exe" or
+      process.name : "ieexec.exe" or
+      process.name : "iexpress.exe" or
+      process.name : "installutil.exe" or
+      process.name : "Microsoft.Workflow.Compiler.exe" or
+      (
+        process.name : "msbuild.exe" and
+          destination.ip != "127.0.0.1"
+      ) or
+      process.name : "msdt.exe" or
+      process.name : "mshta.exe" or
+      (
+        process.name : "msiexec.exe" and not
+        dns.question.name : (
+           "ocsp.digicert.com", "ocsp.verisign.com", "ocsp.comodoca.com", "ocsp.entrust.net", "ocsp.usertrust.com",
+           "ocsp.godaddy.com", "ocsp.camerfirma.com", "ocsp.globalsign.com", "ocsp.sectigo.com", "*.local"
+        ) and
+        /* Localhost, DigiCert and Comodo CA IP addresses */
+        not cidrmatch(destination.ip, "127.0.0.1", "192.229.211.108/32", "192.229.221.95/32",
+                      "152.195.38.76/32", "104.18.14.101/32")
+      ) or
+      process.name : "msxsl.exe" or
+      process.name : "odbcconf.exe" or
+      process.name : "rcsi.exe" or
+      process.name : "regsvr32.exe" or
+      process.name : "xwizard.exe")]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -84,46 +186,19 @@ process.name : "xwizard.exe")]
 ** Name: Trusted Developer Utilities Proxy Execution
 ** ID: T1127
 ** Reference URL: https://attack.mitre.org/techniques/T1127/
-
-[[unusual-network-activity-from-a-windows-system-binary-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id with maxspan=5m [process where
-event.type in ("start", "process_started") and /* known
-applocker bypasses */ (process.name : "bginfo.exe" or
-process.name : "cdb.exe" or process.name : "control.exe" or
-process.name : "cmstp.exe" or process.name : "csi.exe" or
-process.name : "dnx.exe" or process.name : "fsi.exe" or
-process.name : "ieexec.exe" or process.name : "iexpress.exe" or
-process.name : "installutil.exe" or process.name :
-"Microsoft.Workflow.Compiler.exe" or process.name :
-"MSBuild.exe" or process.name : "msdt.exe" or process.name
-: "mshta.exe" or process.name : "msiexec.exe" or
-process.name : "msxsl.exe" or process.name : "odbcconf.exe" or
-process.name : "rcsi.exe" or process.name : "regsvr32.exe" or
-process.name : "xwizard.exe")] [network where (process.name :
-"bginfo.exe" or process.name : "cdb.exe" or process.name :
-"control.exe" or process.name : "cmstp.exe" or
-process.name : "csi.exe" or process.name : "dnx.exe" or
-process.name : "fsi.exe" or process.name : "ieexec.exe" or
-process.name : "iexpress.exe" or process.name :
-"installutil.exe" or process.name :
-"Microsoft.Workflow.Compiler.exe" or process.name :
-"MSBuild.exe" or process.name : "msdt.exe" or process.name
-: "mshta.exe" or process.name : "msiexec.exe" or
-process.name : "msxsl.exe" or process.name : "odbcconf.exe" or
-process.name : "rcsi.exe" or process.name : "regsvr32.exe" or
-process.name : "xwizard.exe")]
-----------------------------------
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: MSBuild
+** ID: T1127.001
+** Reference URL: https://attack.mitre.org/techniques/T1127/001/
+* Sub-technique:
+** Name: Mshta
+** ID: T1218.005
+** Reference URL: https://attack.mitre.org/techniques/T1218/005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Match Legitimate Name or Location
+** ID: T1036.005
+** Reference URL: https://attack.mitre.org/techniques/T1036/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-network-connection-via-dllhost.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-network-connection-via-dllhost.asciidoc
index 75d8a6ce18..f29e2c611c 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-network-connection-via-dllhost.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-network-connection-via-dllhost.asciidoc
@@ -5,65 +5,62 @@ Identifies unusual instances of dllhost.exe making outbound network connections.
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.microsoft.com/security/blog/2021/05/27/new-sophisticated-email-based-attack-from-nobelium/
 * https://www.volexity.com/blog/2021/05/27/suspected-apt29-operation-launches-election-fraud-themed-phishing-campaigns/
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-
-*Version*: 101 (<<unusual-network-connection-via-dllhost-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 107
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=1m [process
-where event.type == "start" and process.name : "dllhost.exe" and
-process.args_count == 1] [network where process.name : "dllhost.exe"
-and not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8",
-"169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.0.0.0/29",
-"192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32",
-"192.0.0.171/32", "192.0.2.0/24", "192.31.196.0/24",
-"192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
-"100.64.0.0/10", "192.175.48.0/24", "198.18.0.0/15",
-"198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
-"FE80::/10", "FF00::/8")]
+[source, js]
 ----------------------------------
+sequence by host.id, process.entity_id with maxspan=1m
+  [process where host.os.type == "windows" and event.type == "start" and process.name : "dllhost.exe" and process.args_count == 1]
+  [network where host.os.type == "windows" and process.name : "dllhost.exe" and
+   not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
+    "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
+    "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
+    "192.175.48.0/24", "198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
+    "FF00::/8")]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,31 +72,3 @@ and not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8",
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[unusual-network-connection-via-dllhost-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=1m [process
-where event.type in ("start", "process_started") and process.name :
-"dllhost.exe" and process.args_count == 1] [network where
-process.name : "dllhost.exe" and not cidrmatch(destination.ip,
-"10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12",
-"192.0.0.0/24", "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32",
-"192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
-"192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16",
-"192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
-"192.175.48.0/24", "198.18.0.0/15", "198.51.100.0/24",
-"203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10", "FF00::/8")]
-----------------------------------
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-network-connection-via-rundll32.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-network-connection-via-rundll32.asciidoc
index 05ae58a9b9..105b793074 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-network-connection-via-rundll32.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-network-connection-via-rundll32.asciidoc
@@ -5,66 +5,68 @@ Identifies unusual instances of rundll32.exe making outbound network connections
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 * https://redcanary.com/threat-detection-report/techniques/rundll32/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-
-*Version*: 102 (<<unusual-network-connection-via-rundll32-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Command and Control
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Unusual Network Connection via RunDLL32
+*Triage and analysis*
+
+
+
+*Investigating Unusual Network Connection via RunDLL32*
 
-RunDLL32 is a built-in Windows utility and also a vital component used by the operating system itself. The functionality
-provided by RunDLL32 to execute Dynamic Link Libraries (DLLs) is widely abused by attackers, because it makes it hard to
-differentiate malicious activity from normal operations.
 
-This rule looks for external network connections established using RunDLL32 when the utility is being executed with no
-arguments, which can potentially indicate command and control activity.
+RunDLL32 is a built-in Windows utility and also a vital component used by the operating system itself. The functionality provided by RunDLL32 to execute Dynamic Link Libraries (DLLs) is widely abused by attackers, because it makes it hard to differentiate malicious activity from normal operations.
 
-#### Possible investigation steps
+This rule looks for external network connections established using RunDLL32 when the utility is being executed with no arguments, which can potentially indicate command and control activity.
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Investigate the target host that RunDLL32 is communicating with.
   - Check if the domain is newly registered or unexpected.
@@ -72,47 +74,40 @@ for prevalence, whether they are located in expected locations, and if they are
 - Identify the target computer and its role in the IT environment.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system,
-persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 - Review the privileges assigned to the user to ensure that the least privilege principle is being followed.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=1m [process
-where event.type == "start" and process.name : "rundll32.exe" and
-process.args_count == 1] [network where process.name :
-"rundll32.exe" and not cidrmatch(destination.ip, "10.0.0.0/8",
-"127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
-"192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32",
-"192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
-"192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16",
-"192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
-"192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24",
-"203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
-"FF00::/8")]
+[source, js]
 ----------------------------------
+sequence by host.id, process.entity_id with maxspan=1m
+  [process where host.os.type == "windows" and event.type == "start" and process.name : "rundll32.exe" and process.args_count == 1]
+  [network where host.os.type == "windows" and process.name : "rundll32.exe" and
+   not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
+       "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32",
+       "192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
+       "100.64.0.0/10", "192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
+       "FE80::/10", "FF00::/8")]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -124,115 +119,19 @@ process.args_count == 1] [network where process.name :
 ** Name: System Binary Proxy Execution
 ** ID: T1218
 ** Reference URL: https://attack.mitre.org/techniques/T1218/
-
-[[unusual-network-connection-via-rundll32-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=1m [process
-where event.type in ("start", "process_started") and process.name :
-"rundll32.exe" and process.args_count == 1] [network where
-process.name : "rundll32.exe" and not cidrmatch(destination.ip,
-"10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12",
-"192.0.0.0/24", "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32",
-"192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32",
-"192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24",
-"192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
-"100.64.0.0/10", "192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24",
-"203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
-"FF00::/8")]
-----------------------------------
-
-Version 12 (8.4.0 release)::
-* Formatting only
-
-Version 10 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=1m [process
-where event.type in ("start", "process_started") and process.name :
-"rundll32.exe" and process.args_count == 1] [network where
-process.name : "rundll32.exe" and not cidrmatch(destination.ip,
-"10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16", "127.0.0.0/8",
-"FE80::/10", "::1/128")]
-----------------------------------
-
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id, process.entity_id with maxspan=1m [process
-where event.type in ("start", "process_started", "info") and
-process.name : "rundll32.exe" and process.args_count == 1] [network
-where process.name : "rundll32.exe" and network.protocol != "dns" and
-network.direction == "outgoing" and not cidrmatch(destination.ip,
-"10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16", "127.0.0.0/8")]
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by process.entity_id [process where process.name :
-"rundll32.exe" and event.type == "start"] [network where
-process.name : "rundll32.exe" and not cidrmatch(destination.ip,
-"10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16", "127.0.0.0/8")]
-----------------------------------
-
-Version 6 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:connection and
-process.name:rundll32.exe and not destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16 or 127.0.0.0/8)
-----------------------------------
-
-Version 5 (7.9.1 release)::
-* Formatting only
-
-Version 4 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:rundll32.exe and event.action:"Network connection
-detected (rule: NetworkConnect)" and not destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16 or 127.0.0.0/8)
-----------------------------------
-
-Version 3 (7.8.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:rundll32.exe and event.action:"Network connection
-detected (rule: NetworkConnect)" and not destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process.name:rundll32.exe and event.action:"Network connection
-detected (rule: NetworkConnect)" and not destination.ip:10.0.0.0/8 and
-not destination.ip:172.16.0.0/12 and not destination.ip:192.168.0.0/16
-----------------------------------
-
+* Sub-technique:
+** Name: Rundll32
+** ID: T1218.011
+** Reference URL: https://attack.mitre.org/techniques/T1218/011/
+* Tactic:
+** Name: Command and Control
+** ID: TA0011
+** Reference URL: https://attack.mitre.org/tactics/TA0011/
+* Technique:
+** Name: Application Layer Protocol
+** ID: T1071
+** Reference URL: https://attack.mitre.org/techniques/T1071/
+* Sub-technique:
+** Name: Web Protocols
+** ID: T1071.001
+** Reference URL: https://attack.mitre.org/techniques/T1071/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-network-destination-domain-name.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-network-destination-domain-name.asciidoc
index 7237d6eb71..45f3f564fb 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-network-destination-domain-name.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-network-destination-domain-name.asciidoc
@@ -5,58 +5,33 @@ A machine learning job detected an unusual network destination domain name. This
 
 *Rule type*: machine_learning
 
-*Machine learning job*: packetbeat_rare_server_domain
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Network
-* Threat Detection
-* ML
+*Tags*: 
 
-*Version*: 100 (<<unusual-network-destination-domain-name-history, version history>>)
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Web activity that occurs rarely in small quantities can trigger this alert. Possible examples are browsing technical support or vendor URLs that are used very sparsely. A user who visits a new and unique web destination may trigger this alert when the activity is sparse. Web applications that generate URLs unique to a transaction may trigger this when they are used sparsely. Web domains can be excluded in cases such as these.
-
-[[unusual-network-destination-domain-name-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-parent-child-relationship.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-parent-child-relationship.asciidoc
index 16e51ebf62..f69da0770f 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-parent-child-relationship.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-parent-child-relationship.asciidoc
@@ -5,94 +5,98 @@ Identifies Windows programs run from unexpected parent processes. This could ind
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/sbousseaden/Slides/blob/master/Hunting%20MindMaps/PNG/Windows%20Processes%20TH.map.png
 * https://www.andreafortuna.org/2017/06/15/standard-windows-processes-a-brief-reference/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-* Investigation Guide
-
-*Version*: 102 (<<unusual-parent-child-relationship-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Unusual Parent-Child Relationship
+*Triage and analysis*
+
+
 
-Windows internal/system processes have some characteristics that can be used to spot suspicious activities. One of these
-characteristics is parent-child relationships. These relationships can be used to baseline the typical behavior of the
-system and then alert on occurrences that don't comply with the baseline.
+*Investigating Unusual Parent-Child Relationship*
+
+
+Windows internal/system processes have some characteristics that can be used to spot suspicious activities. One of these characteristics is parent-child relationships. These relationships can be used to baseline the typical behavior of the system and then alert on occurrences that don't comply with the baseline.
 
 This rule uses this information to spot suspicious parent and child processes.
 
 > **Note**:
-> This investigation guide uses the [Osquery Markdown Plugin]({security-guide}/invest-guide-run-osquery.html) introduced in Elastic stack version 8.5.0. Older Elastic stacks versions will see unrendered markdown in this guide.
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications,
-and any spawned child processes.
-- Examine the host for derived artifacts that indicates suspicious activities:
+- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
+- Examine the host for derived artifacts that indicate suspicious activities:
   - Analyze the process executable using a private sandboxed analysis system.
   - Observe and collect information about the following activities in both the sandbox and the alert subject host:
     - Attempts to contact external domains and addresses.
-      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by
-      filtering by the process' `process.entity_id`.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
       - Examine the DNS cache for suspicious or anomalous entries.
-        - !{osquery{"query":"SELECT * FROM dns_cache", "label":"Osquery - Retrieve DNS Cache"}}
-    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related
-    processes in the process tree.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
     - Examine the host services for suspicious or anomalous entries.
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services","label":"Osquery - Retrieve All Services"}}
-      - !{osquery{"query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE "%LocalSystem" OR user_account LIKE "%LocalService" OR user_account LIKE "%NetworkService" OR user_account == null)","label":"Osquery - Retrieve Services Running on User Accounts"}}
-      - !{osquery{"query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != "trusted"","label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link"}}
-  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and
-  reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
+- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
 
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -100,69 +104,64 @@ and any spawned child processes.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name != null
-and ( /* suspicious parent processes */
-(process.name:"autochk.exe" and not process.parent.name:"smss.exe") or
-(process.name:("fontdrvhost.exe", "dwm.exe") and not
-process.parent.name:("wininit.exe", "winlogon.exe")) or
-(process.name:("consent.exe", "RuntimeBroker.exe", "TiWorker.exe") and
-not process.parent.name:"svchost.exe") or
-(process.name:"SearchIndexer.exe" and not
-process.parent.name:"services.exe") or
-(process.name:"SearchProtocolHost.exe" and not
-process.parent.name:("SearchIndexer.exe", "dllhost.exe")) or
-(process.name:"dllhost.exe" and not
-process.parent.name:("services.exe", "svchost.exe")) or
-(process.name:"smss.exe" and not process.parent.name:("System",
-"smss.exe")) or (process.name:"csrss.exe" and not
-process.parent.name:("smss.exe", "svchost.exe")) or
-(process.name:"wininit.exe" and not process.parent.name:"smss.exe") or
-(process.name:"winlogon.exe" and not process.parent.name:"smss.exe")
-or (process.name:("lsass.exe", "LsaIso.exe") and not
-process.parent.name:"wininit.exe") or (process.name:"LogonUI.exe"
-and not process.parent.name:("wininit.exe", "winlogon.exe")) or
-(process.name:"services.exe" and not
-process.parent.name:"wininit.exe") or (process.name:"svchost.exe"
-and not process.parent.name:("MsMpEng.exe", "services.exe")) or
-(process.name:"spoolsv.exe" and not
-process.parent.name:"services.exe") or (process.name:"taskhost.exe"
-and not process.parent.name:("services.exe", "svchost.exe")) or
-(process.name:"taskhostw.exe" and not
-process.parent.name:("services.exe", "svchost.exe")) or
-(process.name:"userinit.exe" and not process.parent.name:("dwm.exe",
-"winlogon.exe")) or (process.name:("wmiprvse.exe",
-"wsmprovhost.exe", "winrshost.exe") and not
-process.parent.name:"svchost.exe") or /* suspicious child processes
-*/ (process.parent.name:("SearchProtocolHost.exe", "taskhost.exe",
-"csrss.exe") and not process.name:("werfault.exe", "wermgr.exe",
-"WerFaultSecure.exe")) or (process.parent.name:"autochk.exe" and
-not process.name:("chkdsk.exe", "doskey.exe", "WerFault.exe")) or
-(process.parent.name:"smss.exe" and not process.name:("autochk.exe",
-"smss.exe", "csrss.exe", "wininit.exe", "winlogon.exe", "setupcl.exe",
-"WerFault.exe")) or (process.parent.name:"wermgr.exe" and not
-process.name:("WerFaultSecure.exe", "wermgr.exe", "WerFault.exe")) or
-(process.parent.name:"conhost.exe" and not
-process.name:("mscorsvw.exe", "wermgr.exe", "WerFault.exe",
-"WerFaultSecure.exe")) )
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+process.parent.name != null and
+ (
+   /* suspicious parent processes */
+   (process.name:"autochk.exe" and not process.parent.name:"smss.exe") or
+   (process.name:("fontdrvhost.exe", "dwm.exe") and not process.parent.name:("wininit.exe", "winlogon.exe")) or
+   (process.name:("consent.exe", "RuntimeBroker.exe", "TiWorker.exe") and not process.parent.name:"svchost.exe") or
+   (process.name:"SearchIndexer.exe" and not process.parent.name:"services.exe") or
+   (process.name:"SearchProtocolHost.exe" and not process.parent.name:("SearchIndexer.exe", "dllhost.exe")) or
+   (process.name:"dllhost.exe" and not process.parent.name:("services.exe", "svchost.exe")) or
+   (process.name:"smss.exe" and not process.parent.name:("System", "smss.exe")) or
+   (process.name:"csrss.exe" and not process.parent.name:("smss.exe", "svchost.exe")) or
+   (process.name:"wininit.exe" and not process.parent.name:"smss.exe") or
+   (process.name:"winlogon.exe" and not process.parent.name:"smss.exe") or
+   (process.name:("lsass.exe", "LsaIso.exe") and not process.parent.name:"wininit.exe") or
+   (process.name:"LogonUI.exe" and not process.parent.name:("wininit.exe", "winlogon.exe")) or
+   (process.name:"services.exe" and not process.parent.name:"wininit.exe") or
+   (process.name:"svchost.exe" and not process.parent.name:("MsMpEng.exe", "services.exe", "svchost.exe")) or
+   (process.name:"spoolsv.exe" and not process.parent.name:"services.exe") or
+   (process.name:"taskhost.exe" and not process.parent.name:("services.exe", "svchost.exe", "ngentask.exe")) or
+   (process.name:"taskhostw.exe" and not process.parent.name:("services.exe", "svchost.exe")) or
+   (process.name:"userinit.exe" and not process.parent.name:("dwm.exe", "winlogon.exe")) or
+   (process.name:("wmiprvse.exe", "wsmprovhost.exe", "winrshost.exe") and not process.parent.name:"svchost.exe") or
+   /* suspicious child processes */
+   (process.parent.name:("SearchProtocolHost.exe", "taskhost.exe", "csrss.exe") and not process.name:("werfault.exe", "wermgr.exe", "WerFaultSecure.exe", "conhost.exe")) or
+   (process.parent.name:"autochk.exe" and not process.name:("chkdsk.exe", "doskey.exe", "WerFault.exe")) or
+   (process.parent.name:"smss.exe" and not process.name:("autochk.exe", "smss.exe", "csrss.exe", "wininit.exe", "winlogon.exe", "setupcl.exe", "WerFault.exe")) or
+   (process.parent.name:"wermgr.exe" and not process.name:("WerFaultSecure.exe", "wermgr.exe", "WerFault.exe")) or
+   (process.parent.name:"conhost.exe" and not process.name:("mscorsvw.exe", "wermgr.exe", "WerFault.exe", "WerFaultSecure.exe"))
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -174,196 +173,7 @@ process.name:("mscorsvw.exe", "wermgr.exe", "WerFault.exe",
 ** Name: Process Injection
 ** ID: T1055
 ** Reference URL: https://attack.mitre.org/techniques/T1055/
-
-[[unusual-parent-child-relationship-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name != null and ( /* suspicious parent processes
-*/ (process.name:"autochk.exe" and not
-process.parent.name:"smss.exe") or
-(process.name:("fontdrvhost.exe", "dwm.exe") and not
-process.parent.name:("wininit.exe", "winlogon.exe")) or
-(process.name:("consent.exe", "RuntimeBroker.exe", "TiWorker.exe") and
-not process.parent.name:"svchost.exe") or
-(process.name:"SearchIndexer.exe" and not
-process.parent.name:"services.exe") or
-(process.name:"SearchProtocolHost.exe" and not
-process.parent.name:("SearchIndexer.exe", "dllhost.exe")) or
-(process.name:"dllhost.exe" and not
-process.parent.name:("services.exe", "svchost.exe")) or
-(process.name:"smss.exe" and not process.parent.name:("System",
-"smss.exe")) or (process.name:"csrss.exe" and not
-process.parent.name:("smss.exe", "svchost.exe")) or
-(process.name:"wininit.exe" and not process.parent.name:"smss.exe") or
-(process.name:"winlogon.exe" and not process.parent.name:"smss.exe")
-or (process.name:("lsass.exe", "LsaIso.exe") and not
-process.parent.name:"wininit.exe") or (process.name:"LogonUI.exe"
-and not process.parent.name:("wininit.exe", "winlogon.exe")) or
-(process.name:"services.exe" and not
-process.parent.name:"wininit.exe") or (process.name:"svchost.exe"
-and not process.parent.name:("MsMpEng.exe", "services.exe")) or
-(process.name:"spoolsv.exe" and not
-process.parent.name:"services.exe") or (process.name:"taskhost.exe"
-and not process.parent.name:("services.exe", "svchost.exe")) or
-(process.name:"taskhostw.exe" and not
-process.parent.name:("services.exe", "svchost.exe")) or
-(process.name:"userinit.exe" and not process.parent.name:("dwm.exe",
-"winlogon.exe")) or (process.name:("wmiprvse.exe",
-"wsmprovhost.exe", "winrshost.exe") and not
-process.parent.name:"svchost.exe") or /* suspicious child processes
-*/ (process.parent.name:("SearchProtocolHost.exe", "taskhost.exe",
-"csrss.exe") and not process.name:("werfault.exe", "wermgr.exe",
-"WerFaultSecure.exe")) or (process.parent.name:"autochk.exe" and
-not process.name:("chkdsk.exe", "doskey.exe", "WerFault.exe")) or
-(process.parent.name:"smss.exe" and not process.name:("autochk.exe",
-"smss.exe", "csrss.exe", "wininit.exe", "winlogon.exe", "setupcl.exe",
-"WerFault.exe")) or (process.parent.name:"wermgr.exe" and not
-process.name:("WerFaultSecure.exe", "wermgr.exe", "WerFault.exe")) or
-(process.parent.name:"conhost.exe" and not
-process.name:("mscorsvw.exe", "wermgr.exe", "WerFault.exe",
-"WerFaultSecure.exe")) )
-----------------------------------
-
-Version 13 (8.4.0 release)::
-* Formatting only
-
-Version 11 (8.2.0 release)::
-* Formatting only
-
-Version 10 (7.16.0 release)::
-* Formatting only
-
-Version 9 (7.15.0 release)::
-* Formatting only
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.executable:* and (process.parent.name:autochk.exe and
-not process.name:(chkdsk.exe or doskey.exe or WerFault.exe) or
-process.parent.name:smss.exe and not process.name:(autochk.exe or
-smss.exe or csrss.exe or wininit.exe or winlogon.exe or WerFault.exe)
-or process.name:autochk.exe and not process.parent.name:smss.exe or
-process.name:(fontdrvhost.exe or dwm.exe) and not
-process.parent.name:(wininit.exe or winlogon.exe) or
-process.name:(consent.exe or RuntimeBroker.exe or TiWorker.exe) and
-not process.parent.name:svchost.exe or process.name:wermgr.exe and not
-process.parent.name:(svchost.exe or TiWorker.exe) or
-process.name:SearchIndexer.exe and not
-process.parent.name:services.exe or
-process.name:SearchProtocolHost.exe and not
-process.parent.name:(SearchIndexer.exe or dllhost.exe) or
-process.name:dllhost.exe and not process.parent.name:(services.exe or
-svchost.exe) or process.name:smss.exe and not
-process.parent.name:(System or smss.exe) or process.name:csrss.exe and
-not process.parent.name:(smss.exe or svchost.exe) or
-process.name:wininit.exe and not process.parent.name:smss.exe or
-process.name:winlogon.exe and not process.parent.name:smss.exe or
-process.name:(lsass.exe or LsaIso.exe) and not
-process.parent.name:wininit.exe or process.name:LogonUI.exe and not
-process.parent.name:(wininit.exe or winlogon.exe) or
-process.name:services.exe and not process.parent.name:wininit.exe or
-process.name:svchost.exe and not process.parent.name:(MsMpEng.exe or
-services.exe) or process.name:spoolsv.exe and not
-process.parent.name:services.exe or process.name:taskhost.exe and not
-process.parent.name:(services.exe or svchost.exe) or
-process.name:taskhostw.exe and not process.parent.name:(services.exe
-or svchost.exe) or process.name:userinit.exe and not
-process.parent.name:(dwm.exe or winlogon.exe))
-----------------------------------
-
-Version 5 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.executable:* and (process.name:smss.exe and not
-process.parent.name:(System or smss.exe) or process.name:csrss.exe and
-not process.parent.name:(smss.exe or svchost.exe) or
-process.name:wininit.exe and not process.parent.name:smss.exe or
-process.name:winlogon.exe and not process.parent.name:smss.exe or
-process.name:lsass.exe and not process.parent.name:wininit.exe or
-process.name:LogonUI.exe and not process.parent.name:(wininit.exe or
-winlogon.exe) or process.name:services.exe and not
-process.parent.name:wininit.exe or process.name:svchost.exe and not
-process.parent.name:(MsMpEng.exe or services.exe) or
-process.name:spoolsv.exe and not process.parent.name:services.exe or
-process.name:taskhost.exe and not process.parent.name:(services.exe or
-svchost.exe) or process.name:taskhostw.exe and not
-process.parent.name:(services.exe or svchost.exe) or
-process.name:userinit.exe and not process.parent.name:(dwm.exe or
-winlogon.exe))
-----------------------------------
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.parent.executable:* and (process.name:smss.exe and not
-process.parent.name:(System or smss.exe) or process.name:csrss.exe and
-not process.parent.name:(smss.exe or svchost.exe) or
-process.name:wininit.exe and not process.parent.name:smss.exe or
-process.name:winlogon.exe and not process.parent.name:smss.exe or
-process.name:lsass.exe and not process.parent.name:wininit.exe or
-process.name:LogonUI.exe and not process.parent.name:(wininit.exe or
-winlogon.exe) or process.name:services.exe and not
-process.parent.name:wininit.exe or process.name:svchost.exe and not
-process.parent.name:(MsMpEng.exe or services.exe) or
-process.name:spoolsv.exe and not process.parent.name:services.exe or
-process.name:taskhost.exe and not process.parent.name:(services.exe or
-svchost.exe) or process.name:taskhostw.exe and not
-process.parent.name:(services.exe or svchost.exe) or
-process.name:userinit.exe and not process.parent.name:(dwm.exe or
-winlogon.exe))
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.parent.executable:* and ( (process.name:"smss.exe" and not
-process.parent.name:("System" or "smss.exe")) or
-(process.name:"csrss.exe" and not process.parent.name:("smss.exe" or
-"svchost.exe")) or (process.name:"wininit.exe" and not
-process.parent.name:"smss.exe") or (process.name:"winlogon.exe" and
-not process.parent.name:"smss.exe") or (process.name:"lsass.exe" and
-not process.parent.name:"wininit.exe") or (process.name:"LogonUI.exe"
-and not process.parent.name:("winlogon.exe" or "wininit.exe")) or
-(process.name:"services.exe" and not
-process.parent.name:"wininit.exe") or (process.name:"svchost.exe" and
-not process.parent.name:("services.exe" or "MsMpEng.exe")) or
-(process.name:"spoolsv.exe" and not
-process.parent.name:"services.exe") or (process.name:"taskhost.exe"
-and not process.parent.name:("services.exe" or "svchost.exe")) or
-(process.name:"taskhostw.exe" and not
-process.parent.name:("services.exe" or "svchost.exe")) or
-(process.name:"userinit.exe" and not process.parent.name:("dwm.exe" or
-"winlogon.exe")) )
-----------------------------------
-
+* Sub-technique:
+** Name: Process Hollowing
+** ID: T1055.012
+** Reference URL: https://attack.mitre.org/techniques/T1055/012/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-parent-process-for-cmd-exe.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-parent-process-for-cmd-exe.asciidoc
new file mode 100644
index 0000000000..5e236d32b9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-parent-process-for-cmd-exe.asciidoc
@@ -0,0 +1,104 @@
+[[unusual-parent-process-for-cmd-exe]]
+=== Unusual Parent Process for cmd.exe
+
+Identifies a suspicious parent child process relationship with cmd.exe descending from an unusual process.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 110
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "cmd.exe" and
+  process.parent.name : ("lsass.exe",
+                         "csrss.exe",
+                         "epad.exe",
+                         "regsvr32.exe",
+                         "dllhost.exe",
+                         "LogonUI.exe",
+                         "wermgr.exe",
+                         "spoolsv.exe",
+                         "jucheck.exe",
+                         "jusched.exe",
+                         "ctfmon.exe",
+                         "taskhostw.exe",
+                         "GoogleUpdate.exe",
+                         "sppsvc.exe",
+                         "sihost.exe",
+                         "slui.exe",
+                         "SIHClient.exe",
+                         "SearchIndexer.exe",
+                         "SearchProtocolHost.exe",
+                         "FlashPlayerUpdateService.exe",
+                         "WerFault.exe",
+                         "WUDFHost.exe",
+                         "unsecapp.exe",
+                         "wlanext.exe" ) and
+  not (process.parent.name : "dllhost.exe" and process.parent.args : "/Processid:{CA8C87C1-929D-45BA-94DB-EF8E6CB346AD}")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-persistence-via-services-registry.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-persistence-via-services-registry.asciidoc
index 2cbf39ea65..bf71943d64 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-persistence-via-services-registry.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-persistence-via-services-registry.asciidoc
@@ -5,62 +5,72 @@ Identifies processes modifying the services registry key directly, instead of th
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.registry-*
+* endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
+*Tags*: 
 
-*Version*: 100 (<<unusual-persistence-via-services-registry-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where registry.path :
-("HKLM\\SYSTEM\\ControlSet*\\Services\\*\\ServiceDLL",
-"HKLM\\SYSTEM\\ControlSet*\\Services\\*\\ImagePath") and not
-registry.data.strings : ("?:\\windows\\system32\\Drivers\\*.sys",
-"\\SystemRoot\\System32\\drivers\\*.sys",
-"\\??\\?:\\Windows\\system32\\Drivers\\*.SYS",
-"system32\\DRIVERS\\USBSTOR") and not (process.name :
-"procexp??.exe" and registry.data.strings : "?:\\*\\procexp*.sys") and
-not process.executable : ("?:\\Program Files\\*.exe",
-"?:\\Program Files (x86)\\*.exe",
-"?:\\Windows\\System32\\svchost.exe",
-"?:\\Windows\\winsxs\\*\\TiWorker.exe",
-"?:\\Windows\\System32\\drvinst.exe",
-"?:\\Windows\\System32\\services.exe",
-"?:\\Windows\\System32\\msiexec.exe",
-"?:\\Windows\\System32\\regsvr32.exe")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type == "change" and
+  registry.path : (
+      "HKLM\\SYSTEM\\ControlSet*\\Services\\*\\ServiceDLL",
+      "HKLM\\SYSTEM\\ControlSet*\\Services\\*\\ImagePath",
+      "\\REGISTRY\\MACHINE\\SYSTEM\\ControlSet*\\Services\\*\\ServiceDLL",
+      "\\REGISTRY\\MACHINE\\SYSTEM\\ControlSet*\\Services\\*\\ImagePath"
+  ) and not registry.data.strings : (
+      "?:\\windows\\system32\\Drivers\\*.sys",
+      "\\SystemRoot\\System32\\drivers\\*.sys",
+      "\\??\\?:\\Windows\\system32\\Drivers\\*.SYS",
+      "system32\\DRIVERS\\USBSTOR") and
+  not (process.name : "procexp??.exe" and registry.data.strings : "?:\\*\\procexp*.sys") and
+  not process.executable : (
+      "?:\\Program Files\\*.exe",
+      "?:\\Program Files (x86)\\*.exe",
+      "?:\\Windows\\System32\\svchost.exe",
+      "?:\\Windows\\winsxs\\*\\TiWorker.exe",
+      "?:\\Windows\\System32\\drvinst.exe",
+      "?:\\Windows\\System32\\services.exe",
+      "?:\\Windows\\System32\\msiexec.exe",
+      "?:\\Windows\\System32\\regsvr32.exe")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,43 +82,15 @@ not process.executable : ("?:\\Program Files\\*.exe",
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[unusual-persistence-via-services-registry-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.1.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where registry.path :
-("HKLM\\SYSTEM\\ControlSet*\\Services\\*\\ServiceDLL",
-"HKLM\\SYSTEM\\ControlSet*\\Services\\*\\ImagePath") and not
-registry.data.strings : ("C:\\windows\\system32\\Drivers\\*.sys",
-"\\SystemRoot\\System32\\drivers\\*.sys",
-"system32\\DRIVERS\\USBSTOR") and not (process.name :
-"procexp??.exe" and registry.data.strings : "C:\\*\\procexp*.sys") and
-not process.executable : ("C:\\Program Files*\\*.exe",
-"C:\\Windows\\System32\\svchost.exe",
-"C:\\Windows\\winsxs\\*\\TiWorker.exe",
-"C:\\Windows\\System32\\drvinst.exe",
-"C:\\Windows\\System32\\services.exe",
-"C:\\Windows\\System32\\msiexec.exe",
-"C:\\Windows\\System32\\regsvr32.exe")
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-print-spooler-child-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-print-spooler-child-process.asciidoc
index 4ec9026f65..876bfa3c45 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-print-spooler-child-process.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-print-spooler-child-process.asciidoc
@@ -5,78 +5,81 @@ Detects unusual Print Spooler service (spoolsv.exe) child processes. This may in
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-34527
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
-
-*Version*: 100 (<<unusual-print-spooler-child-process-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Use Case: Vulnerability
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Install or update of a legitimate printing driver. Verify the printer driver file metadata such as manufacturer and signature information.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"spoolsv.exe" and (?process.Ext.token.integrity_level_name : "System"
-or ?winlog.event_data.IntegrityLevel : "System") and /* exclusions
-for FP control below */ not process.name : ("splwow64.exe",
-"PDFCreator.exe", "acrodist.exe", "spoolsv.exe", "msiexec.exe",
-"route.exe", "WerFault.exe") and not process.command_line :
-"*\\WINDOWS\\system32\\spool\\DRIVERS*" and not (process.name :
-"net.exe" and process.command_line : ("*stop*", "*start*")) and not
-(process.name : ("cmd.exe", "powershell.exe") and process.command_line
-: ("*.spl*", "*\\program files*", "*route add*")) and not
-(process.name : "netsh.exe" and process.command_line : ("*add
-portopening*", "*rule name*")) and not (process.name : "regsvr32.exe"
-and process.command_line : "*PrintConfig.dll*")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ process.parent.name : "spoolsv.exe" and process.command_line != null and 
+ (?process.Ext.token.integrity_level_name : "System" or ?winlog.event_data.IntegrityLevel : "System") and
+
+ /* exclusions for FP control below */
+ not process.name : ("splwow64.exe", "PDFCreator.exe", "acrodist.exe", "spoolsv.exe", "msiexec.exe", "route.exe", "WerFault.exe") and
+ not process.command_line : "*\\WINDOWS\\system32\\spool\\DRIVERS*" and
+ not (process.name : "net.exe" and process.command_line : ("*stop*", "*start*")) and
+ not (process.name : ("cmd.exe", "powershell.exe") and process.command_line : ("*.spl*", "*\\program files*", "*route add*")) and
+ not (process.name : "netsh.exe" and process.command_line : ("*add portopening*", "*rule name*")) and
+ not (process.name : "regsvr32.exe" and process.command_line : "*PrintConfig.dll*") and
+ not process.executable : (
+    "?:\\Program Files (x86)\\CutePDF Writer\\CPWriter2.exe",
+    "?:\\Program Files (x86)\\GPLGS\\gswin32c.exe"
+ )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -88,55 +91,3 @@ and process.command_line : "*PrintConfig.dll*")
 ** Name: Exploitation for Privilege Escalation
 ** ID: T1068
 ** Reference URL: https://attack.mitre.org/techniques/T1068/
-
-[[unusual-print-spooler-child-process-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"spoolsv.exe" and (process.Ext.token.integrity_level_name : "System"
-or winlog.event_data.IntegrityLevel : "System") and /* exclusions
-for FP control below */ not process.name : ("splwow64.exe",
-"PDFCreator.exe", "acrodist.exe", "spoolsv.exe", "msiexec.exe",
-"route.exe", "WerFault.exe") and not process.command_line :
-"*\\WINDOWS\\system32\\spool\\DRIVERS*" and not (process.name :
-"net.exe" and process.command_line : ("*stop*", "*start*")) and not
-(process.name : ("cmd.exe", "powershell.exe") and process.command_line
-: ("*.spl*", "*\\program files*", "*route add*")) and not
-(process.name : "netsh.exe" and process.command_line : ("*add
-portopening*", "*rule name*")) and not (process.name : "regsvr32.exe"
-and process.command_line : "*PrintConfig.dll*")
-----------------------------------
-
-Version 3 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"spoolsv.exe" and user.id : "S-1-5-18" and /* exclusions for FP
-control below */ not process.name : ("splwow64.exe",
-"PDFCreator.exe", "acrodist.exe", "spoolsv.exe", "msiexec.exe",
-"route.exe", "WerFault.exe") and not process.command_line :
-"*\\WINDOWS\\system32\\spool\\DRIVERS*" and not (process.name :
-"net.exe" and process.command_line : ("*stop*", "*start*")) and not
-(process.name : ("cmd.exe", "powershell.exe") and process.command_line
-: ("*.spl*", "*\\program files*", "*route add*")) and not
-(process.name : "netsh.exe" and process.command_line : ("*add
-portopening*", "*rule name*")) and not (process.name : "regsvr32.exe"
-and process.command_line : "*PrintConfig.dll*")
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-process-execution-on-wbem-path.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-process-execution-on-wbem-path.asciidoc
new file mode 100644
index 0000000000..adb251a5b4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-process-execution-on-wbem-path.asciidoc
@@ -0,0 +1,77 @@
+[[unusual-process-execution-on-wbem-path]]
+=== Unusual Process Execution on WBEM Path
+
+Identifies unusual processes running from the WBEM path, uncommon outside WMI-related Windows processes.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* logs-system.security*
+* winlogbeat-*
+* logs-windows.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Rule Type: BBR
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.executable : ("?:\\Windows\\System32\\wbem\\*", "?:\\Windows\\SysWow64\\wbem\\*") and
+  not process.name : (
+    "mofcomp.exe",
+    "scrcons.exe",
+    "unsecapp.exe",
+    "wbemtest.exe",
+    "winmgmt.exe",
+    "wmiadap.exe",
+    "wmiapsrv.exe",
+    "wmic.exe",
+    "wmiprvse.exe"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-process-execution-path-alternate-data-stream.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-process-execution-path-alternate-data-stream.asciidoc
index bc18e1826c..651dd85e16 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-process-execution-path-alternate-data-stream.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-process-execution-path-alternate-data-stream.asciidoc
@@ -5,61 +5,67 @@ Identifies processes running from an Alternate Data Stream. This is uncommon for
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 * endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 101 (<<unusual-process-execution-path-alternate-data-stream-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.args : "?:\\*:*" and
-process.args_count == 1
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.args : "?:\\*:*" and process.args_count == 1
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -71,37 +77,7 @@ process.args_count == 1
 ** Name: Hide Artifacts
 ** ID: T1564
 ** Reference URL: https://attack.mitre.org/techniques/T1564/
-
-[[unusual-process-execution-path-alternate-data-stream-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.2.0 release)::
-* Formatting only
-
-Version 5 (7.16.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.args : "C:\\*:*"
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: NTFS File Attributes
+** ID: T1564.004
+** Reference URL: https://attack.mitre.org/techniques/T1564/004/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-process-extension.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-process-extension.asciidoc
new file mode 100644
index 0000000000..de64980848
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-process-extension.asciidoc
@@ -0,0 +1,92 @@
+[[unusual-process-extension]]
+=== Unusual Process Extension
+
+Identifies processes running with unusual extensions that are not typically valid for Windows executables.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.executable : "?*" and 
+  not process.name : ("*.exe", "*.com", "*.scr", "*.tmp", "*.dat") and
+  not process.executable : 
+    (
+      "MemCompression",
+      "Registry",
+      "vmmem",
+      "vmmemWSL",
+      "?:\\Program Files\\Dell\\SupportAssistAgent\\*.p5x",
+      "?:\\Program Files\\Docker\\Docker\\com.docker.service",
+      "?:\\Users\\*\\AppData\\Local\\Intel\\AGS\\Libs\\AGSRunner.bin",
+      "\\Device\\Mup\\*\\Software Management\\Select.Html.dep",
+      "?:\\DJJApplications\\MedicalRecords\\bin\\Select.Html.dep",
+      "?:\\ProgramData\\Software Management\\Select.Html.dep",
+      "?:\\Program Files (x86)\\EnCase Applications\\Examiner Service\\EnCase64\\enhkey.dll",
+      "?:\\Program Files (x86)\\Panda Security\\WAC\\PSNAEInj64.dll",
+      "?:\\Program Files (x86)\\Johnson Controls\\LicenseActivator\\crp32002.ngn"
+    ) and
+  not (
+    (process.name : "C9632CF058AE4321B6B0B5EA39B710FE" and process.code_signature.subject_name == "Dell Inc") or
+    (process.name : "*.upd" and process.code_signature.subject_name == "Bloomberg LP") or
+    (process.name: "FD552E21-686E-413C-931D-3B82A9D29F3B" and process.code_signature.subject_name: "Adobe Inc.") or
+    (process.name: "3B91051C-AE82-43C9-BCEF-0309CD2DD9EB" and process.code_signature.subject_name: "McAfee, LLC") or
+    (process.name: "soffice.bin" and process.code_signature.subject_name: "The Document Foundation") or
+    (process.name: ("VeeamVixProxy_*", "{????????-????-????-????-????????????}") and process.code_signature.subject_name: "Veeam Software Group GmbH") or
+    (process.name: "1cv8p64.bin" and process.code_signature.subject_name: "LLC 1C-Soft") or
+    (process.name: "AGSRunner.bin" and process.code_signature.subject_name: "Intel Corporation")
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
+* Sub-technique:
+** Name: Masquerade File Type
+** ID: T1036.008
+** Reference URL: https://attack.mitre.org/techniques/T1036/008/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-process-for-a-linux-host.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-process-for-a-linux-host.asciidoc
index 7db8c0e37e..673eacf555 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-process-for-a-linux-host.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-process-for-a-linux-host.asciidoc
@@ -5,102 +5,102 @@ Identifies rare processes that do not usually run on individual hosts, which can
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_rare_process_by_host_linux
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Persistence
+
+*Version*: 104
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
-* Persistence
 
-*Version*: 100 (<<unusual-process-for-a-linux-host-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.7.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-A newly installed program or one that runs rarely as part of a monthly or quarterly workflow could trigger this alert.
 
-==== Investigation guide
 
+*Investigating Unusual Process For a Linux Host*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating an Unusual Linux Process
-Detection alerts from this rule indicate the presence of a Linux process that is rare and unusual for the host it ran on. Here are some possible avenues of investigation:
-- Consider the user as identified by the username field. Is this program part of an expected workflow for the user who ran this program on this host?
-- Examine the history of execution. If this process only manifested recently, it might be part of a new software package. If it has a consistent cadence (for example if it runs monthly or quarterly), it might be part of a monthly or quarterly business process.
-- Examine the process arguments, title and working directory. These may provide indications as to the source of the program or the nature of the tasks it is performing.
-----------------------------------
+Searching for abnormal Linux processes is a good methodology to find potentially malicious activity within a network. Understanding what is commonly run within an environment and developing baselines for legitimate activity can help uncover potential malware and suspicious behaviors.
 
-==== Threat mapping
+This rule uses a machine learning job to detect a Linux process that is rare and unusual for an individual Linux host in your environment.
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Persistence
-** ID: TA0003
-** Reference URL: https://attack.mitre.org/tactics/TA0003/
-* Technique:
-** Name: Create or Modify System Process
-** ID: T1543
-** Reference URL: https://attack.mitre.org/techniques/T1543/
+*Possible investigation steps*
+
 
-[[unusual-process-for-a-linux-host-history]]
-==== Rule version history
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, and whether they are located in expected locations.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Consider the user as identified by the `user.name` field. Is this program part of an expected workflow for the user who ran this program on this host?
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Validate if the activity has a consistent cadence (for example, if it runs monthly or quarterly), as it could be part of a monthly or quarterly business process.
+- Examine the arguments and working directory of the process. These may provide indications as to the source of the program or the nature of the tasks it is performing.
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 9 (8.4.0 release)::
-* Formatting only
+*False Positive Analysis*
 
-Version 8 (8.3.0 release)::
-* Formatting only
 
-Version 7 (7.15.0 release)::
-* Formatting only
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
 
-Version 6 (7.14.0 release)::
-* Formatting only
 
-Version 5 (7.13.0 release)::
-* Formatting only
+*Response and Remediation*
 
-Version 4 (7.12.0 release)::
-* Formatting only
 
-Version 3 (7.10.0 release)::
-* Formatting only
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 2 (7.9.0 release)::
-* Formatting only
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Systemd Service
+** ID: T1543.002
+** Reference URL: https://attack.mitre.org/techniques/T1543/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-process-for-a-windows-host.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-process-for-a-windows-host.asciidoc
index 1ee5e0a99f..37b22f35ca 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-process-for-a-windows-host.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-process-for-a-windows-host.asciidoc
@@ -5,143 +5,129 @@ Identifies rare processes that do not usually run on individual hosts, which can
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_rare_process_by_host_windows
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Persistence
+* Resources: Investigation Guide
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
-* Persistence
-* Investigation Guide
 
-*Version*: 102 (<<unusual-process-for-a-windows-host-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.7.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-A newly installed program or one that runs rarely as part of a monthly or quarterly workflow could trigger this alert.
 
-==== Investigation guide
 
+*Investigating Unusual Process For a Windows Host*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-###  Investigating an Unusual Windows Process
+Searching for abnormal Windows processes is a good methodology to find potentially malicious activity within a network. Understanding what is commonly run within an environment and developing baselines for legitimate activity can help uncover potential malware and suspicious behaviors.
 
-Searching for abnormal Windows processes is a good methodology to find potentially malicious activity within a network.
-Understanding what is commonly run within an environment and developing baselines for legitimate activity can help
-uncover potential malware and suspicious behaviors.
+This rule uses a machine learning job to detect a Windows process that is rare and unusual for an individual Windows host in your environment.
 
-#### Possible investigation steps:
-- Consider the user as identified by the `user.name` field. Is this program part of an expected workflow for the user who ran this program on this host?
-- Examine the history of execution. If this process only manifested recently, it might be part of a new software package. If it has a consistent cadence (for example if it runs monthly or quarterly), it might be part of a monthly or quarterly business process.
-- Examine the process metadata like the values of the Company, Description and Product fields which may indicate whether the program is associated with an expected software vendor or package.
-- Examine arguments and working directory. These may provide indications as to the source of the program or the nature of the tasks it is performing.
-- Consider the same for the parent process. If the parent process is a legitimate system utility or service, this could be related to software updates or system management. If the parent process is something user-facing like an Office application, this process could be more suspicious.
-- If you have file hash values in the event data, and you suspect malware, you can optionally run a search for the file hash to see if the file is identified as malware by anti-malware tools.
-
-### False Positive Analysis
-- Validate the unusual Windows process is not related to new benign software installation activity. If related to
-legitimate software, this can be done by leveraging the exception workflow in the Kibana Security App or Elasticsearch
-API to tune this rule to your environment.
-- Try to understand the context of the execution by thinking about the user, machine, or business purpose.  It's possible that a small number of endpoints
-such as servers that have very unique software that might appear to be unusual, but satisfy a specific business need.
-
-### Related Rules
-- Anomalous Windows Process Creation
-- Unusual Windows Path Activity
-- Unusual Windows Process Calling the Metadata Service
-
-### Response and Remediation
-- This rule is related to process execution events and should be immediately reviewed and investigated to determine if malicious.
-- Based on validation and if malicious, the impacted machine should be isolated and analyzed to determine other post-compromise
-behavior such as setting up persistence or performing lateral movement.
-- Look into preventive measures such as Windows Defender Application Control and AppLocker to gain better control on
-what is allowed to run on Windows infrastructure.
-
-----------------------------------
-
-==== Threat mapping
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 
-*Framework*: MITRE ATT&CK^TM^
 
-* Tactic:
-** Name: Persistence
-** ID: TA0003
-** Reference URL: https://attack.mitre.org/tactics/TA0003/
-* Technique:
-** Name: Create or Modify System Process
-** ID: T1543
-** Reference URL: https://attack.mitre.org/techniques/T1543/
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+  - If the parent process is a legitimate system utility or service, this could be related to software updates or system management. If the parent process is something user-facing like an Office application, this process could be more suspicious.
+  - Investigate the process metadata — such as the digital signature, directory, etc. — to obtain more context that can indicate whether the executable is associated with an expected software vendor or package.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Consider the user as identified by the `user.name` field. Is this program part of an expected workflow for the user who ran this program on this host?
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Validate if the activity has a consistent cadence (for example, if it runs monthly or quarterly), as it could be part of a monthly or quarterly business process.
+- Examine the arguments and working directory of the process. These may provide indications as to the source of the program or the nature of the tasks it is performing.
+- Examine the host for derived artifacts that indicate suspicious activities:
+  - Analyze the process executable using a private sandboxed analysis system.
+  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE NOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR user_account == null)"}}
+      - !{osquery{"label":"Retrieve Service Unisgned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid, services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path = authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'"}}
+  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-[[unusual-process-for-a-windows-host-history]]
-==== Rule version history
 
-Version 102 (8.6.0 release)::
-* Formatting only
+*False Positive Analysis*
 
-Version 101 (8.5.0 release)::
-* Formatting only
 
-Version 12 (8.4.0 release)::
-* Formatting only
+- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
+- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
 
-Version 11 (8.3.0 release)::
-* Formatting only
 
-Version 10 (8.2.0 release)::
-* Formatting only
+*Related Rules*
 
-Version 9 (8.1.0 release)::
-* Formatting only
 
-Version 8 (7.16.0 release)::
-* Formatting only
+- Unusual Process For a Windows Host - 6d448b96-c922-4adb-b51c-b767f1ea5b76
+- Unusual Windows Path Activity - 445a342e-03fb-42d0-8656-0367eb2dead5
+- Unusual Windows Process Calling the Metadata Service - abae61a8-c560-4dbd-acca-1e1438bff36b
 
-Version 7 (7.15.0 release)::
-* Formatting only
 
-Version 6 (7.14.0 release)::
-* Formatting only
+*Response and Remediation*
 
-Version 5 (7.13.0 release)::
-* Formatting only
 
-Version 4 (7.12.0 release)::
-* Formatting only
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- If the triage identified malware, search the environment for additional compromised hosts.
+  - Implement temporary network rules, procedures, and segmentation to contain the malware.
+  - Stop suspicious processes.
+  - Immediately block the identified indicators of compromise (IoCs).
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
+- Remove and block malicious artifacts identified during triage.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-Version 3 (7.10.0 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Formatting only
+*Framework*: MITRE ATT&CK^TM^
 
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create or Modify System Process
+** ID: T1543
+** Reference URL: https://attack.mitre.org/techniques/T1543/
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-process-for-mssql-service-accounts.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-process-for-mssql-service-accounts.asciidoc
new file mode 100644
index 0000000000..4eb35cc2da
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-process-for-mssql-service-accounts.asciidoc
@@ -0,0 +1,111 @@
+[[unusual-process-for-mssql-service-accounts]]
+=== Unusual Process For MSSQL Service Accounts
+
+Identifies unusual process executions using MSSQL Service accounts, which can indicate the exploitation/compromise of SQL instances. Attackers may exploit exposed MSSQL instances for initial access or lateral movement.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.microsoft.com/en-us/security/blog/2023/08/24/flax-typhoon-using-legitimate-software-to-quietly-access-taiwanese-organizations/
+* https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions?view=sql-server-ver16
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Persistence
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and host.os.type == "windows" and
+  user.name : (
+    "SQLSERVERAGENT", "SQLAGENT$*",
+    "MSSQLSERVER", "MSSQL$*",
+    "MSSQLServerOLAPService",
+    "ReportServer*", "MsDtsServer150",
+    "MSSQLFDLauncher*",
+    "SQLServer2005SQLBrowserUser$*",
+    "SQLWriter", "winmgmt"
+  ) and user.domain : "NT SERVICE" and
+  not (
+    (
+      process.name : (
+        "sqlceip.exe", "sqlservr.exe", "sqlagent.exe",
+        "msmdsrv.exe", "ReportingServicesService.exe",
+        "MsDtsSrvr.exe", "sqlbrowser.exe", "DTExec.exe",
+        "SQLPS.exe", "fdhost.exe", "fdlauncher.exe",
+        "SqlDumper.exe", "sqlsqm.exe", "DatabaseMail.exe",
+        "ISServerExec.exe", "Microsoft.ReportingServices.Portal.WebHost.exe",
+        "bcp.exe", "SQLCMD.exe", "DatabaseMail.exe"
+      ) or
+      process.executable : (
+        "?:\\Windows\\System32\\wermgr.exe",
+        "?:\\Windows\\System32\\conhost.exe",
+        "?:\\Windows\\System32\\WerFault.exe"
+      )
+    ) and
+    (
+      process.code_signature.subject_name : ("Microsoft Corporation", "Microsoft Windows") and
+      process.code_signature.trusted == true
+    )
+  ) and
+  not (
+    (process.name : "cmd.exe" and process.parent.name : "sqlservr.exe") or
+    (process.name : "cmd.exe" and process.parent.name : "forfiles.exe" and process.command_line : "/c echo *")
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Server Software Component
+** ID: T1505
+** Reference URL: https://attack.mitre.org/techniques/T1505/
+* Sub-technique:
+** Name: SQL Stored Procedures
+** ID: T1505.001
+** Reference URL: https://attack.mitre.org/techniques/T1505/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-process-network-connection.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-process-network-connection.asciidoc
index 4721705e7a..c0c212b7db 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-process-network-connection.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-process-network-connection.asciidoc
@@ -5,108 +5,118 @@ Identifies network activity from unexpected system applications. This may indica
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<unusual-process-network-connection-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Unusual Process Network Connection
+*Triage and analysis*
+
+
+
+*Investigating Unusual Process Network Connection*
+
+
+This rule identifies network activity from unexpected system utilities and applications. These applications are commonly abused by attackers to execute code, evade detections, and bypass security protections.
+
 
-This rule identifies network activity from unexpected system utilities and applications. These applications are commonly
-abused by attackers to execute code, evade detections, and bypass security protections.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Investigate the target host that the process is communicating with.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system,
-persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 - Review the privileges assigned to the user to ensure that the least privilege principle is being followed.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by process.entity_id [process where (process.name :
-"Microsoft.Workflow.Compiler.exe" or process.name :
-"bginfo.exe" or process.name : "cdb.exe" or
-process.name : "cmstp.exe" or process.name :
-"csi.exe" or process.name : "dnx.exe" or
-process.name : "fsi.exe" or process.name :
-"ieexec.exe" or process.name : "iexpress.exe" or
-process.name : "odbcconf.exe" or process.name :
-"rcsi.exe" or process.name : "xwizard.exe") and
-event.type == "start"] [network where (process.name :
-"Microsoft.Workflow.Compiler.exe" or process.name :
-"bginfo.exe" or process.name : "cdb.exe" or
-process.name : "cmstp.exe" or process.name :
-"csi.exe" or process.name : "dnx.exe" or
-process.name : "fsi.exe" or process.name :
-"ieexec.exe" or process.name : "iexpress.exe" or
-process.name : "odbcconf.exe" or process.name :
-"rcsi.exe" or process.name : "xwizard.exe")]
+[source, js]
 ----------------------------------
+sequence by process.entity_id
+  [process where host.os.type == "windows" and (process.name : "Microsoft.Workflow.Compiler.exe" or
+                  process.name : "bginfo.exe" or
+                  process.name : "cdb.exe" or
+                  process.name : "cmstp.exe" or
+                  process.name : "csi.exe" or
+                  process.name : "dnx.exe" or
+                  process.name : "fsi.exe" or
+                  process.name : "ieexec.exe" or
+                  process.name : "iexpress.exe" or
+                  process.name : "odbcconf.exe" or
+                  process.name : "rcsi.exe" or
+                  process.name : "xwizard.exe") and
+     event.type == "start"]
+  [network where host.os.type == "windows" and (process.name : "Microsoft.Workflow.Compiler.exe" or
+                  process.name : "bginfo.exe" or
+                  process.name : "cdb.exe" or
+                  process.name : "cmstp.exe" or
+                  process.name : "csi.exe" or
+                  process.name : "dnx.exe" or
+                  process.name : "fsi.exe" or
+                  process.name : "ieexec.exe" or
+                  process.name : "iexpress.exe" or
+                  process.name : "odbcconf.exe" or
+                  process.name : "rcsi.exe" or
+                  process.name : "xwizard.exe")]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -118,59 +128,3 @@ process.name : "odbcconf.exe" or process.name :
 ** Name: Trusted Developer Utilities Proxy Execution
 ** ID: T1127
 ** Reference URL: https://attack.mitre.org/techniques/T1127/
-
-[[unusual-process-network-connection-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:network and event.type:connection and
-process.name:(Microsoft.Workflow.Compiler.exe or bginfo.exe or cdb.exe
-or cmstp.exe or csi.exe or dnx.exe or fsi.exe or ieexec.exe or
-iexpress.exe or odbcconf.exe or rcsi.exe or xwizard.exe)
-----------------------------------
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Network connection detected (rule: NetworkConnect)" and
-process.name:(Microsoft.Workflow.Compiler.exe or bginfo.exe or cdb.exe
-or cmstp.exe or csi.exe or dnx.exe or fsi.exe or ieexec.exe or
-iexpress.exe or odbcconf.exe or rcsi.exe or xwizard.exe)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Network connection detected (rule: NetworkConnect)" and
-process.name:(bginfo.exe or cdb.exe or cmstp.exe or csi.exe or dnx.exe
-or fsi.exe or ieexec.exe or iexpress.exe or
-Microsoft.Workflow.Compiler.exe or odbcconf.exe or rcsi.exe or
-xwizard.exe)
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-host.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-host.asciidoc
new file mode 100644
index 0000000000..9cf101a7bb
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-host.asciidoc
@@ -0,0 +1,126 @@
+[[unusual-process-spawned-by-a-host]]
+=== Unusual Process Spawned by a Host
+
+A machine learning job has detected a suspicious Windows process. This process has been classified as suspicious in two ways. It was predicted to be suspicious by the ProblemChild supervised ML model, and it was found to be an unusual process, on a host that does not commonly manifest malicious activity. Such a process may be an instance of suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/problemchild
+* https://www.elastic.co/security-labs/detecting-living-off-the-land-attacks-with-new-elastic-integration
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Living off the Land Attack Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Defense Evasion
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Living off the Land (LotL) Attack Detection integration assets to be installed, as well as Windows process events collected by integrations such as Elastic Defend or Winlogbeat.  
+
+
+*LotL Attack Detection Setup*
+
+The LotL Attack Detection integration detects living-off-the-land activity in Windows process events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for LotL Attack Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration or Winlogbeat(https://www.elastic.co/guide/en/beats/winlogbeat/current/_winlogbeat_overview.html).
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To set up and run Winlogbeat, follow https://www.elastic.co/guide/en/beats/winlogbeat/current/winlogbeat-installation-configuration.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the LotL Attack Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Living off the Land Attack Detection and select the integration to see more details about it.
+- Under Settings, click Install Living off the Land Attack Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+**Before you can enable this rule**, you'll need to enrich Windows process events with predictions from the Supervised LotL Attack Detection model. This is done via the ingest pipeline named `<package_version>-problem_child_ingest_pipeline` installed with the LotL Attack Detection package.
+- If using an Elastic Beat such as Winlogbeat, add the LotL ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `winlogbeat.yml`.
+- If adding the LotL ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor]. For example, you can check if your winlogbeat or Elastic Defend (the https://docs.elastic.co/en/integrations/endpoint#logs[default index pattern] being `logs-endpoint*`) already has an ingest pipeline by navigating to `Data > Index Management`, finding the index (sometimes you need to toggle "Include hidden indices"), and checking the index's settings for a default or final https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#set-default-pipeline[pipeline].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the LotL ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "problemchild": {
+      "properties": {
+        "prediction": {
+          "type": "long"
+        },
+        "prediction_probability": {
+          "type": "float"
+        }
+      }
+    },
+    "blocklist_label": {
+      "type": "long"
+    }
+  }
+}
+```
+
+
+*Anomaly Detection Setup*
+
+**Before you can enable this rule**, you'll need to enable the corresponding Anomaly Detection job. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your enriched Windows process events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events, or `winlogbeat-*` if you used Winlogbeat.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/problemchild/kibana/ml_module/problemchild-ml.json[this] configuration file, you will see a card for "Living off the Land Attack Detection" under "Use preconfigured jobs". Warning: If the ingest pipeline hasn't run for some reason, such as no eligible data in winlogbeat has come in yet, _you won't be able to see this card yet_. If that is the case, try troubleshooting the ingest pipeline, and check whether any ProblemChild predictions have been generated.
+- Keep the default settings and click "Create jobs" to start the anomaly detection job and datafeed.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-parent-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-parent-process.asciidoc
new file mode 100644
index 0000000000..f1e30e1027
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-parent-process.asciidoc
@@ -0,0 +1,126 @@
+[[unusual-process-spawned-by-a-parent-process]]
+=== Unusual Process Spawned by a Parent Process
+
+A machine learning job has detected a suspicious Windows process. This process has been classified as malicious in two ways. It was predicted to be malicious by the ProblemChild supervised ML model, and it was found to be an unusual child process name, for the parent process, by an unsupervised ML model. Such a process may be an instance of suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/problemchild
+* https://www.elastic.co/security-labs/detecting-living-off-the-land-attacks-with-new-elastic-integration
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Living off the Land Attack Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Defense Evasion
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Living off the Land (LotL) Attack Detection integration assets to be installed, as well as Windows process events collected by integrations such as Elastic Defend or Winlogbeat.  
+
+
+*LotL Attack Detection Setup*
+
+The LotL Attack Detection integration detects living-off-the-land activity in Windows process events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for LotL Attack Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration or Winlogbeat(https://www.elastic.co/guide/en/beats/winlogbeat/current/_winlogbeat_overview.html).
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To set up and run Winlogbeat, follow https://www.elastic.co/guide/en/beats/winlogbeat/current/winlogbeat-installation-configuration.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the LotL Attack Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Living off the Land Attack Detection and select the integration to see more details about it.
+- Under Settings, click Install Living off the Land Attack Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+**Before you can enable this rule**, you'll need to enrich Windows process events with predictions from the Supervised LotL Attack Detection model. This is done via the ingest pipeline named `<package_version>-problem_child_ingest_pipeline` installed with the LotL Attack Detection package.
+- If using an Elastic Beat such as Winlogbeat, add the LotL ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `winlogbeat.yml`.
+- If adding the LotL ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor]. For example, you can check if your winlogbeat or Elastic Defend (the https://docs.elastic.co/en/integrations/endpoint#logs[default index pattern] being `logs-endpoint*`) already has an ingest pipeline by navigating to `Data > Index Management`, finding the index (sometimes you need to toggle "Include hidden indices"), and checking the index's settings for a default or final https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#set-default-pipeline[pipeline].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the LotL ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "problemchild": {
+      "properties": {
+        "prediction": {
+          "type": "long"
+        },
+        "prediction_probability": {
+          "type": "float"
+        }
+      }
+    },
+    "blocklist_label": {
+      "type": "long"
+    }
+  }
+}
+```
+
+
+*Anomaly Detection Setup*
+
+**Before you can enable this rule**, you'll need to enable the corresponding Anomaly Detection job. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your enriched Windows process events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events, or `winlogbeat-*` if you used Winlogbeat.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/problemchild/kibana/ml_module/problemchild-ml.json[this] configuration file, you will see a card for "Living off the Land Attack Detection" under "Use preconfigured jobs". Warning: if the ingest pipeline hasn't run for some reason, such as no eligible data in winlogbeat has come in yet, _you won't be able to see this card yet_. If that is the case, try troubleshooting the ingest pipeline, and if any ProblemChild predictions have been populated yet.
+- Keep the default settings and click "Create jobs" to start the anomaly detection job and datafeed.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-user.asciidoc
new file mode 100644
index 0000000000..fceae7405f
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-process-spawned-by-a-user.asciidoc
@@ -0,0 +1,126 @@
+[[unusual-process-spawned-by-a-user]]
+=== Unusual Process Spawned by a User
+
+A machine learning job has detected a suspicious Windows process. This process has been classified as malicious in two ways. It was predicted to be malicious by the ProblemChild supervised ML model, and it was found to be suspicious given that its user context is unusual and does not commonly manifest malicious activity,by an unsupervised ML model. Such a process may be an instance of suspicious or malicious activity, possibly involving LOLbins, that may be resistant to detection using conventional search rules.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/problemchild
+* https://www.elastic.co/security-labs/detecting-living-off-the-land-attacks-with-new-elastic-integration
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Living off the Land Attack Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Defense Evasion
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Living off the Land (LotL) Attack Detection integration assets to be installed, as well as Windows process events collected by integrations such as Elastic Defend or Winlogbeat.  
+
+
+*LotL Attack Detection Setup*
+
+The LotL Attack Detection integration detects living-off-the-land activity in Windows process events.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for LotL Attack Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration or Winlogbeat(https://www.elastic.co/guide/en/beats/winlogbeat/current/_winlogbeat_overview.html).
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+- To set up and run Winlogbeat, follow https://www.elastic.co/guide/en/beats/winlogbeat/current/winlogbeat-installation-configuration.html[this] guide.
+
+
+*The following steps should be executed to install assets associated with the LotL Attack Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Living off the Land Attack Detection and select the integration to see more details about it.
+- Under Settings, click Install Living off the Land Attack Detection assets and follow the prompts to install the assets.
+
+
+*Ingest Pipeline Setup*
+
+**Before you can enable this rule**, you'll need to enrich Windows process events with predictions from the Supervised LotL Attack Detection model. This is done via the ingest pipeline named `<package_version>-problem_child_ingest_pipeline` installed with the LotL Attack Detection package.
+- If using an Elastic Beat such as Winlogbeat, add the LotL ingest pipeline to it by adding a simple configuration https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#pipelines-for-beats[setting] to `winlogbeat.yml`.
+- If adding the LotL ingest pipeline to an existing pipeline, use a https://www.elastic.co/guide/en/elasticsearch/reference/current/pipeline-processor.html[pipeline processor]. For example, you can check if your winlogbeat or Elastic Defend (the https://docs.elastic.co/en/integrations/endpoint#logs[default index pattern] being `logs-endpoint*`) already has an ingest pipeline by navigating to `Data > Index Management`, finding the index (sometimes you need to toggle "Include hidden indices"), and checking the index's settings for a default or final https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#set-default-pipeline[pipeline].
+
+
+*Adding Custom Mappings*
+
+- Go to the Kibana homepage. Under Management, click Stack Management.
+- Under Data click Index Management and navigate to the Component Templates tab.
+- Templates that can be edited to add custom components will be marked with a @custom suffix. Edit the @custom component template corresponding to the beat/integration you added the LotL ingest pipeline to, by pasting the following JSON blob in the "Load JSON" flyout:
+```
+{
+  "properties": {
+    "problemchild": {
+      "properties": {
+        "prediction": {
+          "type": "long"
+        },
+        "prediction_probability": {
+          "type": "float"
+        }
+      }
+    },
+    "blocklist_label": {
+      "type": "long"
+    }
+  }
+}
+```
+
+
+*Anomaly Detection Setup*
+
+**Before you can enable this rule**, you'll need to enable the corresponding Anomaly Detection job. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your enriched Windows process events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events, or `winlogbeat-*` if you used Winlogbeat.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/problemchild/kibana/ml_module/problemchild-ml.json[this] configuration file, you will see a card for "Living off the Land Attack Detection" under "Use preconfigured jobs". Warning: if the ingest pipeline hasn't run for some reason, such as no eligible data in winlogbeat has come in yet, _you won't be able to see this card yet_. If that is the case, try troubleshooting the ingest pipeline, and if any ProblemChild predictions have been populated yet.
+- Keep the default settings and click "Create jobs" to start the anomaly detection job and datafeed.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Masquerading
+** ID: T1036
+** Reference URL: https://attack.mitre.org/techniques/T1036/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-process-writing-data-to-an-external-device.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-process-writing-data-to-an-external-device.asciidoc
new file mode 100644
index 0000000000..41e6916ac9
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-process-writing-data-to-an-external-device.asciidoc
@@ -0,0 +1,90 @@
+[[unusual-process-writing-data-to-an-external-device]]
+=== Unusual Process Writing Data to an External Device
+
+A machine learning job has detected a rare process writing data to an external device. Malicious actors often use benign-looking processes to mask their data exfiltration activities. The discovery of such a process that has no legitimate reason to write data to external devices can indicate exfiltration.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-2h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/ded
+* https://www.elastic.co/blog/detect-data-exfiltration-activity-with-kibanas-new-integration
+
+*Tags*: 
+
+* Use Case: Data Exfiltration Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Exfiltration
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Data Exfiltration Detection integration assets to be installed, as well as network and file events collected by integrations such as Elastic Defend and Network Packet Capture (for network events only).  
+
+
+*Data Exfiltration Detection Setup*
+
+The Data Exfiltration Detection integration detects data exfiltration activity by identifying abnormalities in network and file events. Anomalies are detected using Elastic's Anomaly Detection feature. 
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Data Exfiltration Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- File events collected by the Elastic Defend integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Data Exfiltration Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Data Exfiltration Detection and select the integration to see more details about it.
+- Under Settings, click Install Data Exfiltration Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Data Exfiltration Detection, you'll need to enable the corresponding Anomaly Detection jobs. 
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your file events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/ded/kibana/ml_module/ded-ml.json[this] configuration file, you will see a card for Data Exfiltration Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Exfiltration
+** ID: TA0010
+** Reference URL: https://attack.mitre.org/tactics/TA0010/
+* Technique:
+** Name: Exfiltration Over Physical Medium
+** ID: T1052
+** Reference URL: https://attack.mitre.org/techniques/T1052/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-remote-file-directory.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-remote-file-directory.asciidoc
new file mode 100644
index 0000000000..a0b2eeb859
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-remote-file-directory.asciidoc
@@ -0,0 +1,91 @@
+[[unusual-remote-file-directory]]
+=== Unusual Remote File Directory
+
+An anomaly detection job has detected a remote file transfer on an unusual directory indicating a potential lateral movement activity on the host. Many Security solutions monitor well-known directories for suspicious activities, so attackers might use less common directories to bypass monitoring.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-90m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/lmd
+* https://www.elastic.co/blog/detecting-lateral-movement-activity-a-new-kibana-integration
+* https://www.elastic.co/blog/remote-desktop-protocol-connections-elastic-security
+
+*Tags*: 
+
+* Use Case: Lateral Movement Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Lateral Movement Detection integration assets to be installed, as well as file and Windows RDP process events collected by the Elastic Defend integration.  
+
+
+*Lateral Movement Detection Setup*
+
+The Lateral Movement Detection integration detects lateral movement activity by identifying abnormalities in file and Windows RDP events. Anomalies are detected using Elastic's Anomaly Detection feature.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Lateral Movement Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- File events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Lateral Movement Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Lateral Movement Detection and select the integration to see more details about it.
+- Under Settings, click Install Lateral Movement Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Lateral Movement Detection, you'll need to enable the corresponding Anomaly Detection jobs.
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your file events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/lmd/kibana/ml_module/lmd-ml.json[this] configuration file, you will see a card for Lateral Movement Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-remote-file-extension.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-remote-file-extension.asciidoc
new file mode 100644
index 0000000000..88a4466443
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-remote-file-extension.asciidoc
@@ -0,0 +1,91 @@
+[[unusual-remote-file-extension]]
+=== Unusual Remote File Extension
+
+An anomaly detection job has detected a remote file transfer with a rare extension, which could indicate potential lateral movement activity on the host.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-90m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/lmd
+* https://www.elastic.co/blog/detecting-lateral-movement-activity-a-new-kibana-integration
+* https://www.elastic.co/blog/remote-desktop-protocol-connections-elastic-security
+
+*Tags*: 
+
+* Use Case: Lateral Movement Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Lateral Movement Detection integration assets to be installed, as well as file and Windows RDP process events collected by the Elastic Defend integration.  
+
+
+*Lateral Movement Detection Setup*
+
+The Lateral Movement Detection integration detects lateral movement activity by identifying abnormalities in file and Windows RDP events. Anomalies are detected using Elastic's Anomaly Detection feature.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Lateral Movement Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- File events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Lateral Movement Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Lateral Movement Detection and select the integration to see more details about it.
+- Under Settings, click Install Lateral Movement Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Lateral Movement Detection, you'll need to enable the corresponding Anomaly Detection jobs.
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your file events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/lmd/kibana/ml_module/lmd-ml.json[this] configuration file, you will see a card for Lateral Movement Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-remote-file-size.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-remote-file-size.asciidoc
new file mode 100644
index 0000000000..f60c100148
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-remote-file-size.asciidoc
@@ -0,0 +1,91 @@
+[[unusual-remote-file-size]]
+=== Unusual Remote File Size
+
+A machine learning job has detected an unusually high file size shared by a remote host indicating potential lateral movement activity. One of the primary goals of attackers after gaining access to a network is to locate and exfiltrate valuable information. Instead of multiple small transfers that can raise alarms, attackers might choose to bundle data into a single large file transfer.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-90m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/lmd
+* https://www.elastic.co/blog/detecting-lateral-movement-activity-a-new-kibana-integration
+* https://www.elastic.co/blog/remote-desktop-protocol-connections-elastic-security
+
+*Tags*: 
+
+* Use Case: Lateral Movement Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Lateral Movement Detection integration assets to be installed, as well as file and Windows RDP process events collected by the Elastic Defend integration.  
+
+
+*Lateral Movement Detection Setup*
+
+The Lateral Movement Detection integration detects lateral movement activity by identifying abnormalities in file and Windows RDP events. Anomalies are detected using Elastic's Anomaly Detection feature.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Lateral Movement Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- File events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Lateral Movement Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Lateral Movement Detection and select the integration to see more details about it.
+- Under Settings, click Install Lateral Movement Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Lateral Movement Detection, you'll need to enable the corresponding Anomaly Detection jobs.
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your file events. For example, this would be `logs-endpoint.events.*` if you used Elastic Defend to collect events.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/lmd/kibana/ml_module/lmd-ml.json[this] configuration file, you will see a card for Lateral Movement Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-service-host-child-process-childless-service.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-service-host-child-process-childless-service.asciidoc
index bfa0ed4951..cc64c51259 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-service-host-child-process-childless-service.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-service-host-child-process-childless-service.asciidoc
@@ -5,81 +5,92 @@ Identifies unusual child processes of Service Host (svchost.exe) that traditiona
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 101 (<<unusual-service-host-child-process-childless-service-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Privilege Escalation
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Changes to Windows services or a rarely executed child process.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-"svchost.exe" and /* based on svchost service arguments -s
-svcname where the service is known to be childless */
-process.parent.args : ("WdiSystemHost","LicenseManager",
-"StorSvc","CDPSvc","cdbhsvc","BthAvctpSvc","SstpSvc","WdiServiceHost",
-"imgsvc","TrkWks","WpnService","IKEEXT","PolicyAgent","CryptSvc",
-"netprofm","ProfSvc","StateRepository","camsvc","LanmanWorkstation",
-"NlaSvc","EventLog","hidserv","DisplayEnhancementService","ShellHWDete
-ction", "AppHostSvc","fhsvc","CscService","PushToInstall") and
-/* unknown FPs can be added here */ not process.name :
-("WerFault.exe","WerFaultSecure.exe","wermgr.exe") and not
-(process.executable : "?:\\Windows\\System32\\RelPost.exe" and
-process.parent.args : "WdiSystemHost") and not (process.name :
-"rundll32.exe" and process.args :
-"?:\\WINDOWS\\System32\\winethc.dll,ForceProxyDetectionOnNextRun" and
-process.parent.args : "WdiServiceHost") and not
-(process.executable : ("?:\\Program Files\\*", "?:\\Program Files
-(x86)\\*", "?:\\Windows\\System32\\Kodak\\kds_i4x50\\lib\\lexexe.exe")
-and process.parent.args : "imgsvc")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : "svchost.exe" and
+
+  /* based on svchost service arguments -s svcname where the service is known to be childless */
+  process.parent.args : (
+    "WdiSystemHost", "LicenseManager", "StorSvc", "CDPSvc", "cdbhsvc", "BthAvctpSvc", "SstpSvc", "WdiServiceHost",
+    "imgsvc", "TrkWks", "WpnService", "IKEEXT", "PolicyAgent", "CryptSvc", "netprofm", "ProfSvc", "StateRepository",
+    "camsvc", "LanmanWorkstation", "NlaSvc", "EventLog", "hidserv", "DisplayEnhancementService", "ShellHWDetection",
+    "AppHostSvc", "fhsvc", "CscService", "PushToInstall"
+  ) and
+
+  /* unknown FPs can be added here */
+  not process.name : ("WerFault.exe", "WerFaultSecure.exe", "wermgr.exe") and
+  not (process.executable : "?:\\Windows\\System32\\RelPost.exe" and process.parent.args : "WdiSystemHost") and
+  not (
+    process.name : "rundll32.exe" and
+    process.args : "?:\\WINDOWS\\System32\\winethc.dll,ForceProxyDetectionOnNextRun" and
+    process.parent.args : "WdiServiceHost"
+  ) and
+  not (
+    process.executable : (
+      "?:\\Program Files\\*",
+      "?:\\Program Files (x86)\\*",
+      "?:\\Windows\\System32\\Kodak\\kds_?????\\lib\\lexexe.exe"
+    ) and process.parent.args : "imgsvc"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -91,8 +102,10 @@ and process.parent.args : "imgsvc")
 ** Name: Process Injection
 ** ID: T1055
 ** Reference URL: https://attack.mitre.org/techniques/T1055/
-
-
+* Sub-technique:
+** Name: Process Hollowing
+** ID: T1055.012
+** Reference URL: https://attack.mitre.org/techniques/T1055/012/
 * Tactic:
 ** Name: Defense Evasion
 ** ID: TA0005
@@ -101,62 +114,7 @@ and process.parent.args : "imgsvc")
 ** Name: Process Injection
 ** ID: T1055
 ** Reference URL: https://attack.mitre.org/techniques/T1055/
-
-[[unusual-service-host-child-process-childless-service-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "svchost.exe" and /* based on svchost
-service arguments -s svcname where the service is known to be
-childless */ process.parent.args :
-("WdiSystemHost","LicenseManager",
-"StorSvc","CDPSvc","cdbhsvc","BthAvctpSvc","SstpSvc","WdiServiceHost",
-"imgsvc","TrkWks","WpnService","IKEEXT","PolicyAgent","CryptSvc",
-"netprofm","ProfSvc","StateRepository","camsvc","LanmanWorkstation",
-"NlaSvc","EventLog","hidserv","DisplayEnhancementService","ShellHWDete
-ction", "AppHostSvc","fhsvc","CscService","PushToInstall") and
-/* unknown FPs can be added here */ not process.name :
-("WerFault.exe","WerFaultSecure.exe","wermgr.exe") and not
-(process.executable : "?:\\Windows\\System32\\RelPost.exe" and
-process.parent.args : "WdiSystemHost") and not (process.name :
-"rundll32.exe" and process.args :
-"?:\\WINDOWS\\System32\\winethc.dll,ForceProxyDetectionOnNextRun" and
-process.parent.args : "WdiServiceHost") and not
-(process.executable : ("?:\\Program Files\\*", "?:\\Program Files
-(x86)\\*", "?:\\Windows\\System32\\Kodak\\kds_i4x50\\lib\\lexexe.exe")
-and process.parent.args : "imgsvc")
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : "svchost.exe" and /* based on svchost
-service arguments -s svcname where the service is known to be
-childless */ process.parent.args :
-("WdiSystemHost","LicenseManager",
-"StorSvc","CDPSvc","cdbhsvc","BthAvctpSvc","SstpSvc","WdiServiceHost",
-"imgsvc","TrkWks","WpnService","IKEEXT","PolicyAgent","CryptSvc",
-"netprofm","ProfSvc","StateRepository","camsvc","LanmanWorkstation",
-"NlaSvc","EventLog","hidserv","DisplayEnhancementService","ShellHWDete
-ction", "AppHostSvc","fhsvc","CscService","PushToInstall") and
-/* unknown FPs can be added here */ not process.name :
-("WerFault.exe","WerFaultSecure.exe","wermgr.exe")
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Process Hollowing
+** ID: T1055.012
+** Reference URL: https://attack.mitre.org/techniques/T1055/012/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-source-ip-for-a-user-to-logon-from.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-source-ip-for-a-user-to-logon-from.asciidoc
index 235bd322d7..8da533fe37 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-source-ip-for-a-user-to-logon-from.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-source-ip-for-a-user-to-logon-from.asciidoc
@@ -5,47 +5,38 @@ A machine learning job detected a user logging in from an IP address that is unu
 
 *Rule type*: machine_learning
 
-*Machine learning job*: auth_rare_source_ip_for_a_user
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-30m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Authentication
-* Threat Detection
-* ML
-* Initial Access
+* Use Case: Identity and Access Audit
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Initial Access
 
-*Version*: 100 (<<unusual-source-ip-for-a-user-to-logon-from-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.14.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Business travelers who roam to new locations may trigger this alert.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -57,13 +48,3 @@ Business travelers who roam to new locations may trigger this alert.
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[unusual-source-ip-for-a-user-to-logon-from-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 2 (8.4.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-sudo-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-sudo-activity.asciidoc
index 99a01eb185..c74c5d6af9 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-sudo-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-sudo-activity.asciidoc
@@ -5,43 +5,37 @@ Looks for sudo activity from an unusual user context. An unusual sudo user could
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_linux_rare_sudo_user
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* ML
+*Tags*: 
 
-*Version*: 100 (<<unusual-sudo-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Uncommon sudo activity can be due to an engineer logging onto a server instance in order to perform manual troubleshooting or reconfiguration.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -53,8 +47,6 @@ Uncommon sudo activity can be due to an engineer logging onto a server instance
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-
 * Tactic:
 ** Name: Privilege Escalation
 ** ID: TA0004
@@ -63,16 +55,3 @@ Uncommon sudo activity can be due to an engineer logging onto a server instance
 ** Name: Abuse Elevation Control Mechanism
 ** ID: T1548
 ** Reference URL: https://attack.mitre.org/techniques/T1548/
-
-[[unusual-sudo-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.3.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-time-or-day-for-an-rdp-session.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-time-or-day-for-an-rdp-session.asciidoc
new file mode 100644
index 0000000000..18300933e4
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-time-or-day-for-an-rdp-session.asciidoc
@@ -0,0 +1,92 @@
+[[unusual-time-or-day-for-an-rdp-session]]
+=== Unusual Time or Day for an RDP Session
+
+A machine learning job has detected an RDP session started at an usual time or weekday. An RDP session at an unusual time could be followed by other suspicious activities, so catching this is a good first step in detecting a larger attack.
+
+*Rule type*: machine_learning
+
+*Rule indices*: None
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 15m
+
+*Searches indices from*: now-12h ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
+* https://docs.elastic.co/en/integrations/lmd
+* https://www.elastic.co/blog/detecting-lateral-movement-activity-a-new-kibana-integration
+* https://www.elastic.co/blog/remote-desktop-protocol-connections-elastic-security
+
+*Tags*: 
+
+* Use Case: Lateral Movement Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Lateral Movement
+
+*Version*: 3
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The rule requires the Lateral Movement Detection integration assets to be installed, as well as file and Windows RDP process events collected by the Elastic Defend integration.  
+
+
+*Lateral Movement Detection Setup*
+
+The Lateral Movement Detection integration detects lateral movement activity by identifying abnormalities in file and Windows RDP events. Anomalies are detected using Elastic's Anomaly Detection feature.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Lateral Movement Detection.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+- Windows RDP process events collected by the https://docs.elastic.co/en/integrations/endpoint[Elastic Defend] integration.
+- To install Elastic Defend, refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[documentation].
+
+
+*The following steps should be executed to install assets associated with the Lateral Movement Detection integration:*
+
+- Go to the Kibana homepage. Under Management, click Integrations.
+- In the query bar, search for Lateral Movement Detection and select the integration to see more details about it.
+- Under Settings, click Install Lateral Movement Detection assets and follow the prompts to install the assets.
+
+
+*Anomaly Detection Setup*
+
+Before you can enable rules for Lateral Movement Detection, you'll need to enable the corresponding Anomaly Detection jobs.
+- Before enabling the Anomaly Detection jobs, confirm that the Pivot Transform asset is installed and actively gathering data in the destination index `ml-rdp-lmd`.
+- Go to the Kibana homepage. Under Analytics, click Machine Learning.
+- Under Anomaly Detection, click Jobs, and then click "Create job". Select the Data View containing your transformed RDP process data i.e.`ml-rdp-lmd`.
+- If the selected Data View contains events that match the query in https://github.com/elastic/integrations/blob/main/packages/lmd/kibana/ml_module/lmd-ml.json[this] configuration file, you will see a card for Lateral Movement Detection under "Use preconfigured jobs".
+- Keep the default settings and click "Create jobs" to start the anomaly detection jobs and datafeeds.
+
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Exploitation of Remote Services
+** ID: T1210
+** Reference URL: https://attack.mitre.org/techniques/T1210/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-user-privilege-enumeration-via-id.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-user-privilege-enumeration-via-id.asciidoc
new file mode 100644
index 0000000000..05f64e64d8
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-user-privilege-enumeration-via-id.asciidoc
@@ -0,0 +1,99 @@
+[[unusual-user-privilege-enumeration-via-id]]
+=== Unusual User Privilege Enumeration via id
+
+This rule monitors for a sequence of 20 "id" command executions within 1 second by the same parent process. This behavior is unusual, and may be indicative of the execution of an enumeration script such as LinPEAS or LinEnum. These scripts leverage the "id" command to enumerate the privileges of all users present on the system.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence by host.id, process.parent.entity_id with maxspan=1s
+  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and 
+   process.name == "id" and process.args_count == 2 and 
+   not (process.parent.name == "rpm" or process.parent.args : "/var/tmp/rpm-tmp*")] with runs=20
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Owner/User Discovery
+** ID: T1033
+** Reference URL: https://attack.mitre.org/techniques/T1033/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-web-request.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-web-request.asciidoc
index 9347d2ce00..6b7c2c5881 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-web-request.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-web-request.asciidoc
@@ -5,47 +5,37 @@ A machine learning job detected a rare and unusual URL that indicates unusual we
 
 *Rule type*: machine_learning
 
-*Machine learning job*: packetbeat_rare_urls
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Network
-* Threat Detection
-* ML
-* Command and Control
+*Tags*: 
 
-*Version*: 100 (<<unusual-web-request-history, version history>>)
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Command and Control
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Web activity that occurs rarely in small quantities can trigger this alert. Possible examples are browsing technical support or vendor URLs that are used very sparsely. A user who visits a new and unique web destination may trigger this alert when the activity is sparse. Web applications that generate URLs unique to a transaction may trigger this when they are used sparsely. Web domains can be excluded in cases such as these.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -57,22 +47,7 @@ Web activity that occurs rarely in small quantities can trigger this alert. Poss
 ** Name: Application Layer Protocol
 ** ID: T1071
 ** Reference URL: https://attack.mitre.org/techniques/T1071/
-
-[[unusual-web-request-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Web Protocols
+** ID: T1071.001
+** Reference URL: https://attack.mitre.org/techniques/T1071/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-web-user-agent.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-web-user-agent.asciidoc
index fad69f804c..2a991b5def 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-web-user-agent.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-web-user-agent.asciidoc
@@ -5,47 +5,37 @@ A machine learning job detected a rare and unusual user agent indicating web bro
 
 *Rule type*: machine_learning
 
-*Machine learning job*: packetbeat_rare_user_agent
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Network
-* Threat Detection
-* ML
-* Command and Control
+*Tags*: 
 
-*Version*: 100 (<<unusual-web-user-agent-history, version history>>)
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Command and Control
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Web activity that is uncommon, like security scans, may trigger this alert and may need to be excluded. A new or rarely used program that calls web services may trigger this alert.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -57,22 +47,7 @@ Web activity that is uncommon, like security scans, may trigger this alert and m
 ** Name: Application Layer Protocol
 ** ID: T1071
 ** Reference URL: https://attack.mitre.org/techniques/T1071/
-
-[[unusual-web-user-agent-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Web Protocols
+** ID: T1071.001
+** Reference URL: https://attack.mitre.org/techniques/T1071/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-windows-network-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-windows-network-activity.asciidoc
index f505ea6997..4916756fa0 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-windows-network-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-windows-network-activity.asciidoc
@@ -5,55 +5,49 @@ Identifies Windows processes that do not usually use the network but have unexpe
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_windows_anomalous_network_activity
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
+*Tags*: 
 
-*Version*: 100 (<<unusual-windows-network-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A newly installed program or one that rarely uses the network could trigger this alert.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Unusual Network Activity
+*Triage and analysis*
+
+
+
+*Investigating Unusual Network Activity*
+
 Detection alerts from this rule indicate the presence of network activity from a Windows process for which network activity is very unusual.  Here are some possible avenues of investigation:
 - Consider the IP addresses, protocol and ports. Are these used by normal but infrequent network workflows? Are they expected or unexpected?
 - If the destination IP address is remote or external, does it associate with an expected domain, organization or geography? Note: avoid interacting directly with suspected malicious IP addresses.
@@ -62,33 +56,3 @@ Detection alerts from this rule indicate the presence of network activity from a
 - Examine the process arguments, title and working directory. These may provide indications as to the source of the program or the nature of the tasks it is performing.
 - Consider the same for the parent process. If the parent process is a legitimate system utility or service, this could be related to software updates or system management. If the parent process is something user-facing like an Office application, this process could be more suspicious.
 - If you have file hash values in the event data, and you suspect malware, you can optionally run a search for the file hash to see if the file is identified as malware by anti-malware tools.
-----------------------------------
-
-
-[[unusual-windows-network-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.3.0 release)::
-* Formatting only
-
-Version 7 (7.15.0 release)::
-* Formatting only
-
-Version 6 (7.14.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-windows-path-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-windows-path-activity.asciidoc
index 4e64919ba4..2b1f861d33 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-windows-path-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-windows-path-activity.asciidoc
@@ -5,48 +5,40 @@ Identifies processes started from atypical folders in the file system, which mig
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_windows_anomalous_path_activity
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
-* Persistence
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Persistence
+* Tactic: Execution
 
-*Version*: 100 (<<unusual-windows-path-activity-history, version history>>)
+*Version*: 104
 
-*Added ({stack} release)*: 7.7.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A new and unusual program or artifact download in the course of software upgrades, debugging, or troubleshooting could trigger this alert. Users downloading and running programs from unusual locations, such as temporary directories, browser caches, or profile paths could trigger this alert.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -58,28 +50,19 @@ A new and unusual program or artifact download in the course of software upgrade
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[unusual-windows-path-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (7.14.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: User Execution
+** ID: T1204
+** Reference URL: https://attack.mitre.org/techniques/T1204/
+* Sub-technique:
+** Name: Malicious File
+** ID: T1204.002
+** Reference URL: https://attack.mitre.org/techniques/T1204/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-windows-process-calling-the-metadata-service.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-windows-process-calling-the-metadata-service.asciidoc
index 70ae069341..67f51cf52b 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-windows-process-calling-the-metadata-service.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-windows-process-calling-the-metadata-service.asciidoc
@@ -5,44 +5,37 @@ Looks for anomalous access to the metadata service by an unusual process. The me
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_windows_rare_metadata_process
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
-* Credential Access
+*Tags*: 
 
-*Version*: 100 (<<unusual-windows-process-calling-the-metadata-service-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A newly installed program or one that runs very rarely as part of a monthly or quarterly workflow could trigger this detection rule.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -54,22 +47,7 @@ A newly installed program or one that runs very rarely as part of a monthly or q
 ** Name: Unsecured Credentials
 ** ID: T1552
 ** Reference URL: https://attack.mitre.org/techniques/T1552/
-
-[[unusual-windows-process-calling-the-metadata-service-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (7.14.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Cloud Instance Metadata API
+** ID: T1552.005
+** Reference URL: https://attack.mitre.org/techniques/T1552/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-windows-remote-user.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-windows-remote-user.asciidoc
index bb86e09f0e..4b08d9e2c6 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-windows-remote-user.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-windows-remote-user.asciidoc
@@ -5,62 +5,53 @@ A machine learning job detected an unusual remote desktop protocol (RDP) usernam
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_windows_rare_user_type10_remote_login
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
-* Initial Access
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Initial Access
 
-*Version*: 100 (<<unusual-windows-remote-user-history, version history>>)
+*Version*: 103
 
-*Added ({stack} release)*: 7.7.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Uncommon username activity can be due to an engineer logging onto a server instance in order to perform manual troubleshooting or reconfiguration.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating an Unusual Windows User
+*Triage and analysis*
+
+
+
+*Investigating an Unusual Windows User*
+
 Detection alerts from this rule indicate activity for a rare and unusual Windows RDP (remote desktop) user. Here are some possible avenues of investigation:
 - Consider the user as identified by the username field. Is the user part of a group who normally logs into Windows hosts using RDP (remote desktop protocol)? Is this logon activity part of an expected workflow for the user?
 - Consider the source of the login. If the source is remote, could this be related to occasional troubleshooting or support activity by a vendor or an employee working remotely?
-----------------------------------
-
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,28 +63,3 @@ Detection alerts from this rule indicate activity for a rare and unusual Windows
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[unusual-windows-remote-user-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-windows-service.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-windows-service.asciidoc
index b1adf42b9c..cfd865d646 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-windows-service.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-windows-service.asciidoc
@@ -5,48 +5,39 @@ A machine learning job detected an unusual Windows service, This can indicate ex
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_windows_anomalous_service
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
-* Persistence
+*Tags*: 
 
-*Version*: 100 (<<unusual-windows-service-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A newly installed program or one that runs rarely as part of a monthly or quarterly workflow could trigger this alert.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -58,25 +49,7 @@ A newly installed program or one that runs rarely as part of a monthly or quarte
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[unusual-windows-service-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-windows-user-calling-the-metadata-service.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-windows-user-calling-the-metadata-service.asciidoc
index a9d2d09d54..eb565274ae 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-windows-user-calling-the-metadata-service.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-windows-user-calling-the-metadata-service.asciidoc
@@ -5,44 +5,37 @@ Looks for anomalous access to the cloud platform metadata service by an unusual
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_windows_rare_metadata_user
-
-*Machine learning anomaly threshold*: 75
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
-* Credential Access
+*Tags*: 
 
-*Version*: 100 (<<unusual-windows-user-calling-the-metadata-service-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Credential Access
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-A newly installed program, or one that runs under a new or rarely used user context, could trigger this detection rule. Manual interrogation of the metadata service during debugging or troubleshooting could trigger this rule.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -54,22 +47,7 @@ A newly installed program, or one that runs under a new or rarely used user cont
 ** Name: Unsecured Credentials
 ** ID: T1552
 ** Reference URL: https://attack.mitre.org/techniques/T1552/
-
-[[unusual-windows-user-calling-the-metadata-service-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (7.14.0 release)::
-* Formatting only
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Cloud Instance Metadata API
+** ID: T1552.005
+** Reference URL: https://attack.mitre.org/techniques/T1552/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-windows-user-privilege-elevation-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-windows-user-privilege-elevation-activity.asciidoc
index fca0e16dba..36716d1e03 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-windows-user-privilege-elevation-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-windows-user-privilege-elevation-activity.asciidoc
@@ -5,48 +5,39 @@ A machine learning job detected an unusual user context switch, using the runas
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_windows_rare_user_runas_event
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
-* Privilege Escalation
+*Tags*: 
 
-*Version*: 100 (<<unusual-windows-user-privilege-elevation-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Privilege Escalation
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Uncommon user privilege elevation activity can be due to an administrator, help desk technician, or a user performing manual troubleshooting or reconfiguration.
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -54,25 +45,3 @@ Uncommon user privilege elevation activity can be due to an administrator, help
 ** Name: Privilege Escalation
 ** ID: TA0004
 ** Reference URL: https://attack.mitre.org/tactics/TA0004/
-
-[[unusual-windows-user-privilege-elevation-activity-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/unusual-windows-username.asciidoc b/docs/detections/prebuilt-rules/rule-details/unusual-windows-username.asciidoc
index 173f300bd4..17d4473ba5 100644
--- a/docs/detections/prebuilt-rules/rule-details/unusual-windows-username.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/unusual-windows-username.asciidoc
@@ -5,64 +5,55 @@ A machine learning job detected activity for a username that is not normally act
 
 *Rule type*: machine_learning
 
-*Machine learning job*: v3_windows_anomalous_user_name
-
-*Machine learning anomaly threshold*: 50
-
+*Rule indices*: None
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 15 minutes
+*Runs every*: 15m
 
 *Searches indices from*: now-45m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html
 
-*Tags*:
-
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* ML
-* Initial Access
+*Tags*: 
 
-*Version*: 100 (<<unusual-windows-username-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Rule Type: ML
+* Rule Type: Machine Learning
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Uncommon user activity can be due to an administrator or help desk technician logging onto a workstation or server in order to perform manual troubleshooting or reconfiguration.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating an Unusual Windows User
+*Triage and analysis*
+
+
+
+*Investigating an Unusual Windows User*
+
 Detection alerts from this rule indicate activity for a Windows user name that is rare and unusual. Here are some possible avenues of investigation:
 - Consider the user as identified by the username field. Is this program part of an expected workflow for the user who ran this program on this host? Could this be related to occasional troubleshooting or support activity?
 - Examine the history of user activity. If this user only manifested recently, it might be a service account for a new software package. If it has a consistent cadence (for example if it runs monthly or quarterly), it might be part of a monthly or quarterly business process.
 - Examine the process arguments, title and working directory. These may provide indications as to the source of the program or the nature of the tasks that the user is performing.
 - Consider the same for the parent process. If the parent process is a legitimate system utility or service, this could be related to software updates or system management. If the parent process is something user-facing like an Office application, this process could be more suspicious.
-----------------------------------
-
-==== Threat mapping
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,34 +65,11 @@ Detection alerts from this rule indicate activity for a Windows user name that i
 ** Name: Valid Accounts
 ** ID: T1078
 ** Reference URL: https://attack.mitre.org/techniques/T1078/
-
-[[unusual-windows-username-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 8 (8.3.0 release)::
-* Formatting only
-
-Version 7 (7.15.0 release)::
-* Formatting only
-
-Version 6 (7.14.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Domain Accounts
+** ID: T1078.002
+** Reference URL: https://attack.mitre.org/techniques/T1078/002/
+* Sub-technique:
+** Name: Local Accounts
+** ID: T1078.003
+** Reference URL: https://attack.mitre.org/techniques/T1078/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/user-account-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/user-account-creation.asciidoc
index 3bbdd9e194..ef8cb552a4 100644
--- a/docs/detections/prebuilt-rules/rule-details/user-account-creation.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/user-account-creation.asciidoc
@@ -5,97 +5,119 @@ Identifies attempts to create new users. This is sometimes done by attackers to
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<user-account-creation-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating User Account Creation
+*Triage and analysis*
+
+
+
+*Investigating User Account Creation*
+
 
 Attackers may create new accounts (both local and domain) to maintain access to victim systems.
 
 This rule identifies the usage of `net.exe` to create new accounts.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Identify if the account was added to privileged groups or assigned special privileges after creation.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 
-### False positive analysis
 
-- Account creation is a common administrative task, so there is a high chance of the activity being legitimate. Before
-investigating further, verify that this activity is not benign.
+*False positive analysis*
+
+
+- Account creation is a common administrative task, so there is a high chance of the activity being legitimate. Before investigating further, verify that this activity is not benign.
+
+
+*Related rules*
 
-### Related rules
 
 - Creation of a Hidden Local User Account - 2edc8076-291e-41e9-81e4-e3fcbc97ae5e
 - Windows User Account Creation - 38e17753-f581-4644-84da-0d60a8318694
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
 - Delete the created account.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : ("net.exe",
-"net1.exe") and not process.parent.name : "net.exe" and
-(process.args : "user" and process.args : ("/ad", "/add"))
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : ("net.exe", "net1.exe") and
+  not process.parent.name : "net.exe" and
+  (process.args : "user" and process.args : ("/ad", "/add"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -107,76 +129,7 @@ process where event.type == "start" and process.name : ("net.exe",
 ** Name: Create Account
 ** ID: T1136
 ** Reference URL: https://attack.mitre.org/techniques/T1136/
-
-[[user-account-creation-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : ("net.exe", "net1.exe") and not process.parent.name :
-"net.exe" and (process.args : "user" and process.args : ("/ad",
-"/add"))
-----------------------------------
-
-Version 13 (8.4.0 release)::
-* Formatting only
-
-Version 11 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 9 (7.16.0 release)::
-* Formatting only
-
-Version 8 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:(net.exe or net1.exe) and not process.parent.name:net.exe
-and process.args:(user and (/ad or /add))
-----------------------------------
-
-Version 7 (7.12.0 release)::
-* Formatting only
-
-Version 6 (7.11.2 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:(net.exe or net1.exe) and not process.parent.name:net.exe
-and process.args:(user and (/ad or /add))
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:("net.exe" or "net1.exe") and not
-process.parent.name:"net.exe" and process.args:("user" and ("/add" or
-"/ad"))
-----------------------------------
-
+* Sub-technique:
+** Name: Local Account
+** ID: T1136.001
+** Reference URL: https://attack.mitre.org/techniques/T1136/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/user-account-exposed-to-kerberoasting.asciidoc b/docs/detections/prebuilt-rules/rule-details/user-account-exposed-to-kerberoasting.asciidoc
index 151f53a3b1..cb27d685ca 100644
--- a/docs/detections/prebuilt-rules/rule-details/user-account-exposed-to-kerberoasting.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/user-account-exposed-to-kerberoasting.asciidoc
@@ -5,22 +5,23 @@ Detects when a user account has the servicePrincipalName attribute modified. Att
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.thehacker.recipes/ad/movement/access-controls/targeted-kerberoasting
 * https://www.qomplx.com/qomplx-knowledge-kerberoasting-attacks-explained/
@@ -29,55 +30,49 @@ Detects when a user account has the servicePrincipalName attribute modified. Att
 * https://adsecurity.org/?p=280
 * https://github.com/OTRF/Set-AuditRule
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Active Directory
-* Investigation Guide
-
-*Version*: 102 (<<user-account-exposed-to-kerberoasting-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Active Directory
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
 
-*Added ({stack} release)*: 8.2.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating User account exposed to Kerberoasting
+*Triage and analysis*
+
+
+
+*Investigating User account exposed to Kerberoasting*
+
+
+Service Principal Names (SPNs) are names by which Kerberos clients uniquely identify service instances for Kerberos target computers.
 
-Service Principal Names (SPNs) are names by which Kerberos clients uniquely identify service instances for Kerberos target
-computers.
+By default, only computer accounts have SPNs, which creates no significant risk, since machine accounts have a default domain policy that rotates their passwords every 30 days, and the password is composed of 120 random characters, making them invulnerable to Kerberoasting.
 
-By default, only computer accounts have SPNs, which creates no significant risk, since machine accounts have a default
-domain policy that rotates their passwords every 30 days, and the password is composed of 120 random characters, making
-them invulnerable to Kerberoasting.
+A user account with an SPN assigned is considered a service account, and is accessible to the entire domain. If any user in the directory requests a ticket-granting service (TGS), the domain controller will encrypt it with the secret key of the account executing the service. An attacker can potentially perform a Kerberoasting attack with this information, as the human-defined password is likely to be less complex.
 
-A user account with an SPN assigned is considered a service account, and is accessible to the entire domain. If any
-user in the directory requests a ticket-granting service (TGS), the domain controller will encrypt it with the secret
-key of the account executing the service. An attacker can potentially perform a Kerberoasting attack with this
-information, as the human-defined password is likely to be less complex.
+For scenarios where SPNs cannot be avoided on user accounts, Microsoft provides the Group Managed Service Accounts (gMSA) feature, which ensures that account passwords are robust and changed regularly and automatically. More information can be found https://docs.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview[here].
 
-For scenarios where SPNs cannot be avoided on user accounts, Microsoft provides the Group Managed Service Accounts (gMSA)
-feature, which ensures that account passwords are robust and changed regularly and automatically. More information can
-be found [here](https://docs.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview).
+Attackers can also perform "Targeted Kerberoasting", which consists of adding fake SPNs to user accounts that they have write privileges to, making them potentially vulnerable to Kerberoasting.
 
-Attackers can also perform "Targeted Kerberoasting", which consists of adding fake SPNs to user accounts that they have
-write privileges to, making them potentially vulnerable to Kerberoasting.
 
-#### Possible investigation steps
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
@@ -85,38 +80,63 @@ write privileges to, making them potentially vulnerable to Kerberoasting.
 - Investigate if tickets have been requested for the target account.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 
-### False positive analysis
 
-- The use of user accounts as service accounts is a bad security practice and should not be allowed in the domain. The
-security team should map and monitor any potential benign true positive (B-TP), especially if the account is privileged.
-Domain Administrators that define this kind of setting can put the domain at risk as user accounts don't have the same
-security standards as computer accounts (which have long, complex, random passwords that change frequently), exposing
-them to credential cracking attacks (Kerberoasting, brute force, etc.).
+*False positive analysis*
+
+
+- The use of user accounts as service accounts is a bad security practice and should not be allowed in the domain. The security team should map and monitor any potential benign true positive (B-TP), especially if the account is privileged. Domain Administrators that define this kind of setting can put the domain at risk as user accounts don't have the same security standards as computer accounts (which have long, complex, random passwords that change frequently), exposing them to credential cracking attacks (Kerberoasting, brute force, etc.).
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services. Prioritize privileged accounts.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services. Prioritize privileged accounts.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Directory Service Changes' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Changes (Success,Failure)
+```
+
+The above policy does not cover User objects, so set up an AuditRule using https://github.com/OTRF/Set-AuditRule.
+As this specifies the servicePrincipalName Attribute GUID, it is expected to be low noise.
+
+```
+Set-AuditRule -AdObjectPath 'AD:\CN=Users,DC=Domain,DC=com' -WellKnownSidType WorldSid -Rights WriteProperty -InheritanceFlags Children -AttributeGUID f3a64788-5306-11d1-a9c5-0000f80367c1 -AuditFlags Success
+```
 
 
 ==== Rule query
 
 
-[source,js]
+[source, js]
 ----------------------------------
 event.action:"Directory Service Changes" and event.code:5136 and
-winlog.event_data.ObjectClass:"user" and
-winlog.event_data.AttributeLDAPDisplayName:"servicePrincipalName"
-----------------------------------
+  winlog.event_data.OperationType:"%%14674" and
+  winlog.event_data.ObjectClass:"user" and
+  winlog.event_data.AttributeLDAPDisplayName:"servicePrincipalName"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -128,26 +148,7 @@ winlog.event_data.AttributeLDAPDisplayName:"servicePrincipalName"
 ** Name: Steal or Forge Kerberos Tickets
 ** ID: T1558
 ** Reference URL: https://attack.mitre.org/techniques/T1558/
-
-[[user-account-exposed-to-kerberoasting-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Directory Service Changes" and event.code:5136 and
-winlog.event_data.ObjectClass:"user" and
-winlog.event_data.AttributeLDAPDisplayName:"servicePrincipalName"
-----------------------------------
-
-Version 2 (8.3.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Kerberoasting
+** ID: T1558.003
+** Reference URL: https://attack.mitre.org/techniques/T1558/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/user-added-as-owner-for-azure-application.asciidoc b/docs/detections/prebuilt-rules/rule-details/user-added-as-owner-for-azure-application.asciidoc
index 3046ac769a..7ccefa98bd 100644
--- a/docs/detections/prebuilt-rules/rule-details/user-added-as-owner-for-azure-application.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/user-added-as-owner-for-azure-application.asciidoc
@@ -5,7 +5,7 @@ Identifies when a user is added as an owner for an Azure application. An adversa
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,50 +14,48 @@ Identifies when a user is added as an owner for an Azure application. An adversa
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
+*Tags*: 
 
-*Version*: 101 (<<user-added-as-owner-for-azure-application-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Configuration Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+==== Setup
 
 
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Add
-owner to application" and event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Add owner to application" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -69,34 +67,3 @@ owner to application" and event.outcome:(Success or success)
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[user-added-as-owner-for-azure-application-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Add
-owner to application" and event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/user-added-as-owner-for-azure-service-principal.asciidoc b/docs/detections/prebuilt-rules/rule-details/user-added-as-owner-for-azure-service-principal.asciidoc
index 041478bd36..4893b7473f 100644
--- a/docs/detections/prebuilt-rules/rule-details/user-added-as-owner-for-azure-service-principal.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/user-added-as-owner-for-azure-service-principal.asciidoc
@@ -5,7 +5,7 @@ Identifies when a user is added as an owner for an Azure service principal. The
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 * logs-azure*
@@ -14,54 +14,50 @@ Identifies when a user is added as an owner for an Azure service principal. The
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-25m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Cloud
-* Azure
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 101 (<<user-added-as-owner-for-azure-service-principal-history, version history>>)
+* Domain: Cloud
+* Data Source: Azure
+* Use Case: Configuration Audit
+* Tactic: Persistence
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
 
+==== Setup
+
+
+The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Add
-owner to service principal" and event.outcome:(Success or success)
+[source, js]
 ----------------------------------
+event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Add owner to service principal" and event.outcome:(Success or success)
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,34 +69,3 @@ owner to service principal" and event.outcome:(Success or success)
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[user-added-as-owner-for-azure-service-principal-history]]
-==== Rule version history
-
-Version 101 (8.6.0 release)::
-* Formatting only
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (7.13.0 release)::
-* Formatting only
-
-Version 4 (7.12.0 release)::
-* Formatting only
-
-Version 3 (7.11.2 release)::
-* Formatting only
-
-Version 2 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.dataset:azure.auditlogs and azure.auditlogs.operation_name:"Add
-owner to service principal" and event.outcome:Success
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/user-added-to-privileged-group.asciidoc b/docs/detections/prebuilt-rules/rule-details/user-added-to-privileged-group.asciidoc
index fcd479bb74..45c68bf3a2 100644
--- a/docs/detections/prebuilt-rules/rule-details/user-added-to-privileged-group.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/user-added-to-privileged-group.asciidoc
@@ -5,98 +5,119 @@ Identifies a user being added to a privileged group in Active Directory. Privile
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/appendix-b--privileged-accounts-and-groups-in-active-directory
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
-
-*Version*: 102 (<<user-added-to-privileged-group-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Resources: Investigation Guide
+* Use Case: Active Directory Monitoring
+* Data Source: Active Directory
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Skoetting
+* Elastic
+* Skoetting
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating User Added to Privileged Group in Active Directory
+*Triage and analysis*
 
-Privileged accounts and groups in Active Directory are those to which powerful rights, privileges, and permissions are
-granted that allow them to perform nearly any action in Active Directory and on domain-joined systems.
 
-Attackers can add users to privileged groups to maintain a level of access if their other privileged accounts are
-uncovered by the security team. This allows them to keep operating after the security team discovers abused accounts.
+
+*Investigating User Added to Privileged Group in Active Directory*
+
+
+Privileged accounts and groups in Active Directory are those to which powerful rights, privileges, and permissions are granted that allow them to perform nearly any action in Active Directory and on domain-joined systems.
+
+Attackers can add users to privileged groups to maintain a level of access if their other privileged accounts are uncovered by the security team. This allows them to keep operating after the security team discovers abused accounts.
 
 This rule monitors events related to a user being added to a privileged group.
 
-#### Possible investigation steps
+
+*Possible investigation steps*
+
 
 - Identify the user account that performed the action and whether it should manage members of this group.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 
-### False positive analysis
 
-- This attack abuses a legitimate Active Directory mechanism, so it is important to determine whether the activity is
-legitimate, if the administrator is authorized to perform this operation, and if there is a need to grant the account
-this level of privilege.
+*False positive analysis*
+
+
+- This attack abuses a legitimate Active Directory mechanism, so it is important to determine whether the activity is legitimate, if the administrator is authorized to perform this operation, and if there is a need to grant the account this level of privilege.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - If the admin is not aware of the operation, activate your Active Directory incident response plan.
 - If the user does not need the administrator privileges, remove the account from the privileged group.
 - Review the privileges of the administrator account that performed the action.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-iam where event.action == "added-member-to-group" and group.name :
-("Admin*", "Local Administrators",
-"Domain Admins", "Enterprise Admins",
-"Backup Admins", "Schema Admins",
-"DnsAdmins", "Exchange Organization Administrators")
+[source, js]
 ----------------------------------
+iam where winlog.api:"wineventlog" and event.action == "added-member-to-group" and
+  group.name : ("Admin*",
+                "Local Administrators",
+                "Domain Admins",
+                "Enterprise Admins",
+                "Backup Admins",
+                "Schema Admins",
+                "DnsAdmins",
+                "Exchange Organization Administrators")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -108,35 +129,3 @@ iam where event.action == "added-member-to-group" and group.name :
 ** Name: Account Manipulation
 ** ID: T1098
 ** Reference URL: https://attack.mitre.org/techniques/T1098/
-
-[[user-added-to-privileged-group-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Rule name changed from: User Added to Privileged Group in Active Directory
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.16.0 release)::
-* Formatting only
-
-Version 2 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:iam and event.action:"added-member-to-group" and
-group.name:(Administrators or "Local Administrators" or "Domain
-Admins" or "Enterprise Admins" or "Backup Admins" or "Schema Admins"
-or "DnsAdmins")
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/veeam-backup-library-loaded-by-unusual-process.asciidoc b/docs/detections/prebuilt-rules/rule-details/veeam-backup-library-loaded-by-unusual-process.asciidoc
new file mode 100644
index 0000000000..5950e6927d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/veeam-backup-library-loaded-by-unusual-process.asciidoc
@@ -0,0 +1,81 @@
+[[veeam-backup-library-loaded-by-unusual-process]]
+=== Veeam Backup Library Loaded by Unusual Process
+
+Identifies potential credential decrypt operations by PowerShell or unsigned processes using the Veeam.Backup.Common.dll library. Attackers can use Veeam Credentials to target backups as part of destructive operations such as Ransomware attacks.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.library-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+library where host.os.type == "windows" and event.action == "load" and
+  (dll.name : "Veeam.Backup.Common.dll" or dll.pe.original_file_name : "Veeam.Backup.Common.dll") and
+  (
+    process.code_signature.trusted == false or
+    process.code_signature.exists == false or
+    process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe")
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Credential Access
+** ID: TA0006
+** Reference URL: https://attack.mitre.org/tactics/TA0006/
+* Technique:
+** Name: OS Credential Dumping
+** ID: T1003
+** Reference URL: https://attack.mitre.org/techniques/T1003/
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/virtual-machine-fingerprinting-via-grep.asciidoc b/docs/detections/prebuilt-rules/rule-details/virtual-machine-fingerprinting-via-grep.asciidoc
index 1d13dbdada..1a7c699165 100644
--- a/docs/detections/prebuilt-rules/rule-details/virtual-machine-fingerprinting-via-grep.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/virtual-machine-fingerprinting-via-grep.asciidoc
@@ -5,7 +5,7 @@ An adversary may attempt to get detailed information about the operating system
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
@@ -14,62 +14,59 @@ An adversary may attempt to get detailed information about the operating system
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://objective-see.com/blog/blog_0x4F.html
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* macOS
-* Linux
-* Threat Detection
-* Discovery
-
-*Version*: 100 (<<virtual-machine-fingerprinting-via-grep-history, version history>>)
+* Domain: Endpoint
+* OS: macOS
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Certain tools or automated software may enumerate hardware information. These tools can be exempted via user name or process arguments to eliminate potential noise.
+==== Setup
 
-==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
+*Setup*
 
-----------------------------------
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name in ("grep",
-"egrep") and user.id != "0" and process.args : ("parallels*",
-"vmware*", "virtualbox*") and process.args : "Manufacturer*" and not
-process.parent.executable in
-("/Applications/Docker.app/Contents/MacOS/Docker",
-"/usr/libexec/kcare/virt-what")
+[source, js]
 ----------------------------------
+process where event.type == "start" and
+ process.name in ("grep", "egrep") and user.id != "0" and
+ process.args : ("parallels*", "vmware*", "virtualbox*") and process.args : "Manufacturer*" and
+ not process.parent.executable in ("/Applications/Docker.app/Contents/MacOS/Docker", "/usr/libexec/kcare/virt-what")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -81,26 +78,3 @@ process.parent.executable in
 ** Name: System Information Discovery
 ** ID: T1082
 ** Reference URL: https://attack.mitre.org/techniques/T1082/
-
-[[virtual-machine-fingerprinting-via-grep-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.name in ("grep",
-"egrep") and user.id != "0" and process.args : ("parallels*",
-"vmware*", "virtualbox*") and process.args : "Manufacturer*" and not
-process.parent.executable in
-("/Applications/Docker.app/Contents/MacOS/Docker",
-"/usr/libexec/kcare/virt-what")
-----------------------------------
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/virtual-machine-fingerprinting.asciidoc b/docs/detections/prebuilt-rules/rule-details/virtual-machine-fingerprinting.asciidoc
index 8973622421..298f7a66f8 100644
--- a/docs/detections/prebuilt-rules/rule-details/virtual-machine-fingerprinting.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/virtual-machine-fingerprinting.asciidoc
@@ -5,98 +5,117 @@ An adversary may attempt to get detailed information about the operating system
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * logs-endpoint.events.*
+* endgame-*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Threat Detection
-* Discovery
+*Tags*: 
 
-*Version*: 100 (<<virtual-machine-fingerprinting-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.8.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
 
-Certain tools or automated software may enumerate hardware information. These tools can be exempted via user name or process arguments to eliminate potential noise.
+==== Setup
 
-==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.args:("/sys/class/dmi/id/bios_version" or
-"/sys/class/dmi/id/product_name" or
-"/sys/class/dmi/id/chassis_vendor" or
-"/proc/scsi/scsi" or "/proc/ide/hd0/model") and not
-user.name:root
-----------------------------------
+*Setup*
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+This rule requires data coming in from one of the following integrations:
+- Elastic Defend
+- Auditbeat
 
-* Tactic:
-** Name: Discovery
-** ID: TA0007
-** Reference URL: https://attack.mitre.org/tactics/TA0007/
-* Technique:
-** Name: System Information Discovery
-** ID: T1082
-** Reference URL: https://attack.mitre.org/techniques/T1082/
 
-[[virtual-machine-fingerprinting-history]]
-==== Rule version history
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
 
-Version 100 (8.5.0 release)::
-* Formatting only
 
-Version 7 (8.4.0 release)::
-* Formatting only
+*The following steps should be executed in order to add the Elastic Defend integration on a Linux System:*
 
-Version 6 (7.12.0 release)::
-* Formatting only
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Version 5 (7.11.2 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Formatting only
+*Auditbeat Setup*
+
+Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
+
+
+*The following steps should be executed in order to add the Auditbeat on a Linux System:*
+
+- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
+- To install the APT and YUM repositories follow the setup instructions in this https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html[helper guide].
+- To run Auditbeat on Docker follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html[helper guide].
+- To run Auditbeat on Kubernetes follow the setup instructions in the https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html[helper guide].
+- For complete “Setup and Run Auditbeat” information refer to the https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html[helper guide].
+
+
+==== Rule query
 
-Version 3 (7.9.1 release)::
-* Formatting only
 
-Version 2 (7.9.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-event.action:executed and
-process.args:("/sys/class/dmi/id/bios_version" or
-"/sys/class/dmi/id/product_name" or "/sys/class/dmi/id/chassis_vendor"
-or "/proc/scsi/scsi" or "/proc/ide/hd0/model") and not user.name:root
+event.category:process and host.os.type:linux and event.type:(start or process_started) and
+  process.args:("/sys/class/dmi/id/bios_version" or
+                "/sys/class/dmi/id/product_name" or
+                "/sys/class/dmi/id/chassis_vendor" or
+                "/proc/scsi/scsi" or
+                "/proc/ide/hd0/model") and
+  not user.name:root
+
 ----------------------------------
 
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/virtual-private-network-connection-attempt.asciidoc b/docs/detections/prebuilt-rules/rule-details/virtual-private-network-connection-attempt.asciidoc
index 2fa95ecd8e..e3ccfde63a 100644
--- a/docs/detections/prebuilt-rules/rule-details/virtual-private-network-connection-attempt.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/virtual-private-network-connection-attempt.asciidoc
@@ -5,68 +5,93 @@ Identifies the execution of macOS built-in commands to connect to an existing Vi
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://github.com/rapid7/metasploit-framework/blob/master/modules/post/osx/manage/vpn.rb
 * https://www.unix.com/man-page/osx/8/networksetup/
 * https://superuser.com/questions/358513/start-configured-vpn-from-command-line-osx
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+
+*Version*: 107
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Lateral Movement
 
-*Version*: 100 (<<virtual-private-network-connection-attempt-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+This rule requires data coming in from Elastic Defend.
 
-----------------------------------
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type in ("start", "process_started") and (
-(process.name : "networksetup" and process.args :
-"-connectpppoeservice") or (process.name : "scutil" and
-process.args : "--nc" and process.args : "start") or (process.name
-: "osascript" and process.command_line : "osascript*set VPN to
-service*") )
+[source, js]
 ----------------------------------
+process where host.os.type == "macos" and event.type in ("start", "process_started") and
+  (
+    (process.name : "networksetup" and process.args : "-connectpppoeservice") or
+    (process.name : "scutil" and process.args : "--nc" and process.args : "start") or
+    (process.name : "osascript" and process.command_line : "osascript*set VPN to service*")
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -78,16 +103,3 @@ service*") )
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[virtual-private-network-connection-attempt-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 4 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.2.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/vnc-virtual-network-computing-from-the-internet.asciidoc b/docs/detections/prebuilt-rules/rule-details/vnc-virtual-network-computing-from-the-internet.asciidoc
index 31fe6e5058..a886691fe0 100644
--- a/docs/detections/prebuilt-rules/rule-details/vnc-virtual-network-computing-from-the-internet.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/vnc-virtual-network-computing-from-the-internet.asciidoc
@@ -5,70 +5,84 @@ This rule detects network events that may indicate the use of VNC traffic from t
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Network
-* Threat Detection
-* Command and Control
-* Host
+* Tactic: Command and Control
+* Domain: Endpoint
+* Use Case: Threat Detection
 
-*Version*: 100 (<<vnc-virtual-network-computing-from-the-internet-history, version history>>)
+*Version*: 104
 
-*Added ({stack} release)*: 7.6.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-VNC connections may be received directly to Linux cloud server instances but such connections are usually made only by engineers. VNC is less common than SSH or RDP but may be required by some work-flows such as remote access and support for specialized software products or servers. Such work-flows are usually known and not unexpected. Usage that is unfamiliar to server or network owners can be unexpected and suspicious.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and destination.port >= 5800 and destination.port <= 5810 and not
-source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
-172.16.0.0/12 or 192.0.0.0/24 or 192.0.0.0/29 or
-192.0.0.8/32 or 192.0.0.9/32 or 192.0.0.10/32 or
-192.0.0.170/32 or 192.0.0.171/32 or 192.0.2.0/24 or
-192.31.196.0/24 or 192.52.193.0/24 or 192.168.0.0/16 or
-192.88.99.0/24 or 224.0.0.0/4 or 100.64.0.0/10 or
-192.175.48.0/24 or 198.18.0.0/15 or 198.51.100.0/24 or
-203.0.113.0/24 or 240.0.0.0/4 or "::1" or "FE80::/10" or
-"FF00::/8" ) and destination.ip:( 10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16 )
+[source, js]
 ----------------------------------
+(event.dataset: network_traffic.flow or (event.category: (network or network_traffic))) and
+  network.transport:tcp and destination.port >= 5800 and destination.port <= 5810 and
+  not source.ip:(
+    10.0.0.0/8 or
+    127.0.0.0/8 or
+    169.254.0.0/16 or
+    172.16.0.0/12 or
+    192.0.0.0/24 or
+    192.0.0.0/29 or
+    192.0.0.8/32 or
+    192.0.0.9/32 or
+    192.0.0.10/32 or
+    192.0.0.170/32 or
+    192.0.0.171/32 or
+    192.0.2.0/24 or
+    192.31.196.0/24 or
+    192.52.193.0/24 or
+    192.168.0.0/16 or
+    192.88.99.0/24 or
+    224.0.0.0/4 or
+    100.64.0.0/10 or
+    192.175.48.0/24 or
+    198.18.0.0/15 or
+    198.51.100.0/24 or
+    203.0.113.0/24 or
+    240.0.0.0/4 or
+    "::1" or
+    "FE80::/10" or
+    "FF00::/8"
+  ) and
+  destination.ip:(
+    10.0.0.0/8 or
+    172.16.0.0/12 or
+    192.168.0.0/16
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,8 +94,6 @@ source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
 ** Name: Remote Access Software
 ** ID: T1219
 ** Reference URL: https://attack.mitre.org/techniques/T1219/
-
-
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -90,75 +102,3 @@ source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[vnc-virtual-network-computing-from-the-internet-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 12 (8.4.0 release)::
-* Formatting only
-
-Version 11 (7.15.0 release)::
-* Formatting only
-
-Version 10 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and destination.port >= 5800 and destination.port <= 5810 and not
-source.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
-172.16.0.0/12 or 192.168.0.0/16 or 224.0.0.0/4 or "::1" or "FE80::/10"
-or "FF00::/8" ) and destination.ip:( 10.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 )
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and destination.port >= 5800 and destination.port <= 5810 and not
-source.ip:(10.0.0.0/8 or 127.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 or "::1") and destination.ip:(10.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport:tcp and destination.port >= 5800 and
-destination.port <= 5810 and not source.ip:(10.0.0.0/8 or 127.0.0.0/8
-or 172.16.0.0/12 or 192.168.0.0/16 or "::1") and
-destination.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16)
-----------------------------------
-
-Version 3 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport: tcp and (destination.port >= 5800 and
-destination.port <= 5810) and ( network.direction: inbound or ( not
-source.ip: (10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) and
-destination.ip: (10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) ) )
-----------------------------------
-
-Version 2 (7.6.1 release)::
-* Removed auditbeat-\*, packetbeat-*, and winlogbeat-* from the rule indices.
-
diff --git a/docs/detections/prebuilt-rules/rule-details/vnc-virtual-network-computing-to-the-internet.asciidoc b/docs/detections/prebuilt-rules/rule-details/vnc-virtual-network-computing-to-the-internet.asciidoc
index 5cbf53ddf2..48e51a26a7 100644
--- a/docs/detections/prebuilt-rules/rule-details/vnc-virtual-network-computing-to-the-internet.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/vnc-virtual-network-computing-to-the-internet.asciidoc
@@ -5,70 +5,84 @@ This rule detects network events that may indicate the use of VNC traffic to the
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
+* packetbeat-*
 * auditbeat-*
 * filebeat-*
-* packetbeat-*
-* logs-endpoint.events.*
+* logs-network_traffic.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Network
-* Threat Detection
-* Command and Control
-* Host
+* Tactic: Command and Control
+* Domain: Endpoint
+* Use Case: Threat Detection
 
-*Version*: 100 (<<vnc-virtual-network-computing-to-the-internet-history, version history>>)
+*Version*: 104
 
-*Added ({stack} release)*: 7.6.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.5.0
-
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-VNC connections may be made directly to Linux cloud server instances but such connections are usually made only by engineers. VNC is less common than SSH or RDP but may be required by some work flows such as remote access and support for specialized software products or servers. Such work-flows are usually known and not unexpected. Usage that is unfamiliar to server or network owners can be unexpected and suspicious.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and destination.port >= 5800 and destination.port <= 5810 and
-source.ip:( 10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16
-) and not destination.ip:( 10.0.0.0/8 or 127.0.0.0/8 or
-169.254.0.0/16 or 172.16.0.0/12 or 192.0.0.0/24 or
-192.0.0.0/29 or 192.0.0.8/32 or 192.0.0.9/32 or
-192.0.0.10/32 or 192.0.0.170/32 or 192.0.0.171/32 or
-192.0.2.0/24 or 192.31.196.0/24 or 192.52.193.0/24 or
-192.168.0.0/16 or 192.88.99.0/24 or 224.0.0.0/4 or
-100.64.0.0/10 or 192.175.48.0/24 or 198.18.0.0/15 or
-198.51.100.0/24 or 203.0.113.0/24 or 240.0.0.0/4 or "::1"
-or "FE80::/10" or "FF00::/8" )
+[source, js]
 ----------------------------------
+(event.dataset: network_traffic.flow  or (event.category: (network or network_traffic))) and
+  network.transport:tcp and destination.port >= 5800 and destination.port <= 5810 and
+  source.ip:(
+    10.0.0.0/8 or
+    172.16.0.0/12 or
+    192.168.0.0/16
+  ) and
+  not destination.ip:(
+    10.0.0.0/8 or
+    127.0.0.0/8 or
+    169.254.0.0/16 or
+    172.16.0.0/12 or
+    192.0.0.0/24 or
+    192.0.0.0/29 or
+    192.0.0.8/32 or
+    192.0.0.9/32 or
+    192.0.0.10/32 or
+    192.0.0.170/32 or
+    192.0.0.171/32 or
+    192.0.2.0/24 or
+    192.31.196.0/24 or
+    192.52.193.0/24 or
+    192.168.0.0/16 or
+    192.88.99.0/24 or
+    224.0.0.0/4 or
+    100.64.0.0/10 or
+    192.175.48.0/24 or
+    198.18.0.0/15 or
+    198.51.100.0/24 or
+    203.0.113.0/24 or
+    240.0.0.0/4 or
+    "::1" or
+    "FE80::/10" or
+    "FF00::/8"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -80,75 +94,3 @@ or "FE80::/10" or "FF00::/8" )
 ** Name: Remote Access Software
 ** ID: T1219
 ** Reference URL: https://attack.mitre.org/techniques/T1219/
-
-[[vnc-virtual-network-computing-to-the-internet-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 12 (8.4.0 release)::
-* Formatting only
-
-Version 11 (7.15.0 release)::
-* Formatting only
-
-Version 10 (7.14.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and destination.port >= 5800 and destination.port <= 5810 and
-source.ip:( 10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16 ) and not
-destination.ip:( 10.0.0.0/8 or 127.0.0.0/8 or 169.254.0.0/16 or
-172.16.0.0/12 or 192.168.0.0/16 or 224.0.0.0/4 or "::1" or "FE80::/10"
-or "FF00::/8" )
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:(network or network_traffic) and network.transport:tcp
-and destination.port >= 5800 and destination.port <= 5810 and
-source.ip:(10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) and not
-destination.ip:(10.0.0.0/8 or 127.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16 or "::1")
-----------------------------------
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport:tcp and destination.port >= 5800 and
-destination.port <= 5810 and source.ip:(10.0.0.0/8 or 172.16.0.0/12 or
-192.168.0.0/16) and not destination.ip:(10.0.0.0/8 or 127.0.0.0/8 or
-172.16.0.0/12 or 192.168.0.0/16 or "::1")
-----------------------------------
-
-Version 3 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-network.transport: tcp and (destination.port >= 5800 and
-destination.port <= 5810) and ( network.direction: outbound or (
-source.ip: (10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) and not
-destination.ip: (10.0.0.0/8 or 172.16.0.0/12 or 192.168.0.0/16) ) )
-----------------------------------
-
-Version 2 (7.6.1 release)::
-* Removed auditbeat-\*, packetbeat-*, and winlogbeat-* from the rule indices.
-
diff --git a/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deleted-or-resized-via-vssadmin.asciidoc b/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deleted-or-resized-via-vssadmin.asciidoc
index cdab4ef972..b39522eee7 100644
--- a/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deleted-or-resized-via-vssadmin.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deleted-or-resized-via-vssadmin.asciidoc
@@ -5,63 +5,67 @@ Identifies use of vssadmin.exe for shadow copy deletion or resizing on endpoints
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Impact
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<volume-shadow-copy-deleted-or-resized-via-vssadmin-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Volume Shadow Copy Deleted or Resized via VssAdmin
+*Triage and analysis*
+
+
+
+*Investigating Volume Shadow Copy Deleted or Resized via VssAdmin*
+
 
-The Volume Shadow Copy Service (VSS) is a Windows feature that enables system administrators to take snapshots of volumes
-that can later be restored or mounted to recover specific files or folders.
+The Volume Shadow Copy Service (VSS) is a Windows feature that enables system administrators to take snapshots of volumes that can later be restored or mounted to recover specific files or folders.
 
-A typical step in the playbook of an attacker attempting to deploy ransomware is to delete Volume Shadow
-Copies to ensure that victims have no alternative to paying the ransom, making any action that deletes shadow
-copies worth monitoring.
+A typical step in the playbook of an attacker attempting to deploy ransomware is to delete Volume Shadow Copies to ensure that victims have no alternative to paying the ransom, making any action that deletes shadow copies worth monitoring.
 
 This rule monitors the execution of Vssadmin.exe to either delete or resize shadow copies.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - In the case of a resize operation, check if the resize value is equal to suspicious values, like 401MB.
@@ -79,17 +83,22 @@ for prevalence, whether they are located in expected locations, and if they are
 - Check if any files on the host machine have been encrypted.
 
 
-### False positive analysis
 
-- This rule may produce benign true positives (B-TPs). If this activity is expected and noisy in your
-environment, consider adding exceptions — preferably with a combination of user and command line conditions.
+*False positive analysis*
+
+
+- This rule may produce benign true positives (B-TPs). If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of user and command line conditions.
+
+
+*Related rules*
 
-### Related rules
 
 - Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
 - Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
@@ -98,33 +107,40 @@ environment, consider adding exceptions — preferably with a combination of use
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
 - If data was encrypted, deleted, or modified, activate your data recovery plan.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Perform data recovery locally or restore the backups from replicated copies (cloud, other servers, etc.).
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-"vssadmin.exe" or process.pe.original_file_name == "VSSADMIN.EXE") and
-process.args in ("delete", "resize") and process.args : "shadows*"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start"
+  and (process.name : "vssadmin.exe" or ?process.pe.original_file_name == "VSSADMIN.EXE") and
+  process.args in ("delete", "resize") and process.args : "shadows*"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -136,96 +152,3 @@ process.args in ("delete", "resize") and process.args : "shadows*"
 ** Name: Inhibit System Recovery
 ** ID: T1490
 ** Reference URL: https://attack.mitre.org/techniques/T1490/
-
-[[volume-shadow-copy-deleted-or-resized-via-vssadmin-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "vssadmin.exe" or process.pe.original_file_name ==
-"VSSADMIN.EXE") and process.args in ("delete", "resize") and
-process.args : "shadows*"
-----------------------------------
-
-Version 15 (8.4.0 release)::
-* Formatting only
-
-Version 13 (8.3.0 release)::
-* Formatting only
-
-Version 12 (8.2.0 release)::
-* Formatting only
-
-Version 11 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-event.action == "start" and (process.name : "vssadmin.exe" or
-process.pe.original_file_name == "VSSADMIN.EXE") and process.args in
-("delete", "resize") and process.args : "shadows*"
-----------------------------------
-
-Version 10 (7.16.0 release)::
-* Rule name changed from: Volume Shadow Copy Deletion via VssAdmin
-+
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "vssadmin.exe" or process.pe.original_file_name ==
-"VSSADMIN.EXE") and process.args : "delete" and process.args :
-"shadows"
-----------------------------------
-
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:vssadmin.exe and process.args:(delete and shadows)
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:vssadmin.exe and process.args:(delete and shadows)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:"vssadmin.exe" and process.args:("delete" and "shadows")
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deletion-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deletion-via-powershell.asciidoc
index 8d52038149..22eccfa8bb 100644
--- a/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deletion-via-powershell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deletion-via-powershell.asciidoc
@@ -5,67 +5,71 @@ Identifies the use of the Win32_ShadowCopy class and related cmdlets to achieve
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/previous-versions/windows/desktop/vsswmi/win32-shadowcopy
 * https://powershell.one/wmi/root/cimv2/win32_shadowcopy
 * https://www.fortinet.com/blog/threat-research/stomping-shadow-copies-a-second-look-into-deletion-methods
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Impact
-* Investigation Guide
-
-*Version*: 102 (<<volume-shadow-copy-deletion-via-powershell-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.16.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Austin Songer
+* Elastic
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Volume Shadow Copy Deletion via PowerShell
+*Triage and analysis*
+
+
+
+*Investigating Volume Shadow Copy Deletion via PowerShell*
+
+
+The Volume Shadow Copy Service (VSS) is a Windows feature that enables system administrators to take snapshots of volumes that can later be restored or mounted to recover specific files or folders.
+
+A typical step in the playbook of an attacker attempting to deploy ransomware is to delete Volume Shadow Copies to ensure that victims have no alternative to paying the ransom, making any action that deletes shadow copies worth monitoring.
 
-The Volume Shadow Copy Service (VSS) is a Windows feature that enables system administrators to take snapshots of volumes
-that can later be restored or mounted to recover specific files or folders.
+This rule monitors the execution of PowerShell cmdlets to interact with the Win32_ShadowCopy WMI class, retrieve shadow copy objects, and delete them.
 
-A typical step in the playbook of an attacker attempting to deploy ransomware is to delete Volume Shadow
-Copies to ensure that victims have no alternative to paying the ransom, making any action that deletes shadow
-copies worth monitoring.
 
-This rule monitors the execution of PowerShell cmdlets to interact with the Win32_ShadowCopy WMI class, retrieve shadow
-copy objects, and delete them.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Investigate the program execution chain (parent process tree).
 - Check whether the account is authorized to perform this operation.
@@ -84,17 +88,22 @@ copy objects, and delete them.
 - Check if any files on the host machine have been encrypted.
 
 
-### False positive analysis
 
-- This rule has chances of producing benign true positives (B-TPs). If this activity is expected and noisy in your
-environment, consider adding exceptions — preferably with a combination of user and command line conditions.
+*False positive analysis*
+
+
+- This rule has chances of producing benign true positives (B-TPs). If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of user and command line conditions.
+
+
+*Related rules*
 
-### Related rules
 
 - Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
 - Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
@@ -103,36 +112,42 @@ environment, consider adding exceptions — preferably with a combination of use
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
 - If data was encrypted, deleted, or modified, activate your data recovery plan.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Perform data recovery locally or restore the backups from replicated copies (cloud, other servers, etc.).
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name :
-("powershell.exe", "pwsh.exe", "powershell_ise.exe") and
-process.args : ("*Get-WmiObject*", "*gwmi*", "*Get-CimInstance*",
-"*gcim*") and process.args : ("*Win32_ShadowCopy*") and
-process.args : ("*.Delete()*", "*Remove-WmiObject*", "*rwmi*",
-"*Remove-CimInstance*", "*rcim*")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe") and
+  process.args : ("*Get-WmiObject*", "*gwmi*", "*Get-CimInstance*", "*gcim*") and
+  process.args : ("*Win32_ShadowCopy*") and
+  process.args : ("*.Delete()*", "*Remove-WmiObject*", "*rwmi*", "*Remove-CimInstance*", "*rcim*")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -144,42 +159,15 @@ process.args : ("*.Delete()*", "*Remove-WmiObject*", "*rwmi*",
 ** Name: Inhibit System Recovery
 ** ID: T1490
 ** Reference URL: https://attack.mitre.org/techniques/T1490/
-
-[[volume-shadow-copy-deletion-via-powershell-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe")
-and process.args : ("*Get-WmiObject*", "*gwmi*", "*Get-
-CimInstance*", "*gcim*") and process.args : ("*Win32_ShadowCopy*")
-and process.args : ("*.Delete()*", "*Remove-WmiObject*", "*rwmi*",
-"*Remove-CimInstance*", "*rcim*")
-----------------------------------
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe")
-and process.args : ("*Get-WmiObject*", "*gwmi*", "*Get-
-CimInstance*", "*gcim*") and process.args : ("*Win32_ShadowCopy*")
-and process.args : ("*.Delete()*", "*Remove-WmiObject*", "*rwmi*",
-"*Remove-CimInstance*", "*rcim*")
-----------------------------------
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deletion-via-wmic.asciidoc b/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deletion-via-wmic.asciidoc
index 262e1c403a..163a1654cb 100644
--- a/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deletion-via-wmic.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/volume-shadow-copy-deletion-via-wmic.asciidoc
@@ -5,60 +5,66 @@ Identifies use of wmic.exe for shadow copy deletion on endpoints. This commonly
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Impact
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<volume-shadow-copy-deletion-via-wmic-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Impact
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Volume Shadow Copy Deletion via WMIC
+*Triage and analysis*
+
+
+
+*Investigating Volume Shadow Copy Deletion via WMIC*
+
 
-The Volume Shadow Copy Service (VSS) is a Windows feature that enables system administrators to take snapshots of volumes
-that can later be restored or mounted to recover specific files or folders.
+The Volume Shadow Copy Service (VSS) is a Windows feature that enables system administrators to take snapshots of volumes that can later be restored or mounted to recover specific files or folders.
 
-A typical step in the playbook of an attacker attempting to deploy ransomware is to delete Volume Shadow
-Copies to ensure that victims have no alternative to paying the ransom, making any action that deletes shadow
-copies worth monitoring.
+A typical step in the playbook of an attacker attempting to deploy ransomware is to delete Volume Shadow Copies to ensure that victims have no alternative to paying the ransom, making any action that deletes shadow copies worth monitoring.
 
 This rule monitors the execution of `wmic.exe` to interact with VSS via the `shadowcopy` alias and delete parameter.
 
-#### Possible investigation steps
+
+*Possible investigation steps*
+
 
 - Investigate the program execution chain (parent process tree).
 - Check whether the account is authorized to perform this operation.
@@ -78,17 +84,22 @@ This rule monitors the execution of `wmic.exe` to interact with VSS via the `sha
 - Check if any files on the host machine have been encrypted.
 
 
-### False positive analysis
 
-- This rule has chances of producing benign true positives (B-TPs). If this activity is expected and noisy in your
-environment, consider adding exceptions — preferably with a combination of user and command line conditions.
+*False positive analysis*
+
+
+- This rule has chances of producing benign true positives (B-TPs). If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of user and command line conditions.
+
+
+*Related rules*
 
-### Related rules
 
 - Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
 - Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Priority should be given due to the advanced stage of this activity on the attack.
@@ -97,33 +108,40 @@ environment, consider adding exceptions — preferably with a combination of use
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
 - If data was encrypted, deleted, or modified, activate your data recovery plan.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Perform data recovery locally or restore the backups from replicated copies (cloud, other servers, etc.).
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name : "WMIC.exe"
-or process.pe.original_file_name == "wmic.exe") and process.args :
-"delete" and process.args : "shadowcopy"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  (process.name : "WMIC.exe" or ?process.pe.original_file_name == "wmic.exe") and
+  process.args : "delete" and process.args : "shadowcopy"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -135,75 +153,11 @@ or process.pe.original_file_name == "wmic.exe") and process.args :
 ** Name: Inhibit System Recovery
 ** ID: T1490
 ** Reference URL: https://attack.mitre.org/techniques/T1490/
-
-[[volume-shadow-copy-deletion-via-wmic-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-(process.name : "WMIC.exe" or process.pe.original_file_name ==
-"wmic.exe") and process.args : "delete" and process.args :
-"shadowcopy"
-----------------------------------
-
-Version 14 (8.4.0 release)::
-* Formatting only
-
-Version 12 (8.3.0 release)::
-* Formatting only
-
-Version 11 (8.2.0 release)::
-* Formatting only
-
-Version 10 (7.16.0 release)::
-* Formatting only
-
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:WMIC.exe and process.args:(delete and shadowcopy)
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:WMIC.exe and process.args:(delete and shadowcopy)
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.name:"WMIC.exe" and process.args:("shadowcopy" and "delete")
-----------------------------------
-
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Windows Management Instrumentation
+** ID: T1047
+** Reference URL: https://attack.mitre.org/techniques/T1047/
diff --git a/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-post-request-declined.asciidoc b/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-post-request-declined.asciidoc
index 68be9d1074..9d3ed969d1 100644
--- a/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-post-request-declined.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-post-request-declined.asciidoc
@@ -5,7 +5,7 @@ A POST request to a web application returned a 403 response, which indicates the
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * apm-*-transaction*
 * traces-apm*
@@ -14,76 +14,34 @@ A POST request to a web application returned a 403 response, which indicates the
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://en.wikipedia.org/wiki/HTTP_403
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* APM
-
-*Version*: 100 (<<web-application-suspicious-activity-post-request-declined-history, version history>>)
+* Data Source: APM
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Security scans and tests may result in these errors. Misconfigured or buggy applications may produce large numbers of these errors. If the source is unexpected, the user unauthorized, or the request unusual, these may indicate suspicious or malicious activity.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-http.response.status_code:403 and http.request.method:post
-----------------------------------
-
-
-[[web-application-suspicious-activity-post-request-declined-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 8 (7.15.0 release)::
-* Formatting only
-
-Version 7 (7.14.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
 http.response.status_code:403 and http.request.method:post
-----------------------------------
-
-Version 6 (7.12.0 release)::
-* Formatting only
-
-Version 5 (7.11.2 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Formatting only
-
-Version 2 (7.7.0 release)::
-* Formatting only
 
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-sqlmap-user-agent.asciidoc b/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-sqlmap-user-agent.asciidoc
index 57116afe8e..3bf0a25608 100644
--- a/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-sqlmap-user-agent.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-sqlmap-user-agent.asciidoc
@@ -5,7 +5,7 @@ This is an example of how to detect an unwanted web client user agent. This sear
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * apm-*-transaction*
 * traces-apm*
@@ -14,73 +14,34 @@ This is an example of how to detect an unwanted web client user agent. This sear
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * http://sqlmap.org/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* APM
-
-*Version*: 100 (<<web-application-suspicious-activity-sqlmap-user-agent-history, version history>>)
+* Data Source: APM
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-This rule does not indicate that a SQL injection attack occurred, only that the `sqlmap` tool was used. Security scans and tests may result in these errors. If the source is not an authorized security tester, this is generally suspicious or malicious activity.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-user_agent.original:"sqlmap/1.3.11#stable (http://sqlmap.org)"
-----------------------------------
-
-
-[[web-application-suspicious-activity-sqlmap-user-agent-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 7 (7.14.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
 user_agent.original:"sqlmap/1.3.11#stable (http://sqlmap.org)"
-----------------------------------
-
-Version 6 (7.12.0 release)::
-* Formatting only
-
-Version 5 (7.11.2 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Formatting only
-
-Version 2 (7.7.0 release)::
-* Formatting only
 
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-unauthorized-method.asciidoc b/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-unauthorized-method.asciidoc
index 2c42542551..ad45382b80 100644
--- a/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-unauthorized-method.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/web-application-suspicious-activity-unauthorized-method.asciidoc
@@ -5,7 +5,7 @@ A request to a web application returned a 405 response, which indicates the web
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * apm-*-transaction*
 * traces-apm*
@@ -14,76 +14,34 @@ A request to a web application returned a 405 response, which indicates the web
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://en.wikipedia.org/wiki/HTTP_405
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* APM
-
-*Version*: 100 (<<web-application-suspicious-activity-unauthorized-method-history, version history>>)
+* Data Source: APM
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 102
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Security scans and tests may result in these errors. Misconfigured or buggy applications may produce large numbers of these errors. If the source is unexpected, the user unauthorized, or the request unusual, these may indicate suspicious or malicious activity.
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-http.response.status_code:405
-----------------------------------
-
-
-[[web-application-suspicious-activity-unauthorized-method-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 9 (8.4.0 release)::
-* Formatting only
-
-Version 8 (7.15.0 release)::
-* Formatting only
-
-Version 7 (7.14.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
 http.response.status_code:405
-----------------------------------
-
-Version 6 (7.12.0 release)::
-* Formatting only
-
-Version 5 (7.11.2 release)::
-* Formatting only
-
-Version 4 (7.10.0 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Formatting only
-
-Version 2 (7.7.0 release)::
-* Formatting only
 
+----------------------------------
diff --git a/docs/detections/prebuilt-rules/rule-details/web-shell-detection-script-process-child-of-common-web-processes.asciidoc b/docs/detections/prebuilt-rules/rule-details/web-shell-detection-script-process-child-of-common-web-processes.asciidoc
index 40b18908fe..d600c233e3 100644
--- a/docs/detections/prebuilt-rules/rule-details/web-shell-detection-script-process-child-of-common-web-processes.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/web-shell-detection-script-process-child-of-common-web-processes.asciidoc
@@ -5,72 +5,71 @@ Identifies suspicious commands executed via a web server, which may suggest a vu
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
+* endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.microsoft.com/security/blog/2020/02/04/ghost-in-the-shell-investigating-web-shell-attacks/
 * https://www.elastic.co/security-labs/elastic-response-to-the-the-spring4shell-vulnerability-cve-2022-22965
 * https://www.elastic.co/security-labs/hunting-for-persistence-using-elastic-security-part-1
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Tactic: Initial Access
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 111
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Persistence
-* Investigation Guide
 
-*Version*: 102 (<<web-shell-detection-script-process-child-of-common-web-processes-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.15.0
 
-*Last modified ({stack} release)*: 8.6.0
+==== Investigation guide
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Triage and analysis*
 
-Security audits, maintenance, and network administrative scripts may trigger this alert when run under web processes.
 
-==== Investigation guide
 
+*Investigating Web Shell Detection: Script Process Child of Common Web Processes*
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Web Shell Detection: Script Process Child of Common Web Processes
+Adversaries may backdoor web servers with web shells to establish persistent access to systems. A web shell is a web script that is placed on an openly accessible web server to allow an adversary to use the web server as a gateway into a network. A web shell may provide a set of functions to execute or a command-line interface on the system that hosts the web server.
+
+This rule detects a web server process spawning script and command-line interface programs, potentially indicating attackers executing commands using the web shell.
 
-Adversaries may backdoor web servers with web shells to establish persistent access to systems. A web shell is a web
-script that is placed on an openly accessible web server to allow an adversary to use the web server as a gateway into a
-network. A web shell may provide a set of functions to execute or a command-line interface on the system that hosts the
-web server.
 
-This rule detects a web server process spawning script and command-line interface programs, potentially indicating
-attackers executing commands using the web shell.
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate abnormal behaviors observed by the subject process such as network connections, registry or file
-modifications, and any other spawned child processes.
+- Investigate abnormal behaviors observed by the subject process such as network connections, registry or file modifications, and any other spawned child processes.
 - Examine the command line to determine which commands or scripts were executed.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
@@ -84,12 +83,15 @@ modifications, and any other spawned child processes.
   - Use the PowerShell Get-FileHash cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
 
-- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently
-malicious must be monitored by the security team.
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -97,33 +99,48 @@ malicious must be monitored by the security team.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-("w3wp.exe", "httpd.exe", "nginx.exe", "php.exe", "php-cgi.exe",
-"tomcat.exe") and process.name : ("cmd.exe", "cscript.exe",
-"powershell.exe", "pwsh.exe", "powershell_ise.exe", "wmic.exe",
-"wscript.exe")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : ("w3wp.exe", "httpd.exe", "nginx.exe", "php.exe", "php-cgi.exe", "tomcat.exe") and
+  process.name : ("cmd.exe", "cscript.exe", "powershell.exe", "pwsh.exe", "powershell_ise.exe", "wmic.exe", "wscript.exe") and
+  not 
+  (
+    process.parent.name : ("php.exe", "httpd.exe") and process.name : "cmd.exe" and
+    process.command_line : (
+      "cmd.exe /c mode CON",
+      "cmd.exe /s /c \"mode CON\"",
+      "cmd.exe /c \"mode\"",
+      "cmd.exe /s /c \"tput colors 2>&1\""
+    )
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -135,8 +152,10 @@ process where event.type == "start" and process.parent.name :
 ** Name: Server Software Component
 ** ID: T1505
 ** Reference URL: https://attack.mitre.org/techniques/T1505/
-
-
+* Sub-technique:
+** Name: Web Shell
+** ID: T1505.003
+** Reference URL: https://attack.mitre.org/techniques/T1505/003/
 * Tactic:
 ** Name: Initial Access
 ** ID: TA0001
@@ -145,38 +164,27 @@ process where event.type == "start" and process.parent.name :
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[web-shell-detection-script-process-child-of-common-web-processes-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Rule name changed from: Webshell Detection: Script Process Child of Common Web Processes
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-("w3wp.exe", "httpd.exe", "nginx.exe", "php.exe", "php-cgi.exe",
-"tomcat.exe") and process.name : ("cmd.exe", "cscript.exe",
-"powershell.exe", "pwsh.exe", "powershell_ise.exe", "wmic.exe",
-"wscript.exe")
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-("w3wp.exe", "httpd.exe", "nginx.exe", "php.exe", "php-cgi.exe",
-"tomcat.exe") and process.name : ("cmd.exe", "cscript.exe",
-"powershell.exe", "pwsh.exe", "wmic.exe", "wscript.exe")
-----------------------------------
-
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Windows Command Shell
+** ID: T1059.003
+** Reference URL: https://attack.mitre.org/techniques/T1059/003/
+* Sub-technique:
+** Name: Visual Basic
+** ID: T1059.005
+** Reference URL: https://attack.mitre.org/techniques/T1059/005/
+* Technique:
+** Name: Windows Management Instrumentation
+** ID: T1047
+** Reference URL: https://attack.mitre.org/techniques/T1047/
diff --git a/docs/detections/prebuilt-rules/rule-details/webproxy-settings-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/webproxy-settings-modification.asciidoc
index 182ac6b832..078f834cf8 100644
--- a/docs/detections/prebuilt-rules/rule-details/webproxy-settings-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/webproxy-settings-modification.asciidoc
@@ -5,64 +5,92 @@ Identifies the use of the built-in networksetup command to configure webproxy se
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
-* auditbeat-*
 * logs-endpoint.events.*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://unit42.paloaltonetworks.com/mac-malware-steals-cryptocurrency-exchanges-cookies/
 * https://objectivebythesea.com/v2/talks/OBTS_v2_Zohar.pdf
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Data Source: Elastic Defend
+
+*Version*: 206
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* macOS
-* Threat Detection
-* Credential Access
 
-*Version*: 100 (<<webproxy-settings-modification-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 7.12.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Potential false positives
+*Setup*
+
+
+This rule requires data coming in from Elastic Defend.
+
+
+*Elastic Defend Integration Setup*
+
+Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
+
+
+*Prerequisite Requirements:*
+
+- Fleet is required for Elastic Defend.
+- To configure Fleet Server refer to the https://www.elastic.co/guide/en/fleet/current/fleet-server.html[documentation].
+
+
+*The following steps should be executed in order to add the Elastic Defend integration on a macOS System:*
+
+- Go to the Kibana home page and click "Add integrations".
+- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
+- Click "Add Elastic Defend".
+- Configure the integration name and optionally add a description.
+- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
+- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html[Helper guide].
+- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
+- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
+For more details on Elastic Agent configuration settings, refer to the https://www.elastic.co/guide/en/fleet/current/agent-policy.html[helper guide].
+- Click "Save and Continue".
+- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
+For more details on Elastic Defend refer to the https://www.elastic.co/guide/en/security/current/install-endpoint.html[helper guide].
 
-Legitimate WebProxy Settings Modification
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.category : process and event.type : start and process.name :
-networksetup and process.args : (("-setwebproxy" or
-"-setsecurewebproxy" or "-setautoproxyurl") and not (Bluetooth or
-off)) and not process.parent.executable :
-("/Library/PrivilegedHelperTools/com.80pct.FreedomHelper" or
-"/Applications/Fiddler
-Everywhere.app/Contents/Resources/app/out/WebServer/Fiddler.WebUi" or
-"/usr/libexec/xpcproxy")
+[source, js]
 ----------------------------------
+event.category:process and host.os.type:macos and event.type:start and
+ process.name : networksetup and process.args : (("-setwebproxy" or "-setsecurewebproxy" or "-setautoproxyurl") and not (Bluetooth or off)) and
+ not process.parent.executable : ("/Library/PrivilegedHelperTools/com.80pct.FreedomHelper" or
+                                  "/Applications/Fiddler Everywhere.app/Contents/Resources/app/out/WebServer/Fiddler.WebUi" or
+                                  "/usr/libexec/xpcproxy") and
+ not process.Ext.effective_parent.executable : ("/Applications/Proxyman.app/Contents/MacOS/Proxyman" or "/Applications/Incoggo.app/Contents/MacOS/Incoggo.app")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -74,23 +102,3 @@ Everywhere.app/Contents/Resources/app/out/WebServer/Fiddler.WebUi" or
 ** Name: Steal Web Session Cookie
 ** ID: T1539
 ** Reference URL: https://attack.mitre.org/techniques/T1539/
-
-[[webproxy-settings-modification-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:start and
-process.name:networksetup and process.args:("-setwebproxy" or
-"-setsecurewebproxy" or "-setautoproxyurl")
-----------------------------------
-
diff --git a/docs/detections/prebuilt-rules/rule-details/webserver-access-logs-deleted.asciidoc b/docs/detections/prebuilt-rules/rule-details/webserver-access-logs-deleted.asciidoc
index 5eaf8fb2ea..f3626a21b7 100644
--- a/docs/detections/prebuilt-rules/rule-details/webserver-access-logs-deleted.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/webserver-access-logs-deleted.asciidoc
@@ -5,66 +5,72 @@ Identifies the deletion of WebServer access logs. This may indicate an attempt t
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * auditbeat-*
 * winlogbeat-*
 * logs-endpoint.events.*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Linux
-* Windows
-* macOS
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<webserver-access-logs-deleted-history, version history>>)
+* Domain: Endpoint
+* OS: Linux
+* OS: Windows
+* OS: macOS
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 105
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type == "deletion" and file.path :
-("C:\\inetpub\\logs\\LogFiles\\*.log",
-"/var/log/apache*/access.log",
-"/etc/httpd/logs/access_log",
-"/var/log/httpd/access_log",
-"/var/www/*/logs/access.log")
+[source, js]
 ----------------------------------
+file where event.type == "deletion" and
+  file.path : ("C:\\inetpub\\logs\\LogFiles\\*.log",
+               "/var/log/apache*/access.log",
+               "/etc/httpd/logs/access_log",
+               "/var/log/httpd/access_log",
+               "/var/www/*/logs/access.log")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -73,35 +79,6 @@ file where event.type == "deletion" and file.path :
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
 * Technique:
-** Name: Indicator Removal on Host
+** Name: Indicator Removal
 ** ID: T1070
 ** Reference URL: https://attack.mitre.org/techniques/T1070/
-
-[[webserver-access-logs-deleted-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type == "deletion" and file.path :
-("C:\\inetpub\\logs\\LogFiles\\*.log",
-"/var/log/apache*/access.log",
-"/etc/httpd/logs/access_log",
-"/var/log/httpd/access_log",
-"/var/www/*/logs/access.log")
-----------------------------------
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/werfault-reflectdebugger-persistence.asciidoc b/docs/detections/prebuilt-rules/rule-details/werfault-reflectdebugger-persistence.asciidoc
new file mode 100644
index 0000000000..57ee346e68
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/werfault-reflectdebugger-persistence.asciidoc
@@ -0,0 +1,75 @@
+[[werfault-reflectdebugger-persistence]]
+=== Werfault ReflectDebugger Persistence
+
+Identifies the registration of a Werfault Debugger. Attackers may abuse this mechanism to execute malicious payloads every time the utility is executed with the "-pr" parameter.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.registry-*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://cocomelonc.github.io/malware/2022/11/02/malware-pers-18.html
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+registry where host.os.type == "windows" and event.type == "change" and
+  registry.path : (
+    "HKLM\\Software\\Microsoft\\Windows\\Windows Error Reporting\\Hangs\\ReflectDebugger",
+    "\\REGISTRY\\MACHINE\\Software\\Microsoft\\Windows\\Windows Error Reporting\\Hangs\\ReflectDebugger"
+  )
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Event Triggered Execution
+** ID: T1546
+** Reference URL: https://attack.mitre.org/techniques/T1546/
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/whoami-process-activity.asciidoc b/docs/detections/prebuilt-rules/rule-details/whoami-process-activity.asciidoc
index 7d463211ea..260415adaf 100644
--- a/docs/detections/prebuilt-rules/rule-details/whoami-process-activity.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/whoami-process-activity.asciidoc
@@ -5,10 +5,10 @@ Identifies suspicious use of whoami.exe which displays user, group, and privileg
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * logs-system.*
 * endgame-*
@@ -17,171 +17,136 @@ Identifies suspicious use of whoami.exe which displays user, group, and privileg
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<whoami-process-activity-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Some normal use of this program, at varying levels of frequency, may originate from scripts, automation tools and frameworks. Usage by non-engineers and ordinary users is unusual.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Whoami Process Activity
+*Triage and analysis*
+
+
+
+*Investigating Whoami Process Activity*
 
-After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps.
-This can happen by running commands to enumerate network resources, users, connections, files, and installed security
-software.
 
-This rule looks for the execution of the `whoami` utility. Attackers commonly use this utility to measure their current
-privileges, discover the current user, determine if a privilege escalation was successful, etc.
+After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
 
-#### Possible investigation steps
+This rule looks for the execution of the `whoami` utility. Attackers commonly use this utility to measure their current privileges, discover the current user, determine if a privilege escalation was successful, etc.
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
 
-### False positive analysis
 
-- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify
-suspicious activity related to the user or host, such alerts can be dismissed.
+*False positive analysis*
 
-### Related rules
 
-- Account Discovery Command via SYSTEM Account - 2856446a-34e6-435b-9fb5-f8f040bfa7ed
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
 
-### Response and remediation
 
-- Initiate the incident response process based on the outcome of the triage.
-- Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
-- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+*Related rules*
 
 
-==== Rule query
+- Account Discovery Command via SYSTEM Account - 2856446a-34e6-435b-9fb5-f8f040bfa7ed
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.name : "whoami.exe"
-and ( (/* scoped for whoami execution under system privileges */
-(user.domain : ("NT AUTHORITY", "NT-AUTORITÄT", "AUTORITE NT", "IIS
-APPPOOL") or user.id : ("S-1-5-18", "S-1-5-19", "S-1-5-20")) and
-not (process.parent.name : "cmd.exe" and process.parent.args :
-("chcp 437>nul 2>&1 & C:\\WINDOWS\\System32\\whoami.exe /groups",
-"chcp 437>nul 2>&1 & %systemroot%\\system32\\whoami /user",
-"C:\\WINDOWS\\System32\\whoami.exe /groups",
-"*WINDOWS\\system32\\config\\systemprofile*")) and not
-(process.parent.executable :
-"C:\\Windows\\system32\\inetsrv\\appcmd.exe" and process.parent.args :
-"LIST") and not process.parent.executable : ("C:\\Program
-Files\\Microsoft Monitoring Agent\\Agent\\MonitoringHost.exe",
-"C:\\Program Files\\Cohesity\\cohesity_windows_agent_service.exe")) or
-process.parent.name : ("wsmprovhost.exe", "w3wp.exe", "wmiprvse.exe",
-"rundll32.exe", "regsvr32.exe") )
-----------------------------------
+*Response and remediation*
 
-==== Threat mapping
 
-*Framework*: MITRE ATT&CK^TM^
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved hosts to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
-* Tactic:
-** Name: Discovery
-** ID: TA0007
-** Reference URL: https://attack.mitre.org/tactics/TA0007/
-* Technique:
-** Name: System Owner/User Discovery
-** ID: T1033
-** Reference URL: https://attack.mitre.org/techniques/T1033/
 
-[[whoami-process-activity-history]]
-==== Rule version history
+==== Setup
 
-Version 102 (8.6.0 release)::
-* Formatting only
 
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.name : "whoami.exe"
-----------------------------------
 
-Version 11 (8.4.0 release)::
-* Formatting only
+*Setup*
 
-Version 9 (8.3.0 release)::
-* Formatting only
 
-Version 8 (8.2.0 release)::
-* Formatting only
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
-Version 7 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.name:whoami.exe
-----------------------------------
 
-Version 6 (7.12.0 release)::
-* Formatting only
+==== Rule query
 
-Version 5 (7.11.2 release)::
-* Formatting only
 
-Version 4 (7.10.0 release)::
-* Updated query, changed from:
-+
 [source, js]
 ----------------------------------
-process.name:whoami.exe and event.code:1
-----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.name : "whoami.exe" and
+(
+  (
+    /* scoped for whoami execution under system privileges */
+    (
+      user.domain : ("NT *", "* NT", "IIS APPPOOL") and
+      user.id : ("S-1-5-18", "S-1-5-19", "S-1-5-20", "S-1-5-82-*") and
+      not ?winlog.event_data.SubjectUserName : "*$"
+    ) and
+    not (
+      process.parent.name : "cmd.exe" and
+      process.parent.args : (
+          "chcp 437>nul 2>&1 & C:\\WINDOWS\\System32\\whoami.exe  /groups",
+          "chcp 437>nul 2>&1 & %systemroot%\\system32\\whoami /user",
+          "C:\\WINDOWS\\System32\\whoami.exe /groups",
+          "*WINDOWS\\system32\\config\\systemprofile*"
+      )
+    ) and
+    not (process.parent.executable : "C:\\Windows\\system32\\inetsrv\\appcmd.exe" and process.parent.args : "LIST") and
+    not process.parent.executable : (
+        "C:\\Program Files\\Microsoft Monitoring Agent\\Agent\\MonitoringHost.exe",
+        "C:\\Program Files\\Cohesity\\cohesity_windows_agent_service.exe"
+    )
+  ) or
+  process.parent.name : ("wsmprovhost.exe", "w3wp.exe", "wmiprvse.exe", "rundll32.exe", "regsvr32.exe")
+)
 
-Version 3 (7.9.0 release)::
-* Formatting only
+----------------------------------
 
-Version 2 (7.7.0 release)::
-* Formatting only
+*Framework*: MITRE ATT&CK^TM^
 
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Owner/User Discovery
+** ID: T1033
+** Reference URL: https://attack.mitre.org/techniques/T1033/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-account-or-group-discovery.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-account-or-group-discovery.asciidoc
new file mode 100644
index 0000000000..04b37e51c1
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/windows-account-or-group-discovery.asciidoc
@@ -0,0 +1,110 @@
+[[windows-account-or-group-discovery]]
+=== Windows Account or Group Discovery
+
+This rule identifies the execution of commands that enumerates account or group information. Adversaries may use built-in applications to get a listing of local system or domain accounts and groups.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+(
+  (
+   (
+    (process.name : "net.exe" or process.pe.original_file_name == "net.exe") or
+    (
+     (process.name : "net1.exe" or process.pe.original_file_name == "net1.exe") and
+     not process.parent.name : "net.exe"
+    )
+   ) and process.args : ("accounts", "group", "user", "localgroup") and not process.args : "/add"
+  ) or
+  (process.name:("dsquery.exe", "dsget.exe") and process.args:("*members*", "user")) or
+  (process.name:"dsquery.exe" and process.args:"*filter*") or
+  process.name:("quser.exe", "qwinsta.exe", "PsGetSID.exe", "PsLoggedOn.exe", "LogonSessions.exe", "whoami.exe") or
+  (
+    process.name: "cmd.exe" and
+    (
+      process.args : "echo" and process.args : (
+        "%username%", "%userdomain%", "%userdnsdomain%",
+        "%userdomain_roamingprofile%", "%userprofile%",
+        "%homepath%", "%localappdata%", "%appdata%"
+      ) or
+      process.args : "set"
+    )
+  )
+) and not process.parent.args: "C:\\Program Files (x86)\\Microsoft Intune Management Extension\\Content\\DetectionScripts\\*.ps1"
+and not process.parent.name : "LTSVC.exe" and not user.id : "S-1-5-18"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: Permission Groups Discovery
+** ID: T1069
+** Reference URL: https://attack.mitre.org/techniques/T1069/
+* Sub-technique:
+** Name: Local Groups
+** ID: T1069.001
+** Reference URL: https://attack.mitre.org/techniques/T1069/001/
+* Sub-technique:
+** Name: Domain Groups
+** ID: T1069.002
+** Reference URL: https://attack.mitre.org/techniques/T1069/002/
+* Technique:
+** Name: Password Policy Discovery
+** ID: T1201
+** Reference URL: https://attack.mitre.org/techniques/T1201/
+* Technique:
+** Name: Account Discovery
+** ID: T1087
+** Reference URL: https://attack.mitre.org/techniques/T1087/
+* Sub-technique:
+** Name: Local Account
+** ID: T1087.001
+** Reference URL: https://attack.mitre.org/techniques/T1087/001/
+* Sub-technique:
+** Name: Domain Account
+** ID: T1087.002
+** Reference URL: https://attack.mitre.org/techniques/T1087/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-cryptoapi-spoofing-vulnerability-cve-2020-0601-curveball.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-cryptoapi-spoofing-vulnerability-cve-2020-0601-curveball.asciidoc
index 8f9f0cc686..5e1c50c596 100644
--- a/docs/detections/prebuilt-rules/rule-details/windows-cryptoapi-spoofing-vulnerability-cve-2020-0601-curveball.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/windows-cryptoapi-spoofing-vulnerability-cve-2020-0601-curveball.asciidoc
@@ -5,49 +5,49 @@ A spoofing vulnerability exists in the way Windows CryptoAPI (Crypt32.dll) valid
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-windows.*
+* logs-system.security*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
+*Tags*: 
 
-*Version*: 100 (<<windows-cryptoapi-spoofing-vulnerability-cve-2020-0601-curveball-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Use Case: Vulnerability
 
-*Added ({stack} release)*: 7.7.0
+*Version*: 104
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.provider:"Microsoft-Windows-Audit-CVE" and
-message:"[CVE-2020-0601]"
+[source, js]
 ----------------------------------
+event.provider:"Microsoft-Windows-Audit-CVE" and message:"[CVE-2020-0601]" and host.os.type:windows
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -59,28 +59,7 @@ message:"[CVE-2020-0601]"
 ** Name: Subvert Trust Controls
 ** ID: T1553
 ** Reference URL: https://attack.mitre.org/techniques/T1553/
-
-[[windows-cryptoapi-spoofing-vulnerability-cve-2020-0601-curveball-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 6 (7.12.0 release)::
-* Formatting only
-
-Version 5 (7.11.2 release)::
-* Formatting only
-
-Version 4 (7.11.0 release)::
-* Formatting only
-
-Version 3 (7.10.0 release)::
-* Formatting only
-
-Version 2 (7.9.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Code Signing
+** ID: T1553.002
+** Reference URL: https://attack.mitre.org/techniques/T1553/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-defender-disabled-via-registry-modification.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-defender-disabled-via-registry-modification.asciidoc
index c02a74f48d..708a69a255 100644
--- a/docs/detections/prebuilt-rules/rule-details/windows-defender-disabled-via-registry-modification.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/windows-defender-disabled-via-registry-modification.asciidoc
@@ -5,121 +5,146 @@ Identifies modifications to the Windows Defender registry settings to disable th
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.registry-*
 * endgame-*
+* logs-windows.sysmon_operational-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://thedfirreport.com/2020/12/13/defender-control/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<windows-defender-disabled-via-registry-modification-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Windows Defender Disabled via Registry Modification
+*Triage and analysis*
+
 
-Microsoft Windows Defender is an antivirus product built into Microsoft Windows, which makes it popular across multiple
-environments. Disabling it is a common step in threat actor playbooks.
+
+*Investigating Windows Defender Disabled via Registry Modification*
+
+
+Microsoft Windows Defender is an antivirus product built into Microsoft Windows, which makes it popular across multiple environments. Disabling it is a common step in threat actor playbooks.
 
 This rule monitors the registry for configurations that disable Windows Defender or the start of its service.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
-- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate
-software installations.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Check if this operation was approved and performed according to the organization's change management policy.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity,
-the configuration is justified (for example, it is being used to deploy other security solutions or troubleshooting),
-and no other suspicious activity has been observed.
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Analysts can dismiss the alert if the administrator is aware of the activity, the configuration is justified (for example, it is being used to deploy other security solutions or troubleshooting), and no other suspicious activity has been observed.
+
+
+*Related rules*
 
-### Related rules
 
 - Disabling Windows Defender Security Settings via PowerShell - c8cccb06-faf2-4cd5-886e-2c9636cfcb87
 - Microsoft Windows Defender Tampering - fe794edd-487f-4a90-b285-3ee54f2af2d3
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Re-enable Windows Defender and restore the service configurations to automatic start.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Review the privileges assigned to the user to ensure that the least privilege principle is being followed.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-registry where event.type in ("creation", "change") and ( (
-registry.path: ( "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\DisableAntiSpyware",
-"\\REGISTRY\\MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\DisableAntiSpyware" ) and registry.data.strings:
-("1", "0x00000001") ) or ( registry.path: (
-"HKLM\\System\\*ControlSet*\\Services\\WinDefend\\Start", "\\R
-EGISTRY\\MACHINE\\System\\*ControlSet*\\Services\\WinDefend\\Start"
-) and registry.data.strings in ("3", "4", "0x00000003",
-"0x00000004") ) ) and not process.executable :
-("?:\\WINDOWS\\system32\\services.exe",
-"?:\\Windows\\System32\\svchost.exe", "?:\\Program Files
-(x86)\\Trend Micro\\Security Agent\\NTRmv.exe")
+[source, js]
 ----------------------------------
+registry where host.os.type == "windows" and event.type in ("creation", "change") and
+  (
+    (
+      registry.path: (
+        "HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\DisableAntiSpyware",
+        "\\REGISTRY\\MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\DisableAntiSpyware"
+      ) and
+      registry.data.strings: ("1", "0x00000001")
+   ) or
+   (
+      registry.path: (
+        "HKLM\\System\\*ControlSet*\\Services\\WinDefend\\Start",
+        "\\REGISTRY\\MACHINE\\System\\*ControlSet*\\Services\\WinDefend\\Start"
+      ) and
+      registry.data.strings in ("3", "4", "0x00000003", "0x00000004")
+   )
+  ) and
+
+  not
+    (
+      process.executable : (
+          "?:\\WINDOWS\\system32\\services.exe",
+          "?:\\Windows\\System32\\svchost.exe",
+          "?:\\Program Files (x86)\\Trend Micro\\Security Agent\\NTRmv.exe"
+      ) and user.id : "S-1-5-18"
+    )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -131,65 +156,15 @@ EGISTRY\\MACHINE\\System\\*ControlSet*\\Services\\WinDefend\\Start"
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[windows-defender-disabled-via-registry-modification-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type in ("creation", "change") and ( (
-registry.path:"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\DisableAntiSpyware" and registry.data.strings: ("1",
-"0x00000001") ) or (
-registry.path:"HKLM\\System\\*ControlSet*\\Services\\WinDefend\\Start"
-and registry.data.strings in ("3", "4", "0x00000003",
-"0x00000004") ) ) and not process.executable :
-("?:\\WINDOWS\\system32\\services.exe",
-"?:\\Windows\\System32\\svchost.exe", "?:\\Program Files
-(x86)\\Trend Micro\\Security Agent\\NTRmv.exe")
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type in ("creation", "change") and ( (
-registry.path:"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\DisableAntiSpyware" and registry.data.strings: ("1",
-"0x00000001") ) or (
-registry.path:"HKLM\\System\\*ControlSet*\\Services\\WinDefend\\Start"
-and registry.data.strings in ("3", "4", "0x00000003",
-"0x00000004") ) )
-----------------------------------
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (8.1.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-registry where event.type in ("creation", "change") and
-((registry.path:"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
-Defender\\DisableAntiSpyware" and registry.data.strings:"1") or
-(registry.path:"HKLM\\System\\ControlSet*\\Services\\WinDefend\\Start"
-and registry.data.strings in ("3", "4")))
-----------------------------------
-
-Version 3 (7.15.0 release)::
-* Formatting only
-
-Version 2 (7.13.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
+* Sub-technique:
+** Name: Indicator Blocking
+** ID: T1562.006
+** Reference URL: https://attack.mitre.org/techniques/T1562/006/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-defender-exclusions-added-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-defender-exclusions-added-via-powershell.asciidoc
index b68ce41225..37c95a42e4 100644
--- a/docs/detections/prebuilt-rules/rule-details/windows-defender-exclusions-added-via-powershell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/windows-defender-exclusions-added-via-powershell.asciidoc
@@ -5,66 +5,65 @@ Identifies modifications to the Windows Defender configuration settings using Po
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.bitdefender.com/files/News/CaseStudies/study/400/Bitdefender-PR-Whitepaper-MosaicLoader-creat5540-en-EN.pdf
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
-
-*Version*: 102 (<<windows-defender-exclusions-added-via-powershell-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 7.14.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Windows Defender Exclusions Added via PowerShell
+*Triage and analysis*
+
 
-Microsoft Windows Defender is an antivirus product built into Microsoft Windows. Since this software product is
-used to prevent and stop malware, it's important to monitor what specific exclusions are made to the product's configuration
-settings. These can often be signs of an adversary or malware trying to bypass Windows Defender's capabilities. One of
-the more notable [examples](https://www.cyberbit.com/blog/endpoint-security/latest-trickbot-variant-has-new-tricks-up-its-sleeve/)
-was observed in 2018 where Trickbot incorporated mechanisms to disable Windows Defender to avoid detection.
 
-#### Possible investigation steps
+*Investigating Windows Defender Exclusions Added via PowerShell*
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+
+Microsoft Windows Defender is an antivirus product built into Microsoft Windows. Since this software product is used to prevent and stop malware, it's important to monitor what specific exclusions are made to the product's configuration settings. These can often be signs of an adversary or malware trying to bypass Windows Defender's capabilities. One of the more notable https://www.cyberbit.com/blog/endpoint-security/latest-trickbot-variant-has-new-tricks-up-its-sleeve/[examples] was observed in 2018 where Trickbot incorporated mechanisms to disable Windows Defender to avoid detection.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Examine the exclusion in order to determine the intent behind it.
@@ -79,18 +78,22 @@ for prevalence, whether they are located in expected locations, and if they are
   - Use the PowerShell Get-FileHash cmdlet to get the files' SHA-256 hash values.
     - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 
-### False positive analysis
 
-- This rule has a high chance to produce false positives due to how often network administrators legitimately configure
-exclusions. In order to validate the activity further, review the specific exclusion and its intent. There are many
-legitimate reasons for exclusions, so it's important to gain context.
+*False positive analysis*
+
+
+- This rule has a high chance to produce false positives due to how often network administrators legitimately configure exclusions. In order to validate the activity further, review the specific exclusion and its intent. There are many legitimate reasons for exclusions, so it's important to gain context.
+
+
+*Related rules*
 
-### Related rules
 
 - Windows Defender Disabled via Registry Modification - 2ffa1f1e-b6db-47fa-994b-1512743847eb
 - Disabling Windows Defender Security Settings via PowerShell - c8cccb06-faf2-4cd5-886e-2c9636cfcb87
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -98,31 +101,39 @@ legitimate reasons for exclusions, so it's important to gain context.
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Exclusion lists for antimalware capabilities should always be routinely monitored for review.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name :
-("powershell.exe", "pwsh.exe", "powershell_ise.exe") or
-process.pe.original_file_name in ("powershell.exe", "pwsh.dll",
-"powershell_ise.exe")) and process.args : ("*Add-MpPreference*",
-"*Set-MpPreference*") and process.args : ("*-Exclusion*")
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ (process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe") or ?process.pe.original_file_name in ("powershell.exe", "pwsh.dll", "powershell_ise.exe")) and
+  process.args : ("*Add-MpPreference*", "*Set-MpPreference*") and
+  process.args : ("*-Exclusion*")
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -134,8 +145,14 @@ process.pe.original_file_name in ("powershell.exe", "pwsh.dll",
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-
+* Sub-technique:
+** Name: Disable or Modify Tools
+** ID: T1562.001
+** Reference URL: https://attack.mitre.org/techniques/T1562/001/
+* Sub-technique:
+** Name: Indicator Blocking
+** ID: T1562.006
+** Reference URL: https://attack.mitre.org/techniques/T1562/006/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -144,51 +161,7 @@ process.pe.original_file_name in ("powershell.exe", "pwsh.dll",
 ** Name: Command and Scripting Interpreter
 ** ID: T1059
 ** Reference URL: https://attack.mitre.org/techniques/T1059/
-
-[[windows-defender-exclusions-added-via-powershell-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 10 (8.4.0 release)::
-* Formatting only
-
-Version 8 (8.3.0 release)::
-* Formatting only
-
-Version 7 (8.2.0 release)::
-* Formatting only
-
-Version 6 (8.1.0 release)::
-* Formatting only
-
-Version 5 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and (process.name :
-("powershell.exe", "pwsh.exe", "powershell_ise.exe") or
-process.pe.original_file_name in ("powershell.exe", "pwsh.dll",
-"powershell_ise.exe")) and process.args : ("*Add-
-MpPreference*-Exclusion*", "*Set-MpPreference*-Exclusion*")
-----------------------------------
-
-Version 4 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type == "start" and (process.name :
-("powershell.exe", "pwsh.exe") or process.pe.original_file_name :
-("powershell.exe", "pwsh.exe")) and process.args : ("*Add-
-MpPreference*-Exclusion*", "*Set-MpPreference*-Exclusion*")
-----------------------------------
-
-Version 2 (7.15.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-event-logs-cleared.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-event-logs-cleared.asciidoc
index 6c10e26580..0b1ac1e466 100644
--- a/docs/detections/prebuilt-rules/rule-details/windows-event-logs-cleared.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/windows-event-logs-cleared.asciidoc
@@ -5,95 +5,96 @@ Identifies attempts to clear Windows event log stores. This is often done by att
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<windows-event-logs-cleared-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Resources: Investigation Guide
 
-*Added ({stack} release)*: 7.12.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic, Anabella Cristaldi
+* Elastic
+* Anabella Cristaldi
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Windows Event Logs Cleared
+*Triage and analysis*
+
+
+
+*Investigating Windows Event Logs Cleared*
 
-Windows event logs are a fundamental data source for security monitoring, forensics, and incident response. Adversaries
-can tamper, clear, and delete this data to break SIEM detections, cover their tracks, and slow down incident response.
+
+Windows event logs are a fundamental data source for security monitoring, forensics, and incident response. Adversaries can tamper, clear, and delete this data to break SIEM detections, cover their tracks, and slow down incident response.
 
 This rule looks for the occurrence of clear actions on the `security` event log.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
   - Verify if any other anti-forensics behaviors were observed.
 - Investigate the event logs prior to the action for suspicious behaviors that an attacker may be trying to cover up.
 
-### False positive analysis
+
+*False positive analysis*
+
 
 - This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
-  - This activity is potentially done after the adversary achieves its objectives on the host. Ensure that previous
-  actions, if any, are investigated accordingly with their response playbooks.
+  - This activity is potentially done after the adversary achieves its objectives on the host. Ensure that previous actions, if any, are investigated accordingly with their response playbooks.
 - Isolate the involved host to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.action:("audit-log-cleared" or "Log clear")
+[source, js]
 ----------------------------------
+event.action:("audit-log-cleared" or "Log clear") and winlog.api:"wineventlog" and
+  not winlog.provider_name:"AD FS Auditing"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -102,28 +103,10 @@ event.action:("audit-log-cleared" or "Log clear")
 ** ID: TA0005
 ** Reference URL: https://attack.mitre.org/tactics/TA0005/
 * Technique:
-** Name: Indicator Removal on Host
+** Name: Indicator Removal
 ** ID: T1070
 ** Reference URL: https://attack.mitre.org/techniques/T1070/
-
-[[windows-event-logs-cleared-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.3.0 release)::
-* Formatting only
-
-Version 3 (8.2.0 release)::
-* Formatting only
-
-Version 2 (7.16.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Clear Windows Event Logs
+** ID: T1070.001
+** Reference URL: https://attack.mitre.org/techniques/T1070/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-firewall-disabled-via-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-firewall-disabled-via-powershell.asciidoc
index cbbf52e3f4..5bd3dd5dd8 100644
--- a/docs/detections/prebuilt-rules/rule-details/windows-firewall-disabled-via-powershell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/windows-firewall-disabled-via-powershell.asciidoc
@@ -5,9 +5,9 @@ Identifies when the Windows Firewall is disabled using PowerShell cmdlets, which
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
@@ -16,104 +16,112 @@ Identifies when the Windows Firewall is disabled using PowerShell cmdlets, which
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://docs.microsoft.com/en-us/powershell/module/netsecurity/set-netfirewallprofile?view=windowsserver2019-ps
 * https://www.tutorialspoint.com/how-to-get-windows-firewall-profile-settings-using-powershell
 * http://powershellhelp.space/commands/set-netfirewallrule-psv5.php
 * http://woshub.com/manage-windows-firewall-powershell/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Defense Evasion
-* Investigation Guide
-* Elastic Endgame
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
 
-*Version*: 102 (<<windows-firewall-disabled-via-powershell-history, version history>>)
+*Version*: 110
 
-*Added ({stack} release)*: 8.0.0
+*Rule authors*: 
 
-*Last modified ({stack} release)*: 8.6.0
-
-*Rule authors*: Austin Songer
+* Austin Songer
 
 *Rule license*: Elastic License v2
 
-==== Potential false positives
-
-Windows Firewall can be disabled by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Windows Profile being disabled by unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
 
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Windows Firewall Disabled via PowerShell
+*Triage and analysis*
+
+
 
-Windows Defender Firewall is a native component that provides host-based, two-way network traffic filtering for a
-device and blocks unauthorized network traffic flowing into or out of the local device.
+*Investigating Windows Firewall Disabled via PowerShell*
+
+
+Windows Defender Firewall is a native component that provides host-based, two-way network traffic filtering for a device and blocks unauthorized network traffic flowing into or out of the local device.
 
 Attackers can disable the Windows firewall or its rules to enable lateral movement and command and control activity.
 
-This rule identifies patterns related to disabling the Windows firewall or its rules using the `Set-NetFirewallProfile`
-PowerShell cmdlet.
+This rule identifies patterns related to disabling the Windows firewall or its rules using the `Set-NetFirewallProfile` PowerShell cmdlet.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Contact the account owner and confirm whether they are aware of this activity.
 - Investigate other alerts associated with the user/host during the past 48 hours.
 - Inspect the host for suspicious or abnormal behavior in the alert timeframe.
 
-### False positive analysis
 
-- This mechanism can be used legitimately. Check whether the user is an administrator and is legitimately performing
-troubleshooting.
+*False positive analysis*
+
+
+- This mechanism can be used legitimately. Check whether the user is an administrator and is legitimately performing troubleshooting.
 - In case of an allowed benign true positive (B-TP), assess adding rules to allow needed traffic and re-enable the firewall.
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
 - Re-enable the firewall with its desired configurations.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.action == "start" and (process.name :
-("powershell.exe", "pwsh.exe", "powershell_ise.exe") or
-process.pe.original_file_name == "PowerShell.EXE") and process.args
-: "*Set-NetFirewallProfile*" and (process.args : "*-Enabled*" and
-process.args : "*False*") and (process.args : "*-All*" or
-process.args : ("*Public*", "*Domain*", "*Private*"))
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.action == "start" and
+  (process.name : ("powershell.exe", "pwsh.exe", "powershell_ise.exe") or ?process.pe.original_file_name == "PowerShell.EXE") and
+   process.args : "*Set-NetFirewallProfile*" and
+  (process.args : "*-Enabled*" and process.args : "*False*") and
+  (process.args : "*-All*" or process.args : ("*Public*", "*Domain*", "*Private*"))
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -125,25 +133,19 @@ process.args : ("*Public*", "*Domain*", "*Private*"))
 ** Name: Impair Defenses
 ** ID: T1562
 ** Reference URL: https://attack.mitre.org/techniques/T1562/
-
-[[windows-firewall-disabled-via-powershell-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 7 (8.4.0 release)::
-* Formatting only
-
-Version 5 (8.3.0 release)::
-* Formatting only
-
-Version 4 (8.2.0 release)::
-* Formatting only
-
-Version 3 (8.1.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Disable or Modify System Firewall
+** ID: T1562.004
+** Reference URL: https://attack.mitre.org/techniques/T1562/004/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-installer-with-suspicious-properties.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-installer-with-suspicious-properties.asciidoc
new file mode 100644
index 0000000000..191f50c871
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/windows-installer-with-suspicious-properties.asciidoc
@@ -0,0 +1,79 @@
+[[windows-installer-with-suspicious-properties]]
+=== Windows Installer with Suspicious Properties
+
+Identifies the execution of an installer from an archive or with suspicious properties. Adversaries may abuse msiexec.exe to launch local or network accessible MSI files in an attempt to bypass application whitelisting.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://lolbas-project.github.io/lolbas/Binaries/Msiexec/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+sequence with maxspan=1m
+  [registry where host.os.type == "windows" and process.name : "msiexec.exe" and
+   (
+    (registry.value : "InstallSource" and
+     registry.data.strings : ("?:\\Users\\*\\Temp\\Temp?_*.zip\\*",
+                             "?:\\Users\\*\\*.7z\\*",
+                             "?:\\Users\\*\\*.rar\\*")) or
+
+    (registry.value : ("DisplayName", "ProductName") and registry.data.strings : "SetupTest")
+    )]
+  [process where host.os.type == "windows" and event.action == "start" and
+    process.parent.name : "msiexec.exe" and
+    not process.name : "msiexec.exe" and
+    not (process.executable : ("?:\\Program Files (x86)\\*.exe", "?:\\Program Files\\*.exe") and process.code_signature.trusted == true)]
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: System Binary Proxy Execution
+** ID: T1218
+** Reference URL: https://attack.mitre.org/techniques/T1218/
+* Sub-technique:
+** Name: Msiexec
+** ID: T1218.007
+** Reference URL: https://attack.mitre.org/techniques/T1218/007/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-network-enumeration.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-network-enumeration.asciidoc
index d1891d913f..0943357571 100644
--- a/docs/detections/prebuilt-rules/rule-details/windows-network-enumeration.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/windows-network-enumeration.asciidoc
@@ -5,9 +5,9 @@ Identifies attempts to enumerate hosts in a network using the built-in Windows n
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * winlogbeat-*
 * logs-windows.*
 * endgame-*
@@ -16,97 +16,113 @@ Identifies attempts to enumerate hosts in a network using the built-in Windows n
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Discovery
-* Investigation Guide
-* Elastic Endgame
+*Tags*: 
 
-*Version*: 102 (<<windows-network-enumeration-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Tactic: Collection
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Rule Type: BBR
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Windows Network Enumeration
+*Triage and analysis*
+
+
 
-After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps.
-This can happen by running commands to enumerate network resources, users, connections, files, and installed security
-software.
+*Investigating Windows Network Enumeration*
 
-This rule looks for the execution of the `net` utility to enumerate servers in the environment that hosts shared drives
-or printers. This information is useful to attackers as they can identify targets for lateral movements and search for
-valuable shared data.
 
-#### Possible investigation steps
+After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps. This can happen by running commands to enumerate network resources, users, connections, files, and installed security software.
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+This rule looks for the execution of the `net` utility to enumerate servers in the environment that hosts shared drives or printers. This information is useful to attackers as they can identify targets for lateral movements and search for valuable shared data.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Identify the user account that performed the action and whether it should perform this kind of action.
 - Investigate other alerts associated with the user/host during the past 48 hours.
-- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network
-connections.
+- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
+
 
-### False positive analysis
+*False positive analysis*
 
-- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify
-suspicious activity related to the user or host, such alerts can be dismissed.
 
-### Response and remediation
+- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
+
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and ((process.name : "net.exe"
-or process.pe.original_file_name == "net.exe") or ((process.name :
-"net1.exe" or process.pe.original_file_name == "net1.exe") and
-not process.parent.name : "net.exe")) and (process.args : "view" or
-(process.args : "time" and process.args : "\\\\*")) /* expand when
-ancestry is available and not descendant of [process where
-event.type == "start" and process.name : "cmd.exe" and
-((process.parent.name : "userinit.exe") or
-(process.parent.name : "gpscript.exe") or
-(process.parent.name : "explorer.exe" and
-process.args : "C:\\*\\Start Menu\\Programs\\Startup\\*.bat*"))] */
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  ((process.name : "net.exe" or process.pe.original_file_name == "net.exe") or
+   ((process.name : "net1.exe" or process.pe.original_file_name == "net1.exe") and
+       not process.parent.name : "net.exe")) and
+  (process.args : "view" or (process.args : "time" and process.args : "\\\\*")) and
+  not process.command_line : "net  view \\\\localhost "
+
+
+  /* expand when ancestry is available
+  and not descendant of [process where event.type == "start" and process.name : "cmd.exe" and
+                           ((process.parent.name : "userinit.exe") or
+                            (process.parent.name : "gpscript.exe") or
+                            (process.parent.name : "explorer.exe" and
+                               process.args : "C:\\*\\Start Menu\\Programs\\Startup\\*.bat*"))]
+  */
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -118,65 +134,15 @@ process.args : "C:\\*\\Start Menu\\Programs\\Startup\\*.bat*"))] */
 ** Name: Remote System Discovery
 ** ID: T1018
 ** Reference URL: https://attack.mitre.org/techniques/T1018/
-
-[[windows-network-enumeration-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-((process.name : "net.exe" or process.pe.original_file_name ==
-"net.exe") or ((process.name : "net1.exe" or
-process.pe.original_file_name == "net1.exe") and not
-process.parent.name : "net.exe")) and (process.args : "view" or
-(process.args : "time" and process.args : "\\\\*")) /* expand when
-ancestry is available and not descendant of [process where
-event.type == ("start", "process_started") and process.name :
-"cmd.exe" and ((process.parent.name :
-"userinit.exe") or (process.parent.name :
-"gpscript.exe") or (process.parent.name :
-"explorer.exe" and process.args :
-"C:\\*\\Start Menu\\Programs\\Startup\\*.bat*"))] */
-----------------------------------
-
-Version 8 (8.4.0 release)::
-* Formatting only
-
-Version 6 (8.3.0 release)::
-* Formatting only
-
-Version 5 (8.2.0 release)::
-* Formatting only
-
-Version 4 (7.15.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-((process.name : "net.exe" or process.pe.original_file_name ==
-"net.exe") or ((process.name : "net1.exe" or
-process.pe.original_file_name == "net1.exe") and not
-process.parent.name : "net.exe")) and (process.args : "view" or
-(process.args : "time" and process.args : "\\\\*")) /* expand when
-ancestory is available and not descendant of [process where
-event.type == ("start", "process_started") and process.name :
-"cmd.exe" and ((process.parent.name :
-"userinit.exe") or (process.parent.name :
-"gpscript.exe") or (process.parent.name :
-"explorer.exe" and process.args :
-"C:\\*\\Start Menu\\Programs\\Startup\\*.bat*"))] */
-----------------------------------
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
+* Technique:
+** Name: Network Share Discovery
+** ID: T1135
+** Reference URL: https://attack.mitre.org/techniques/T1135/
+* Tactic:
+** Name: Collection
+** ID: TA0009
+** Reference URL: https://attack.mitre.org/tactics/TA0009/
+* Technique:
+** Name: Data from Network Shared Drive
+** ID: T1039
+** Reference URL: https://attack.mitre.org/techniques/T1039/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-registry-file-creation-in-smb-share.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-registry-file-creation-in-smb-share.asciidoc
index b6b7b42fde..2126f03f09 100644
--- a/docs/detections/prebuilt-rules/rule-details/windows-registry-file-creation-in-smb-share.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/windows-registry-file-creation-in-smb-share.asciidoc
@@ -5,63 +5,61 @@ Identifies the creation or modification of a medium-size registry hive file on a
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.file-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.elastic.co/security-labs/detect-credential-access
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
-* Credential Access
-* Investigation Guide
-
-*Version*: 102 (<<windows-registry-file-creation-in-smb-share-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Tactic: Credential Access
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Added ({stack} release)*: 8.2.0
+*Version*: 108
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Windows Registry File Creation in SMB Share
+*Triage and analysis*
+
+
+
+*Investigating Windows Registry File Creation in SMB Share*
+
 
-Dumping registry hives is a common way to access credential information. Some hives store credential material, as is the
-case for the SAM hive, which stores locally cached credentials (SAM secrets), and the SECURITY hive, which stores domain
-cached credentials (LSA secrets). Dumping these hives in combination with the SYSTEM hive enables the attacker to
-decrypt these secrets.
+Dumping registry hives is a common way to access credential information. Some hives store credential material, as is the case for the SAM hive, which stores locally cached credentials (SAM secrets), and the SECURITY hive, which stores domain cached credentials (LSA secrets). Dumping these hives in combination with the SYSTEM hive enables the attacker to decrypt these secrets.
 
-Attackers can try to evade detection on the host by transferring this data to a system that is not
-monitored to be parsed and decrypted. This rule identifies the creation or modification of a medium-size registry hive
-file on an SMB share, which may indicate this kind of exfiltration attempt.
+Attackers can try to evade detection on the host by transferring this data to a system that is not monitored to be parsed and decrypted. This rule identifies the creation or modification of a medium-size registry hive file on an SMB share, which may indicate this kind of exfiltration attempt.
+
+
+*Possible investigation steps*
 
-#### Possible investigation steps
 
 - Investigate other alerts associated with the user/source host during the past 48 hours.
 - Identify the user account that performed the action and whether it should perform this kind of action.
@@ -69,43 +67,48 @@ file on an SMB share, which may indicate this kind of exfiltration attempt.
 - Inspect the source host for suspicious or abnormal behaviors in the alert timeframe.
 - Capture the registry file(s) to determine the extent of the credential compromise in an eventual incident response.
 
-### False positive analysis
 
-- Administrators can export registry hives for backup purposes. Check whether the user should be performing this kind of
-activity and is aware of it.
+*False positive analysis*
+
+
+- Administrators can export registry hives for backup purposes. Check whether the user should be performing this kind of activity and is aware of it.
+
+
+*Related rules*
 
-### Related rules
 
 - Credential Acquisition via Registry Hive Dumping - a7e7bfa3-088e-4f13-b29e-3986e0e756b8
 
-### Response and remediation
+
+*Response and remediation*
+
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved hosts to prevent further post-compromise behavior.
-- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are
-identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business
-systems, and web services.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 - Reimage the host operating system and restore compromised files to clean versions.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-file where event.type == "creation" and /* regf file header */
-file.Ext.header_bytes : "72656766*" and file.size >= 30000 and
-process.pid == 4 and user.id : ("S-1-5-21*", "S-1-12-1-*")
+[source, js]
 ----------------------------------
+file where host.os.type == "windows" and event.type == "creation" and
+ /* regf file header */
+ file.Ext.header_bytes : "72656766*" and file.size >= 30000 and
+ process.pid == 4 and user.id : ("S-1-5-21*", "S-1-12-1-*") and
+ not file.path : (
+    "?:\\*\\UPM_Profile\\NTUSER.DAT",
+    "?:\\*\\UPM_Profile\\NTUSER.DAT.LASTGOOD.LOAD",
+    "?:\\Windows\\Netwrix\\Temp\\????????.???.offreg",
+    "?:\\*\\AppData\\Local\\Packages\\Microsoft.*\\Settings\\settings.dat*"
+ )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -117,8 +120,10 @@ process.pid == 4 and user.id : ("S-1-5-21*", "S-1-12-1-*")
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-
+* Sub-technique:
+** Name: Security Account Manager
+** ID: T1003.002
+** Reference URL: https://attack.mitre.org/techniques/T1003/002/
 * Tactic:
 ** Name: Lateral Movement
 ** ID: TA0008
@@ -127,26 +132,7 @@ process.pid == 4 and user.id : ("S-1-5-21*", "S-1-12-1-*")
 ** Name: Remote Services
 ** ID: T1021
 ** Reference URL: https://attack.mitre.org/techniques/T1021/
-
-[[windows-registry-file-creation-in-smb-share-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-file where event.type == "creation" and /* regf file header */
-file.Ext.header_bytes : "72656766*" and file.size >= 30000 and
-process.pid == 4 and user.id : "s-1-5-21*"
-----------------------------------
-
-Version 101 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
-Version 2 (8.3.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: SMB/Windows Admin Shares
+** ID: T1021.002
+** Reference URL: https://attack.mitre.org/techniques/T1021/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-script-executing-powershell.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-script-executing-powershell.asciidoc
index d5caa48095..7714343a61 100644
--- a/docs/detections/prebuilt-rules/rule-details/windows-script-executing-powershell.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/windows-script-executing-powershell.asciidoc
@@ -5,62 +5,68 @@ Identifies a PowerShell process launched by either cscript.exe or wscript.exe. O
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: low
 
 *Risk score*: 21
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Initial Access
-* Investigation Guide
+*Tags*: 
 
-*Version*: 102 (<<windows-script-executing-powershell-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Execution
+* Resources: Investigation Guide
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.6.0
+*Version*: 111
 
-*Last modified ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
-## Triage and analysis
 
-### Investigating Windows Script Executing PowerShell
+*Triage and analysis*
+
+
+
+*Investigating Windows Script Executing PowerShell*
 
-The Windows Script Host (WSH) is an Windows automation technology, which is ideal for non-interactive scripting needs,
-such as logon scripting, administrative scripting, and machine automation.
 
-Attackers commonly use WSH scripts as their initial access method, acting like droppers for second stage payloads, but
-can also use them to download tools and utilities needed to accomplish their goals.
+The Windows Script Host (WSH) is an Windows automation technology, which is ideal for non-interactive scripting needs, such as logon scripting, administrative scripting, and machine automation.
+
+Attackers commonly use WSH scripts as their initial access method, acting like droppers for second stage payloads, but can also use them to download tools and utilities needed to accomplish their goals.
 
 This rule looks for the spawn of the `powershell.exe` process with `cscript.exe` or `wscript.exe` as its parent process.
 
-#### Possible investigation steps
 
-- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files
-for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 - Investigate commands executed by the spawned PowerShell process.
 - If unsigned files are found on the process tree, retrieve them and determine if they are malicious:
   - Use a private sandboxed malware analysis system to perform analysis.
@@ -74,12 +80,15 @@ for prevalence, whether they are located in expected locations, and if they are
 - Determine how the script file was delivered (email attachment, dropped by other processes, etc.).
 - Investigate other alerts associated with the user/host during the past 48 hours.
 
-### False positive analysis
 
-- The usage of these script engines by regular users is unlikely. In the case of authorized benign true positives
-(B-TPs), exceptions can be added.
+*False positive analysis*
+
+
+- The usage of these script engines by regular users is unlikely. In the case of authorized benign true positives (B-TPs), exceptions can be added.
+
+
+*Response and remediation*
 
-### Response and remediation
 
 - Initiate the incident response process based on the outcome of the triage.
 - Isolate the involved host to prevent further post-compromise behavior.
@@ -87,8 +96,7 @@ for prevalence, whether they are located in expected locations, and if they are
   - Implement temporary network rules, procedures, and segmentation to contain the malware.
   - Stop suspicious processes.
   - Immediately block the identified indicators of compromise (IoCs).
-  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that
-  attackers could use to reinfect the system.
+  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 - Remove and block malicious artifacts identified during triage.
 - If the malicious file was delivered via phishing:
   - Block the email sender from sending future emails.
@@ -96,24 +104,39 @@ for prevalence, whether they are located in expected locations, and if they are
   - Remove emails from the sender from mailboxes.
   - Consider improvements to the security awareness program.
 - Reimage the host operating system and restore compromised files to clean versions.
-- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
-malware components.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 - Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
-- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the
-mean time to respond (MTTR).
-----------------------------------
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
+events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
+Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
+`event.ingested` to @timestamp.
+For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and process.parent.name :
-("cscript.exe", "wscript.exe") and process.name : "powershell.exe"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.parent.name : ("cscript.exe", "wscript.exe") and process.name : "powershell.exe" and
+  not (
+    process.parent.name : "wscript.exe" and
+    process.parent.args : "?:\\ProgramData\\intune-drive-mapping-generator\\IntuneDriveMapping-VBSHelper.vbs" and
+    process.parent.args : "?:\\ProgramData\\intune-drive-mapping-generator\\DriveMapping.ps1"
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -125,74 +148,23 @@ process where event.type == "start" and process.parent.name :
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[windows-script-executing-powershell-history]]
-==== Rule version history
-
-Version 102 (8.6.0 release)::
-* Formatting only
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-process where event.type in ("start", "process_started") and
-process.parent.name : ("cscript.exe", "wscript.exe") and process.name
-: "powershell.exe"
-----------------------------------
-
-Version 13 (8.4.0 release)::
-* Formatting only
-
-Version 11 (8.3.0 release)::
-* Formatting only
-
-Version 10 (8.2.0 release)::
-* Formatting only
-
-Version 9 (7.13.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.category:process and event.type:(start or process_started) and
-process.parent.name:(cscript.exe or wscript.exe) and
-process.name:powershell.exe
-----------------------------------
-
-Version 8 (7.12.0 release)::
-* Formatting only
-
-Version 7 (7.11.2 release)::
-* Formatting only
-
-Version 6 (7.11.0 release)::
-* Formatting only
-
-Version 5 (7.10.0 release)::
-* Formatting only
-
-Version 4 (7.9.1 release)::
-* Formatting only
-
-Version 3 (7.9.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.parent.name:(cscript.exe or wscript.exe) and
-process.name:powershell.exe
-----------------------------------
-
-Version 2 (7.7.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-event.action:"Process Create (rule: ProcessCreate)" and
-process.parent.name:("wscript.exe" or "cscript.exe") and
-process.name:"powershell.exe"
-----------------------------------
-
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: PowerShell
+** ID: T1059.001
+** Reference URL: https://attack.mitre.org/techniques/T1059/001/
+* Sub-technique:
+** Name: Visual Basic
+** ID: T1059.005
+** Reference URL: https://attack.mitre.org/techniques/T1059/005/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-script-interpreter-executing-process-via-wmi.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-script-interpreter-executing-process-via-wmi.asciidoc
index 85ed09f2ef..75dcbd180f 100644
--- a/docs/detections/prebuilt-rules/rule-details/windows-script-interpreter-executing-process-via-wmi.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/windows-script-interpreter-executing-process-via-wmi.asciidoc
@@ -5,62 +5,82 @@ Identifies use of the built-in Windows script interpreters (cscript.exe or wscri
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
-* logs-windows.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.library-*
+* logs-windows.sysmon_operational-*
+* endgame-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Initial Access
+*Tags*: 
 
-*Version*: 101 (<<windows-script-interpreter-executing-process-via-wmi-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Initial Access
+* Tactic: Execution
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 109
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan = 5s [any where (event.category
-== "library" or (event.category == "process" and event.action : "Image
-loaded*")) and (dll.name : "wmiutils.dll" or file.name :
-"wmiutils.dll") and process.name : ("wscript.exe", "cscript.exe")]
-[process where event.type == "start" and process.parent.name :
-"wmiprvse.exe" and user.domain != "NT AUTHORITY" and
-(process.pe.original_file_name : ( "cscript.exe",
-"wscript.exe", "PowerShell.EXE", "Cmd.Exe",
-"MSHTA.EXE", "RUNDLL32.EXE", "REGSVR32.EXE",
-"MSBuild.exe", "InstallUtil.exe", "RegAsm.exe",
-"RegSvcs.exe", "msxsl.exe", "CONTROL.EXE",
-"EXPLORER.EXE", "Microsoft.Workflow.Compiler.exe",
-"msiexec.exe" ) or process.executable :
-("C:\\Users\\*.exe", "C:\\ProgramData\\*.exe") ) ]
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan = 5s
+    [any where host.os.type == "windows" and 
+     (event.category : ("library", "driver") or (event.category == "process" and event.action : "Image loaded*")) and
+     (?dll.name : "wmiutils.dll" or file.name : "wmiutils.dll") and process.name : ("wscript.exe", "cscript.exe")]
+    [process where host.os.type == "windows" and event.type == "start" and
+     process.parent.name : "wmiprvse.exe" and
+     user.domain != "NT AUTHORITY" and
+     (process.pe.original_file_name :
+        (
+          "cscript.exe",
+          "wscript.exe",
+          "PowerShell.EXE",
+          "Cmd.Exe",
+          "MSHTA.EXE",
+          "RUNDLL32.EXE",
+          "REGSVR32.EXE",
+          "MSBuild.exe",
+          "InstallUtil.exe",
+          "RegAsm.exe",
+          "RegSvcs.exe",
+          "msxsl.exe",
+          "CONTROL.EXE",
+          "EXPLORER.EXE",
+          "Microsoft.Workflow.Compiler.exe",
+          "msiexec.exe"
+        ) or
+      process.executable : ("C:\\Users\\*.exe", "C:\\ProgramData\\*.exe")
+     )
+    ]
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -72,73 +92,23 @@ loaded*")) and (dll.name : "wmiutils.dll" or file.name :
 ** Name: Phishing
 ** ID: T1566
 ** Reference URL: https://attack.mitre.org/techniques/T1566/
-
-[[windows-script-interpreter-executing-process-via-wmi-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan = 5s [any where (event.category
-== "library" or (event.category == "process" and event.action : "Image
-loaded*")) and (dll.name : "wmiutils.dll" or file.name :
-"wmiutils.dll") and process.name : ("wscript.exe", "cscript.exe")]
-[process where event.type in ("start", "process_started") and
-process.parent.name : "wmiprvse.exe" and user.domain != "NT
-AUTHORITY" and (process.pe.original_file_name : (
-"cscript.exe", "wscript.exe", "PowerShell.EXE",
-"Cmd.Exe", "MSHTA.EXE", "RUNDLL32.EXE",
-"REGSVR32.EXE", "MSBuild.exe", "InstallUtil.exe",
-"RegAsm.exe", "RegSvcs.exe", "msxsl.exe",
-"CONTROL.EXE", "EXPLORER.EXE",
-"Microsoft.Workflow.Compiler.exe", "msiexec.exe" )
-or process.executable : ("C:\\Users\\*.exe",
-"C:\\ProgramData\\*.exe") ) ]
-----------------------------------
-
-Version 4 (8.4.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan = 5s [library where dll.name :
-"wmiutils.dll" and process.name : ("wscript.exe", "cscript.exe")]
-[process where event.type in ("start", "process_started") and
-process.parent.name : "wmiprvse.exe" and user.domain != "NT
-AUTHORITY" and (process.pe.original_file_name : (
-"cscript.exe", "wscript.exe", "PowerShell.EXE",
-"Cmd.Exe", "MSHTA.EXE", "RUNDLL32.EXE",
-"REGSVR32.EXE", "MSBuild.exe", "InstallUtil.exe",
-"RegAsm.exe", "RegSvcs.exe", "msxsl.exe",
-"CONTROL.EXE", "EXPLORER.EXE",
-"Microsoft.Workflow.Compiler.exe", "msiexec.exe" )
-or process.executable : ("C:\\Users\\*.exe",
-"C:\\ProgramData\\*.exe") ) ]
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan=5s [library where file.name :
-"wmiutils.dll" and process.name : ("wscript.exe", "cscript.exe")]
-[process where event.type in ("start", "process_started") and
-process.parent.name : "wmiprvse.exe" and user.domain != "NT
-AUTHORITY" and (process.pe.original_file_name in
-( "cscript.exe",
-"wscript.exe", "PowerShell.EXE",
-"Cmd.Exe", "MSHTA.EXE",
-"RUNDLL32.EXE", "REGSVR32.EXE",
-"MSBuild.exe", "InstallUtil.exe",
-"RegAsm.exe", "RegSvcs.exe",
-"msxsl.exe", "CONTROL.EXE",
-"EXPLORER.EXE",
-"Microsoft.Workflow.Compiler.exe",
-"msiexec.exe" ) or
-process.executable : ("C:\\Users\\*.exe", "C:\\ProgramData\\*.exe")
-) ]
-----------------------------------
-
+* Sub-technique:
+** Name: Spearphishing Attachment
+** ID: T1566.001
+** Reference URL: https://attack.mitre.org/techniques/T1566/001/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Command and Scripting Interpreter
+** ID: T1059
+** Reference URL: https://attack.mitre.org/techniques/T1059/
+* Sub-technique:
+** Name: Visual Basic
+** ID: T1059.005
+** Reference URL: https://attack.mitre.org/techniques/T1059/005/
+* Technique:
+** Name: Windows Management Instrumentation
+** ID: T1047
+** Reference URL: https://attack.mitre.org/techniques/T1047/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-service-installed-via-an-unusual-client.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-service-installed-via-an-unusual-client.asciidoc
index ff285bee34..0a77aa1f1d 100644
--- a/docs/detections/prebuilt-rules/rule-details/windows-service-installed-via-an-unusual-client.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/windows-service-installed-via-an-unusual-client.asciidoc
@@ -3,67 +3,84 @@
 
 Identifies the creation of a Windows service by an unusual client process. Services may be created with administrator privileges but are executed under SYSTEM privileges, so an adversary may also use a service to escalate privileges from administrator to SYSTEM.
 
-*Rule type*: query
+*Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
 * logs-system.*
+* logs-windows.*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://www.x86matthew.com/view_post?id=create_svc_rpc
 * https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4697
 * https://github.com/atc-project/atomic-threat-coverage/blob/master/Atomic_Threat_Coverage/Logging_Policies/LP_0100_windows_audit_security_system_extension.md
 
-*Tags*:
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+
+*Version*: 109
+
+*Rule authors*: 
 
 * Elastic
-* Host
-* Windows
-* Threat Detection
-* Privilege Escalation
 
-*Version*: 100 (<<windows-service-installed-via-an-unusual-client-history, version history>>)
+*Rule license*: Elastic License v2
 
-*Added ({stack} release)*: 8.1.0
 
-*Last modified ({stack} release)*: 8.5.0
+==== Setup
 
-*Rule authors*: Elastic
 
-*Rule license*: Elastic License v2
 
-==== Investigation guide
+*Setup*
 
 
-[source,markdown]
-----------------------------------
+The 'Audit Security System Extension' logging policy must be configured for (Success)
+Steps to implement the logging policy with Advanced Audit Configuration:
 
-----------------------------------
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+System >
+Audit Security System Extension (Success)
+```
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.action:"service-installed" and
-(winlog.event_data.ClientProcessId:"0" or
-winlog.event_data.ParentProcessId:"0")
+[source, js]
 ----------------------------------
+configuration where host.os.type == "windows" and
+  event.action == "service-installed" and
+  (winlog.event_data.ClientProcessId == "0" or winlog.event_data.ParentProcessId == "0") and
+  not winlog.event_data.ServiceFileName : (
+    "?:\\Windows\\VeeamVssSupport\\VeeamGuestHelper.exe",
+    "?:\\Windows\\VeeamLogShipper\\VeeamLogShipper.exe",
+    "%SystemRoot%\\system32\\Drivers\\Crowdstrike\\*-CsInstallerService.exe",
+    "\"%windir%\\AdminArsenal\\PDQInventory-Scanner\\service-1\\PDQInventory-Scanner-1.exe\" "
+  )
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,13 +92,7 @@ winlog.event_data.ParentProcessId:"0")
 ** Name: Create or Modify System Process
 ** ID: T1543
 ** Reference URL: https://attack.mitre.org/techniques/T1543/
-
-[[windows-service-installed-via-an-unusual-client-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 3 (8.4.0 release)::
-* Formatting only
-
+* Sub-technique:
+** Name: Windows Service
+** ID: T1543.003
+** Reference URL: https://attack.mitre.org/techniques/T1543/003/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-subsystem-for-linux-distribution-installed.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-subsystem-for-linux-distribution-installed.asciidoc
new file mode 100644
index 0000000000..e0e1147a9a
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/windows-subsystem-for-linux-distribution-installed.asciidoc
@@ -0,0 +1,126 @@
+[[windows-subsystem-for-linux-distribution-installed]]
+=== Windows Subsystem for Linux Distribution Installed
+
+Detects changes to the registry that indicates the install of a new Windows Subsystem for Linux distribution by name. Adversaries may enable and use WSL for Linux to avoid detection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.registry-*
+* logs-windows.sysmon_operational-*
+* endgame-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://learn.microsoft.com/en-us/windows/wsl/wsl-config
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+* Data Source: Sysmon
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Windows Subsystem for Linux Distribution Installed*
+
+
+The Windows Subsystem for Linux (WSL) lets developers install a Linux distribution (such as Ubuntu, OpenSUSE, Kali, Debian, Arch Linux, etc) and use Linux applications, utilities, and Bash command-line tools directly on Windows, unmodified, without the overhead of a traditional virtual machine or dualboot setup. Attackers may abuse WSL to avoid security protections on a Windows host and perform a wide range of attacks.
+
+This rule identifies the installation of a new Windows Subsystem for Linux distribution via registry events.
+
+
+*Possible investigation steps*
+
+
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Examine which distribution was installed. Some distributions such as Kali Linux can facilitate the compromise of the environment.
+- Contact the account owner and confirm whether they are aware of this activity.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate that the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+
+
+*False positive analysis*
+
+
+- This is a dual-use tool, meaning its usage is not inherently malicious. Analysts can dismiss the alert if the administrator is aware of the activity, no other suspicious activity was identified, and the WSL distribution is homologated and approved in the environment.
+
+
+*Related Rules*
+
+
+- Host Files System Changes via Windows Subsystem for Linux - e88d1fe9-b2f4-48d4-bace-a026dc745d4b
+- Execution via Windows Subsystem for Linux - db7dbad5-08d2-4d25-b9b1-d3a1e4a15efd
+- Suspicious Execution via Windows Subsystem for Linux - 3e0eeb75-16e8-4f2f-9826-62461ca128b7
+- Windows Subsystem for Linux Enabled via Dism Utility - e2e0537d-7d8f-4910-a11d-559bcf61295a
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+registry where host.os.type == "windows" and
+ registry.path : 
+       ("HK*\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Lxss\\*\\PackageFamilyName",
+        "\\REGISTRY\\*\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Lxss\\*\\PackageFamilyName")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Modify Registry
+** ID: T1112
+** Reference URL: https://attack.mitre.org/techniques/T1112/
+* Technique:
+** Name: Indirect Command Execution
+** ID: T1202
+** Reference URL: https://attack.mitre.org/techniques/T1202/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-subsystem-for-linux-enabled-via-dism-utility.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-subsystem-for-linux-enabled-via-dism-utility.asciidoc
new file mode 100644
index 0000000000..46cd1c47f6
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/windows-subsystem-for-linux-enabled-via-dism-utility.asciidoc
@@ -0,0 +1,120 @@
+[[windows-subsystem-for-linux-enabled-via-dism-utility]]
+=== Windows Subsystem for Linux Enabled via Dism Utility
+
+Detects attempts to enable the Windows Subsystem for Linux using Microsoft Dism utility. Adversaries may enable and use WSL for Linux to avoid detection.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://blog.f-secure.com/hunting-for-windows-subsystem-for-linux/
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Elastic Endgame
+* Data Source: Elastic Defend
+
+*Version*: 7
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Windows Subsystem for Linux Enabled via Dism Utility*
+
+
+The Windows Subsystem for Linux (WSL) lets developers install a Linux distribution (such as Ubuntu, OpenSUSE, Kali, Debian, Arch Linux, etc) and use Linux applications, utilities, and Bash command-line tools directly on Windows, unmodified, without the overhead of a traditional virtual machine or dualboot setup. Attackers may abuse WSL to avoid security protections on a Windows host and perform a wide range of attacks.
+
+This rule identifies attempts to enable WSL using the Dism utility. It monitors for the execution of Dism and checks if the command line contains the string "Microsoft-Windows-Subsystem-Linux". 
+
+
+*Possible investigation steps*
+
+
+- Identify the user account that performed the action and whether it should perform this kind of action.
+- Contact the account owner and confirm whether they are aware of this activity.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
+- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
+
+
+*False positive analysis*
+
+
+- This is a dual-use tool, meaning its usage is not inherently malicious. Analysts can dismiss the alert if the administrator is aware of the activity, no other suspicious activity was identified, and WSL is homologated and approved in the environment.
+
+
+*Related Rules*
+
+
+- Execution via Windows Subsystem for Linux - db7dbad5-08d2-4d25-b9b1-d3a1e4a15efd
+- Suspicious Execution via Windows Subsystem for Linux - 3e0eeb75-16e8-4f2f-9826-62461ca128b7
+- Host Files System Changes via Windows Subsystem for Linux - e88d1fe9-b2f4-48d4-bace-a026dc745d4b
+- Windows Subsystem for Linux Distribution Installed - a1699af0-8e1e-4ed0-8ec1-89783538a061
+
+
+*Response and Remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type : "start" and
+ (process.name : "Dism.exe" or ?process.pe.original_file_name == "DISM.EXE") and 
+ process.command_line : "*Microsoft-Windows-Subsystem-Linux*"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: Indirect Command Execution
+** ID: T1202
+** Reference URL: https://attack.mitre.org/techniques/T1202/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-system-information-discovery.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-system-information-discovery.asciidoc
new file mode 100644
index 0000000000..ec72094816
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/windows-system-information-discovery.asciidoc
@@ -0,0 +1,80 @@
+[[windows-system-information-discovery]]
+=== Windows System Information Discovery
+
+Detects the execution of commands used to discover information about the system, which attackers may use after compromising a system to gain situational awareness.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-endpoint.events.process-*
+* logs-windows.*
+* endgame-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+* Data Source: Elastic Endgame
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+(
+  (
+    process.name : "cmd.exe" and process.args : "ver*" and not
+    process.parent.executable : (
+        "?:\\Users\\*\\AppData\\Local\\Keybase\\upd.exe",
+        "?:\\Users\\*\\python*.exe"
+    )
+  ) or 
+  process.name : ("systeminfo.exe", "hostname.exe") or 
+  (process.name : "wmic.exe" and process.args : "os" and process.args : "get")
+) and not
+process.parent.executable : (
+    "?:\\Program Files\\*",
+    "?:\\Program Files (x86)\\*",
+    "?:\\ProgramData\\*"
+) and not user.id : "S-1-5-18"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-system-network-connections-discovery.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-system-network-connections-discovery.asciidoc
new file mode 100644
index 0000000000..912fccf1fc
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/windows-system-network-connections-discovery.asciidoc
@@ -0,0 +1,77 @@
+[[windows-system-network-connections-discovery]]
+=== Windows System Network Connections Discovery
+
+This rule identifies the execution of commands that can be used to enumerate network connections. Adversaries may attempt to get a listing of network connections to or from a compromised system to identify targets within an environment.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Discovery
+* Rule Type: BBR
+* Data Source: Elastic Defend
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where event.type == "start" and
+(
+  process.name : "netstat.exe" or
+  (
+   (
+    (process.name : "net.exe" or process.pe.original_file_name == "net.exe") or
+    (
+     (process.name : "net1.exe" or process.pe.original_file_name == "net1.exe") and
+     not process.parent.name : "net.exe"
+    )
+   ) and process.args : ("use", "user", "session", "config") and not process.args: ("/persistent:*", "/delete", "\\\\*")
+  ) or
+  (process.name : "nbtstat.exe" and process.args : "-s*")
+) and not user.id : "S-1-5-18"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Discovery
+** ID: TA0007
+** Reference URL: https://attack.mitre.org/tactics/TA0007/
+* Technique:
+** Name: System Network Connections Discovery
+** ID: T1049
+** Reference URL: https://attack.mitre.org/techniques/T1049/
+* Technique:
+** Name: System Information Discovery
+** ID: T1082
+** Reference URL: https://attack.mitre.org/techniques/T1082/
diff --git a/docs/detections/prebuilt-rules/rule-details/windows-user-account-creation.asciidoc b/docs/detections/prebuilt-rules/rule-details/windows-user-account-creation.asciidoc
new file mode 100644
index 0000000000..c19f1cc29d
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/windows-user-account-creation.asciidoc
@@ -0,0 +1,69 @@
+[[windows-user-account-creation]]
+=== Windows User Account Creation
+
+Identifies attempts to create a Windows User Account. This is sometimes done by attackers to persist or increase access to a system or domain.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-system.*
+* logs-windows.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 5m
+
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Persistence
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Skoetting
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.module:("system" or "security") and winlog.api:"wineventlog" and
+  (event.code:"4720" or event.action:"added-user-account")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Persistence
+** ID: TA0003
+** Reference URL: https://attack.mitre.org/tactics/TA0003/
+* Technique:
+** Name: Create Account
+** ID: T1136
+** Reference URL: https://attack.mitre.org/techniques/T1136/
+* Sub-technique:
+** Name: Local Account
+** ID: T1136.001
+** Reference URL: https://attack.mitre.org/techniques/T1136/001/
+* Sub-technique:
+** Name: Domain Account
+** ID: T1136.002
+** Reference URL: https://attack.mitre.org/techniques/T1136/002/
diff --git a/docs/detections/prebuilt-rules/rule-details/wireless-credential-dumping-using-netsh-command.asciidoc b/docs/detections/prebuilt-rules/rule-details/wireless-credential-dumping-using-netsh-command.asciidoc
index bc69197605..edc82f3bc4 100644
--- a/docs/detections/prebuilt-rules/rule-details/wireless-credential-dumping-using-netsh-command.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/wireless-credential-dumping-using-netsh-command.asciidoc
@@ -5,66 +5,114 @@ Identifies attempts to dump Wireless saved access keys in clear text using the W
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
 * winlogbeat-*
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
 * logs-windows.*
 * endgame-*
+* logs-system.security*
 
 *Severity*: high
 
 *Risk score*: 73
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://learn.microsoft.com/en-us/windows-server/networking/technologies/netsh/netsh-contexts
 * https://www.geeksforgeeks.org/how-to-find-the-wi-fi-password-using-cmd-in-windows/
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Credential Access
-* Discovery
-* Elastic Endgame
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Credential Access
+* Tactic: Discovery
+* Data Source: Elastic Endgame
+* Resources: Investigation Guide
+* Data Source: Elastic Defend
 
-*Version*: 1
+*Version*: 8
 
-*Added ({stack} release)*: 8.6.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Investigation guide
 
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+*Triage and analysis*
+
+
+
+*Investigating Wireless Credential Dumping using Netsh Command*
+
+
+Netsh is a Windows command line tool used for network configuration and troubleshooting. It enables the management of network settings and adapters, wireless network profiles, and other network-related tasks.
+
+This rule looks for patterns used to dump credentials from wireless network profiles using Netsh, which can enable attackers to bring their own devices to the network.
+
+> **Note**:
+> This investigation guide uses the https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html[Osquery Markdown Plugin] introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
+
+
+*Possible investigation steps*
+
+
+- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
+- Investigate other alerts associated with the user/host during the past 48 hours.
+- Inspect the host for suspicious or abnormal behavior in the alert timeframe:
+  - Observe and collect information about the following activities in the alert subject host:
+    - Attempts to contact external domains and addresses.
+      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
+      - Examine the DNS cache for suspicious or anomalous entries.
+        - !{osquery{"label":"Osquery - Retrieve DNS Cache","query":"SELECT * FROM dns_cache"}}
+    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
+    - Examine the host services for suspicious or anomalous entries.
+      - !{osquery{"label":"Osquery - Retrieve All Services","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"}}
+      - !{osquery{"label":"Osquery - Retrieve Services Running on User Accounts","query":"SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE\nNOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR\nuser_account == null)\n"}}
+      - !{osquery{"label":"Osquery - Retrieve Service Unsigned Executables with Virustotal Link","query":"SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,\nservices.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =\nauthenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'\n"}}
+
+
+*False positive analysis*
+
+
+- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
+
+
+*Response and remediation*
+
+
+- Initiate the incident response process based on the outcome of the triage.
+- Isolate the involved host to prevent further post-compromise behavior.
+- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
+- Review the privileges assigned to the user to ensure that the least privilege principle is being followed.
+- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
+- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
+- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 
 
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-process where event.type == "start" and (process.name : "netsh.exe"
-or process.pe.original_file_name == "netsh.exe") and process.args :
-"wlan" and process.args : "key*clear"
+[source, js]
 ----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+ (process.name : "netsh.exe" or ?process.pe.original_file_name == "netsh.exe") and
+  process.args : "wlan" and process.args : "key*clear"
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -76,8 +124,10 @@ or process.pe.original_file_name == "netsh.exe") and process.args :
 ** Name: OS Credential Dumping
 ** ID: T1003
 ** Reference URL: https://attack.mitre.org/techniques/T1003/
-
-
+* Technique:
+** Name: Credentials from Password Stores
+** ID: T1555
+** Reference URL: https://attack.mitre.org/techniques/T1555/
 * Tactic:
 ** Name: Discovery
 ** ID: TA0007
diff --git a/docs/detections/prebuilt-rules/rule-details/wmi-incoming-lateral-movement.asciidoc b/docs/detections/prebuilt-rules/rule-details/wmi-incoming-lateral-movement.asciidoc
index 8f60a69fc2..f7936746bc 100644
--- a/docs/detections/prebuilt-rules/rule-details/wmi-incoming-lateral-movement.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/wmi-incoming-lateral-movement.asciidoc
@@ -5,60 +5,72 @@ Identifies processes executed via Windows Management Instrumentation (WMI) on a
 
 *Rule type*: eql
 
-*Rule indices*:
+*Rule indices*: 
 
-* logs-endpoint.events.*
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
 * winlogbeat-*
-* logs-windows.*
+* logs-windows.sysmon_operational-*
 
 *Severity*: medium
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
 *Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*Tags*:
+*References*: None
 
-* Elastic
-* Host
-* Windows
-* Threat Detection
-* Lateral Movement
+*Tags*: 
 
-*Version*: 101 (<<wmi-incoming-lateral-movement-history, version history>>)
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+* Data Source: Sysmon
 
-*Added ({stack} release)*: 7.11.0
+*Version*: 110
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-sequence by host.id with maxspan = 2s /* Accepted Incoming RPC
-connection by Winmgmt service */ [network where process.name :
-"svchost.exe" and network.direction : ("incoming", "ingress") and
-source.ip != "127.0.0.1" and source.ip != "::1" and source.port >=
-49152 and destination.port >= 49152 ] /* Excluding Common FPs
-Nessus and SCCM */ [process where event.type == "start" and
-process.parent.name : "WmiPrvSE.exe" and not process.args :
-("C:\\windows\\temp\\nessus_*.txt",
-"C:\\windows\\TEMP\\nessus_*.TMP",
-"C:\\Windows\\CCM\\SystemTemp\\*",
-"C:\\Windows\\CCMCache\\*",
-"C:\\CCM\\Cache\\*") ]
+[source, js]
 ----------------------------------
+sequence by host.id with maxspan = 2s
+
+ /* Accepted Incoming RPC connection by Winmgmt service */
+
+  [network where host.os.type == "windows" and process.name : "svchost.exe" and network.direction : ("incoming", "ingress") and
+   source.ip != "127.0.0.1" and source.ip != "::1" and source.port >= 49152 and destination.port >= 49152
+  ]
+
+  /* Excluding Common FPs Nessus and SCCM */
 
-==== Threat mapping
+  [process where host.os.type == "windows" and event.type == "start" and process.parent.name : "WmiPrvSE.exe" and
+   not (?process.Ext.token.integrity_level_name : "System" or ?winlog.event_data.IntegrityLevel : "System") and
+   not user.id : ("S-1-5-18", "S-1-5-19", "S-1-5-20") and
+   not process.executable :
+               ("?:\\Program Files\\HPWBEM\\Tools\\hpsum_swdiscovery.exe",
+                "?:\\Windows\\CCM\\Ccm32BitLauncher.exe",
+                "?:\\Windows\\System32\\wbem\\mofcomp.exe",
+                "?:\\Windows\\Microsoft.NET\\Framework*\\csc.exe",
+                "?:\\Windows\\System32\\powercfg.exe") and
+   not (process.executable : "?:\\Windows\\System32\\msiexec.exe" and process.args : "REBOOT=ReallySuppress") and
+   not (process.executable : "?:\\Windows\\System32\\inetsrv\\appcmd.exe" and process.args : "uninstall")
+   ]
+
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -66,8 +78,10 @@ process.parent.name : "WmiPrvSE.exe" and not process.args :
 ** Name: Lateral Movement
 ** ID: TA0008
 ** Reference URL: https://attack.mitre.org/tactics/TA0008/
-
-
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
 * Tactic:
 ** Name: Execution
 ** ID: TA0002
@@ -76,70 +90,3 @@ process.parent.name : "WmiPrvSE.exe" and not process.args :
 ** Name: Windows Management Instrumentation
 ** ID: T1047
 ** Reference URL: https://attack.mitre.org/techniques/T1047/
-
-[[wmi-incoming-lateral-movement-history]]
-==== Rule version history
-
-Version 101 (8.5.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan = 2s /* Accepted Incoming RPC
-connection by Winmgmt service */ [network where process.name :
-"svchost.exe" and network.direction : ("incoming", "ingress") and
-source.ip != "127.0.0.1" and source.ip != "::1" and source.port >=
-49152 and destination.port >= 49152 ] /* Excluding Common FPs
-Nessus and SCCM */ [process where event.type in ("start",
-"process_started") and process.parent.name : "WmiPrvSE.exe" and not
-process.args : ("C:\\windows\\temp\\nessus_*.txt",
-"C:\\windows\\TEMP\\nessus_*.TMP",
-"C:\\Windows\\CCM\\SystemTemp\\*",
-"C:\\Windows\\CCMCache\\*",
-"C:\\CCM\\Cache\\*") ]
-----------------------------------
-
-Version 5 (8.4.0 release)::
-* Formatting only
-
-Version 4 (8.0.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan = 2s /* Accepted Incoming RPC
-connection by Winmgmt service */ [network where process.name :
-"svchost.exe" and network.direction : ("incoming", "ingress") and
-source.address != "127.0.0.1" and source.address != "::1" and
-source.port >= 49152 and destination.port >= 49152 ] /* Excluding
-Common FPs Nessus and SCCM */ [process where event.type in
-("start", "process_started") and process.parent.name : "WmiPrvSE.exe"
-and not process.args : ("C:\\windows\\temp\\nessus_*.txt",
-"C:\\windows\\TEMP\\nessus_*.TMP",
-"C:\\Windows\\CCM\\SystemTemp\\*",
-"C:\\Windows\\CCMCache\\*",
-"C:\\CCM\\Cache\\*") ]
-----------------------------------
-
-Version 3 (7.16.0 release)::
-* Updated query, changed from:
-+
-[source, js]
-----------------------------------
-sequence by host.id with maxspan = 2s /* Accepted Incoming RPC
-connection by Winmgmt service */ [network where process.name :
-"svchost.exe" and network.direction == "incoming" and
-source.address != "127.0.0.1" and source.address != "::1" and
-source.port >= 49152 and destination.port >= 49152 ] /* Excluding
-Common FPs Nessus and SCCM */ [process where event.type in
-("start", "process_started") and process.parent.name : "WmiPrvSE.exe"
-and not process.args : ("C:\\windows\\temp\\nessus_*.txt",
-"C:\\windows\\TEMP\\nessus_*.TMP",
-"C:\\Windows\\CCM\\SystemTemp\\*",
-"C:\\Windows\\CCMCache\\*",
-"C:\\CCM\\Cache\\*") ]
-----------------------------------
-
-Version 2 (7.12.0 release)::
-* Formatting only
-
diff --git a/docs/detections/prebuilt-rules/rule-details/wmi-wbemtest-utility-execution.asciidoc b/docs/detections/prebuilt-rules/rule-details/wmi-wbemtest-utility-execution.asciidoc
new file mode 100644
index 0000000000..c45f9a481e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/wmi-wbemtest-utility-execution.asciidoc
@@ -0,0 +1,65 @@
+[[wmi-wbemtest-utility-execution]]
+=== WMI WBEMTEST Utility Execution
+
+Adversaries may abuse the WMI diagnostic tool, wbemtest.exe, to enumerate WMI object instances or invoke methods against local or remote endpoints.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* winlogbeat-*
+* logs-windows.*
+* endgame-*
+* logs-system.security*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Execution
+* Data Source: Elastic Defend
+* Rule Type: BBR
+* Data Source: Elastic Endgame
+
+*Version*: 2
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and process.name : "wbemtest.exe"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Windows Management Instrumentation
+** ID: T1047
+** Reference URL: https://attack.mitre.org/techniques/T1047/
diff --git a/docs/detections/prebuilt-rules/rule-details/wmic-remote-command.asciidoc b/docs/detections/prebuilt-rules/rule-details/wmic-remote-command.asciidoc
new file mode 100644
index 0000000000..84dbb6f992
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/wmic-remote-command.asciidoc
@@ -0,0 +1,76 @@
+[[wmic-remote-command]]
+=== WMIC Remote Command
+
+Identifies the use of wmic.exe to run commands on remote hosts. While this can be used by administrators legitimately, attackers can abuse this built-in utility to achieve lateral movement.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Lateral Movement
+* Data Source: Elastic Defend
+* Rule Type: BBR
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+process where host.os.type == "windows" and event.type == "start" and
+  process.name : "WMIC.exe" and
+  process.args : "*node:*" and
+  process.args : ("call", "set", "get") and
+  not process.args : ("*/node:localhost*", "*/node:\"127.0.0.1\"*", "/node:127.0.0.1")
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Lateral Movement
+** ID: TA0008
+** Reference URL: https://attack.mitre.org/tactics/TA0008/
+* Technique:
+** Name: Remote Services
+** ID: T1021
+** Reference URL: https://attack.mitre.org/techniques/T1021/
+* Sub-technique:
+** Name: Windows Remote Management
+** ID: T1021.006
+** Reference URL: https://attack.mitre.org/techniques/T1021/006/
+* Tactic:
+** Name: Execution
+** ID: TA0002
+** Reference URL: https://attack.mitre.org/tactics/TA0002/
+* Technique:
+** Name: Windows Management Instrumentation
+** ID: T1047
+** Reference URL: https://attack.mitre.org/techniques/T1047/
diff --git a/docs/detections/prebuilt-rules/rule-details/wpad-service-exploit.asciidoc b/docs/detections/prebuilt-rules/rule-details/wpad-service-exploit.asciidoc
new file mode 100644
index 0000000000..371729d962
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/wpad-service-exploit.asciidoc
@@ -0,0 +1,74 @@
+[[wpad-service-exploit]]
+=== WPAD Service Exploit
+
+Identifies probable exploitation of the Web Proxy Auto-Discovery Protocol (WPAD) service. Attackers who have access to the local network or upstream DNS traffic can inject malicious JavaScript to the WPAD service which can lead to a full system compromise.
+
+*Rule type*: eql
+
+*Rule indices*: 
+
+* logs-endpoint.events.process-*
+* logs-endpoint.events.network-*
+* logs-endpoint.events.library-*
+
+*Severity*: high
+
+*Risk score*: 73
+
+*Runs every*: 5m
+
+*Searches indices from*: now-9m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: None
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Privilege Escalation
+* Data Source: Elastic Defend
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+/* preference would be to use user.sid rather than domain+name, once it is available in ECS + datasources */
+/* didn't trigger successfully during testing */
+
+sequence with maxspan=5s
+  [process where host.os.type == "windows" and event.type == "start" and process.name : "svchost.exe" and
+     user.domain : "NT AUTHORITY" and user.name : "LOCAL SERVICE"] by process.entity_id
+  [network where host.os.type == "windows" and network.protocol : "dns" and process.name : "svchost.exe" and
+     dns.question.name : "wpad" and process.name : "svchost.exe"] by process.entity_id
+  [network where host.os.type == "windows" and process.name : "svchost.exe"
+     and network.direction : ("outgoing", "egress") and destination.port == 80] by process.entity_id
+  [library where host.os.type == "windows" and event.type : "start" and process.name : "svchost.exe" and
+     dll.name : "jscript.dll" and process.name : "svchost.exe"] by process.entity_id
+  [process where host.os.type == "windows" and event.type == "start" and
+     process.parent.name : "svchost.exe"] by process.parent.entity_id
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Privilege Escalation
+** ID: TA0004
+** Reference URL: https://attack.mitre.org/tactics/TA0004/
+* Technique:
+** Name: Exploitation for Privilege Escalation
+** ID: T1068
+** Reference URL: https://attack.mitre.org/techniques/T1068/
diff --git a/docs/detections/prebuilt-rules/rule-details/writedac-access-on-active-directory-object.asciidoc b/docs/detections/prebuilt-rules/rule-details/writedac-access-on-active-directory-object.asciidoc
new file mode 100644
index 0000000000..95bd84cf1e
--- /dev/null
+++ b/docs/detections/prebuilt-rules/rule-details/writedac-access-on-active-directory-object.asciidoc
@@ -0,0 +1,92 @@
+[[writedac-access-on-active-directory-object]]
+=== WRITEDAC Access on Active Directory Object
+
+Identifies the access on an object with WRITEDAC permissions. With the WRITEDAC permission, the user can perform a Write Discretionary Access Control List (WriteDACL) operation, which is used to modify the access control rules associated with a specific object within Active Directory. Attackers may abuse this privilege to grant themselves or other compromised accounts additional rights, ultimately compromising the target object, resulting in privilege escalation, lateral movement, and persistence.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* winlogbeat-*
+* logs-system.security*
+* logs-windows.*
+
+*Severity*: low
+
+*Risk score*: 21
+
+*Runs every*: 60m
+
+*Searches indices from*: now-119m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 100
+
+*References*: 
+
+* https://www.blackhat.com/docs/us-17/wednesday/us-17-Robbins-An-ACE-Up-The-Sleeve-Designing-Active-Directory-DACL-Backdoors.pdf
+
+*Tags*: 
+
+* Domain: Endpoint
+* OS: Windows
+* Use Case: Threat Detection
+* Tactic: Defense Evasion
+* Data Source: Active Directory
+* Use Case: Active Directory Monitoring
+* Rule Type: BBR
+
+*Version*: 4
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+The 'Audit Directory Service Access' logging policy must be configured for (Success, Failure).
+Steps to implement the logging policy with Advanced Audit Configuration:
+
+```
+Computer Configuration >
+Policies >
+Windows Settings >
+Security Settings >
+Advanced Audit Policies Configuration >
+Audit Policies >
+DS Access >
+Audit Directory Service Access (Success,Failure)
+```
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+host.os.type: "windows" and event.action : ("Directory Service Access" or "object-operation-performed") and
+  event.code : "4662" and winlog.event_data.AccessMask:"0x40000"
+
+----------------------------------
+
+*Framework*: MITRE ATT&CK^TM^
+
+* Tactic:
+** Name: Defense Evasion
+** ID: TA0005
+** Reference URL: https://attack.mitre.org/tactics/TA0005/
+* Technique:
+** Name: File and Directory Permissions Modification
+** ID: T1222
+** Reference URL: https://attack.mitre.org/techniques/T1222/
+* Sub-technique:
+** Name: Windows File and Directory Permissions Modification
+** ID: T1222.001
+** Reference URL: https://attack.mitre.org/techniques/T1222/001/
diff --git a/docs/detections/prebuilt-rules/rule-details/zoom-meeting-with-no-passcode.asciidoc b/docs/detections/prebuilt-rules/rule-details/zoom-meeting-with-no-passcode.asciidoc
index 5a0fe5b277..eddf1a5535 100644
--- a/docs/detections/prebuilt-rules/rule-details/zoom-meeting-with-no-passcode.asciidoc
+++ b/docs/detections/prebuilt-rules/rule-details/zoom-meeting-with-no-passcode.asciidoc
@@ -5,7 +5,7 @@ This rule identifies Zoom meetings that are created without a passcode. Meetings
 
 *Rule type*: query
 
-*Rule indices*:
+*Rule indices*: 
 
 * filebeat-*
 
@@ -13,57 +13,50 @@ This rule identifies Zoom meetings that are created without a passcode. Meetings
 
 *Risk score*: 47
 
-*Runs every*: 5 minutes
+*Runs every*: 5m
 
-*Searches indices from*: now-6m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+*Searches indices from*: None ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
 
 *Maximum alerts per execution*: 100
 
-*References*:
+*References*: 
 
 * https://blog.zoom.us/a-message-to-our-users/
 * https://www.fbi.gov/contact-us/field-offices/boston/news/press-releases/fbi-warns-of-teleconferencing-and-online-classroom-hijacking-during-covid-19-pandemic
 
-*Tags*:
+*Tags*: 
 
-* Elastic
-* Application
-* Communication
-* Zoom
-* Continuous Monitoring
-* SecOps
-* Configuration Audit
-
-*Version*: 100 (<<zoom-meeting-with-no-passcode-history, version history>>)
+* Data Source: Zoom
+* Use Case: Configuration Audit
+* Tactic: Initial Access
 
-*Added ({stack} release)*: 7.10.0
+*Version*: 103
 
-*Last modified ({stack} release)*: 8.5.0
+*Rule authors*: 
 
-*Rule authors*: Elastic
+* Elastic
 
 *Rule license*: Elastic License v2
 
-==== Investigation guide
 
+==== Setup
 
-[source,markdown]
-----------------------------------
 
-----------------------------------
+
+*Setup*
 
 
+The Zoom Filebeat module or similarly structured data is required to be compatible with this rule.
+
 ==== Rule query
 
 
-[source,js]
-----------------------------------
-event.type:creation and event.module:zoom and
-event.dataset:zoom.webhook and event.action:meeting.created and not
-zoom.meeting.password:*
+[source, js]
 ----------------------------------
+event.type:creation and event.module:zoom and event.dataset:zoom.webhook and
+  event.action:meeting.created and not zoom.meeting.password:*
 
-==== Threat mapping
+----------------------------------
 
 *Framework*: MITRE ATT&CK^TM^
 
@@ -75,22 +68,3 @@ zoom.meeting.password:*
 ** Name: Exploit Public-Facing Application
 ** ID: T1190
 ** Reference URL: https://attack.mitre.org/techniques/T1190/
-
-[[zoom-meeting-with-no-passcode-history]]
-==== Rule version history
-
-Version 100 (8.5.0 release)::
-* Formatting only
-
-Version 6 (8.4.0 release)::
-* Formatting only
-
-Version 4 (7.13.0 release)::
-* Formatting only
-
-Version 3 (7.12.0 release)::
-* Formatting only
-
-Version 2 (7.11.2 release)::
-* Formatting only
-
diff --git a/docs/index.asciidoc b/docs/index.asciidoc
index d64655893d..3c6a90b547 100644
--- a/docs/index.asciidoc
+++ b/docs/index.asciidoc
@@ -89,3 +89,5 @@ include::detections/prebuilt-rules/downloadable-packages/8-5-1/prebuilt-rules-8-
 include::detections/prebuilt-rules/downloadable-packages/8-6-1/prebuilt-rules-8-6-1-appendix.asciidoc[]
 
 include::detections/prebuilt-rules/downloadable-packages/8-7-1/prebuilt-rules-8-7-1-appendix.asciidoc[]
+
+include::detections/prebuilt-rules/downloadable-packages/8-14-1/prebuilt-rules-8-14-1-appendix.asciidoc[]